开云体育

This is really just to test that our new mailing list is working properly. Dave AA6YQ and I have had quite a few discussions via private e-mail regarding various facets of DXLab. I can tell you first hand that he is very open to new ideas as long as they fit within his grand plan for the future of DXLab. Glad you could join our list, let's make it a good one. ----- 73, Rich - W3ZJ (List moderator) www.w3zj.com

Ron PA1ZX DXForecast http://members1.chello.nl/~r.a.f.eberson/DXF

Dave, Take a look at the following link http://www.ea4tx.com/index_en.htm which is some developers information on the rotor control that Ron asked about. From what I can gather it is not an RS232 interface but works with some plug in boards and drivers that you can access through DDE or Windows messaging. It looks like they would be happy to answer questions or help with the interface if you want to get involved with that. My guess is that the more software that supports them the happier they are. ----- 73, Rich - W3ZJ www.w3zj.com

Dave, I have been trying the new capture window and like it very much. This morning, I got the run time error from CI-V commander without WinWarbler running. What I had open was CI-V commander, DXKeeper (with the new capture window) and DXview. One small change of frequency from the radio dial and up came the error. It's not consistent though, I can't reproduce it at will. ----- 73, Rich - W3ZJ www.w3zj.com

I've added additional error trapping to this version -- hopefully the runtime error 6 crash W3ZJ's been experiencing will be replaced by an entry in the error log that helps me track down the root cause. Its quite possible that this error trapping will enable the program to recover gracefully, so keep an eye out for an errorlog.txt file in your CI-V Commander folder. CI-V Commander version 2.5.2 is available by downloading http://www.qsl.net/civ_commander/CI-V%20Commander252.exe and saving it into your CI-V Commander folder. You can then directly execute it. 73, Dave, AA6YQ --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote: > Dave, > > I have been trying the new capture window and like it very much. > This morning, I got the run time error from CI-V commander without > WinWarbler running. What I had open was CI-V commander, DXKeeper > (with the new capture window) and DXview. One small change of > frequency from the radio dial and up came the error. It's not > consistent though, I can't reproduce it at will. > > ----- > 73, Rich - W3ZJ > www.w3zj.com

Our man Kurt, OE1002419, noticed that both the FR and LZ callbook URLs had changed, tracked down the new URLs, and sent them my way. So we have him to thank for the updated Pathfinder searches now available. Keep in mind that the F callbook includes FR addresses, and so provides a second source of Reunion QSL info. To update your search library, click Pathfinder's "Info" button, or link to http://www.qsl.net/pathfinder/UpdateSearchLibrary.htm. The Pathfinder Web Client ( http://www.qsl.net/pathfinder/WebClient/ ) has been updated with the above changes; the only action required of its users is to click their Browser's "refresh" button. As always, reports of new online QSL sources or changes to existing sources are greatly appreciated. 73, Dave, AA6YQ Pathfinder is a free program that makes it easy to find QSL information from more than 100 web-accessible sources. See http://www.qsl.net/pathfinder/ for additional information and download instructions. Or use the Pathfinder Web Client -- its a little less flexible, but requires no downloading or installation and runs in any Javascript-supporting browser on Windows, MacOS, Linux, or Unix; just visit http://www.qsl.net/pathfinder/WebClient/ .

The primary purpose of this release is to correct the defect in Hygain DCU rotator support reported by Julio below. I learned from Ed at DataMatrix (the developers of ProLog) that the "set bearing" and "move rotator" commands must be separated by at least 150ms, which explains why clicking the SP button once fails, but clicking it twice succeeds. Without a Hygain rotator, my testing is limited, so Julio please let me know whether this eliminates the problem. If anyone else is using a Hygain rotator -- with either the Rotor EZ or standard Hygain controller -- I'd also appreciate a works/fails report. While I was in the code, I added direct latitude/longitude entry, and added the mechanism required for interoperation with PropView. This release is available by downloading http://www.qsl.net/dxview/DXView125Update.exe - store it in your DXView folder and execute it. You can then run the extracted DXView125.exe . 73, Dave, AA6YQ -----Original Message----- From: Julio [mailto:jperalta@...] Sent: Monday, March 12, 2001 18:09 PM To: Bernstein, Dave Subject: Re: DXView Dave I hope you don't construe this as complaining, at this point my comments are to help, as I understand you are doing some beta testing or something of that sort. When I have the main DXView window up and I set a rotor heading either by adding a callsign or clicking on a country it requires 2 clicks of the mouse on the SP or LP button to start the rotor in motion. I've even tried the clicks as long as 10 seconds apart and it will still activate the rotor action. One click will not start the rotor! I'm not sure if this is how you wanted it to work, but I suspect not. Thanks again, 73's Julio

