That makes a lot of sense, thanks for breaking it down. I guess in the end it just comes down to our loads are far from predictable, long straight cut then a 90 degree turn at the end, or hitting a knot, slotting vs free air, hitting a screw. I can’t imagine the reaction time it would take for that to be effective, seems it could make it worse by lowering enough that when that does happen there is less holding.
Instead of ending lower maybe a timeout is a better option.
A lot of people use a new gcode for each tool change, seems like it could lead to issues if you mixed them up.
Why is everysingle change so difficult now.
So there is another setting in there I keep wondering about. Step pulse timing. We only need 1 microsecond, it is currently set to 4. I understand changing this just increases maximum step rate, which we really do not care about. Is there any other upsides to changing to 1, are there any downsides? Axes | Wiki.js “Pulse_us”
*edit - it looks like we should turn it down to one info for nothing else to get tighter laser timing, “The speed of the processor can also come into play if a lot of processor time is required per step. High density laser engraving is one example.” So less processor time, fater laser pulses.
It’s working well as-is with the default, and you aren’t anywhere near needing more steps for the normal case. Why mess with it?
I’m not sure we need anything different. I’m not having any trouble with the JL1 using the default settings. I could probably monkey with the setting, but again the defaults seem to work fine.
What indication do you have that there’s a problem?
To keep yourself sane, gcode should always return it back to where it found it at the end (which is what my fancy gcode does). Of course, if you had to cancel the job in the middle, it would leave it in a different state. Not sure how you would do a timeout. This also isn’t YBR. If I did this (and it’s completely not necessary), I would leave my hold amps at 0.5 and update my gcode to raise to 0.800 at the start and return to 0.500 at the end. I should probably just get a smart power strip and have it auto turn it off at night or something. This is all a fun thought exercise anyway.
Yeah, I see what some just start changing other things. I really like making sure we squeeze all the performance out we can.
Just for raster. We were a step better than Marlin config’s, Mitch’s new tweaks should get us more. This we double that. I guess split the difference just to make sure we are not on the bleeding timing edge, but I see no reason to send longer pulses if they are not helping anything.
No problem just faster raster. My little 2.8W laser can handle more, I can only imagine what some of the bigger laser users can benefit from.