Terry, Matters around TCP spotting has been raised a number of times (and I note a subsequent response from Robert AD6I).
Terry - as Bill raises - JTAlert is by FAR the most advanced tool that has the "potential" ... yet at the moment lacks "capability". [ Laurie VK3AMA also runs his own "spotting" site https://hamspots.net that may be worth investigating. ] I know that Laurie follows posts in here very keenly; it would be worthwhile reviewing posts if not adding supportive posts at the JTAlert support forum at https://hamapps.groups.io/ . Refer to chatter that may occur in this main developer's forum for WSJTX in any post that you make as such is always assistive. WSJT-X should be kept as far as possible to minimal "external" functions with third-party apps providing communication and connectivity to other services. Perhaps even providing direct comms with PSKREPORTER is outside the scope of what it should be servicing (though I state is very reasonable in providing this currently)? The aim here with WSJTX is performance with streamlined code and core functionality only. 73 Steve I VK3VM / VK3SIR -----Original Message----- From: Bill Somerville <g4...@classdesign.com> Sent: Tuesday, 30 June 2020 11:02 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Request for WSJT-X Feature On 30/06/2020 01:53, Terry Estes wrote: > Many other amateur radio stations use the N3FJP Logging Software, > primarily for logging ARRL Field Day and Winter Field Day contests. > The addition of Field Day exchange capabilities to WSJT-X has made the > use during FD of FT-8 a major improvement and has increased its use > for FD. > Many stations now utilize Raspberry Pi computers running WSJT-X under > various forms of Linux. (Mine is Raspbian Stretch) N3FJP unfortunately > only runs on Windows based computers. > Herein lies the problem - A way to export the WSJT-X log entries > (packets) to the N3FJP software. > WSJT-X appears to utilize UDP communications with N1MM Logging Software. > N3FJP utilizes TCP communications to import the logging packets from > other communications packages such as FLDigi. N3FJP acts as a TCP > Server on a Windows machine and FLDigi as a TCP Client on a Linux > machine, interconnected either by Ethernet cable or by WiFi. > > Proposal: It would make things appear seamless if WSJT-X could also > act as a TCP Client, running on the Linux machine, sending the > appropriate logging packets to the N3FJP Server on the Windows machine. > The FLDigi implementation sends the callsign to N3FJP as it is first > collected by FLDigi, allowing N3FJP to check for duplication (DUPEs). > As long as WSJT-X is checking for dupes, it may not be necessary to > send the call across prior to completion of the FD exchanges. > WSJT-X can send the complete contact log information across, in proper > order, to N3FJP at the completion of the contact. > Any and all information about the N3FJP software is provided by its > creator/owner to help further the interconnection capability and > utilization of his software. > > Thanks for your consideration, > > Terry Estes, W4ZQ > w...@arrl.net Terry, JTAlert can nearly do this for you. Unfortunately to make setup easier JTAlert reads the WSJT-X settings file and also expects the WSJT-X process to be running on the same machine. It may be worth asking Laurie, VK3AMA, if there is a way for JTAlert to do without those same machine requirements. The bulk of JTAlert communications with WSJT-X are via the WSJT-X UDP Message Protocol, which will run just fine over a network connection. 73 Bill G4WJS. _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
