Date   

Re: WinWarbler SSB macro not working

Dave AA6YQ
 

@ more AA6YQ comments below

I did it, i.e. I used Realtek Audio in WinWarbler and the message was properly reproduced in the PC audio system.
Then I changed back in Winwarbler config>soundcard the "Phone Transmission" to the "microHAM CODEC" soundcard and..... the message(s) are correctly reproduced again via the radio.
Then it appears that now everything is re-shaped and that only the changing of the soundcard and the coming back to the correct one has solved the problem. I do not know why it happened, but I'm glad of the result!

@ It's unusual for a diagnostic step to solve the problem. Something obviously changed; it would be best to understand what, and how -- otherwise, the incorrect behavior could return -- and at the worst possible time.

@ Joe W4TV, any suggestions for how to proceed from here?

73,

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?


Re: WinWarbler SSB macro not working

Carlo - IK2RPE
 

Dave,
I did it, i.e. I used Realtek Audio in WinWarbler and the message was properly reproduced in the PC audio system.
Then I changed back in Winwarbler config>soundcard the "Phone Transmission" to the "microHAM CODEC" soundcard and..... the message(s) are correctly reproduced again via the radio.
Then it appears that now everything is re-shaped and that only the changing of the soundcard and the coming back to the correct one has solved the problem. I do not know why it happened, but I'm glad of the result!

Many thanks

Carlo IK2RPE

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

+ 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








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


Re: N4PY Icom software, IC-7610 and Commander problem

neil_zampella
 

Thanks Dave ... I knew it had nothing to do with the UDP reporting
settings, but didn't know about the TCP connection :)

Neil, KN3ILZ

On 3/21/2021 12:23 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

UM ... Commander does not interface with WSJT-X via UDP. AFAIK it uses a direct serial connection via a COM port.

+ Commander and WSJT-X interoperate by means of TCP commands that Bill G4WJS and I defined several years ago. It provides a single abstraction that works for every radio model supported by Commander; this proved more difficult than either of us understood going in, but we made it work.

73,

Dave, AA6YQ





Re: N4PY Icom software, IC-7610 and Commander problem

Dave AA6YQ
 

+ AA6YQ comments below

UM ... Commander does not interface with WSJT-X via UDP. AFAIK it uses a direct serial connection via a COM port.

+ Commander and WSJT-X interoperate by means of TCP commands that Bill G4WJS and I defined several years ago. It provides a single abstraction that works for every radio model supported by Commander; this proved more difficult than either of us understood going in, but we made it work.

73,

Dave, AA6YQ


Re: N4PY Icom software, IC-7610 and Commander problem

Dave AA6YQ
 

+ AA6QY comments below

Hmmmmm... Guess I didn't do a very good job with the terminology, so I'll give it another try. I said UDP not based on personal knowledge, but based on the fact that to get the communications to work between WSJT-X and Commander I went to the reporting tab of WSJT-X settings and entered the UDPServer IP address (127.0.0.1) and the UDP server port number (2237) and checked off three boxes that had to do with UDP requests. Then, in a panel called Secondary UDP Server, I checked a box saying "Enable logged contact ADIF broadcast" and again plugged in an IP address and server port number. The box up the page aways that said "Use TCP/IP" address was NOT checked.

+ That section of WSJT-X controls governs the routing of UDP messages containing QSOs to be logged. It has nothing to do with transceiver control.


The N4PY Icom software is basically the same as the Pegasus software for all the other brands. N4PY told me that the technique I referred to was special for communications with DXLab, but maybe that's not true either?

+ A TenTec Pegasus is essentially a PC peripheral. If Commander is installed on that PC, it controls the Pegasus frequency and mode by writing a record in a file named Pegasus.in in a specified "Control folder". To switch a Pegasus between RX and TX, Commander writes either PTTOFF or PTTON into a file named Pegasus.aux in the same "Control folder".


Anyway, in Commander config, General Tab, Radio panel, I selected Pegasus_N4PY as the model and then specified the location of a "control folder". In the N4PY program settings, I specified the name of that same folder, which they call the "Transfer folder". And, N4PY and Commander were able to successfully communicate via that folder.

+ Pegasus_N4PY is a "Pegasus Emulator".

And, what I tried to tell you is this: When I use that means of communications between N4PY and Commander, Commander no longer responds to the request from WSJT-X to turn on PTT when I run the PTT test in WSJT-X.

+ If you have Commander's Radio Model set to Pegasus_N4PY, then when Commander is directed switch from RX to TX, it writes PTTON in the Pegasus.aux file in the "Control folder". I've just verified that this works correctly; you can do so yourself by using Notepad to open the Pegasus.aux file in the "Control folder". If you have N4PY's Pegasus Emulator controlling your IC-7610, and you're saying that the IC-7610 is not being switched between RX and TX, then the question to ask is why the Pegasus Emulator is not responding to a PTTON in the Pegasus.aux file by directing the IC-7610 to switch from RX to TX.

+ Perhaps the Pegasus emulator is responding -- but far too slowly for WSJT-X. Commander opening a file, writing PTTON or PTTOFF in it, and then closing that file is not a slow operation - even if the file is hosted on a solid state drive (which I would think it would quickly wear out!). The Pegasus Emulator must periodically open/read/close the Pegasus.in and Pegasus.aux files to see if new frequencies and modes have been specified, or RX/TX changes have been specified respectively. The time from Commander receiving an RX=>TX or TX=>RX directive from WSJT-X to the Pegasus Emulator learning that it's to switch the transceiver's RX/TX would likely be hundreds of milliseconds, if not seconds.


