On 2017-08-16 11:46, Anton Lundin wrote:
Step one would be some documentation. How to read and write settings
to the computer. Whats the protocol? Which settings are there and how
to
interpret the data.
The information doesn't need to be "public", but the code we write
based
on it will be. As far as I know there is only one manufacturer which
has
public documentation, and thats HeinrichsWeikamp. We have "non public"
documentation from more manufacturers, but its best if Ratio would be
willing to publish their documentation.
I already have access to official documentation from Ratio/Divesystem.
But it only contains information for downloading the dives (which I have
implemented). It does not contain any info on settings or anything else.
Step two would be a device to test it against. It doesn't need to be a
"full production" device, it could just as well be a device that failed
QA for reasons irellevant to program and test the code against. IE
consmetic defects, a couple of dead pixels on the display, uneven
backlight or such.
I don't have a test device either.
Jef
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
