EI CGR-30P and IFD-540
Printed From: Avidyne
Category: Avidyne General
Forum Name: IFD 5 Series & IFD 4 Series Touch Screen GPS/NAV/COM
Forum Description: Topics on Avidyne's IFD 5 Series and IFD 4 Series Touch Screen GPS/NAV/COM
URL: http://forums.avidyne.com/forum_posts.asp?TID=1081
Printed Date: 07 May 2025 at 10:45am
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com
Topic: EI CGR-30P and IFD-540
Posted By: jonesronc
Subject: EI CGR-30P and IFD-540
Date Posted: 31 May 2016 at 4:11pm
|
Having trouble getting the IFD-540 to talk to the CGR-30P; the IFD sees the fuel data from the CGR-30P but I'm not seeing waypoint data on the CGR-30P with its Rx mode on COM 3. Using AVIATION format on the serial port of the IFD-540; I know it's good, as it's piggybacked with the same data and port as the MLB-100. Anybody have a configuration that works? Thanks! |
Replies:
Posted By: paulr
Date Posted: 01 Jun 2016 at 8:42am
| 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). |
Posted By: jonesronc
Date Posted: 01 Jun 2016 at 4:01pm
|
I'll try turning COM3 off than on and see if that fixes anything. Thanks for the tip! I'm not terribly concerned about not having waypoints on the CGR, as the print is small, and I can read the data on the IFD540 in bigger print. I think I'd be more bummed if it was the other way around, like you have it. V/R, Ron |
Posted By: paulr
Date Posted: 01 Jun 2016 at 4:58pm
|
Good luck, Ron. Here's specifically what I did:
|
Posted By: DavidBunin
Date Posted: 02 Jun 2016 at 12:24pm
|
AVIDN is the default waypoint that the IFD-540 outputs right at first, before you press ENTR for the first time. During the self test, the CDI annunciators are lit, the deviation bars are half-displaced (up and left, if I recall) and the active waypoint is AVIDN (located, strangely, at the Garmin headquarters building in Olathe, KS). Sounds like your CGR30P is latching onto that initial test data as real information and then rejecting the real data when it comes up. David Bunin |
Posted By: paulr
Date Posted: 03 Jun 2016 at 11:23am
| 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. |
Posted By: jonesronc
Date Posted: 03 Jun 2016 at 10:06pm
| Tried the reset, got the flight plan waypoint to show up on the maintenance screen, but nothing on the inflight fuel screens. Apparently the cgr is getting the data, but not processing it properly. Will call EI. Thanks, Paul! |
Posted By: paulr
Date Posted: 06 Jun 2016 at 8:42pm
| 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. |
Posted By: jonesronc
Date Posted: 08 Jun 2016 at 12:25pm
|
The EI-CGR is now working; it defaults to fuel flow only, you have to twist the rotary knob to get the waypoint info. Oops, didn't know that. For installing, it turns out that the current software version 10.1.something or other, only puts out AVIATION format on one serial port. So, you have to 'piggyback' or parallel a wire from a port that also requires that format, for example the MLB-100. I've tried to attach a copy of the images of my current config, which works, once the AVIATION port is 'piggbacked'.
|
Posted By: paulr
Date Posted: 09 Jun 2016 at 10:46am
| 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. |
Posted By: flybikeski
Date Posted: 09 Jun 2016 at 3:09pm
| 10.2 will allow two serial ports to both have AVIATION format. I just prewired my JPI for another AVIATION port and will enable it then. Piggyback will work, but may be confusing for anyone working on the system in the future. They will look at the config screen and it will not tell them how the fuel computer is getting the data. They may not even catch the physical "piggybacking" of the wiring. Most would know, but I bet it would flummox some. |
Posted By: paulr
Date Posted: 20 Jul 2016 at 12:27pm
|
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. |
Posted By: ColinR
Date Posted: 06 Oct 2016 at 3:11pm
|
Hi there, I'd be interested to know how you solved this problem. I have the same problem. The equipment is fitted to a Socata TB20 which has an IO-540 engine. The CGR is receiving Flight plan data using 'Aviation' format data out of the IFD540. However, the IFD540 is not receiving ARNAV/EI FUEL from the CGR on Com3. The unit was rewired as suggested both by Avidyne and Ei to Com2, but there was no communication at all. Using Com3 I have found a temporary fix, using this sequence. 1. Master Switch ON, this powers up the CGR. 2. Start engine. 3. Avionics Master Switch ON, this applies power to the IFD540. 4. Accept start up menu's on IFD540, which then defaults to the Fuel page. 5. Pull CGR circuit breaker 6. Reset circuit breaker after a few seconds. The initial data string from the CGR is then accepted by the IFD540 and Fuel Flow and Fuel Qty appear on the IFD540. I also tried starting the engine with both the CGR and IFD powered up. This caused the IFD to reboot and forget/lose the fuel data. Your suggestion of going into the Maintenance settings of the CGR also works but is quite time consuming. Pulling the circuit breaker and restarting the CGR is quicker in my set up. Regards, ------------- Colin |
Posted By: paulr
Date Posted: 06 Oct 2016 at 3:14pm
| 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. |
Posted By: ColinR
Date Posted: 06 Oct 2016 at 3:27pm
|
My avionics guy managed to rewire the CGR very quickly, by removing the pins on the connector to the display, and inserting them into the Pin that corresponds to Com2. Only took a few minutes. It didn't work and we swapped them back again. ------------- Colin |
Posted By: paulr
Date Posted: 03 Jul 2017 at 10:12am
| 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. |