armbian in the full desktop version runs noticeably slower than it runs on
amd64 stuff, but its more than fast enough to run a full screen gui for a 3d
printer. I'll gladly tolerate a just noticeable lag that never crashes,
uptimes from kernel update to kernel update, with klipper/moonraker/fluidd
feeding nginx, broadcasting to any web browser in the house that is watching
aliasname:80, in exchange for an 18 watt power draw (including its 24" AOL
monitor) while sitting idle between jobs. I use firefox to localhost:80 on
the local machine actually running the printer at speeds around 10x what it
could do OOTB 4 years ago when it was new.
FWIW, I probably have another $2000 in better hdwe., much of which I
designed in OpenSCAD. I may ask what seems to be off the wall questions
simply hoping to glean additional info because I enjoy plowing new ground
and making it work better. Part of the upgrade is closed loop
stepper/servos, because they have at least a 10x improvement in the accuracy
of motor control. The error at the instant determines motor current, running
at 7x speeds, average motor power is 30% of the burn your hand temps the
usual setup does, it can even reverse a motor that overshoots, putting it
back where it belongs using around 4x the instant power if it has to. The
latest addition is a motorized nozzle cleaner, operated as part of the
startup gcode.
I've got to get my web page up again, I lost it when those two seagate 2T
drives went offline at 2 weeks accumulated runtime as I was trying make
bookworm run now 18 months ago. It runs when it gets around to it, opening a
local file is an automatic lockup for 30 seconds. And no one has identified
that problem. Around 30 fresh installs with the only usb plugged in being
the wireless button for logitek keyboard/mouse but I still get orca and
brltty yelling every keystroke at me thru my speakers. Yet when I question
the broken bookworm installer, I catch hell from the powers that be here.
Total denial that the problem exists has been the universal response.