Date   

WinWarbler and IC7851 configuration setup

Norm_W4QN
 

This is addressed to those DXLAB / WinWarbler users with the IC7851 radio. 
I am looking for the radio setup to interface with the PC running WinWarbler for the SSB, Digital (RTTY), and CW.  modes.  My setup does 
now interface with the other radio control modules e.g. Commander, and I want to add WinWarbler as well.  I know there is a pretty comprehensive description in Dave's Help-User guide, but so far the resuts have not been satisfactory.  There are the WinWarbler Configuration elements, and the necessary 7851 settings that I am looking for.

I think there may be many similarities with other ICOM radios with the built-in sound cards, e,g, 7300 and 7610 models that could apply

Hopefully there are some users of both WW and 7851 that can offer some guidance.  To avoid unnecessary bandwidth I can be contacted directly via email - my call at bellsouth dot net,

Norm W4QN


Re: How to import only LOTW QSO's that are NOT in DXK?

bob-w9zv
 

On Thu, Oct 14, 2021 at 09:36 AM, g4wjs wrote:
uestion back to you is how did you manage to upload QSOs to LoTW that are not in your existing DXKeeper log? The answer to that should also find you a source for the missing QSO records.
long story bill.. various logs being imported over time into LOTW from other sources which may not now be available is only one...   really doesnt matter why, i'd simply like to "push" them into the DXK log at this point and try to get to a point where they are synced.


Re: How to import only LOTW QSO's that are NOT in DXK?

g4wjs
 

On 14/10/2021 15:33, bob-w9zv wrote:

trying to sync up LOTW and DXK log, and when i do get lots of QSO's that ARE in LOTW log but NOT in the DXK logs.
i get many "no matching QSO in log" in the LotW_QSOs_ADI_error.txt file.

how do do an import of all QSO's that are absent in the DXK log but present in the LOTW log?
Hi Bob,

I think the first question back to you is how did you manage to upload QSOs to LoTW that are not in your existing DXKeeper log? The answer to that should also find you a source for the missing QSO records.



--
73

Bill

G4WJS.


How to import only LOTW QSO's that are NOT in DXK?

bob-w9zv
 


trying to sync up LOTW and DXK log, and when i do get lots of QSO's that ARE in LOTW log but NOT in the DXK logs.
i get many "no matching QSO in log" in the LotW_QSOs_ADI_error.txt file. 

how do do an import of all QSO's that are absent in the DXK log but present in the LOTW log? 


Re: Commander UDP packet issue

w6de
 

Greg, wrong Dave.  Maybe you intended Dave, AA6YQ.

 

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Gregg W6IZT via groups.io
Sent: Wednesday, October 13, 2021 22:36
To: DXLab@groups.io
Cc: 'Larry Gauthier (K8UT)'
Subject: [DXLab] Commander UDP packet issue

 

Greetings Dave:

 

I hope that all is well. I use the UDP broadcasts from Commander with K8UTs FreqEZ application to control antenna switching. Generally the two apps work well together. I have discovered that at times the  xml  values sent by commander appear to not update properly. I set up a listener in Node Red to look at the xml data.  Before this capture I had changed bands from 17m to 160m. Both od the VFOs were set to 1.840 MHz. Here is a capture of the xml file. As you can see the VFO B frequency is indicating 18.000 MHz.

 

<?xml version="1.0" encoding="utf-8"?>

<RadioInfo>

<app>DXLab</app>

<RadioNr>1</RadioNr>

<Freq>184000</Freq>

<TXFreq>1810000</TXFreq>

<Mode>Data-U</Mode>

<IsSplit>False</IsSplit>

</RadioInfo>

 

Restarting Commander resolves what appears to be an issue. I was going to attach the error log but it is 95 Mbs. I can put it in Google Drive or DropBox, whichever you prefer.

 

Thanks for all that you do.

 

73

Gregg W6IZT

 

 


Re: WSJT-X interaction issues with Spot Collector, DXView, Pathfinder, DXKeeper

HB
 

Dave...
You've got mail!

Thanks,
Hank
K4HYJ


Re: Commander UDP packet issue

Dave AA6YQ
 

+ AA6YQ comments below

