LabVIEW
Error messages appear to late
Hi 99,
how often have you been told to learn LabVIEW basics, including the mantra "THINK DATAFLOW!"?
@labview99 wrote:
The subVI has to error indicators which has to show in the main program and the problem is that the errors appears to late in the main program, appears when the execution finished.
The "error" is shown in the calling MainVI as soon as DATAFLOW allows…
(Exactly like you have it programmed to work!)
Are you sure you need a large sequence structure in the MainVI to call your subVI 5 times? Could a FOR loop do the same job - much simpler, much more readable?
Hi 99,
@labview99 wrote:
But if I execute the subVi only the error of REARMAR it works okey, but when I execute the mainVI it doesn´t work
The subVI executes the very same way if you call it from your MainVI or by starting it manually. So I guess this "it doesn't work" claim is wrong…
(There is another problem in the frame where you write "BARRERA INVADIDA" to the ERROR indicator, but this applies independently how you call that VI.
Also the indicator showing this "REARMAR" string has no label: NEVER delete the labels of frontpanel elements!)
Hi 99,
@labview99 wrote:
Now, I find the way to send the cylinder to different posiitons. But I want to take into account also de errors that can occur during the movement of the cylinder. Such as, the movement can be stopped because somebody invade barrier. And if that occur I want to rearm and send again to the position. And when I try to do this the cylinder doesn´t move.
It's fine you already started to create a statemachine in your MainVI. You should do the same with your subVI!
Your subVI can be improved and siomplified a lot, this is just a simple suggestion for the first step:
When you understand the code in this image then you should start to think about using strings to store numeric values: that's pure Rube-Goldberg!
The first frame(s) look like this:
Why is Velocidad a DBL value when your device only handles U8 data?
Why do you need to convert Posicion to a hex-formatted string? Simply convert the scaled DBL value to an U16 value and use SplitNumber to get both bytes. After doing so you can compare the resulting position with the setpoint position using both U16 values…
Hi 99,
@labview99 wrote:
Hi GerdW,
I have to convert to hex-formatted string because I need to do the opertion by numerical instruction.
No, you don't need to use strings to do numeric calculations! That's Rube-Goldberg!
Your subVI after some improvements - as suggested before several times!
@labview99 wrote:
But why in the mainVI after showing the message of REARMAR I sent to the case posicion1 of my case structure and the cylinder doesn´t move.
Where do you do this in the latest version of your MainVI? I cannot spot that…
(Btw. you should be able to answer that by using debugging techniques like probes and highlight execution!)
Hi GerdW,
I have simplifyed the subVI as you told me first.
The mainVI starts when I introduce one posiiton where I want to sent the cylinder. And when it reads this position the cylinder start moving. But, if somebody stop the movement, the program stops. So I want to show one message and then go back to repeat the subVI in the posicion1.
In this case, first I show a message of RESETEAR and then I want to go again to the first case which is posicion1. And in the case of posicion1, the program has to repeat again the subVI to move the cylinder to the correct position.
Doing this I am supossing that the movement of the cylinder is stopped in the middle and after showing the message of RESETEAR i would like to go to the case posicion1, to complete the movement.
Best regards
