Error -1073807346 on NI-VISA

[mimi345]

I have build a program that connect a USB serial to the computer using NI-VISA. It was successful running without any error for more than a year. But now, the error box has pop-up both on development and deployment computers. I'm using LabVIEW 2012 SP1 & NI-VISA 5.3 version on Windows 7. I have check all the passports in the listbox but still got the same error. Do you have any idea why this thing happened now? What should I do to resolve this error? Thank you.

[JÞB]

It would really help me help you out if you mentioned what the device is.  Or even if it's a VCP, TMC or GPIB via USB. Perhaps even show the device IN MAX And windows device manager.  Better yet,  link the manual!  Yes, we can help RTFM for you but, there are lots of USB devices and even I haven't read all of their manuals. 

Really wild guess.  Has someone been unplugging the device and plugging it into a new port? 

[mimi345]

I'm using ATEN USB to RS-232 adapter. Even if someone has unplugged the device and plugged it into a new port, the comm port has been set to same new comm port as well.

Here is the link to the ATEN USB manual. https://assets.aten.com/product/manual/uc232a_um_w_2017-05-04.pdf

What is other possibilities that cause this error? I'm really sure its not happened because of the wrong port.

Thank you.

[JÞB]

Get a better converter.

Prolific does take liberty with the R in RS-232.

And, that does not tell me what the device you are communicating with is. 

PS: the RS in RS-232,422,485...is short for Recommended Standard.  AKA "My firmware engineer SAYS that he knows what to do...."

Yeah, at 77 baud on a 60mA DC teletype loop....programmed originally on punch cards!

[Bob_Schor · Accepted solution]

As is often the case, the problem is either Hardware or Software, and you haven't given us enough information to help us "guess" which it might be.

Hardware:

• What is the device that plugs into your RS-232-to-USB converter?
• What are the specifications (Baud Rate, Parity being the most important) of this device?
• What do you know about its "communication protocol", i.e. how to "manually" talk to it?

Software:

• Attach your relevant VIs.  Don't bother with pictures (unless they are executable-ready LabVIEW Snippets).

Suggestion for tests:

1. Plug your RS-232-to-USB device into a working USB Port on your LabVIEW PC.
2. Plug your serial device into the Serial Converter.
3. Start MAX.  You should be able to identify the "device" that is your Serial Device.
4. Open a Test Panel.  Set up the Communication Parameters.  Don't forget to configure VISA Termination Character (if your device uses one, of course).
5. Try to "talk" to your Device.  Usually there is a "Initialize" string you can send that wakes the device up and gets it to send you its ID.  See if this works.
6. If so, see if you can give it the "Send me Data" command, and see what comes back.

If this all works, be sure your code is doing much the same thing.  If it doesn't work, provide answers to the Hardware and Software "Unknowns" referenced above, and we'll check out your code and think about your devices.

Bob Schor