LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

real weird labview behavior

Hello,
I have a vi that will work for hours or at times days, then it will hang with no error messages or obvious reason; the run arrow continues to show it running but its not. After I figure out the vi isn't working anymore, I hit the abort button and get the "resetting vi: dialog box. The only way to shut it down is to kill labview from the task manager. But then, when I restart labview, it doesn't work correctly and still appears in "processes" of the taskmanager, hogging lots of memory. Trying to kill it there gives an access denied dialog box. The only solution is to reboot.

I am reading several serial ports asynchronously and it appears to hang when addressing them. I have a NI AT232/16 card (PCI card with 16 serial p
orts). I am wondering if there is a timing issue reading different serial ports on the same card - any suggestions?
0 Kudos
Message 1 of 3
(1,262 Views)
Hi reniam,
May be easier for us to help if you can post your VI ... or, give us some details about:
- which are the serial related functions involved
- external device description
- other operations contained in your VI
- the speed at you are trying to communicate with external devices
0 Kudos
Message 2 of 3
(1,262 Views)
I've had this behaviour when something goes wrong in a low level hardware
access and an operation simply hangs, never timing out. The "resetting vi.."
dialog appears while Labview is waiting for the failed call to return so it
can closedown execution of the vi, but if it never does then there's little
it can do about it. My suspicion is that this is something with the card or
the card drivers rather than with Labview.

I assume you've already done a search (given it's an NI card) and found
nothing that seems relevant so all you can do is keep playing with it;
update the drivers if there's a newer version available and if that doesn't
fix it see if you can isolate the problem. Perhaps try changing things like
handshaking if you have the option to. And perhaps tr
y writing a "stress
tester"- a VI that opens one port for writing and another for reading,
connect a null modem cable between, send lots of data at different rates and
see if that makes diagnosis easier.


"reniam" wrote in message
news:50650000000800000035370000-1007855737000@exchange.ni.com...
> Hello,
> I have a vi that will work for hours or at times days, then it will
> hang with no error messages or obvious reason; the run arrow continues
> to show it running but its not. After I figure out the vi isn't
> working anymore, I hit the abort button and get the "resetting vi:
> name> dialog box. The only way to shut it down is to kill labview from
> the task manager. But then, when I restart labview, it doesn't work
> correctly and still appears in "processes" of the taskmanager, hogging
> lots of memory. Trying to kill it there gives an access denied dialog
> box. The only solution is to reboot.
>
> I am reading several serial ports asynchronously and it appears to

> hang when addressing them. I have a NI AT232/16 card (PCI card with 16
> serial ports). I am wondering if there is a timing issue reading
> different serial ports on the same card - any suggestions?
0 Kudos
Message 3 of 3
(1,262 Views)