-
-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laser cooldown / rest #602
Comments
Laser diode has 10-20.000 hrs lifetime if properly handled. Sorry for your diode, in my opinion you should provide a better heatsink and good thermal contact between ld and heatsink, and-or regulate driving current to a lower value. It is very common that china seller, sells ld telling a ovverrated value of power (ie 2,5W for a 2W or less) or tell the peak power instead of nominal-continuos power Always check datasheet of diode |
About autopause i think that the most elegant way is to put it outside of gcode, i mean in lasergrbl itself, and send pause/resume. I think is already in dev roadmap |
i had the same issues in m3 mode,after doing a 20min run with a lot of on off cycles my diodes would die,i was told my driver needed a soft start and stop for the diode,my driver had soft start but not stop,i put a 0.22ufd cap in parelell with the diode to turn it off slower,im led to belive the thermal shock of turning on and off without a soft on and off kills them,after my mod it seems fine,im using a nichia m-140 runing at 1100ma. |
Ok,, so I've dealt with 50+ laser modules by now. I've had a recent string of 1/2 watt UV lasers (7 of them so far) that do great on all these little test runs. I go to do an eight hour engraving and the laser dies about 20 minutes in. Seems like it's the actual diode that dies. 3 different suppliers so far.
What they say is let the laser sit for five minutes every 30 minutes of running. doesn't account for the 20 minute lifetime of the recent lasers.
My question is,, can we add an auto pause to the program?? Is there an elegant way to do it??
The text was updated successfully, but these errors were encountered: