2026-04-21 8:27 AM - last edited on 2026-04-30 5:47 AM by mƎALLEm
Hello everyone,
i want to build a CAN FD network with three NUCLEO-C092RC boards. So far i can transmit frames, as i can see on an oscilloscope. But the moment i connect TWO boards, the interrupt is not triggered. My code should activate user LED2 if it receives a frame with one specific id:
Board 1 (0x101) triggers LED when receiving message 0x344 or 0x234
Board 2 (0x234) triggers LED when receiving message 0x344 or 0x101
Board 3 (0x344) triggers LED when receiving message 0x101 or 0x234
i use a nom. baudrate of around 500 kbit/s and data baudrate of 1 Mbit/s with a clock of 40 MHz (HSE).
The Boards are connected with two short (10cm) twisted jumper cables and the jumpers for the 120 Ohm resistor are also plugged in on both baords.
when i test it in external loopback mode, it works (with ident. change)
Could this just be a problem with my wires (reflexion , parasi. C ,etc.)?
thanks a lot for the help
Solved! Go to Solution.
2026-04-28 5:43 AM - edited 2026-04-28 5:55 AM
Hello,
I don't see you put STDBY pin to 0 to wake the transceiver up.
There is an internal 10K pull down on the board on STBY pin:
But there is an internal Pull up on it (~33k). To me it's a bit conflicting:
So set the STBY to 0 (Transceiver_STDBY_Pin in your code).
2026-04-28 7:21 AM
@mƎALLEm, the datasheet says exactly the same: STBY pin needs low state for the transceiver to be in Normal mode.
2026-04-28 8:09 AM
Idk what it was, but now it works with 500kBit/s. I think, i flashed the same software everytime. Now i have just one project and change the if-statements and IDs manually.
Stdby was not the problem, because i already had frames. This is pin is set as RESET in my GPIO setup function. Now i hope, i can just bump up the speed and switch back to CAN FD. As far as i know the transceiver can handle up to 5 Mbit/s.
Thank you all for the support
2026-04-28 8:15 AM
If the Standby pin was not the problem why marking the solution as answered then?
Meanwhile, you have another issue in the clock config.
You are using HSE but you set the crystal to be 40MHz while on the board the crystal is 48MHz:
It works because you are using the same board with the same software but if you connect another CAN node it won't work because there will be a mismatch in the CAN bitrate.
2026-04-28 8:18 AM - edited 2026-04-28 8:20 AM
Another issue I've just detected in your configuration:
Nominal bitrate is at 2.5Mb/s!! You must not exceed 1Mb/s in the nominal phase with FDCAN.
2026-04-29 3:10 AM
To correct myself:
@mƎALLEm wrote:
So set the STBY to 0 (Transceiver_STDBY_Pin in your code).
The 33K pull-up resistor was on TxD pin of the tranceiver while on STDBY, the internal resistor ranges from 660K to 4.4M according to the VIO voltage.
Sorry for the wrong information.
This post will be unmarked.
2026-04-29 8:23 AM - edited 2026-04-29 8:28 AM
Hello,
I've created a project running on two NUCLEO-C092RC boards. Two IDs have been used: 0x555 and 0x777. Refer to the #define at the beginning of the main.c.
Nominal phase bitrate: 500kb/s, (sample point set @87.5%) Data phase bitrate: 1Mb/s (sample point set @68.75%), 12 bytes are transmitted/received.
HSE: 48MHz as available on the board.
The blue LED is toggling while receiving a FDCAN frame over HAL_FDCAN_RxFifo1Callback() callback.
I've attached the project. I used IAR but you can generate the project for CubeIDE.
Hope that helps.
2026-04-29 9:26 AM
Thanks @mƎALLEm, very useful!
2026-04-30 5:42 AM
Ok, that was my problem with CAN-FD- I thought i would work. Now i am trying to build the network with nom. 1MBit/s and 4,8 MBit/s as data. This is not a private project. It is for a test setup. The idea is to take a look at, what happens, if we have a very high bitrate and long wires to hopefully see reflexions and communication error. That's why i set the bitrates very high. Since 5MBit/s is not really possible with 48 MHz, i will take 4,8 MHz.
Thank you very much for the support. So far the combination with 1MBit/s and 4,8MBit/s seems to work. I think it was because i set nom. speed way to high.
2026-04-30 5:42 AM
Thank your for the example