What's new
Van's Air Force

Don't miss anything! Register now for full access to the definitive RV support community.

Garmin G5 CAN bus protocol

Status
Not open for further replies.

rocketbob

Well Known Member
I recently did an upgrade installing two G5's, a GMU-11, and a Val avionics Nav 2000 which talks to the two G5's nicely via RS-232. Only problem is the lack of extra serial ports to hook up legacy GPS's. Curious if one could roll together a LRU with an Arduino on the CAN bus to add additional inputs to the G5's that would be menu selectable. Sort of like the GAD29 but to be able to switch to an NMEA source via the CAN bus adapter I would make. Is it possible to get the Garmin CAN bus protocol docs to do something like this?
 
I recently did an upgrade installing two G5's, a GMU-11, and a Val avionics Nav 2000 which talks to the two G5's nicely via RS-232. Only problem is the lack of extra serial ports to hook up legacy GPS's. Curious if one could roll together a LRU with an Arduino on the CAN bus to add additional inputs to the G5's that would be menu selectable. Sort of like the GAD29 but to be able to switch to an NMEA source via the CAN bus adapter I would make. Is it possible to get the Garmin CAN bus protocol docs to do something like this?

I am afraid that would be very proprietary. Never seen that protocol in the public (or in private for that matter).
 
CANbus

The CAN bus is able and then some, most of my aircraft's body systems are on a twin CANbus including a few serial streams. Outside of AIRINC 825 and the older CANaero standards there isn't much defined stuff for small AC.
The impossible hill to climb however would be Garmin opening up their protocol.
 
G5 CAN Bus

Hi,

I plan to install a G5 on my RV8. But I have to interface it with a KX165 for VOR signals. I plan to use an arduino for that. I can't use the serial port because I'm going to use it for another function. Have you been able to get information about the G5's CAN interface?

Regards
Herv
 
can CAN

Seized by the same curiosity as Bob, and for the same reason.

I don't believe Garmin is doing any crypto or other obfuscation on the CAN bus, though its possible. They just don't want things mucked up by civilians, so they don't publish. The RS232 protocol for the G5 nav input, for example, is rather straightforward.

Discovering the traffic on the CAN bus should be pretty straightforward as well with the right equipment. Maybe some sniffing is in order. Others of the same bent can have a look and post anything interesting.

ron
 
Last edited:
Seized by the same curiosity as Bob, and for the same reason.

I don't believe Garmin is doing any crypto or other obfuscation on the CAN bus, though its possible. They just don't want things mucked up by civilians, so they don't publish. The RS232 protocol for the G5 nav input, for example, is rather straightforward.

Discovering the traffic on the CAN bus should be pretty straightforward as well with the right equipment. Maybe some sniffing is in order. Others of the same bent can have a look and post anything interesting.

ron

Interesting discussion.

I have a Rigol MSO5104 scope (and a Saleae logic analyzer, for that matter) that I believe will decode the CAN protocol. That might be an interesting experiment, although it would obviously require buying a Garmin unit.

Not the end of the world...

TB
 
hello
I'm going to buy a G5 this fall. I have the possibility to use a CAN frame analyzer so I will be able to try to see if there is a similarity with the NMEA2000 or other.....
 
I have a Salae Logic and a G5. I?ll hook it up and see what type of data is coming through. I?d love to get baro into the G5 directly from the Efis. It would be best though to check the comm between the G3x and G5. I?ll be happy to loan my logic analyzer if someone wants to do that.
 
Type this into Google:

investigating CAN bus network integrity in avionics systems

This is one of the strangest papers I have come across in my Avionics career. It investigates the (quite obvious) vulnerability of the CAN bus to a physically connected attacker (of course the same goes for just about anything used in an aircraft today).
Anyway they "reverse engineered" parts of our CAN bus protocol (we had to laugh at this - we put all that in the public domain long ago, all they had to do is download the protocol document from our website).
Anyway - they also had a go at our friends from Garmin, you may find their findings enlightening.

Regardless of Garmin or us - OK to listen to the CAN bus but be very careful sending anything on the CAN bus if you do not have the full picture of how it is implemented - you can quite easily cause havoc unintentionally. Message rates and timing may be of importance and this is not obvious. Also you may think you can use "unused" addresses for your own purposes - but these may be used by the receivers and you would never know.

