Hi,
I'm developing a project which requires a desktop computer hosting a LabVIEW application to control the state of a RT target (myRIO). The problem I'm running into is that I'd like to be able to control what phase the RT target is working in, such as Initialize, Configure, Shutdown, Idle. This seems to call for a State Machine design pattern, but the trouble is that I'd also like to make sure that the data these different states are dependent on are configured appropriately before they're exectured.
So my question is as follows:
Is there any existing design pattern that allows us to reliably queue up different states to control a real time target, whilst ensuring that every time we queue a 'Configure' state, for example, all of the data that the Configure state is dependent on is queued with it?
What I've been thinking:
I've been thinking that an array of desired states could be held within an object, and that we're only able to read the state of the object publically; setting the array is private to the object. A set of publically accessible methods to that class could be called so that for each addition of a new state to the state queue would be done through a SubVI, whose connector pane defines the data dependencies. However I'm not sure how you'd get this working between both the PC and the RT target, since LVOOP is pass by value rather than pass by reference.
I'd really like to hear your thoughts.