{"id":28,"date":"2008-10-22T00:11:24","date_gmt":"2008-10-22T05:11:24","guid":{"rendered":"http:\/\/chrismeyer.org\/wordpress\/?p=28"},"modified":"2009-05-12T14:10:50","modified_gmt":"2009-05-12T19:10:50","slug":"labview-shared-variable-engine","status":"publish","type":"post","link":"https:\/\/chrismeyer.org\/wordpress\/?p=28","title":{"rendered":"LabVIEW Shared Variable Engine"},"content":{"rendered":"

I spent more than 20 minutes trying to figure out the LabVIEW shared variable engine so it’s worth writing about.\u00a0 My objective was to test the shared variable engine across multiple networked computers, if you are just trying to get the shared variable engine running this post applies to you as well, but you should not follow the steps to configure multiple computers.<\/p>\n

The first note, is that they have a good page write up regarding shared variables here<\/a>.\u00a0 After reading a little bit about shared variables you should open up LabVIEW, go to:<\/p>\n

Help – Find Examples. . .\u00a0 and search for shared.\u00a0 This will bring up a list of shared variable examples.\u00a0 Open up the “Shared Variable Client – Server.lvproj”.<\/p>\n

\"\"<\/a><\/p>\n

Now expand the server.lvlib and run “Variable Server.vi”.\u00a0 Once you have this up and running, go back to the project explorer and now expand clients.lvlib and run any of the VI’s from this category – ie: “Data Item Binding Client.vi”.<\/p>\n

Now you should have something that looks like:<\/p>\n

\"\"<\/a>

Running Server<\/p><\/div>\n

\"Client<\/a>

Client Receiving Data<\/p><\/div>\n

What’s happening is the LabVIEW project is sharing waveform information from the “server” in the form of TCP (I had UDP here, it’s clearly not as this would not have any confirmation of packet receipt – TCP vs. UDP<\/a>) information packets and the “client” is listening to the waveform data and initializing communications by sending the server it’s Client Name.<\/p>\n

If you want to get this example running across multiple computers you can see some useful information here<\/a>.\u00a0 The idea is that you need to now repeat the above steps on another computer, only this time DON’T open and run another server, we’re going to get the Client to read data from the other computer!<\/p>\n

First step is to repeat the above and get the example project open on another computer.\u00a0 Once you have the project opened up, let’s choose to get data from the other computer who is running now as a server.<\/p>\n

First double click the “bound waveform” variable so we can choose where to get data from.<\/p>\n

\"Double<\/a>

Double Click Bound Waveform<\/p><\/div>\n

Now check the box “Bind to Source”, and click Browse… and find your other computer who is acting as the server.<\/p>\n

\"Bind<\/a>

Bind to Source; Browse. . .<\/p><\/div>\n

\"Select<\/a>

Select Remote Server<\/p><\/div>\n

\"Note<\/a>

Note Change in Binding<\/p><\/div>\n

Now go back and run any of the client VI’s and with any luck you should have data running from the server to each of the clients successfully!<\/p>\n

\"Open<\/a>

Open a CLIENT on Another Machine<\/p><\/div>\n

If you create your own VI’s it’s very simple to create shared variables, just right click the project, go to new variable and configure it just as you’ve done above and you should be off and rolling in no time!<\/p>\n

<\/p>\n


\n<\/p>\n

<\/input><\/p>\n","protected":false},"excerpt":{"rendered":"

I spent more than 20 minutes trying to figure out the LabVIEW shared variable engine so it’s worth writing about.\u00a0 My objective was to test the shared variable engine across multiple networked computers, if you are just trying to get the shared variable engine running this post applies to you as well, but you should […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,21,11],"tags":[],"class_list":["post-28","post","type-post","status-publish","format-standard","hentry","category-college","category-labview","category-mechanical-engineering"],"_links":{"self":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/28","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=28"}],"version-history":[{"count":10,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/28\/revisions"}],"predecessor-version":[{"id":45,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/28\/revisions\/45"}],"wp:attachment":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=28"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=28"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=28"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}