LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Visa Read Timeout

Hey Gerd,

thanks again for help.

I tried the Programm shown in your last snippet.

It still does the same as the previous one in a much smarter way. What would you do in the false case?

But i added an write to file, so that all received Data gets stored and at least you can check them after finishing the Vi.

I got the feeling it´s not working as i had planned it.

Greetings Gotti

0 Kudos
Message 11 of 14
(303 Views)

Hi Gotti,

 


@Gotti wrote:

I tried the Programm shown in your last snippet.

It still does the same as the previous one in a much smarter way.


Thanks.

General advice: the cleaner the code the less errors can hide within…

 


@Gotti wrote:

What would you do in the false case?


Nothing.

In your original VI you were only looking for that "Status/Error:" message to determine the two values within this specific message. Your code would ingnore all the other messages from your device (or: handle other messages incorrectly or not at all)!

When you also want to handle all the other messages from your device then you need to improve the string handling to recognize each message and store its specific data efficiently…

 


@Gotti wrote:

I got the feeling it´s not working as i had planned it.


The point is: what's your plan?

Did you create a nice Programmablaufplan before starting to code?

Did you learn about correct handling of serial communication as shown here?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 12 of 14
(296 Views)

Yes i did plan my programmstructure before i start programming.

As i understand in all previous help i got one step back and started to programm all interfaces with its planned functions in an individual Vi. The the modules them self work fine and did what they are specified for.

Know i am back at my first question and need to combine them.

As i did more research, i think the way to go is to start an Projekt and put them together.

Just found QUEQUED-Massage Handler as well the delacor QMH toolkit.

Is this in your eyes the way to go to avoid this parallel loops?

But for me it looks very complex and may a bit overshooting or is that just a lack of understanding?

When using message handler you would recommend the labview standart or the toolkit?

If you recommend it, can you recommend some explaining videos or sheets?

greets gotti

 

0 Kudos
Message 13 of 14
(289 Views)

Hi Gotti,

 


@Gotti wrote:

As i did more research, i think the way to go is to start an Projekt and put them together.

Just found QUEQUED-Massage Handler as well the delacor QMH toolkit.

Is this in your eyes the way to go to avoid this parallel loops?


Any project in LabVIEW should start with creating a new project in LabVIEW… 🙂

 

Why do you want to avoid parallel loops? (QMH or DQMH basically is a whole bunch of parallel loops!)

Parallel loops are needed to run independent code in parallel…

 


@Gotti wrote:

When using message handler you would recommend the labview standart or the toolkit?


Why do you want to use any toolkit to handle messages from your device? Which toolkit do you think of?

(And btw. in German and English is it "standard". Es gibt keinen Anlass, hier irgendeine Stand-Art auszuwählen! :))

 


@Gotti wrote:

If you recommend it, can you recommend some explaining videos or sheets?


Right at the top of the LabVIEW board you will find a list of "Training resources"…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 14 of 14
(283 Views)