Is Labview a good choice for developing vehicle infotainment system ?

[Sibin]

Developing of in vehicle infotainment system using Labview is a good choice ?, considering all the criteria like UI, Interfacing of phones etc...

[LuI]

Sibin,

as always, it depends ...

At the beginning let me state that I imagine the alternative to LabVIEW is one or the other C-compiler as being used with embedded systems.

LabVIEW, IMHO, is good for prototyping or for not-mass-market systems. My most-used systems have some several 10 users.

I do not think it was a good choice for systems that are planned to be sold by several 10th of 1000s. One of my reasons is licensing, but installation and roll-out are, amoung others, more.

UI can be done quite easy and can reach a level where the LV-base is rarely - if at all - be detectable.

Interfacing is clear a big pro of LabVIEW. But I do not have experience with interfacing phones. And the devil is always in details...

Another big plus is the inherent multithreading of LabVIEW and the ease of using it. LabVIEW makes it much easier to provide services and have them react in parallel to other threads. Think of incoming calls while playing a video. Or scheduled alarms and reminders etc.

On the other hand, when working for big automotive producers, you need a strict quality system and defined processes. This can be done with LabVIEW, and is, again IMHO, easier to be maintained once it is established. But it is probably harder to set up.

Again, just my € 0.02!

Greetings from Germany!

--

LuI

[TroyK]

What hardware are you planning on using? What processor? What OS?

Raspberry Pi/Linux? ARM/Android? These are the first questions you should be asking yourself.

You'll want something small that doesn't use too much power.

LabVIEW wont run on a Raspberry Pi or Android. There is LabVIEW embedded for ARM processors but it costs an ARM and a leg (pardon the pun).

LabVIEW is designed for data acquisition, analysis and presentation (of that data). It does that very well.

As Lul said, LabVIEW may be ok for mocking up a UI quickly, but  it's probably not a good choice for a vehicle infotainment system.

[LuI]

I do utilize LabVIEW especially for algorithm devellopment. For instance I have created a compression algorithm for continuous biological signals, that runs on low-power embedded 8-bit microcontrollers. There had been so many limitations that conventional libraries did not work for us. The final lagorithm had than be re-invented in C, but at that time we knew what to expect and what could be achieved.

And I have a bunch of test sequencers programmed in LabVIEW. Overall less than ~100 installations over time. Includíng controlling different devices, generating sophisticated signals, advanced signal analysis & test, professional reporting, database logging, process control etc.

I had been asked to sell the frameword as a product, but we decided the documentation and support effort is not worth it...

[Sibin]

In Vehicle Infotainment System using LabVIEW on the Process. This is just a Home Screen