02-05-2018 11:40 AM
Hi All - Would appreciate any help in determining what is causing the software to either get hung up or crashes LabVIEW altogether.
We are using Labview 2016 32 bit, and two Copley Motion Controls STP-075-07 StepNet stage controllers to control and move a linear stage and a rotational stage. We used the CopleyBasicGui.vi that came with the StepNet controllers as our template to modify for our specific programming goals. Attached are the Labview subvi routines that simply open the device, send and receive commands to the stepney controller then close the device. These vi’s work just fine in a single operation, but when used repeatedly in a loop, it will either have a soft crash: it gets hung up at the “copley.setup.vi” or a hard crash: closing down LabVIEW entirely.
02-06-2018 06:12 PM
When does Error 1172 occur during this process (from your Capture PNG)?
In addition, in the CopleyBasicGui, I recommend connecting your error wires, both to enforce data flow, and you could probe them to see if an error is occurring.
What hardware are you using for the CAN communication?
02-06-2018 08:39 PM
Can you post some of your subvis? Copley.Setup and Linear.AbsMove?
Initial guess is you are opening several references to the same .dll and not closing them.
02-07-2018 10:30 AM
wrote:
When does Error 1172 occur during this process (from your Capture PNG)?
In addition, in the CopleyBasicGui, I recommend connecting your error wires, both to enforce data flow, and you could probe them to see if an error is occurring.
What hardware are you using for the CAN communication?
Hi There. Error 1172 happened during the "Copley LOS Open and Close Exp.vi" around loop #95 out of 100. This program opens the device at the beginning and doesn't close it until all the loops are done.
The CAN communication is through a Kvaser Leaf Light HS v2, USB 2.0.
Attached are all the subvis also. Thanks!
02-07-2018 10:31 AM
wrote:
Can you post some of your subvis? Copley.Setup and Linear.AbsMove?
Initial guess is you are opening several references to the same .dll and not closing them.
Yes, please find attached all the subvis.
Thanks!
02-08-2018 04:36 PM
I'd agree that you want to look into the references you are making to any .dll. In addition, based on the error you may want to inspect the VIs that are listed there. Lastly, from looking into some of your subVIs, I highly suggest wiring your error clusters, both to enforce data flow and to track errors.