Open Deltaplc opened 2 weeks ago
You can reduce G0 speed to 50% or 25% of max by sending speed override commands. The sender you use may have UI controls for doing that. A user plugin could implement a M-code to dynamically set the G0 override to any percentage by calling plan_feed_override(), IMO better than having a new core setting for a default percentage. But of course a plugin could add a setting in addition to a M-code...
You can reduce G0 speed to 50% or 25% of max by sending speed override commands. The sender you use may have UI controls for doing that. A user plugin could implement a M-code to dynamically set the G0 override to any percentage by calling plan_feed_override(), IMO better than having a new core setting for a default percentage. But of course a plugin could add a setting in addition to a M-code...
Thanks for the reply Sorry but I don't understand....with which command can I set the G0 speed override? If I change "Override speed G0", does the maximum speed of the G1 commands also change accordingly or does it remain unchanged?
Sorry but I don't understand....with which command can I set the G0 speed override?
There are three single character real-time commands that are not easy to send manually.
Some senders, like ioSender, has override buttons that sends the commands: Other senders may have different UI element(s) for doing the same, and some not allowing to change the speed.
If I change "Override speed G0", does the maximum speed of the G1 commands also change accordingly or does it remain unchanged?
It remains unchanged.
The basic problem is that lightburn uses the G0 command by default, for all movements that do not concern machining. I attach a small gcode:
Se modifico "Override speed G0", cambia di conseguenza anche la velocità massima dei comandi G1 oppure rimane invariata?
Rimane invariato.
Ok, this might solve my problem if I could add a gcode command to startup.....
Can I do it? What command should I enter?
A user plugin can be made that implements a M-code, closest I have found by a quick search is M220, but it is for all motion. A extra parameter could be added to apply it only to rapids? Or perhaps there is a industry standard M-code that is used by some CNC manufacturers?
O forse esiste un codice M standard del settore utilizzato da alcuni produttori CNC?
No, I don't know of any cnc codes that only set the speed of G0 movements. Because (unfortunately) it is always linked to the maximum speed of all other movements!
Si potrebbe aggiungere un parametro extra per applicarlo solo alle rapide?
YES I think that would be the best! It would make everything much easier and more flexible!
I have now added a plugin, but not yet added it to all the drivers and the Web Builder. If you are compiling yourself you may add it manually, but remember to update to the latest core first.
Ora ho aggiunto un plugin , ma non l'ho ancora aggiunto a tutti i driver e al Web Builder. Se stai compilando da solo, puoi aggiungerlo manualmente, ma ricorda di aggiornare prima all'ultimo core.
I'll definitely try it soon!! thank you for your support!!
Ora ho aggiunto un plugin , ma non l'ho ancora aggiunto a tutti i driver e al Web Builder. Se stai compilando da solo, puoi aggiungerlo manualmente, ma ricorda di aggiornare prima all'ultimo core.
Bench tested plugin!! Seems to work very well!! And exactly what I needed! Actually, better! Thank you very much!
Good morning I apologize for the inconvenience I use ligtburn to drive a laser where I installed your grblhal. To move (for example) from the starting point to the engraving area, use the G0 command, given that in my case I use a very high max travel speed, I wanted to know if it was possible to set a value for the movements in G0 mode other than the max travel value of the axes? Maybe even default to the entire firmware.... or it would be great if you could add a $ setting to do this! Thanks for the help