Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ACU-AMNx board and MVP checklist #9143

Closed
7 of 24 tasks
ZetaR60 opened this issue May 16, 2018 · 3 comments
Closed
7 of 24 tasks

ACU-AMNx board and MVP checklist #9143

ZetaR60 opened this issue May 16, 2018 · 3 comments
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

Comments

@ZetaR60
Copy link
Contributor

ZetaR60 commented May 16, 2018

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:

  • Generic API for running shell commands
  • Shell command to batch other commands
  • cron-like shell command to schedule other commands
  • Remote shell access over the network

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

@aabadie
Copy link
Contributor

aabadie commented May 16, 2018

Very nice project @ZetaR60 !

Regarding 'for EEPROM API and support on ATmega', you might be interested by #8862.

@ZetaR60
Copy link
Contributor Author

ZetaR60 commented May 16, 2018

@aabadie What? EEPROM API with ATmega support and CLI test cases? All that's missing now is wrapping it in a ribbon with a little bow. Added a note on the list. Thank you very much!

I intend for the batch and cron to store info in EEPROM. Very important for a special batch that runs after booting, so that you can configure the network and stuff on the CLI (or remote access) and then have it save the configuration.

@kaspar030 kaspar030 added Type: new feature The issue requests / The PR implemements a new feature for RIOT Area: boards Area: Board ports labels May 17, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this as completed Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

3 participants