Automated tester of circuit boards

[cmhand]

So you are saying that every wait step should have its own frame in the stacked sequence??? Such as you were saying in frame 4 apply 12V to machine in one frame, then the next frame is just wait 1.5 seconds, and then move on to the next frame??? I dont understand why you guy are all bashing the stacked sequence because everything I want it to do is working just I would like to clean it up with all the LEDS, how do I have just one LED for each ACC Cold, Ignition, and 12V machine(console) that can be activated when needed from sequence to sequence??? If you guys suggest using a state machine can you send me a very simple version that I can try to work off of...I found an example from the examples developed by NI but it kind of confuses me. Ill attach that example too and maybe someone can edit that for me or try to explain it.

[Dennis_Knutson]

Have you considered what to do if, for example, test frame x fails and you want to skip the rest of the tests? Have you considered what to do if you get some sort of error, want to clear it, and restart again from where the error happened? The stacked sequence structure is completely infexible. Once started is has to run each and every frame and in a completely fixed manner.

What exactly is your question about the example. It's actually one of the simpler ones.

[cmhand]

The property node and all the random logic gates at the bottom of the while loop, is this necessary for my application???

[Dennis_Knutson]

The logic is actually pretty simplified. In a more complex test sequencer, it can be much worse.

All the logic does is stop the while loop if all of the tests have been executed or stop if a failure occurs AND the Stop on Fail button is true. The property node is just used to get the number of tests to perform. This VI is a bit different than the shipping example but the principle is the same.

[cmhand]

Im going to develop something quick and can you let me know if im going in the right direction...I added a few frames and what they are supposed to do...I still dont know what needs to be connected to the bottom left corner to the array size...sorry if this is a pain to you its just really frustrating trying to do all this from scratch.

[cmhand]

so this is what I have so far and am stuck from here. I have all the steps I need to do in the case structure. For anyone that is just tuning in what I am trying to do is test circuit boards one step at a time. Each step will be a frame in the case structure. Not exactly sure if my logic outside the case structure is right because I just copied and pasted it from the example state machine tester attached earlier. I dont know what I need to hook up to my case structure...any help would be great.

[Dennis_Knutson]

Here's a modification that you might want to look at. In the most common usage, a shift register and enum are used in a state machine. In each state, you select the value of the enum to define the next state to execute. In this example, there is no logic to determine what the next state should be. In a more robust implementation, you would determine the next state based on some results. In something more robust, you would also want to use a type def for the enum.