Date   

Re: DX Keeper and upload to LotW

Gilbert Baron W0MN
 

Is all LoTW processing first cone first served or do small uploads get any priority?

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, March 20, 2021 18:43
To: DXLab@groups.io
Subject: Re: [DXLab] DX Keeper and upload to LotW

 

+ AA6YQ comment below

I have now confirmed that uploading my QSOs to LoTW now works! I am a very happy camper. There is a very slight delay but nothing serious.

+ QSOs submitted to LoTW are placed in a queue that is processed in arrival order by the LoTW Server. The ARRL maintains a web page that shows the expected processing delay at the beginning of the most recent hour, and at the beginning of the 11 preceding hours:

http://www.arrl.org/logbook-queue-status

+ On the QSL tab of DXKeeper's Main window with the "QSL Via" panel set to LoTW, clicking the "Check LoTW Queue" button will display the expected processing delay as of the beginning of the most recent hour.

+ Generally, this delay is about 1 minute, but it can increase substantially when a log containing hundreds of thousands of QSOs is submitted to LoTW. Immediately after a contest, the expected processing delay is often denominated in hours.

     73,

           Dave, AA6YQ


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


N4PY Icom software, IC-7610 and Commander problem

Floyd Sense
 

I have a new IC-7610 and at first had Commander directly connected to the rig via USB.  I have WSJT-X configured with Commander as the rig, exchanging information via UDP.  That all worked great.  The next step was to implement the N4PY Icom software to gain support for the Elad TM-2 controller.  I was unable to get N4PY and Commander talking to each other using a N4PY external port via a virtual cable to Commander.  N4PY then suggested that I just use the old file transfer technique and so I set that up and indeed it worked well.  But, next time I fired up WSJT-X, I found it was unable to communicate with Commander.  When doing the CAT test, I got a green result but when I hit the PTT test button in WSJT-X, I got an error message saying Commander didn't respond to the command to set PTT on.  Tried several times, restarting everything, but same result.  Is it possible to use the UDP path while also using the old file transfer technique?

73, Floyd - K8AC


Re: DX Keeper and upload to LotW

Dave AA6YQ
 

+ AA6YQ comment below
I have now confirmed that uploading my QSOs to LoTW now works! I am a very happy camper. There is a very slight delay but nothing serious.

+ QSOs submitted to LoTW are placed in a queue that is processed in arrival order by the LoTW Server. The ARRL maintains a web page that shows the expected processing delay at the beginning of the most recent hour, and at the beginning of the 11 preceding hours:

http://www.arrl.org/logbook-queue-status

+ On the QSL tab of DXKeeper's Main window with the "QSL Via" panel set to LoTW, clicking the "Check LoTW Queue" button will display the expected processing delay as of the beginning of the most recent hour.

+ Generally, this delay is about 1 minute, but it can increase substantially when a log containing hundreds of thousands of QSOs is submitted to LoTW. Immediately after a contest, the expected processing delay is often denominated in hours.

     73,

           Dave, AA6YQ


Re: Getting Winwarbler to work with IC-7610 in RTTY FSK mode

Dave AA6YQ
 

+ AA6YQ comments below

And the answer is: I should have set up USB B in the 7610 menu instead of USB A. The answer was in a contest university presentation seen here:
https://www.kkn.net/~n6tv/N6TV_Dayton_2019_Everything_USB.pdf

+ The source of the Icom virtual USB Port information in that document is Icom's " Tips for the USB port settings" document, available via

https://www.icomjapan.com/support/manual/2574/

+ This document is cited in Note 2.c in "the FSK connection" in

https://www.dxlabsuite.com/dxlabwiki/FSKConnection

73,

Dave, AA6YQ


Re: WinWarbler SSB macro not working

Dave AA6YQ
 

+ AA6YQ comments below

It is perfectly reproduced through VLC player and through the audio of the PC

+ Good. What soundcard is the VLC player configured to use? Temporarily configure WinWarbler to use the same soundcard for phone transmission. What happens when you active a phone macro in WinWarbler?

73,

Dave, AA6YQ


Re: DX Keeper and upload to LotW

Serge Bertuzzo
 

Hi Dave. T
I have now confirmed that uploading my QSOs to LoTW now works! I am a very happy camper. There is a very slight delay but nothing serious. 

Have a great day and thank you once again for your ongoing support and assistance.

73

Serge
VA3SB


Re: WinWarbler SSB macro not working

Carlo - IK2RPE
 

