CANBus not going well. EBB SB 2240/2209.

[Broken3Dprinter]

Getting errors when I try to flash the bus after getting the id off of DFU mode. I have tried to install it before, but I couldn't get the MCU to show up to put the info in the config file.

I get this error.:

Flashing out/klipper.bin to 0483:df11
sudo dfu-util -d ,0483:df11 -R -a 0 -s 0x8002000:leave -D out/klipper.bin
dfu-util 0.11
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading element to address = 0x08002000, size = 36440
Erase [=========================] 100% 36440 bytes
Erase done.
Download [=========================] 100% 36440 bytes
Download done.
File downloaded successfully
Submitting leave request...
dfu-util: Error during download get_status
Failed to flash to 0483:df11: Error running dfu-util

Is it possible that it has already been loaded? If so, how do I determine the name of the MCU? Nothing shows up with the id serial lookup command.

Thanks for any help

Joel

 

[lomasjr]

Forget about the dfu-util: Error during download get_status. You actually were successful at flashing klipper. However since you put a klipper build for canbus, you won't be able to find the device via serial/by-id. You have to issue:

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

That will retrieve the canbus_uuid that you can the configure in printer.cfg.
Make sure also you have setup can0.
Please read the configuration guide @ https://www.klipper3d.org/CANBUS.html#host-hardware

 

[Broken3Dprinter]

Thanks for the information. Still not getting anywhere. It would be wonderful if someone had a Voron IT service where you could call and get all my questions asked. I did have the printer working briefly, but I wanted a different probe, and I figured while I was at it, I would go ahead with a can bus to reduce the number of wires. If there is anyone out there that can help, here is what I have:

Voron 2.4 with Stealthburner. Revo3D hotend
BTT EBB SB 2209/22040
BTT U2c
BTT Octopus
Raspberry pi
Beacon probe

I have gone through all the steps of installing these. I'm trying to work through the Config file.
1. How do you tell the config file to use a UUID/
2. What do you use in the config file if it asks for a serial with the UUID?
3. When you use the ls /dev/serial/by-id/* command, what should show up? Currently when I do this, it only shows the address of the Beacon. Should the Octopus MCU, Beacon MCU and EBB2209/2240 all show up?
4. If I start from scratch (again), do i need to do something to the Octopus board to "reset" it?

Apologies if this seems elementary to some, but I've spent 20+ hours trying to set and reset the software. I feel like I'm missing some core knowledge here.

Thanks in advance if anyone can help

Joel

 

[Sandman50]

Home

A guide for setting up CANBus hardware on 3D printers

canbus.esoterical.online

Follow this guide. Possible to start from step 1 and redo the work just to ensure it's all correct.

The other thing about CAN is that it's a bus communication tech, so the wires are connected H-H and L-L. Not H-L, L-H

1) Like this:

[mcu]
canbus_uuid: ca90cdaf1bc3


[mcu EBBCan]
canbus_uuid: 41aa0e263ad8

2) Use either the uuid, or the serial address. But if you are going with a CAN toolhead, then both the MCU and the toolhead will be addressed via canbus_uuid. (I may be wrong with the U2C board... I've never used one).

3) IIRC, it needs to be in DFU mode to see via that command line.

4) The mainboard needs to also be flashed with katapult/can

IMHO, I'd start from scratch.
When I'm bringing up a new board I keep a notepad open as well as there's some copy/paste required to create the command lines. Simpler there than inside putty.

 

[5twenty]

Page 7 is what helped me go: AHA! (https://github.com/bigtreetech/U2C/blob/master/BIGTREETECH U2C V1.0&V1.1 User Manual.pdf)

Also, irrespective of which board you have: https://wiki.kb-3d.com/en/home/btt/voron/u2c_v2

Those two helped me tremendously. I wasn't understanding how it should go, until I saw that picture in the BTT guide. I have Mellow U2C though, and it is running excellently now. I also have some BTT U2Cs lying around that I can now utilize thanks to those.

Don't forget: you are flashing each CAN item separately, via USB and Pi (or whatever board you are connecting to - I have a Manta and CB1 that I'll be using now, again thanks to the above), THEN connecting and identifying.

It's a bit confusing, unless you do this a lot (at least for me it is).

All these skills are, as the Army likes to say, perishable. If you don't use them often, you'll be back at square one each time you do. And if you aren't building 3d printers or other devices that use these electronics every day, you'll lose a lot of knowledge.

And Sandman50 is correct, in the sense that he is incorrect : You WON'T need a CAN ID for your MCU. At least I didn't.

My Switchwire is setup thusly:

[mcu]
###Change to device found by "ls -l /dev/serial/by-id/" with just one this MCU connected to Pi
serial: /dev/serial/by-id/usb-Klipper_stm32g0b1xx_080025000B504B5735313920-if00

####################################################################
#    SB2040v2 Settings
####################################################################
[mcu SB2040v2]
canbus_uuid: 534f81d945dc # SB toolhead

 

[Broken3Dprinter]

These were helpful, thank you. I have my canbus uuid. Unfortunately, now I can't determine my Octopus UUID or serial. I've tried hooking the pi up to only the octopus, but I can't get anything to show up with the ls /dev/serial/by-id/* command.

pi@voron24:~/klipper $ ls /dev/serial/by-id/*
ls: cannot access '/dev/serial/by-id/*': No such file or directory

I've searched all over for an answer. I've double checked my menuconfig settings. I've hooked the pi directly to the octopus, leaving the canbus out of the loop.

Is there some way that I need to reboot or reset the octopus?