Error 7003 and LV2017 64-bit crash after 2nd time running stepper run mode example.

[cburak]

The first time I run the Stepper Step Mode Example.vi after starting LabVIEW with rescale 1, Vel Limit 10000, Accel 10000, current limit 1.7 and target position 100000, the program runs fine. When I run it again, I get error 7003 and sometimes LabVIEW crashes.

LabVIEW must be restarted to get the vi to run successfully again.

I cannot find error 7003 on the Phidgets site.

The stepper controller is a new 1067.

[cburak]

Addendum: The example code works repeatedly in LV 2015 64-bit.

Any thoughts on the difference between 2015 and 2017?

[cvaum]

I am having a 32 bit LabView crash after calling StepperAddPositionOffset.vi while all other Stepper Library calls work. If I comment out the StepperAddPositionOffset.vi call I can run the vi over and over without a crash but calling that function does not produce an error (probed before and after call) but LabView hangs and PC must be re-booted (Windows 10 Pro 64 bit)

[jdecoux]

cburak: Error 7003 means the the library has timed out when looking for your device. Since the program has already successfully run once, chances are LabVIEW is holding on to something after your program has been run. Try running Reset All.vi under the Phidgets->Phidget Common palette after running the program, then run your program again.

For more information, check the Common Problems section of the LabVIEW language page here: https://www.phidgets.com/docs/Language_ ... orkarounds

All Phidgets error codes in LabVIEW are offset by 7000 to avoid conflicting with LabVIEW's own error codes. In this case, error 7003 is equivalent to error code 3 in our other supported languages. You can get the description of a Phidgets error code by using Phidgets->Phidget Common->ErrorHandler.vi

[jdecoux]

cvaum: A similar problem with StepperAddPositionOffset.vi has been fixed in a recent release. Please update your Phidget LabVIEW library and try again.

https://www.phidgets.com/docs/Language_ ... #Libraries