- Messages
- 20,641
- Reaction score
- 15,127
- # of dives
- I'm a Fish!
@wetb4igetinthewater so from what you sent me, here's the "Features" that they claim are different than the Shearwater
wifi-who cares? frankly it's more annoying to connect to wifi computers than bluetooth since you have to usually disconnect from a wifi network to get on there, pointless
wet switch-the shearwaters will activate via pressure switch after several meters so again, what's the point?
LED flashlight-really? the screens are bright enough as is, don't want to deal with a lens on the front that is another major flood point, especially at deep trimix depths.
Status Display LED-why does a wrist computer need a buddy light?
Solenoid driver circuit-Shearwater used to have it with the Predator but has moved it into a separate part of the bus inside the rebreather itself. This is nifty for those that want to go the homebuilt eCCR route which Shearwater has said many times they want nothing to do with, but at the same time, the point of canbus is to have modules. This is going to put everything inside of the one case and at that point there is no point in digital communication because it isn't communicating with anything except itself....
HUD driver circuit-why? the shearwater has the canbus centralized in the rebreathers, where JMI has put it in the handset. This is really useless IMO. Sure in a homebuilt you can have it connect to a HUD, but then if the handset fails you're screwed. In the Shearwater DiveCAN the bus is based inside the head and has separate cables going out to each device which makes it much more robust IMO. Less convenient since you have to put that board/battery either in the head or like Dive Rite did in a separate canister, but still more robust than leaving everything in the handset.
Ambi cable gland-don't have a cable gland yet, but the Shearwaters have buttons on the sides so can easily be used on either arm and are on many commercially available rebreathers
Stack timer-Shearwater has this on the divecan units, just not on the standalones but how can a standalone realistically have a stack timer when it doesn't know when you're on loop or off? either way it's a 30 second firmware update if enough people asked for it
Real time clock with no need to reset time after battery change-the petrel and perdix both do this, and they also sync time with the computer when you download the log
Accelerometer-nifty I guess, but why?
gyro-same the shearwater has a compass, and I really don't need to know what pitch my forearm is
Based on that, they don't do anything meaningful that the Petrel EXT doesn't do already, and some of the things that it does do significantly increase leak potential in the case design with excessive thru hull ports *i.e. why the Shearwaters don't have wet contacts, why bother having 2 extra thru-hull ports when having the pressure sensor turn it on a 2m is sufficient for 99.999999% of use cases*.
Basically this is a fancy Predator controller or AV1, etc. and has a lot of superfluous features that I really don't see any benefit in having....
wifi-who cares? frankly it's more annoying to connect to wifi computers than bluetooth since you have to usually disconnect from a wifi network to get on there, pointless
wet switch-the shearwaters will activate via pressure switch after several meters so again, what's the point?
LED flashlight-really? the screens are bright enough as is, don't want to deal with a lens on the front that is another major flood point, especially at deep trimix depths.
Status Display LED-why does a wrist computer need a buddy light?
Solenoid driver circuit-Shearwater used to have it with the Predator but has moved it into a separate part of the bus inside the rebreather itself. This is nifty for those that want to go the homebuilt eCCR route which Shearwater has said many times they want nothing to do with, but at the same time, the point of canbus is to have modules. This is going to put everything inside of the one case and at that point there is no point in digital communication because it isn't communicating with anything except itself....
HUD driver circuit-why? the shearwater has the canbus centralized in the rebreathers, where JMI has put it in the handset. This is really useless IMO. Sure in a homebuilt you can have it connect to a HUD, but then if the handset fails you're screwed. In the Shearwater DiveCAN the bus is based inside the head and has separate cables going out to each device which makes it much more robust IMO. Less convenient since you have to put that board/battery either in the head or like Dive Rite did in a separate canister, but still more robust than leaving everything in the handset.
Ambi cable gland-don't have a cable gland yet, but the Shearwaters have buttons on the sides so can easily be used on either arm and are on many commercially available rebreathers
Stack timer-Shearwater has this on the divecan units, just not on the standalones but how can a standalone realistically have a stack timer when it doesn't know when you're on loop or off? either way it's a 30 second firmware update if enough people asked for it
Real time clock with no need to reset time after battery change-the petrel and perdix both do this, and they also sync time with the computer when you download the log
Accelerometer-nifty I guess, but why?
gyro-same the shearwater has a compass, and I really don't need to know what pitch my forearm is
Based on that, they don't do anything meaningful that the Petrel EXT doesn't do already, and some of the things that it does do significantly increase leak potential in the case design with excessive thru hull ports *i.e. why the Shearwaters don't have wet contacts, why bother having 2 extra thru-hull ports when having the pressure sensor turn it on a 2m is sufficient for 99.999999% of use cases*.
Basically this is a fancy Predator controller or AV1, etc. and has a lot of superfluous features that I really don't see any benefit in having....