Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| can_higher_layer_protocols:whatiswrongwithrtr [2012/08/07 15:42] – heinz | can_higher_layer_protocols:whatiswrongwithrtr [2026/08/14 14:21] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Why using RTRs is not advised in CANopen? ===== | ||
| - | |||
| - | |||
| - | 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 802 V1.1.0: CANopen application note - CAN remote frames: Avoiding of usage (IGCO_802v01010000.pdf) | ||
| - | |||
| - | |||
| - | \\ | ||
| - | It can be downloaded free of charge after a registration at [[http:// | ||
| - | \\ | ||
| - | \\ | ||
| - | In short the main topics: | ||
| - | |||
| - | |||
| - | * 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. | ||
| - | * Some CAN controllers react different on the 'data length' | ||
