10-26-2009 02:22 PM
I'm working with a Vi that is repeatedly used in the Teststand Sequence.I find the Vi works when It is called the First time but does not for the subsequent calls.
I tried the Unload options in the Properties - unload option and that did not help. I can use the File-' Unload all modules' to get it working but I would like to use an automated way of doing it.
I saw a post on the forum that talks about this problem,the solution entered there is for Teststand 4.0 and I could not relate it to the version I'm using(3.5)
Any ideas on how to unload a Vi after it is done executing ?
http://forums.ni.com/ni/board/message?board.id=330&message.id=17257&query.id=1043600#M17257
Thanks
Vamshi
10-26-2009 03:59 PM
10-26-2009 04:05 PM
Loading and unloading seems like a band-aid solution. The best thing to do would be to fix the VI so that it works every time it is called. You don't have much of a description of the problem except the VI does not work. What exactly does not work? Is there an error generated? If so, what?
Can you post the VI and a sample sequence that calls it?
10-26-2009 04:13 PM
10-27-2009 07:16 AM
Thanks for the information. I never thought it would be something to do with the Vi.Whenever I execute the Vi it works just fine,but when I call it from teststand it worked only for the first time.This made me doubt it is a unloading issue.
Info:
I'm working on CAN messaging,When I send a message (0X7E0) on the Bus,the module responds with the resquested information on message (0X7E8h). I'm using this Vi repeatedly in the Teststand sequence.
When I say the Vi does not work on subsequent calls,there is no error message,but just that It does not do its job,in case catch the response (0x7E8h) on the bus.
When I do the unload all then it works for any subsequent calls.
From your response I think I might not be closing/ending the Vi properly.I'm posting the Vi and any ideas to improve it is appreciated.
10-27-2009 09:07 AM
I don't use CAN so I'm missing those subVIs and obviously can't run it.
Your VI is messy and I did some cleanup to see what you are doing (attached below). What you could do is set a breakpoint and step into the VI.