I hope that all is well. I use the UDP broadcasts from Commander with K8UTs FreqEZ application to control antenna switching. Generally the two apps work well together. I have discovered that at times the xml values sent by commander appear to not update properly. I set up a listener in Node Red to look at the xml data. Before this capture I had changed bands from 17m to 160m. Both od the VFOs were set to 1.840 MHz. Here is a capture of the xml file. As you can see the VFO B frequency is indicating 18.000 MHz.

<?xml version="1.0" encoding="utf-8"?>

<RadioInfo>

<app>DXLab</app>

<RadioNr>1</RadioNr>

<Freq>184000</Freq>

<TXFreq>1810000</TXFreq>

<Mode>Data-U</Mode>

<IsSplit>False</IsSplit>

</RadioInfo>


+ So that I can see what's going on, please do the following

1. On the Configuration window's General tab, check the "log debugging info" box

2. Terminate Commander

3. Using its front panel, set both of the radio's VFOs to 18,100 with Split disabled

4. Delete the errorlog.txt file in your Commander folder

5. Start Commander, and wait for it to fully initialize

6. QSY to 1,840 without enabling Split

7. Wait for Commander's Main window to display the new frequency

8. On the Configuration window's General tab, uncheck the "log debugging info" box

9. attach the errorlog.txt file from your Commander folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ



Thanks for all that you do.



73

Gregg W6IZT






<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Commander UDP packet issue

Gregg W6IZT
 

Greetings Dave:

 

I hope that all is well. I use the UDP broadcasts from Commander with K8UTs FreqEZ application to control antenna switching. Generally the two apps work well together. I have discovered that at times the  xml  values sent by commander appear to not update properly. I set up a listener in Node Red to look at the xml data.  Before this capture I had changed bands from 17m to 160m. Both od the VFOs were set to 1.840 MHz. Here is a capture of the xml file. As you can see the VFO B frequency is indicating 18.000 MHz.

 

<?xml version="1.0" encoding="utf-8"?>

<RadioInfo>

<app>DXLab</app>

<RadioNr>1</RadioNr>

<Freq>184000</Freq>

<TXFreq>1810000</TXFreq>

<Mode>Data-U</Mode>

<IsSplit>False</IsSplit>

</RadioInfo>

 

Restarting Commander resolves what appears to be an issue. I was going to attach the error log but it is 95 Mbs. I can put it in Google Drive or DropBox, whichever you prefer.

 

Thanks for all that you do.

 

73

Gregg W6IZT

 

 


Re: Broken RBN Spots

Pete Smith
 

Hi Pete - these probably arise mostly through erratic sending, QRM  or propagation conditions blurring the existence of the space between, for example,  "CWT" and "N3JT".  CW Skimmer then looks at what it has copied and thinks "that could be a legitimate call."  I see these very frequently in CWTs. Not much you can do unless SpotCollector has or can add a blacklisting function.  In theory, RBN node operators can blacklist calls in their Aggregator software, but we do not attempt to do that for them from the RBN server.

73, Pete N4ZR
Check out the new Reverse Beacon Network
web server at <http://beta.reversebeacon.net>.
For spots, please use your favorite 
"retail" DX cluster.
On 10/13/2021 4:54 PM, Pete W1RM wrote:

I have spot collector set to show unworked entities for the marathon.  I am getting a ton of bad/broken spots.  Spots like TN3JT and TN2IC just as examples.  I don’t know if these bad spots are coming from one source (node) or are being propagated all over the place.

 

I do know some of the sources are what I’ll call reliable sources, like K1TTT and KM3T.

 

Other than just ignore them, what to do?

 

Pete Chamalian, W1RM

W1RM@...

 

 


Re: Broken RBN Spots

Dave AA6YQ
 

+ AA6YQ comments below

I have spot collector set to show unworked entities for the marathon. I am getting a ton of bad/broken spots. Spots like TN3JT and
TN2IC just as examples. I don't know if these bad spots are coming from one source (node) or are being propagated all over the
place.

I do know some of the sources are what I'll call reliable sources, like K1TTT and KM3T.

Other than just ignore them, what to do?

+ Add them to SpotCollector's "Special Callsigns" list with no tags; they will then be ignored.

73,

Dave, AA6YQ


Broken RBN Spots

Pete W1RM
 

