☑️Processor
...
features
Summary | Public |
|---|
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).
The scope of a Local Variable is file-specific; therefore, its storage and use must happen in the same file. Other features also use or affect Local variable such as file splitting. To ensure consistent tracking per file and reference integrity, the Local Variable management was moved from the main processor to the post-processor. To see the actual Local Variables used in the point list, the user will need to generate the robot code.
| Code Block |
|---|
///LVARS <LB>,<LI>,<LD>,<LR>,<LS>,<LP>,<LBP>,<LEX> |
Motoman Plasma - Refactor local variables management for touch sensing
Local Variables are used to store touch shifts used during plasma cutting touch sensing.
The scope of a Local Variable is file-specific; therefore, its storage and use must happen in the same file. Other features also use or affect Local variable such as file splitting. To ensure consistent tracking per file and reference integrity, the Local Variable management was moved from the main processor to the post-processor. To see the actual Local Variables used in the point list, the user will need to generate the robot code.
| Code Block |
|---|
///LVARS <LB>,<LI>,<LD>,<LR>,<LS>,<LP>,<LBP>,<LEX> |
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.
| Code Block |
|---|
var answer = this.Context.ShowMessageWindowYesNoCancel("My user message");
if (answer == MessageWindowResult.Yes)
{
// Code to execute if the user clicked Yes
} |
Updated documentation now includes a detailed list of compatible controllers for each brand.
🐞Fixed Bugs
...
Summary
...
Public Description
...
Processor editor help feature stopped working
...
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 - Remove unintended Shift Off commands
...
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.
...
| hidden | true |
|---|
...
description | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Multi-robot simultaneous support for ABB, Fanuc, Kuka, and Motoman. Make the most of your cycle time with controller-ready robot code for independent motion between multiple robots in a single cell. The robot brands now offering multi-robot support has been upgraded with the ability to output an additional scheduler program that orchestrates robot program execution, handshake event generation/output to synchronize robots using instructions available from each brand’s multi-robot option, and wait-time event generation/output to add strategic delays in robot programs. All of these features work alongside existing process-specific features, allowing for multi-robot welding, plasma cutting, part handling, and more. For comprehensive details on multi-robot output support and the level of validation for each processor, please refer to the respective documentation for each brand. | |||||||||||||
KUKA Inline is now supported by the Robotmaster standardized plasma processor template, including support for multi-touch sensing along the path by using the KUKA.TouchSense package. Previously, KUKA Inline was only supported via the basic template which required customization. Now, users can use a more robust, turnkey solution designed for seamless integration with Hypertherm hardware. The standardized processor is optimized for user-friendly configuration via menus and includes detailed user documentation.
| |||||||||||||
Fanuc is now supported by the Robotmaster standardized plasma processor template, including support for multi-touch sensing along the path by using a new search macro. Previously, Fanuc was only supported via the basic template which required customization. Now, users can use a more robust, turnkey solution designed for seamless integration with Hypertherm hardware. The standardized processor is now optimized for user-friendly configuration via menus and includes detailed user documentation. |
✅ Improvements
Summary | Public description |
|---|---|
Enhance the Tool DSL by incorporating the Description field. | |
Introducing Tooling Name DSL to allow more advanced customization particularly in pick-and-place or multi-robot scenarios. To support multi-robot, a new level of DSL has been introduced: | |
Introducing session file name and file path DSL to improve the trackability of custom generated code. | |
Learn about the actual menus, process and event for each brands directly inside the documentation. With improved formatting, and dedicated sections generated code we enhanced clarity and usability, ensuring a more intuitive experience for users across all brands.
| |
ABB Plasma - Update touch array to account for disabled touch sensing case | Corrects invalid peOffset(0) output from programs not using touches, ensuring ABB code compliance. |
OTC - Restrict double byte characters from being output in program | Double Byte characters in an OTC program file may hinder successful program loading. To enhance user experience, we have implemented features in the processor menu to alert users if any Double Byte characters are detected in the output program. These settings can be found in the Controller settings. |
The processor editor about page now displays the proper build version and the DSL version used to check compatibility with files. Hyperlinks have been updated. |
🐞Fixed Bugs
Summary | Public description |
|---|---|
Fixed Fanuc tool frame output as a comment. | |
Renaming an Event code ID in a Folder crashes PDE (DEFECT-130) | Fixed crash triggered when renaming an Event code ID in a processor folder. |
PDE doesn't reflect "operation level only" menus support for Home/Transition operation (DEFECT-25) | The processor editor now reflects the current support for “operation-level only” menus (i.e., available for task operations but not available for Home/Transition operations). |
| Page Properties | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
Section below contains the live Jira macros using public description. Its content will be copy pasted into the static table above to be supported by Refined. And this section will be hidden (Page Properties macro > Hidden) ☑️Processor features
✅ Improvements
🐞Fixed Bugs
|
...