From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Grandegger Subject: Re: [SocketCan] Problem of accuracy Date: Mon, 09 Jul 2012 11:22:31 +0200 Message-ID: <4FFAA2D7.4010905@grandegger.com> References: <4FF55274.3030006@volkswagen.de> <4FF8102C.8030609@grandegger.com> <4FF9E9E4.4090602@grandegger.com> <4FFA85B3.5080800@grandegger.com> <4FFA9466.3040600@grandegger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from ngcobalt02.manitu.net ([217.11.48.102]:39567 "EHLO ngcobalt02.manitu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752414Ab2GIJWe (ORCPT ); Mon, 9 Jul 2012 05:22:34 -0400 In-Reply-To: Sender: linux-can-owner@vger.kernel.org List-ID: To: Mohamed HAMZAOUI Cc: linux-can Mailing List On 07/09/2012 11:19 AM, Mohamed HAMZAOUI wrote: > My real-time requirement is minimum to be accurate on 1ms for manage > deterministic CAN protocol (like MILCAN). Well, what jitter would be acceptable for a period of 1ms? BTW: what happens if you use a period of 0.7 ms. Do you then see a period of 1ms on the bus? Wolfgang.