You are on page 1of 1

1. labVIEW Architecture?

1,State machine with String meassage or Queue based(Such as JKI State machine): This is
traditional way to write LabVIEW code, but this is a single task achitecture,if I setup a high
speed DAQ and analysis system. This achitecture is limited for this kind of application,
because DAQ system should have 2 task: Data acquisition and analysis,even data storage.
So how to use this type of state machine for multi task application?
2,Engine based State machine architecture: Setup some engines(DAQ engine,Error handler
engine,Data analysis engine),LabVIEW UI just control the engine run mode, using message
queue to communication with various of engine. I don't know how to use it in Run-time
mode,because this architecture is based on Queue message and Dynamic call mechanism.
so the engines should be VI rather than EXE.
3,LabVIEW OOP architecture: I hardly use this architecture

You might also like