I have spot collector set to show unworked entities for the marathon.  I am getting a ton of bad/broken spots.  Spots like TN3JT and TN2IC just as examples.  I don’t know if these bad spots are coming from one source (node) or are being propagated all over the place.

 

I do know some of the sources are what I’ll call reliable sources, like K1TTT and KM3T.

 

Other than just ignore them, what to do?

 

Pete Chamalian, W1RM

W1RM@...

 

 


Re: Trouble creating anSWL in DXKeeper

Robert T
 

TU Dave... got it !

RET

<pre>1</pre>

On 10/13/2021 11:39 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:


+ AA6YQ comments below

Having trouble getting DXK to give me the SWL option after I search a call. I right click on the call which opens a menu but the option to create an SWL is not there. There's a whole list of options ie: QSY to freq, Spot call, delete from Clublog etc.

+ On the Main window's QSL tab, set the "QSL Via" panel to "QSL cards", "Single labels", "2-column labels", or "3-column labels".

+ Now when you right-click the Log Page Display entry on the Main window's "Log QSOs" tab, an "Add SWL entry to QSL Queue" option will be present.

73,

Dave, AA6YQ





Re: Trouble creating anSWL in DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

Having trouble getting DXK to give me the SWL option after I search a call. I right click on the call which opens a menu but the option to create an SWL is not there. There's a whole list of options ie: QSY to freq, Spot call, delete from Clublog etc.

+ On the Main window's QSL tab, set the "QSL Via" panel to "QSL cards", "Single labels", "2-column labels", or "3-column labels".

+ Now when you right-click the Log Page Display entry on the Main window's "Log QSOs" tab, an "Add SWL entry to QSL Queue" option will be present.

73,

Dave, AA6YQ


Trouble creating anSWL in DXKeeper

Robert T
 

Having trouble getting DXK to give me the SWL option after I search a call.  I right click on the call which opens a menu but the option to create an SWL is not there.  There's a whole list of options ie: QSY to freq, Spot call, delete from Clublog etc.
 
I've created SWLs before but something isn't going right this time around.
 
Any ideas?
 
Bob, K2RET


Re: K3s second VFO RTTY

Peter Dougherty
 

I'd been using OneNote for many years to document everything, but after I got rid of my auto-tuner and my MicroKeyer, and simplified the rest of my station (pre-FT8) I let it all kinda fall by the wayside, and since I've really lost the hamming bug for the most part it just stopped appearing on my radar. So I'd make a change, kept it running and left it alone...Other than sound cards it's kinda-sorta worked, but every so often Windows breaks things and I have to re-set all my sound cards. At the moment I don't have the hours necessary to do any of this, but I'll try to make some time in December or January when work slows down, and hope nothing goes bad until then!


Re: K3s second VFO RTTY

w6de
 

The easy (?, but accurate) way to document computer settings displayed on your computer monitor, is to use the “Print Screen” function of Windows.  Print Screen will capture the entire monitor screen and place it on the clip board.  However, Alt + Print Screen will capture the last active window on the monitor and place that smaller window image on the clip board.  See these instructions:

https://www.wikihow.com/Use-the-%22Print-Screen%22-Function-on-a-Keyboard

or

https://www.dell.com/support/kbdoc/en-us/000147539/how-to-use-the-print-screen-key-in-microsoft-windows-operating-systems

The Dell explanation is a bit more concise and includes instruction for earlier Windows versions..

 

After capturing each sound card setting in this manner, you can paste the image in a document; also explained in the above links.  Repeat the process for each sound setting window.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ via groups.io
Sent: Tuesday, October 12, 2021 18:23
To: DXLab@groups.io
Subject: Re: [DXLab] K3s second VFO RTTY

 

+ AA6YQ comments below

So it looked like it was just a simple matter of enable two-channel receive in the appropriate sound card setting. Windows 10 seems to love resetting sound settings at major updates, and  that's what fixed it (well, kinda-sorta fixed it).

+ Document all of your sound settings; then you can easily check/restore them after a Windows 10 update.

But this brings up two questions. One, how will setting this to 2-ch affect JT-modes operation (if at all)

+ There should be no impact, but give WSJT-X a try to be certain.

, and second, levels seem to be a bit of an issue for the second VFO now; I'm only hearing the strongest signals. I'm a bit hesitant to mess with them, again, fearing screwing up WSJT.

