That’s Pin 9 of the D-SUB connector. It’s serial NMEA data from an approved GPS for continuous location information to be fed to the ELT. It is NOT RF. Absolutely not.
When a 406 ELT is activated, it sends its last known position immediately if a GPS is feeding it data (example: activated by the remote switch in flight prior to an off airport landing) it will continue to update that position data in transmissions sent in the data burst until it no longer receives data from the on-board GPS.
This is how 406 ELTs are light years ahead of their dumb 121.5 “beacon” counterparts. They’re not just “homing” devices. They send their location, as fed from the on board panel GPS as soon as they’re activated. SAR literally travels straight to the position.
They don’t wail like a traditional 121.5 ELT all the time. Their main job is to send a data burst to the satellite on orbit which is relayed to AFRCC. If they have a wail/beacon on 121.5 they do it intermittently in-between data packets at a much much reduced power level. You have to be a lot closer to them to “home in” on them than a traditional 121.5 wailer.
They CAN be installed without a GPS source. But if installed that way they’re not much better than a 121.5 beacon. They’ll transmit the aircraft’s tail number essentially, by transmitting their discreet ELT ID number, which must be registered to the aircraft tail number by the installer or owner. Instructions on how to register are included with the ELT. And their power output as a beacon is reduced and they’re also difficult to home in on the full power data packets without special homing gear due to the less frequent nature of the transmissions.
CAP aircraft with Becker SAR radios as well as USCG with the exact same radio, it can “average” the location and direction in homing mode because it knows the transmission is infrequent, but older left/right antenna and gear can’t easily home directly to a 406 beacon. You have to know how the beacon works to do your own manual averaging and ignore the needle indications when there’s no data packet “blast” present on the frequency. Same with older Doppler DF gear. You’ll just be homing on noise if you pay any attention to the direction indicated when the ELT packet data noise is not being heard by your receiver.
Note: The serial interface on that is one wire. Serial data requires a transmit and a ground. They appear to be using the common airframe ground for both the ground for the data and the ground for the remote activation switch closure. Not my favorite way to do serial data.
I’d make damn sure that the ELT is “copying” the NMEA serial stream from the panel GPS by scheduling a test where the transmitted data burst can be read properly with a proper 406 ELT receiver or worst case, a call to AFRCC. Or however else the manufacturer suggests to test the NMEA input to the ELT. I wouldn’t trust a one wire serial connection with airframe ground to be working without some way to see that the ELT is seeing each 4800 b/sec packet from the GPS and properly decoding it.
There’s probably data on how to test the NMEA serial line somewhere in that doc. I didn’t read all of it. If not, ask Artex how you ensure the serial data from the GPS is being decoded properly by the ELT before letting that thing out of the shop.
A quick Google shows that Artex has a through-the-satellite test function and website for $60 so you can see exactly what the ELT sent during a properly done test that will not trigger SAR or require contact with AFRCC.
http://www.406test.com/overview.aspx
Other information shows...
Once that initial test through the satellite is done, it’s up to the shop doing the annual test if they want to do a proper through-the-satellite test or just a quick listen for the weak 121.5 wail.
It’s recommended to keep tests less than 30 seconds to not have them received and decoded by the satellites.
Technically I’m sure the satellites hear it anyway, they’re just saying AFRCC will ignore transmissions less than 30 seconds.