Voron Trident Can Bus EBB36 X end stop relocation

 

There is so much to change on the carriage that it must be removed.

You can see the Xstop wires here.

Voron Trident Can Bus EBB36 upgrade

Note: the printhead LED's connector is reversed.

also reversed is extruder motor (fixed in config).

There was a sticker on the TMC2209 that prevents heat sink to stick.

Recommended order of assembly:

Remove cable chains.  Install both X and Y endstops.

best STL that I found:

https://www.printables.com/model/429169-rigid-ebb36-v12-mount-on-voron-cw2-stealthburner-t

Using BTT u2c 2.1

BTT EBB36 v1.2

https://github.com/EricZimmerman/VoronTools/blob/main/EBB_CAN.md

The End stops must be moved, also need mounts for umbilical:

https://mods.vorondesign.com/detail/ho9WEyf6msbGKhTbtM59mQ

The X-endstop uses existing mounts on the carriage.

Can Bus Cable

I used silicone wire (red/black) 18g and 22g and 1/4 inch nylon sleeve.

You have to widen the end of the sleeve by cutting it off, putting it on
a x-acto knife and re-melting.

It needs a stiffener 3mm nylon or PTFE

I think the opposite twist was good, making the sleeve a bit easier. 
The stiffener (either ptfe or nylon) was critical.

It was somewhat difficult in spite of seeing it done at work so many
times...

Very important to verify that the connectors fit well.

Setup canbus on voron:  (i used 500000, and i think by doing it in this order, it propagates).

https://github.com/rlaferla/Voron/blob/main/CAN_Bus_Guide.md

Setup u2c, follow instructions from:

https://github.com/bigtreetech/U2C/issues/4

setup ebb36 

Follow instructions from:

https://github.com/Arksine/katapult

and 

https://github.com/bigtreetech/EBB  (klipper build settings)

Wiring:

24v probe is problematic.

VERY IMPORTANT, don't forget to remove the USB jumper on the ebb36.  Also, if your canbus cable power works, the power LED lights up on ebb36.

References:

https://forum.vorondesign.com/threads/can-bus-upgrade-information-and-sources.323/

https://bttwiki.com/U2C.html#optional-wiring-diagram

https://lab4450.com/product/ebb36/

https://os.ratrig.com/docs/toolboards/btt/ebb-36-12/

Commands:

edit canbus settings

sudo vi /etc/network/interfaces.d/can0

update canbus #must reboot#sudo ifconfig can0 down;sudo ifconfig can0 up

Show canbus speed:

ip -details -statistics link show can0

hit reset button on EBB36 to bring board into remote mode.

Scan with klippy

~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0

python3 ~/katapult/scripts/flashtool.py -i can0 -q

Flash EBB36

 python3 ~/katapult/scripts/flash_can.py -i can0 -u e3972ab4348d -f ~/klipper/out/klipper.bin

https://developer.amazon.com/docs/fire-tablets/connecting-adb-to-device.html

Fixing windows privileges

 Doesn't seem to work on windows 11.

trying Tweaking.com - Windows Repair

A:  I like to force a disk check with the command "chkdsk /F C:"

<windows><r>
chkdsk /F C:
<ctrl><shift><enter>
y

then reboot

B: fix privileges %userprofile%

ICACLS %userprofile% /T /Q /C /RESET 

takeown /R /SKIPSL /F %userprofile% /D N

then reboot

Orange pi 5 setup

 running from microSD.

remove "pro"

https://askubuntu.com/questions/1434512/how-to-get-rid-of-ubuntu-pro-advertisement-when-updating-apt

apt-get  --assume-yes  --purge  remove  ubuntu-advantage-tools

apt-get install rsnapshot

apt-get install samba

(I used apt-get install samba* and i think it installed a lot more than necessary)

apt-get install unison

crontab -e

0,15,30,45 *   *   *   *   /home/matt/start_unison_movie

#40 23 * * 6 /home/matt/rsnapshot_run

40 23 * * * /usr/bin/rm /home/root/.unison/lk*

*/5 * * * * /bin/touch /media/matt/2tb_prime/touch &>/dev/null

#*/5 * * * * /bin/mount /dev/md0 /media/backup

secret privilege

GRANT PROXY ON ``@`` TO `matt`@`localhost` WITH GRANT OPTION

add motd file:

98-custommotd 

#!/bin/bash

echo

cat /proc/mdstat

dmesg |grep Gb

echo

Prusa Slicer Voron Profiles.

The Voron profiles are not very similar to the Prusa MK3s profiles.

The short way is to remove the "Compatible printers condition" restriction to be a prusa....

Set the printer to Prusa MK3s.

Filament to "Generic PETG".  

Switch tab to "Filament Settings".

go to sub tab "Dependencies"

Remove Prusa Vender string in compatible printers condition.

The long (but still useful way is)

In PrusaSlicer 2.6 Set Printer to Voron.

Set filament profile to Basic PET.  

Open tab for "Filament Settings"

Click on save profile (you need to have a local profile to overwrite)

Click on Prusa Diff (mouse over says "Compare this preset with some other"

Check "Show all presets (including incompatible)"

Change left box to "Generic PETG"

All of the changes will be visible...

On the bottom (in 2.6 only) is a check box "transfer values from left to right"

64bit Voron USB setup

 Use Pi Imager to install Klipper 64bit (with login/wifi)

if wifi doesn't work enable by updateding wpa_supplicant

install kiauh

use kiauh 

             install octoprint

                    restore backup

                    uninstall filament sensor, then install

                    klipper config directory:

            uninstall klipper

            install klipper

                   https://www.klipper3d.org/Installation.html

            update all

mount SD card

mount /dev/mmcblk0p1 /media/pi/boot

mount /dev/mmcblk0p2 /media/pi/root

make pi sudoer

/etc/sudoers.d/010_pi-nopasswd

apt-get install samba

 smbpasswd -a pi

enable SPI

sometimes mainsail conflicts with octoprint.

systemctl disable moonraker.service

or 

systemctl disable octoprint.service

Octoprint/Klipper diagnostics

When you install the kiauh way:

klippy.log is in ~/printer_data/logs 

read log via 

~/klipper/scripts/logextract.py ~/printer_data/logs/klippy.log

When you install the Octopi way..

Klippy.log is in tmp.

read Klippy.log using  ~/klipper/scripts/logextract.py  i.e

cp ~/tmp/klippy.log . 

~/klipper/scripts/logextract.py  klippy.log 

Octoprint logs are in:

~/.octoprint/logs

its not uncommon to have klipper fail to connect if you use mcu_pi.

to restart klipper, type following in linux login

sudo service klipper restart

systemctl stop octoprint

service klipper restart

systemctl start octoprint

to add debug into .cfg

{ action_respond_info("_PRINT_START") }

alias cssh='ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null'

sudo service klipper stop;rm klippy.log ;sudo service klipper start

swap between octoprint and 

sudo systemctl disable octoprint.service

sudo systemctl enable moonraker.service

or

sudo systemctl enable moonraker.service

sudo systemctl enable octoprint.service