Rainier
CEO MGL Avionics
 
I just started doing an install of a dual G5/GMU11/GAD29B/175 system in a certified aircraft. I have an inexpensive canbus logger I've used to log canbus messages on a car project of mine and plan to do some logging to see if I can make sense of the packets.
 
Helo Rocketbob,
Have you been able to do some analysis on the G5 CAN link?
Regards
Herv?

I can chime in here. I have 2 G5s, a GMU-11 and GAD-13. I hooked up a cheap $100 CAN bus analyzer from Amazon and observed. The packet protocol is fairly straightforward, easy to reverse engineer, and has no encryption or obsfucation. Here's a little bit of useful data that I located, mostly specific to the G5. When I characterize more of the GMU-11 and GAD-13 packets, I'll post a more complete and properly-formatted write-up.

---------------------------------

* AHRS data packets transmitted at 50Hz, CAN ID 18882100. Packets start with 0xDD00. Pitch, roll, raw gyro and raw accelerometer data are in 32-bit floating point format starting at packet byte 20.

* Pitot/Static data packets at 10Hz, CAN ID 18882100, packet starts 0xDD0A. IAS, TAS and pressure altitude are at byte offsets 4, 8, 16.

* Any time the G5 knobs are used to change a value, the updated value is sent in a packet with CAN ID 10882200 and packet header 0xEA65, new value in floating point at byte offset 3. Byte #2 indicates what is being changed:
0: altimeter setting in millibars
2: altitude bug
3: user pitch adjustment
4: VLOC course/OBS
5: heading bug

Angles/headings are always radians, speeds in meters/sec, altitudes in meters, pressures in millibars.
 
Awesome! I never did get around to doing this other than making an easy way to plug into the canbus wires. What can usb adapter are you using? Wireshark?
 
hello Cowlove,
Last week I spied CAN traffic between my G5 and GMU11. I get this file style:
1479.1632;RX;411574272x;8;1;0;1;0;60;0;186;83;
1479,1632;RX;411574528x;8;221;0;56;0;3;100;0;0;
1479,1632;RX;411574528x;8;78;114;11;0;254;183;1;8;
1479,1632;RX;411574528x;8;194;45;156;64;61;188;227;190;
1479,1633;RX;411574528x;8;134;130;56;186;202;175;83;185;
1479,1643;RX;411574528x;8;109;108;134;192;84;213;16;191;
1479,1642;RX;411574528x;8;224;91;122;191;129;252;151;186;
1479,1642;RX;411574528x;4;0;16;74;188;;;;;;
I can't correlate with your observations.
Can you give me an example of your CAN? traffic with interpretation?
Thank you very much.
 
Ok, I'm sleeping again !!!!! :):)

411574528x = 18882100hex
And I see in my second frame data begin with 221;0 witch is 0XDD en hex.....

So, for exemple with this frame:
1479,4122;RX;411574528x;8;221;10;48;0;68;115;11;0;
1479,4122;RX;411574528x;8;29;2;0;0;104;97;141;62;
1479,4122;RX;411574528x;8;230;235;97;63;54;118;16;59;
1479,4123;RX;411574528x;8;85;134;31;67;96;108;95;65;
1479,4132;RX;411574528x;8;96;108;95;65;0;0;0;0;
1479,4132;RX;411574528x;4;11;221;45;61;;;;;

IAS was 0;68;115;11 ? (44730B in Hex)
 
My value last year:

-----id------- DLC B0 B1 B2 B3 B4 B5 B6 B7 Read Value --------- FUNCTION
0x10882200 007 E4 65 00 00 00 DA C5 00 1013 --------- altimeter setting in millibars
0x10882200 007 E4 65 00 00 38 C7 47 00 1020 --------- altimeter setting in millibars

0X10882200 007 E4 65 02 0A D7 F3 41 00 100 --------- altitude bug
0X10882200 007 E4 65 02 0A D7 73 42 00 200 --------- altitude bug
0X10882200 007 E4 65 02 67 66 98 43 00 1000 --------- altitude bug

0X10882200 007 E4 65 03 88 C3 64 3B 00 0,2 --------- user pitch adjustment
0X10882200 007 E4 65 03 88 C3 E4 3A 00 0,1 --------- user pitch adjustment
0X10882200 007 E4 65 03 88 C3 E4 BA 00 -0,1 --------- user pitch adjustment

