Hi, all,
Could some of the gurus here help me out? I need to advise a customer tomorrow about whether they should chose LabVIEW or Measurement Studio as an ADE for TestStand. The application will be engineering system test of a life-critical networked system, especially at large scales.
LabVIEW looks like a nice stable product, but I'm concerned about the level of difficulty of using it in this context. This may be my newness or something intrinsic. But the lack of something as basic as a Map VI or class is worrisome (as are the gyrations that the people who developed the prototype had to go through in a different thread.) Even something as basic as getting a VI to retain a value (memory) seems difficult.
For instance, configuration. The customer wants to load configuration info dynamically to keep it synchronized with their own hardware configurations. In the context of LabVIEW's seeming aversion to memory, does this mean that every test step in TestStand is going to have to reconfigure the system?
I'm not crazy about locking into .NET technology (having read the "Choosing the Right ADE" document,) but I just wonder if the dataflow paradigm is going to create a lot of trouble needlessly.
Any help appreciated.
Thanks,
- Steve.