CALLSIGN field not updated from WSJT-X running from Raspberry Pi
Posted: 15 Oct 2020, 16:27
I posted this a week ago and no one responded, so I am trying this board. I love the software, thanks for all you all do.
==========================================================================
Hello,
I searched the forums and found this topic, but none of the suggestions worked for me and the posts were rather dated so I thought I would post my question.
I am running Log4om version 2.9.0.0 on a windows 10 machine with a static IP address
I am running WSJT-x version 2.2.2 on a Raspberrypi running raspien
My configuration allows UDP traffic from ports 2333, 2237, and 12060.
[
When I had log4om and WSJT-x running on the same machine, the CALLSIGN field was populated when I double-clicked a callsign to begin a qso and when I logged the contact in WSJt-x the qso was logged in log4om.
Now that I am running WSJT-x from another machine, the CALLSIGN field is not updated (it's blank), but the QSO is logged when I log it on WSJT-x.
Can anyone help with this?
Mike - K3MAW
==========================================================================
Hello,
I searched the forums and found this topic, but none of the suggestions worked for me and the posts were rather dated so I thought I would post my question.
I am running Log4om version 2.9.0.0 on a windows 10 machine with a static IP address
I am running WSJT-x version 2.2.2 on a Raspberrypi running raspien
My configuration allows UDP traffic from ports 2333, 2237, and 12060.
[
When I had log4om and WSJT-x running on the same machine, the CALLSIGN field was populated when I double-clicked a callsign to begin a qso and when I logged the contact in WSJt-x the qso was logged in log4om.
Now that I am running WSJT-x from another machine, the CALLSIGN field is not updated (it's blank), but the QSO is logged when I log it on WSJT-x.
Can anyone help with this?
Mike - K3MAW