Heres a 6 minute long video of me trying to do a multiple tool job, twice. I wish I could make it shorter but I am no video editor. I was unable to recreate the issue of the router turning on during a probe, but there were myriad other things that happened so I’d still appreciate any feedback.
0:00 I start a job to cut some air, but the job has multiple tools. The first cut works as expected
0:59 first cut completes, router turns off
1:04 I press Cycle Start, the device brings up a message to load a new tool
1:09 I jog the rails closer to me to load a new bit
1:16 I pretend to load a new bit
1:20 I jog the z down to get ready for a z probe, and place the probe on my work surface
1:25 I attempt to probe by pressing the z probe button in the middle of the probe screen, nothing happens. I press it many times
1:34 I press other probe buttons to see if I can get any movement, no dice
1:45 flummoxed, I wonder what I am supposed to do next
1:48 I exit probing. The load tool message is no longer red, but now blue for some reason
1:56 I press Cycle Start, hoping for some kind of change. The onefinity begins probing for some reason
2:13 because the bit is about to crash into the spoilboard, I press the e-stop
2:20 I release the e-stop
2:26 I jog the Onefinity to see if it will move, it does
2:38 I am now able to probe, and do so
2:56 I give a thumbs up because it seems like something good just happened
3:05 I attempt to start the next tool path by pressing Cycle Start hundreds of times. No joy
3:11 I give up and press Rewind. Let’s try again!
3:17 I press cycle start to see if anything happens. Z Limit error! (Maybe from the earlier e-stop?)
3:22 I home the Onefinity
3:39 ready to start over, I go to work origin
3:43 I press Cycle Start 20 or 30 times, no joy
3:49 I press rewind. Sometimes this makes the Cycle Start button work
3:50 The Onefinity tells me to load a different tool. I pretend to do so and press Cycle Start.
3:51 We’ve started over! Let’s cut some air
4:47 the first cut is done. Time to load a new bit?
4:55 I jog the Onefinity to get the router to a place I can load a new bit (Note that I did NOT press Cycle Start beforehand this time, as I did last time)
5:01 I pretend to load a new bit
5:07 I prepare to probe for z
5:13 probing for z works this time!
5:27 I press Cycle Start 20 or 30 times, no joy
5:36 I press Go To Work Origin, maybe that will make it be able to start?
5:40 nope. Cycle Start does nothing. I press it many more times to make sure (Sometimes it works I swear!)
5:48 I begin pressing random buttons to see if I can get the Onefinity to do anything
5:52 I press Home, maybe that will allow it to continue the job
6:05 I press Go To Work Origin
6:10 I press Cycle Start quite a few more times. Still nothing.
6:13 I begin manicly pressing random gcodes
6:18 I press anything I can think of to press. No dice
6:20 I give up. This is usually when I would make a new job that is just the next step that was not able to be completed, but that, in addition to all the weird stuff that happens when I try to do a multiple bit job, seems to always mess up the alignment. So there goes some expensive wood into the trash.
To answer other questions, I have a Onefinity Elite Foreman, my software version is 5.03, I make my gcode with Fusion 360, then transfer it to the Masso box by moving the thumb drive to my laptop and copying it (The network transfer functionality stopped working a few days after I got the Onefinity for some reason)
Here is the .NC file:
masso bug test.nc (8.6 KB)
As you can see, I cannot figure out how to do a multiple bit job. Any advice or maybe it’s in a document somewhere?
I would appreciate any help. Thanks again!
