02-08-2018 03:43 PM
Afternoon,
I'm currently supporting a client on site who is getting a VISA driver error message. The error starts as "Error - 1073807338 occured at VISA. Clost in Advanced Serial Write and Read.vi SubVI2.vi-> MAIN PROGRAM.vi". I've attached an image and the error log file. Any suggestions is gratefully appreciated.
Best,
Joao da Silva
02-09-2018 09:31 AM
Hello Joao da Silva,
Error -1073807253 is a framing error. Serial data is transferred one byte at a time. Each byte has a specific format with a start bit, data bits, parity, and stop bits. A framing error occurs when a byte of data is received, but it is not in the format expected.
Have you tried the application in another computer, or force reinstalling NI-VISA in the computer that your client is using?
02-09-2018 10:01 AM
Hello Oscar,
But the error message you posted is not the one that the OP is asking about.
The error message is:
Error -1073807338 occurred at an unidentified location
Possible reason(s):
VISA: (Hex 0xBFFF0016) The VISA driver failed to properly close the session or object reference. This might be due to an error freeing internal or OS resources, a failed network connection, or a lower level driver or OS error."
That is an error I've never seen before and would indicate a deeper problem with the drivers.
02-09-2018 10:05 AM
That's correct, RavensFan
I would still try in another computer, and force-reinstalling NI-VISA (and NI-Serial/NI-488.2 depending on the protocol they're using).
That way we can know if the error relies in a corruption in the driver, or if the application is performing tasks in an unsupported way. What do you think?
Regards,
08-20-2019 03:18 PM
Anyone get to the bottom of this?
I have a usbd cdc acm serial interface to a NordicSemi dongle that I programmed, and I occasionally get this error while pushing commands from the client on a LabVIEW VISA interface. Funny though, because a serial PuTTY interface never causes the error.
As an interesting side, the error is almost always associated with a fatal error on the dongle (the usbd interface). The dongle shuts the port and restarts the embedded application I programmed.
Not sure if it's the LabVIEW driver causing the connection to drop, but I don't get this error with other serial drivers. Maybe you should try alternates (PuTTY, RealTerm, HyperTerminal) to see if the behavior is consistent?