Why wont these globals update?

Question

I have only used globals once or twice before and they always seemed to work out for things like one VI running in the background continusly polling an instrument then have other VI's just read the global.
That does not seem to work in this case. The arrays in the global never change and are always the default value.
I know you will not be able to run the attached code without one of our boards, but at least you can tell me if I am doing something that is just plain wrong....
Attachments:
Login and Get Analogs And Descretes Continus Folder.zip ‏367 KB

Answer 1

RTSLVU wrote: 
The VI's work fine on their own and I tossed in the globals so other vi's could use the data. I thought that's what globals were for?
You mean the VI that you posted worked fine?   Globals in LabVIEW....  Well your statement is correct for text-based languages.  For LabVIEW, other than giving headaches and storing static data, I'm not sure what else they are good for..  (we often have debates on the subject )
RTSLVU wrote: 
I looked at the "Action Engine" example and
don't really understand it...
Action Engines or Functional Globals are not that complicated.  Functional Globals uses an un-initialized shift register to keep the last value from the previous run.  So they are often used as a means of sharing data.  Their safety (or safeguard) is that the Functional Globals use states to initialize, write a new valus, read the last value, and optionally reset the value (although initialize may do the same thing).
RTSLVU wrote: 
The locals in that
reinilialize the indicators in that vi are because I was worried about
stale data. I had noticed during development that fir instance
the "Image$?" indicator would still be true from the last time the VI
was called, maybe I am over thinking it as teh indicators are only there
for trouble shooting?
You should initialize values on wires outside a loop (before entering the loop).   And you should avoid using Locals at all cost.  The variable in LabVIEW is the actual wire, so there is no need to "pass" a value.