JCAndersen

We have our own TCP based library for this. It has been proven to be very reliable, also on wireless connections.

Let me start be stating that I do not for one bit believe that what you are seeing is a hardware problem. We abandons the use of Shared Variables / Network Variables over a decade ago. It was unstable and you could never know when it would suddenly stop working. And then it is a complete black box to debug. It may have become better since 2009 when I decided never to touch it again, but it looks like it still has problems.

Hi Filippo. My guess is that your "OK Button" has its mechanical action set to "Latched when released". Since you update the shared variable with the value from "OK Button" every 100 ms you will not even see the "Boolean" blink. I would use an Event structure in your "scada.vi" and create a "Value Changed" event for the "OK Button". In that event case I would update the shared variable from the "New Value" terminal. I would also create a "Value Changed" case for the "stop" button and wire the value from the "New Value" terminal to the loop termination terminal. Then you can remove the 100 ms delay. I hope this helps.

Yes, like drjdpowell says, you will find that the LabVIEW API provided by many instrument manufactures have been made on a Monday morning by an intern, just be be able to state in the marketing material that they have a LabVIEW driver. I have re-written many of those for scratch using the programmer guide and SCPI commands.

Well you have a clear race condition here when setting the "ActPlot" property in two parallel running loops, so I do not see how the behavior you describe is a surprise. It is working completely as one should expect.

Thank you dadreamer. You were right. It was that old version you mentioned. Out customer actually found the installer on an old network drive. I was for LabVIEW 6.0, and I have at all running now 🙂

Hi. I have received some code from a customer which is created with LabVIEW 8.2.1. It uses an old add-on tool for accessing an SQL database, but I cannot find that tool anywhere. I can see that the VI's I have are trying to load sub VI's from "<vi.lib>:\addons\SQL\Access" and then a number of different llb files. Can anyone her point me in the direction of which tool kit this comes from? Is it a very old version of the Database Connectivity tool kit or is it something else? Thanks.

Yes, there is many things wrong with this. What about the new adapter icons. What is the point of moving away from the well known product logos and just use the first letter of product name instead? It makes no sense.

I attended my first TestStand course in 2004 and have been working with TestStand on a regular basis since 2008. To me it seems that every one who has replied to this thread until now is making the most common miss assumption about TestStand: "TestStand is a test sequencer". Of cause you are right about that, but it is so much more. With TestStand you get a toolbox for creating your own test management frame work. This means that you as a test developer need to spend some time getting to know you toolbox, just like you had to learn how to program in LabVIEW at some point. An yes, TestStand is a complex toolbox to get your head around. That is the trade off for the flexibility you get. In the posts here I have not seen one challenge that I could not implement and make work in TestStand, just as easy or easier that in a custom LabVIEW sequencer. And when you are on the track with TestStand, you will realize all benefits like batch executions, reporting and property loading. Of cause you can implement and maintain all of this your self, but they are handed to you with TestStand and NI will maintain the fundamental function for you. However I do agree with Chris_Collier that it would be nice if NI provided a course on how to make high level architectures with TestStand. So I guess my point is this: Do not just buy a TestStand license and start using it out of the box as a simple test sequencer. You need to be clear about your goals for the test system, learn how to use TestStand and then learn how to implement you test system with TestStand.