0X10882200 007 E4 65 05 00 FB 0E BD 00 358 --------- heading bug
0X10882200 007 E4 65 05 00 FC 8E BC 00 359 --------- heading bug
0X10882200 007 E4 65 05 00 00 00 00 00 360 --------- heading bug
0X10882200 007 E4 65 05 35 FA 8E 3C 00 1 --------- heading bug
0X10882200 007 E4 65 05 35 FA 0E 3D 00 2 --------- heading bug
0X10882200 007 E4 65 05 50 77 56 3D 00 3 --------- heading bug
0X10882200 007 E4 65 05 35 FA 8E 3D 00 4 --------- heading bug
0X10882200 007 E4 65 05 DB 0F C9 3F 00 90 --------- heading bug
0X10882200 007 E4 65 05 DB 0F 49 C0 00 180 --------- heading bug
0X10882200 007 E4 65 05 DC 0F C9 BF 00 270 --------- heading bug
 
other value not decoded :
0x18882100 0xDD 0x00 0x38 0x00 0x03 0x64 0x00 0x00
0x18882100 0xD4 0x74 0x9C 0xBF
0x18882000 0x01 0x00 0x01 0x00 0x14 0x00 0xB1 0x18
0x18882100 0x00 0x00 0x00 0x00
0x18882000 0x01 0x00 0x01 0x00 0x3C 0x00 0xCC 0x14
0x18882100 0xB5 0x7D 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882100 0x00 0x20 0xDF 0x3B
0x18882100 0xA1 0x7D 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882000 0x01 0x00 0x01 0x00 0x3C 0x00 0x39 0xB3
0x18882100 0xDD 0x00 0x38 0x00 0x03 0x64 0x00 0x00
0x18882100 0x00 0xE8 0xE8 0x3B
0x18882000 0x01 0x00 0x01 0x00 0x34 0x00 0xDB 0xD0
0x10882000 0x01 0x00 0x01 0x00 0x10 0x00 0x01 0xF7
0x108A2222 0xE4 0x73 0x09 0x00 0x00 0x00
0x18882100 0x00 0x08 0xA3 0x3B
0x18882100 0xC9 0x7D 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882000 0x01 0x00 0x01 0x00 0x3C 0x00 0x08 0xF4
0x18882100 0xDD 0x00 0x38 0x00 0x03 0x64 0x00 0x00
0x18882100 0x00 0xD0 0xB0 0x3B
0x18882100 0xF1 0x7D 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882000 0x01 0x00 0x01 0x00 0x3C 0x00 0xA3 0x3A
0x18882100 0xDD 0x00 0x38 0x00 0x03 0x64 0x00 0x00
0x18882100 0x00 0x40 0x1C 0xBA
0x18882100 0x05 0x7E 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882000 0x01 0x00 0x01 0x00 0x3C 0x00 0xA8 0x66
0x18882100 0xDD 0x00 0x38 0x00 0x03 0x64 0x00 0x00
0x18882100 0x00 0xE0 0xF9 0xBA
0x18882100 0x19 0x7E 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882000 0x01 0x00 0x01 0x00 0x3C 0x00 0x9C 0x82
0x18882100 0xDD 0x00 0x38 0x00 0x03 0x64 0x00 0x00
0x18882100 0x00 0x60 0x43 0x3B
0x18882100 0x2D 0x7E 0x0B 0x00 0xFE 0xB7 0x01 0x08
0x18882000 0x01 0x00 0x01 0x00 0x34 0x00 0xD8 0x1A
0x10882200 0xDC 0x0C 0x00 0x00 0x00 0x00
 
Awesome! I never did get around to doing this other than making an easy way to plug into the canbus wires. What can usb adapter are you using? Wireshark?

I'm using a microchip APGDT002 usb can bus analyzer with "candump" on ubuntu. I got it because it was the cheapest one on Amazon Prime. It's garbage. It drops quite a bit of data at the data rates garmin uses.

A $10 ESP32 microcontroller with a $5 can bus transceiver works 100% better, zero garbled data.

I mostly wanted to get AHRS and heading/alt bug data out of the G5, but may investigate further and see if an open source, $20 alternative to the GAD13 is feasible.
 
