Two SV-HARNESS-D37

RockFLY

New Member
Joined
Oct 24, 2008
Messages
20
G'day, I must be missing something.

In the same way one SV-GPS-250 unit should have its wires connected to both displays, can all other the wires from two main SV-HARNESS-D37 be routed to a common connector so that the various feeds are common to both displays? In other words, if I take two SV-HARNESS-D37 looms and bundle them to a single connector for space saving and convenience, is this OK?

For the future features list ... I'd like to see a glide range ring please.

Cheers, Stu
 

jakej

Well-Known Member
Joined
Oct 10, 2007
Messages
2,141
Location
Adelaide, Australia
Stu

Not sure what you are trying to acheive here - however if you've got 2 displays I'd use this wiring hub http://www.vx-aviation.com/documents/AXIS-15A-110101.pdf - that way you can add/duplicate any compatible avionics as you see fit later.

Jake J
 

RockFLY

New Member
Joined
Oct 24, 2008
Messages
20
Thanks Jake.

That looks like an option, but I am trying to avoid anything else that may fail in service. An SV-HARNESS-D37 comes with each display. I appreciate that displays talk to each other and everything else on the network via the DB9 serial connectors and splitters (even if one screen fails), so it appears that a second SV-HARNESS-D37 loom is only required to connect the SV-GPS-250 to both displays. ... i.e. all the other wires are academic. I figure that if I terminate all the common wires from each SV-HARNESS-D37 looms into sockets on another D37 connector, anything I connect to that can feed info directly to both displays for ultimate redundancy. Is this overkill ?

Alternatively, should I be removing all the redundant wires from the second SV-HARNESS-D37 except those for the SV-GPS-250?

Cheers, Stu
 

RockFLY

New Member
Joined
Oct 24, 2008
Messages
20
Another thing for the future features list ... a VNE warning as a function of KTAS would be helpful.

Some aircraft, like my F1 Rocket, are TAS limted due flutter at about 240 KTAS. At 10,000', TAS is around 30 KTS faster than IAS, so there's not much point in warning about VNE in KIAS up high. After all, KTAS is already being calculated, so I trust this is a straightforward option.

Cheers, Stu
 

jakej

Well-Known Member
Joined
Oct 10, 2007
Messages
2,141
Location
Adelaide, Australia
Stu

I usually remove any wires not needed as they can act as an 'antenna' receiving 'noise' from other electrics etc, makes for a neater installation too ;)
It's a good idea to connect to both screens for redundancy.

Jake J
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
Most connections between screens are common, but not ALL of them.

Ones that cannot be hooked to both screens at the same time:
Battery (even with no batteries connected)
USB (4 wires)
Dim Out

So you are welcome to hook power, all the serials, and the audio wires together, but you need to keep USB and the battery connections independent to each screen.

Many installs have more than just the GPS puck hooked up. If you use our transponder that takes a serial port, if you use us for an altitude encoder that's another, if you have a backup GPS, if you have an SL-30, etc. We don't share this data across the network, it must be hooked to each screen. So the large majority of connections on the back of each screen gets used even if you have multiple screens.
 

RockFLY

New Member
Joined
Oct 24, 2008
Messages
20
Thanks guys,

I have already replaced both USB cables with shortened panel mount USB ports from SteinAir and will mount the batteries somewhere where they are kept as cool as possible (Li-ion degrades at about 25% per annum at room temperature and faster at higher temps - about %5 pa sealed in a bag in the fridge). I will effectively bundle the other wires into a common connector to tidy up the loom. Then all the other devices can connect to both displays via the one connector ... such as the SV-GPS-250, Garmin 430W, GMA-240, GTX-327 and Icom A-210. :)

Some panel pix at: http://www.mykitlog.com/users/display_log.php?user=RockFLY&project=797&category=5592&log=115354&row=1
 
Top