...
The LSC interface includes more than is absolutely required by ScanImage, because it was designed with the idea that it would provide a stage controller interface that would to be generally useful, independent of any single application.
That said, you are probably reading this page because you are a ScanImage user with a custom stage. At the moment, ScanImage requires the following properties and methods of LSC to be implemented/functional:
Properties
nonblockingMoveCompletedDetectionStrategyisMoving(get only)positionAbsoluteRaw(get only)positionDeviceUnits(get only)- resolution (get only)
Methods
moveStartHook
...
getResolutionBestHook(This method has a default implementation in LSC, but if the default method doesn't apply to your device then you should provide an override.)
Testing
When your subclass is complete, it is critical to test its operation with real hardware in a "safe" setting before live use. Implementing an LSC subclass involves a fair amount of complexity and some amount of testing/debugging time will likely be necessary to ensure reliable operation. Using an LSC without proper testing could lead to wild stage moves and damage to your rig.