Their server will not accept the Cabrillo file - errors.
First, the log official name should be WA-SALMON-RUN. That has to be changed in the cabrillo file after downloading.
I think we are missing some fields, or incorrect order.
2 Likes
@K4AZE Can you take a look here?
1 Like
@K4ARP Hey David,
Try going into your ‘K4ARP -WA-SALMON-RUN’ logbook and then going to settings → export and then ‘export cabrillo’ and trying to re-export it now. That should export in the proper order now (and with the proper name). Let me know if you are still having issues.
Thanks & 73
Brad K4AZE
2 Likes
Hi Brad,
Still didn’t work.
I have attached the screen shot of the errors.
Now, if I don’t get the log uploaded it is not that big of a deal.
More, that I am trying o help out WRL getting these logs sorted out.
I have done a lot of database and code work and know how picky it can be.
(Attachment ec1b73d2-6a0a-4d61-b185-e40fe743c1bf.pdf is missing)
1 Like
@K4ARP For some reason your screenshot didn’t come through.
When I re-exported the log this morning from your account it has everything in the correct order, unless im missing something
Shoot that updated screenshot over when you get a free min and i’ll take a look and compare.
Thanks for your help!!
Thanks & 73
Brad K4AZE
@K4ARP I’m not really understanding their highlighted errors because here is a snippet of the file i provided a min ago.
…..SOAPBOX:
QSO: 14295 PH 2025-09-20 1807 K4ARP 59 PACIFIC N3EG 59 COW
QSO: 14269 PH 2025-09-20 1810 K4ARP 59 PACIFIC K7SH 59 WAH
QSO: 14261 PH 2025-09-20 1814 K4ARP 59 PACIFIC KA7APR 59 ADA
QSO: 14279 PH 2025-09-20 1820 K4ARP 59 PACIFIC WV7X 59 PIE
…..
you can see the order is correct:
QSO: freq, mode, date, time, yourCallsign, rstSent, sentExchange, theirCallsign, rstRcvd, rcvdExchange
If you open the log that you re-exported/downloaded this morning and then re-sent to them does it look like the above snippet and/or the file i just sent a min ago?
Thanks & 73
Brad K4AZE
Reply front the tech running the contest.
Hi David,
You’re missing the sent location column of the log (your county abbreviation). The log lines should read kind of like a QSO: Freq, Mode, Time, then Sent Call, Sent RS(T), Sent Location, then Received Call, Received RS(T), Received Location.
One of your lines near the end is also missing a frequency.
Cheers,
David T Mullins
david.t.mullins@pm.me
Phone / Text 971-337-0882
1 Like
@K4ARP Hey David Good Morning,
The only thing I can think is that they are kicking it back because you have ‘PACIFIC’ wrote out instead of using the abbreviation for it which is PAC ( County Abbreviations – Salmon Run ). I’ve went into your account and changed the ‘Your exchange’ to be PAC instead of ‘PACIFIC’. Try exporting it now and see if you can submit it because as you can see in the examples above its got all the data in the correct order(s) they are requesting.
Here is the updated file: https://drive.google.com/file/d/1sGVX0XCXj29mGlF3nlq2mGClvTNC465k/view?usp=sharing
i would make sure the header info is correct but it was exported directly from your account.
Thanks & 73
Brad K4AZE
Thanks again for all your help.
One of those things you have to do once to find out what their dBase expects.
For me, I would have had a translation for anyone putting in the county to “Replace” with the abbreviation.
Part of the email I sent back to the salmon run tech.
“OK, we got it.
Your confirmation number is 28smp9wz.wa-salmon-run.
For me it would have been helpful to have the required / optional, expected order, fields in an example, and/or spreadsheet.”
1 Like
@K4ARP of course! So i’m assuming that worked and you were able to submit the log?
On the QSO parties we do have a list of counties that are loaded into the exchange received and sent fields that validate the correct county abbreviation. (see screenshots) however for some reason with this particular one it looks like that wasn’t working as expected.
I’ll get with the team and have it corrected going forward. Let me know if you need anything else!
Thanks & 73
Brad K4AZE
Many thanks Brad.
WRL ream is awsume!!!
Cheers,
David T Mullins
david.t.mullins@pm.me
Phone / Text 971-337-0882
3 Likes