[CA] [CA11] Axiom w/airmar dst800

[DaveE]

A question regarding my new axiom 9... Should it not be able to access depth/speed data from an Airmar dst800 "smart sensor" connected to the NMEA 2000 (raymarine seatalkng) network directly? I don't have a particular need for a full sonar application, so I am not connecting a down vision transducer, but I would like simple depth and speed data available to the Axiom. Is there something I'm missing?

Thanks!

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum Dave,

While it is certainly possible to include a DST800 within a system featuring a MFD running LightHouse 3 software, the system would additionally need to include an i70S MFID to support calibration, offset, and alarms associated with depth, speed, and temperature data from the DST800.

[DaveE]

Thanks, so the i70s would become the "depth source" for the axiom? Is there a better way (ie simpler... cheaper...) way to do this? I just want to supply depth and speed inputs to the Axiom.

Thanks!

[Chuck - Raymarine - Moderator]

Dave,

An alternative would be to install an i40 Bidata System and then interface it to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone via an E22158 SeaTalk to SeaTalkng Converter Kit.

[DaveE]

Thanks, that option may be preferable... though I’m seeing in my research that calibration may not be possible via the i40?

So the dst 800 would remain connected directly to the backbone as a spur, and the i40 would plug into the backbone via the yellow terminal on the adapter kit... meaning I would also need to buy an additional blue backbone cable to add that special converter block to my system ... all correct?

If I go the i70 route, it just plugs directly into the backbone as a spur, as does the dst800?

The system is properly terminated, and if I understand correctly, the backbone is powered from my evoluction AP control unit (ACU-200).

Just to understand the dst 800 a little better.... what does “smart sensor” really mean?

The marketing from Airmar describes: “Depth, speed, and temperature signals are
processed inside the sensor and can be displayed on any radar, chart plotter, or
device that accepts NMEA 0183 or NMEA 2000® data.”

If the data is translated into a NMEA protocol within the instrument and attached as a spur to the backbone, why is the axiom unable to see those inputs?

Thanks again for all the great insight.

[Chuck - Raymarine - Moderator]

Dave,

Q1. I’m seeing in my research that calibration may not be possible via the i40?
A1. Correct.

A2. So the dst 800 would remain connected directly to the backbone as a spur, and the i40 would plug into the backbone via the yellow terminal on the adapter kit... meaning I would also need to buy an additional blue backbone cable to add that special converter block to my system ... all correct?
A2. See the response to Q1. While it is certainly possible to add an i40 Bidata to the system to monitor data, it will not be able to calibrate or configure alarms associated with depth, speed, or temperature via the i40 Bidata.

Q3. If I go the i70 route, it just plugs directly into the backbone as a spur, as does the dst800?
A3. Correct.

Q4. The system is properly terminated, and if I understand correctly, the backbone is powered from my evoluction AP control unit (ACU-200).
A4. While the ACU-200 can provide power to a SeaTalkng / NMEA 2000 which is limited to the autopilot components, it is considered a best installation practice to instead power the SeaTalkng / NMEA 2000 backbone from a switched 12VDC power circuit connected to the supplied SeaTalkng Power Cable which in turn is connected to one of the backbone's spur sockets.

Q5. Just to understand the dst 800 a little better.... what does “smart sensor” really mean?
Q5. Prior to the introduction of 'smart transducers", all instrument transducer were designed to output an analog signal which in turn would be processed and calibrated by an instrument display. The instrument display would then transmit data to other equipment via NMEA 0183, NMEA 2000, or a proprietary communications protocol. Smart sensors are designed with internal microprocessors and transmit calibrated NMEA 2000 or NMEA 0183 data. Such calibration may be performed via an instrument which has been specifically designed to perform such calibrations for a specific make/model of transducer. In the case of some third party products, such calibration may be performed via a computer application provided by the manufacturer of the NMEA 2000 sensor.

Q6. The marketing from Airmar describes: “Depth, speed, and temperature signals are
processed inside the sensor and can be displayed on any radar, chart plotter, or
device that accepts NMEA 0183 or NMEA 2000® data.” If the data is translated into a NMEA protocol within the instrument and attached as a spur to the backbone, why is the axiom unable to see those inputs?
A6. Again, the MFD will be able to repeat whatever value data is supplied to the MFD. However, should the instrument require to have an offset (ex. keel offset, waterline offset, require calibration, or should it be desired to configure an alarm associated with the instrument data, then please note that the MFD's software will not support doing so.