logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

LOGic9's Poor Contest Handling of Florida QSO Party
K4QR
#1 Posted : Sunday, May 15, 2016 9:15:45 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 6
Location: The Villages, FL 32163

Thanks: 1 times
I used LOGic9 (version 9.0.84) to enter, score & export my QSOs for the 2016 Florida QSO Party (held April 30 thru May 1, 2016 UTC). Unless I'm guilty of terrible pilot error (not understanding enough about LOGic9 program), I cannot believe how poorly LOGic9 handles this contest, despite having a built-in contest form for it.

Here's a snippet of LOGic9's export of my QSOs for that contest:

QSO: 14292 PH 2016-04-30 2332 N8SK 2 SUMTER K0HC KS
QSO: 14245 PH 2016-04-30 2339 N8SK 1 SUMTER WA3HAE PA
QSO: 14247 PH 2016-04-30 2350 N8SK 3 SUMTER N1CC TX
QSO: 14219 PH 2016-05-01 0006 N8SK 4 SUMTER K0OO MD
QSO: 14249 PH 2016-05-01 0017 N8SK 5 SUMTER N0QQ CA
QSO: 7181 PH 2016-05-01 0048 N8SK 6 SUMTER AA4PP FL
QSO: 7205 PH 2016-05-01 0056 N8SK 7 SUMTER KI4NBE FL

The Florida QSO Party's contest robot "vomited" all over that exported file when I submitted it.

Here's a snippet AFTER I made extensive (manual) modifications to that log file to make it acceptable to that contest robot:

QSO: 14292 PH 2016-04-30 2332 N8SK 59 SUM K0HC 59 KS
QSO: 14245 PH 2016-04-30 2339 N8SK 59 SUM WA3HAE 59 PA
QSO: 14247 PH 2016-04-30 2350 N8SK 59 SUM N1CC 59 TX
QSO: 14219 PH 2016-05-01 0006 N8SK 59 SUM K0OO 59 MD
QSO: 14249 PH 2016-05-01 0017 N8SK 59 SUM N0QQ 59 CA
QSO: 7181 PH 2016-05-01 0048 N8SK 59 SUM AA4PP 59 FL
QSO: 7205 PH 2016-05-01 0056 N8SK 59 SUM KI4NBE 57 FL

Comparing the two snippets, we see that LOGic (or my pilot error) failed to handle these things properly:

(1) I toggled on "serial number" (as a handy way of counting QSOs); the Florida QSO Party's contest robot did not like its presence;

(2) LOGic9 failed to include the SENT signal report (59) as part of my exchange sent (even though LOGic's contest form had a field for it that I dutifully entered "59"s into); and

(3) LOGic9 failed to include the RECEIVED signal report (59, 57, etc) as part of the exchange the other station sent to me (even though LOGic's contest form had this field and I again dutifully entered the 59 or 57 into it).

Perhaps, LOGic's handling of the Florida QSO Party can be improved before next years (2017) contest. Or, perhaps, someone can instruct me where I went wrong (pilot error) in setting LOGic up for this contest.

73,
Tony/N8SK


Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
WN4AZY
#2 Posted : Wednesday, May 18, 2016 11:44:49 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,061
Man
Location: Auburn, GA

Thanks: 974 times
Was thanked: 485 time(s) in 400 post(s)
Hi Tony:

Sorry for the problems and that you had to do all that manual formatting.

With LOGic, you have complete control over the layout of the exported Cabrillo file. What is needed is a different Cabrillo export template -- either a new one or selecting a different existing template that is in the correct format. This is all documented in Help -- Look under Contesting, towards the bottom of the topic.

Another possibility is that some contests accept ADIF output. That would be easier if it is accepted. Cabrillo isn't really a standard. Every contest could potentially be different -- hopefully the contest sponsor uses the same format as another contest, but they don't have to.

I'll research it and post more later.

Tnx & 73,

Dennis WN4AZY
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.023 seconds.