Jog Motion #2

[quangvi]

no , Hi @chamnit Feedrate override do not work with jog motions, but problem is happen, if the axis had move slow speed and travel is long(about 500mm) , i want to change fast speed , i only press stop or reset,

[chamnit]

Please read and try to understand the jogging documentation in the doc folder. It explains how it works.

[quangvi]

Hi @chamnit , I understand is work with "manual command" but the button "X+X-,,Y+ Y-,Z+,Z-. not accept feedrate overide, This is intentional? it's fidget

[chamnit]

No, I don't believe you do. Grbl has no "buttons". You are confusing a GUI function for Grbl's. I'll say this again. Feedrate overrides are ignored for jog motions and please try to read and understand the jogging document. It's all explained there.

[quangvi]

thank @chamnit, sorry my english a little stupid , i had designed buttons additional in your GUI function for Grbl's, my machine have 1000mm for Z axis or more, 30mm for X axis or more, it's lathe machine cnc 2 axis, axis so long travel, if i press X+ or Z+ in Gui or button (my additional ) with feedrate low (Ex: F10 ), i will waiting a long time but feedrate overide not accept ,it's fidget , next time (maybe 1 to 2 weeks) I'll edit code GRBL ,Feedrate override will work with jog motions, it will accept buttons x + ,y +, z +, x-, y- ,z- can press feedrate overide, in my machine ,again thanks

[chamnit]

@quangvi : Please understand that feedrate overrides do NOT work with jogging. This is completely intentional. It prevents misuse and accidental damage when exiting the jog state and starting a program. The override value may have been set very high, forgotten, and result a hard crash into the material. This usually results in a broken bit, damaged spindle, ruined workpiece, and even machine damage. If you want it to work with jogging, please place it in your own repo. This will not be added to Grbl.

[quangvi]

thank you @chamnit , I understand , in many cnc machine industrial (I have machine cnc 4 Axis) , feedrate overrides is work with jogging, even feedrate overrides work homing cycle . when exiting the jog state and starting a program ,feedrate override will reset value default (one or more machine i know not reset).the results in a broken bit, damaged spindle, ruined workpiece, and even machine damage had warning in user manual ,users must be responsible for the misuse or forget ,because Z axis not returned home(or raised off the table) , X axis or Y axis moving will broken drill , it is the user's fault , i will place it in my own repo thank .

[chamnit]

@quangvi :

in many cnc machine industrial (I have machine cnc 4 Axis) , feedrate overrides is work with jogging, even feedrate overrides work homing cycle .

Allowing feed overrides during these tasks makes absolutely no sense. You have direct control over jogging feed rate if the host GUI implements it properly, and everyone knows that altering homing rate can change its repeatability and accuracy. Either way, it's dangerous and lazy.

[quangvi]

thank you @chamnit , I understand , but workers use it and they do not want to change, their programming Gcode directly on a 7-inch LCD interface, and feedrate overrides work with jogging, ex : they enter Gcode G1 X20 Z20 F100 but true Gcode is G1 X20 Z20 F200 ,this call trial Gcode in jogging, they don't want waiting or press stop button and want press feedrate overrides 200% , this is reason

[chamnit]

@quangvi : I still don't see what your problem is. G1 X20 Z20 F200 is valid g-code. Grbl would update the motion with feedrate overrides. This is not a unique jogging motion, like with a rotary dial or jogging increment keypresses on an industrial machine. We are talking about two totally different things here.

If you choose to jog with G1, that's your preference. Grbl's new jogging mode is designed for usage that is completely independent of g-code parser and machine state. Again, it's up to the GUI to handle how responsive their jogging is to rate changes. I've outlined how to do this in the jogging wiki page, like I mentioned for you to read and study.

[quangvi]

nono , this is call " try Gcode in JOG" , the workers( in my company ) , 1 st ,they program Gcode G1 X20 Z20 F100 ( JOG ) ,2st they will press button Feedrate overide up or down until cushy, ex: the Gui is display 200% now , Gcode relapce in File cnc is G1 X20 Z20 F200, this is example

[chamnit]

@quangvi : I don't give up often but I'm giving up trying to explain this. Grbl's feed rate overrides work with any normal gcode command, like a G1 as you have described. I don't know how many other ways I can say this. Whatever you are doing that is causing to not work is not a Grbl problem. It's your host GUI. Grbl is only a service. YourGUI is responsible for sending gcode and override commands to Grbl. Please just stop.

[quangvi]

sorry @chamnit ,sorry for being annoying to you , i want GRBL is better , i had read your comment again , and i understand, i had mistake, I'm actually using google translation english but it's not good, i will edit source GUI GRBL in my own repo, thank