@amrimed wrote:
i don't understand very well so can you add me with an example or a VI and thank you.
There isn't a VI that can help you understand this concept. You need to grasp the concept before worrying about asking someone to do your work for you. It'll be better for everyone involved.
First, you need to think about what happens when you push a button. Let's say when it's not pressed it creates a 0 value. When pressed, it creates a 1. This is done in hardware circuitry. But, it follows the old question about a tree falling in the woods making a sound. If there's nobody listening, there isn't a sound. If nothing is looking for the button press, there's no way to start an action. You cannot start your VI based on this button. That's why you were pointed towards the idea of a state machine.
In an embedded system, you want your VI to run on startup. That way, it's always running in the background and looking for the button press. Once pressed, it goes into a "state" that performs the task you have in mind. It's not a VI. Instead, it's a state. When you press the button again, it goes back into the original idle state. Doing this, you maintain the ability to read the next button press.
You should start by trying to make a VI that can handle this. Then, transition the idea to your myRIO
