AIS 650 - STNG Output Not Working, NMEA Does.

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum Wimpress,

Q1) Is this a Software or a Hardware glitch?
A1) Based upon the information provided, one or more of the following may be responsible for reported issue:
- failure to interface the MFD and AIS650 to one another via a powered and properly terminated SeaTalkng backbone
- the SeaTalkng bus is not powered (verify that the SeaTalkng bus has been powered form a switched 12 VDC power circuit located at the approximate mid-point of the backbone's LEN load)
- early software within the AIS650 (should the AIS650's software have been updated prior to disconnecting the AIS650 from the SeaTalkng backbone, then this may be ruled out)
- failure of the MFD's SeaTalkng port (should other devices which have been interfaced to the SeaTalkng backbone be communicating with the MFD, then the MFD's SeaTalkng port would be deemed to be operational)
- failure of the AIS650's SeaTalkng port

Q2) In the AIS or the display?
A2) See the response above. Fault isolation may be performed by interfacing the MFD to another compatible device having a SeaTalkng communications interface.

Q3) Can I just hook up AIS IN to the #3 NMEA 0183 port on the E140 at 4800 baud (and save a bi-directional port)?
A3) Doing so will prohibit the MFD from controlling the AIS650's Silent Mode state.

Q4) What would I lose in using 4800 baud and in not having AIS OUT back to the AIS?
A4) Due to the high volume of data associated with communications of AIS data, Raymarine's AIS recievers, as well as those of most other manufacturers, exclusively support NMEA 0183 communications at 38400 BAUD.

Q5) Most importantly, can I trust the AIS unit's reliability in the future, or should it be returned and repaired?
A5) Should the AIS650 still be within it warranty period, then it is recommended that it be serviced prior to the end of its warranty period. That said, failure of the AIS650's SeaTalkng communications circuitry (assuming no other damage the AIS650) should have not effect upon its NMEA 0183 communications.