So finally got my elite up and running after a faulty y rail. Spindle installed and have my fein dust extractor plugged in to the power supply. When I ran the “Elite” test cut as soon as I hit cycle start the spindle fired up as well as the dust extractor and away it went with no issues.
After that I went into vectric and created a 32x32 box and chose to pocket cut that to resurface my wasteboard as I had moved and re-leveled my table. Saved my toolpaths and loaded into the masso and hit cycle start and the spindle fired up but my dust extractor did not. I immediately stopped the program as I did not want mdf dust everywhere. Restarted it a couple times with no luck so I reloaded the “Elite” test file and sure enough both spindle and extractor fired right up. So I reloaded the wasteboard file and both started just fine. I didn’t change gcode, didn’t do anything different so I’m trying to figure out why it starts sometimes and other times it doesn’t.
After all that as I was surfacing my wasteboard and my zero was set to front left corner of wasteboard the machine was going around the final pass and as it went to the right rear corner the y gantry’s made hard contact with the stops in the back and stalled the machine. I hit the estop and rehomed and chose to start the program again from the line it stopped on and it did it again. I would have thought with the technology in this system that the machine doing that would have been out of the question unless there’s some parameters in the Masso that wasn’t set correctly from onefinity with possibly journeyman or foreman parameters as my machine is a woodworker. Any thoughts ?
I do not own an Elite series, but I have been using a Masso G3 controller for a while. Does it come with a wiring diagram that details the configuration of the inputs and outputs used on the Touch controller? I am curious how Onefinity is implementing the auto on/off outlets.
Would you be able to upload a closeup image of the Masso controller inside the Touch case, showing all the wiring connections?
I would take a look at the g code program that works and see if there’s a M7 or M8 being used to turn on the dust extractor and a M9 to turn it off, you may need to have these added by the post processor.
That’s just it, I see no gcode to start vacuum on the test file and the vacuum is connected to the power supply not the Masso….and it ended up working on the 3rd or 4th try with no change to the gcode. Probably going to end up going with a IoT power strip and hook it to my pwncnc vfd and it will power extractor at 5500rpm.
I haven’t entered any gcode so far and sometimes it works, sometimes it doesn’t. But having to enter gcode every cut kinda defeats the purpose of auto vac doesn’t it ?
Could you give me instructions on how to edit that in Vectric Pro? I’m assuming by going into the masso ARC atc inches post processor in vectric and editing but I’ve never did that.
You have it right…
I would save a copy to the desktop
change the extension to .txt
Theyre broken up conviently, and i would inject the code there…
After you change it, change the extension back to what it was, and move it into the mypostp folder… when you do that it’ll be the only post processor you have available in ventric
I have mine go to the back center after finishing instead of xy0 for example
Definately run a test file. I like to make a simple square with one pass and cut air to validate what you want is what’s happening
I was able to get the PP edited to include the M08 code to start extractor and oddly enough the M09 code to shut it down was already there.
Ran the wasteboard flattening file again and the y gantry’s slammed into the back stops again and stalled the machine again. I don’t understand, I can jog it all over and it slows and stops but during the program it crashes.
Is the program sized right, are you zeroing xy appropriatly. I wonder if soft limits are set correctly. Hard & soft limits in masso
Can’t help with the how to on soft limits but I’m sure Google can give a step by step
It doesn’t surprise me the stop command was there, but I’m glad you were able to figure it out
The wasteboard is 32x32 travel is 32.25x32.25 and xy both zeroed at front left corner. The board was about an inch too far back which I’ve since fixed but I would have thought this fancy masso controller wouldn’t allow us to program outside the limits. Even the raspberry pi system wouldn’t let you do that but it would let you jog into stops, the elite won’t let you jog in hard but seems it doesn’t mind letting programming do it.
Haven’t ran the file again since moving my wasteboard forward and probably won’t until it needs it again just curious if this is a problem or normal.
That’s exactly what it was, by default the controller came to me with both soft limits and hard limits disabled. I feel much better now, thanks for your help sir!
