Logbook memory map - is this normal

[Rob]

Hi,

when i look at the memory map of the dive profile in my ostc there ist something strange.
The documentation say a dive starts with 0xFA 0xFA and ends with 0xFD 0xFD so far so good.

Before the first dive i cleaned my logbook (maybe this is the reason).
The memory dump says
Byte 00267 - 31499 = 0xFF
Then
Byte 31500 0xFD 0xFD
Byte 31502 0xFA 0xFA 0x20 0x06 0x05 0x0B 0x0C 0x01
The real profile ends at the memory end with byte 33034

This is the only profile where the dive ends after 31232 0xFF bytes.

The other dives i have, form a friends OSTC, end at memoryend with 0xFD 0xFD
and at the last position, byte 33034 with 0xFE
and not, as my dive directly before the divestart and
without the 0xFE so i have no last dive?

Maybe im still diving and didn't recognize that.

Both OSTC with version firmware 1.90.

My OSTC
Dive start found at 31502
Date of dive: 05.06.2011
Dive end found at 31500
Lastdive byte 0xFE not found


my friends OSTC
Dive start found at 28430
Date of dive: 09.05.2011
Dive end found at 29266

Dive start found at 29268
Date of dive: 29.05.2011
Dive end found at 30923

Dive start found at 30925
Date of dive: 02.06.2011
Dive end found at 33032
Lastdive byte 0xFE found at 33034

Best regards
Rob

[heinrichsweikamp]

Hallo Rob,

The memory area for the dive profiles is not a 1:1 copy of the physical memory. The download routine searches for 0xFD 0xFD 0xFE (Very unlikely that this sequence is not in your unit if the dive ended normally).
Then it transmits 32768Bytes from address "0xFE+1" (The byte after the 0xFD 0xFD 0xFE sequence). So, the last byte you should get from a unit without any corrupted dives is always 0xFE.

Regards,
Matthias

P.S.: If you're coding a parser currently, a new description with the doubled buffer size (65536 Bytes) will be available soon. We're currently debugging the new format.

[Rob]

Hallo Matthias,

maybe the problem came becaus i have deleted the logbook (reset menu - reset logbook).
The other profiledate i have are also from a brand new N2 with two dives and the initial dive that came with the N2. So this logbook was not resetted and the 0xFD 0xFD 0xFE sequence was where it should be.

You are right, i'm currently implementing a parser.
Please send me the new Description when it is finished ( im also intrested in older descriptions ) I have the one from 01/12/08 latest update 04/10/11 or tell me where i can download it.

best regards
Rob

[heinrichsweikamp]

Hi,

Attached the new description for the coming 1.91beta. Page2 has a checklist for your parser to support all variants of dives that may be available in the memory.
Changes are small:
- 64kB instead of 32kB logbook
- CNS and GF profile data (Extended information)
- SetPoint changes (EventByte,6)
- New dives do have 10Byte extra in the header

The 1.91beta will be available in the next days.

Cheers,
Matthias