www.dl2rum.de

I cannot see it on the Apple Store nor in the Downloads section. How can i get it?

Got it, thanks! Now this bl**dy setup.

WSJT-X and RumlogNG on the same machine. I followed the instructions in the WSJT-X and RUMlog section of the help. IP address used for all settings is 127.0.0.1 as mentioned in the manual.

RUMlog sees the connection to the radio, but doesn't follow. I need to Reset Cat a few times for RUMlog to show the new frequency.
Switching bands in WSJT-X doesn't switch the radio.

Switched from using 127.0.0.1 to the real internal IP address in the 192.168 range. This solves the Follow TRX issue in RUMlog.
Switching bands in WSJT-X still doesn't switch bands on the radio. Test CAT and Test PTT in WSJT-X work as expected. When switching the bands manually using the radio both WSJT-X and RUMlog follow correctly.

How can i make sure WSJT-X is sending the band changes to RUMlog?

Thanks,

Ton.

I was using Wireshark and when i switch from 20m to 15m in WSJT-X.
I can see the XML with the CmdSetFreMode request being sent to port 7374, but then i immediately get another GetCmdFreq and a response with 14.074 as frequency. So WSJT-X assumes the radio is on 20m and will not switch to 15.

Does that make sense?

Ton.

For now i will run RUMlog and WSJT-X on two separate serial interfaces.

You should show us all of your settings.

You have to get CAT control from RUMlog working first - without Fldigi and without WSJT-X
Changing ip addresses can not affect your serial CAT connection.
ip addresses may change. You should use localhost or 127.0.0.1
Why do you have set the Power up RTS line option? This may interfere your connection.
You have selected two PTT options for WSJT. Deselect the PTT option in RL --> UDP --> WSJT-X or set in WSJT-X --> Radio --> PTT Method to None

DL2RUM wrote:You have to get CAT control from RUMlog working first - without Fldigi and without WSJT-X

CAT control works correctly in RUMlog.

DL2RUM wrote:Changing ip addresses can not affect your serial CAT connection.

I know. I find this strange as well. Maybe because i have A LOT of interfaces in my Mac.

Code: Select all

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether f4:5c:89:ac:1a:41
	inet6 fe80::e1:7aab:d1d2:32d6%en0 prefixlen 64 secured scopeid 0x5
	inet 192.168.1.56 netmask 0xffffff00 broadcast 192.168.1.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
en1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
	options=60<TSO4,TSO6>
	ether 4a:00:05:0e:dc:f0
	media: autoselect <full-duplex>
	status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
	options=60<TSO4,TSO6>
	ether 4a:00:05:0e:dc:f1
	media: autoselect <full-duplex>
	status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
	ether 06:5c:89:ac:1a:41
	media: autoselect
	status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
	ether c6:07:6e:33:c6:2d
	inet6 fe80::c407:6eff:fe33:c62d%awdl0 prefixlen 64 scopeid 0xa
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
bridge0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 4a:00:05:0e:dc:f0
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	member: en1 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 6 priority 0 path cost 0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 7 priority 0 path cost 0
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::791d:91cc:d40:332b%utun0 prefixlen 64 scopeid 0xc
	nd6 options=201<PERFORMNUD,DAD>
en7: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 00:e0:4c:68:e7:67
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (none)
	status: inactive
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
	ether 38:c9:86:24:51:0a
	media: autoselect (none)
	status: inactive

DL2RUM wrote:ip addresses may change. You should use localhost or 127.0.0.1

I will follow your advice.

DL2RUM wrote:Why do you have set the Power up RTS line option? This may interfere your connection.

Unchecked. Don't see a difference.

DL2RUM wrote:You have selected two PTT options for WSJT. Deselect the PTT option in RL --> UDP --> WSJT-X or set in WSJT-X --> Radio --> PTT Method to None

There is no WSJT-X --> Radio --> PTT Method --> None so i did the first option.

All IP addresses set to 127.0.0.1 instead of 192.168.1.56. RUMlog follows the radio correctly. WSJT-X follows RUMlog correctly.

Radio doesn't follow the band change in WSJT-X.

Radio doesn't follow the band change in WSJT-X.

Does the radio follow RUMlog? Can you command the radio to QSY?

www.dl2rum.de

CAT Control issue WSJT-X->RUMlog using Kenwood TS590S

CAT Control issue WSJT-X->RUMlog using Kenwood TS590S

Re: 3.7?

Re: 3.7?

Re: 3.7?

Re: 3.7?

Re: 3.7?

Re: 3.7?

Re: 3.7?

Re: 3.7?

Re: 3.7?