HamApps Support (VK3AMA)
On 20/06/2019 7:06 am, techpubsman wrote:
My club uses N3FJP Field Day logger for field day. We have five operating positions each with a laptop that network connects to a master laptop where the actual logging file exists. For the last few days I have set up the laptops in the network configuration we will be using this weekend and tried to get JTALert to play nicely with N3FJP FD Logging software. Read the tutorial and Looked at a lot of YouTube videos on the subject. Running the latest WSJT-X, JTAlert and FD Logging software versions. Just can not get them to work together. When I click on the TCP checkbox, the software indicates the software on that laptop is a client and you must connect to our master laptop which I have done. There is no interaction between JTALert and N3FJP.Randy,
As a first step, ignore JTAlert and make sure you have the N3FJP networking setup correctly. You may want to post to the "N3FJPSoftwareUsers" users group to get accurate answers on how to correct the networking problems. N3FJP himself monitors that group and is best placed to provide assistance.
With respect to JTAlert, you need to run a copy on each laptop that is running a local copy of the N3FJP FD log and WSJT-X. Setup JTAlert to work with that local copy of FD Log as per the JTAlert Tutorial in its Help File. Don't try and have each JTAlert access the remote master log. Have JTAlert log to the local copy of FD log and leave that local copy of FD log (assuming you have the FD Log network setup correctly) manage the transfer of the data to the Master log.
de Laurie VK3AMA