Agreed but at least visually, the CR-6 looks to be in a different class to the Enders. Be interesting to know if it's just appearances.
@Rilot That CNC is clearly subtractive machining and therefore not at home in an additive forum
Looks good though. Hefty linear rail on the back there. Is it limited to Aluminium by the spindle or can it handle steel? I'd have guessed by the size of the rail that with the right spindle it could handle something tougher.
@Vince Sorry, missed out on notifications for a couple of pages worth. Mini Nuke is looking nice.
@ChrisLX200 Had my printer in bits again but have had a go at adjusting the wheels. Seems the inner wheels are adjustable and the outer not but I think the whole plate is on slots so loosening the screws adjusting and then tightening them seems to have allowed me to get a reasonable balance....I hope. Proof will be in the printing but spent all my time swearing at inanimate objects in an entirely sane fashion
OctoPi networking issue. I took everything (the control box, specifically) apart again.....and again....and again - hence the swearing - because I had issues with the Pi running OctoPrint. It stopped connecting to my wifi on at least half the boots if not more. Then found it wasn't pingable reliably but I could SSH into it and the web interface was working. All very odd and I put it down to wifi being as reliable as your average plumber (apologies to any plumbers reading, if you're offended you're clearly above average
) and also that the Pi was shut inside a steel box.....which obviously is great for signal propagation! Ordered a panel-mount ethernet port and have shoe-horned that into the case too. This was going to fix the problem. Tested it, all fine. Put it together, nope. After much faffing about (Pi has to be unmounted to get an HDMI cable in), I found that sometimes when it boots dhcpcd reports "eth0: waiting for carrier" and then "Timed out". "Fixed" this by setting a static IP and testing it worked. Put it all back together and it decided it wasn't going to stay working. You can see why there was swearing, right? Anyway, it seems that sometimes it correctly initialises networking and sometimes it doesn't. If it does, it works fine. If it doesn't then restarting dhcpcd or downing the interface (ifconfig eth0 down) and bringing it up again make no difference. I don't know why it happens but I do have a badly-implemented workaround that perhaps some of you can improve and at worst it might spare someone the diagnostic phase if they have the same problem.
This is the thread I found:
https://www.raspberrypi.org/forums/viewtopic.php?t=269898
My workaround is to add "ethtool -s eth0 autoneg on" to /etc/rc.local both before and after the octoprint stuff - just adding it before didn't seem to work 100% of the time - like I said, this is a badly-implemented workaround and almost certainly in the wrong place. The same could probably be done for wlan0 but perhaps a different command - any successful ethtool command seems to bring it to life. Incidently, I tried reflashing the SD card with a new copy of OctoPi and it did the same. I've also tried apt-get upgrades, full-upgrade and dist-upgrade as well as uninstalling and reinstalling dhcpcd5.