Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[TG11] Axiom LH3 "own AIS target"
08-16-19, 07:45 PM (This post was last modified: 08-22-19 02:00 PM by Chuck - Raymarine - Moderator.)
Post: #1
[TG11] Axiom LH3 "own AIS target"
Recenty installed AIS transponder (GME AIS120T class B - australia)
onto N2K network connected to Axiom MFDs (x2)
Only one MFD configured as data master.

its all working as expected .. except..
I now see my own boat MMSI/name shown as an AIS target.

I have checked the settings in AIS transponder (using AIS pro2) USB config
tool, all correct. (it correctly shows "all other targets" in its AIS "other targets list")

Likewise I have a standard horizon GX2200E with inbuilt AIS capability (connected via Actisense AIS nmea0183 to n2000 converter)
that I CAN connect to N2K if required. (normally AIS output from this to N2K disabled)

Likewise if i disconnect AIS (GME) transponder from N2K
(but leave it powered up and transmitting as normal)
AND then enable GX2200 to send AIS data to N2K
.. I get the same problem - Axiom displays my own AIS target. (verified the same MMSI as programmed into BOTH GX2200 and AIS120T)

Summary: using either AIS source (but not at same time), the Axiom displays
my own boat as an AIS target. (& hence its impossible to enable AIS alarms etc)

I cannot find anywhere in LH3 to input an MMSI to identify my boat,
and there are no settings in EITHER of the AIS source units to disable this.
Both source units have correct MMSI & KNOW what my own boat MMSI is.

It is not possible to connect AIS source/s to Axiom MFD via 0183 .. for obvious reason.

can you pls advise if ths is a known shortcoming of Axiom LH3 PGN (AIS) implementation
and what you can suggest to correct this.
Find all posts by this user
Quote this message in a reply
08-25-19, 10:04 PM
Post: #2
RE: [TG11] Axiom LH3 "own AIS target"
Hello sunnycoastgreg,

We have previously found and fixed issues with our own AIS transceivers when within range of a shore-based AIS repeater station (see the v1.6 update for AIS650 and v1.05 for AIS700).

It's the job of the specialist device (the AIS transceiver) to know its own vessel and not output that as if it were a valid other-vessel target, rather than have a separate filter within the MFD to receive what appears to be a valid AIS target but to ignore it. The latter is error-prone (another place for a typo or stale configuration if the boat is sold and the MMSI number changes).

I suspect that your AIS transceiver's core hardware/software may come from the same specialist supplier as our own, and they also probably have software updates available to fix this issue. I would contact the manufacturers to get those updates.

Regards,
Tom

Raymarine since 1999.
Interests: Diagnosis of problems in sonar/fishfinders, NMEA2000, ethernet comms, autopilots, thermal cameras
Location: Sydney, Australia.

Please don't PM me asking for direct support, please ask a public question instead so that others can see the question and answer. Forum posts will always be answered before PM requests.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us