First let me start with the fact that the entire aircraft is Garmin. Very near having the airworthiness inspection scheduled. Last thing I did was put the wings on for the last time. First time I actually connected the d-subs to the roll servo and powered everything up. That’s when things went south. Hopefully a Garmin guru out there can enlighten me as to what the problem might be. Here’s an abbreviated list of components I have that would relate to my issue. Dual GDU 460’s PFD and MFD. GMC 305 autopilot controller. Two GSA 28’s and a GTN 650. Been trying to troubleshoot for 3 days and about to give up!
Scenario 1. Hook everything up normally. Turn power on to everything . The two screens start flashing red X’s on just about everything. Engine instruments, Attitude, HSI..etc
Scenario 2. Unplug the roll servo and pull the autopilot circuit breaker. Both GDU’s return to normal and all the information returns to normal. Both screens communicate with each other as normal. Only message I get is ADAHRs not receiving Magnetometer data. Understandable as it’s not calibrated yet.
Scenario 3. Plug the roll servo back in and leave the autopilot CB pulled. Result is see Scenario 1!
Scenario 4. Unplug the roll servo and reset the autopilot CB. Result is see Scenario 1 again!!! ARGH!!
Here’s where I ABOUT LOST IT! Decided to throw the Pitch servo into the mix.
Scenario 5. Disconnected the the pitch servo and attached a Garmin “removed GSA 28 d-sub” to the end that would attach to the servo. Disconnected the roll servo again but left the autopilot CB IN and this time everything worked as it should.
Scenario 6. Left everything as it was in Scenario 5 and plugged in the roll servo again and you guessed it…..SEE SCENARIO 1!!! *#!#!!**##
The wiring harnesses and panel were built by Pacific Coast Avionics. Sean did a spectacular job. Now as a bit of possible screw-ups on my part. I have d-subs at the wing root to the actual servo in the event I ever had to remove the wing I would just have to unplug it instead of de-pinning it. Could the described scenarios above be a result of possibly swapping either the can-bus pins or the RS-232 pins? The common denominator in all this is the roll servo connector at the wing root. The other possible issue could be in the configuration modes for the RS-232 settings for the autopilot. I don’t mind repinning the can-bus pins or the RS-232 pins at the connectors I just want to be sure that screwing with these pins won’t damage anything if they are wrong. (Maybe they already are wrong). My gut tells me this a communication issue between my roll servo and the autopilot and or the rest of the can-bus or RS-232 communication link. Does this sound like a can-bus or RS-232 communication conflict?
Starting to feel like this RV-10 is trying to get in it’s lost shot to the “you know what’s” before it concedes and let’s me win!!! LMAO
Thanks for any input that anyone can provide.
Scenario 1. Hook everything up normally. Turn power on to everything . The two screens start flashing red X’s on just about everything. Engine instruments, Attitude, HSI..etc
Scenario 2. Unplug the roll servo and pull the autopilot circuit breaker. Both GDU’s return to normal and all the information returns to normal. Both screens communicate with each other as normal. Only message I get is ADAHRs not receiving Magnetometer data. Understandable as it’s not calibrated yet.
Scenario 3. Plug the roll servo back in and leave the autopilot CB pulled. Result is see Scenario 1!
Scenario 4. Unplug the roll servo and reset the autopilot CB. Result is see Scenario 1 again!!! ARGH!!
Here’s where I ABOUT LOST IT! Decided to throw the Pitch servo into the mix.
Scenario 5. Disconnected the the pitch servo and attached a Garmin “removed GSA 28 d-sub” to the end that would attach to the servo. Disconnected the roll servo again but left the autopilot CB IN and this time everything worked as it should.
Scenario 6. Left everything as it was in Scenario 5 and plugged in the roll servo again and you guessed it…..SEE SCENARIO 1!!! *#!#!!**##
The wiring harnesses and panel were built by Pacific Coast Avionics. Sean did a spectacular job. Now as a bit of possible screw-ups on my part. I have d-subs at the wing root to the actual servo in the event I ever had to remove the wing I would just have to unplug it instead of de-pinning it. Could the described scenarios above be a result of possibly swapping either the can-bus pins or the RS-232 pins? The common denominator in all this is the roll servo connector at the wing root. The other possible issue could be in the configuration modes for the RS-232 settings for the autopilot. I don’t mind repinning the can-bus pins or the RS-232 pins at the connectors I just want to be sure that screwing with these pins won’t damage anything if they are wrong. (Maybe they already are wrong). My gut tells me this a communication issue between my roll servo and the autopilot and or the rest of the can-bus or RS-232 communication link. Does this sound like a can-bus or RS-232 communication conflict?
Starting to feel like this RV-10 is trying to get in it’s lost shot to the “you know what’s” before it concedes and let’s me win!!! LMAO
Thanks for any input that anyone can provide.