The backend of the Water System project, for a more user oriented (features) review check the front-end Water-System GUI.
Clone from git with the submodules with that command -
git clone --recursive https://github.com/ism-hub/WaterSystemBackend.git
Open using vscode with Platformio installed, and that's it you now can compile, upload, run and edit the code.
We have the ESP8266 as the main controller, connected to it we have nodes with the sensors and the valve, the nodes sit on top of the plant.
This version is using SPI as the communication scheme and only has the valves in the nodes. The ESP8266 is connected, via SPI interface, to a SPI chip (a bigger one with more CS pins, named MySPI). The MySPI chip is connected to a Switches Board (you can turn switches on and off via SPI). In turn, the Switches Board connected to the valves and pumps (via transistors) and you can turn them on and off.
Gives us a bigger SPI board to work with (more CS pins), based on the 74HC595 shift-register (storage + parallel out shift register) and few NAND gates to make it interface with the SPI.
Can turn switches on and off via an SPI interface, based on the same idea as the MySPI chip
We connect the transistors to the pump, valves and switches in the Switches Board. I had a PSpice simulation with the values of the resistors and the transistor I've used, I switched computers and need to find and install it again, so soon.
The project will move to use the RS485 specifications for communication with the Modbus protocol on an Attiny85 as the nodes (the main MCU will stay the ESP8266).
The main idea is that our model fire events before it changes and after the it changes (the before it changes event can fail, if so, the after it changes event won't fire), services/controllers register themselves to the events to add functionality. For example, on 'pump on' event the hardware controller will turn on the pump. The functionality is packaged inside modules.
The project is composed from a set of modules, each module adds a different feature/functionality. For a better understanding on how the modules work and how to use them checkout the Module Framework I'm using.
Adds the HTTP server capabilities (can get and send HTTP messages), and adds the HTTP Framework so the user can write controllers and handle the requests.
Connects between the domain model and the hardware (adds controllers to listen to events on model changes and turn on/off/reads the hardware).
Adds the Repository Design Pattern and json serialization service.
Adds the AP-service (can control the AP via it e.g. turn it on/off change the password etc..) and the REST API for the service (the controller for the framework) see Water-System GUI to see a graphical interface for the REST API.
The same as the AP-Module only the ESP8266 acts like a station.
Adds a service that can run a function/task at fixed intervals or at some time.
Not really a framework, for now just holding the services we that we want to stay on for the duration of the program (even if no-one is referencing them), can stop/restart/start services that registered to the framework (supposed to remind you the 'systemctl' from Linux).
Work in progress, a service that shows you the time, you can set the time, get the time from a NTP server etc... Has an REST API for the user to control.