ACU-AMNx board and MVP checklist #9143
Labels
Area: boards
Area: Board ports
State: stale
State: The issue / PR has no activity for >185 days
Type: new feature
The issue requests / The PR implemements a new feature for RIOT
Summary:
This issue is to show progress towards support in RIOT for a new board by Acutam Automation (my company), as well as a checklist of items required to reach a minimum viable product (MVP). I also welcome any feedback anyone wishes to share here.
Description:
The ACU-AMNx (Acutam Autonomous Mesh Node) is a field deployable IoT unit for agricultural and industrial automation. The primary target market at the moment is for Florida citrus growers, since I have some connections in that market. The goal is to be able to use a solar powered 6LoWPAN mesh network over an area of up to a few hundred acres (~a sq km) to take measurements and automate the valves and pumps. Internet uplink is currently planned to be a Linux board connected to the network that serves as a router for cell network connection.
The design strategy is have a modular system that is very flexible, and can be adapted to new uses easily. Inside the ACU-AMNx unit will be a main board providing six generic daughterboard attachment points ("slots", though they will be soldered). So, for example, solar can be swapped to primary cells or to an isolated DC-DC converter by assembling the unit with a different daughterboard. I plan to pot the whole assembly and use long lifespan components, so it will hopefully last for >10 years in the field (giving a low total cost of ownership).
An IP67 rated external port is planned to allow peripherals to be connected to provide specific sensor or actuator support. For the MVP a dielectric soil moisture sensor will be the first peripheral.
Checklist:
Bugfixes:
CPU and low-level:
Basic drivers:
External port and card drivers:
Remote management and automation support:
Schematic:
I have decided to open-source the schematic, at least for the main board. I am uncertain about opening other parts due to my inexperience with the risks of open-source in the target market. In the case of the main board, I think that increased collaboration with RIOT and the IoT community is worth the risks.
autonomous-mesh-node-0.7.0_schematic.pdf
The text was updated successfully, but these errors were encountered: