Can not recover from loss of serial communication

[billko]

Didn't you just answer your own question?

[cirrusio]

Not at all. This doesn't explain why the port would not be released.

[billko]

Sure it does - you exit gracefully, it closes.  You abort, it doesn't.

[sebster]

I've had something similar, and agree it is frustrating trying to do debug when you have to reboot everything.

What I did was make a new vi, and place a 'VISA Close' with the reference wired to a constant of the COM port. Whenever my main vi crashed, running this simple vi released the port to allow further debugging.

Hope this helps.

[cirrusio]

billko -forgive me, but your comment is neither helpful nor constructive and it is apparent that you have not read the thread carefully. It's not even clear to me what you are responding to above. My question was not how the problem it's created (this was apparent from the outset), but why I have to reboot our at the very least logoff. To be honest, this seems like an LV bug more than anything else. This made debugging very problematic and slow. I want to know how to avoid thisin the future and "code right"is a ridiculous response (correct, but ridiculous).

Sebester - thanks for the idea, but I tried this a while back and it didn't work for me.

[billko]

---

@mtat76 wrote:
billko -forgive me, but your comment is neither helpful nor constructive and it is apparent that you have not read the thread carefully. It's not even clear to me what you are responding to above. My question was not how the problem it's created (this was apparent from the outset), but why I have to reboot our at the very least logoff. To be honest, this seems like an LV bug more than anything else. This made debugging very problematic and slow. I want to know how to avoid thisin the future and "code right"is a ridiculous response (correct, but ridiculous).

Sebester - thanks for the idea, but I tried this a while back and it didn't work for me.

---

I don't think I could be any clearer than my last post.

From your post I originally replied to:

Soooo, the reason I was getting issues with the serial communication had to do with not properly closing the reference to the serial session (as I was testing I was essentially not closing and then opening up a new session on the port over and over again until something eventually just died).  Handling shutdown properly fixed this, but what I can't figure out is why LabVIEW wouldn't let go of the port eventually.

So that suggests to me that LV is working   Correctly.  You cleaned upafter yourself and it closed.  You didn't clean up after yourself and it didn't.  So which one of you is right?  The one that said your problem was fixed, or the one that said you're still having a problem???