LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dequeue not executed

Solved!
Go to solution

I am the one sending data manually using XBEE module and probe window. I'll work on your suggestion. But how can we check the data of the string queue? do we use "get queue status"?

 

And, the cases you refer are: 1st case (1A0 and the others) and 2nd case is what?

0 Kudos
Message 11 of 21
(1,622 Views)
Solution
Accepted by PJason

Hi PJason,

 

So what can you suggest with the architecture?

What do you want to achieve?

Using a queue to decouple processes is quite common and recommended.

 

Maybe you first should make sure your processes (like that VISARead) is running smoothly and correctly…

 

And, the cases you refer are: 1st case (1A0 and the others) and 2nd case is what?

The other case is "default", when no tag of your tag list is found.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 12 of 21
(1,622 Views)

Yes, the VISA functions perfectly after I applied the suggestion of 

 

 

0 Kudos
Message 13 of 21
(1,615 Views)

I've tried your solution and it seems that VISA read would only send the data once a timeout occurs and the data are in bulk. Also, the middle loop simply just matches the index of the current data and ff its true, the index will increment and starts match again with using the previous index

 

And as I what have observed, the response of the VI somewhat slows down. I'm confused now, please enlighten me. Please see the attached VI if there are any mistakes I've made

0 Kudos
Message 14 of 21
(1,608 Views)
Solution
Accepted by PJason

Even Now It wont work as Expected as you are dequeuing two queues in the same loop, as you wont get data for both queues at same time, so it will wait till both gets dequeued.

----------------------------------------------------------------------------------------------------------------
Palanivel Thiruvenkadam | பழனிவேல் திருவெங்கடம்
LabVIEW™ Champion |Certified LabVIEW™ Architect |Certified TestStand Developer

Kidlin's Law -If you can write the problem down clearly then the matter is half solved.
-----------------------------------------------------------------------------------------------------------------
Message 15 of 21
(1,600 Views)

Hi PJason,

 

it seems that VISA read would only send the data once a timeout occurs and the data are in bulk.

You have configured your VISA connection to wait for TermChars. (Read the help for VISAConfigureSerialPort!)

That's why I removed BytesAtPort: the VISARead will output the received string as soon as it receives the configured TermChar! As it seems you don't use such a TermChar (or the wrong one) and VISARead waits until the timeout occurs: either set the correct TermChar or read just 3 chars (as it seems that's what you want)!

When reading just 3 chars: keep an eye on synchronization between your sender and your VISARead loop. (Using a TermChar would make that much easier…)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019