[DXBase] DXBase 2005 LOTW, Orion rig control, VUCC award tracking, Propagation mode & spot filtering

2004年5月01日 11:18:22 -0500

Bill,
With regards to the LoTW -- if you DO NOT CHECKMARK the
"Include QSL detail: " -- then NONE of the Extra Details
will be in your adi file download (like CQZ, ITUZ, GRIDSQUARE,
and IOTA)...
73 Joe wa6axe
William H. Hein wrote:
> I have discovered two issues with DXB 2005, which I installed yesterday:
>> LOTW IMPORT OVERWRITING GOOD DATA WITH BAD: I am concerned that the way DXB
> 2005 processes imported LOTW data may overwrite accurate data with incorrect
> data. The DXB help file states that DXB will update IOTA, State, County, CQ
> zone and ITU zone from the imported LOTW data. There is a substantial
> amount of inaccurate information in the LOTW database, especially zone data.
> Lots of people don't know the difference between ITU and CQ zones and have
> recorded their LOTW zone data (especially ITU) incorrectly. LOTW database
> does not verify zone data (not sure about grid loc/state and other potential
> data errors).
>> I am also concerned about the SSB/LSB & USB point raised earlier on this
> reflector. I don't want the LOTW import creating duplicate QSOs in my DXB
> logbook because a LOTW SSB QSO doesn't match a DXB USB or LSB QSO.
>> Ideally, users should be able to accept or reject each data field that the
> LOTW import process wants to change (with the exception of the LOTW
> confirmed data) to keep their logbook data accurate. This is the way
> DXKeeper (from the DX Lab suite) works and is an approach worth copying
> IMHO.
>> ORION RIG CONTROL: When I set the frequency of my Ten-Tec Orion my clicking
> the QSY field on a cluster spot in the DX Info window, DXB resets the rig's
> SSB bandwidth to 3000Hz and the CW bandwidth to 100Hz (depending on the mode
> of the spot). I prefer that DXB not change my rig's mode bandwidth from the
> last BW used in any particular mode, or at least let me preset more useful
> values.
>> Also, when selecting a CW spot in this manner, DXB puts the Orion into UCW
> mode (Upper sideband CW). UCW causes the beat tone to decrease in frequency
> when tuning the VFO from a lower to higher frequency. This is
> counter-intuitive and the opposite of the way most ham transceivers are set
> up. I prefer that DXB put the Orion into LCW (Lower sideband CW) mode when
> I select a CW spot.
>> VUCC AWARD TRACKING: I have lived at 5 different QTHs during my amateur
> radio career. All of these QTHs are within the same DXCC entity, so no
> problems there. However, per VUCC rules, I cannot mix my Southern
> California, Colorado and Vermont QSOs for the awards. DXB includes QSOs
> from all my QTHs when calculating VUCC status yielding inflated figures.
> Any ideas on how to parse out correct data? Separate logbooks for each QTH
> is not a solution as that would screw up my DXCC and WAZ data.
>> PROPAGATION MODE: I thought the ADIF 1.0 field PROP_MODE was going to be
> supported in DXB 2005? In particular, I would like to track the propagation
> mode of my 10,000+ 6m QSOs (ES, F2, TEP, AUR, FAI, et al).
>> SPOT FILTERING: Is there a way to filter out 2m & up spots? On days like
> today, the DX Info window is full of EU 2m and up spots which are of no
> interest to me. I have set up the DX Spot Alerts to not alert me to any 2m
> or 4m spots, however this does not stop all the EU 2m and up stuff from
> being displayed.
>> 73,
> Bill NT1Y (ex-AA6TT)
>>> _______________________________________________
> DXBase Reflector - Please visit us on the web at www.dxbase.com
> - - - - - - - - - - - - - - - - - - - - - - - 
> To UNSUBSCRIBE please visit:
> http://mailman.qth.net/mailman/listinfo/dxbase
>