Ah, that was the missing step.
Thanks for the quick reply.
Jeff
K9KLD
Search found 17 matches
- Wed 11. Aug 2021, 18:06
- Forum: RUMlogNG
- Topic: QSL Address label issue
- Replies: 2
- Views: 1764
- Wed 11. Aug 2021, 17:32
- Forum: RUMlogNG
- Topic: QSL Address label issue
- Replies: 2
- Views: 1764
QSL Address label issue
I have run into an issue trying to print address labels with Avery 5160. The labels are offset down and to the right about a 1/4 of an inch and the right sides are cut off. I am using a borderless paper in the print dialog under Paper Handling -> Destination Paper Size, but it still acts like it has ...
- Fri 18. Jun 2021, 15:33
- Forum: RUMlogNG
- Topic: DX Suite Commander output bug
- Replies: 8
- Views: 3274
Re: DX Suite Commander output bug
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
Thanks
Jeff
K9KLD
- Fri 18. Jun 2021, 14:21
- Forum: RUMlogNG
- Topic: DX Suite Commander output bug
- Replies: 8
- Views: 3274
Re: DX Suite Commander output bug
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 ...
- Fri 18. Jun 2021, 12:39
- Forum: RUMlogNG
- Topic: DX Suite Commander output bug
- Replies: 8
- Views: 3274
Re: DX Suite Commander output bug
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 ...
- Thu 17. Jun 2021, 17:32
- Forum: RUMlogNG
- Topic: DX Suite Commander output bug
- Replies: 8
- Views: 3274
Re: DX Suite Commander output bug
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.
- Thu 17. Jun 2021, 13:45
- Forum: RUMlogNG
- Topic: DX Suite Commander output bug
- Replies: 8
- Views: 3274
DX Suite Commander output bug
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 ...
- Wed 16. Jun 2021, 19:46
- Forum: RUMlogNG
- Topic: Multiple Grid locator support
- Replies: 8
- Views: 3423
Re: Multiple Grid locator support
I sent a reply Monday and another today to your follow up. Hopefully it did not get lost in spam.
- Thu 10. Jun 2021, 21:33
- Forum: RUMlogNG
- Topic: Multiple Grid locator support
- Replies: 8
- Views: 3423
Re: Multiple Grid locator support
I have seen both 4 and 6 char grids in the ones I have downloaded from lotw. I think that depends on how the contact creates the location. I think an improvement would be to use one of the user defined fields if it could be mapped to the VUCC_GRID field in the ADIF files that Rumlog exports. Those ...
- Thu 10. Jun 2021, 17:50
- Forum: RUMlogNG
- Topic: Multiple Grid locator support
- Replies: 8
- Views: 3423
Re: Multiple Grid locator support
Here is an example of one of the confirmed records at LOTW. The VUCC_GRIDS field has all four grids that where part of the QSO. <APP_LoTW_OWNCALL:5>K9KLD <STATION_CALLSIGN:5>K9KLD <CALL:5>------ <BAND:2>6M <FREQ:8>50.30480 <MODE:3>FT8 <APP_LoTW_MODEGROUP:4>DATA <QSO_DATE:8>20210606 <APP_LoTW_RXQSO ...