I spent the majority of yesterday trying to figure out UGS and Chilipeppr with limited success. After a few hours of messing around, I figured out I had to install Java on the laptop, then figured out about getting a COM port driver installed and running… Lots of fun.
I got UGS working so I could jog the machine around, got it zeroed out… moved it around and hit ‘home’ and it came home right. I tried a carve and the path was absolutely HUGE! (vcarve desktop trial) not to mention it dragged the bit thru the solid oak board like it was a hot knife thru butter (lucky the bit didn’t break) and I had to abort the cut. Hit HOME and it went back to home, but the Z axis tried to push down thru the material (bit not running) and nearly wrenched the gantry off the machine. Spent an hour re-adjusting the v-rollers. Now the machine makes a little rattling noises when it rolls thru certain areas.
Was able to successfully make a few things in Easel, but now I’m gunshy about using UGS or anything like that. I’ve got 2 questions:
1 - I can’t remember due to my trauma, but when the bit is zeroed out and you hit ‘SEND’, does the Z-axis raise itself while it skews over to the starting position? I can see it dragging the big across the board.
2 - if you upload code with multiple bit paths, how do you change them? Will it bring the gantry back to home and pause? or do I just upload only 1 bit path at a time and run multiple files thru?
The z axis should raise and move to the beginning of the cut path. I don’t believe UGS supports tool changes… may need to make separate programs for each tool. I like UGS but have had it do some crazy things every now and then. Especially the return to zero function which should take you back to the zeroed work position. Sometimes it works and sometimes it doesn’t. I’ve crushed a couple of z homing switches because I wasn’t quick enough when it didn’t work correctly.
I use UGS. I have an older laptop that I run my machine with and can’t get the newest version of java so maybe this is part of my problem. I have to zero my machine in UGS, run my toolpath, then I have to close out UGS and restart the whole process to run my next toolpath. Pain in the arse but that’s how I’ve gotten it done. I’ve heard of others having to do the same thing. In short, after I run a toolpath I don’t click the home button, I close it out and start over.
UGS 1.0.8 does not remember whether you work in mm or inches, if you work in mm and it is set to inches it will move too much and destory your work
UGS 1.0.9 does stay in mm so the above does not occur with me anymore. At the end of the job the tool rests at XY zero and Z at highest point plus safe z so you have to bring the z axis down and reset zero before starting the next job. Apart from that it is a pretty stable version.
UGS 2.0 nightly build has had some of z axis runaway problems, Seems a nasty problem as it has been re-opened multiple times. I had a few scary moments too so I decided further testing needed to wait untill the installation of hard limit switches.
UGS 1.0.9 is running on a Lenovo Windows 10 desktop.
When you manually jog in UGS it sets it to “relative mode” be sure to set it back to “absolute mode” when you run your g-code or it can go CRAZY. I have modified my post processor to automatically include it in the header of every cut file.
I could never get the 2.0 build to work right, I use 1.0.9 and never had even 1 issue. as far as dragging the tool over the work sounds like you are not getting safe travel z height set properly in the code? could be the 2.0 issue though
Once at the zero I want, “reset zero” always works for me, unless I forget!
Just happened again. I used the 1.0.9 version this time. I rebuilt my toolpaths, made sure to slow the bit down. Set my zero… exited UGS and restarted to make sure it was my zero. Turned on the router, hit send and BAM… it just jams the router straight down untl it bottomed out on the work piece. With smoke going everywhere from the friction, I turned off my unit and backed it out by hand. I’m using the 3D plan that comes with the free trial version. It’s really stumping me. Everything works perfect in Easel. I’m not giving up as I don’t want to be limited by Easel.
I think it is. I just created some gcode with “Vector Art 3D Machinist” from Vectric and it pretty much did the opposite, lol. It moved to x/y raised up about 3/4" and started air-cutting. That’s much easier to deal with, tho.
Did it again… so I hit ‘return to zero’ and it went back but stayed way up in the air and said it was at -19mm, so I lowered my Z axis and re-zeroed it and now it’s basically working. This is really strange since I had the bit barely touching when I started UGS and it showed zeroe’s for all 3 axis.