Getting back to Commander and my WSJT-X problem: If I specify the radio as an IC-7610 (with direct connection to the 7610 USB CAT port), then a box appears in the radio panel below the model area that says "Verify CI-V command acceptance". If I fail to check that box, then the WSJT-X PTT test fails in exactly the same manner as when I'm using the control folder with the port controlled by N4PY. I check that box, and then the WSJT-X PTT fest completes properly.

+ When you have Commander configured to control your IC-7610 directly, to what do you have the "Command interval" set in the Radio panel on the Configuration window's General tab?

+ If the "Command interval" is too short, Commander's outgoing "report status" commands can collide with the radio's responses to previous "report status" commands, because the Icom CI-V bus conveys commands and responses on a single conductor. Enabling "Verify CI-V command acceptance" forces Commander to not send a new "report status" command until it has received the radio's response to the previous "report status" command. By setting the "Command interval" to a small value and enabling "Verify CI-V command acceptance", Commander and the radio can interoperate at the maximum possible speed without collisions; I run my IC-7300 with a "Command interval" of 10 ms - with "Verify CI-V command acceptance" enabled.

+ If you specify a short "Command interval" but do not enable "Verify CI-V command acceptance", then outgoing commands can be garbled by CI-V bus collisions. Either increase the "Command interval", or enable "Verify CI-V command acceptance"; I recommend the latter.

So, that's the story. If it still doesn't make sense, I'll just have to find another way to makes things work.

+ I now understand what you're doing. However, the scheme of conveying commands from Commander to a Pegasus Emulator through files and then from the Pegasus Emulator to your IC-7610 is likely far too slow for WSJT-X.

+ And if WSJT-X interoperates correctly with Commander when you enable "Verify CI-V command acceptance", then you have Commander configured for optimal control of your IC-7610.

73,

Dave, AA6YQ


Re: N4PY Icom software, IC-7610 and Commander problem

neil_zampella
 


On 3/20/2021 10:47 PM, Floyd Sense wrote:
Hmmmmm... Guess I didn't do a very good job with the terminology, so I'll give it another try.  I said UDP not based on personal knowledge, but based on the fact that to get the communications to work between WSJT-X and Commander I went to the reporting tab of WSJT-X settings and entered the UDPServer IP address (127.0.0.1) and the UDP server port number (2237) and checked off three boxes that had to do with UDP requests.  Then, in a panel called Secondary UDP Server, I checked a box saying "Enable logged contact ADIF broadcast" and again plugged in an IP address and server port number.  The box up the page aways that said "Use TCP/IP" address was NOT checked. 

UM ... Commander does not interface with WSJT-X via UDP.   AFAIK it uses a direct serial connection via a COM port.


73, K8AC


Re: N4PY Icom software, IC-7610 and Commander problem

Floyd Sense
 

Hmmmmm... Guess I didn't do a very good job with the terminology, so I'll give it another try.  I said UDP not based on personal knowledge, but based on the fact that to get the communications to work between WSJT-X and Commander I went to the reporting tab of WSJT-X settings and entered the UDPServer IP address (127.0.0.1) and the UDP server port number (2237) and checked off three boxes that had to do with UDP requests.  Then, in a panel called Secondary UDP Server, I checked a box saying "Enable logged contact ADIF broadcast" and again plugged in an IP address and server port number.  The box up the page aways that said "Use TCP/IP" address was NOT checked. 

The N4PY Icom software is basically the same as the Pegasus software for all the other brands.  N4PY told me that the technique I referred to was special for communications with DXLab, but maybe that's not true either?  Anyway, in Commander config, General Tab, Radio panel, I selected Pegasus_N4PY as the model and then specified the location of a "control folder".  In the N4PY program settings, I specified the name of that same folder, which they call the "Transfer folder".  And, N4PY and Commander were able to successfully communicate via that folder.

And, what I tried to tell you is this: When I use that means of communications between N4PY and Commander, Commander no longer responds to the request from WSJT-X to turn on PTT when I run the PTT test in WSJT-X. 

Getting back to Commander and my WSJT-X problem: If I specify the radio as an IC-7610 (with direct connection to the 7610 USB CAT port), then a box appears in the radio panel below the model area that says "Verify CI-V command acceptance".  If I fail to check that box, then the WSJT-X PTT test fails in exactly the same manner as when I'm using the control folder with the port controlled by N4PY.  I check that box, and then the WSJT-X PTT fest completes properly.  So, that's the story.  If it still doesn't make sense, I'll just have to find another way to makes things work.  Thanks for your time.

73, K8AC


Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ AA6YQ comments below

Dave - thank you, you nailed it. Changed the forward slash to an underscore and the report is now generated just fine.

+ Good! Did you use a script to generate the progress report?

73,

Dave, AA6YQ


Re: DX Keeper and upload to LotW

Dave AA6YQ
 

+ AA6YQ comment sbelow

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

+ First-come, first served. If small uploads were given priority, every logging application would break large uploads into groups of uploads small enough to have priority - accomplishing nothing except lowering aggregate throughput.

73,

Dave, AA6YQ


Re: N4PY Icom software, IC-7610 and Commander problem

Dave AA6YQ
 

+ AA6YQ comments below

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.

+ WSJT-X and Commander interoperate via TCP, not 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?

+ I know nothing about N4PY's Icom software, much less how it would interoperate with Commander.

+ I also don't know what "the old file transfer" technique refers to.

+ I do know that you can't have two different applications directly sending CAT commands to the same transceiver.

73,

Dave, AA6YQ


Re: How Do I Designate a POTA QSO in DXK

w2eck
 

Dave - thank you, you nailed it. Changed the forward slash to an underscore and the report is now generated just fine.

Thank you again for the wonderful support you provide.

73 & Be Safe
Paul w2eck


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

2101 - 2120 of 202621