When we get reports like this, it invariably turns out to be Chart Plotter or Application that has a problem – usually software related.

The reason for this, is that AIS units do not differentiate between different types of AIS messages; either the regular dynamic ones that include the MMSI number and the position/course/speed of the vessel or the more infrequently transmitted static ones that include the MMSI number, name, dimensions, boat type, etc. and in the case of Class A vessels the voyage data that includes navigation state, destination, ETA, etc.

An AIS unit either receives all of the messages or none. In theory, if the AIS was getting poor reception and missing some messages then because a boat might send 10 dynamic messages for every 1 static message, you are more likely to see the boat without the static data, but it would be random and some boats would have their names. The application only needs to receive the static data once for a target, and then it is in its temporary AIS database for the duration that the application is running.

As I mentioned, the Chart Plotter or Application maintains its own AIS database where it ties together the MMSI numbers in the dynamic and static messages and builds up an AIS target list where every boat should (within 6 minutes) have a name, dimensions, boat type, etc.

The static messages are longer than the dynamic ones and might be split across a couple of UDP network packets. You could try setting the iAISTX to operate in TCP mode and then setup a new Device on the Navionics App; TCP mode, Host = 192.168.1.1 and Port = 2000.

TCP mode is a guaranteed delivery protocol with error checking, packet sorting and re-transmit functionality, that ensures all network packets are always fully received. The downside, is that it is a one device protocol so you cannot have more than one device receiving the data at a time.