BlueDefender
Member
I'm working on a project where I would like to get AIS data into a NavNet-VX2 via the Network port (DATA2 is in use) using my own AIS source rather than an FA-30.
From poking around, I understand that the FA-30 runs on static IP 172.31.24.2 and emits AIS sentences in a UDP packet broadcast to 172.31.*.* on port 10021.
Here is an example of a UDP packet payload sent by the FA-30
01 12 00 01 00 00 00 00 21 41 49 56 44 4d 2c 31 2c 31 2c 2c 42 2c 31 33 60 65 3f 35 50 50 31 3a 50 46 77 35 54 4d 73 3f 4b 57 30 67 77 32 52 36 49 38 2c 30 2a 33 39 0d 0a 21 41 49 56 44 4f 2c 31 2c 31 2c 2c 2c 31 3e 71 63 36 36 3f 50 3f 77 3c 74 53 46 30 6c 34 51 40 3e 34 3f 77 70 30 50 30 30 2c 30 2a 32 39 0d 0a
The packet payload has two parts:
1. A Furuno-specific preamble (in underline)
2. AIS sentence(s) in ASCII format (in bold)
For the curious - the AIS sentence in this case translated from Hex to Ascii is:
!AIVDM,1,1,,B,13`e?5PP1
Fw5TMs?KW0gw2R6I8,0*39
!AIVDO,1,1,,,1>qc66?P?w<tSF0l4Q@>4?wp0P00,0*29
I have a couple of questions for Furuno tech gurus:
1. If my device were to broadcast UDP packets onto the network on port 10021 that contained JUST part 2 (an ASCII AIS sentence), will the NavNetVX-2 be able to parse them in addition the the more proprietary payload? (ie. does the VX2 work with any non-Furuno AIS sources on the network)
2. If not, are there any details on the preamble format so that given a valid AIS sentence I could generate the preamble for it.
[Update - after a little more traffic sniffing it appears that of the 8-bytes that are Furuno specific, the second byte is a sequence-counter that wraps when it hits 0xFF, and the rest of the bytes are unused or static and don't seem to relate to the AIS payload. It would be nice to see any info on this though to ensure I'm not missing something before experimenting on my VX2. ]
From poking around, I understand that the FA-30 runs on static IP 172.31.24.2 and emits AIS sentences in a UDP packet broadcast to 172.31.*.* on port 10021.
Here is an example of a UDP packet payload sent by the FA-30
01 12 00 01 00 00 00 00 21 41 49 56 44 4d 2c 31 2c 31 2c 2c 42 2c 31 33 60 65 3f 35 50 50 31 3a 50 46 77 35 54 4d 73 3f 4b 57 30 67 77 32 52 36 49 38 2c 30 2a 33 39 0d 0a 21 41 49 56 44 4f 2c 31 2c 31 2c 2c 2c 31 3e 71 63 36 36 3f 50 3f 77 3c 74 53 46 30 6c 34 51 40 3e 34 3f 77 70 30 50 30 30 2c 30 2a 32 39 0d 0a
The packet payload has two parts:
1. A Furuno-specific preamble (in underline)
2. AIS sentence(s) in ASCII format (in bold)
For the curious - the AIS sentence in this case translated from Hex to Ascii is:
!AIVDM,1,1,,B,13`e?5PP1
Fw5TMs?KW0gw2R6I8,0*39!AIVDO,1,1,,,1>qc66?P?w<tSF0l4Q@>4?wp0P00,0*29
I have a couple of questions for Furuno tech gurus:
1. If my device were to broadcast UDP packets onto the network on port 10021 that contained JUST part 2 (an ASCII AIS sentence), will the NavNetVX-2 be able to parse them in addition the the more proprietary payload? (ie. does the VX2 work with any non-Furuno AIS sources on the network)
2. If not, are there any details on the preamble format so that given a valid AIS sentence I could generate the preamble for it.
[Update - after a little more traffic sniffing it appears that of the 8-bytes that are Furuno specific, the second byte is a sequence-counter that wraps when it hits 0xFF, and the rest of the bytes are unused or static and don't seem to relate to the AIS payload. It would be nice to see any info on this though to ensure I'm not missing something before experimenting on my VX2. ]