hello cowlove
Thank you very much for all this information. For my part, the goal is to make an interface with an arduino between my G5, KX155 (VOR) and PA TrueTrak (for Alt and heading bug).
With your information, the link with the truetrak is on the right way ...
Regards
 
hello
Has anyone been able to make recordings of the CAN frames emitted by GAD29?
I am looking for the GAD29 identifiers and the frames corresponding to the VOR/LOC/GLIDE indications...I have started a table of G5, GMU11 and GDU375 identifiers and data ....
Regards
 
I have connected a CAN logger to my system:
GDU-460
GMA-24R
GTN-750XI
GAD-29
GEA-24
GSU-25
Two GSA-28's
I have powered each, 1 at a time, onto the Bus and sniffed traffic for about a minute.
I did not have the GTN installed when I tried the GAD ... in that mode it did not send anything. Although when I turn on the GDU, it indicates via messages that inputs for the GAD are missing. So there is some LRU to LRU communication going on that I missed ... I may have also missed some power on messages ... because I logged AFTER the device was turned on ... I need to go back and sniff the startup trafic.

I have categorized the CAN IDs and various DLC for each ID, for each device powered onto the bus, but have not looked at the actual data bytes for each CAN packet yet.
I would like to categorize the individual devices before I start connecting multiple devices at the same time and start seeing the LRU to LRU messaging.

I would be interested in what you have been able to learn about reading some specific parameters ... might provide insight in larger classes of parameters.
 
Hi,
good morning,
I can send you my xls file in which I analyzed the frames of the G5, GDU470 and GMU11. There are the identifiers and the data that I could extract (HDG, Altitude, Pitch, roll, Hdg bug....). If you could send me your frame logs, it would be nice...
Regards
Hervé
 
Last edited:
Hello
I am reactivating this tread because I am always looking for information on CAN messages...
If someone was able to make recordings of the frames.... :)
Regards
Hervé
 
Hello all, Im trying to decode GEA24 messages to be able display them in a different system. If I have results will post them.
Regards,
Maximo.
 
You guys do know that the G5 has a well-documented RS-232 output format with all the important data already on it, right? The specifications are right there in the manual.
 
You guys do know that the G5 has a well-documented RS-232 output format with all the important data already on it, right? The specifications are right there in the manual.

I think why Bob started this thread way back there, he was using the two available serial ports for duplex coms with the Val Nav 2000 and was looking for some way to get another NMEA GPS's data into the dual G5 setup at the same time.

I think this is what he had setup (sub the Val for the SL30):

g5.PNG

I believe this is what sent him down the trail of trying to figure out how to use the CAN bus to add additional GPS NAV sources.
 
Hello Maximo,
if you already have CAN frame recordings, I can help you decode them.
I've already done this type of analysis for frames transmitted by the G5 and GMU11.
Regards
Hervé
 
Hello Maximo,
if you already have CAN frame recordings, I can help you decode them.
I've already done this type of analysis for frames transmitted by the G5 and GMU11.
Regards
Hervé
Hi Herve. Thanks. Yes I have some now. Here are some of them from G5.

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C974 dlc:5 remote:1 extended:1 data:0x2E 0x68 0xE6 0x40 0x67

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C974 dlc:5 remote:1 extended:1 data:0x2E 0x68 0xE6 0x40 0x67

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C974 dlc:5 remote:1 extended:1 data:0x2E 0x68 0xE6 0x40 0x67

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E

RX id:0x1648C944 dlc:14 remote:1 extended:1 data:0xE6 0xB6 0xEF 0xEE 0xD7 0x67 0xD5 0xE6 0x0 0xB2 0x48 0xC9 0x44 0x4E
 
My value last year:

-----id------- DLC B0 B1 B2 B3 B4 B5 B6 B7 Read Value --------- FUNCTION
0x10882200 007 E4 65 00 00 00 DA C5 00 1013 --------- altimeter setting in millibars
0x10882200 007 E4 65 00 00 38 C7 47 00 1020 --------- altimeter setting in millibars

0X10882200 007 E4 65 02 0A D7 F3 41 00 100 --------- altitude bug
0X10882200 007 E4 65 02 0A D7 73 42 00 200 --------- altitude bug
0X10882200 007 E4 65 02 67 66 98 43 00 1000 --------- altitude bug

