On 2015-11-04 09:51, Paul-Erik Törrönen wrote:
Hmph, did my previous message get caught in the moderation?
No, you only replied to me, and not the mailinglist :-)
Unfortunately I don't have time at the moment to look into adding a new communication backend. Sorry, but maybe you can have a look yourself?
I can give it a shot, although its been close to 20 years since I did anything in C.
Is there any .c-file that could be used as a skeleton code?
You can look at one of the simpler backends, like the cressi leonardo. But the first step will be to figure out how the protocol works, and how to interpret the data. Since it seems to be ascii based, you won't need much coding there.
I checked the draft manual but it was a bit sparse and seemed to be towards adding new models of already supported maker.
The manual is for using the libdivecomputer api, not implementing a new backend.
I quickly ran your logs through my portmon parsing scripts, and it seems the dive computer sends back plain ascii data. The attached *.log file contains the I/O operations, and the *.txt contains the raw data received from the dive computer.
Curious, the data seems to be much less than what the OPOS displays (it had the readings for each tempstick sensors, CO2 sensor data, 3xO2 sensors as well as temperature and depth, 50min sampled each 10s).
Maybe you only captured part of the download? I suggest you keep capturing with portmon for as long as the sentinel application is running.
Jef