LabVIEW
Computer freezes completely
This is a tricky one. So I thought I'd fish a little for suggestions.
We have a new Dell Precision 380, loaded with a NI-PCI 6509, and a 6023E card. The system monitors a couple of potentiometers and some digital inputs, as well as handling communication with an Atlas Copco Nutrunner.
There is also another application on the same PC written in VB6, that handles barcode code printing (on a serial request) and database integration.
Initially my LV (7.1) program ran fine. But after the VB6 applications and printer drivers were initially installed, something "broke" in LabView and I was no longer able to open the Properties of any VI. Uninstalling and reinsatlling LabView didn't help. Eventually I formated and reinstalled Windows and LabView; This seemed to fix the problem....until now.
To try and isolate the problem, I'll try running my LV program separately from the VB6 application. But in the end, the two will have to play nicely.
What I'm wondering is if there's a way to possibly find out exactly what's locking things up. I know there's a million possibilities for this one. I'm just curious how others might approach it.
Thanks.
We have a new Dell Precision 380, loaded with a NI-PCI 6509, and a 6023E card. The system monitors a couple of potentiometers and some digital inputs, as well as handling communication with an Atlas Copco Nutrunner.
There is also another application on the same PC written in VB6, that handles barcode code printing (on a serial request) and database integration.
Initially my LV (7.1) program ran fine. But after the VB6 applications and printer drivers were initially installed, something "broke" in LabView and I was no longer able to open the Properties of any VI. Uninstalling and reinsatlling LabView didn't help. Eventually I formated and reinstalled Windows and LabView; This seemed to fix the problem....until now.
To try and isolate the problem, I'll try running my LV program separately from the VB6 application. But in the end, the two will have to play nicely.
What I'm wondering is if there's a way to possibly find out exactly what's locking things up. I know there's a million possibilities for this one. I'm just curious how others might approach it.
Thanks.
Thanks for the reply Sam.
In this case I think I may have solved the issue. This is actually something we've seen before here. But it was a couple of years ago.
There really aren't too many things that will completely lock a computer like that. I had a suspicion that somehow the COM ports were involved, as they had been when this happened before.
On this PC we're using a PCI Serial Port expansion card from Lava. Until yesterday I had just been using the driver supplied to me by coworker. But when I looked on the company's website, I noticed they had another driver for the same model card. It seems that some cards were built with a different UART chipset, and these cards could experience "occasional lock ups". There was another driver for these cards. So far the new driver seems to have solved the problem.
If this hadn't worked, I probably would have tried running Winternals RegMon and FileMon in hopes of capturing the last files accessed to see if that would shed any light on what was locking up.
Hopefully I won't have to do that.
In this case I think I may have solved the issue. This is actually something we've seen before here. But it was a couple of years ago.
There really aren't too many things that will completely lock a computer like that. I had a suspicion that somehow the COM ports were involved, as they had been when this happened before.
On this PC we're using a PCI Serial Port expansion card from Lava. Until yesterday I had just been using the driver supplied to me by coworker. But when I looked on the company's website, I noticed they had another driver for the same model card. It seems that some cards were built with a different UART chipset, and these cards could experience "occasional lock ups". There was another driver for these cards. So far the new driver seems to have solved the problem.
If this hadn't worked, I probably would have tried running Winternals RegMon and FileMon in hopes of capturing the last files accessed to see if that would shed any light on what was locking up.
Hopefully I won't have to do that.