0X10882200 007 E4 65 03 88 C3 64 3B 00 0,2 --------- user pitch adjustment
0X10882200 007 E4 65 03 88 C3 E4 3A 00 0,1 --------- user pitch adjustment
0X10882200 007 E4 65 03 88 C3 E4 BA 00 -0,1 --------- user pitch adjustment

0X10882200 007 E4 65 05 00 FB 0E BD 00 358 --------- heading bug
0X10882200 007 E4 65 05 00 FC 8E BC 00 359 --------- heading bug
0X10882200 007 E4 65 05 00 00 00 00 00 360 --------- heading bug
0X10882200 007 E4 65 05 35 FA 8E 3C 00 1 --------- heading bug
0X10882200 007 E4 65 05 35 FA 0E 3D 00 2 --------- heading bug
0X10882200 007 E4 65 05 50 77 56 3D 00 3 --------- heading bug
0X10882200 007 E4 65 05 35 FA 8E 3D 00 4 --------- heading bug
0X10882200 007 E4 65 05 DB 0F C9 3F 00 90 --------- heading bug
0X10882200 007 E4 65 05 DB 0F 49 C0 00 180 --------- heading bug
0X10882200 007 E4 65 05 DC 0F C9 BF 00 270 --------- heading bug
Hi Eld, I tried to use you logic to decode my messages. What I dont understand for example is how you get 1013mb value from the Hexa data of the CAN bus. (DA C5 00 ) ?
 
You guys do know that the G5 has a well-documented RS-232 output format with all the important data already on it, right? The specifications are right there in the manual.
Hi Matt, yes Im aware of that. In fact I have a ESP32 reading from G5 RS232 data. All the specs are in the manual, there are 2 messages one for GPS Data (57 bytes long starting with the char "@" with a rate of 1per second) and other for AHRS variables (59 bytes long starting with "=" char, with a rate or 10 per second). It is very detailed in the manual. However I want to get data from engine GEA24 unit...
 
If you take from with Id 0x1882200
1707412435812.png
Bbyte 0 and 1 in the frame represent a label, in this case 0xE465.
For this label, the complete transmission will be carried out using 6 concecutive frames, the number of which is visible on byte 2. The rest of the data correspond to the values to be transmitted.
In this example, they are encoded in 32bit floating....
So, for the "altitude Bug" value, it's on frame ident 0x10882200,
label 0xE465 (byte 0 and 1)
and frame number 2 (byte 2))
 
@Maximo:
there's something strange about your frames, because the CAN protocol is based on a maximum DLC of 8 data, but yours have DLCs of up to 14 data.....
 
There are other types of weft, including cyclic ones.
For example, the one sent with ident 0x18882100. Bytes 0 and 1 of the first frame sent contain the label followed by the total number of data in byte 2.
example 1: label 0xDD00 with 0x38 i.e. 52 data transmitted over 7 consecutive frames.
And on these 52 data we find, for example, the pitch from byte 20 coded in 32bit floating point, unit in radian.

Here are 2 examples of G5 frames:
620,8212;RX;0x18882000x;8;0x01;0x00;0x01;0x00;0x3C;0x00;0x60;0x33;
620,8212;RX;0x18882100x;8;0xDD;0x00;0x38;0x00;0x03;0x64;0x03;0x60;
620,8212;RX;0x18882100x;8;0x7A;0x77;0x07;0x00;0xFF;0x97;0x01;0x08;
620,8212;RX;0x18882100x;8;0xF9;0xCF;0x4B;0x3F;0xBD;0xD4;0xA2;0xBE;
620,8223;RX;0x18882100x;8;0x9B;0x52;0x25;0x3C;0xA8;0xC3;0x9A;0xB8;
620,8222;RX;0x18882100x;8;0xE8;0x4C;0x44;0xC0;0x04;0x04;0xC6;0xBD;
620,8222;RX;0x18882100x;8;0x20;0xB2;0xF9;0xBE;0x7E;0x76;0x92;0xB8;
620,8222;RX;0x18882100x;4;0x00;0xA8;0xA4;0x3B;;;;;

