I am trying to set up my Rapid change ATC with my masso and aftermarket 2.2 k spindle. I believe I have everything set up correctly but can seem to get the file from R/C with the macros fire for “find Z position” to do anything. I have the spindle lowered down into the ATC in position 1 with the light lit ( the light is Green, all the videos I’ve seen it was amber, is that ok)
I load the file from the usb, press CTRL+R button, then cycle start button, nothing moves. I just get a “IR beam is clear, Adjust and retry”. I’m not sure what I’m doing or have set up incorrectly.
It shows low. If I break the beam in any of the slots the light turns green and the F1 screen shows high. I left my shop for the weekend and I can’t remember if it was the input 7 or not showing the high low signal.
I have the same issue. The GCode for the Find Z Position program looks wrong to me. It is just:
M66 P1 L3 Q1 S2
MSG IR beam is clear. Adjust and retry
Which I think means to wait for input 1 to become high or timeout after 1 second, and then display the error message no matter what.
I’m having other issues with the setup process as well. The process is not streamlined. You’d think that they could just take the position of cup 1, tool-set the collet nut, and have all the info needed to auto-configure the setup without all this headache from the end user. I would not recommend this system to anyone as it is now due to setup alone.
The following is an example of the Find Z gcode I have seen posted before…
M66 P5 L3 Q1 S2
MSG IR beam is clear. Adjust and retry
M30
M98 P600 L3000
M66 P5 L4 Q1 S2
MSG Beam still obstructed. Run again
M30
MSG Record MACHINE Z Position
M30
From what I have learned the process you are asking for is actually the streamlined process that Don has set up. After finding the correct Z height using the supplied macro many of the other important heights are calculated behind the scenes. You will of course need to determine the exact XY position of pocket #1, and fill in a few other parameters that are more user specific.
It is unfortunate that you are having difficulty, but Don provides excellent support - not sure if you have already reached out to him. The help windows and online documentation he provides for the WebUI is also excellent - not sure if you have read that yet.
If you are not using the WebUI but rather Masso’s RapidChasnge ATC logic, and perhaps also not using Onefinity’s Easy ATC model, then things may require a bit more work and patience on your part.
If you want help here, you’ll need to provide more details of the ‘process’ issues you are experiencing.
P1 is referencing the wrong input. It’s referencing Aux 1. If you set everything up like page 42,43 and page 60 of the manual, Tool detection sensor should be Aux 5.
This means in your profile on the webUI you have not set your Tool Detection to Aux 5. It’s not mentioned in the manual or the video as far as I can tell. I had the same issue before checking the actual Gcode. It took me more time than I’d like to admit to figure out why it was referencing Aux 1.
That is odd, the Find Z Height download pulled from the WebUI only contains the code I posted above. I’ve grabbed it many times from the Onefinity Masso configuration on the WebUI and it only gives those two lines.
I followed the Onefinity supplied manual in detail and am using the Easy ATC. It also fails one of the tool tracking test routines (the full tool change test works fine though).
I got it working by measuring manually, and ignored the test failure. In the WebUI I also had to enable tool detection and correct the miss-assigned aux values. In practice, all tool changes work fine.
The only issue that really bothers me while using it is the fact that it looses tool memory if I run Start From Line on the Masso. In that case it seems to always load slot 1 no matter what, which has ruined a few cuts. That is beside the point of this thread though.
