LabVIEW
Error messages
Hi 99,
@labview99 wrote:
The problem is that when I have to push one button of the phisical machine because the cylinder has been stopped in the middle of the way I need to change the "dta receive" of the first subVI, without sending again the subVI
The motors I use send response messages containing actual positions and error flags. I can react on those values in a statemachine.
Your device also sends responses containing actual position - atleast you are waiting until setpoint and response are equal. Why can't you react on those values in your statemachine in a determined way?
@labview99 wrote:
The problem is that when I have to push one button of the phisical machine because the cylinder has been stopped in the middle of the way I need to change the "dta receive" of the first subVI, without sending again the subVI
Best regards
If you need to do this then you need to break up your first subVI to be able to do this. You have lots of states buried in that subvi. Bring those states to the top level and then you have more control. This may mean making more subvis (please do make icons that describe the subvi instead of using the generic icon - it will make your life a lot easier).
Your recibir datos.vi has a flat sequence structure. The code in each of those frames of the flat sequence structure represents a state of your state machine. If you divide those up then you can make decisions at each state, change values, etc. You may not even need to use a subvi - just do it all in the state at the top level.
Hi 99,
@labview99 wrote:
One qyuestion how can I convert hexadecimal to binary?
Why do you need this? You can AND/OR with U16 to test bits, too…
(There's a ToBooleanArray function.)
@labview99 wrote:
I think I have got it.
One qyuestion how can I convert hexadecimal to binary?
I hope you realize that hex, bin, and decimal are all the same numbers...
Can you share what you have tried? Have you brought the states from your subvi to your top level vi? One of your states would be to check to see if the cylinder has stopped moving. If it has stopped moving then you have a state which determines if it has completed its movement (it has gone to the right location) or it needs to continue. You then take the appropriate action. This is how a state machine works. It sounds to me, though, like you're still trying to use that terrible subvi that you were using earlier. With that approach you're not going to be able to achieve what you want to achieve.
