We have a protocol file that – for reasons unknown to any current employee – ties into a sequencer. There could well be a good reason for the way it was done. It’s fragile and temperamental but it’s been going
OK. However, we now need things like backlash takeout moves and nobody wants to touch this lest we break something completely. I’m getting enough experience with the motor app/records to know that a driver would be the best way to go long term.
Thanks for pointing me toward those base classes. The command set for the Silverpak is pretty simple, so it may be relatively trivial to copy and modify the drivers you suggested.
From: Mark Rivers [mailto:email@example.com]
Sent: Saturday, 4 October 2014 1:08 AM
To: Peter Linardakis; firstname.lastname@example.org
Subject: RE: Driver/Protocol for Lin Engineering Silverpak 23CE stepper motor
What do you already have?
If you do end up writing a new driver, I would encourage you to consider using the asynMotorController and asynMotorAxis base classes in motor/motorApp/MotorSrc.
There are some examples of simple drivers that use this architecture, for example:
motor/motorApp/ACRSrc/ACRMotorDriver.cpp (507 lines of code)
motor/motorApp/AcsSrc/MCB4BDriver.cpp (336 lines of code)
Does anyone out there have a driver or a good protocol file for a Lin Engineering Silverpak 23CE integrated stepper motor, driver and controller? I just thought I’d check before embarking on an unfortunately necessary
re-write of what we already have.
Dr Peter Linardakis
Accelerator Research & Development Engineer
Nuclear Physics | Research School of Physics and Engineering
Australian National University
p: +61 2 6125 2862