PEAK-System Forum

Hi,

thanks for your reply.

I'm using the 8.6.0 source driver in netdev mode and with socketCAN interface. Hope that is correct now

Adding "deftsmode=0" to pcan.conf file fixed the software timestamps for me. I've stopped reading docs at "install package" .

regards

Hi,

I'm using the USB adapters to debug an embedded application on my desktop PC, as this simplifies development quite a bit. The SOC CAN module uses socketCAN, so I can't switch driver.

The SOC can driver (flexcan) produces valid software timestamps, however it doesn't implement hardware ...

Thanks, the canutils repo moved home again...

I've played with TIMESTAMPING mode a bit, but I still can't get it to work properly. When I use this like in candump.c, I expect to get software timstamp in stamp[0] and hardware timestamp in stamp[2]. However, there is no difference between those two ...

Thanks for your reply!

Can you please give some more details? I've replaced SO_TIMESTAMP option with SO_TIMESTAMPING in candump.c, however now timestamping stopped working completely. I also don't have a variable stamp[0], neither in cmsg struct nor anywhere in candump.c.

Is this problem specific ...

Hi@all,

I'm having a problem with getting kernel/driver generated timestamps on PCAN USB Interface / socketCAN driver. After some time, the kernel timestamps of received messages are in the future compared to locally generated timestamps:

clock_gettime: (2018-10-16 13:28:50.365177) kernel ...

Please Unplug and PlugIn the CAN-USB and check if this Problem is still there.
this fixes the problem.

How could you be sure that these CAN Frames are not on the BUS? '
I've connected a third device in listen only mode to the bus (freescale I-MX28 device running embedded linux).

Same setup as ...

no problem. It's getting really strange now :shock:

In this log are two messages per second on the bus (that is correct). The ID 704 message is transmitted by a socket application and the 705 by a bus device.

output of candump -t A can0

-- everything is fine here --
(2016-12-19 14:08:07.531693 ...

Hi,

I don't have status/error messages enabled for the socket. The messages I'm getting are regular messages that have passed the driver at some point. However, they are not on the physical bus at that moment of time.

Maybe a few comments inside the screenshots will clarify my problem

canopen3 ...

This also happens when my slave device disables the CAN hardware.
In my case, this is the case when the master requests the slave to enter bootloader mode.

Hi @all,

I'm having some problems using the socketcan interface that comes with the pcan driver.
My set up is the following:
- Linux PC with pcan interface, master software working on one socket, Wireshark/candump sniffing on another socket.
- Microcontroller with integrated can interface, working ...