Fwd: Loosing CAN messages with socket-CAN

Fwd: Loosing CAN messages with socket-CAN

[Marc Kleine-Budde]

[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]

Hello Jeroen,

please use the linux-can Mailinglist, but don't post HTML mails there.

Marc

-------- Original Message --------
Subject: Loosing CAN messages with socket-CAN
Date: Wed, 3 Apr 2013 12:17:31 +0200
From: Jeroen Lammertink <jeroen.lammertink@nl.abb.com>
To: bet-frogger@users.berlios.de

Marc Kleine-Budde,

I hope you can put me in the right direction for the following problem: We
seem to loose CAN messages.

We are sending batches of 80 CAN messages using socket CAN to transfer an
image for download. After the 80 messages we wait for a response
consisting of a single CAN message. Within the messages we have coded a
sequence number, so that we can detect lost messages. Besides the CAN
device that is subject of download, we have also a (hardware) CAN sniffer
on the CAN bus. We typically log CAN messages when we put them in the
socket. With this set-up we typically detect loosing a short series of
(mostly 5) CAN messages, somewhere halfway the batch of 80. No other
devices are present on the CAN bus.

I've dumped below some version and set-up info of Ubuntu, socket-can and
ifconfig.

Is this problem known?
May this problem be related to using an old version of socket can?
How can I upgrade Ubuntu to the latest versions of socket-can?

Thanks in advance,

Jeroen Lammertink


bmterra@q7buntu:~/user/jla$ uname -a
Linux q7buntu 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar 11 22:19:42
UTC 2013 i686 i686 i386 GNU/Linux
bmterra@q7buntu:~/user/jla$ cat /proc/net/can/version
rev 20090105 abi 8
bmterra@q7buntu:~/user/jla$ ifconfig can0
can0      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:1128 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4400 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1024
          RX bytes:9024 (9.0 KB)  TX bytes:34176 (34.1 KB)
          Interrupt:18


-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: Fwd: Loosing CAN messages with socket-CAN

[Marc Kleine-Budde]

[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]

On 04/03/2013 12:37 PM, Marc Kleine-Budde wrote:
> We are sending batches of 80 CAN messages using socket CAN to transfer an
> image for download. After the 80 messages we wait for a response

Are you evaluating the return value of the write() or sendmsg() systemcall?

> consisting of a single CAN message. Within the messages we have coded a
> sequence number, so that we can detect lost messages. Besides the CAN
> device that is subject of download, we have also a (hardware) CAN sniffer
> on the CAN bus. We typically log CAN messages when we put them in the
> socket. With this set-up we typically detect loosing a short series of
> (mostly 5) CAN messages, somewhere halfway the batch of 80. No other
> devices are present on the CAN bus.
> 
> I've dumped below some version and set-up info of Ubuntu, socket-can and
> ifconfig.
> 
> Is this problem known?
> May this problem be related to using an old version of socket can?

This is either a userspace problem or a buggy driver. The driver problem
may have been fixed in the meantime.

> How can I upgrade Ubuntu to the latest versions of socket-can?

First we have to figure out what's brokoen.

> Thanks in advance,
> 
> Jeroen Lammertink
> 
> 
> bmterra@q7buntu:~/user/jla$ uname -a
> Linux q7buntu 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar 11 22:19:42
> UTC 2013 i686 i686 i386 GNU/Linux
> bmterra@q7buntu:~/user/jla$ cat /proc/net/can/version
> rev 20090105 abi 8
> bmterra@q7buntu:~/user/jla$ ifconfig can0
> can0      Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           UP RUNNING NOARP  MTU:16  Metric:1
>           RX packets:1128 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4400 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1024
>           RX bytes:9024 (9.0 KB)  TX bytes:34176 (34.1 KB)
>           Interrupt:18

Which CAN hardware are you using?

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]