Awesome video! Just want to say as a RU-vid Creator myself, this is a great information channel. I've watched a bunch of videos on this subject and hands down you tell it the best! I know my channel isn't huge yet but definitely working on it, I'm definitely going to give you a big shout out on my next video so maybe it will bring you some of my viewers. Thank you again for such a great video! 👍👍
This video gave me a solution for a 2 day long problem. I had no CAN device no matter how I flashed the CAN toolhead board. Not a single guide mentioned that, I need to reflash my main FW on the Octopus to set it up as a USB to CAN converter. After that it was a piece of cake. Thank you! 🥳🥳💚💚
I had my 2.4 350 using an Octopus pro via usb to can bridge and using a sb2209 rp2040 with can via the Octopus pros’s rj11. I had just over 1000 hours with a timer to close error maybe 3 times, I added Siboors ercf kit to my printer with btt’s new CEB and could not get a print finished without a shutdown due to a timer to close error. After changing the btt mmb to usb I could get further into the print, then I turned off my sb LEDs and was able to get further but still not able to finish. I spend the past 2 weeks trying to fix it. I tried changing the sd card, unplugged my webcam, then Upgraded to btt pi2, when that didn’t work I changed the sb2209 to a known good 1, still got the error, changed the Octopus to another know good 1, same error. I added a btt u2c as a last ditch effort and was able to finish a print! Put my old btt pi1.2 with the original sd card, put the mmb back on can using btt’s ceb, sb LEDs back on, plugged the webcam back in and everything’s good so far, I have 12 hours without a error so far. It was a timer close error with ebbcan shutdown. So after that enjoyable situation I think I will always use a dedicated usb to can board. My Micron 180 is can with the Manta mp8 and ebb36 with over 1300 hours but I do see a timer to close error every 300 hours. I have 0 room to add anythinh in the electronics compartment so I’ll have to live with that one.
hey so I have the exact same board and followed everthing up to getting the canbus id... but it does not find the octopus boad and instad says " Total 0 uuids found" and does not give me the id. Any ideas a to why?
Another question please,, 🤣🤣 so something is defective with my ebb sb2209 - (rp2040) board, I have a replacement can I just re flash the can board and install it and get right back to working order or do I have to go threw all the flashing from the btt pi to the octopus pro board?
Yeah there was a bad batch sent out. I notified them about that and they made a post about it on their discord. Unfortunately they had already sent out a large portion of that batch. Luckily it's a very simple fix and doesn't damage anything if reversed.
Sorry I don't understand the question. Are you talking about the configuration menu for making the firmware? For those you need to be in the correct directory. For example for klipper firmware you have to be in the ~/klipper/ directory before running make menuconfig
Yes it's virtually the same process. You'll just have to set up the make menuconfig according to the MCU onboard. Overall the boards do the same thing.
I didn't have one specifically for canbus, but all you need to do is add it to the configuration of the EBB. It would be virtually the same config setup as shown in my other accelerometer video. Just skip over the flashing firmware parts. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-FBWj8q5e6Wo.htmlsi=s7jC4vPrI-DHEz_n
If you have the BTT sb2209 as shown in the video this is what you need to put in the printer.cfg. note that its common for the MCU to be labeled [mcu EBBCan] or something like that. I use [mcu sb2209] so that is why my pins start with sb2209: change that to match whatever your MCU is named. [adxl345] cs_pin: sb2209:gpio1 spi_software_sclk_pin: sb2209:gpio2 spi_software_mosi_pin: sb2209:gpio0 spi_software_miso_pin: sb2209:gpio3 axes_map: z,-y,x [resonance_tester] probe_points: 100, 100, 20 accel_chip: adxl345
I have an octopus board 446 that i am trying to set up canbus using btt ebb36 So i bought the rj11 to can cable and the cambus cable for the sb2209 cuz I didn’t want to make a canbus cable and that one is much cheaper. My question is how to avoid frying my boards The rj11 to molex female doesn’t show which wire is can h and which is can l Any idea how to verify
It only uses the 2 center pins for canbus the rest are not connected to anything. With the rj11 port facing you the left (pin 3) is can high and the right (pin 4) is can low. In my plug it's red for high and green for low which seems to be standard for those plugs but it's best to probe for continuity to be sure. Luckily hooking up canbus in reverse will not burn anything, it just will not communicate. Just never connect power lines to canbus lines that will damage things.
There can be many reasons fom missing or incorrectly placed 120r jumpers, to non matching bitrates. There is also evidence that the RJ 11 plug for the octopus has been wired backwards in a batch so there's a chance that the wires need to be switched 180 degrees. If you have only the octopus plugged in to the host and nothing else connected via canbus, can you get the octopus UUID?
Hey there, so i´ve been trying to setup a SB2209 with a STM32G0B1 according to your tutorial. Somehow whenever trying to flash katapult get : make: *** No rule to make target 'flash'. Stop. Any Ideas maybe? Thanks anyways for this tutorial!
What is showing in lsusb when you put the sb2209 in DFU mode? It is a little different than the rp2040 version. Also are you setting up the make menuconfig for the stm32G0B1 and not the rp2040?
@@StackingLayers hi, thanks for the quick answer so far. It gives me the Id, as well as the STM Controller in DFU mode, so i guess going into dfu mode worked. The make menu i set up for the STM according to the manual for the board. Actually i can even install the klipper firmware without a problem with the same settings and process, katapult doesn't seem to want tho... :)
Hey, thanks for the tutorial. As I was following up your instructions I stumbled upon an old problem I had trying to flash through USB. I had confirmation "File downloaded succesfully" like in your video. But after flashing board is not listed inthe connected USB devices. Do know anything about that?
If you are flashing the firmware set up for canvas it will no longer give you the dev/serial/by-id/* you need to get the UUID using this command, ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
So I get this "Found canbus_uuid=b9cfdc5584ef, Application: Klipper" and lsusb Bus 001 Device 004: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapter But still mcu can't connect. I couldn't flash my EBB36 and it is disconnected. Is it required to connect the canbus in order for Klipper to connect to Octopus Pro MCU in this config.
@aphlox you will have to flash the EBB36 to communicate over can us and it is important that the bitrate matches the other canbus nodes. Most common now is to use 1000000. No you shouldn't need other can devices connected for only the octoPro to work but you should not connected it to klipper until you have the other devices set-up too. I've seen people having issues getting things setup that way. Get all boards flashed and providing their UUID, then set it up in the printer.cfg
Send, make clean Then run the, make menuconfig to make the firmware again, also make sure you are in the correct directory when doing that. /klipper for klipper firmware and /katapult if you are doing katapult
Does not detect uuid application:katapult but it gives query complete I've been trying to finish the setup I am unable Has anyone had the same problem? I want to thank everyone for their answers because the video is excellent, it's my fault because I have little experience,thanks.
Are you able to get a UUID if only the octopus is connected to the host? There has been a bad batch of the rj11 wires where the can high and can low are reversed. If the high and low are reversed thus can happen. Other things is if the bitrates are not matching, or other firmware configuration errors.
