LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

reading shared variables

Hi There,

 

I hope your well this afternoon.

 

I am attaching some example code for you to try. When you open it, make sure you Deploy All on both lib1 and lib2 to create the process in the DSM. Then run the writer VI first, and then the reader VI. You should find when changing the switch, the LED lights up, the DSM status of both variables updates (to true) and the reading VVI indicator goes true also. 

 

Also notice the timing in both VIs, of about 100ms. Your reading VI must read slower (or at the same rate) than the writer, otherwise you'll read repeated data. 

 

I hope this finds you well, 

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 11 of 13
(1,023 Views)
screen shots of how vi are now
0 Kudos
Message 12 of 13
(1,014 Views)

Hi There,

 

I am afraid the images havent help me much.

 

Have you tried any more of the above advise I have given, regarding the LabVIEW fix and my simple code to test shared variables and binding?

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 13 of 13
(1,003 Views)