LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Continuous Data Read/Write and Multiple State Machines

@crossrulz: That is a fair point. The reason I am keeping the state off the microcontroller is because I am using an Arduino and trying to conserve as much memory as I can. Currently the Arduino holds I2C code to retrieve and convert sensor data, wireless code to communicate it and I/O code to control the channels. I figured it would be better to allow the computer to do the decision making and have the MCU as a middleman.

 

@Bob_Schor: Thank you for the clarification! EDIT: I posted my reply before I saw your more comprehensive suggestion. Stepping away from my computer now but will take a look soon.

 

Best,

Yusif Nurizade

 

 

0 Kudos
Message 11 of 12
(967 Views)
A device would be a piece of equipment that has a single communications port. Say you have some sort of ethernet-based acquisition box that has 4 analog inputs. That should be treated as a single device because the inputs are not really independent of one another. Reading from one input could impact your ability to read the others.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 12 of 12
(954 Views)