Hi,
I got my M4 machine up and running but it randomly kicks my connection to it. I’m using an android phone to control the M4 but I did disable all of the phone’s other wireless connection like bluetooth and mobile data and even removed the sim card to ensure the phone wasn’t trying to hop onto other networks in an attempt to link to the internet. I also find If I try to link my PC to the M4 it also has a hard time connecting to it and does occasionally get kicked off the connection when it does connect. The worst problem is that the M4 has not yet successfully completed a cutting job. I’m generating my gcode for cutting jobs with Estlcam if that helps explain anything. The machine will cut well, with good accuracy, then all of a sudden it will just stop moving and lose the job. I would give a print out of the console codes when the machine crashes but when the machine stops in the middle of a job it also kicks my connection to it and when I reconnect, the console looks fresh (like the machine just booted up) so I can’t even review any error messages it may have generated before or during the crash. I should probably mention I’m trying to run the same file each time and that the machine is failing at different points in the job durring each attempt so I don’t think the file is the issue.
Also, as of updating my firmware to v0.80 the calibration is not running correctly, I have it set to do a 9x9 grid that is 2000mm x1000mm, it does maybe half of the points of the 3 x 3 grid than claims the calibration process is complete, than kicks my connection to the machine. Strangely, when I reconnect to the machine, it actually moves accurately but leaves way too much slack in the belts it isn’t pulling with and then even will occasionally will make erroneous movements (for example I might tell it to move left on the X axis 20mm and it will move a bit to the left and up on the y axis and then on the z axis until it’s about to top out and I have to kill the power to it).
The first time I attempted a cut with the M4, it lasted the longest (~4 hours) but it has been pergessivly shorter on each attempt before crashing (my last attempt today, the machine only got 25 minutes into the job before crashing) so I suspect that something is degrading as I use the machine and since the issue are kind of all over the place I suspect it might be the motherboard but I was wondering if anyone had any other ideas as to what’s going on before I sink more of my very limited resources into buying a new motherboard for my machine.
Hi Zach, the wifi/connection problems are certainly not my forte, but I can try to help while Bar returns from his trip!
The serial log would be really helpful here to see what sort of error is causing the disconnection. I think the disconnection pop up that allows you to save the serial log may not be working on your phone for some reason. Were you able to see the pop up on your PC when you connected briefly? There is a slight delay on the pop-up too, so if you refresh the browser or cut power too quickly you may not be seeing it.
Also the shorter and shorter duration of the cuts makes me wonder if this is the dust-build up problem with the encoders. The temporary fix for this is to hit the encoder board connections with some compressed air. That might be worth a shot while we troubleshoot.
I’m connecting to the M4 in AP mode and using maslow.local. As I’m using it away from the house where there is not wifi. Also, I tried what Anna suggested and blew out the encoders with compressed air. I then wrapped them with some electrical tape to prevent dust from getting in them in the future and ran a smaller cut job. It failed about an hour in (about 2/3 of the way through the job) and when I checked phone it had been kicked from the M4’s network and automatically closed the page (android trying to be “helpfull” I guess). When I logged back on, the machine acts like it has been power cycled, the readout is wiped to job is no longer loaded up and the machine refuses to move until I go through the whole setup process again (retracting in all the belts and unreeling them again).
I’m starting to suspect that a power delivery issue is at play. I have the machine so far from the house, I’m using 2 50’ extension cords to deliver power (they are both rated for 16 amps but I know it’s still not ideal).
My brother just gave me an old windows laptop, so I’m going the try using it to interface with the M4 (instead of my Android phone), so if something goes wrong again I can actually review and save the log. Also, I found a spot closer to the house where I will only need one extension cord to reach everything so power delivery should be more robust.
I will probably try to do another cut in a few days and will keep you updated. Thanks again for your suggestions thus far
Hey so I tried the spot closer to the house with the old laptop and…success:D I also tried simulating a power failure (quickly unplugging and plugging the machine back in with the laptop running and the machine was behaving exactly as it did before. Except now with the laptop, it kept the old interface open and just opened a new interface in a new tab so I could review what was happening before the machine reset. Now I’m almost certain it was a power delivery issue (from the wall and not on the machine itself). it’s done 2 cut files without issue and is currently cutting a third (part of a large job I’ll post on here when it’s done). I’m very impressed with the M4, now that everything is running smoothly. Thanks for your help and advice (I did hot glue the encoder wires like you suggest in the latest update, just to be sure dust ingress wasn’t the issue and won’t become one in the future).
