Equipment/HPC LS3060 Laser Cutter/LogBook
Logbook
10/06/2013 note by Solexious
Mirror #2 and lens replaced. Needs new internal light.
03/12/2012 note by Solexious
The cutter has now had its 50 hour clean, all mirrors re aligned and its max power reduced back to 60%. Its working well.
3/12/2012 note by Mark
Chloe reported that the computer "just flashed to the boot up screen (big letter 'e' and intel logo), when the job was stopped now it won't boot up. Have tried unplugging the power cord and waiting for 10 seconds but still won't boot." Then added "It just needed a little longer than 10 seconds, is working fine now!"
Probably needs a clean or a new PSU.
16/9/2012 note by Oskarpearson
The laser seems underpowered - we can't get a successful cut on the recommended settings for different materials (ply and mdf). I've notified the list, IRC, and logged problems on the google logbook too with the settings we used.
24/7/2012 note by Solexious
Laser power ammeter has now been installed. The upshot of this is that the power supply was limiting the current for a 100w tube, not a 40w tube. This has been fixed in the machine settings so the max power used is 60% (19ma~).
The tube is fucked by being over driven to hell, so we need to get in a spare asap to replace it when it falls over totally.
This now means we should get much closer to our 1000 hours target, fingers crossed. But also tis extended maintence period has fixed a long running problem that kept causing down time. It will have saved us time in the long run, if you don't think it was worth it, you can 'do one'. <3
8/5/2012 note by Solexious
Reports of minor power loss fixed by levelling the bed (was too high on the left side causing de-focus) Need to look into a new bed asap.
1/5/2012 note by Solexious
Minor fire cleaned up, sadly the lasercutter had seen some use while it had an our of order sign on it :(
29/3/2012 note by Solexious
Cleaned the optics for their 75 hour clean. (9 hours late)
Russ 10:17, 13 April 2012 (UTC)
Coolbot had crashed (around 2012-04-12 19:00). It was reporting water temperature as 19, but after a reboot reported it was actu