Robertspark wrote:Hmm, I suspect that the laser is not able to be directly driven from uccnc, and again you need another piece of hardware that will fire the laser quicker relative to the pwm signal.
The problem I am having is not the speed of switching the laser as it is more than capable of turning on and off at the speed commanded by the UC100. I can command the laser to turn on and for 10x faster at a much higher resolution using a GRBL-Mega controller and the laser is in perfect sync. What type of hardware you referring to?
Robertspark wrote:The carrier wave from the uc100 if it is set on 100khz kernel loop cannot be any quicker than
100,000 / 255 *2.... So 784 Hz.
I agree to some point. My tests involve Q0 and Q255. Nothing in-between. I simply want the laser on or off. I am not changing the intensity of the laser. I should be able to set the PWM frequency to 5000Hz and still be able to achieve that.
Robertspark wrote:Because of the way the uc100 will fill the pwm signal with a 1 or zero on every kernel loop and use the pwm signal to provide 255 steps
As mentioned, I do not require 255 steps for this test. I only need 2, 0% and 100%. Intensity is not being used in this test.
The issue I am having is not the speed of the PWM signal, it is the timing and as mentioned in an earlier post, There appears to be a lag from when the M10 Qxxx command is sent and then the PWM pin signal actualy changes. And it gets so out of sync at speed that a Q0 may get missed and the laser does not turn off. The Laser driver simply reacts within 100ns to a TTL pulse. The timing issue is occuring in the UC100.