621,5882;RX;0x18882100x;8;0xDD;0x0A;0x30;0x00;0x78;0x7A;0x07;0x00;
621,5882;RX;0x18882100x;8;0x1D;0x02;0x00;0x00;0x00;0x00;0x00;0x00;
621,5882;RX;0x18882100x;8;0x00;0x00;0x00;0x00;0xE5;0x3A;0x1E;0xAC;
621,5883;RX;0x18882100x;8;0xBA;0xC1;0x44;0xBD;0xDB;0xF6;0xB3;0x42;
621,5892;RX;0x18882100x;8;0x60;0xA4;0x66;0x41;0x00;0x00;0x00;0x00;
621,5892;RX;0x18882100x;4;0x4C;0x30;0x74;0xBD;;;;;

1707473121172.png
 
There are other types of weft, including cyclic ones.
For example, the one sent with ident 0x18882100. Bytes 0 and 1 of the first frame sent contain the label followed by the total number of data in byte 2.
example 1: label 0xDD00 with 0x38 i.e. 52 data transmitted over 7 consecutive frames.
And on these 52 data we find, for example, the pitch from byte 20 coded in 32bit floating point, unit in radian.

Here are 2 examples of G5 frames:
620,8212;RX;0x18882000x;8;0x01;0x00;0x01;0x00;0x3C;0x00;0x60;0x33;
620,8212;RX;0x18882100x;8;0xDD;0x00;0x38;0x00;0x03;0x64;0x03;0x60;
620,8212;RX;0x18882100x;8;0x7A;0x77;0x07;0x00;0xFF;0x97;0x01;0x08;
620,8212;RX;0x18882100x;8;0xF9;0xCF;0x4B;0x3F;0xBD;0xD4;0xA2;0xBE;
620,8223;RX;0x18882100x;8;0x9B;0x52;0x25;0x3C;0xA8;0xC3;0x9A;0xB8;
620,8222;RX;0x18882100x;8;0xE8;0x4C;0x44;0xC0;0x04;0x04;0xC6;0xBD;
620,8222;RX;0x18882100x;8;0x20;0xB2;0xF9;0xBE;0x7E;0x76;0x92;0xB8;
620,8222;RX;0x18882100x;4;0x00;0xA8;0xA4;0x3B;;;;;

621,5882;RX;0x18882100x;8;0xDD;0x0A;0x30;0x00;0x78;0x7A;0x07;0x00;
621,5882;RX;0x18882100x;8;0x1D;0x02;0x00;0x00;0x00;0x00;0x00;0x00;
621,5882;RX;0x18882100x;8;0x00;0x00;0x00;0x00;0xE5;0x3A;0x1E;0xAC;
621,5883;RX;0x18882100x;8;0xBA;0xC1;0x44;0xBD;0xDB;0xF6;0xB3;0x42;
621,5892;RX;0x18882100x;8;0x60;0xA4;0x66;0x41;0x00;0x00;0x00;0x00;
621,5892;RX;0x18882100x;4;0x4C;0x30;0x74;0xBD;;;;;

View attachment 55739
Dear Wasp, Trying to get this. Below is my interpretation.

LABEL 0xDD00
620,8212;RX;0x18882100x;8;0xDD;0x00;0x38;0x00;0x03;0x64;0x03;0x60; ... means 38hex long message
620,8212;RX;0x18882100x;8;0x7A;0x77;0x07;0x00;0xFF;0x97;0x01;0x08;
620,8212;RX;0x18882100x;8;0xF9;0xCF;0x4B;0x3F;0xBD;0xD4;0xA2;0xBE; ... bytes # 20,21,22,23

Byte 20 with 4 bytes length
HEX 0xBD;0xD4;0xA2;0xBE, converting to 32bit floating point ...
DEC -0.103826 rads
DEG -5,948 degrees

Is it Correct ?
 
.... My value last year:

-----id------- DLC B0 B1 B2 B3 B4 B5 B6 B7 Read Value --------- FUNCTION
0x10882200 007 E4 65 00 00 00 DA C5 00 1013 --------- altimeter setting in millibars
0x10882200 007 E4 65 00 00 38 C7 47 00 1020 --------- altimeter setting in millibars

