...
The Cyclone is aparently an FPGA with Intellectual Property protection features. I'm not sure I would know how to break that with an electron microscope.....
I do, but we're a good distance apart.The EXP GPS module seems to line up with an Inventek Systems ISM-420-R1. See photo markup:
If that is the case, then I should be able to pump a new GPS signal in on PIN 14. It appears to be a UART (serial data) signal. Pins 4 and 5 configure the baud rate and data protocol with the two resistors being pulled low or high.
Does anyone know of a "safe" way to probe pin 14 to confirm it is a serial line?
I don't have an oscilloscope, but maybe someone else does?
Don
Don - You could try making a simple data probe using a 2 volt LED diode and 300 ohm resistor. I don't know how to post a graphic in this text so will refer you to page 9 of the ACK E-04 instillation manual. There is a graphic on that page that shows you how the probe is made. If there is data on that line you want to test the LED will flash. This test won't tell you if the line is "serial data" but it may help you determine if the line is polled data. One would think if the flashing or flickering is repetitive it would suggest a serial data line.Does anyone know of a "safe" way to probe pin 14 to confirm it is a serial line?
That one will, I'm certain, be no better than what's in there -- a cheap, consumer grade GPS receiver with no pedigree whatsoever. Little to no documentation, and no provision for an off-board antenna.https://www.pololu.com/product/2138/specs
would this work for us?
we need to find one approved and where can we find those?
If someone knows how to program we might be able to support this box on our own....
Plus unlock the 1090!
It can be simpler than that. The most time consuming part would be nibbling out a hole to mount a DB9 connector.We would still need a doghouse like addition to do a level shift from UART to RS232, but that is a $20 circuit and some circuit board soldering.
That's my question as well -- whether connecting an acceptable GPS source is enough (very good news) or whether the firmware would need to be tweaked to work with something else (very bad news).I was pondering your work and the following occurred to me: Speaking for the certified ADS600-B NavWorx units, It's my understanding that the 430W needs firmware 5.x, or better, to output 'ADSB+' on its serial lines and that UAT Console 4.1.0, or better, is needed on the NavWorx unit. It's my guess that this is required so that the NavWorx unit can understand the ADSB+' format.
Does anybody know what's so special about the data format of 'ADSB+' that differs from typical NMEA sentences?
Do the other "certified" GPS sources (uAvionics, GRT, etc) output similar data formats?
Can the latest firmware for the EXP unit understand 'ADSB+' data format and for that matter can it understand the data format sentences from the other "certified" units?
Just thought the question should be asked because there appears to be a dependency between the ADS600-B and the 430W units so why wouldn't there be one on the EXP units.
Hi Don,
I was pondering your work and the following occurred to me: Speaking for the certified ADS600-B NavWorx units, It's my understanding that the 430W needs firmware 5.x, or better, to output 'ADSB+' on its serial lines and that UAT Console 4.1.0, or better, is needed on the NavWorx unit. It's my guess that this is required so that the NavWorx unit can understand the ADSB+' format.
Does anybody know what's so special about the data format of 'ADSB+' that differs from typical NMEA sentences?
Do the other "certified" GPS sources (uAvionics, GRT, etc) output similar data formats?
Can the latest firmware for the EXP unit understand 'ADSB+' data format and for that matter can it understand the data format sentences from the other "certified" units?
Just thought the question should be asked because there appears to be a dependency between the ADS600-B and the 430W units so why wouldn't there be one on the EXP units.
I have spoken with Uavionix(SkyFYX), GRT(2020GPS) and Trig(TN72) in regard to output protocols for their respective GPS sources. They have each said their NMEA+ outputs are not compatible with garmins ADSB+ protocol. The best advice I have received to date besides the NexNav mini (which is already allowed by the AD) @$1.9k is a big MAYBE on the Garmin 20A, which retails at $850. They all could be guarding themselves for all I know.Hi Don,
I was pondering your work and the following occurred to me: Speaking for the certified ADS600-B NavWorx units, It's my understanding that the 430W needs firmware 5.x, or better, to output 'ADSB+' on its serial lines and that UAT Console 4.1.0, or better, is needed on the NavWorx unit. It's my guess that this is required so that the NavWorx unit can understand the ADSB+' format.
Does anybody know what's so special about the data format of 'ADSB+' that differs from typical NMEA sentences?
Do the other "certified" GPS sources (uAvionics, GRT, etc) output similar data formats?
Can the latest firmware for the EXP unit understand 'ADSB+' data format and for that matter can it understand the data format sentences from the other "certified" units?
Just thought the question should be asked because there appears to be a dependency between the ADS600-B and the 430W units so why wouldn't there be one on the EXP units.