Writing this down for my own history just as much as it might help someone else. I've done two nine machines so far this way. Hope this helps someone!
- Hardware used: EBB36 v1.1 + U2C v1.2
- CAN wiring: Get FEP Wire. Used to recommend 18 Gauge for Power, reclaimed twisted pair from CAT-5 or CAT-6 cable for CAN-H, CAN-L, but I've also received failures eventually from my CAT-6 cable. It's not rated for the movement. Get better cables.
Easy way to remember: Ensure power is correctly wired on each end (it's different) and then pair CAN-L with GROUND below, and CAN-H with 24V below in each of the connectors. Image references below.
- U2C: https://lab4450.com/wp-content/uploads/2022/08/u2c-connections-e1661988111305.png
- CAN: https://lab4450.com/wp-content/uploads/2022/08/ebb36.png
Plug in the EBB36 and U2C together. Double check continuity on each end and each wire before going further. Keep the cable plugged in for now
Should be labeled on the silk screen.
- Check to ensure resistance is 60 OHM on CAN-L and CAN-H lines on either end before moving on any further.
- Once validated, unplug the harness you built.
The EBB36 draws 24v, and won't get this from only the USB connection. Wire this thing up to your PSU - best to use proper crimping and everything here.
Check to ensure the node is in dfu mode with the following command:
dfu-util -l
If it's in DFU mode, you'll see a device. If not, you'll most likely get an error. Try again until you get this correct. Flash U2C with firmware from https://github.com/lab4450/u2c.
git clone https://github.com/lab4450/u2c
cd u2c
dfu-util -a 0 -D U2C_V2_STM32G0B1.bin -s 0x08000000:mass-erase:force
I tried compiling candlelight so many times, and for one reason or another it kept failing. I am determined to crack this nut eventually, but for those of you just looking for a solution this works.
sudo nano /etc/network/interfaces.d/can0
allow-hotplug can0
iface can0 can static
bitrate 500000
up ifconfig $IFACE txqueuelen 1024
pre-up ip link set can0 type can bitrate 500000
pre-up ip link set can0 txqueuelen 1024
Unplug and re-plugin your U2C and validate that the can0 interface is up and running
ifconfig can0
Should look something like this:
can0: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1024 (UNSPEC)
RX packets 0 bytes 0 (0.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Ensure EBB36 has a jumper on the USB power jumper (closest to the actual USB port) and hold down the boot0 button to put in DFU mode. Check again to see if it's in DFU mode with:
dfu-util -l
Download the canboot repo:
cd ~/
git clone https://github.com/Arksine/CanBoot
cd CanBoot
make menuconfig
- Micro-controller Architecture: STMicroelectronics STM32
- Processor model: STM32G0B1
- Build CanBoot deployment application: 8KiB bootloader
- Clock Reference: 8 MHz crystal
- Communication interface: CAN bus (on PB0/PB1)
- Enable Status LED: check
- Status LED GPIO Pin: PA13
make clean
make
dfu-util -a 0 -D out/canboot.bin -s 0x08000000:mass-erase:force
Remove the USB power jumper, and plug back in your harness.
Run the following command from the CanBoot directory:
python3 ~/CanBoot/scripts/flash_can.py -i can0 -q
If you don't see your EBB36 CAN ID, don't go further. Try again with Setup CANBoot on your ESP326. If you see your ID, then keep going.
cd ~/klipper
make menuconfig
- Enable extra low-level configuration options: check
- Micro-controller Architecture: STMicroelectronics STM32
- Processor model: STM32G0B1
- Bootloader offset: 8KiB bootloader
- Clock Reference: 8 MHz crystal
- Communication interface: CAN bus (on PB0/PB1)
- CAN bus speed: 500000
make clean
make
python3 ~/CanBoot/scripts/flash_can.py -i can0 -f ~/klipper/out/klipper.bin -u <UUID from Step 6>
You should see a progress bar, and flashing commence. If this doesn't work, go back to Step 4.
In printer.cfg, add the following
[mcu EBB]
canbus_uuid: <UUID from Step 6>
Restart the klipper firmware.
Add the following sections to your printer.cfg
[board_pins EBB36_G0B1_v1.2]
mcu: EBB
aliases:
aliases_step:
EXT_EN=PD2,EXT_STEP=PD0,EXT_DIR=PD1,EXT_UART=PA15
aliases_limitsw: # these are preferred for endstops (including klicky)
LIMIT_1=PB7,LIMIT_2=PB5,LIMIT_3=PB6
aliases_bltouch: # these are the dupont connectors for bltouch
PROBE_1=PB9,PROBE_2=PB8
aliases_fans:
FAN0=PA1,FAN1=PA0
aliases_thermistors:
TH0=PA3,PT100_CS=PA4,PT100_SCLK=PA5,PT100_MISO=PA6,PT100_MOSI=PA7
aliases_heaters:
HE0=PA2
aliases_rgb:
RGBLED=PD3
aliases_adxl:
ADXL_CS=PB12,ADXL_SCLK=PB10,ADXL_MISO=PB2,ADXL_MOSI=PB11
aliases_i2c:
AUX0=PB3,AUX1=PB4
And now, replace in your printer.cfg with the newly set alias pins where appropriate. For example, my [extruder] section looks like this:
[extruder]
step_pin: EBB:EXT_STEP
dir_pin: EBB:EXT_DIR
enable_pin: !EBB:EXT_EN
Reference the pinout for the EBB36 https://github.com/bigtreetech/EBB/blob/master/EBB%20CAN%20V1.1%20(STM32G0B1)/EBB36%20CAN%20V1.1/Hardware/EBB36%20CAN%20V1.1&V1.2-PIN.png, and replace sections in your config as appropriate. Good to test one thing at a time.
/EBB36%20CAN%20V1.1/Hardware/EBB36%20CAN%20V1.1&V1.2-PIN.png){kind=link}
Really useful guide thanks. Just for clarity Step 5 is what?
"If you don't see your EBB36 CAN ID, don't go further. Try again with Step 5. If you see your ID, then keep going."
I assume it's the section "Ensure can0 interface setup on your OS".