Move window/power and speed +~

[hvacr9 (ron benevento)]

The power and speed correction window is a nice update. My question is…aside from doing all the math is there any way I can find the “current speeds and power after a few clicks on the +and minus buttons

[hvacr9 (ron benevento)]

Anyone?[quote=“hvacr9, post:1, topic:38646, full:true”]
The power and speed correction window is a nice update. My question is…aside from doing all the math is there any way I can find the “current speeds and power after a few clicks on the +and minus buttons
[/quote]
Anyone??

[Rick (Technical Evangelist)]

@hvacr9

is there any way I can find the “current speeds and power after a few clicks on the +and minus buttons

Not really. Here is the reasoning as provided directly from Oz:

@LightBurn

Power and Speed can now be adjusted in the Move window while the job is running, but those changes are only active until you stop the job, and don’t affect the settings in LightBurn - the controller doesn’t have a way for me to know what the new settings are, because of the way these real-time controls are handled by it.

What most people do is use a generator or a set of samples with different settings to run test swatches, and use those to get the initial starting point set before doing the fine tuning. This is a good one: Lightburn PowerScale Generators - O2 Creative

[hvacr9 (ron benevento)]

Thank you for the explanation…if it would be difficult for the software to calculate I surely am not going to try. I was hoping that it was a simple algorithm since all variables are known…

[LightBurn (Oz)]

@hvacr9

since all variables are known

The problem is that they aren’t - GRBL has defaults for these values, but they can be easily changed, and there’s no way for LightBurn (or any other software) to query what the step increments or limits are. I could track based on what I know the defaults to be, but didn’t bother because I assume someone is going to change them, and for them it’d be wrong.

[hvacr9 (ron benevento)]

Ahh…understood,we can view and change the variables as a convenience since already interconnected. Send only… that explains the other “wish” which is a real time DRO