RapidChange Solo: Configuring Tool Changes on MASSO

Jason IP3 min read
Other ManufacturerOther TopicTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

The RapidChange Solo can automate tool release and pickup on a MASSO-controlled machine, but not by assigning every tool to one integrated ATC location. The supported evidence points to a workflow built around the RapidChange post processor and subprograms. The machine unloads the current tool, pauses for the operator to replace it in the single slot, loads the replacement, requests confirmation, and then resumes the normal tool-change sequence.

Why one integrated ATC slot cannot serve every tool

MASSO can assign multiple tool numbers to the same physical location, but that mapping does not create storage capacity. During an integrated tool change, the controller must return the installed tool before collecting the requested tool.

Slot condition Integrated ATC result Risk
Current tool occupies the single slot after unloading The machine immediately retrieves that same tool The requested tool is never introduced
Replacement tool already occupies the slot The machine attempts to return the current tool to an occupied location Collision and damage to tools or holders

Therefore, assigning all tool numbers to one pocket does not implement the required exchange. The operator must remove the unloaded tool and insert the replacement between separate unload and load operations.

Use subprogram control instead of integrated ATC control

The documented decision path is straightforward: use the RapidChange post processor and supplied subprograms when operating the Solo with MASSO. The available evidence states that this sequence has not been implemented through MASSO's integrated tool-changer support.

Do not treat a shared pocket assignment as a workaround. The subprogram approach is materially different because it separates unloading from loading and inserts an operator-controlled pause between them.

Operator sequence for a Solo tool change

  1. Generate the machining program with the RapidChange post processor and retain the required RapidChange subprograms.
  2. When the tool change is reached, allow the subprogram to unload the installed tool into the Solo.
  3. Wait while the machine moves clear and displays the operator message.
  4. Remove the unloaded tool from the single slot and place the required replacement tool in that slot.
  5. Press Cycle Start so the subprogram loads the replacement tool.
  6. Confirm that the tool loaded correctly, then press Cycle Start again to resume the program.

This process replaces the manual collet-wrench operation, but it does not make the Solo an unattended multi-pocket changer. An operator must exchange the tools in the slot and acknowledge the prompts.

Organize MASSO program and subprogram files

The reported MASSO file-handling constraint is that there is no global folder for these subprograms. Keep the machining program where MASSO can resolve the required subprograms; the demonstrated file-management method is to copy the active machining program into the folder containing the subprograms before running it.

Project folders can remain the master storage structure. For execution, place the selected program with the required subprogram files, run the job, and remove the copied program afterward if desired. Confirm this arrangement with a test file before relying on it for production.

Verify the installation before production

Use the RapidChange test files to verify the complete sequence before running a workpiece. Confirm that the machine unloads the current tool, moves clear, displays the expected prompt, waits for Cycle Start, loads the replacement, pauses for load confirmation, and resumes only after the final Cycle Start.

A successful test-file run establishes basic sequence operation but does not by itself prove production readiness. Perform a controlled dry run of the actual posted program and verify subprogram resolution, clearance, slot occupancy, operator prompts, tool retention, and the subsequent tool-length-setting action configured for the machine. Stop the test if the slot is occupied when an unload move begins or if the requested subprogram cannot be found.

Frequently Asked Questions

Can all MASSO tool numbers use one RapidChange Solo slot?

No. A shared integrated-ATC location either causes the machine to retrieve the tool it just unloaded or attempts to place a tool into an occupied slot. Use the RapidChange post processor and subprogram workflow instead.

Does RapidChange Solo provide unattended MASSO tool changes?

No. The sequence unloads the tool and moves clear, but the operator must replace the tool in the Solo, press Cycle Start to load it, confirm the load, and press Cycle Start again to continue.

Where should RapidChange subprograms be stored for MASSO?

The evidence reports no global subprogram folder. Place the active machining program where MASSO can resolve the required subprograms, with the demonstrated approach being to copy the program into the subprogram folder and verify resolution with a test run.

Back to blog