VISA: (Hex 0xBFFF0015) Timeout expired before operation completed.

[Gabess]

Hello , 

I just installed inf file from NI VISA Wizard for T-10 Illuminance meter from konica Minolta . Then , I try to test it on NI Visa Test panel but it shown that time out expired . I already try change the bit, baudrate, and parity but it does not change anything . I also try to add some delay after VISA open using node property. But the result is same. 

Thank you . 

[AeroSoul]

Timeout property node is a VISA setting, it does not actually add any delay to your code.

Longer wires also do not cause any delay.

What i recommend is to read user manual of the device, there should be settings written in there, without user manual all we can do is guess.

---

[GerdW]

Hi Gabess,

---

@Gabess wrote:

I also try to add some delay after VISA open using node property.

---

You don't "add some delay", but you set a timeout value: that is a difference…

Even though your image looks like a snippet it seems it is not a snippet: LabVIEW does not recognize the code and so we cannot run/edit/debug your image. Especially we cannot check that string constant for its display mode: when you use the wrong display mode then your device will not recognize the command (correctly)!

Maybe there is a timeout because the data take too long to travel along all those bended wires!? (Mind to use AutoCleanup on your code?) 🙂

[Gabess]

Do you mean the data is baudrate, byte and parity? I didnt find any datasheet about this product, i already try contact the manufacturer. if i have more information about this product i will tell you more detail. I made mistake, i assume time out = time delay, that is my bad. Thank you for your response. 

[Gabess]

Sorry about this i using labview 2011 but i did using snippet from VI. But its okay that my mistakes, I i will attach the vi. I admit i made mistakes about misconception between time out and time dela 🙂 I assume it same thing. Okay i will try to clean up all the wires sir, thank you for response. 

[GerdW]

Hi Gabess,

---

@Gabess wrote:

I i will attach the vi. I admit i made mistakes about misconception between time out and time dela 🙂 I assume it same thing. Okay i will try to clean up all the wires sir, thank you for response. 

---

Use the AutoCleanup tool to clean the wires…

See this:

(After cleanup, with comments.)

[Gabess]

Dear Gerads,

Since my LabView is lower version i cant import it into vi, but its okay i remake it  by my self and make it more tidy. The result still same thing Gerads, Thank you for your response. 

[Gabess]

Hello I got the information from the third party .

Baudrate: 9600

NPLC: 150 

data bit:7 bit

parity: Even 

stop bit: 1 bit

I adjust all the settings to this setup but turns out the result same thing. I read a book to determine the time out should be like 100 (constant) x150 (instrument nplc) /60(power source nplc) = 250 s. 

 . 

[AeroSoul]

I think you misunderstood GerdW, you DON'T NEED 70 second delay before reading values. You need like 1 second and even this can be an overkill.

EDIT: I saw your response too late. 250s is definitely way too much, maybe 250ms or 2.5s, but 250s is crazy.

[GerdW]

Hi Gabess,

---

@Gabess wrote:

Hello I got the information from the third party .

Baudrate: 9600

…

data bit:7 bit

parity: Even 

stop bit: 1 bit

---

Then your VI should look like this:

---

@Gabess wrote:

NPLC: 150 

I read a book to determine the time out should be like 100 (constant) x150 (instrument nplc) /60(power source nplc) = 250 s. 

---

Which book did you read? Can you provide a link to a PDF?

A timeout of 250s (or 70s like in your VI) is not reasonable: even the slowest devices I had to work with responded within less than 10s…

What's the point of waiting for 150 NPLC (number of power line cycles) when requesting the device ID response???

Does your device even understand that command?

Btw. you REALLY should watch this video on "proper way to communicate over serial"!