Timeline for Choosing wiring & protocol for MCU network
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2022 at 19:17 | comment | added | ambienthack | @DKNguyen, I haven't rejected RS-485, but bus arbitration does't sound easy to me. My instinct says there will be lots of implementation details. The solution is intended to work for years without oversight. There will be multiple copies with slightly different configurations. Bugfixing will be costly. That's why I'd like to stick with well supported standard solition. Maybe there is a well known arbitration protocol available (over RS-485)? | |
| Sep 15, 2022 at 7:06 | comment | added | Kartman | There’s wireless solutions that would probably be cheaper - esp32 for wifi and bluetooth. There’s also a point to point protocol that I’ve not used for these devices that might suit. Then you’re left with the issue of pairing/addressing which you’d have to resolve in most other of the solutions anyway. | |
| Sep 15, 2022 at 3:41 | comment | added | DKNguyen | You basically rejected RS-485 because it's not a unicorn. Is it really so troublesome to just wait until the bus is quiet for some amount of time before transmitting and making sure what you send on the bus is actually what is on the bus to detect a collision? And if so, just stop transmitting, have everyone wait some random amount of time and then being listening for a quiet bus again. | |
| Sep 15, 2022 at 2:14 | answer | added | hacktastical | timeline score: 2 | |
| Sep 15, 2022 at 1:03 | review | Close votes | |||
| Sep 30, 2022 at 3:09 | |||||
| S Sep 14, 2022 at 23:19 | review | First questions | |||
| Sep 15, 2022 at 4:35 | |||||
| S Sep 14, 2022 at 23:19 | history | asked | ambienthack | CC BY-SA 4.0 |