Subsurface / libdivecomputer performance with Veo 2.0

[Landstander]

I'm a relatively new diver, using subsurface 4.2 on Ubuntu Linux 14.10. One thing I've noticed is that the process of downloading data from my Oceanic Veo 2.0 dive computer is extremely slow. It looks like the cable is just a USB serial converter, so this might be normal, but I'm hoping there are some configuration tweaks which could help.

Any suggestions?

 

[dirkhh]

Define extremely slow... Most of the USB serial converter cables used with dive computers are terrible and the protocols require long waits between accesses. So this may indeed be normal... Iirc with the standard Oceanic protocol you can expect 15-30 seconds per dive, depending on dive computer settings. I don't have a Veo 2.0 but I have experimented with Veo data and a simulator.

 

[bradells]

I'm a relatively new diver, using subsurface 4.2 on Ubuntu Linux 14.10. One thing I've noticed is that the process of downloading data from my Oceanic Veo 2.0 deive computer is extremely slow. It looks like the cable is just a USB serial converter, so this might be normal, but I'm hoping there are some configuration tweaks which could help. Any suggestions?

It will take a few moments to download dives , doesn't matter the software (I'm setup the same, but on a mac.)

I haven't timed it, but usually around a minute or so for a few dives.

BRad

 

[Landstander]

Define extremely slow... Most of the USB serial converter cables used with dive computers are terrible and the protocols require long waits between accesses. So this may indeed be normal... Iirc with the standard Oceanic protocol you can expect 15-30 seconds per dive, depending on dive computer settings. I don't have a Veo 2.0 but I have experimented with Veo data and a simulator.

The last time I used it was for my checkout dives, so 4 dives total (each in the 20-30 minute range) which occurred over the course of 2 days. It took well over 10 minutes to complete the download.

 

[dirkhh]

That's very long.
My initial guess would be either wet contacts or possibly a defective cable.
One thing that will help us figure this out is for you to turn on the log file. There's an option in the download dialog to do that. Send me the logfile and I'll take a look.

 

[Landstander]

OK, I'll try to force a re-download (since there are no new dives stored) with logging enabled after work tomorrow. Thanx!

 

[Landstander]

That's very long.
My initial guess would be either wet contacts or possibly a defective cable.
One thing that will help us figure this out is for you to turn on the log file. There's an option in the download dialog to do that. Send me the logfile and I'll take a look.

I made several attempts last night and today, and to my great surprise wasn't able to reproduce the issue. I've been downloading the day after completing a dive, so at this point I think your suspicion of wet contacts is most likely correct. I'll let you know if it turns up again (without that being the case), but the problem can probably be considered closed in the meantime.

Thanx for your help, and sorry for the inadvertent noise.