Differences between Onefinity/RC method vs Masso 5.10 metod for Rapidchange (FAQ)ATC

Onefinity Easy ATC (Automatic Tool Changer) Onefinity ATC FAQs
1

Benefits:

  • Multiple automatic tool changes with built in fail safes can be run within a g code program.
  • Manual tool/s may be used as part of a larger multiple tool change g code program.
  • A tool setter under the dust cover may be used. However the cover must be opened by the user during homing as well as the auto tool zero function in the F4 screen.
  • Users can easily configure custom before and after tool change macros with our new macro hooks creation tool.
  • If a tool change is aborted the subroutines will know the state of the tool.
  • If a tool fails to load or unload or reports a false positive the recovery process is simple. Correct the issue and resume with cycle start. In both g code programs and running a tool change with the “load tool [N]” program files generated from the web app.
  • A message box will pop up indicating the nature of the error.

Restrictions:

  • 4-5 inputs and 4-5 outputs are required depending on how many tool pockets are used.
  • Tool changes can not be initiated from the MDI. you must run one of the tool change programs.
  • After a power cycle the tool in the spindle must be synced with Masso by running the appropriate sync tool [N] program file.

Masso’s Native tool changer has the following benefits and restrictions:

Benefits:

  • Multiple automatic tool changes with built in fail safes can be run within a g code program.
  • Run T[N] M06 tool changes from the MDI.
  • Tool number persistence through power cycles.
  • Only 1 input and 1 output required.

Restrictions:

  • A tool setter may not be used located with in the dust cover of the magazine.
  • No ability to use a manual tool as part of a larger multiple tool change g code program.
  • No ability to do a manual tool change without disabling the tool changer in use.
  • If a tool fails to load or unload or reports a false positive there is no way to correct the issue and resume.
  • The recovery process requires more user intervention to correct.
  • The user must back up in the g code file being run or in the case of an T[N] M06. Preform a number of on screen selections and restart the process depending on the nature of the error.
  • No indication of the nature of the error is reported to the user.

If you decide to go forward with Masso’s Native tool changer they have documentation to assit with the setup here

1 Like
2

  • This must be referring to the Rapidchange sold direct from their website since the Onefinity does not have a dust cover. The touch probe can be used with the Onefinity mounting bracket that comes with the ATC

  • You can perform a manual tool change from the Masso tools tab without having to disable the tool changer.

One other consideration is the ability (or lack thereof if using the WebUI) to specify individual pocket coordinates. This could be viewed as a benefit for WebUI method since you just have to enter one pocket location and it automatically calculates the others. Or it could be viewed as a disadvantage since the RapidChange ATC requires very precise X Y coordinates for your pockets, and if things aren’t lining up exactly for every pocket, the inability to modify an individual pocket location if necessary can be considered a limitation. This may not be an issue if you’re using 4 pockets, but when tethering 2 (or more) ATCs together if your pockets farthest away from pocket 1 aren’t picking up tools correctly but others are you may need the ability to enter individual pocket coordinates to get them all working. The Masso UI lets you do but I’m not aware of a way to do this with the WebUI unless this has been added

Another consideration is overall user experience when running jobs and file management.

1 Like