> I looked into it and on a specific dive the
> headers report a profile size of 0x5ad8 but the
> amount of bytes send for the profile is 0x5ad3
> (including the profile and dive end bytes of
> 0xFDFD) followed by 0x4D.
I looked into it a little more. I wrote some python code to read the data from ...
Search found 2 matches
- 25 May 2015, 08:41
- Forum: OSTC+, OSTC3, cR, sport and OSTC 2 (Mod. 2015 and later)
- Topic: OSTC3 download dives and internal logbook problem
- Replies: 17
- Views: 10592
- 24 May 2015, 06:05
- Forum: OSTC+, OSTC3, cR, sport and OSTC 2 (Mod. 2015 and later)
- Topic: OSTC3 download dives and internal logbook problem
- Replies: 17
- Views: 10592
Re: OSTC3 download dives and internal logbook problem
I didn't have any problems reading the profiles from my ostc3 with version 1.78 but now I've upgraded to 1.80 subsurface cannot download the dives.
I looked into it and on a specific dive the headers report a profile size of 0x5ad8 but the amount of bytes send for the profile is 0x5ad3 (including ...
I looked into it and on a specific dive the headers report a profile size of 0x5ad8 but the amount of bytes send for the profile is 0x5ad3 (including ...