mrkevinweiss / riot-10-promo-board Goto Github PK

After some discussion it would be nice to agree how to manage the publicity of this board.

There were ideas about when to release it and how to do so. After some discussion here is what I propose...

We close the forum post saying that we have started the work and for further details people can ping me.
A few weeks before the RIOT summit we move this repo (possibly renaming it too) into the RIOT-OS org and announce on the forum/twitter that we have this available, this should give people enough time to prepare any hacking tools/apps needed.
We can also ask people if they are interested in getting one (maybe purchase or donation) and would allow us some time to prepare the correct amount of boards needed.

Let me know if there are some flaws with the plan!

If it's gonna be bolted down, then the board needs a generous electrically disconnected place for the bolt.

This will be used to track all the issues relating to the road map. It will be broken down into chunks and separated by the critical paths.
When each issue is resolved we can add it to the README or separate document in the repo.

Design

• #6
• #7
• Modules
• Responsibilities
• Tooling
• #9
• Overall design

Prototype Implementation

• Dev-board firmware
• PCB design
• Schematic design
• Enclosure design
• Server software mockup

First Run

• Board bringup and module confirmation tests
• Hardware tracking/commissioning
• Internal Distribution
• Start software hosting
• Mechanical assembly

Manufacturability

• QA tests
• Conformance tests
• Internal/self-declared EMC tests
• Higher volume order
• Cost reduction

Do any non-Canadians even know who Red Green is?
And why would it be bolted down in that case? Shouldn't duct tape be used?

I am reading other open issues and there seems to be some bewilderment with the circuit components and functionality, so I propose that we follow a series of common steps to reach a common goal. We can use milestones or projects for it

Nothing complex but well defined , for example:

1. What we want to achieve or what problem to address with this solution.
2. Main characteristics of the circuit (including costs)
   2.2. And each section
   2.3 Blocks drawing
3. Components selection, layers, surface finish, PCB size and/or shape, components on top or both faces, TG type, etc
4. Footprints design (if it's necessary)
5. PCB design
   5.1. Multi-person review
   5.2 Panelization
6. Order a few to test and review, and if all goes well, go to manufacturing.

important! the above is just an example, 🙏 manifest yourself @MrKevinWeiss and lead us or type the genesis step xD

Referenced issues:
#4 #3 #1

Any ideas yet how to "display a time-sensitive web-link"? E-Paper? LCD? LED matrix for QR?

This is where we can narrow down what the actual application will look like.

So far I have written my best guess in the readme. Let's hear everyone ideas early and we can sort out what is feasible to accomplish and what can be pushed to the next board/iteration.

Does the board need a SIM slot? eSIM functionality?
Is public LoraWAN actually ubiquitous enough at this point?
Are we giving these away at event? Or selling for low number of EU? Do they come with connectivity?

We are closing in on an idea and pretty soon we will need to select the components.
The big things to look at will be RIOT support, and availability.

Seeing as the team is ~10, as soon as we are happy with the initial selection I will order 25 of all high risk components (2 per person and 5 for safety).

I hope we don't need to break this into seperate threads (ie, one issue per major component).

We need:

• MCU (with or without LoRa?)
• battery charger/management
• power conditioning (5v, 3.3v, 1.8?)
• LCD/OLED/EInk/LED matrix?
• Access to console (USB or UART)
• Button (capacitive touch or protected push button)
• Tamper protection
• non-volatile storage (backup registers, eeprom, fram, internal/external flash?)
• RTC (internal or external)
• Debug access

We need to name the board... Ideally something easy to type, though I wouldn't mind something like cachie-mc-cacherson.

If anyone has some ideas please write them down.

Does it make sense to have the device field rechargable?

I don't know our power budget yet, but if it's really just using a teeny tiny LiPo, then there could be an "If you care, bring a power bank and donate 5 minutes" aspect to it. (By claiming the NFC code for that duration, you might listed in the hall of fame of People In Charge).