The project I’m working on is about making a home automation system using an Android touch screen and some Arduino slaves that communicates using rs485 and modbus.
In the previous article, I wrote about how to create Arduino slaves that wait for modbus requests. It is now time to present how to write an Android project that acts as a master and communicate with slave devices.The nice thing of this design is that the logic that controls the smart home system is not constrained to be on the masters’ node. Instead, it can be distributed across all the Arduino devices. Indeed, since rs485 and modbus protocol were designed for industrial environments, this project could be easily used in industrial automation.
The project I’m working on is about making a home automation system using an Android touch screen and some Arduino slaves that communicates using rs485 and modbus.
In the previous article, I wrote about how to create Arduino slaves that wait for modbus requests. It is now time to present how to write an Android project that acts as a master and communicate with slave devices.The nice thing of this design is that the logic that controls the smart home system is not constrained to be on the masters’ node. Instead, it can be distributed across all the Arduino devices. Indeed, since rs485 and modbus protocol were designed for industrial environments, this project could be easily used in industrial automation.
In the previous article, I wrote about how to create Arduino slaves that wait for modbus requests. It is now time to present how to write an Android project that acts as a master and communicate with slave devices.The nice thing of this design is that the logic that controls the smart home system is not constrained to be on the masters’ node. Instead, it can be distributed across all the Arduino devices. Indeed, since rs485 and modbus protocol were designed for industrial environments, this project could be easily used in industrial automation.