Forum Replies Created
- rmaso February 1, 2016 at 12:29 pm in reply to: SA124B SH_API.DLL restart in Labview
In case anyone else is looking at this type of problem, I implemented a fix as suggested above by Justin.
I was concerned about the accidental disconnection of the device and the USB cable. Using the LabVIEW wrapper VI’s submitted by someone else on this forum, I would monitor the error lines for the 5010 error. When that was detected, it would close the device, wait for the cable to be plugged back in (by repeatedly asking for serial numbers of connected devices), then try the connect and initiate/setup commands again. This works terrifically! The only thing to note is that as written, the VI to close the device only runs when there is no error, so you can’t pass the 5010 error cluster to it as it is currently written. I chose to just pass an error constant to the VI to make it always run.
I tried this method over and over and it ran flawlessly (after working out the above error issue).
I know this is an old thread, but hopefully it’ll help someone somewhere!
Thanks to Justin and Andrew for their help with my program.rmaso January 26, 2016 at 12:12 pm in reply to: Labview drivers for SA44
After further investigation, Error 13 is a general LabVIEW error: File is not a resource file. “Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format.
The VI is pointing to the correct location of the Spike DLL. Any thoughts?
Thanks!rmaso January 26, 2016 at 11:51 am in reply to: Labview drivers for SA44
I’m trying to run the updated version, but am getting an Error Code 13 right out the gate after saGetSerialNumberList. I have my SA44B connected and it works fine with Spike. I’ve unplugged to power on an off the SA several times, but can’t get the project to run.
Any ideas with error 13 is?