-
Notifications
You must be signed in to change notification settings - Fork 59
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
CAN bus states DOWN during setup #84
Comments
CAN is going to be down by default. The network service has to be brought up. If you go the route of ifupdown, you will need to install it and nettools (if using Armbian or debian or ubuntu). If you go the systemd route, the github issue I submitted should "work" and will clarify that path. For more details, see here #83 |
@clembo1 most people don't need to install anything. It's only the edge case armbian-based distros that have issues that your issue ticket covers. |
I followed your tutorial (it was great - good job :D), and it kind of fixed my issue. The can0 network is in the "UP" state now, even when rebooting. However the qlen value is only at 10 - not the 1024 its supposed to. Thank you in advance :D |
Hello people :)
I got to the klipper flashing part via katapult.
I flashed to an BTT octopus pro H723 board with the CAN adapter built in to the motherboard (so no U2C or anything in that sort is needed)
started from the beginning of the guide by making the can0 file an followed the guide through without any issues. However now when i push a "ip -s -d link show can0" command in the CLI it writes the CAN state as DOWN instead of the desired UP.
I have checked if I did everything right in the warning sign section and after what i see everything is configured correctly.
I hope you can help. Thanks in advance! :D
The text was updated successfully, but these errors were encountered: