Re: [wsjt-devel] OSX - WSJT-X UDP interface -- help from Apple Mac folks -pse!

[KI7MT <ki...@gm...>]

Hi Bill,

See below

On 08/20/2016 01:41 PM, Bill Somerville wrote:
> Hi Greg,
> 
> On 20/08/2016 20:30, KI7MT wrote:
>> It works OK on Linux ( Ubuntu 14.04 + Python 2.7.6 ) except it prints a
>> bunch of unicode characters for spaces on each line, looks pretty bad.
> The data is not plain text, the format is described in NetworkMessage.hpp.

OK, I'll have a read through the hpp file.

>>
>> There are other ways to monitor decodes outside of UDP messaging using
>> Python. You could simply parse the ALL_TXT file for the current time -1
>> minute at the top of each minute + <some time delay to allow for
>> decoding or whatever>, or simply run the loop at time + 5 seconds or
>> whatever in a loop. That would allow you to also format the line to you
>> liking.
> 
> Please do not read the log or temporary files that WSJT-X is writing 
> while WSJT-X is running, that leads to locks that can impact on WSJT-X 
> performance. The UDP protocol is intended to be the way to interact with 
> WSJT-X programmatically. There is a little work to be done to code the 
> routines to decode the data types used in the message, but once that is 
> done you will find everything you need from WSJT-X plus a few handy replies.

What I've been doing for WSPR, which I assume is the same for other
WSJT-X modes, was to simply copy the ALL_WSPR.TXT at T = 00 + 5 seconds
to a file outside of the WSJT-X directory, then parse the tmp file for
what I needed.

I've not done this with the WSJT-X ALL.TXT file, only the ALL_WSPR.TXT
file, but it should not be any different I wouldn't think. At one point
I had a cron job doing this so I cold add the WSPR decodes to a Database
for other activities.

I don't think I ever tried to open the file(s) directly, for the reasons
you stated above, and I don't recall ever having run into a lock file
situation. I can't speak for others needs, but, for my purposes, I just
want access to the decoded lines for the the various modes I run.

A present, I don't have a need to talk to WSJT-X programatically unless
that's the only way to get the decoded data I need without interfering
with WSJT-X activities.

> 
> 73
> Bill
> G4WJS.

73's
Greg, KI7MT