开云体育

Mike, I see 100 spots by K9IMM in the last 4 hours, all of which look reasonable to me.? Are you still seeing the bad ones, and where? 73, Pete N4ZR

+ AA6YQ comments below + The name of that checkbox is "Enable on newly-needed Entry", and its the explanatory popup displays "when checked, Autoscroll will automatically be enabled when a new Spot

Sorry, Dave - with some clarity :) The tick box is the one on the Spot Database Display Config Tab: Auto-scroll - Enable on newly acquired Entry - this is ticked. Action: Double-click on entry in

+ AA6YQ comments below + Add K9IMM to SpotCollector's Special Callsign List with a BadSource tag: https://www.dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm 73, Dave, AA6YQ

The RBN or skimmer station k9imm-# is spotting all decodes regardless of band to 6m.? Is there a way to filter this station out as a bad spotter?? Many of the FT mode skimmers are horrible.

+ AA6YQ comments below + Before you log the QSO from the Capture window, depress the CTRL key while clicking the Spot button to generate a local spot; locally-spotted callsigns appear in Commander's

Is it possible to have the contact that's been logged in DXKeeper Capture to show in the DXCommander Bandspread listings like the active DX stations from SpotCollector? Perhaps there's something in

In additions to Joe’s guidance, in WSJTX, Settings, Reporting tab, Logging panel, is “Prompt me to log QSO” checked? 73, Dave, w6de Sent: 27 February, 2025 17:39 To: [email protected] Subject:

+ AA6YQ comments below + The tradeoff is the time - and frustration - saved for many users by preventing errors that would be made if those prompts and warnings weren't present - and the time I can

I'm aware that one can have DXK prepare a "discrepancy report" and go back to resolve the issue. That's not what I want ... I want to be prompted for each discrepancy and resolve it on the fly as

Information on integrating WSJTX with DXLab Suite is here: <http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes> There are two versions ... one "Direct" using

Not too long ago I switched to the new release (2.7.0) of WSJT for FT8. For some reason now, the logged contact for WSJTis not getting relayed and captured by DXK.? The contacts are logged in the

#more AA6YQ comments below # if you set the "Handling of LoTW QSL inconsistency" panel to "Preserve log data, ignore LoTW data, and report inconsistencies when operation ends", no changes will be

It may for someone who is not paying attention. On the other hand, If I make a change to a filtered sub set of the log that is wrong, I can always filter the log again and reverse the change. But

+ AA6YQ comments below All of "the log page display is filtered" prompts + Those prevent a log of errors, some of which have consequences that would be time-consuming to repair. The LotW Sync

Perhaps I’m working FT8 looking for needed calls. JTAlert gives me this info. I may not want to QSY to another frequency/band depending on the “need” for the spotted station. If the spot is

In SpotCollector you can set up the "Need" filter to do exactly that. Set your spot collector display window to show reason for the need [e.g., show columns for need, band, mode, zone, iota, & etc

On Wed, Feb 26, 2025 at 04:29 PM, Dave w6de wrote: > > > > I believe that highlight would be a persisting distraction. I use the band > view in DXView to check my entire band and mode status for

Perhaps I’m working FT8 looking for needed calls. JTAlert gives me this info. I may not want to QSY to another frequency/band depending on the “need” for the spotted station. If the spot is

Understand, but I don’t want to QSY until I see the data shown in the DXView Progress Window and then decide if I want to change bands/modes. + What's the problem with QSYing before you know it's