Problem in visa write : error -1073807298

[DamienHTS]

Hello,

I have tried to communicate with the card using Hyperterminal and it is OK. The communication is good.

I have installed the full VISA driver and the problem is always here.

Now, I uninstalled the VISA driver on my computer and I re-installed this driver (NI-VISA 3.2f1) and I have the same problem.
With the debbuger I have seen the error code is generated by the VISA Write VI but the datas are sended.

I think it is a problem with the VISA drivers installation but I don't know what I can do... and what I can install...

[JulesSchmidt]

I have the same type of problem. I identified it with the following configuration : A PC W2K with LabVIEW FDS 7.1 and a virtual COM port done with an Advantech ADAM 4570 ethernet to serial port module.
The configuration worked properly with LabVIEW 7.0 FDS but doesn't work any more with the the LabVIEW 7.1 FDS. The only change is the 7.0 to 7.1 upgrade.
The physical COM ports are able to be written with the VISA write VI, but the virtual port generate the error -1073807298 on the VISA Write VI.
I upgraded VISA Libraries from the 3.1 version (delivered with my LabVIEW 7.1) to the 3.2 version available on this NI site. It doesn't change anything about this problem.
Notice that the virtual COM port works properly with it Advantech utility.

[Qia.sky]

Maybe you should add error handler to deal with this error

It is quit good if you pass this error,and visa read can work fine.

[BEHajder]

I am seeing this problem with LabVIEW 6.1.

I have a vi that simply opens a VISA session on COM1 and writes a string, then closes the session. The open succeeds, and the write is properly sent out the com port, but the write generates the error code -1073807298 as described in this thread.

I am temporarily working at home on a 1.8 Ghz Compaq with Win XP Home. I will try this on other PCs at work later.

I was wondering if anyone ever found a definitive reason for this error code?

[hancom]

I am having the exact same issue an I am running 8.2.  Also I have tried to use property nodes and set fewer properties and have no success in finding the issue.  Help please!

[Dennis_Knutson]

If you are having problems with a USB-RS232 converter, try the fix mentioned here.

[BEHajder]

Hello hancom, I never did resolve the cause of this particular error, I don't think it's related to a USB adapter as it occurred using a "normal" COM port supplied with the PC. In the heat of developing the customer's product, I worked around this error by checking for and ignoring this specific error code as a result of the VISA write. That solution seemed acceptable, as testing proved that other errors were still trapped and handled normally. This error is since specifically ignored in projects using serial VISA write functions.