On 2015-10-18 20:10, Anton Lundin wrote:
On 18 October, 2015 - "Paul-Erik Törrönen" wrote:
I think you misunderstood me. The universal tool is not a sniffer tool for capturing the communication between the shearwater desktop (SD) application and your petrel. It's a standalone application that will download the dives from your petrel.
This I understand, but...
But unlike the SD application it does use serial communication. Hence
the need to specify the serial
port. Does that make it more clear?
Yes, and hence it requires that the comX is actually present, no?
As I stated previously, there was no comX assigned to the Petrel when I used the SD to download, which led me to assume that the SD does it in some other way.
So to be clear, when I use the universal tool, I need to first configure the Petrel Bt-device to be a serial device, then use that comX-device to do a dump of the dives, yes?
I'll have a go with this next time I get my laptop near one of the rEvos :-)
Great!
Alas, I had a chance to do this just a moment ago, but with no result. I only had about 20 minutes, so what I did was trying the Subsurface (maybe I should really post this on Subsurface-maillist), checking the dump-option:
Latest Subsurface from git on Linux FC 22 with Dell-laptop: The Bt is found, paired, but when I hit download, the DC immediately switches out of the Bt-state with an error message (abrupt command or something therewith). No dump-file.
Latest Subsurface from git on Linux FC 22 with Dell-laptop: Instead of using the Bt-configuration in Subsurface, configure it separately with Blueman to use /dev/rfcomm0 -> Same result as above, no dump-file.
Subsurface 4.5 on Windows 7 with Dell-laptop: Same result as above, no dump-file.
Subsurface 4.4.93 on Windows XP with Compal 91. Ditto
If I used the SD on the Compal XP, then it downloaded everything without a hitch.
I will try to get one unit, or at least the Shearwater-handset borrowed for a full day, to get into this more thoroughly.
The magic trick is that you need to use the Predator protocol to talk with your DC. Over the older Predator protocol we can do memory dumps, which we can't do over the Petrel protocol.
Depending on why you need the memory dump, this is not always a good idea. The legacy predator has some major drawbacks when used with a petrel: The predator protocol can only download a fraction of the petrel's memory (the last 128K out of 16M), so only the most recent dives can be downloaded. And for those dives you loose half of the info, because for each sample you get only the first 10 bytes instead of the full 20 bytes.
So in most cases, it will be more interesting to dump the individual dives, instead of downloading a memory dump with the predator protocol.
Jef