Differences
This shows you the differences between two versions of the page.
| Last revisionBoth sides next revision | |||
| can_higher_layer_protocols:whatiswrongwithrtr [2012/08/07 15:37] – created heinz | can_higher_layer_protocols:whatiswrongwithrtr [2012/08/07 15:42] – heinz | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| CiA, especially the Special Interest Group CANopen is not recommending using RTR Messages. You may ask: why? | CiA, especially the Special Interest Group CANopen is not recommending using RTR Messages. You may ask: why? | ||
| \\ | \\ | ||
| - | The CiA has a paper explaining the contras and giving advice for better solutions. CiA AN 802 V1.0: ''' | + | The CiA has a paper explaining the contras and giving advice for better solutions. CiA 802 V1.1.0: CANopen |
| + | |||
| \\ | \\ | ||
| - | It can be downloaded free of charge after a registration at http:// | + | It can be downloaded free of charge after a registration at [[http:// |
| \\ | \\ | ||
| \\ | \\ | ||
| Line 14: | Line 16: | ||
| * The number of transmit messages buffers supporting CAN remote frames is limited on most so-called FullCAN controllers. | * The number of transmit messages buffers supporting CAN remote frames is limited on most so-called FullCAN controllers. | ||
| * Implementation of a CAN driver handling RTR is much more complex. On some controllers impossible. | * Implementation of a CAN driver handling RTR is much more complex. On some controllers impossible. | ||
| - | * Some CAN controllers react different on the 'data length' | + | * Some CAN controllers react different on the 'data length' |
