EI CGR-30P and IFD-540

Same configuration, no worky, but I have the opposite problem: the 540 isn't getting fuel data from the CGR-30P on COM3 but the CGR gets waypoint data. Fuel data works if I turn the CGR-30P output on COM3 to "off" and then back on in maintenance mode, but that's a pain in the butt. EI support wants me to try rewiring to COM2 but I am extremely skeptical that will fix the problem--their thinking is apparently that it's a timing issue that would be resolved by moving to the other UART (or whatever they're using for serial conversion).

1. Master on: CGR30P powers up.
2. Avionics master on: IFD540 powers up
3. Verified IFD540 is at fuel setup screen, with “-----“ shown in all fields
4. Waited for IFD540 to get GPS lock
5. Entered a flight plan (direct KDCU-KNEW)
6. Entered CGR30P user setup menu
7. Verified GPS distance data is correct
8. GPS waypoint shows as “AVIDN” for some reason vice KNEW.
9. changed COM3 output on CGR30 from “ARNAV/EI” to “NONE”, then changed it back
10. Pressed rotary selector on CGR30P to confirm changes
11. Noted that fuel status screen on IFD showed (correctly) 82.0 gallons on boarf
    

That might be true in Ron's case; for me, it's the opposite-- the CGR's fuel state data isn't being displayed on the IFD for whatever reason. Since even my ancient KLN94 could manage this feat, it's kinda frustrating.

Please let us know what they say, Ron. I'm curious to see if they tell you to rewire to use a different COM port.

Thanks, Ron. I'll take a look at my config when I get home and see if I can figure anything out. I didn't know about the AVIATION piggyback requirement.

I restarted my support thread with EI and Avidyne, and here's what I learned:

1. The IFD doesn't have any logs that can be used to troubleshoot LIO handshaking problems.

2. Serial port logging is being added in 10.2.

3. EI said "The reason we need to have the interface swapped to COM2 is that COM2 is a direct route to the main board and processor of the CGR.  COM3 and COM4 are virtual ports, and go through an intermediary chip...for some reason or another, that chip can occasionally cause some issues with certain GPS communications."

4. EI is sending me an adapter that plugs into the back of the CGR to swap the ports so I don't have to rewire; if that fixes the problem, then I'll know it's because COM3 is a virtual port. If not, then maybe the 10.2 logging features will shed some more light.

I still haven't solved it. I haven't installed the COM3<->COM2 adapter that E-I sent me, so when I want fuel data, I go into maintenance mode. I can't pull the breaker because my CGR30p is primary, so there's no breaker. It's a pain in the butt.

Thread resurrection: I mentioned upthread that E-I had sent me a simple wiring adapter to swap COM2 and COM3. I installed it at annual, updated the port settings on the CGR itself, and now get fuel range data at startup, as God and Avidyne intended. From that, I conclude that something is wacky with COM3 on the CGR series when used with the IFD540. E-I knows about the issue but I doubt they will do anything about it, as their support guys claimed it was an interrupt processing issue due to hardware.