Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| can_higher_layer_protocols:what_is_wrong_with_rtr [2014/09/30 21:40] – heinz | can_higher_layer_protocols:what_is_wrong_with_rtr [2018/08/21 23:08] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| 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 802 V1.1.0: CANopen application note - CAN remote frames: Avoiding of usage (IGCO_802v01010000.pdf) | + | 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:// |
| - | CiA AN 802 V1.0: //CANopen statement on the use of RTR-messages// | + | |
| - | It can be downloaded free of charge after a registration at [[http:// | + | |
| - | \\ | + | |
| - | \\ | + | |
| In short the main topics: | In short the main topics: | ||
| - | * The number of transmit messages buffers supporting CAN remote frames is limited on most so-called [[can_faq_basic_full| | + | * The number of transmit messages buffers supporting CAN remote frames is limited on most so-called [[:can_faq_basic_full| |
| * 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' | ||