It is perfectly reproduced through VLC player and through the audio of the PC


Carlo IK2RPE



-----Messaggio originale-----
Da: DXLab@groups.io <DXLab@groups.io> Per conto di Dave AA6YQ
Inviato: sabato 20 marzo 2021 19:51
A: DXLab@groups.io
Oggetto: Re: [DXLab] WinWarbler SSB macro not working

+ AA6YQ comments below

I have the problem that when I activate the SSB macro in WinWarbler it does no longer work (transmit) and a window appears saying:

“attempt to play C:\DXLab\WinWarble\Phone\msag2.wav on soundcard2 failed: (282) and (translated from Italian) the specified parameter is outside from the allowed interval of the specified command”

My working conditions are WIN10Pro, Icom 7300, microHAM II

In WinWarbler>config>Soundcard I have microHAM CODEC chosen for PSK & RTTY Reception and Transmission and same for Phone transmission.

What I have to do/check furthermore?

+ WinWarbler is relaying that error message from the soundcard device driver.

+ Using Windows Explorer, please navigate to your

C:\DXLab\WinWarble\Phone

+ folder. Double-click on the entry for

msag2.wav

+ What happens?

73,

Dave, AA6YQ









--
Questa email è stata esaminata alla ricerca di virus da AVG.
http://www.avg.com


Re: WinWarbler SSB macro not working

Dave AA6YQ
 

+ AA6YQ comments below

I have the problem that when I activate the SSB macro in WinWarbler it does no longer work (transmit) and a window appears saying:

“attempt to play C:\DXLab\WinWarble\Phone\msag2.wav on soundcard2 failed: (282) and (translated from Italian) the specified parameter is outside from the allowed interval of the specified command”

My working conditions are WIN10Pro, Icom 7300, microHAM II

In WinWarbler>config>Soundcard I have microHAM CODEC chosen for PSK & RTTY Reception and Transmission and same for Phone transmission.

What I have to do/check furthermore?

+ WinWarbler is relaying that error message from the soundcard device driver.

+ Using Windows Explorer, please navigate to your

C:\DXLab\WinWarble\Phone

+ folder. Double-click on the entry for

msag2.wav

+ What happens?

73,

Dave, AA6YQ


Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ AA6YQ comments below

Dave - yes there is a Reports folder

+ You previous post included this error message:

C:\Dxlab\DXKeeper|Reports\W2ECK WWFF/POTA Progress Report 2021-03019.txt for output; a log report cannot be generated"

1. I'm assuming that the vertical bar after to the immediate right of "DXKeeper" is actually a backslash character

2. the forward slash between "WWFF" and "POTA" may be making Windows unhappy; try replacing it with a dash or underscore character.

73,

Dave, AA6YQ


Re: DX Keeper and upload to LotW

Dave AA6YQ
 

+ AA6YQ comments below

I still have an issue uploading QSOs to LoTW.
I downloaded the latest version of the Gateway program (1.2.1) as you suggested. I have the "Upload to LoTW" checked.


In the DXKeeper Export QSOs tab I have "Export standard ADIF for LoTW" checked.

+ That setting is not relevant to automatically uploading QSOs to LoTW. It's only used when exporting a file to be manually uploaded.


