Timeline for Issue with Rostopic Name Length Affecting Node Communication
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2023 at 16:52 | comment | added | jubago | The way I solved this problem was by determining which lengths of names for topics and nodes would not cause issues. Once I determined the ideal length for nodes and topics (in my case, 20 characters), I created the names as follows: each topic and node is assigned a unique name shorter than 16 chars, which allows me to identify it (e.g., "simulator_node"). If a name already has 16 chars, I simply append 4 randomly generated characters for each simulation. Otherwise, I add "_" chars until the name reaches 16 characters, and then I append the same 4 randomly generated characters as before. | |
| Oct 3, 2023 at 16:52 | vote | accept | jubago | ||
| Sep 27, 2023 at 19:30 | history | answered | Mike973 | CC BY-SA 4.0 |