Subsurface & Shearwater Perdix AI

Please register or login

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

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

The Windows build hit a few hiccups, but I was able to make it work. The resultant installer can be found in this Google Drive shared folder.

This build is naturally untested and I hope I'm not stepping on toes by sharing it.

I've tested it quickly on Windows and I'm happy to say it renders the air pressures from the Perdix AI correctly. I've attached a screenshot of a dive profile for reference.

Thank you again the Subsurface developers for an amazing application.
 

Attachments

  • 170912SubsurfacePerdix.jpg
    170912SubsurfacePerdix.jpg
    33.4 KB · Views: 168
This build is naturally untested and I hope I'm not stepping on toes by sharing it.

Minor issue noted after loading the "scuba flag" that marks your dive site(s) from the map get removed. I will test it more thoroughly once I get a dive to log - but it loads and appears to be seamless. Thanks
 
With the "fix" it seems to only pull transmitter 1 (T1) start and end pressure across. It seems to not pull across any T2 start and end pressure. At this point is no better or worse than it was before - I may need to play with SubSurface to see how it works on the RMV/SAC formula.

I did this by deleting my last dive and reapplying the dive in SubSurface...
 

Attachments

  • screenprint of dual transmitter test.docx
    1.1 MB · Views: 144
With the "fix" it seems to only pull transmitter 1 (T1) start and end pressure across. It seems to not pull across any T2 start and end pressure.

Can you send me a sample DB that shows the problem. So far I have only had databases with single sensor, and thus it is not surprising that there are some problems with it. Also the detection of OC/CCR is currently faulty as I have not seen any data from CCR dives to see how this info is actually available in the DB.
 
I'm trying to get both the Windows and Linux builds to build reliably using a Docker container (and automatically upload the resulting builds). I'm struggling a bit with the "googlemaps" dependency.

My dives appear to have continuous air pressure data for both transmitters.

You can find my Shearwater Desktop exported DB here.

The database has a column `currentPPO2SetPoint` in the `dive_log_records` table which probably indicates CCR mode. There's also `currentCircuitSetting` in the same table (I'm guessing "1" for this column means CCR).
 
I'm trying to get both the Windows and Linux builds to build reliably using a Docker container (and automatically upload the resulting builds). I'm struggling a bit with the "googlemaps" dependency.
You sound like you want to contribute to the project. I might suggest you join the Subsurface mailing list subsurface Info Page. You don't need to be a programmer (but great if you are) to make a meaningful contribution. Testing and feedback is very useful.
Your build issue sounds like it's due to the current master requiring a more recent version of Qt (5.9.x) than most distros ship, in order to support the Google earth (replacing Marble) plugin and support BLE downloads on Androud. You may also be interested in Dirk's "daily" (not daily) builds.
 
Can you send me a sample DB that shows the problem.

I sent you a message in Conversation to see if we can work together. Otherwise this thread may fill up with some dribble that others are not interested in...
 
My dives appear to have continuous air pressure data for both transmitters.

You can find my Shearwater Desktop exported DB here.

The database has a column `currentPPO2SetPoint` in the `dive_log_records` table which probably indicates CCR mode. There's also `currentCircuitSetting` in the same table (I'm guessing "1" for this column means CCR).

I am pretty sure 0 on currentCircuitSetting means CCR. At least this method gives CCR in all dives in your log (except the first one). And another log I have results in all dives being correctly OC. I have a patch ready for this and as far as I can tell, this is the way to go...
 
@theBro: Ah, I got confused: I forgot the first dive in the DB was an OC "test dive" by Shearwater.
@elmo: Thanks, I've subscribed to the list and I'll try installing a later version of qt5 in the container :) .
 
The Windows build hit a few hiccups, but I was able to make it work. The resultant installer can be found in this Google Drive shared folder.

This build is naturally untested and I hope I'm not stepping on toes by sharing it.

I've tested it quickly on Windows and I'm happy to say it renders the air pressures from the Perdix AI correctly. I've attached a screenshot of a dive profile for reference.

Thank you again the Subsurface developers for an amazing application.
Hi

I have test this release with a computer installed with Windows 10 Creator Update, it doesn't work with my Perdix AI. :-(

On which version of windows did you do that ?

I'm installing a dual boot with a Linux Mint 18.2 ;-)

Best Regards
 
https://www.shearwater.com/products/teric/

Back
Top Bottom