Re: CAN device driver statistics

Am Dienstag, 2. Dezember 2014, 14:03:33 schrieb Bram Kerkhof:
> Personally, I would consider that to be an indispensable  requirement.
> Proper bus health monitoring should be an integral part of the design of any
> CAN-based network, especially because the application domain for CAN is more
> often than not in operating and controlling potentially dangerous
> machines/vehicles. 
> 
> Bus statistics and error counters are a part of that, so they should be
> easily and universally available.

That bus health monitoring is essential in nearly all kind of CAN communication systems,
the question was, what should the driver deliver, what can be collected at application level.

- Bus error counters must be read out and provided  by the driver
- the same for the CAN node status
- Bus load can be calculated by the application, but only if no acceptance filter is active 
- data transfer volume (in byte, KiB ...) can be calculated by the application
   - here again, which role plays the acceptance filter
	is only the data volume related to the application important (if at all)
	or the overall data volume on the bus

What do you expect from the driver? What should better be done in the application?

And, thanks so far for the discussion.


-- 
mit freundlichen Grüßen

	Heinz-Jürgen Oertel
	emtas GmbH 

> 
> Cheers,
> Bram
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Heinz-Jürgen Oertel
> Sent: dinsdag 2 december 2014 12:21
> To: CANLIST
> Subject: [CANLIST] CAN device driver statistics
> 
> Hello,
> 
> asking for your opinion,
> does it make sense that a low level CAN device driver (like can4linux)
> provides statistical information like the number of bytes transmitted and
> received?
> Another example are error counter values or average bus load. What do you
> think? 
>  
> 

--
Archives and useful links: http://groups.yahoo.com/group/CANbus
Subscribe and unsubscribe at www.vector.com/canlist/
Report any problems to <[email protected]>