No dice. The only values $33 would accepted are 0 and 1.
I checked the PWM coming out of the controller with a large circle cut at 20mm/s:
LB Power: 00%, Duty Cycle: 0% Hz: 0 (probably undetectable)
LB Power: 01%, Duty Cycle: 12% Hz: 10k
LB Power: 25%, Duty Cycle: 34% Hz: 10k
LB Power: 50%, Duty Cycle: 56% Hz: 10k
LB Power: 75%, Duty Cycle: 78% Hz: 10k
LB Power: 99%, Duty Cycle: 78% Hz: 10k
LB Power: 100%,Duty Cycle: 0% Hz: 0 (probably undetectable)
Interesting that 1% power gets a 12% duty cycle. It’s probably something monport did in the firmware to keep everything within minimum firing current?
First I thought the 10kHz was hitting my multimeter limit, but specs say the meter can read up to 60Mhz. 10k seems rather high. Can the PSU and the tube handle such high frequency?
Well, that’s a better match to the power supply’s PWM demodulation filter, even if the control setting makes no sense.
Ruida controllers default to 20 kHz, old-school Arduino controllers use 1 kHz, and the power supply converts all those PWM signals into the equivalent analog voltage to control the tube current. Ruida controllers also have an analog voltage output that works fine, too.
Not sure what you mean. When LB is trying to fire at 1%, the duty cycle is 12%. Are you saying the physical power knob on the ammeter doesn’t affect duty cycle and lower the output power in a different way?
I believe that’s correct, based on what we’ve seen with similar HV supplies used with Ruida controllers.
The PWM input controls the current between zero and whatever the maximum the power supply can produce.
The knob reduces the maximum value the power supply can produce.
So the same PWM input to the power supply can produce any output from the “normal” value with the knob fully clockwise to “zero” with it fully counterclockwise.
Which means you have no idea what power the laser will produce for a given PWM percentage without also knowing the knob’s position on an uncalibrated scale.