PCAN USB Pro doesn't work with 3.4MBPS CAN FD settings

[rajeshmchavan]

Hello,
We are having PCAN devices for our testing and development.
Recently we switched to CANFD protocol for one of our products and PCAN USB pro seems to be not working in reception mode for certain baud rates.

Here are our CAN FD baud settings -
nominal bit rate 1MBPS data bit rate 3.4MBPS. Our devices keep sending data over CAN bus but PCAN USB doesn't acknowledge it and our controller increments transmit error counter and ultimately stops sending.

However, our devices work perfectly fine when connected to Vector CANoe or Intrepid NeoVi.

although PCAN works fine for nominal bit rate 1MBPS and fast data rate of 2MBPS.

Are we missing something here or PCAN doesn't support this baud rate.
PCAN Firmware Version is 3.2.0
Driver version is 4.1.4

[M.Heidemann]

Hello,

I assume you mean a PCAN-USB Pro FD by "PCAN USB Pro", please correct me if i am wrong.

Which software do you use with your PCAN-USB Pro FD?

Have used the exact same bitrate setting (Besides the bitrate itself: BRP, TESG1, TSEG2, SJW) as with your other devices ?

is your termination correct?

Is your PCAN-Interface possibly running in "Listen-only"-mode?

Please report back to us regarding this.

Best Regards

Marvin

[rajeshmchavan]

Hello,
Thanks for getting back to me.
Yes you are right - PCAN-USB Pro FD by "PCAN USB Pro".
We are using the same bit rate settings with other devices as well.
We have the correct termination of 120 ohm.
We are using PCAN View Software for our tests.<Imagage Attached>
And we are not in Listen only mode either.<Image attached>

[M.Heidemann]

Hello,

Which data is shown when a trace is recorded?

Please make sure to enable the logging of error-frames:

PCAN-View_Trace_Error_settings.PNG (7.56 KiB) Viewed 5903 times

And share you results with us.

Best Regards

Marvin

[rajeshmchavan]

Hello,
Please find attached the screenshot.
We have connected our board to PCAN hardware. So just two nodes.
There is an acknowledgment error from the PCAN side for the messages being sent by our device.
And as there is no ACK, CAN controller of our device increment transmit error count and eventually goes to bus off condition.
Note: Sometimes PCAN is able to detect messages as well as seen in the attached image.

Thanks.

[rajeshmchavan]

I'm not completely sure but the problem could be with the unavailability of 16 Mhz or 32Mhz crystal on the PCAN hardware.
I think with 24Mhz crystal we might not be able to create proper timing values for the exact 3.2MBPS data rate. There would be some deviation from PCAN side.
Please confirm if my assumption is correct or if there is any possible solution.

[M.Heidemann]

Hello,

Please use the PCAN-Bitrate Calcualation Tool to determine the proper Bitrate-Configuration
using a different clock-frequency, the values for BRP, TSEG1, TSEG2, SJW will be different
depending on the clock-frequency.

https://www.peak-system.com/fileadmin/m ... onTool.zip

Please make sure, that you use the same sample-point for your Bitrate-Calculation.

Please report back to us, if you were able to resolve the issue this way.

Best Regards

Marvin

[rajeshmchavan]

Thanks for the tool.
However unfortunately i didn't have any success even after changing all the possible values provided by the tool.
Any help would be appreciated.

[M.Heidemann]

Hello,

could you send us the exact bitrate-configuration of your other devices?

Best Regards

Marvin

[rajeshmchavan]

Hello Marvin,
First of all sorry that I put 3.4Mbps(instead of 3.2Mbps) in the problem statement I just realized my typo here.
We are struggling with 3.2mbps baud rate settings with PCAN.
Here are the settings of our device-

Nominal Bit Rate = 1Mbps
Data Bit rate = 3.2Mbps
CAN module clock source = 16MHz
Arbitration phase sampling point = 75%
Arbitration phase bit time = 1us(8Tq, 1Tq =125ns)
Data pahse sampling point = 60%
Data pahse bit time = 0.3125us(5Tq, 1Tq =62.5ns)

.nominalBitrate =
{
.preDivider = 0,
.rJumpwidth = 3,
.propSeg = 6,
.phaseSeg1 = 3,
.phaseSeg2 = 3,
}
.dataBitrate =
{
.preDivider = 0,
.rJumpwidth = 0,
.propSeg = 1,
.phaseSeg1 = 0,
.phaseSeg2 = 1,
}