LabVIEW
Is there a recommended way to perform embedded Linux systems testing with LabView?
I think there aren't really standards for this. After all the protocol will depend a lot on the specific needs, the used tools and also on any possible company internal standards. This is not so much something about a new technology as much more about the problems of trying to standardize on a protocol for testing systems. Testing is a very broad field and there is no single protocol that would cover all aspects of it.
@MattFunke wrote:I've just been drafted into a programming team that is working on an SBC with embedded Linux. It's my job to write the SBC's end of the testing procedure; the other end will be a Windows XP PC running LabView 8 (Pro, I believe).Is there a recommended communications protocol and method to test embedded Linux systems with LabView -- using a particular Ethernet socket, say -- or is this so new that there's not much out there and it's up to the individual application?I'd just like to do this right. If there are strong reasons for recommending a particular protocol or method, I'd like to conform to them, so I'd appreciate it if someone could supply me with a pointer to where I could find them if they exist. Thanks for your time and consideration.
For production tests only you can go with the most simple and proprietary protocol you can come up with. If you need to be able to get into systems for remote monitoring after they have shipped to customers you will want to investigate into protocols that sit more or less on top of http so that they can easily be configured in firewalls and such to allow access to the units from specific adresses.
I would personally go for a rather simple ASCII based protocol where you can define your own commands and responses as the needs arise. With a little bit of forthought you can come up with something that is both easy to implement as well as futureproof by allowing to add new commands when you see the need.
Rolf Kalbermatter
