VP-X Laptop Interface

[flickroll]

A laptop interface for the VP-X system would be very nice and beneficial. VP-X users are dependent on the EFIS manufacturer to provide features in their VP-X interface. If, for example, the EFIS manufacturer chooses to not allow a wig wag light set up, the end user then has no way to enable this feature. A laptop interface would allow this feature (generally a one time set up) to be enabled without sending the VP-X box back to VP for configuration. A laptop interface would also allow extensive testing when the VP-X system is first commissioned in the aircraft. Thanks

[Marc Ausman]

As far as I know all the core features will be implemented by the EFIS guys. If not in the first release it would be shortly thereafter. Let's wait and see.

[pilotspike]

Really? Having to rely soley on a 3rd party vendor to at least communicate and interact with this unit is probably enough to lose my business, though I am only one. Is there not at least a RS232 or Ethernet based interface outside of an EFIS? How do users troubleshoot problems if they can't isolate the VPX system from the EFIS?

I'd be afraid that this would lead to tons of vendor finger pointing sessions.

Spike

[Marc Ausman]

There is an interface you can hook to your PC, but it is for people who are somewhat computer savvy. http://www.verticalpower.com/forums/...read.php?t=758

All the interfaces that you can see on the PC are available on the EFIS - settings, fault codes, etc. so I don't see much of an issue.

Flickroll is using beta software that does not have all the features implemented on the EFIS yet.

[pilotspike]

Thats nifty to see that you guys have published an API, though it looks like it has been disclaimered as unsupported. Though thats really a different discussion.

Let me ask my question in a different way. How would a builder who is bench testing his install find out if a problem was with the EFIS or with the VPX itself?

John

[Marc Ausman]

I'm not sure how to answer your question - it is very broad.

If the comm link is OK, the EFIS will display faults, position and status data that can help troubleshoot.

Is there a specific case you're wondering about?

[pilotspike]

Sure. If I wire up my plane with an EFIS and VPX and I have problems configuring the VPX how do I know if the problem (coms or not) is due to the EFIS having problems or the VPX having problems? Who do I call and how do I know? I can see this coming up if upgrading your EFIS software or if you use the EFIS to upgrade the VPX software (as is mentioned on the VPX page). Is it possible to brick the VPX device during an upgrade if power is lost, the EFIS burps, etc?

It would be good to have an interface to the VPX so that we can use a laptop/desktop to perform the same functions (or at least some high level of functional coverage) to at least isolate problems between manufactures.

Don't get me wrong, I like this product and am way more inclined to purchase it than I am the 200 product line. I just am not enthused at what feels like the potential of getting caught needing technical support and no clear way of identifying who should be giving me that support.

[Marc Ausman]

Best bet is to call us first and we can make the determination.

All the electrical stuff is done by the VP-X, the EFIS is just a display. I don't think it is as convoluted as you might imagine. The EFIS integrates with many things (AP, wx receiver, radios, GPS, etc.) and yes there can be some weird cases where it's hard to determine the problem but usually it's not too bad.