LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

only first sequence is being processed

Hi

I build a vi with this structure:
while loop{
case{
for loop{
sequences}}}
when I start it, only the first sequence is processed, then happens nothing, but there is no error message. Any ideas?
0 Kudos
Message 1 of 9
(3,182 Views)
Hello Robert,

if you would show us your vi, we could probably help 🙂 At the moment it could be everything.

Best regards,
GerdW
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 9
(3,174 Views)
How can I make it public?
0 Kudos
Message 3 of 9
(3,172 Views)
ah, i got it (hope so)
0 Kudos
Message 4 of 9
(3,171 Views)
Hello Robert,

from a first look everything seems to be ok.
But if you would use error clusters or some handles for your hardware communication then you would not need a sequence at all.
Now I only rearranged your vi to have a better overview.

It would be nice if you could save it as development distribution to include the subvi's. Or make a Zip-file with those subvi's.

Best regards,
GerdW
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 5 of 9
(3,162 Views)
ok, I got it out to save as .llb
Here you go
0 Kudos
Message 6 of 9
(3,157 Views)
Hello Robert,

wow that's big... And wow, you really like those sequences to have up to 22 frames...

So some quick advices:
1) Use more subvi's. I have changed your Write-vi's to use your "Write general.vi". They are much more readable now...

2) You should REALLY use the error cluster like provided by GPIB Read/Write. This way you can easily determine the erranous subroutine and you can get rid of those massive seuqences!

3) In "MM400" frame #3 you have a "stop". That's not good. You never know at which point your program stops. That's why you should use an error cluster...

4) Can you split your MM400 into several subroutines doing only one control parameter? You have so many input terminals, that's confusing 🙂 And you don't see those terminals in the block diagram because of this big sequence...

Hope this helps for the moment,
GerdW
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 7 of 9
(3,148 Views)
Thanks GerdW, I´ll try those error clusters, hope they will help me.
0 Kudos
Message 8 of 9
(3,146 Views)
Hello Robert,

an error cluster will surely increase the readibility of any vi doing hardware in/out...
See the example pic.

Best regards,
GerdW
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 9 of 9
(3,143 Views)