Hello all,
I currently have a very frustrating situation in an application I am developing. Since it is in development, everything is kind of in flux, so if something crashes and LV has to rebooted, this is not a problem (just a little annoying). However, what is happening is that when I go to perform an operation on a serial port, my system crashes mid-connection - LabVIEW and all. When I attempt to restart LV and the application, the ports are found and valid but I get the error that VISA is not able to access them. This is the same error that is thrown when another system (or application) has control of the port. In this case, ALL programs have been shut down prior to restart so I am not sure what could be hanging on to the port. Here are some more observations:
- If I close LV completely and attempt to open a connection to the port in MAX, I get the same error.
- If I power off the device that is connect via USB232 and disconnect it from the computer and then turn it back on and reconnect the device, same result.
- Oddly, this device is reported as still present in MAX even when the device has been disconnected or powered off and I can not unistall the resource via Windows Device manager (image attached). Ultimately, the attempt to uninstall the device hangs and the system will have to be rebooted.
- Looking in Process Explorer (not the Windows Task Manager), I can see a running process LabVIEW.exe with the child nimxsoffline.exe running (image attached) even though there is no obvious instance of LabVIEW running on the machine. the process appears to be an unkillable zombie... the deadliest.
Currently, my only recourse is to reboot the computer. While rebooting works, this is an incredibly frustrating way of attempting to debug a program. I am running NI-Serial 4.1 which I uninstalled and reinstalled yesterday. ANY ideas will be much appreciated.
Cheers, Matt