PEAK-System Forum

Hello,

I have the device working under netdev now, I was not defining the sample-point which was causing the problem. Entirely my fault. The following works for netdev:


fb@xxx:~$ sudo ip link set can0 type can bitrate 500000 sample-point 0.800 dbitrate 2000000 dsample-point 0.800 fd on
fb@xxx ...

I have plugged the device into itself CAN1->CAN2 and I can send and receive CAN-FD frames so there is nothing wrong with the driver. There must be some other odd reason why the device I am communicating with seems to work OK under windows but not Linux.

I would like to try getting the device ...

Sorry I posted in between you giving me the answer. So specifying the clock-rate in Hz works but I still cannot communicate with my device (goes into bus_passive with flashing red LED). Hmm.


fb@xxx:~/Downloads/peak-linux-driver-8.6.0/Documentation$ sudo pcanfdtst rx --fd -b 500k -d 2M -c 24000000 ...

I should have looked at dmesg as error 33 is a bitrate error, it does not seem to like the nominal bitrate of 500k:


fb@xxx:~/Downloads/peak-linux-driver-8.6.0/Documentation$ dmesg | tail
[10680.203878] pcan: clk=24 btr=500000 sp=0 [BRP=0 TSEGx=0/0 SJW=0]
[10697.339966] pcan: bitrate error 971.8 ...

Hello,

Now when trying to use the -d parameter the device fails to open with error -33:


fb@xxx:~/Downloads/peak-linux-driver-8.6.0/Documentation$ sudo pcanfdtst rx --fd -b 500k -d 2M -c 60 /dev/pcanusbfd32
failed to open "/dev/pcanusbfd32" (err -33)

No pcan device is opened. Exiting ...

In short I cannot receive FD frames under Linux using the latest driver when compiled for either chardev or netdev. Note under windows the PCAN-VIEW application works fine. The device to which I am connected has a 500k nominal speed with a 2M data rate for FD frames. I am able to receive frames in ...