I’ve been experiencing a number of problems on both Laguna CNCs.
At first I was blaming them on my own gcode but I’ve now experienced enough of them to say confidently that the problems are not just my own problems. Furthermore, I’ve experienced some of these while Doug Squires was with me and we sanity checked each other to confirm that the problems were with the machine/controllers.
-
The controllers on both machines are difficult to use (speed control in particular is very cumbersome). This is an inconvenience but not critical. That said, I suspect that those controllers are nothing more than serial devices that are emitting gcode. There’s probably good replacements for them.
-
The USB file-reader has serious problems. I’ve only noticed this on the large machine, but it happens every time I use it – I load a file onto the USB stick. I load the file and start cutting. Maybe I cancel and want to reset. Then, seemingly for no reason, the controller can no longer find files on the USB stick that it was just reading a few seconds ago. Occasionally pressing cancel and trying again works but usually I resort to a full reboot of the controller and even then often the reboot isn’t enough and I have to reboot again or even three times. This is particularly annoying in that the controller gives untrustworthy messages about the state of the home setting. It generally seems to remember the home position but the controller will always ask if you really want to continue without a set home.
-
I’ve seen both the large and small machines terminate prematurely for no apparent reason. There is no way for the devices to show status so I have no way of knowing what error faults might have been triggered. Maybe I’m seeing this often because my cuts involve a lot of detailed instructions (i.e. long gcode files comprising many small movements). But really, I have no idea why it happens sometimes and not others.
-
I’ve seen both machines dramatically lose track of z. In the most extreme case while using the smaller machine I had a run that suddenly decided in the middle of a run that the Z=0 plane was about 3 inches higher than it was just a few seconds before. This can not be explained by a tool slipping – the program was clearly running much higher. Furthermore, it can not be explained by a bug in my gcode as I re-ran the same exact file (after resetting z) on the same material and it ran to completion without incident.
-
The spoil board on the large machine in the “A” section has been sufficiently carved-into that it can no longer pull a sufficient vacuum to stabilize work. This is expected and it would be easy to accommodate for between resurfacings by simply using the further vacuum sections (like the E) except for the fact that the z-puck doesn’t have a long-enough cord meaning that I have to resort to manual Z; however, manual Z is particularly problematic for me because my cuts involve tool changes and the precision of the paper method is tricky. Maybe there’s a way to attach a longer cable to the z puck?