Scott Alfter  wrote:
>
> 3D printers pretty much always have some sort of microcontroller running
> them directly...anything from an 8-bit AVR on up to ARM-compatible devices
> like the LPC176x or STM32Fx families.  Any of these are sufficient for
> accurately firing stepper motors, monitoring endstops and thermistors, etc.
> in a Cartesian or CoreXY printer configuration; more advanced kinematics
> (such as Delta or SCARA) sees more benefits from a 32-bit controller.
>
> To the extent that a Raspberry Pi is involved in 3D printing, it's usually
> just streaming gcode to the printer's microcontroller.  Even if you're
> running something like Klipper (which shifts more of the motion-control work
> to the Raspberry Pi), you're still streaming some sort of simplified command
> sequence to a microcontroller that provides the necessary realtime control.

That's true for "usually", though it's not always the case:
https://github.com/Wallacoloo/printipi

Also, with LinuxCNC:
http://soundproofingforum.co.uk/rpi_linuxcnc/raspberrypilinuxcnc.htm

--
__          __
#_ < |\| |< _#

--- SoupGate-Win32 v1.05