Smoothiedriver is a series of motor driver pcbs that are designed to connect to the no-driver series of Smoothieboard (coming soon). At the core of the system is the 3 pin parallel stepper system used on modern repraps: Enable, Direction, Step. All Smoothiedrivers support at least this basic interface which is compatible with older AVR based motion controllers such as RAMPS.

The first Smoothiedriver is a dc motor controller with encoder feedback, implemented as a full h-bridge driven by an ARM Cortex-M0 microcontroller. The current prototype is a triple channel controller that can drive 3.5A per channel. More drivers are planned and are in development from stepper drivers that can handle over 2A with 64x microstepping to bldc controllers!

This image shows the board layout of the Smoothiedriver interface:

» –> <img src=“/_mediaexternal/” undefined> </html>

You can download the eagle files for that image to check sizing here:

Smoothie-compatible motor controllers

  • Class X2. Electrically Compatible
  • En-Dir-Step electrical interface
  • Class X1. Hardware Compatible
  • all requirements of Class X2
  • East edge pinout compatibility w/ Smoothieboard no-driver

The Pololu a4988 breakout boards commonly used in RAMPS boards and the CW4050 are examples of Class X2 Smoothie-compatible drivers as are most external stepper drivers that support parallel interface.

Smoothiedriver motor controllers

  • Class 2. Basic Smoothiedriver
  • all requirements of Class X1
  • En-Dir-Step pins become En-Sda-Scl when En is disabled to receive basic config
  • North-South hardware i2c bus is passed through
  • Class 1. Standard Smoothiedriver
  • all requirements of Class 2
  • hardware i2c bus fully supports the Smoothie Accessory Protocol

The first true Smoothiedriver will probably be the Smoothiedriver DC. It will begin as a Class 2 Smoothiedriver until firmware for full Class 1 support has been completed on both sides (Smoothieware and Smoothieware Mini.)

The first Smoothiedriver DC-2 prototype had firmware but it was using a different mcu than is currently being targeted so the firmware will have to be rewritten. On the bright side mbed just went open source so now the same libraries can be used for both Smoothieware and Smoothieware Mini!