Re: CANopen and the need for time-stamping

Hello Jana

You only need built-in timers if the timestamp must be super accurate. This
I think is mostly important for bus analysis tools and is not needed for
CANopen.

Timestamping the message using an MCU timer in the receive interrupt should
be enough for most applications.

Simon

Simon Byholm - Software Manager / Quality Manager

Phone: +358 6 357 6306
Fax: +358 6 357 6320
email: [email protected]
web: www.tke.fi

TK Engineering solves your CAN, CANopen, J1939 and NMEA2000 problems by providing the hardware, software and know-how you need to design, manufacture and troubleshoot your industrial and heavy machine CAN networks. Call +358 6 357 6300 or email [email protected] to learn how we can help you solve your CAN related problems.

On 23.10.2014 16:30, Janakiraman, Hareesh wrote:
>
> Hello,
>
> Some CAN implementations have a built-in timer for time-stamping of 
> messages. These timers also provide a time-out interrupt should 
> transmission or reception of a mailbox does not occur in a 
> pre-determined time. The eCAN module of in the 28xx MCUs from TI is an 
> example. My question is this: Is the presence of a _built-in_ timer 
> absolutely essential for CANopen implementation? (/Note that I am not 
> referring to timers that are external to the CAN module, since all 
> MCUs have one or more of “general-purpose” timers/). I believe the 
> answer is “no”, since I see in the websites of many 3^rd parties who 
> develop CANopen stacks a list of processors and I know not all of them 
> have a built-in timer/counter as part of the CAN IP.
>
> /Hareesh Jana/
>