I’m using 2 RapidChange ATC tethered together. I got it mostly working with the standard setup documented by Onefinity, however I couldn’t get all 8 pockets to pick up the tools consistently given the inablity to manually specify the pocket coordinates in the WebUI. The RapidChange isn’t very forgiving with the pocket coordinates, and where it’s auto calculated in the WebUI I was left in a position where the first 5-6 tools would pick up and the last 2 or 3 wouldn’t and didn’t have the flexiiblity to manually override the pocket locations
With the Masso 5.10 native support you can specify each pocket location, which is how i fixed my problem and got it working consistently for all 8 pockets. I’ve been running the ATC this way and having tried both ways I actually prefer this way since you don’t need the subroutines and additional folder structure and file management associated with the WebUI and subroutine approach. That being said as stated earlier there are definitely pros and cons as Don has outlined, but with the Masso config I personally find it less complicated and cleaner.
I’d suggest trying it both ways and see which way you like better. For me it’s the native Masso approach. If you go that path you don’t need the wires connecting inputs and outputs 3-5 on the masso, nor do you need to configure them in the Masso F1 screen, (although you could leave the wires in case you switch back to the subroutines at some point in the future). You still will need the input 7 (or whichever input you hooked up the yellow jumper wire up to on the other wiring harness that has the power and ground). However in Masso that will instead be setup as Toolchanger 1 instead of Aux6.
The last thing you’ll want to do in Masso is use RapidChange toolchanger config instead of Linear 2. You’ll enter the coordinates of each pocket but also the top section of that page has some info that will be needed. I spoke to Don and he told me how to get the proper values for those fields by exporting info from the WebUI.
Spindle start Position == Z spin in web UI
Z engage position == z=engage in web UI
Retorque count: set to 1
Tool check-1 Z position == Zone 1 in web UI
Tool check-2 Z position: == Zone 2 in web UI
You don’t need to set everything up in the WebUI to get these values. …you basically just need to identify the proper Z value and enter that in the Web UI, then go to the gear icon and select the “view profile details” to get the few values that you need for the masso rapidchange config screen. There’s probably a way to just calculate the values doing some math using the Z position and not needing to reference the WebUI, however I didn’t spend too much time trying to figure that out so I just enter the Z in WebUI and grab the values it spits out on the “view profile details” UI.