Will Winder wrote: PsyKo wrote:
Will Winder wrote:How has Universal Gcode Sender been treating you?
I'm planning to revisit the jogging functionality soon, are there any features or improvements you would like to see? Or other things that would make your life easier?
I have one recommendation (I think this should be a completely new topic). For some reason, I always have to restart my UGCS after finishing a job. This resets my zero position.
I already updated to last version of UGCS. I will update to last version of GRBL soon.
Any idea ?
That bug should be fixed for you in 1.0.5, unfortunately the jogging commands are not working as well as they did in 1.0.4 (once you upgrade to 0.8c). Sorry for trying to derail the thread, carry on!
Yes agree with this one too, While making PCBs there is usually a combination of 3+ files, Isolation routing, Drill files (1+), Cutting board. And as PsyKo mention one has to re-align per file (this is the source of a lot offset errors).
Other "features" I would love are:
1) T6, I was thinking of editing the code and making the change to intercept the tool change command (T6) and have a configuration for this command, for example tool change is at X0,Y0,Z40. Then allow me to zero out the Z-axis since different tools have different lengths and continue
this will be so great since I wouldn't have to restart for tool change and I could combine the 3+ files into 1 file with T6 in between. Even if there is no configuration I can insert the gcode G0 X0 Y0 Z40 then T6 as long as it pauses, allows me to zero z-axis and continue.
2) while using the jog feature, it will be nice if it only send the command for the one axis I press the button for, instead of all 3 axis, I had the unfortunate event of braking a few 0.3mm end-mills because I had used the command interface to change the z-axis up 10, then wanted to jog left or right by say 10mm, but by doing so it send the command G0 X10 Y0 Z0 (oops!!) I would expect the command do be only for the axis the button was pressed like "G0 X10".
Another more common problem; process a gcode file file ended with code as some non zero coordinate, then I use jog control to move Z-axis... again it sends G0 X0 Y0 Zval. Imagine I was drilling a whole and there was an offset error, press cancel. Then try to move up to take the drill bit out of the hole. oops again G0 X0 Y0 Z<val>.
3) I tried 1.0.5, I like how you are now querying grbl 0.8c for the machine axis coordinates (would probably help with (2)), the one thing that didn't like is that now is messing up with calibration / characterizing, for example I want to move x-axis right in 3.5mm increments and measure per move. in 1.0.4 it would set the value 3.5, and hit the X+ per increment resulting in commands like G0 X3.5 Y0 Z0, G0 X7 Y0 Z0, G0 X10.5 Y0 Z0, and so on, for each one of this I would take a measurement with a digital caliper.
But now since it updates current position, it will send commands like G0 X3.5 Y0 Z0, G0 X7.42 Y0 Z0, G0 X10.42 Y0 Z0, since is taking what grbl thinks the machine is at and adding 3.5, which I agree it should be the default behavior, but it will be nice to be able turn it off. Now I have to calculate for every move to get what I want or use the command line... for example for above I would have to enter 3.58 (10.5-7.42) and do this for every subsequent jog increment. As you can see I moved back to 1.0.4 because of this.
4) Spindle ON/OFF
5) ABORT/STOP button
But as mention before this probably deserves its own thread...
FYI also thinking about ways to add Vision controls but not sure if this could be added or it belongs different app. Is there a ways I can write a separate APP that interfaces with UGCS?
Thanks a a lot for this awesome app and your considerations for these new features.