Now when I log a contact (presently operating in the BARTG RTTY contest, the DXKeeper Gateway window indicates that the call has been logged and I get a pop up window indicating the the QSO has been uploaded to LoTW.
All seems to be working - however, when I go to my LoTW account and log in to check that the QSO has been logged, I do not see any of my recent contest QSO's.
Is there a delay to get the QSO uploaded?

+ No, but there can be a delay in LoTW processing your uploaded QSOs.

+ Have the QSOs you logged directly in DXKeeper before the contest appeared in LoTW?

+ Please check LoTW again an hour from now; are your uploaded QSOs present?

73,

Dave, AA6YQ


Re: DX Keeper and upload to LotW

Serge Bertuzzo
 

Good morning Dave/group. 

I still have an issue uploading QSOs to LoTW.
I downloaded the latest version of the Gateway program (1.2.1) as you suggested. I have the "Upload to LoTW" checked. 
In the DXKeeper Export QSOs tab I have "Export standard ADIF for LoTW"  checked. Now when I log a contact (presently operating in the BARTG RTTY contest, the DXKeeper Gateway window 
indicates that the call has been logged and I get a pop up window indicating the the QSO has been uploaded to LoTW. 
All seems to be working - however, when I go to my LoTW account and log in to check that the QSO has been logged, I do not see any of my recent contest QSO's. 
Is there a delay to get the QSO uploaded? Is this normal behavior?

Thank you for your assistance/feedback. 

Regards

 

Serge
VA3SB


WinWarbler SSB macro not working

Carlo - IK2RPE
 

I have the problem that when I activate the SSB macro in WinWarbler it does no longer work (transmit) and a window appears saying:

“attempt to play C:\DXLab\WinWarble\Phone\msag2.wav on soundcard2 failed: (282) and (translated from Italian) the specified parameter is outside from the allowed interval of the specified command”

My working conditions are WIN10Pro, Icom 7300, microHAM II

In WinWarbler>config>Soundcard I have microHAM CODEC chosen for PSK & RTTY Reception and Transmission and same for Phone transmission.

What I have to do/check furthermore?

Thanks


Carlo  IK2RPE


Re: How Do I Designate a POTA QSO in DXK

w2eck
 

Dave - yes there is a Reports folder

73 Paul


Re: Getting Winwarbler to work with IC-7610 in RTTY FSK mode

Floyd Sense
 

And the answer is: I should have set up USB B in the 7610 menu instead of USB A.  The answer was in a contest university presentation seen here:
https://www.kkn.net/~n6tv/N6TV_Dayton_2019_Everything_USB.pdf


Getting Winwarbler to work with IC-7610 in RTTY FSK mode

Floyd Sense
 


New IC-7610 here and the goal is to get it working with Winwarbler on FSK RTTY.  At this point, I have PTT working, but no FSK output when transmitting.
In the 7610, I have these settings:

USB Send = DTR
USB Keying)rtty) = RTS
In Commander, Port = 5, baud=115200,N,8,1
DTR=off, RTS=Flow

When I go to the PTT-Rcving panel on General tab of Commander config, the rig responds properly to TX and RX.  
The second com port for the 7610 is Com4.

In Winwarbler config, RTTY tab, FSK LSB is selected, mark offset is -2125, optimal offset is 2210 and FSK control is EXTFSK64 (this is a 64 bit win 10).  I open the EXTFSK window and select Com4, FSK Output - RTS, PTT output-DTR.

In MMTTY setup, PFF&FSK panel, port is set to EXTFSK64.
MMTTY TX Port panel, COM-TxD(FSK) is selected, and pressing USB port button, C is selected.

In MMTTY soundcard tab, USB audio codec selected for reception and one of the blank items selected for transmission.

I return to Winwarbler, in RTTY mode, and press the Start button.  The rig (in RTTY mode) goes to TX mode and the EXTFSK window shows LTRS being sent, but the monitor audio shows that no data is being sent.  If data keyed into Winwarbler input box, EXTFSK shows data being sent, but it isn't heard on the monitor.  Why is the FSK data not making it to Com4?

Could be something not set right in the 7610 menus, but the manual(s) don't show examples for FSK from an external program.  I've read through most of the 7610 RTTY posts here, with no luck.Help!

73, K8AC


WinWarbler

Yuriy Veselov
 

Dave, thanks for your prompt help.
Everything works fine now.
73  GL.

Yuri  R2ZX


Re: DX Keeper and upload to LotW

Serge Bertuzzo
 

Thank you very much for your prompt response Dave.
While I made sure all of the software I was using was the latest version, I confess that I did not check for a recent version of the N1MM+ DXKeeper Gateway software. 
My apologies. I have downloaded the latest version and will try it out. 

Keep up the great work. 

73
Serge
VA3SB


Re: DxCommander and inadvertent Xmt

Dave AA6YQ
 

+ AA6YQ comments below

Hi - I was operating FT8 (new to it) for a bit. QSOs were logged with DxKeeper and everything seemed very streamlined. I left the computer configuration the same and simply turned off my radio and came back to it a day or so later. FT8 operation was fantastic...QSOs were being logged. It was very strange...I was actually getting involved in the FT8 as I had many contacting me and had to manage that by direct intervention. Anyway, after several QSOs I looked at the log and none had been logged even though the prompt to log came up for each (and there were several) and I clicked OK.
This is where the fun starts. It seemed as though I was getting inadvertent transmissions commanded by the WSJTX app. I would have to hit the power button on the radio as I could not figure out from the various screens why this was happening. I then shut down all the apps (WSJTX, Dxlab, etc) and did not power down the computer. When I restarted DxLab and commander only, as soon as commander connected with the radio, it would start to transmit. Again, I used the power button to stop the inadvertent transmission. I then turned the radio back on and the radio (Yaesu FT991A) showed a blinking transmission light (it was not transmitting, but maybe being commanded to transmit??). I then restarted everything...computer...radio. Now, I think SSB voice operation is ok - I have not checked FT8 operation again yet.
Any hints here? I would like to consistently record FT8 contacts (I think I missed a few) and switch to other modes easily. There are a lot of moving parts with all these apps so I am not sure I have a grasp on this.
Any help would be appreciated.