+ I've not heard of anyone being unable to find soundcard levels that work for all digital modes.

I go months with the radio off these days due to work commitments, only doing an hour or two in a DX or 160 contest, and some 6m FT8 in June and July when the band is hopping. I just don't have the cycles between my ears to remember all these arcane settings any more.

+ Take a few minutes to document your settings! Doing so will save you hours down the road...

        73,

               Dave, AA6YQ


Re: K3s second VFO RTTY

Dave AA6YQ
 

+ AA6YQ comments below
So it looked like it was just a simple matter of enable two-channel receive in the appropriate sound card setting. Windows 10 seems to love resetting sound settings at major updates, and  that's what fixed it (well, kinda-sorta fixed it).
+ Document all of your sound settings; then you can easily check/restore them after a Windows 10 update.

But this brings up two questions. One, how will setting this to 2-ch affect JT-modes operation (if at all)
+ There should be no impact, but give WSJT-X a try to be certain.

, and second, levels seem to be a bit of an issue for the second VFO now; I'm only hearing the strongest signals. I'm a bit hesitant to mess with them, again, fearing screwing up WSJT.
+ I've not heard of anyone being unable to find soundcard levels that work for all digital modes.
I go months with the radio off these days due to work commitments, only doing an hour or two in a DX or 160 contest, and some 6m FT8 in June and July when the band is hopping. I just don't have the cycles between my ears to remember all these arcane settings any more.
+ Take a few minutes to document your settings! Doing so will save you hours down the road...

        73,

               Dave, AA6YQ


Re: K3s second VFO RTTY

Peter Dougherty
 

So it looked like it was just a simple matter of enable two-channel receive in the appropriate sound card setting. Windows 10 seems to love resetting sound settings at major updates, and  that's what fixed it (well, kinda-sorta fixed it).But this brings up two questions. One, how will setting this to 2-ch affect JT-modes operation (if at all), and second, levels seem to be a bit of an issue for the second VFO now; I'm only hearing the strongest signals. I'm a bit hesitant to mess with them, again, fearing screwing up WSJT.

I go months with the radio off these days due to work commitments, only doing an hour or two in a DX or 160 contest, and some 6m FT8 in June and July when the band is hopping. I just don't have the cycles between my ears to remember all these arcane settings any more. I would dearly love to have some kind of set-it-once and save it forever process, but Windows breaks things regularly. But that said, it's nice to dabble into RTTY again every so often. The hamshack PC is my only system now that my wife has moved into my office for remote-work-from-home, and I have to use it as my work PC for the 50-70 hour work weeks I'm putting in.


Re: DXK/DXV - user specified digital mode family

Wolf, DK1FW
 

Thanks for the explanation Dave.

I was not aware of the comlications to add RTTY.
I will sit back patiently.

73 de Wolf, DK1FW

Am 12.10.2021 um 14:42 schrieb Dave AA6YQ:

+ AA6YQ comments below

DXKeeper and DXView allow to set/view a user-specified digital mode
family to support personal objectives beyond DIGITAL progress for DXCC.
While the list, from which this can be chosen, includes some pretty
exotic modes it does not include RTTY.

Many of us have chased RTTY DXCC for decades before ARRL changed it to
DIGITAL thus down-grading the more difficult RTTY DXCC to a personal
objective.
Old RTTY-ers like myself still aim at DXCC HR level in RTTY only and on
multiple bands in addition to the ease of attaining those DIGITAL goals
by using FT8.

Having RTTY worked status at a glance in DXV is quite different from
generating a progress report.

So I wonder if you could add RTTY to the list of user-specified digital
modes. The user-base of RTTY is probably still bigger than that of
OLIVIA and THROB.

+ I didn’t include RTTY in the initial implementation of "user-specified digital mode" because it's quite a bit more complicated to implement, and would have considerably delayed that initial implementation. It's still "on the list" - but not imminent.

73,

Dave, AA6YQ






Re: WSJT-X interaction issues with Spot Collector, DXView, Pathfinder, DXKeeper

HB
 

Thanks Dave...
I have been traveling for work - I'll be back home tomorrow and do as you ask.

Stay tuned!

Hank
K4HYJ

4201 - 4220 of 208020