New installs (not 530 swaps) - updates wanted

We'll see if anybody pipes up but the majority of installs so far have been plug & play installs.   There have been some clean installs and from our perspective, they went well but I'm sure you're looking for end-user feedback on the process.

I went from 430W to 540.  Not exactly plug and play, but it wasn't a 100% clean install either.
The circuit breakers needed to be changed from what my 430W had, but I was prepped for it after reading the install manual.  In fact I installed all new CB's on my avionics bus.  I wired a COM swap switch to my yoke. I also installed a PSEngineering PMA450 and wired up the standby pins to it to do future standby monitoring.

Flew it 700nm yesterday from the avionics shop home.  I do need to get the photocells calibrated between my 430W and the 540 as the 430W was way too bright compared to the 540 when in the pitch black night.  I tried using manual adjustments on the 540, but the increments seemed too coarse so I found the 430W and adjusted it down to match the 540 brightness.

I just realized I can't attach photos to the forums.  I'll get them somewhere on the Internet and post a URL.

To set the dimming on the 430W, press the enter key and turn on the unit.  This will put it in maintenance mode.  Scroll with the big knob until you get to the lighting page.  From there it is pretty self explanatory.  The instructions are in the 430W install manual if you get stuck.  You can find it on the Internet.

Thanks, and best.

There are a lot of things to cover with an install.
Gring has it pretty well delineated; my shop picked up things I would not have expected.
Example: next software revision will supposedly allow standby frequency monitoring - <but it has to be wired - thanks to Gring mine is>
Comm panel freq swap switches
Comm panel source switches
TXP ident
TAS605 mute (my shop had to be educated because other traffic systems do not permit mute)

You want every option wired in my opinion whether you choose to use it or not.

I'm glad I wired all the bells and whistles, may not use them all.

Gring has it well outlined in his install posts.

Good luck.

Wow, your project did grow.

Question for the Avi-team:

In dual IFD installs - how are peripheral devices handled, e.g.
1. I have dual 540s. I have TAS 605. Traffic shows up on IFD #2, but not IFD #1 - and traffic option for datablock selection is grayed out on IFD #1.

2. Right now, my JPI 700 is not showing up on either of my IFDs. Probably a configuration problem, have contacted shop. Question, do the IFDs data share fuel flow between units, or how does that work?

These are probably stupid questions (coming from me), but I am sure they will come up again.

Maybe will help you too, roy32jm, since you're doing dual IFDs.

Thanks

David,  I have a JPI-700 with fuel flow option and it is tied into my IFD540 via RS-232.

The RS-232 aviation data out from the IFD540 is wired to the JPI-700.

The JPI-700 has a reply RS-232 path to update the IFD540 with fuel flow , fuel used etc.

Mine works fine

Ed

Yes,  The RS-232 must be configured in the IFD540

Not sure on the cross feed as I have only 1 IFD540 but it is possible for two RS-232 receivers to  connect to a single RS-232 Tx if there is no handshaking (In this case there is not)

Ed

Thanks Steve.

I am assuming the TAS605A input is RS232, and not ARINC 429? I have no doubt the JPI700 is as well.

I am in LEX tonight, back to TUS tomorrow. I'll drag out the manual and figure out how to harvest a datalog.

Thanks.

BTW - Steve - limited experience so far and I know corrections needed - but seems like great products.

DMG

Edited by ddgates - 11 Nov 2014 at 10:05pm

Gring wrote: David, the TAS can be wired for either ARINC 429 or RS232. From memory, the RS232 gives you additional information such as N-number or sqwak code but is limited to 9 targets. ARINC 429 does not have the additional info, but can display 30 targets.

Edited by oskrypuch - 12 Nov 2014 at 8:51am

Gring wrote: ... From memory, the RS232 gives you additional information such as N-number or sqwak code but is limited to 9 targets ...