RailCore® is a family of Core-XY based Reprap 3D printers designed by J. Steve White, Tony Akens, and Ben Withem.
The RailCore kits ship with Duet boards running RepRapFirmware (RRF), and the official configs are for RRF. Plenty of RailCore owners now run Klipper instead. This section covers what changes, which boards work, and how to set a RailCore up.
z_tilt,
probe, mesh, homing, input shaping and macros, step by step.CHECK: must be verified on your
machine.RRF on a Duet is a complete, well-supported setup. Nothing about the RailCore requires Klipper. Switch if you want one of these:
exclude_object, and a large pool of community macros.Stay on RRF if your printer prints well and you don’t want a second computer in the loop, or if you rely on Duet Web Control, a PanelDue, or RRF features such as its standalone (no host) operation.
| RepRapFirmware (Duet) | Klipper | |
|---|---|---|
| Where motion is planned | on the Duet | on a host computer (usually a Raspberry Pi); the board only steps motors and reads sensors |
| Config | config.g plus homex.g, bed.g and other macro files on the SD card |
one printer.cfg (plus [include] files) on the host |
| Changing config | edit, then M98 P"config.g" or reboot |
edit, then FIRMWARE_RESTART |
| Web interface | Duet Web Control | Mainsail or Fluidd (through Moonraker) |
| Display | PanelDue | KlipperScreen on an HDMI/DSI touchscreen; the PanelDue is not a standard Klipper display |
| Three-motor bed leveling | M671 leadscrew positions + G32 running bed.g |
[z_tilt] section + Z_TILT_ADJUST |
| Mesh | M557 + G29 |
[bed_mesh] + BED_MESH_CALIBRATE (optionally adaptive) |
| Steps | steps/mm (M92) |
rotation_distance (mm per motor turn) |
| Motor current | M906 in mA |
run_current in amps RMS |
| Probe offset | G31 X Y Z |
x_offset, y_offset, z_offset in [bltouch] or [probe] |
| Homing | homeall.g, homex.g … |
[stepper_*] endstop settings + [safe_z_home] or [homing_override] |
Klipper names the two CoreXY motors stepper_x and stepper_y, but they are the A and B belt
motors, not the axes. On the RailCore II kit the rear motor (Duet X port) is stepper_x and the
front motor (Duet Y port) is stepper_y.
Klipper supports the Duet 2 (SAM4E8E processor); start from Klipper’s generic-duet2-duex.cfg, or from our 300ZL sample, which already has the RailCore wiring. Know the limits first:
FIRMWARE_RESTART.bossac after erasing the board (Klipper’s
Bootloaders guide, “SAM4 micro-controllers”). To go
back to RRF, erase and flash the RRF firmware the same way.Klipper supports the Duet 3 Mini 5+ (SAME54 processor) and its Expansion Mini 2+ drivers; start from Klipper’s generic-duet3-mini.cfg or our Mini sample. The same USB-only and back-up-first notes apply. The Mini sample has had less real-world testing than the 300ZL one.
Any board Klipper supports will run a RailCore. You need at least six stepper drivers (X, Y, three Z, extruder) and an input for the probe. Common choices:
Use the matching generic-*.cfg from
Klipper’s config folder for the pins, and
take the machine values (rotation distances, leadscrew positions, probe offsets) from our
sample configs.
Then follow the RailCore Klipper config guide.