Too many different pieces of software. Why not simply connect JTAlert by TCP to Logger32?
?
If you must use socat, then look at the Logger32 TCP event viewer window. It should be 'listening' (waiting for a connection. The LED at the bottom right should be amber). From what you describe (only one contact logged, then nothing)? My SWAG is that after the first contact is logged, socat is not disconnecting and therefor cannot reconnect to log a second contact. You will see in the Logger32 TCP event viewer that after the first contact is logged, the socket stays connected (the LED at the bottom right stays green).
?
If the Logger32 TCP socket is stuck with an open connection (anything other than an amber LED), then it is not necessary to shut down all the software and restart. Simply right click on the Logger32 TCP pane on the lower status bar. Close then re-open the socket. It will re-open 'listening'.
?
Or something like that. SeventyThree(s).
?
On 11/19/2024 4:10 AM EST Peter Eckersberger via groups.io <oe3epw@...> wrote:
?
?
Hello,
Need some help. Using for more than a year the?program combination "Logger32", "JTAlert" and - thanks Prasad - "Socat" v 1.7.3.0-windows master. For me and my needs the most convenient program system.
This system was working flawlessly until a week ago when all of a sudden the logging via "Socat" into "Logger32" had partly quitt. "Partly" because the very first QSO is getting logged as expected but nothing happens with the following contacts. Although those QSOs are still logged into the JTAlerts "Standard ADIF file" they don't show up in "Socat" and are therefore not transferred to "Logger32". The whole logging control system gets stuck. Very disappointing. To get rid of this situation I've to switch off all programs in use and start again by loading "Logger32", followed by "JTAlerts" "Auto-Start" feature starting "Socat", "WSJT-X" and "VE7CC". When all needed programs are running I'm able to make ONE qso. THIS only ONE is shown on "Socat" and gets transferred to "Logger32", for all the following contacts .... see the story above. Back to square one.
To me it seems the frog is hidden somewhere in "Socat". When googling around I realized that there is a newer Socat-version 1.8.0.1 for Windows available. Maybe there is a helpful person who can give me a hand on that matter. OM Prasad maybe can make a comment on whether or not "Socat" could be the root of my problem and if an update to the newer Socat-version could help to overcome it.
?
73 and tnx in advance de Peter, OE3EPW
AR? SK
?
Finally here my program config ...
