01-08-2007 12:56 PM
01-19-2007 07:25 PM
Hi Ayman,
It sounds like it's not properly closing the session. By exiting LabVIEW, you are forcing LabVIEW to close down all open handles that were left open in memory. Obviously, we need to close them properly in your sequence to avoid having to close LabVIEW. I have some questions for you to help troubleshoot this issue.
How are you passing the CAN handles through your sequence? If you place a breakpoint at the step that calls the CAN close call, do you see that it performs this step? Which API are you using in CAN, the frame or channel API? How many ports or CAN objects do you open?
Regards,
01-22-2007 08:08 AM
Hello,
Thanks for your reply.
I am passing the CAN handles using FileGlobas variables
I have 3 CAN ports open and Yes it does execute the close operation which I placed in the cleanup step. I use frame API to close the channels with the VI called ncClose
Note: When i execute the sequence file on its own, not through the Labview interface, I get no errors no matter how many times it closes, which made is more confusing to pin point the problem.
Hopefully this rings a bell
Thanks,
Ayman
01-23-2007
02:45 PM
- last edited on
07-02-2025
05:19 AM
by
Content Cleaner
01-24-2007 01:07 PM
Hi Ayman,
Also, when you say you "use frame API to close the channels with the VI called ncClose", do you mean that you use the Frame API throughout your code for this port? You are not mixing the Channel and Frame API for this port, correct?
I assume you are just using the Frame API here, but I wanted to make sure.
Regards,