LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI works Execuable does not work

ok, from the first smaller screenshot that might be confusing, so here the explanation:

 

part one are the outputs, (valve settings, etc):

(for better handling i keep an Boolean array with the status of each Output)

WWolf78_0-1644605417539.png

 

 

part two are the "non critical" input signals:

WWolf78_1-1644605514711.png

 

part three are the critical Inputs,

WWolf78_2-1644605567184.png

 

so i store them in the Cluster:

WWolf78_3-1644605595640.png

 

 

main reason is the security handling:

additional to the three Loops of the QMH I created a fourth on, which only handles security issues (like open housing, emergeny button,..)="Task Sec"

for handling those Inputs  in another loop I had to create this in another "section" as accessing from two loops in the same task array does not work.

0 Kudos
Message 11 of 17
(656 Views)

Him GerdW

 

thanks for the input, I hope I could clarify the first points of your reply,

 

the other ones:

 

 

  • Using BytesAtPort to determine the number of bytes to read is considered "non optimal" behaviour…
    • I know, when I was programming, this was in in the examples so I kept it.additional it works.
      BUT: if I have time, I'll replace this
  • Using local variables when the terminal is unused is considered "bad style".
    • where do I do this??
  • Using locals when a shift register should be used is considered "bad style".
    • where??

 

0 Kudos
Message 12 of 17
(652 Views)

Hi Wolf,

 

@WWolf78 wrote:
Using local variables when the terminal is unused is considered "bad style"
where do I do this??
Using locals when a shift register should be used is considered "bad style".
where??

Look out for "Enum message out". Both times…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 13 of 17
(647 Views)

ah, I'm using this only for debugging. thereby at debugging I can see which case was used, so this is nothing for the GUI or the user

 

back to the main question:

why does this not work?

 

I think I can exclude the file path.
I take a look at the folders and the Program does create the Logfile and it has content, so this works

 

so it remains:

VISA Configuration

and initialization of the I/O's

 

any suggestions what the error could be?

0 Kudos
Message 14 of 17
(610 Views)

Hi Wolf,

 


@WWolf78 wrote:

so it remains:

VISA Configuration

and initialization of the I/O's

 

any suggestions what the error could be?


Which errors do you get for both items?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 15 of 17
(604 Views)

the I/O's does work, as after initialization I check some of those and thereby I get no Error, so this works

 

when I try using the Serial communication I get this one:

 

WWolf78_0-1644826288147.png

 

0 Kudos
Message 16 of 17
(598 Views)

ok, got the source for this one:

 

it was the invoke note at the beginning from the VI.

after deleting I don't get the error any more

 

WWolf78_0-1644828631509.png

 

and very curious:

now the VI and the serial communication works


now I'm confused


ok, additional I've disabled the checkbox here:

WWolf78_1-1644828799543.png

 

could have been this the reason?!?

 

0 Kudos
Message 17 of 17
(589 Views)