What Am I Doing Wrong?

Elite Series (Masso & Redline) (Gen 1) Troubleshooting (Elite Series)
1

This happens every time to me and I can’t figure out what I’m doing wrong.

  1. Boot up Machie

  2. Home machine

  3. Go to “Load File” Screen

  4. Load program

  5. Go to “Jog & Probing” screen.

  6. Install tool

  7. Probe tool

  8. Exit Probing screen

  9. Go back to “Program and MDI” screen.

  10. Push the “Go To Work Origin” button (spindles moves to proper place)

  11. Push “Rewind” Button

  12. Push “Cycle Start” button

  13. Program runs, stops, and a window opens telling me to install the tool (per the program).

  14. Tool already installed and probed, so I hit the “Cycle Start” button again (which is says to do after installing the tool).

  15. ********* Spindle then just drops all the way down like a rock (spindle does not start spinning) and hits the work piece resulting in an error.

  16. I then have to hit the Emergency Button, release it, and Home machine again.

I thought about after step 13, when it opens a window and tells me to install the tool, probing the tool again, but while the window is open, I can’t change screens (to the “Job & Probing” screen) to probe the tool again. All I can do is push the “Cycle Start” button again. Which then cause the Z axis to just drop.

Any help would be great. This is driving me crazy.

2

Is your Z zero set to top of material or bottom of material?

3

My z is set to top of material. The z is actually all I ever have to probe because I have G55 (and others at different locations depending on the fixture I am using) set to a certain spot where my fixture holds the material.

4

I don’t know if it matters, but I always do my tool loading and probing before I load my file, then hit cycle start

2 Likes
5

I will give that a try. Thanks for a suggestion.

6

Sounds like you are getting Masso all mixed up with tools, and how long they are.

When you set Z0 with a tool, Masso registers that Z0 corresponding to that tool. Then when your program starts, the gcode switches to a new tool with a different tool offset and the Z values stored are no longer valid. The solution is to use the MDI button, and enter TXM6 (where X is the tool number), to load a new tool. Then set X0, Y0, and Z0 with the tool your going to use in the program.

When Masso goes straight into the table, my guess is that it is making a rapid move over to a tool setting to check the length of the tool stick out. Are you using a tool setter? If not you can disable automatically checking tool stick out when new tools are loaded.

2 Likes
7

If you can, sharing some example gcode would be helpful. It sounds like this occurs somewhere in the preamble, so just the lines prior to the actual cut starting should be sufficient. This sounds like what would happen if your program replaced your current cutter compensation with that of a length=0 tool from the tool table and then commanded a move to an (assumed) safe height.

8

I don’t know if you’d find starting over again with setting up your probe and tool setter useful, but this video, in combination with the 1F manual on the tool setter, may guide you to success as I found it did for me: https://youtu.be/w7auvta0g44?si=MxfDR8OmocnHBfK4

2 Likes
9

Thanks for this info/thought. I will give this a try just for experience and knowledge sake.

1 Like
10

Thanks for the link. Following his process (probing the tool etc before loading the toolpath) definitely worked.

1 Like