LabVIEW
RT XNET Bus Off Recover
Hi Kevin,
Inside the print VI is just a call to the OS to add text to the screen, it affects timing just enough to make a difference, as it turns out.
I believe I am already working directly with a colleague of yours via email. We had a couple of recommendations to changes in Bus Off Recovery. First, we recommend against calling the XNET Stop VI when attempting bus off recovery. Calling the Stop VI then Starting again will lose synchronization with other hardware (not an issue in your particular case). I have filed CAR 310735 to look further into this issue or the Stop/Start timing combination. Second, we recommend adding an XNET Wait (Interface Communicating).vi to hold the code until the interface moves from bus off to error passive. Using the Wait VI could hold up other code, so it might be useful to move transmit code into a separate loop than other code. The default timeout of the XNET Wait VI is 10 seconds.
It's up to you, but I imagine the rest of this discussion can continue via email with your colleague. If so, I will take the time to post the highlights of our conversion back to here. Looking forward to working with you.
Just a side note, might be more useful to open a thread on the AEN or VeriStand Forum since I watch those more regularly.
I tried those recommendations yesterday, and it did not work. The only way I've ever gotten the interface to recover is with a stop then a start. I sent this to Ryan also, but I tried your suggestion and a bunch of combinations with the little example I created, and I put the ones that did recover from Bus Off in one folder and the ones that didn't in another.
