Closed philrosenberg closed 3 years ago
A quick google found this: https://forums.ni.com/t5/Instrument-Control-GPIB-Serial/NI-488-Command-requires-GPIB-Controller-to-be-Controller-in/td-p/346433?profile.language=en
Seems that This is probably nothing to do with GPIB, but probably to do with a file missing or not in the correct location.
Reinstalled the software. This is just a zip file of labview stuff that needs unzipping to the C drive.
Left the old software in a directory called lidar_uninstalled_20210506
This seems to have fixed the problem. I'll wait to see if Jus gets back to me then close this issue.
Heard back - the reinstall fix is fine
When I hit the accept settings button to start the lidar logging I get an error saying "NI488: Command requires GPIB controller to be controller in charge"
The instrument has been out on a project where it was slaved to another lidar controlling its scanning - not sure if that is the problem.
I've emailed Jus at Halo to see if they have any suggestions (he helped me with setting up the slaving).
Once I clear the error, everything seems to work just fine. But the fact that the error needs clearing means that on power up the lidar doesn't automatically restart scanning.
Screen grab of error below.