Re: SYNC messages in CANopen verses Sync Flags in MilCAN

"Koppe (MC)" <[email protected]> Sun, 18 Mar 2018 19:51:38 +0100
Newsgroups gmane.comp.hardware.bus.can
Message-ID <[email protected]>
Hello John,

> There isn't any data with a SYNC message in CANopen.


Since version 4.1 of the CANopen specification 301 there is an optional SYNC counter. The object 1019h allows
Access to the „Synchronous counter overflow value“. Here is a verbatim copy of the object description:

This object shall indicate the configured highest value the synchronous counter supports. This object shall be implemented by the producer and the consumer, if the synchronous counter is supported by the CANopen device. If the value is greater than 1, the SYNC message shall have a data length of 1 byte. The SYNC consumer shall ignore the value itself. An EMCY message (error code: 8240h – unexpected SYNC data length) may be transmitted by a SYNC consumer in the case the configured data length of the SYNC message does not meet the data length of a received SYNC message. 


Hence, if a CANopen device has passed the conformance test and supports object 1019h it will check for the DLC and you have a problem. 

And in addition: I do not enjoy a "custom CANopen protocol“ at all. Either it is CANopen, or
it is a custom protocol. I found already enough products on the market that have a hidden warning
label: „Attention - this product may contain CANopen“.



Greetings,
Uwe


---------------------------------------------------------------------
MicroControl GmbH & Co. KG
Junkersring 23, 53844 Troisdorf, Germany

Homepage: www.microcontrol.net <http://www.microcontrol.net/>
Facebook: www.facebook.com/MicroControl.net <http://www.facebook.com/MicroControl.net>
Twitter : http://twitter.com/_microcontrol_ <http://twitter.com/_microcontrol_>
---------------------------------------------------------------------