DX Suite Commander output bug

[kb9kld]

I believe I have found a bug with the DXLab Commander output from the port set on the radio setup tab. It appears to be specific to the Icom 756 radio as the KX3 I have works correctly. Here are captures from Wireshark on the port with an application querying it. The CmdGetFreq command sends .000 instead of the proper frequency. The other commands used look correct. The second capture is the same application polling the WSJTX Cat port configured on the UDP preference tab. It works correctly there and returns the proper frequency. So this appears to be an issue in the frequency formatting for the IC-756 radio from the port configured on the radio tab.

Icom 756 Radio 1

Dx Suite Commander Radio 1 Port 7801

<command:10>CmdGetFreq<parameters:0>
<CmdFreq:4>.000
<command:12>CmdSendSplit<parameters:0>
<CmdSplit:3>OFF
<command:11>CmdSendMode<parameters:0>
<CmdMode:3>USB



From the UDP Tab WSJTX CAT port

<command:10>CmdGetFreq<parameters:0>
<CmdFreq:9>50313.000
<command:12>CmdSendSplit<parameters:0>
<CmdSplit:3>OFF
<command:11>CmdSendMode<parameters:0>
<CmdMode:3>USB

Jeff
K9KLD

[DL2RUM]

<CmdFreq:4>.000 will be sent whenever the frequency is unknown. Is the frequency shown correct in the logging mask?

[kb9kld]

Yes, ithe freq shows correctly in the log entry field and in the two radio toggle box. It tracks if you change the VFO. Those two samples were taken moments apart from each of the two ports without changing anything in Rumlog. The one configured in WSJT-X dialog works, the radio one does not.

[DL2RUM]

Just tested the Icom setting with a IC-705. It works as expected. Are you sure you have selected different port numbers for each server?
The Network windows may show you useful information.

[kb9kld]

Here is a capture of the radio settings and the network dialog along with the wireshark capture. I turned off the port for the second radio and I disabled the exchange cat data on the UDP tab for WSJT-X. So the only active port should be the one for the 756 radio. The command to retrieve the mode works as I can change the radio mode and I see that response change. So that suggests that it is following the radio and the messages all lok well formed other than the frequency value. The network shows the proper port and the WSJT connection which is what I am using to connect.

Happy to run any other debugging you can suggest.

[DL2RUM]

Which client app do you use? I tested with WSJT-X only.
The question is, which command is sent to poll for the frequency?

[kb9kld]

I am using the formal WSJT-X 2.4.0 release. This is the actual exchange recorded from watching the network traffic. This works fine for my KX3 and a Kenwood radio with the same messages when I configure them to use a radio specific port. It seems to be tied to the 756. The set commands also work as WSJT-X can command the radio to change frequency. The commands to transmit also work. It appears isolated to the get frequency. And it is only a problem when using the DX Commander port on the radio tab.

WSJT-X sends:

<command:10>CmdGetFreq<parameters:0>

Rumlog responds with:

<CmdFreq:4>.000

This tells me Rumlog understands the request, but it is just not returning the correct value when it comes over the port set in the radio tab. So it feels like whatever logic that processes the incoming request to poll the radio state has some difference on the two paths for the Icom 756 Radio. The WSJT-X port returns the value from the active radio when there are two. And that always works. I can switch active radios back and forth and WSJT-X follows. I can point WSJT-X to the 2nd radio on the port defined in the radio tab and for the KX3 and the Kenwood that works. Making the 756 the 2nd radio does not change either. No matter which radio the 756 is, it does not work on the radio port. It is just the 756 that gives the bad response when using it's radio port. I don't have any other Icoms to try to see if it specifically the Icom 756.

[DL2RUM]

It's a little bit more complex as assumed.
The 756 supports few CI-V commands only. It's not possible to find out if the current frequency is used for RX or for TX. That's why the frequency is flagged as unknown.

Try this: https://dl2rum.de/RUMlogNG/RUMlogNG_Test.zip

[kb9kld]

That version works as expected. That makes it work really nice to have the two WSJT-X instances running and have them be locked to control the correct radio.

Thanks
Jeff
K9KLD