Dave, When I click on a callsign in DXKeeper, obviously I have worked the guy, but the progress window does not always indicate any contact with his country. Also, I have worked 3G0Y 8 times on 80,30,20,10 meter CW, and 10, 15 meter SSB. The progress window shows only an F in CW and 40 meters. DXView shows that the prefix is CE0E. So I entered that in the filter window and clicked DXCC it came up with another station on Easter Island that I had worked on 40 CW but nothing for 3G0Y. I did a recompile in the progress window but nothing changed. Also, when I do a DXCC Summary, it shows 97 countries worked and 96 confirmed. Logger, which has a duplicate of the same log shows 252 countries worked and 52 confirmed which is correct. There are just short of 5000 entries in my log dating back to November 1999. Most of the entries in DXKeeper were imported from Logger. ----- 73, Rich - W3ZJ www.w3zj.com

Along with the DXCC database support described below, this release also includes updated online help, which is accessible via http://www.qsl.net/dxkeeper/Help/index.htm . If you've installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.5 by downloading and then running www.qsl.net/dxkeeper/DXKeeper115Update.exe -- your online help will automatically be update by this process. 73, Dave, AA6YQ --- In dxlab@y..., "Dave Bernstein" <dhb@m...> wrote: > To ensure its ability to perform callsign lookups, DXKeeper will from > now on include a copy of the DXCC database previously only packaged > with DXView. During startup, DXKeeper will determine whether DXView > is installed. If so, it will reference DXView's copy of this > database, ignoring its own copy -- this permits a single point of > database maintenance, e.g. when adding a new DXCC entity. If DXView > is not installed, then DXView will refer to its own copy of the > database. > > Callsign lookups during import operations will directly reference a > DXCC database, either DXView's (if installed) or DXKeeper's. DXView > itself will not participate in import operations, which should speed > things up quite a bit. > > For callsign lookups during interactive operations (such as logging a > QSO), DXKeeper will attempt the callsign lookup via DXView if its > running; in performing this lookup, DXView updates its information > display. If DXView is not running, then DXKeeper will perform the > lookup using its copy of the database. > > So import operations run fast and don't depend on (or overload) > DXView, interactive operations use DXView if its running, but in no > case will DXKeeper create a QSO that's missing DXCC prefix or country > code information. > > There's more complexity here than I'd like, but most of it is hidden > from the user. If you've installed DXView, then you can use it to > maintain your DXCC database and DXKeeper will automatically be > consistent. If you aren't using DXView, then DXKeeper has its own > DXCC database (though you lack a tool to update it, and thus have to > download updates from DXKeeper web site). > > Comments? > > The above approach is implemented (in DXView 1.1.5) and appears to > work, but I'd like to test a few more cases before posting it. > > 73, > > Dave, AA6YQ > > --- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote: > > Sounds like there's a latent defect in the DDE connection between > DXKeeper > > and DXLab. I suggest you hold off until I release a version of of > DXKeeper > > that performs the country code lookup without consulting DXView. > Shouldn't > > take too long... > > > > 73, > > > > Dave, AA6YQ > > -----Original Message----- > > From: Richard B Drake [mailto:rich@w...] > > Sent: Wednesday, March 21, 2001 17:50 PM > > To: dxlab@y... > > Subject: RE: [dxlab] Re: Progress window > > > > > > > > > > Does this explain the large variance in confirmed countries you > > > mentioned earlier? > > > > > > > I don't know, but I am having a great deal of difficulty with the > > import. I took out all the DXCC entries in the ADIF file to force > > a lookup in DXView. It starts off going OK, pretty slow but I can > > live with that. Then it suddenly seems to lose communication with > > DXView and starts flying along without putting in a DXCC prefix. > > The first time I tried it, it only put in about 10 prefixes before > > that happened. I tried again and this time it got to about 400 > > before it lost the connection. In any case it will not handle my > > 5000 entry log in one go. It gets up to QSO# 3762 and dies. I can > > handle that by doing it in two pieces but I don't know what to do > > about the loss of communication with DXView. > > > > ---- > > 73, Rich - W3ZJ > > > > > > Yahoo! Groups Sponsor > > > > iWin.com - The Place to Win Stuff! > > > > > > To unsubscribe from this group, send an email to: > > dxlab-unsubscribe@y... > > > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of > Service. > > > > > > > >

