LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in visa write : error -1073807298

Hello,

I have a problem in visa write. The error code occurred is -1073807298: VISA: (Hex 0xBFFF003E) Could not perform operation because of I/O error.

I want communicate with an extern component in USB. A driver (CP2101) convert my USB in virtual COM Port and I can use this COM Port for communicate in serial with the component. The USB is transparent. I use this like it is a serial communication.

I do a "VISA Configure Serial Port" and a "VISA write".

In my computer with LabView 7.0 development version, it is OK: No Problem.

But in another computer with LabView runtime engine and Visa runtime engine. It's not ok. The "VISA write" send the data and the component receive this data but the "VISA write" generate the error code.

I don't understand why?

Thanks for help me.

Damien
0 Kudos
Message 1 of 17
(11,010 Views)
Just a quick question:

Which runtime engines are installed on the other PC?
Is it the one for LV7?

Read page 2 of this link:

LINK

They refer to updating the version of NI-VISA.


-JLV-
Message 2 of 17
(10,998 Views)
I 've install the LV7 engine:
- NI LabView runtime engine 7.0
- NI VISA 3.0.0f5
They are in the LV7 Driver CD.

I can test to install the last version of the engine.
- NI LabView runtime engine 7.1.1
- NI VISA 3.2
0 Kudos
Message 3 of 17
(10,984 Views)
Hello

You write:
"But in another computer with LabView runtime engine and Visa runtime engine. It's not ok. The "VISA write" send the data and the component receive this data but the "VISA write" generate the error code"

So, the Visa write generates error and also sends the data?

Maybe you mean Visa Read. If this is a tru, check fierst if you have enough bytes in the buffer (VISA property node "Bytes at Port"), which you want to read. You might also want to check if the timeout is not a problem. Check LV examples for this.

regards
Pawel
0 Kudos
Message 4 of 17
(10,975 Views)
Hello,

No, It is the "VISA Write" who generate the error. And the data is transmissed because my card bip and respond.

I do a "VISA configure": it's OK.
I do a "VISA Write": I have an error code but my card bip -> that mean the data is transmissed.
I do a "VISA Read": I receive datas sended by the card.

The result is good but I have this error message...

Damien

PS: Sorry, my english isnot fluent...
0 Kudos
Message 5 of 17
(10,964 Views)
It is very diffucult to say what is wrong from what you explained.
I propose you debug you sequence with the "Highlight execution" turned on. Try to follow the error or set the debugger to stop on error. See where exactly the error is generated.

good luck
Pawel
0 Kudos
Message 6 of 17
(10,962 Views)
The problem is that the error doesn't occurred when I work on my computer with the LV7 development version.
The error occurred only when I am on a runtime version on another computer.
So I can't use the debugger.

And I'm sure that the error is generated by the "VISA write". But I don't know why?
0 Kudos
Message 7 of 17
(10,956 Views)
One thing to do is to turn on NI Spy to view the serial communication. I would also like to know if you use ASRL1::INSTR or Com1 as your VISA Reference Name. If you use Com1, change it to ASRL1::INSTR and see if that works. Com1 is a VISA alias and unless you modify the visconf.ini file, you will get an error. Installing only the VISA run-time does not create the alias.
0 Kudos
Message 8 of 17
(10,950 Views)
I use ASRL3::INSTR and my card is connected in the port COM3.
0 Kudos
Message 9 of 17
(10,945 Views)
Can you communicate to the instrument using Hyperterminal? I'm thinking that there might be a problem with the USB driver installation. Another thing to try is doing a full VISA installation and seeing if the problem goes away.
Message 10 of 17
(10,943 Views)