![how to get info from petrel to techlog how to get info from petrel to techlog](https://images.coplusk.net/project_images/85360/image/paper_earrings_13_1300003752.jpg)
Since DiveCAN ® devices are independent and mutually suspicious, data logging can be expanded. It has no complex duties and simpler systems are easier to verify and validate. In the case of Shearwater’s typical DiveCAN ® implementation, the module that manages the solenoid is only tasked by reading the sensors and firing the solenoid. Rather than having a monolithic device that calculates decompression, manages a graphical display, monitors sensors and incorporates other functions, devices can be split out into modules.
![how to get info from petrel to techlog how to get info from petrel to techlog](https://i.ytimg.com/vi/5HyKb87gM1c/maxresdefault.jpg)
In life support applications, the modularity can be useful as well. It also allows for backup power schemes and batteries outside the loop powering devices inside the loop. This means that power sources don’t have to be in the same place as power. It is relatively easy to add two more wires and provide power on the bus. There is another benefit that isn’t strictly part of CAN, but is part of DiveCAN ® and many other CAN implementations. This ability to advance along with new technology as it becomes readily available is another key advantage of the DiveCAN ® bus. If new technology comes out, it is relatively easy to just unplug the old device and plug in a new device. If a handset fails, it can be easily replaced in the field. It allows modules to be replaced individually as required. Networking a diving system makes sense for many of the same reasons that networks are used in other applications. In short, it is widely used, simple, and reliable. The connection is digital and error checked which means it is either received correctly, or the error is detected. Finally, CAN was designed to be a platform that would be used to support a message structure like NMEA 2000 or J1939, and that was exactly what we wanted. The protocol handler is built into the hardware of the ARM microprocessors that interest us, and the cable level transceiver handlers are inexpensive and used by the millions in the automotive industry meaning there is no concern of discontinuation. It has predictable latency with high traffic, unlike Ethernet. It allows very long cable lengths for surface control applications. It is suitable for high speed device control like brake-by-wire in cars and turret aiming in tanks. It can operate in very electrically noisy environments like a car or semi-trailer. It is based on the industry standard CAN bus that is widely used for cars, boats, trucks, tanks, and factory networks. DiveCAN ® is a communications protocol consisting of a physical layer and protocol layers. In the end, the extremely robust CAN protocol won. We looked at vehicle protocols like CAN, MilCAN, and NMEA 2000. We looked at process control protocols like DeviceNet and Modbus.
![how to get info from petrel to techlog how to get info from petrel to techlog](https://aapgmukchapter.files.wordpress.com/2017/08/20170721_130815.jpg)
Internet protocols like Ethernet were also considered.
How to get info from petrel to techlog serial#
We looked at basic serial and at higher level serial like HDLC and SDLC as well as microprocessor communication protocols like I2C and SPI. As more digital communication becomes integrated into rebreathers, Shearwater went in search of the best digital solution. Digital communications are clearly replacing analog communications in computer based devices.