Timeline for Strange behavior of auto retransmission on STM32 CAN bus
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2021 at 1:20 | vote | accept | Maple | ||
| Nov 19, 2021 at 1:19 | comment | added | Maple | See an update in OP. Your very first guess was spot-on. We did have messages with same arbitration field but different data. | |
| Nov 19, 2021 at 0:44 | comment | added | Maple | Tried with third silent node and throughput dropped even more. So, this is not an ACK. | |
| Nov 17, 2021 at 9:02 | comment | added | Maple | You've given me compelling idea. If two nodes happen to generate exactly same message and attempt to send them at exactly the same time then there would be nobody to ACK. Hmm... I'll try to add one silent node to the test just to do the ACK-ing. | |
| Nov 17, 2021 at 8:18 | comment | added | Maple | Yes, it is possible for two nodes to generate same ID with different data or even with absolutely identical messages. I estimate the chances of that are minuscule, but I might be wrong. The reason to flip high bits is exactly as you've guessed, to have symmetrical data flow for the test. In real application we have approximately even data volume in all directions. | |
| S Nov 17, 2021 at 6:16 | review | First answers | |||
| Nov 17, 2021 at 9:24 | |||||
| S Nov 17, 2021 at 6:16 | history | answered | Flexz | CC BY-SA 4.0 |