Error -1073807343

[njf1003]

My LabView program had been running just fine until today when I'm getting:

Error -1073807343 occurred at Old VISA Open in port init.vi->upconversion4.vi

Possible reason(s):

VISA: (Hex 0xBFFF0011) Insufficient location information or the device or resource is not present in the system.

Previously when I've gotten a VISA error I've just restarted the computer, but that isn't seeming to work this time. 

The problem occurs when trying to control a newport stepper stage. Their supplied software will still run the stage so it's just something going on with LabView.

[kosist90 · Accepted solution]

Usually this error occurs, when COM port value (or another type of VISA alias name) is not present in the system/is changed. You've uploaded VIs without drivers VI, so I can't see how serial communication is implemented, but I noticed, that port init.vi does not have VISA reference input. Thus, it is hardcoded inside of that subVI.

So I suggest to open that subVI, and verify, that VISA reference value is the same, as COM port where your device is connected.

Sincerely, kosist90

Check out new features of LabVIEW 2017!

[billko]

Oops, misread the post.

[njf1003]

Thanks!

The VISA reference value had changed some how so I had to change the Serial port number being fed into that sub VI so the right VISA reference input was generated.

[billko]

---

@njf1003 wrote:

Thanks!

The VISA reference value had changed some how so I had to change the Serial port number being fed into that sub VI so the right VISA reference input was generated.

---

Just so you understand, you are treating the symptom, not fixing the problem.  The problem is that the COM port is changing.  That's the problem that should be fixed.  Could it be that this is a USB to RS-232 adapter and someone unplugged it and then stuck it back into a different USB port?

[njf1003]

It is RS-232 to USB. I'm pretty sure it's always been plugged into the same USB port though. I did run several Windows software updates between when it worked and didn't so maybe one of those changed the COM port? 

[billko]

---

@njf1003 wrote:

It is RS-232 to USB. I'm pretty sure it's always been plugged into the same USB port though. I did run several Windows software updates between when it worked and didn't so maybe one of those changed the COM port? 

---

Hmmm, I can't really see any reason for it to change unless someone changed it.  This is very strange.  I've seen computers do weird things when waking up from hibernation, especially hardware-wise.  Do you think this might have been the case?

[njf1003]

Probably something like that.