I’m running a Onefinity Elite Gen 1 Foreman (48"x48") with a Redline controller on firmware 1.4.9, and I’d like to report what I believe is a UX issue with the M6 tool change handling.
CURRENT BEHAVIOR
When the controller encounters a Tx M6 command in a G-code program, it stops execution at that line with no visual feedback, no popup, and no indication of what the operator is expected to do next. The interface remains on the RUN screen, Machine State shows “Ready”, and nothing suggests that a tool change is required.
To proceed, the operator must:
1. Realize on their own that a tool change is expected
2. Manually navigate to TOOL → Tool Change
3. Identify which tool the program is waiting for (by going back to the G-code)
4. Trigger the manual tool change sequence manually
None of these steps are prompted or guided by the interface.
For reference, once the manual tool change sequence is triggered, everything works perfectly — the machine moves to the change position, the operator swaps the tool, the toolsetter measures it, and the program resumes automatically. The end-to-end sequence is solid. The only missing piece is the automatic UI transition at the moment M6 is encountered.
EXPECTED BEHAVIOR
When the controller encounters a Tx M6 command, it should automatically switch to the Tool Change interface and clearly display which tool number the program is requesting. The operator should be guided through the tool change sequence without having to navigate menus or guess what is needed.
This is especially important in a production environment. The current behavior creates unnecessary friction and is a potential source of operator error — particularly for newer users who may not yet know where to find the manual tool change interface.
I hope this can be addressed in a future firmware update. Thank you for the great work on the Redline platform — the pace of development is impressive.
Best regards