Stjohn's RV-7

6 hours.

Adding this from last weekend. Got everything back in, with ferrite beads installed on everything going into and out of the EFIS and the GNS430w. There’s definitely a big difference in both the amount of noise generated by the EFIS and the amount of RF dumped into the EFIS on transmit, even in a shop full of metal things. I still have to wire in the RDAC and sensors permanently, but this time around, I actually got the EFIS audio output wired in correctly, and I can now hear Bitching Betty in my headset. The volume is a little low, and the sample rate is terrible. I’m not sure what to do about that. Maybe Matt at MGLUSA can shed some light on it.

I also mounted an avionics ground plate full of tabs right near the radio stack for shorter connections between avionics and ground. It also looks like my antenna will go under the pax floor pan to keep it as far away from the antennas, sensors, and servo in the tail or the radio stack and EFIS.

I also get to fish out the cheesy RCA cable from the main bundle and replace it with a twisted triple to carry power, ground and data to the AHRS and magnetometer. If I can get all this shite to sing in harmony, then it’s on to the baffles and other FWF fun.

The system won’t be noise-free until I no longer have unterminated wires, which means at the airport with the wings attached and all circuits complete, but I can live with that for now.

6 hours.

Yesterday and today was an ugly mess. I had to pull the wiring harness to try to figure out a couple of things, first and foremost, why is my radio dumping RF energy into my EFIS? I’ve checked all the grounds, twice, three times, both at radio, both ends of the antenna, and the EFIS itself. I grounded the shields of the ARINC connector as well, while I was in there. It seems to be a little better. I get no clicking of relays, but I still have the Bermuda Triangle effect whenever I key the mic. I’ve also got no mic audio. I don’t know if that’s my headset, which, at last outing, proved itself extremely unreliable in the mic department. My other headset looks like the foam muff on the mic dissolved itself into the actual microphone somehow, so I doubt that one works. This just gets weirder and weirder.

One thing I’m not too sure about: If I place one probe of my multimeter against the inner conductor on the antenna’s BNC connector and the other one on the antenna rod, I get no beep. I thought an antenna had one pole connected to the center conductor and the other pole connected to a ground plane. It may be that I have a defective antenna, which would suck, but better than a fried radio or EFIS.

Looks like I’ll be ordering yet another antenna from ACS, but until then, my old RAMI whip antenna will have to do for now.

6 hours.

Avionics installed! Everything powered up, no smoke! It also appears that I’ve connected everything correctly, with notable exception: One, I can’t seem to get any audio signal from the EFIS. This could be because I’ve connected the wrong wires to the RCA plug, or something is misconfigured in the EFIS software. It’s also entirely possible that the pins are in the wrong spot on the audio panel connectors. I think I used either the ADF or DME connection, but I have to check my notes to make sure. I definitely screwed up the pilot side mic connection. If you plug the mic in, it keys the mic. With nothing plugged in, the stick-grip push to talk trigger works fine. I’m going to try with my other headset, but I suspect it’ll be the same.

The GNS430W seems to be working OK. I can’t hear SMO or LAX tower, but I can hear aircraft overhead talking to them. ARINC data connection from the 430W to the EFIS seems to be working OK as well, at least there are messages being passed back and forth. I can’t pick up the SMO VOR either. It’s a weak signal, and there are a couple of hills between me and it. If I had a flatbed trailer, I’d put the fuselage on it, tow it up to the airport parking lot and to some tests there. Those devices aren’t designed to transmit to ground targets, so I’m not surprised I’m not picking it up. Had a bit of a scare though. At some point the large frequency knob stopped working. I could change the point frequencies with the small knob, but the major frequencies wouldn’t change. After going through several power cycles and various configurations, it started working. I think I had some kind of remote control enabled, but it’s working as of now.

Transponder lights up, but shows no altitude encoding from the EFIS. That’s probably a configuration issue as well, and I didn’t spend a lot of time on it.

I didn’t get all the antennas done, I just put a BNC end on the COMM antenna cable so I could test the radio without risking frying the thing by keying the mic and dumping all that RF energy right into the box itself. The location of the COMM antenna might be a problem. When I key the xmit, the EFIS shows me descending at 500fpm and a 20 degree yaw to the right. Since the plane is still in the guest house, this is clearly incorrect. I think I can swap the transponder antenna for the COMM antenna (this is why I got a new COMM antenna with a BNC connector) and get the COMM antenna the recommended 6 feet from the EFIS. The question then is, will the transmitted signal interfere with the operation of the autopilot pitch servo? I’ve still got a couple feet of antenna cable to spare on each end, so I can move that antenna all over the place and still be OK. I’m just trying to avoid punching any more holes in my airplane. Of course, in retrospect, using that cheesy audio cable to carry the AHRS data instead of a proper shielded two-conductor cable may have been a mistake. I so want to be done with this…