+ Hint 1: read the WSJT-X user manual in

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.3.0-rc1_en.html

+ If you have questions, feel free to post them here, or on the WSJT-X support forum in

https://wsjtx.groups.io/g/main/messages


+ For QSOs logged in WSJT-X to be conveyed to DXKeeper, you must appropriately configure DXLab. Step-by-step instructions are here:

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes


+ For the QSOs you logged before configuring DXLab to receive them, you can direct DXKeeper to import them from the ADIF file that WSJT-X maintains. In the WSJT-X File menu, run the "Open Log Directory" command. That will produce a Windows Explorer window containing the file

wsjt_log.adi

+ This file contains all QSOs logged with WSJT-X. If none of these QSOs have previously been recorded in DXKeeper, you can simply direct DXKeeper to import this file. Otherwise, you must enable "Duplicate checking" on the "Import QSOs" tab of DXKeeper's Main window before importing the above file; importing with duplicate checking enabled is a slow operation.

73,

Dave, AA6YQ


Re: DX Keeper and upload to LotW

Dave AA6YQ
 

+ AA6YQ comments below

I have looked around the documentation/archives and have not been able to find a solution to uploading QSOs to LotW using N1MM+ DXKeeper Gateway software. I am using all of the latest version of the software mentioned below.

I log all my qso's to DXKeeper. When using WSJT-X and JTAlert, I have the software set up so that it automatically logs the contacts to DX Keeper.
I also have DXKeeper set up so that any contact that is logged via the capture window is uploaded to LotW. I can see when this is happening as I see a window indicating that the QSO is being uploaded to LotW.
If I make a contact and then go to the LotW site I can verify that the qso has indeed been uploaded.
My issue is when I use DXKeeper and N1MM DXKeeper Gateway. When making qsos with N1MM (say in a CW contest) even though I do see that QSO's are being logged in DXKeeper, if I go to LotW I do not see the latest contact(s) with the stations that I just worked.

I thought I had everything set up properly in DXKeeper as it seems to work when using WSJT and JTAlert software. Perhaps uploading automatically to LotW does not work when using the N1MM+ DXKeeper Gateway program for some reason? Please let me know if you require any additional information on my setup.

Any guidance or assistance would be greatly appreciate. Thank you very much in advance.

+ Did you check the "Upload to LoTW" box on the N1MM-DXKeeper Gateway window's Main window?

+ If this box is not present, upgrade to version 1.2.1 of the Gateway, which is available here:

https://www.dxlabsuite.com/N1MM-DXKeeper/index.htm

73,

Dave, AA6YQ


DxCommander and inadvertent Xmt

Lance HP
 

Hi - I was operating FT8 (new to it) for a bit. QSOs were logged with DxKeeper and everything seemed very streamlined. I left the computer configuration the same and simply turned off my radio and came back to it a day or so later. FT8 operation was fantastic...QSOs were being logged. It was very strange...I was actually getting involved in the FT8 as I had many contacting me and had to manage that by direct intervention. Anyway, after several QSOs I looked at the log and none had been logged even though the prompt to log came up for each (and there were several) and I clicked OK.
This is where the fun starts. It seemed as though I was getting inadvertent transmissions commanded by the WSJTX app. I would have to hit the power button on the radio as I could not figure out from the various screens why this was happening. I then shut down all the apps (WSJTX, Dxlab, etc) and did not power down the computer. When I restarted DxLab and commander only, as soon as commander connected with the radio, it would start to transmit. Again, I used the power button to stop the inadvertent transmission. I then turned the radio back on and the radio (Yaesu FT991A) showed a blinking transmission light (it was not transmitting, but maybe being commanded to transmit??). I then restarted everything...computer...radio. Now, I think SSB voice operation is ok - I have not checked FT8 operation again yet.
Any hints here? I would like to consistently record FT8 contacts (I think I missed a few) and switch to other modes easily. There are a lot of moving parts with all these apps so I am not sure I have a grasp on this.
Any help would be appreciated.

Lance

4281 - 4300 of 204790