LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA: (Hex 0xBFFF006C) An overrun error occurred during transfer.

Hi wise NI LabVIEW people,

 

I am getting the following error and I am a learner in LabVIEW so please suggest a solution.

Error - VISA: (Hex 0xBFFF006C) An overrun error occurred during transfer. A character was not read from the hardware before the next character arrived.

 

I am reading Temperature, Pressure and Flow value from a TSI flow meter. For your reference, I attached the vi that controls the flow meter.


I hope I could explain the issue. Please feel free to ask questions for more discussion. Thanks for your time.

0 Kudos
Message 1 of 19
(728 Views)

Hi Raj,

 


@HarshRaj18 wrote:

Error - VISA: (Hex 0xBFFF006C) An overrun error occurred during transfer. A character was not read from the hardware before the next character arrived.

 

I am reading Temperature, Pressure and Flow value from a TSI flow meter. For your reference, I attached the vi that controls the flow meter.


Please feel free to ask questions for more discussion.


No, you did not attach your VI to the message…

Read from VISA more often or request more bytes per read.

All the inportant stuff is explained in this excellent video!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 19
(724 Views)

Hi,

 

How do you do buffer flushes? I am also facing same type of issue but not able to resolve it.

0 Kudos
Message 3 of 19
(722 Views)

Hi Raj,

 

please keep your discussion in one place…

 

Flushing the buffers is only a bandaid!

I repeat: all the important stuff is explained in the video linked in my previous message!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 19
(714 Views)

Hi GerdW,

 

Thanks for the video, I'll check it. I hope you can see the Vi now.

0 Kudos
Message 5 of 19
(704 Views)

Hi Raj,

 

did you notice my signature line?

Could you please dowconvert your VI for an older LabVIEW version and attach again - I prefer LV2019 (File->Save for previous).

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 19
(700 Views)

Do you have a link to the manual of the device you are trying to communicate with?  We need something to reference to make sure you are talking to it correctly.  I suspect you need to add a button to conditionally write your command and then still try to read every loop.  But, again, I need to manual to verify this.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 7 of 19
(680 Views)

Hi,

 

Thank you for your suggestions. Here is the manual of the instrument 4100.

https://tsi.com/getmedia/ded05ee1-b119-4b66-8709-114e4f074c73/4000-4100-RS-Command-Set-1980340L-web?...

 

On the page 7, it mentions that both the buffers are 50 bytes, if that is helpful.

0 Kudos
Message 8 of 19
(630 Views)

Hi GerdW,

 

Here is the 2019 version of the vi for your kind look into it.

0 Kudos
Message 9 of 19
(626 Views)

Hi Raj,

 


@HarshRaj18 wrote:

Here is the 2019 version of the vi for your kind look into it.


Nope, you saved for LV2023 now…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 10 of 19
(620 Views)