Hi! We're working on a project that will see some E-727 units driving S-330 tip/tilt platforms. The S-330 will be driven by analog inputs during normal operation, with the IOC being used mostly for higher level control and decimated telemetry (position every 1/10th of a second or so), because the platforms are for fine-tuned pointing of laser beams, and the control loop is a tad high for an IOC (or for control over GCS, for that matter).
I've successfully connected the IOC with the E-727 units (thanks for your work!), but following our experience with the Galil motor driver we were hoping for a more general interface to the controller from the IOC side. We'd like to be able enable/disable the analog inputs as control source (to enforce whether the units are in operational mode or not), and it would be great to be able to send the ATZ command as part of the initialisation process.
Correct me if I'm wrong, but from my understanding of the code, none of these are possible right now. There's get/setGCSParameter, but this is used internally to read and set some specific values, and the concept of ATZ seems to be there only to react to errors regarding it (e.g., trying to execute a command while the Auto Zero process is ongoing).
If that's correct, I would like to know your thoughts about adding those capabilities (choosing control source being the main one). Do you believe they have a place in your driver, or you prefer keeping it simple and moving that to a standalone program? If you're ok with expanding the driver, we could contribute code ourselves. If you prefer not to, then it would be great to know now, because I'd rather not have to maintain modifications on vendored-in code.
Hi! We're working on a project that will see some E-727 units driving S-330 tip/tilt platforms. The S-330 will be driven by analog inputs during normal operation, with the IOC being used mostly for higher level control and decimated telemetry (position every 1/10th of a second or so), because the platforms are for fine-tuned pointing of laser beams, and the control loop is a tad high for an IOC (or for control over GCS, for that matter).
I've successfully connected the IOC with the E-727 units (thanks for your work!), but following our experience with the Galil motor driver we were hoping for a more general interface to the controller from the IOC side. We'd like to be able enable/disable the analog inputs as control source (to enforce whether the units are in operational mode or not), and it would be great to be able to send the ATZ command as part of the initialisation process.
Correct me if I'm wrong, but from my understanding of the code, none of these are possible right now. There's get/setGCSParameter, but this is used internally to read and set some specific values, and the concept of ATZ seems to be there only to react to errors regarding it (e.g., trying to execute a command while the Auto Zero process is ongoing).
If that's correct, I would like to know your thoughts about adding those capabilities (choosing control source being the main one). Do you believe they have a place in your driver, or you prefer keeping it simple and moving that to a standalone program? If you're ok with expanding the driver, we could contribute code ourselves. If you prefer not to, then it would be great to know now, because I'd rather not have to maintain modifications on vendored-in code.