DXKeeper 1.1.6 corrects a defect that prevents addition of the first QSO to a log via the Capture Window. This release also includes further improvements to the online help. If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.6 by downloading and then running www.qsl.net/dxkeeper/DXKeeper116Update.exe -- your online help will automatically be update by this process. If a previous version of DXKeeper is not already installed on your PC, you can obtain this release via http://www.qsl.net/dxkeeper/download.htm . 73, Dave, AA6YQ

This release - corrects a defect that prevented the import operation from properly crediting QSOs that were worked but not confirmed - corrects a defect that caused PSK QSOs to not be included in Mixed results - can generate a detailed progress report (click the "Report" button on the Progress tab) - when the "Import from Logger" box is checked, relocates the second and subsequent words of the incoming Name field to the Notes field. If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.7 by downloading and then running www.qsl.net/dxkeeper/DXKeeper117Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ

Closing DXKeeper while it is minimized on the task bar by right clicking on the task bar icon and selecting close, produces the following error: "Run-time error '384' A form can't be moved or sized while minimized or maximized" ----- 73, Rich - W3ZJ www.w3zj.com

It would be nice after clicking "clear" in the capture window if the keyboard focus would go to the callsign entry window as it does after clicking "log". I often find myself trying to type a new callsign into the clear button :-) ----- 73, Rich - W3ZJ www.w3zj.com

This release - corrects a defect that produced a crash if you tried to close DXKeeper while it was iconified - in the QSO Capture window, clearing all fields leaves the text entry cursor in the callsign field If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.8 by downloading and then running www.qsl.net/dxkeeper/DXKeeper118Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ

Thanks to Fred K3ZO, Pathfinder can now search the online Indonesian callbook. Access to this site can be a little slow, as requests and results must traverse the Amateur Packet Radio (AMPR) Network, making response time dependent on channel utilization and the load at the AMPRNet-Internet gateway. To update your search library, click Pathfinder's "Info" button, or link to http://www.qsl.net/pathfinder/UpdateSearchLibrary.htm. The Pathfinder Web Client ( http://www.qsl.net/pathfinder/WebClient/ ) has been updated with the above addition; the only action required of its users is to click their Browser's "refresh" button. As always, reports of new online QSL sources or changes to existing sources are greatly appreciated. 73, Dave, AA6YQ Pathfinder is a free program that makes it easy to find QSL information from more than 100 web-accessible sources. See http://www.qsl.net/pathfinder/ for additional information and download instructions. Or use the Pathfinder Web Client -- its a little less flexible, but requires no downloading or installation and runs in any Javascript-supporting browser on Windows, MacOS, Linux, or Unix; just visit http://www.qsl.net/pathfinder/WebClient/ .

I have just downloaded and installed Pathfinder 3.0 But when I enter a call sign and press one of the buttons, I just get a page which says "You are not authorised to view this page" What have I missed? Robin gw3zcf

In this release, I modified the internal representation of latitudes and longitudes to correct a defect that caused the incorrect display of positions between 0 South and 0 1' North, or between 0 East and 0 1' West ; I doubt anyone would have ever noticed, but my 11th grade trig teacher would kill me if she ever discovered this error. While I believe that my testing covered all the combinations, it was a deep change -- so I'd appreciate it if someone who likes breaking things would take a shot at this version. I also completed the transition to direct latitude and longitude entry, converting the QTH position text boxes on the Configuration screen to accept things like 42 15' N rather than 42.25 with a check in the "North" box. When you first run this version, please verify that your QTH location is still correct. The online help has also been updated. This release is available by downloading http://www.qsl.net/dxview/DXView126Update.exe - store it in your DXView folder and execute it. You can then run the extracted DXView126.exe . 73, Dave, AA6YQ

