I have noticed 3 things that seem odd. The first one is kind of scary.
I found that if I set my PWM period down in the 2Khz range my laser turns on at very very low power (won't touch a piece of paper) immediately when I issue an M3 command. No movement nor FIRE button required. If I move or FIRE manually, the laser fires at the called for power. The machine works fine otherwise. I was able to vector and raster ok because the extremely low power doesn't have any affect on the media. When I set the PWM freq at the default Engine/Parameter value of 0.0002 (5KHz) it doesn't exhibit this unexpected result. Once I identified the culprit while using at 500Hz I went back to the default of 5K, verified proper operation and then incrementally stepped the freq down until it failed to work "properly". I think that was someplace south of 3.3Khz but just don't recall exactly. Sorry, I should have taken better notes. I can go back and replicate this with pen in hand if that helps.
I discovered the second funny as a result of the first one. When I use the AUG function, generate code and execute it through completion, I noticed that the laser stays on. Auto on still blinks. FIRE turns works at the called for power %. Any subsequent move lights the laser off. At the end of the gcode file there is an M30 to end the code before the M5 to disable the laser and then another M30. If I knew where the post processor was I could probably sort this one out by myself.
The last one I haven't really investigated much. When I set Setup in Metric to TRUE in the Engine/Planner I got some very strange results. I will look into this a bit more when I have more time to document the effects accurately. Right now I just home and then issue a G20 command to get to INCH units. Works fine.
Lowering the PWM can have unexpected results due to the
setting of the Tickle pulse being set at 1ms. Various lasers
will repond differently to the tickle. Id turn it off and see what
that does, the setting for the tickle is in the Setup for LaserMinimum
One of my lasers has autotickle and doesnt use this at all, so
results will vary. The problem is that the Pokeys only has power setting
of 0 - 100, so if the tickle is set to 1, that "1" is longer and longer
as you lower the khz for the PWM.. 1/100th of a 1 second period
is a lot more time on than 1/100th of a 200us period.
So if you want lower frequency PWM, kill the tickle pulse.
>>ere is an M30 to end the code before the M5 to disable the laser
M30 means rewind, not stop. Nothing after an m30 will be performed.
I had the tickle ser to 0 Yesterday when I was having this fun, with tickle set to 0 I noticed that free axis 4 display bounced between .9999 and 1 whenever the M3 was run. That value did not change as I changed tickle from 0 a 3. I'll confirm again today when I have some time.
The first M30 in the code appears just BEFORE the M5 which it's followed by a 2nd M30. So the program is rewinding before the M5 disables the laser power.
[The extension txt has been deactivated and can no longer be displayed.]