Page 1 of 1
Printing CFs?
Posted: 23 Jun 2011, 15:32
by PeterK
Does someone knows a software to read and print CFs?
I spend quite some time setting up my OSTC and I'd like to store these for restore in case the settings are lost during firmware update.
Writing on paper is certainly an option but I'd prefer a software solution.
Peter
Re: Printing CFs?
Posted: 23 Jun 2011, 18:12
by Bardass
i use screen copy with my mac
Re: Printing CFs?
Posted: 23 Jun 2011, 23:59
by hexxon
over here, i'm so desperate to get mine that … well
here it is…
http://huexley.free.fr/OSTC_MK2_CF.pdf

its a PDF but you can copy/past the text inside

Re: Printing CFs?
Posted: 24 Jun 2011, 23:11
by PeterK
Dear hexxon
this is a misunderstanding. I want to print MY CFs in order to restore them easily after a firmware update.
Anyway, I appreciate your PDF, this is also very helpful.
Re: Printing CFs?
Posted: 28 Jun 2011, 11:09
by PeterK
In DivingLog there is an option called "WritetoBinary". If turned on there should be a dump file created with all the data read from the OSTC.
I'll check if that file can be opened and read to restore CFs.
Re: Printing CFs?
Posted: 28 Jun 2011, 20:04
by PeterK
I've opened the binary file using a text editor. However, only a few items are readable. Does someone knows a software tool that can read the binary file?
Re: Printing CFs?
Posted: 29 Jun 2011, 07:41
by dmainou
Open the current settings in jdivelog.
highlight the text
ctrl-c
open word
ctrl-v
Re: Printing CFs?
Posted: 29 Jun 2011, 07:42
by dmainou
or simply use a pen and paper to write those non default ones.
Re: Printing CFs?
Posted: 29 Jun 2011, 11:40
by BlupBlup
I've an other tips
I've two OSTC MK2...
I want to have both the same. I've to resynch them after a reset, including if no firmeware update. I connect one to PC. Download parma to JDivelog, then disconnect OSTC without closing JDl and connect the second one and upload param.
Just be carrefull to change the custom text or your ostc will have the same name.
Unfortunatelly I didn't always work when doing firmware update or having different versions. With some version it's completly impossible to upload param from a previous version to the new one. With some other versions it's only partially possible. This is because param format change between versions. You should be very carreful to avoid aving strange stuff when you do that. It's also because of those change that ostc is always reset to default after firmware update.