Today, I was dismayed to see that DXView's title bar was displaying a UTC time that was off by one hour. I fired up WinWarbler, and the UTC time in its title bar was correct. DXView, WinWarbler, and most other DXLab applications use common code for this function -- how could the two programs report different times using the same code? I terminated DXView and restarted it -- the time shown in its title bar was now correct. These programs report time by checking the system clock every second using a Windows API that supposedly handles daylight savings time transitions. Evidently running programs don't make the time transition properly -- you must shut them down and restart them. I will investigate further -- perhaps there's something I can do to make this completely automatic, as originally intended. 73, Dave, AA6YQ

PropView uses the included IonCap propagation prediction engine to forecast the minimum and maximum useable frequencies between two locations over a specified 24 hour period. Results are rendered in an easy-to-understand color-graphic display. You can specify locations via direct latitude/longitude entry. Alternatively, PropView interoperates with DXView to allow location selection via DXCC prefix entry or by clicking on locations on a world map. A sample screen shot, online help, and download instructions are available via www.qsl.net/propview . Critique and suggestions would be appreciated. 73, Dave, AA6YQ

After generating a prediction for propagation between two locations, check "Show Critical Frequencies" and uncheck "Show Open Bands". The black curve represents the lowest useable frequency (LUF) as a function of time. Any frequency lower than the black curve will not support communications due to absorption. The blue, green, and red curves provide a statistical range for the maximum useable frequency (MUF) as a function of time. The actual MUF will be at or above the blue curve with 90% confidence, at or above the green curve with 50% confidence, and at or above the red curve with 10% confidence. Any frequency above the actual MUF will not support communications, due to insufficient reflection. So at any specified time, you can identify which frequencies will likely support communication between the specified locations: they are bounded on the low-end by the black curve, and on the high-end by the statistical range between the blue and red curves. You can use the green curve as a kind of "expected MUF" curve; being an optimist, I tend to use the red curve for this purpose. To make it easier to see what ham bands are open when, uncheck the "Show Critical Frequencies" box and check "Show Open Bands". Horizontal lines represent ham bands lying between the LUF and statistical MUF. The thickist lines indicates openings based on the 90% confidence MUF (the blue curve), and the thinnest lines indicate openings based on the 10% confidence MUF (the red curve). If you now check "Show Critical Frequencies", the relationship between horizontal lines and critical frequency curves should be apparent. Suggested corrections, improvements, and/or clarifications to the above would be appreciated; I'll incorporate the result into the online help. 73, Dave, AA6YQ --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote: > Ron, > > I have now also installed PropView and I am afraid I can not > reproduce any of your symptoms. It seems to be working fine though > I am still trying to learn how to interpret the graphs. If I were > you, I would first try simply rebooting, that often cures all > kinds of unknown problems. If that fails to help, try > re-installing PropView. What operating system are you running and > what is your machine, speed/memory etc.? > > 73, Rich - W3ZJ > > > -----Original Message----- > > From: Ron Eberson [mailto:zx@c...] > > Sent: Tuesday, April 03, 2001 11:59 AM > > To: dxlab@y... > > Subject: [dxlab] PropView 1.0.1 > > > > > > > > > > Helo all. > > > > I have install the 1.01 version of PropView. > > > > I have the next problem. > > > > 1. When i click the Predict button the next mesagge > > show: Error 13 Run > > time error. > > 2. If i click the help button i have a screen for > > DOS and and must put a > > filename????? > > 3. I have also if i click the Config button the > > same error 13 > > 4. I can not save my Antenna degrees and my output > > power. > > 5. The DXView give the long and lat super on DXProp. > > > > Who can help me. > > > > Ron > > > > > > ------------------------ Yahoo! Groups Sponsor > > > > To unsubscribe from this group, send an email to: > > dxlab-unsubscribe@y... > > > > > > > > Your use of Yahoo! Groups is subject to > > http://docs.yahoo.com/info/terms/ > > > > > >