flight rejected?

I keep getting some of my flights rejected by olc with this message:

IGC-file cannot be read or has wrong format! Please send the file via
eMail to
Error by parsing IGC-File; Error by B-Record:
B2312064540367N12131900WA0019700183LLXNNOREC180SEC _326676154_326675526 ;
For input string: "NNO"

Can anyone explain what is happening? I've sent the files to the olc
help many times but never get any response

Boggs.

On May 8, 10:54*pm, GARY BOGGS wrote:
I keep getting some of my flights rejected by olc with this message:

IGC-file cannot be read or has wrong format! Please send the file via
eMail to
Error by parsing IGC-File; Error by B-Record:
B2312064540367N12131900WA0019700183LLXNNOREC180SEC _326676154_326675526 ;
For input string: "NNO"

Can anyone explain what is happening? *I've sent the files to the olc
help many times but never get any response

Boggs.

Can you view the flight log on using your favorite IGC display
software?

I'd parse the offending item as "NOREC180SEC" which I'd guess
indicates no record for 180 seconds. Just a wild guess though.

IGC file handling varies with the end user software. For example
SeeYou will load a file and display it just fine, but Winscore rejects
it and won't score it. The problem record was found to be:

B2658243351470N11217183WA0420204402+113180218121

That’s a bad time (hour 26).

Don't know if there is any IGC/GFAC specification for error handling,
but perhaps there should be.

Andy

On 9/05/2011 8:17 PM, Andy wrote:
On May 8, 10:54 pm, GARY wrote:
I keep getting some of my flights rejected by olc with this message:

IGC-file cannot be read or has wrong format! Please send the file via
eMail to
Error by parsing IGC-File; Error by B-Record:
B2312064540367N12131900WA0019700183LLXNNOREC180SEC _326676154_326675526 ;
For input string: "NNO"

Can anyone explain what is happening? I've sent the files to the olc
help many times but never get any response

Boggs.

Can you view the flight log on using your favorite IGC display
software?

I'd parse the offending item as "NOREC180SEC" which I'd guess
indicates no record for 180 seconds. Just a wild guess though.

IGC file handling varies with the end user software. For example
SeeYou will load a file and display it just fine, but Winscore rejects
it and won't score it. The problem record was found to be:

B2658243351470N11217183WA0420204402+113180218121

That’s a bad time (hour 26).

Don't know if there is any IGC/GFAC specification for error handling,
but perhaps there should be.

Andy

Its looks to me as though Gary is using a LX Colibri.
The LX Navigation Colibri puts a record such as this in:
LLXNORIGIN0620003137191S11712781E
This records a time and starting location. I have found these in my
files just before the B records start.

I think the offending record in Gary's file is a corrupt record. I think
that the B record should not have the LLXNORE... in it but be on a
separate record. It looks like the start of the LLXNORIGIN record which
has been corrupted.
The REC180SEC_... does not make sense to me.

John O