janhieber / waterctrl Goto Github PK

code and test motor control with current board

When soil is under direct sun with high temps, the sensor reports too low frequencies.

The frequencies indicate that the soil is wet, but that is not the case.

Further examination required.

should receive messages from RPi and act
when data is present.
should forward queued messages to RPi

Code and validate sensor measurement

Implement the SPI protocol (described in https://github.com/janhieber/WaterCtrl/blob/master/firmware/SPECS.md) in the ARM firmware.

When RPi does not send data for X seconds
we assume that it hangs, so restart the RPi

Using FreeRTOS would be a big improvement to the current self written "scheduler".
Pros:

• Message queues and signalling between processes/threads
• Much easier programming because every thread has its own endless loop, no need for static vars and counters...
• Much cleaner design of codebase
• Much easier to change or enhance functionallity

I think point 2 is the biggest one and absolutely worth the switch to FreeRTOS.
As soon as I have a bit free time i will move this project over to FreeRTOS, but that can be summer...

code with different log classes: INFO, ERROR, DEBUG

code function for routing log messages

• with desitnations: to UART, to SPI/RPI
• with log class filter
• enable error LED when ERROR class message occurs, think about clearing LED

WLAN access data (SSID, PSK) should be a config file on SD boot partition.
RPi should read the file on every boot and setup WLAN.

Convert the ARM firmware project for using Eclipse STM32 System Workbench

should send messages every X seconds and receive from STM.

should rung message parsing and routing on receive.

code with dumplex.
RPi is master and is sending messages every X seconds.
If no data, nothing is sent, but we need this to receive data from STM.

@dropedout @mbernloehr @mgeforce

As I have not much time to work on this project at the moment, it is up to you to implement the missing functionality. I'm sorry, but currently I have other tasks with higher prio at hand.

But... if I dont miss anything, we are only a bit from a running first version.

STM:

• Moisture measurement works
• PWM works
• Message broker works, but reiceived messages are not processed, see #7

RPI:

• Message broker works
• database connection works
• Web interface works
• watering logic is under development by @mbernloehr

So if we fix #7, we should be able to have a running device.