DXbase expects VFOa to be your rx and if split VFOb to be the xt. If non split, VFOa controls both. If you don't want to operate this way to be compatible with the design of the software, then you'll need to turn off the radio interface. If the makers of radios ever adopt some kind of a standard, maybe these kinds of issues could be reasonably addressed. But until then, this is the standard that we use to be compatible with most radios.
Regards, Jack ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[email protected]> Sent: Saturday, May 14, 2005 1:03 PM Subject: [Dxbase] Icom (et al) VFO/frequency polling logic >I really wish Dxbase would not switch my radio to VFO A before reading the > frequency I am on when making a QSO. It is very irritating when it > suddenly > changes frequency, band, mode, etc., then enters the WRONG information in > the logging screen, meanwhile, the station with whom I am in QSO suddenly > disappears ... > > It seems to me that it would be quite easy to just poll the radio for the > current frequency and mode and be done with it. > > This would make the radio interface concept *more* accurate, which, along > with convenience and speed, is probably its intent. However, it is > actually > *less* accurate than not having a radio interface at all - at lease I know > the information I enter is correct if I have to enter it manually ... I > obviously cannot rely on the radio interface to do it accurately if Dxbase > insists on reading the information from a particular location (VFO A) > reguardless of where I happen to be operating at the time. > > The 2006 upgrade was flawless and the Dxbase 2006 Utility (particular the > Column Order component) is a sustantial improvement. > > 73, > Don Chisholm > > > > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] >
