Showing posts with label navico. Show all posts
Showing posts with label navico. Show all posts

SRT proprietary AIS commands

My Navico NAIS-300, like most other commercial AIS class B products that have been available for a while, uses the SRT AIS class B OEM board. I know the same board is used in the Raymarine 500, True Heading AIS-CTRX, Transas, Digital Yacht AIT250/1000, and many more. The tell-tale seems to be that the AIS transponder comes with Pro AIS software. I have hooked up a serial data logger so that I could find out what NMEA-0183 commands the Pro AIS software sends to the transponder. Unfortunately neither SRT nor any of the vendors publish the protocol.

My research into this started because I wanted to control my AIS transponder's transmit setting using software. For some reason there are many functions that you can assign to the remote button input, but not a reliable level-style on/off of the transmit functionality. This has been added to recent firmware versions, but mine contains older firmware. However, an hour's worth of analysis shows that controlling the transmitter is actually quite easy. In fact, almost everything that you can set up using Pro AIS is easy as pie to implement.

Basics


The SRT product, logically, uses the 'P' prefix to indicate Proprietary, followed by SRT. Here is an example of a PSRT message:
$PSRT,LED,01*49
Just like all other sentences I document on this page the shown message format is inclusive of the NMEA style checksum bytes at the end of the line, e.g. *49 in the message above.

For some reason some sentences start with a prefix $DUAIQ. I have no theory as to why this is so, maybe the data is intercepted by a different microcontroller.

Authorization

Some sentences require the passing of a password. Luckily, the protocol to do this is very simple -- just send the following sentence before every authorized message:
$PSRT,012,,,(--QuaRk--)*4B

Silent mode

To make the AIS silent (not transmit its own position) send the following authorized (prefix with the command above) sentence:
$PSRT,TRG,02,33*6A

To make the AIS transmit its own position send the following authorized sentence:
$PSRT,TRG,02,00*6A

Alarm mode

To make the AIS output all alarms every minute send the following authorized sentence:
$PSRT,ALM,0000*45

To make the AIS output only the active alarms send the following authorized sentence:
$PSRT,ALM,0001*44

GPS update speed

To make the AIS output GPS data every second send the following authorized sentence:
$PSRT,GER,01*54

To make the AIS output GPS data every four seconds send the following authorized sentence:
$PSRT,GER,00*55

GPS data


The SRT board has a complete GPS on-board. For some reason it only sends out two GPS sentences: RMC and GBS. See the GPSD source for more information on these sentences (as well as those below.)

To get the GPS to send out more GPS sentences send the following authorized sentence:
$PSRT,GPSDATA,,,1*60
This will cause the board to send out VTG, GGA, GSV, GLL and ZDA sentences as well as RMC and GBS. My particular board has a small bug in that it also starts sending out two copies each of the RMC and the GBS commands.

To get it to stop sending the additional GPS messages, send the following authorized command:
$PSRT,GPSDATA,,,0*61



Interrogating the board

There is a whole stack of sentences that can be used to read out system information. These are

LED status
Send: $DUAIQ,LED*29
Recv: $PSRT,LED,a*hh
a bit 1: Power On
a bit 2: TX timeout
a bit 3: Error
a bit 4: SRM status
hh: checksum

Internal data
Send: $DUAIQ,ADC*22
Recv: $PSRT,ADC,a,b,c,d,e,f,g*hh
a: Tx forward power
b: Tx reverse power
c: RSSI Rx 1
d: RSSI Rx 2
e: Internal 3V3 supply
f: Internal 6V supply
g: Supply voltage
hh: Checksum

Boat data
Send: $DUAIQ,SSD*20
Recv: $AISSD,a,b,c,d,e,f,g,h*hh
a: Callsign, 8 bytes fixed length; @ for unused bytes
b: Ship's name,20 bytes fixed length; @ for unused bytes
c: GPS antenna distance from bow, in m
d: GPS antenna distance from stern, in m
e: GPS antenna distance from port side, in m
f: GPS antenna distance from SB side, in m
g: ?
h: ?
hh: Checksum

MMSI
Send: $DUAIQ,010*55
Recv: $PSRT,010,,,c*hh
a: ?
b: ?
c: MMSI

OEM name
Send: $DUAIQ,SRM*28
Recv: $PSRT,SRM,a,b,c*hh
a: ?
b: ?
c: OEM name used in AIS messages, 7 bytes fixed length; unused bytes are filled with @.
hh: Checksum

Vessel type
Send: $DUAIQ,VSD*25
Recv: $AIVSD,a,b,c,d,e,f,g,h*hh
a: vessel type. 36 = Sailing vessel, 37 = Pleasure craft
b: ?, always 00.0
c: ?, always 0000
d: ?, always @@@@@@@@@@@@@@@@@@@
e: ?, always 000000
f: ?, always 00
g: ?, always 00
h: ?, always 00
i: ?, always 00
hh: Checksum

Software version
Send: $DUAIQ,SWF*26
Recv: $PSRT,SWF,a,b*hh
a: AIS software version
b: FPGA version
hh: Checksum

Transponder Serial Number
Send: $DUAIQ,SNO*36
Recv: $PSRT,SNO,a*hh
a: Serial number in ASCII, 10 digits. Usually all 0.

Reset Data Programming

The following command is reputed to reset the AIS back to its factory settings, inclusive of the MMSI number, so that it can be reprogrammed.

$PSRT,RDP*6F

I haven't tried this myself, so I cannot say whether this actually works.

Lowrance yellow Ethernet cabling

The Navico 'yellow' ethernet connector used on new Lowrance devices such as the HDS series has the advantage of being watertight and easy to make a reliable twist-on connection:

Navico Yellow Ethernet connector

In case you want to use a standard Ethernet switch, or have guys lay ethernet cabling through some narrow ducting you cannot use the normal Lowrance Ethernet cabling and have to crimp an RJ-45 jack onto the Lowrance cable.

On opening up the cable I found two twisted pairs of cable, as expected, plus a shield:

Navico Ethernet cable pairs exposed

The pairs are blue and orange. I connected those the same way as a 3 Com sourced very thin Ethernet cable I had lying around: blue to pins 1+2 and orange to pins 3+6 of the RJ-45 jack. This isn't according to either T568A or T568B, but that cannot be helped when the cable pairs are blue and orange. In practice the cable works fine, both when wired directly and when wired to a switch. I don't know whether the is actually a cross over cable or direct through though, so if you use a switch that doesn't do auto MDI-X you may have to swap the pairs.

Here's the crimped connector:

Navico cable to RJ-45 jack

and the final cable:

Finished Navico to RJ-45 Ethernet cable

Once plugged in a quick run of tcpdump revealed the IP address of the Lowrance HDS and a ping proves that my Mac and HDS are able to talk to each other:

PING 169.254.17.126 (169.254.17.126): 56 data bytes
64 bytes from 169.254.17.126: icmp_seq=0 ttl=64 time=0.788 ms
64 bytes from 169.254.17.126: icmp_seq=1 ttl=64 time=0.405 ms
64 bytes from 169.254.17.126: icmp_seq=2 ttl=64 time=0.480 ms

Hurrah, one more item from my to-do list done!

Update


May 2010: Commenters have asked me whether this means they can now interface a HDS or Broadband Radar to their PC. Alas, no. The test done above was just a convenient way for me to test that the munged cable works.June 22, 2010: Yes, you can! Navico has released a SDK that allows navigation software providers to interface with the Broadband Radar. As far as I know, only Expedition has released the necessary software so far (August 2010). For more information see Simrad BR24PC, Free Range BroadBand Radar #2 at Panbo.