forum.heinrichsweikamp.com

I have posted this query on the Divinglog forum as well but maybe someone here can help.

When I try to upload from my OSTC Mk2 to DivingLog5.0
I get the following window:

OSTC ParseHeader2
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

This has never happened before.
The only difference is that I was running the computer in CCR mode and the dives I was trying to download where all CCR dives.

Any advice

David

Sounds like you need to Update Divinglog to the most current (5.0.8?) Version: http://www.scuba-divelog.com/dl50/Divinglog50.exe

Also, which version is running on your Mk.2?

Regards,
Matthias

Updated Diving log 5.0.10 and re installed last stable version, 2.50, onto Mk2
Still had the same problem

Hi David

I had this happening in the past. In this case a custom function was out of range. Try resetting the CF and try to download again. If it still does not work, please enable "WriteToBinary" in the download settings in Diving Log and email me the OSTC.bin file.

Sven

Tried that everything is set back to default settings and Divinglog is now stuck with green progress 95% full and the same error message above, also the message "Writing Binary File" is in the OSTC download window

Found a solution.
I used the downloader option inthe download window and set it for a Mk11 and the dives where downloaded.

Can you see if the binary file is already written to the location form the download settings and send me the file? I think the crash happens while parsing the data, which occurs after writing the binary. The universal downloader works, but it does not transfer as much data as the OSTC downloader.

See attached file. I have just noticed that the universal downloading does noy output all the data
David

Hi David

Thank you, I've found the problem. The dive on March 30 at 11:08 AM has an incorrect start gas byte (254) in the header. I've implemented code to correct that to gas 1 so the import works, but due to the incorrect data it is not clear which was actually the start gas for this dive, so you may have to correct it after the import.

Please download this zip file and extract it into the Diving Log program folder. Then the download should work again. Make sure to check the gas of this dive.

Sven

david tobin Wrote:
-------------------------------------------------------
> Updated Diving log 5.0.10 and re installed last
> stable version, 2.50, onto Mk2

Did you do the dive in question with the latest beta? That would explain it (Betas do not reset the settings - which always may be an issue if the setting is a new one...).

regards,
Matthias

Problem solved - thank you for the help
The dive that caused the problem was done on the latest beta version.
It was my first rebreather training dive and so the time using the computer in ccr mode. I clearly set it up wrong as subsequent dives have been OK.