i’m just sending a small feedback when it comes to exporting cabrillo log files with WRL based on the previous contest that i participated in which is the ARRL digital contest that happened on june 6th i exported my origional log and submitted it to the ARRL i kept getting a return saying that the grid is missing which that i didn’t understand because it was showing in the .log file so i tried exporting and submitting again kept getting that error before i decided to export the log in ADIF create a log in N1MM and import the ADIF into N1MM then have it export a new cabrillo file and upload the new log to ARRL then they accepted the log don’t know what made the ARRL decide to reject the one from WRL but accept the one from N1MM but hope this helps the team make adjustments for the next ARRL contests coming up especially field day
examples are enclosed in the link to my google drive folder
For every contest on WRL you have to enter your exchange in the ‘my exchange’ field underneath the main logging fields before exporting your Cabrillo. Then it will have all the the correct exchange data and fields in the Cabrillo.
completely understandable which that was already in the log the way that i did it was where apparently WSJTX was not communicating with WRL CAT control software at all with the 255.0.0.1 address nor 127.0.0.1 address i just made contacts and at intervals i pause closed the software moved the wsjtx log.adi file from where WSJTX saves it to my desktop continue making the contacts and uploading the adi file to the contest log as is and it brought the callsign their grid their report if they were not participating right on over with the info already filled i would expect that when i export the cabrillo and sent it to the ARRL they would accept it but apparently didn’t and had to export the contest log in ADI and had N1MM create the cabrillo file for the ARRL to accept the submission
that’s why i added the accepted and rejected files as comparison to help the contest team in the upcoming ARRL hosted contests the rejected is what WRL generated and and ARRL rejected and the accepted is what N1MM generated that ARRL accepted
Ohh ok, yeah importing an adif will not bring in the contest exchange data into the contest exchange fields in a contest. They need to be logged in the contest logbook. We will be trying to add the functionality of passing the contest exchange data while streaming contacts from wsjtx via the cat control app at some point. The problem is its difficult to know exactly what the contest exchange is in that context. In the ARRL digital contest its not hard because its just the gridsquare but in other situations where the contest exchange may be something other than a gird, thats where the difficulty comes in. but with all that said, as long as you are entering the exchange in the contest exchange field(s) inside the contest logbook and adding the ‘my exchange’ data before exporting the cabrillo everything will export as expected. After we get through WRTC2026, Field Day 2026, and finish a couple of major upgrades we will be adding a lot of enhancements and new features to the contesting side of WRL .
nice i figured passing that along to help the team in future contests especially from what i went through with the digital contest last weekend where for some reason WSJTX was not making the contact with the CAT control software not sure if WSJTX is and CAT is not hearing the communication or CAT is listening and WSJTX is not talking where i tried it in contest mode and in regular mode setting the log destination to a test log made couple contacts and no luck so that’s my only last solution to not use the CAT control program and just import the adi log periodically in my WRL contest log
ok i don’t use gridtracker just because i found that when i do any FT# modes i keep getting the same grids constantly so there’s no need for me to use it in my case so for me i would basically launch CAT control software change the listening port to the screenshot start the WSJTX service then open WSJTX itself and set the port to what i changed then close everything then reopen CAT control and start listening then WSJTX in that order and it should start talking to each other if i’m correct?
@W7AAF yes, set the UDP port in WSJTX (for the primary UDP section) to 2238 and set the WSJTX settings in the WRL cat control app to 2238, close everything down, start the UDP listener in the WRL cat control app then start wsjtx
tried it out making 7 contacts those are synced and shows up on my WRL log on the app so right now they are now talking to each other
does it also work with the WSJTX clones as long i set the port to 2238 on them and am connected to a hotspot for WRL communication? just because i use MSHV when i go out to a park or a summit because of the ability to have a queue without having to go into fox mode and allow me to set a repeat limit before it goes to the next contact in the queue
@W7AAF ok great! Yes clones should work. I only use JTDX (which in all fairness is just wsjtx) and it works without any issues but im pretty sure most of the clones are sending the QSO broadcast data over UDP the same way WSJTX does so in theory yeah it should work the same. I would test it prior to going out in the field though just to double check