☑️Processor Improvements
Summary | Public Description | ||
---|---|---|---|
Motoman - Prevent code generation when variable limits are reached | Motoman robot controllers have variable limits. To avoid generating robot code that may not load, controller settings are now included to alert the user when the limits are reached. These limits can vary from one integration to another. | ||
Motoman Welding - Refactor local variables management for touch sensing | Local Variables are used to store touch shifts used during touch sensing (embedded touch or in a separate touch operation).
| ||
Motoman Plasma - Refactor local variables management for touch sensing | Local Variables are used to store touch shifts used during plasma cutting touch sensing.
| ||
Motoman Plasma/Welding - Touch macros can output the operation touch speed | Motoman touch macros now output the touch operation touch speed instead of a fixed value. This change represents the new default behavior, while retaining the option for a fixed value if needed. | ||
In addition to notifications, the context DSL now offers a method to display Yes/No/Cancel windows for user interaction.
| |||
Updated documentation now includes a detailed list of compatible controllers for each brand. |
🐞Fixed Bugs
Summary | Public Description |
---|---|
While the documentation was easily accessible through the Windows Start menu, the processor editor would stop working when attempting to access the documentation by clicking on the “Help” button located in the top left menu. | |
Processor editor crashes when using drag/drop to re-order menu 'Categories' | The processor editor could crash when attempting to re-order the menu 'Categories' by using drag/drop and dropping the item outside or below the end of the list. |
Motoman welding process outputs unintended Shift Off commands when interpolated shift is enabled with only one touch. | |
Motoman - Robot configuration is not reset when program files are split | Force Motoman robot configuration to be reset when program files are split. It was potentially causing issue due to Motosim initializing the robot configuration to default value if absent from the file. |
ABB - Invalid WaitTime command when using optimized motions menu | An incorrect 'WaitTime' event was added when "Precision Motion Overrides" were enabled. |
Page Properties | ||||||
---|---|---|---|---|---|---|
| ||||||
☑️Improvements
|
|
|
|
🐞Fixed Bugs
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...