Hi everyone,
I would like to bluntly ask the title question, as I am a rec diver with little experience. The stickies and various posts hint at some rationale behind the refusal of Shearwater, OSTC, xDeep, Liquivision and other tech brands to produce DCs with AI -by AI, I do not mean dying blond hair black-. Why would all your gas tank pressures not be recorded by the DC ? Given the price tag of these brands I guess it would make little difference to add gas integration hardware (for the software part, I have no clue).
I guess that _relying_ on a DC with wireless pressure gauge for your remaining gas is not safe, compared to reading analog gauges. But there are probably a number of solutions to this:
- sell only transmitters that are attached to an analog (mechanical) SPG
- have some analog means of indicating on the SPG that the transmitter battery is low/dead
- no display of gas pressures on the primary screen of the DC in default layout (so that it remains easier to stay safe, grab the SPG and look rather than push buttons on the DC).
My first impression is that the info of breathing rate in the log is valuable. Don't you want to know and learn from your logs how you have reacted to some events like cold, worries, surge on a cliff, cramps, task load, overuse of lungs to adapt to sudden depth/buoyancy change... in terms of ventilation ?
I have already noticed that my console DC is "smoothing" pressure readings and that it is impossible to notice that a valve is not properly open all-the-way; and that it takes too long until the DC wakes up and gives a stable reading during the first surface gas check. But this could be partly fixed in software if I had access (OSTC).
As a side remark, I find that the wireless capabilities of both high end or massmarket DCs are disappointing if compared to all the dirt cheap electronic gizmos. One would expect at the very least some positioning info on buddy (distance, depth diff), using a standard protocol so that it works even if buddy has brand XYZ, and the adoption of bluetooth and usual NFC technologies for linking with PCs & phones.
Anyhow, I would mostly like to read the reasons behind lack of AI, from those who know why they do not want it in their DC.
TIA.
I would like to bluntly ask the title question, as I am a rec diver with little experience. The stickies and various posts hint at some rationale behind the refusal of Shearwater, OSTC, xDeep, Liquivision and other tech brands to produce DCs with AI -by AI, I do not mean dying blond hair black-. Why would all your gas tank pressures not be recorded by the DC ? Given the price tag of these brands I guess it would make little difference to add gas integration hardware (for the software part, I have no clue).
I guess that _relying_ on a DC with wireless pressure gauge for your remaining gas is not safe, compared to reading analog gauges. But there are probably a number of solutions to this:
- sell only transmitters that are attached to an analog (mechanical) SPG
- have some analog means of indicating on the SPG that the transmitter battery is low/dead
- no display of gas pressures on the primary screen of the DC in default layout (so that it remains easier to stay safe, grab the SPG and look rather than push buttons on the DC).
My first impression is that the info of breathing rate in the log is valuable. Don't you want to know and learn from your logs how you have reacted to some events like cold, worries, surge on a cliff, cramps, task load, overuse of lungs to adapt to sudden depth/buoyancy change... in terms of ventilation ?
I have already noticed that my console DC is "smoothing" pressure readings and that it is impossible to notice that a valve is not properly open all-the-way; and that it takes too long until the DC wakes up and gives a stable reading during the first surface gas check. But this could be partly fixed in software if I had access (OSTC).
As a side remark, I find that the wireless capabilities of both high end or massmarket DCs are disappointing if compared to all the dirt cheap electronic gizmos. One would expect at the very least some positioning info on buddy (distance, depth diff), using a standard protocol so that it works even if buddy has brand XYZ, and the adoption of bluetooth and usual NFC technologies for linking with PCs & phones.
Anyhow, I would mostly like to read the reasons behind lack of AI, from those who know why they do not want it in their DC.
TIA.