LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Reading COM : VISA: (Hex 0xBFFF0015) Timeout expired, before timeout (10 Sec) is over!

I read ASCII data from COM1 all day long, 4 string sections within 34 Char, write to an ASCII-CSV-file and if app is started read old data to display in variable time resolutions the data.
Is there any example-app near to this?
I am completely new to LabView.
I started with Basic2Port serial read write, getting above timeout message before specified timeout is over.

Usually my data comes every 5-8 seconds from an oil quality measuring sensor.

best regards
Frank from Achenbach Buschhütten GmbH, manufacturer of rolling mills
0 Kudos
Message 1 of 5
(2,964 Views)
Hello Frank,

Here are some further examples you might test with:
Serial Communication - Advanced Serial Write and Read
Sending and Receiving Serial Commands using VISA
Serial Communication for LabVIEW 6.1

Most of all serial communication problems are due to wrong port settings, so pleasedoublecheck cour serial configuration.
Here is a good knowledge base for troubleshooting serial communications:
Ingo Schumacher
Systems Engineering Manager CEERNational Instruments Germany
0 Kudos
Message 2 of 5
(2,955 Views)
Sorry, something went wrong with the last link.
Here is it again:

Serial Communication Starting Point
Ingo Schumacher
Systems Engineering Manager CEERNational Instruments Germany
0 Kudos
Message 3 of 5
(2,950 Views)
My actual program is reading, but often beginning initializing problems. It reads huge amount of bytes and more often than there is new data. The only good thing is - the starting bytes are still valid, although it is previous data..

I will attach my program in the actual version, that you can check it a bit, and please add some solutions.
0 Kudos
Message 4 of 5
(2,930 Views)
I think I dont understand the problem completely.
But there is one thing I noticed. I assume that one data telegramm is 34 bytes long - because you are waiting until there are at least 34 bytes before you step into the reading routine. But then, in the reading all the data that is present. Possibly it is more than one telegram, so there are chances that you allready read the beginning of the next datagram - information that, of course, will be missing if you try to interpret the data you are reading in the next iteration.
Try to read only 34 bytes at a time (leave the rest inside the buffer until the next iteration). If you are running into timing trouble, decrease the waiting time.
Ingo Schumacher
Systems Engineering Manager CEERNational Instruments Germany
0 Kudos
Message 5 of 5
(2,926 Views)