List of things that need to be looked into, organized on topic.
- Measure current consumption
- Redesign power supply (work-in-progress)
- Silkscreen (needs to be more comprehensive)
- Update documentation
- When using immediate message format: the first received message will be send immediately, the second measurement will not be send and stored in the buffer, at the next interrupt from a module, the remaining buffer (from previous measurement) gets added to the new measurement.
measuring -> app data available -> send lora -> new measurement payload
This problem is not present when using data accumulation.
- Improve results concerning the air quality
- Hardware redesign (work-in-progress)
- There is a ripple visible in the acoustic measurements originating from the wake up and sleep functionality of the motherboard. A small fluctuation of the supply voltage causes a visible spike in the measurement. The fluctuation is already smaller by removing Diodes 4 and 5, but then there is no possibility to use multiple supply voltages. If the wake up and sleep of the motherboard is more coordinated to not occur during a sound measurement, the problem can also be solved without altering the hardware.
- Silkscreen (needs to be more comprehensive)
- Check naming of the repo's
- battery module
- luminosity sensor
- actuator board e.g., LEDs, buzzer, etc.
- todo's for the configurator tool
- Make it possible to program the motherboard for a second time without the need of restarting the tool
- check .exe release
- Add extra functionality concerning the battery module
- Disable polling for buttons
- Incorporate "enable/disable data accumulation"
- Support new message formats
- Add extra functionality concerning the battery module
- if more than x-time, no data is received in the databank, make the graph 0 for that time to make sure that when the measurements start again, no intersection line is drawn between the 2 points.