PEAK-System Forum

I have a PCAN-M.2 Single Channel (IPEH-004083) in an Intel NUC7i7DNBE that shows the following error in the journal:


Jun 2 15:06:54 NUC7 kernel: [165382.171662] pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
Jun 2 15:06:54 NUC7 kernel: [165382.171670] pcieport 0000:00 ...

So I think I found the root cause.


When configuring the PCAN-M.2 to 501 kbit, it would choose tq 400 instead of tq 12. There would be no problem in that case.
When changing SJW to 2 instead of the default 1, there seems to be no problem.
When measuring the bit timing using an oscilloscope, I ...

Today I tried using a PCAN-USB adapter (IPEH-002022) and it didn't show any error. What is the difference between PCAN-USB and PCAN-M.2?

Edit:
So I noticed that the bit timing that is used by PCAN-USB when configured to 500 kbit are the following:

bitrate 500000 sample-point 0.875
tq 125 prop ...

Hello,

The bus is properly terminated. As I mentioned in my message there is no problem when the PCAN-M.2 is connected with the 2 custom boards.

This morning I experimented a bit more with the setup, also having an additional RM9000 encoder available for testing. I found the following:

When ...

Hello,

I'm using a PCAN-M.2 interface on a Intel NUC7i7DNBE to communicate with a machine over a 500 kbit CAN bus. The CAN bus on this machine has 2 custom boards and 3 IFM RM9000 CANOpen encoders connected, so combined with the NUC there are 6 nodes on the bus. The bus is properly terminated at ...