Suunto Downloader
-
- Posts: 103
- Joined: Fri Dec 08, 2006 05:33
- Location: Alaska, USA
- Contact:
-
- Posts: 103
- Joined: Fri Dec 08, 2006 05:33
- Location: Alaska, USA
- Contact:
Might help. I have one for saleMjorud wrote:I tried it with 2.2.1.22. Have installed 2.2.1.29 now and I still get the same errormessage (when importing the xml file). Have e-mailed the xml to Sven now. Hope he figures out whats wrong...
And maybe I should go get a new interface..
Would you send me the XML file? Please tell me which dives were rejected.
You can run the downloader from the command line if you want or there is a way to save the file from DiveLog also.
Thank you Jon for the file. I checked it and the problem is on dive 13 where the data seems to be corrupt. The error is caused by the incorrect entry time of 1:255
Code: Select all
<DiveData>
<SurfaceIntervalMinutes>255</SurfaceIntervalMinutes>
<SurfaceIntervalHours>255</SurfaceIntervalHours>
<DiveNumber>254</DiveNumber>
<SampleInterval>0</SampleInterval>
<PersonalSetting>0</PersonalSetting>
<AltitudeSetting>0</AltitudeSetting>
<StartingPressure>0</StartingPressure>
<GasMix>0</GasMix>
<FO2>0</FO2>
<StartingAirTemp>254</StartingAirTemp>
<Year>255</Year>
<Month>0</Month>
<Day>255</Day>
<Hour>1</Hour>
<Minute>255</Minute>
<DiveProfile>
<Datum>0</Datum>
<Datum>0</Datum>
<Datum>-1</Datum>
<Datum>0</Datum>
Error Reading XML file
I have a similar problem.
Get the message "Error Reading XML file". I sent the XML file to you Sven and James.
I use the latest SuuntoDownload 2.2.1.29 with Suunto USB cable.
/Erik
Get the message "Error Reading XML file". I sent the XML file to you Sven and James.
I use the latest SuuntoDownload 2.2.1.29 with Suunto USB cable.
/Erik
Hi Erik
In your case the problem is the "Personal Info" setting of your Suunto and because the XML file is saved as ANSI file and not as true UTF-8 file. To fix your problem quickly, you must change in the personal info of your Suunto with the Suunto Dive Manager the word "Göran" to "Goeran" (to replace the "ö"). Then it should work.
James, I just saw that the XML file is saved as ANSI file (although the encoding in the first line says UTF-8 ). You can see this if you open the file in Notepad and choose "Save as". This is no problem as long as no special characters are in the file, like in this case. But I think the only way this can happen is via the personal setting field.
Sven
In your case the problem is the "Personal Info" setting of your Suunto and because the XML file is saved as ANSI file and not as true UTF-8 file. To fix your problem quickly, you must change in the personal info of your Suunto with the Suunto Dive Manager the word "Göran" to "Goeran" (to replace the "ö"). Then it should work.
James, I just saw that the XML file is saved as ANSI file (although the encoding in the first line says UTF-8 ). You can see this if you open the file in Notepad and choose "Save as". This is no problem as long as no special characters are in the file, like in this case. But I think the only way this can happen is via the personal setting field.
Sven
-
- Posts: 103
- Joined: Fri Dec 08, 2006 05:33
- Location: Alaska, USA
- Contact:
OK, Sven. I'll try to fix it. The compiler reports it as UTF-8, so I'm not sure where to start looking - but I'll think of something. I'm not sure I'll produce a fix in the current version though, I'm hip deep in the D model upgrade.divinglog wrote:James, I just saw that the XML file is saved as ANSI file (although the encoding in the first line says UTF-8 ). You can see this if you open the file in Notepad and choose "Save as". This is no problem as long as no special characters are in the file, like in this case. But I think the only way this can happen is via the personal setting field.
Sven
Thanks!divinglog wrote:Hi Erik
In your case the problem is the "Personal Info" setting of your Suunto and because the XML file is saved as ANSI file and not as true UTF-8 file. To fix your problem quickly, you must change in the personal info of your Suunto with the Suunto Dive Manager the word "Göran" to "Goeran" (to replace the "ö"). Then it should work.
Sven
-
- Posts: 103
- Joined: Fri Dec 08, 2006 05:33
- Location: Alaska, USA
- Contact: