Leaderboard

This library has a bug. The underlying Read VI should use byte arrays as input and output data and the Call Library Node should be configured accordingly for this parameter to be Array, 8 bit unsigned Integer, Pass as C array pointer. With the current C String configuration in the Call Library Node, LabVIEW will scan the string after the Call Library Node has finished, and terminate it after the first 0 byte (since that is how in C strings are terminated).

Your CLFN's are running in the root loop (that's why they are orange). You really need them to be set to "Run in any thread" but for that, your DLL has to be thread-safe. If it is thread-safe then change it. If not, you are stuck with what you have.

I know many people never go the route of using TestStand, choosing to roll their own sequencer and make it work (as I did once upon a time) However I'm starting to hear from a few folks who adopted TestStand and are going back to try to make their own sequencers (as I hope to never do) So, I shook the corporate tree some and have a meeting tomorrow for which I'm representing y'all, based on what I was hearing at NIWeek That being said, if any have gone the route of TS only to turn back, and you'd like your voice shared inside the guts of the mothership, please do share here. FWIW, If you've got specifics as to why you've never tried, that would be best for another thread. Thanks for understanding ~,~ The Captain was here Tag anyone you may know have done the same @Mark Yedinak@Mark Balla

All, Thanks for chiming in. I actually hadn't heard of the promise of TS Lite and will be sure to bug the powers that be about it. All in all, most things here resonate with the themes I've heard before and am glad to have ammo in hand to go to the conversation with, as it's gotten delayed; so feel free to keep chiming in. If I had to sum up the big points Cost: LV exe is free cheapest TS deployment gets 500+ Simplicity: Simple enough needs that can get away without the extra features in TS Parallelization: not easy to implement or visualize parallel tasks Training: Don't want to learn another tool myself to dev or for other people to use; just not intuitive enough API woes: Buggy in important areas; hangs between LV Data Access: Getting data around, into and out and between the modules can be challenging Deployment: Just doesn't go smooth History: Been burned before for one situation, why go back TestStand Lite: when please? UI Editor: complicated and overloaded to the point of distraction UI Tester GUI: Understanding components and creating in LV is an untenable beast I hope that is a good representation. ~,~ The Captain was here