RE: MilCAN processors

"Stremerch, Wim" <[email protected]>
Newsgroups gmane.comp.hardware.bus.can
Message-ID <[email protected]>
Hi John,

 

Error frames are allowed on the bus, but if a controller sees an error
frame it should not retransmit the message. 

We use a controller that supports TTCAN. In this mode it will not
retransmit the message when an error frame is received.

 

Best regards,

Wim Stremerch

 

From: [email protected]
[mailto:[email protected]] On Behalf Of John
Dammeyer
Sent: donderdag 20 december 2012 1:08
To: 'CANLIST'
Subject: [CANLIST] MilCAN processors

 

Hi Everyone,

 

One of the MilCAN specifications is that a node is not allowed to issue
an error frame to get a message retransmitted. As I understand it the
designers of MilCAN wanted to insure that the Sync Flag Message always
showed up at exactly the same time.  Since the number of replies in each
sync slot are restricted only a large burst of higher priority messages
could thwart the sync flag.  And an error burst that caused retries.

 

For example.  Imagine there is time for 20 messages between SYNC FLAGs.
The system designer has one SYNC FLAG where there are 18 replies leaving
room for two ASYNC messages.  Say 4 of the replies are corrupted by a
noise burst during the CRC.  The retries would now extend past the time
point for a new SYNC FLAG and potentially it would be shifted or
delayed.  Plus old data would show up in the next SYNC Slot.

 

The trouble is,  there are very few CAN devices out there that can have
the ERROR frame turned off.  Yes, the node can go to listen mode but
then all messages get through including ones with invalid CRCs.

 

Has anyone run into a processor family where this is possible?  Am I
misinterpreting the MilCAN spec?

 

Best Regards,

 

John Dammeyer

 

"ELS! The Solution"
Automation Artisans Inc.
http://www.autoartisans.com/ELS/
Ph. 1 250 544 4950

 



DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.