Closed albrecht-flo closed 12 months ago
Has the bus been terminated? There shouldn't be any errors at all in either setup.
Thank you for your reply.
Yes the bus has been terminated.
The problem seemed to originate from powering the CANPico through the Picos' VSYS instead of a USB cable, when powered through a USB connection it works.
That fixed the issue for me, it has nothing to do with the SDK. -> Closing
Ah, I can tell you from experience that the CAN transceivers really don't like being under-voltage. They mostly just work , of course - until they don't. I once chased an intermittent error like this for hours until I discovered the power to my USB hub had fallen out the back and the hub was now not delivering a proper voltage.
I am trying to send a package from one CANPico to the other, when running the firmware while attached to my PC via USB the packages get transmitted (with an no ACK error but still received). But when I try to run the same binary using the picoprobe for debugging I get a NBIT0ERR when trying to send anything. Initialization does not raise any errors. I can also observe this with the hello_can.c firmware file in this SDK.
Do you have any idea what might be causing this? Any help would be much appreciated. :)
I am running the CANPico with the
MCP2517FD
CAN Controller. With micropython on these chips the frames could be transmitted