labview abort button causes compac rio to shutoff

[cbt]

Ok let me try to explain this

Im running a chamber with 2 crios 9074

The problem im having is when i abort the vi one crio keeps my digital outputs in there current state which is what I want but the other crio turns off my digital outputs causing my system to vent my test pressure which i dont want.

This is also code that I have ran on other chambers which act like i want keeping the outputs in there current state I believe it has something to do with this crio setup or drivers.

Things I've tried

set all crio drivers like the others system didn't help

changed out the crio chassis

[vt92]

You should never use the LabVIEW abort button (on the toolbar) to stop a vi.  You should have a "soft" abort button on the front panel that shuts everything down in an orderly fashion before exiting the program.

Post your code and we can offer more detailed suggestions. 

[cbt]

I do that in the code but im still wondering why one rio acts one way and the other does it different when the abort button is pressed

[cbt]

any other advice?

[Zachmx]

Is there a reason you need to be aborting the VI? Could you deploy the code as a Real-Time Executable that runs at startup? This would allow you to headlessly and safely maintain the digital outputs.

As vt92 said, Aborting the VI is not recommended, especially when unexpected behavior could cause damage to your system.

[cbt]

I understand that but im still wondering why 2 crios with the same code and hardware act differently im going to triple check the wiring i thought the 9476 module would keep the state of the output

[billko]

I think the OP is trying to kill the vi on purpose to leave everything in an "up" state.  I think a modified suggestion of a "soft" abort is better.  Exit gracefully, but with everything up and running.

[Mark_Yedinak]

It is more likely than not a matter of timing. The abort simply kills everything and can leave things in unknown states. As things are getting the rug yanked from under them they may react differently. I wouldn't worry much about why it is happening becasue as stated, it is the wrong way to stop the system. It is by nature undefined.

[cbt]

both of the rios are on the same project and being read thru a local network would it be better if they were hooked in series?

[Mark_Yedinak]

---

@cbt wrote:

both of the rios are on the same project and being read thru a local network would it be better if they were hooked in series?

---

I don't think the network is the issue. Implement a proper shutdown and you will know and have control over what happens. Trying to understand and explain/control something that is by nature undefined is a futile effort.