BB1
Contributor
Hi,
Hopefully Scubacastor, DirkHH and others will kick in here as well as they obviously know more about this than me.
I had a chat to a dive buddy tonight who is a java developer amongst other things (handy!)
He said - and these are excerpts from a skype conversation - the following:
not encyrpted - the class files can be decompiled
all the project/code is in there
java code/classes are "compiled" into .class file
Use 7zip to open the jar file
Then use this program to decompile the class files
If you try this at home do it on a COPY of your SDA files!!!!
Now it gets more interesting:
it's all stored on the dive computer
the sync gets the username/password from the computer and uses that for the sync
the data will be transferred in bytes not readable ascii/utf8 text etc
Then in reference to Scubastor's post: all the code to access the SDA memory is visible in sdasync.jar (start renomming *.jar into *.zip, open the file you'll get all compiled and easy to decompile - done it - bits of code to access the memory). he said this: yeah looks pretty straight forward
So I asked the current million $ question: so do you think its possible to get at the dive log info??
And he came back with:
for sure - just use the existing usb communction classes and dump the output to what ever you like. That jar has a built in http server that does the front end communication with the sync. Also looks like a tunnel (ssl) to send the data back to the web servers.
OK coloured text to hopefully show who the comments were from is making this easier to read and follow.
I also sent a big email to Sven at Diving Log 5.0 asking what format he would need to info in to be able to import into his program as that would satisfy my needs completely:
Here what was emailed:
Trying to find out if we can use your program to upload dives from our UEMIS SDA dive computers.
UEMIS unfortunately went into liquidation 3 days ago leaving many owners with no way to download our dives once the UEMIS servers are taken down.
Thankfully some helpful friends have been looking at the java files and decompiled them to show how the information is being synchronised out of them.
Quoting him now \"just use the existing usb communction classes and dump the output to what ever you like.\" then \"that jar has a built in http server that does the front end communication with the sync\".
So with this in mind, what format is required by your software to be able to import dive information.
I have over 150 dives in my computer and online at UEMIS including technical dives which I really don't want to lose!!
I'll update this if or when I get a reply from Sven and if I can get anymore info from my friend about how to export/extract the divelog info.
I'm guessing the file format needed will be .xml from earlier posts by others??
Feel free to add info, point out problems or assist as this will help us all!
Hopefully Scubacastor, DirkHH and others will kick in here as well as they obviously know more about this than me.
I had a chat to a dive buddy tonight who is a java developer amongst other things (handy!)
He said - and these are excerpts from a skype conversation - the following:
not encyrpted - the class files can be decompiled
all the project/code is in there
java code/classes are "compiled" into .class file
Use 7zip to open the jar file
Then use this program to decompile the class files
If you try this at home do it on a COPY of your SDA files!!!!
Now it gets more interesting:
it's all stored on the dive computer
the sync gets the username/password from the computer and uses that for the sync
the data will be transferred in bytes not readable ascii/utf8 text etc
Then in reference to Scubastor's post: all the code to access the SDA memory is visible in sdasync.jar (start renomming *.jar into *.zip, open the file you'll get all compiled and easy to decompile - done it - bits of code to access the memory). he said this: yeah looks pretty straight forward
So I asked the current million $ question: so do you think its possible to get at the dive log info??
And he came back with:
for sure - just use the existing usb communction classes and dump the output to what ever you like. That jar has a built in http server that does the front end communication with the sync. Also looks like a tunnel (ssl) to send the data back to the web servers.
OK coloured text to hopefully show who the comments were from is making this easier to read and follow.
I also sent a big email to Sven at Diving Log 5.0 asking what format he would need to info in to be able to import into his program as that would satisfy my needs completely:
Here what was emailed:
Trying to find out if we can use your program to upload dives from our UEMIS SDA dive computers.
UEMIS unfortunately went into liquidation 3 days ago leaving many owners with no way to download our dives once the UEMIS servers are taken down.
Thankfully some helpful friends have been looking at the java files and decompiled them to show how the information is being synchronised out of them.
Quoting him now \"just use the existing usb communction classes and dump the output to what ever you like.\" then \"that jar has a built in http server that does the front end communication with the sync\".
So with this in mind, what format is required by your software to be able to import dive information.
I have over 150 dives in my computer and online at UEMIS including technical dives which I really don't want to lose!!
I'll update this if or when I get a reply from Sven and if I can get anymore info from my friend about how to export/extract the divelog info.
I'm guessing the file format needed will be .xml from earlier posts by others??
Feel free to add info, point out problems or assist as this will help us all!
Last edited: