SK
Signal K2mo ago
Runar

CAN works, then don't!

My CAN connection is all fine and dandy on start-up, but after a while it fades with only a few connections, only to die. Anyone experienced this or have an idea for trouble shooting? Restarting the Pi restarts the CAN connection. Restarting SignalK server doesn't.
No description
No description
No description
3 Replies
barnaclebill
barnaclebill2mo ago
I've had this happen on CAN HATs that are dying. I recommend opening a shell and trying "candump can0". That will tell you if the interface itself is still up and receiving data. Then try "dmesg | grep can" to see if you're getting any errors. When this happened to me I was getting SPI bus errors on the interface, which was a sign the HAT was bad. You can also try "sudo ifconfig can0 down" and then "sudo ifconfig can0 up". That might help but isn't a permanent fix.
Runar
Runar2mo ago
So I went throught these steps and on the first candump I got nothing. After shutting it down and turning it up, the connection was once again active. Then I wanted it to die slowly as in the past, but it didn't happen while I was in the boat. This is what I got after the last dmesg:
No description
barnaclebill
barnaclebill2mo ago
Try "ifconfig can0" and see if you are getting RX or TX errors.
Want results from more Discord servers?
Add your server