Timeline for RS-485 Modbus device to MCU
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2015 at 17:09 | comment | added | Spehro 'speff' Pefhany | Yes, you'll have to study the features of the CPU peripherals if you need to support that flavor of Modbus. | |
| Apr 28, 2015 at 16:58 | comment | added | Andrejs Gasilovs | Thank you. This is a type of pitfall that I haven't been aware of. As far as I understand there is no way to quickly estimate for a certain MCU if that is the case and can be found only deep in specification? | |
| Apr 28, 2015 at 14:43 | comment | added | Spehro 'speff' Pefhany | @KubaOber Exactly- which is why you have to consider it at an early stage- devote (most likely) an additional pin and some internal timer hardware. | |
| Apr 28, 2015 at 14:36 | comment | added | Kuba hasn't forgotten Monica | For MODBUS-RTU, one solution is to attach the RXD input to a timer input as well. That way you can detect the MARK condition using a timer. | |
| Apr 28, 2015 at 14:06 | history | edited | Spehro 'speff' Pefhany | CC BY-SA 3.0 |
deleted 1 character in body
|
| Apr 28, 2015 at 13:53 | history | answered | Spehro 'speff' Pefhany | CC BY-SA 3.0 |