The Good And The Bad Of Living With Azteeg X5 Mini WiFi
Once the Azteeg X5 Mini was properly installed in my Monoprice Maker Select, the printer went right back to work making parts for Sawppy. I'm extremely happy about how quiet the stepper motors are running. The loudest noise by far is the power supply cooling fan, which is at least a steady white noise that more easily fades to the background versus the constantly varying sound of stepper motors printing an object.
The first test print with X5 Mini in control showed signs of under-extrusion. Tuning extrusion parameters is a continuing challenge but I blame the printer hardware and not the electronics control board for that issue. This was eventually solved by upgrading the entire print head, a story to be covered later.
While the core functionality is pretty solid, some of the auxiliary features of a Azteeg X5 Mini are rather less so.
The most irritating problem is its WiFi feature. Out of the box it acts as a WiFi access point with default name and password. There is a menu to change the default name and password so my printer wouldn't be vulnerable to pranksters in range. After changing those menu values and rebooting as recommended, I can see my new "AP SSID" and "AP Password" values in the menu. But the actual access point continued using the old SSID and password as if the menu had no effect. I'd like to think such a glaring security issue would be patched by now, but I just have to wait for them to fix this.
Separate from the WiFi issue, there are some problems upon startup, manifesting itself in one of three ways:
- Upon power-up, the status LEDs usually start blinking. But every once in a while, the onboard LEDs are solid on and not blinking. The board does not respond at all in this state.
- Even if the LEDs start blinking and the board responds, it may boot into a state where all control communication looks OK but nothing moves. It will talk to my OctoPi as if everything is OK: The board will accept G-code and show progress processing them and return "OK" after every command... but no motor movements occur.
- Even if the board responds to movement, occasionally the homing cycle at the beginning of a print job fails for no reason I could diagnose.
In all three cases, the workaround is to turn off the printer and turn it back on again. This can get annoying at times because it sometimes require multiple on/off cycles to get there. Once printing actually starts, everything performs well. And the best part - no smell of stress electronics threatening to burst into flames.