Still, cant get the number 1013 or 1020 from the above 32bit floating point of your post (Apr 29, 2020).
1013 in float would be 0x 44 7d 40 00 and
1020 being 0x 44 7f 00 00
I don`t see those values above. What I am doing wrong ?
 
I want to get data from engine GEA24 unit
The GEA 24 would only be installed as part of a G3X system, and if you have a G3X system then you have access to all the engine data you could ever want via its publicly-documented RS-232 output. So I really don't understand the objective here.
 
The GEA 24 would only be installed as part of a G3X system, and if you have a G3X system then you have access to all the engine data you could ever want via its publicly-documented RS-232 output. So I really don't understand the objective here.
Given that from G5 I can get only 2 sets of values (GPS Data, and Flight Data) and need also Engine data. That was the reason trying to read GEA24.
 
This isn't exactly where this question fits, but it seems the right kind of expertise is posting here: I have a KX-155 (brick outhouse of a radio I am super reluctant to part with...) whose NAV functions have been neutered ever since my G3X Touch displaced the KI displays. SO: Has anyone here come up with a (likely Arduino etc. to ARINC-429?) design that takes the KX-155 (or 165 for that matter) analog outputs and interfaces them with the G3X to display as a second NAV on the PFD HSI?
 
  • Like
Reactions: eld
The GEA 24 would only be installed as part of a G3X system, and if you have a G3X system then you have access to all the engine data you could ever want via its publicly-documented RS-232 output. So I really don't understand the objective here.
Personally, I'm watching this thread because I have no free serial ports on my G3X, so would prefer being able to tap onto the CAN bus.
 
Yes I have make a error for 1013


some values for G3X :

SourceIdLabel:Byte0 , 1SizeByte 2First data (byte x)FormatCommentCoefUnit
G3X PFD0x10022222E465
7
0332-bit floatBaro/100Mb
G3X PFD0x10022222E465
7
2332-bit floatAltBug* 3.28084Ft
G3X PFD0x10022222E465
7
3332-bit floatUserPitch* 180/ PI°
G3X PFD0x10022222E465
7
4332-bit floatVloc* 180/ PI°
G3X PFD0x10022222E465
7
6332-bit floatObs
G3X PFD0x10022222DC02
16
1232-bit floatSlip* 180/ PI°
G3X PFD0x10242100DD00
60
2032-bit floatPitch* 180/ PI°
G3X PFD0x10242100DD00
60
2432-bit floatRoll* 180/ PI°
G3X PFD0x10242100DD0A
52
1232-bit floatIas* 3600/1852Kt
G3X PFD0x10242100DD0A
52
1632-bit floatTas* 3600/1852Kt
G3X PFD0x10242100DD0A
52
3232-bit floatPalt* 3.28084Ft
G3X PFD0x10242100DD0A
52
3632-bit floatTemperature°

Exemple of capture :

ID:0x10022222
7
E46500868FC347Label:E465knob:00Baro:1001mb
ID:0x10022222
7
E46502B81EC644Label:E465knob:02AltBug:5200Ft
ID:0x10022222
7
E46503FDAD003DLabel:E465knob:03UserPitch:1.8
ID:0x10022222
7
E46504C29201BFLabel:E465knob:04Vloc:331°
ID:0x10022222
7
E465065077D63FLabel:E465knob:06Obs:
1
ID:0x10002100
16
DC020C00430100000000000000000000Label: DC02slip:
ID:0x10242100
52
DD0A30008112B601FF030000CABFA9408B27AC407E57803CFAC588BC1948DB42B8D69243D08E9B41E07E9B416025803E99D1E8BCLabel DD0Aias:10Kttas:10Ktpalt:90FtTemp:19.4°
ID:0x10242100
60
DD00380003640100651AB601FE5701082EEFB4405B18E9BD344D15BB74370C393CEB20BAA43280B9A8AF8FBF00F0B63C0060313BF59A0E3900D4883DLabel DD00pitch:-7°roll:-0°

Regards,
Eric
 
Last edited:
The GEA 24 would only be installed as part of a G3X system, and if you have a G3X system then you have access to all the engine data you could ever want via its publicly-documented RS-232 output. So I really don't understand the objective here.
When you have not RS-232 port free, we must find a other solution ...
Regards,
Eric
 
Last edited:
Thank you Eric for this summary table...
There is only to have recordings of frame emitted by other garmin devices (GEA24, GMA-24, GTN-750, GAD-29, GEA-24, GSU-25, GSA-28's......) to complete this table...
I have some GMU11 frames that I'm currently analizing.... (id 0x10A82000, 0x10A82100 and 0x10A82200)
Regards
Hervé
 
Status
Not open for further replies.
Back
Top