-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to setup CAN network #5
Comments
Like most STM32 boards, you only need to use the CAN Bridge option to connect Cheetch 3.0 to other CAN boards. The CAN-RX / CAN-TX of Cheetah V3.0 is located on PB8 and PB9. After resetting in menuconfig, compile and upload the firmware to Cheetah V3.0. Of course, you also need to update printer.cfg. |
Hi, |
@eliwong Could you provide a setup instruction for CAN bridge mode on the Cheetah V3.0? |
I have used the Fysetc Spider WIKI to have instructions on can settings and USART communication. Also, you have an excellent Github repo about CANBUS with a great guide: Mixing both did the trick. For your canboot flash "make menuconfig", make sure you have correct jumpers settings (B0 ; GND ; 3V3 and power jumper), and set canboot communication to USB, same pins as the spider or the board (MKS Monster) used as an exemple in Maz0r's guide, because it's the same STM32 chip. I still haven't been able to use CAN and USART at the same time, so I'm stuck with USB communication, and I believe that's a limitation on the chip. Hope that will help. |
Is there any specific instructions to set up CAN bus on this board, I have searched but very little information, do I need another u2c board to set it up? |
Attempted to setup the CAN network, but I am unable to establish communication. The Pi doesn't recognize a can0 network. The BigTreeTech Octopus requires the MCU be flashed to set the board into CANbridge mode, at which point that network is visible. I don't see any documentation or firmware to do the same for the Cheetah. I need some guidance on setting that up.
The text was updated successfully, but these errors were encountered: