Integrated Motion
We packed a bunch of new stuff into a gigantic release. This time, we’ve focused on features which can help you build more complex systems.
Before you upgrade, please refer to our migration guide from v4 to v5. We’ve changed some fundamentals between these two versions to be more standards compliant and introduce new capabilities that needed some API changes, including a more robust encoder configuration.
Configuration options for the digital IO were extended considerably. You can now configure a GPIO pin in lots of new ways, including setting the default voltage for hardware that supports it.
For digital inputs, the configuration options include:
Similarly, digital outputs can be configured as
Home and limit switches are fully supported in the firmware as well. This means all defined homing modes from 1 to 37 are now supported!We hope most of these are self-explanatory, but our documentation can help guide you through their configuration and use cases.
Auto-tuning has found its way to the torque controller! This time, we’ve built it directly into the drive itself. Settling time and damping ratio can be set to configure the performance of the current controller.
Encoder oversampling (up to 32kHz) and improved low-pass filtering on the encoder signal provide a cleaner position and velocity feedback signal. This can improve control performance, so you may be able to achieve sharper motion control tuning.
The external scaled measurement feature can now throw an error when it exceeds some defined limits, and a warning when it gets close (95%). We’ve added a filter to provide a way to clean up the signal. As this is often used in conjunction with a motor temperature sensor, this can help prevent overheating. We’ve added similar errors and warnings to the Drive and Core temperature values.
If you need to push your servo drive or power supply to their rated power limits, you may have struggled to prevent protection mechanisms from kicking in and shutting everything down. Running at high velocity and high torque at the same time can be tricky without exceeding these limits. So we introduced the feature Power Limit and the object Max power (0x200B) to give you the ability to surf the limits and get the most power out of your motor.
We’ve added three distinct methods to cover many more situations where you want a valid offset:
If a single-turn, absolute encoder is mounted to an axis that physically cannot rotate a full revolution, it can be helpful to ensure that the single-turn position value doesn’t overflow within its range of motion. But knowing where this encoder overflow will happen during assembly is tricky. For this reason, object `0x21FF` can be used to offset this single-turn overflow location. The position will be adjusted internally and the physical mounting of your encoder won’t need to be adjusted.
There are other things we could mention, such as the snazzy new logo in our ESI file. But as this is already getting long, visit the OBLAC Drives firmware update feature, and jump in! Our documentation should guide you along, and you can always contact our support team if you need some help.
We’re excited to see what you build!
