OSTC over BLE experiences and questions

[Jan Mulder]

On 04-07-17 17:47, Matthias Heinrichs wrote:
> Hi Jan,
> 
> Am 04.07.2017 um 15:23 schrieb Jan Mulder:
>> BT snoop file (made with btmon) is attached. Wireshark is your friend :-)
> 
> The funny stuff happens between Packet #365 and #366 (most likely). 
> Until then, the header (first 256byte) looks quite perfect (A dive from 
> the 2nd July 2017 to 3082mbar max depth, 57min and 26seconds). It's 
> properly closed with the 0xFB, 0xFB at the end.
> 
> Then the first depth sample: 0xcf:0x46:0x00 -> 18127mbar depth (+0x00 
> additional bytes)??!
> Second sample is just as wrong: 0x02:0x90:0x03:... -> 36866mbar depth 
> (+0x03 additional bytes which are non-sense on their own like a manual 
> gas change within the first two seconds PLUS a normal gas change).
> 
> I checked my code and I can't see any difference between sending the 
> header bytes and the profile bytes. Look for "comm_send_dive1:" in 
> https://bitbucket.org/heinrichsweikamp/hwos_code/src/7db10ebae205ebb391cb15fe613a3d8301b87cba/src/comm.asm?at=default&fileviewer=file-view-default 
> 
> 
> Hmm...
> 
> Regards,
>      Matthias
> 
> 

Not sure it is relevant ... dive is made with the OSTC3 in fixed 
setpoint CCR mode. Going to look at your code tonight.

--jan