While we’re on the topic of beam power, if you cap your max at say 0.8 in the smoothie config, does that have any effect on the generated g-code?
If I run a job at 100%, would it be the same as say …60%, 70%, 80%, 80%, 80% (…0.6, 0.7, 0.8, 0.9, 1.0)
Or is 100% actually 100% of 0.8 so it would be a calculated where 100% is 0.8 while 90% is 0.72 (90% of 0.8). Does that make sense?
I assume that the s-values will just be capped at the value you set, but not sure.
Yep, we had a good little chat about that. For smoothie with a 80% limit set the power in LW to 1. I tried to set it at decimals and it would not raster anyway.
it is not a cap it actually changes the range of PWM you can specify, so AFAIK it would be 100% of 0.8 and scale as expected… ie 0-0.8
proportional_power = ( (laser_maximum_power - laser_minimum_power) * power ) + laser_minimum_power;
Where power is the s value 0.0-1.0
@Wolfmanjm Thanks, that’s good to know.
Ok, so it sounds like the scale slides. If I’m understanding correctly, there is still a difference between 80-100 if capped at 0.8 in the config. In terms of a gradient, we should continue to see an increase in power over 80% instead of 80-100 being exactly the same (capped)