Scott L
Contributor
What is so interesting about post dive log information will always remain a mystery with me.
Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.
Benefits of registering include
Can we try and keep this thread for just posts on the actual work being done on extracting the info we need - it'll help those doing the actual programming and reverse engineering work if they don't have to sift through the extra chatter. This job will possibly be hard enough anyway. We have the whole UEMIS sub-forum available for extra topics.
To those interested in this topic... TnT and I worked on this for a few hours today. Kudos to him for staying up till almost midnight to help me interpret what I see.
First, TnT has figured out a way to get dive data back from the UEMIS web server in what appears to be a reasonable XML format - so at least the dives logged so far should be 'extractable'.
But the actual sync process (needed for an offline sync) is weird, to put it mildly. And as bad as I feared. Basically the USB filesystem is used as a communication tunnel between the web server and the dive computer. The java applet writes requests to a special file ('/req.txt') in the USB filesystem and receives answers from the computer through files in the /ANS directory. It is unclear at this stage what the different requests mean, how exactly they are encoded, if there is some authentication that is needed to unlock the communication, etc.
Laura - any response from UEMIS on their willingness to share documentation of this protocol with the community?