Before I put the EFIS back in, I made a new LED warning light for the panel. This one’s chrome and screwed in properly unlike the cheesy plastic one I had before. Much more solid. That LED is friggin’ bright, though. Apparently 800mcd is bright enough to get your attention in bright light, which is fine, since this will be primarily a daytime aircraft.

I still need to test the GPS transmit to the ELT and ground the ELT as well.

4 hours.

Finally got back into it today. First thing I did was dismount the EFIS in preparation for making a hole for the ELT remote switch. Then I reinstalled the radio trays back in their spot so I’d have a stiffer panel to work with during the process of making the hole. I still need to figure out where the ELT wire’s going to make its way to the panel. Oh, and I realized I need another roll of 3-conductor shielded wire, because I also have to get GPS data back to the ELT as well. I guess it transmits the last known position while it’s screaming for help.

I need to start finishing things in the back of the baggage compartment, because not only am I tired of crawling around back there, I need to not have that to worry about while I’m finishing up the wiring.

I also have some 4-40 screws on order from ACS, because the ELT kit doesn’t actually provide any. I also have a BNC-terminated antenna on the way.

10 hours.

This is what I wound up with at the end of yesterday:

It might look like a mess, but it’s not. Every pin in every connector has been checked twice, and the coils are grouped by device and function. Except the one or two I missed. This has been an exercise in patience and squinting at little wires. It’s like everything else in this project: If you look at the whole thing it looks insane and impossible, but if you look at it one piece at a time, it’s not that big a deal.

Each wire only has two ends, so that makes a good place to start. First I did all the power and ground connections. There are several. The 430 has 3 devices in one, but only two have their own power feeds, unless I’m driving a superflag device off the NAV unit, which I’m not. The audio panel is the hairiest part, because there are so many connections and a couple of them share pins, which sucks, because you have to make pigtails that combine two wires, usually audio returns, into a single pin that plugs into the connector. The shields absolutely suck. I probably should have used 24ga wire, but I had green 20ga wire, so I used that. That’s where I learned the Aeroelectric (and probably standard) way to bridge shield to a standard wire. That wasn’t that difficult, but there were a lot of them, and now they’re all ganged together and fastened to the audio panel’s frame. The deal is, you ground the shields at the audio panel to reduce noise, or at least attempt to do so. Supposedly this is how you keep EMI noise out of your audio connections, which tend to run all over the aircraft and often past some noisy things like strobes, relays, etc. Now, hopefully, in crushing together all those cables, I haven’t compromised the insulation integrity, and during the soldering process, didn’t melt through any signal wires. I still need to verify connectivity and isolation, but I’m off to Vancouver for SIGGRAPH, so that’ll have to wait.

I couldn’t just leave it be, though. I powered up the audio panel, which lights up fine, but I didn’t want to risk powering up the radio. If something is screwed up in my wiring and the mic key is stuck on, the RF power with no antenna will fry me out of $7500 worth of radio, GPS, and NAV equipment. Not to say I didn’t try. I had some leftover RG400, which I put a BNC end on, and was going to connect the other end to my COMM antenna, but that didn’t happen. RG400 cable has two layers of shield on it, so the usual trick of pushing the shield down and pulling the wire through doesn’t work. My current RAMI antenna needs pigtails for wiring, and dammit, so does the marker beacon antenna. So I need a COMM antenna that uses a BNC connector like everything else.

One thing I missed while I was wiring is the COMM remote recall function. This uses a discrete input (fancy name for an external button) to scroll through a list of preset frequencies. It looks almost useful enough to take apart the main connector on the GNS430W and add a tail for it, but I don’t actually have a free button for it. If I didn’t do remote ident on the transponder I could. The other suck part about the GNS430W is that it doesn’t have the same remote function protocol as the SL30, which can be fully controlled via RS232 communication. Sure would be nice to be able to set frequencies from the EFIS, but this setup will be fine as is.

I also got a phone extension cable to make up for the shortcomings of the one shipped with the ACK 406 ELT, which doesn’t quite reach all the way to the panel after threading its way through the wire bundle. I also figured out how to install phone cable ends, a skill useless in every other facet of life, since I don’t even have a landline anymore and subsequently will probably never wire a phone jack in this house. The new cable, with the end cut off, goes fine through the portholes I drilled for the strobe cable. Yes, I know it’s probably bad, but as long as the strobe noise doesn’t trigger the ELT’s emergency transmit mode, I can live with it.

When I get back, I’ll also have to dismount the EFIS to install the ELT remote switch and verify GPS communication. Then my time in the tailcone is DONE. I’ll reinstall the flap arm and the flap motor and call it a day.

The other thing I have to do is run another wire for push-to-talk on the pilot side. The audio panel has facilities for multiple push-to-talk sources, diagrammed by shorting the PTT circuit to the MIC return, which is the same thing as shorting it to ground. Right now, I have both PTT buttons coming out of one wire, and I need two, one for pilot, one for copilot.

I also need to lay out my wire codes on here so I have a record of them.