Difference between revisions of "Projects:Badge"

From SHA2017
Jump to: navigation, search
(Software)
 
(36 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{TeamInfo
+
{{Project
 
|Lead=User:Bitlair.nl-kartoffel
 
|Lead=User:Bitlair.nl-kartoffel
 
|Does=Design an awesome badge
 
|Does=Design an awesome badge
|Exclusive team=No
 
 
|Contact=badge@lists.sha2017.org
 
|Contact=badge@lists.sha2017.org
 
|IRC=sha2017-badge
 
|IRC=sha2017-badge
|Vacancies=0
+
|Vacancies=3
 +
|Size=8
 
|Projectleiding=User:Damnlie
 
|Projectleiding=User:Damnlie
 +
|ManagedVacancy={{Jobs
 +
|JobTitle=Embedded hardware programmer
 +
|JobDescription=You can help us implement a MicroPython interpreter on the ESP32
 +
|JobNeededWhen=January 2017 to *.
 +
|JobExpectedCommitment=Your free time
 +
|JobSkillset=Embedded programming
 +
|JobVacancyAmount=1
 +
|JobTeamSubTeam=Badge
 +
|JobImage=Hackertyper.jpg
 +
|JobContactUserPrimary=User:Bitlair.nl-Kartoffel
 +
|JobContactUserSecondary=User:Anus
 +
}}
 
}}
 
}}
 +
 +
<div style="border: 1px solid black; background: black; width: 40em; align: left">
 +
<div style="border: 5px dashed yellow;">
 +
<div style="border: 1px solid black; background: #eee; padding: 1em; align: left">
 +
 +
'''Read https://wiki.sha2017.org/w/Projects:Badge for general and sponsorship information.'''
 +
 +
</div>
 +
</div>
 +
</div>
 +
  
 
== About ==
 
== About ==
 
We want to make an awesome badge.
 
We want to make an awesome badge.
  
We have an irc channel at #sha2017-badge on freenode and a mailing list at badge@lists.sha2017.org
+
We have an irc channel at #sha2017-badge and #sha2017-badge-dev on freenode and a mailing list at badge@lists.sha2017.org
  
 
Current team members:
 
Current team members:
  
* realitygaps
 
* the_Jinx
 
* Einstein
 
 
* Kartoffel
 
* Kartoffel
* puckipedia
+
* Sebastius
 +
* tsd
 +
* Sprite_TM
 
* Underhand
 
* Underhand
 +
* MarkusBec
 +
* Roosted
 +
* the_JinX
 +
* realitygaps
 +
* raboof
 +
 +
== ToDo ==
 +
* Order parts
 +
* Assemble badges (done by assembly house in China)
 +
* Designing and ordering flyers
 +
* Send infodesk content for booklet
 +
* Contact logistics with weight/volume to transport badges from The Hague to event
 +
* Bagging badges with displays, batteries, etc.
 +
* Build 10/20-fold flashing station for badges
  
Our current brainstorms and meeting notes are at https://pad.ijhack.nl/p/shabadge.
+
== In progress ==
Technical specs (subject to change): https://pad.sha2017.org/p/badge-technical.
+
* Finish factory FW
 +
* Assembling 5 more rev1.0.0 boards for development
 +
* Arranging assembly
 +
* Sourcing lanyards / bags / sticky pads / ...
 +
* µGFX support for the display
 +
* Micropython hooks for hardware drivers & µGFX
  
We will continue having meetings online on the irc channel once every couple of weeks for the moment.
+
== Done ==
 +
* Three prototype runs
 +
* Finish BOM
 +
* Order batteries
 +
* Order displays
 +
* Sourcing parts
 +
* Hardware drivers in C
  
== Badge functions ==
+
== Planning ==
The idea is that everyone gets a badge that is primarily useful during the event, and also fun and easy to tinker with. Every badge will connect to legacy WiFi (so it's smart to bring a laptop that can do 5GHz). The badge will be able to display information like a talk schedule, fahrplan, angel shifts.  
+
=== May / June ===
 +
* May 27-28: Hekketon @ revspace
 +
 
 +
=== June ===
 +
* June 3/4: Factory firmware done (basic downloading, small eink status message 'updating')
 +
 
 +
=== Mid-June ===
 +
* ESP modules and last parts arrive at assembler
 +
* Start assembly
 +
 
 +
=== Mid to end of June ===
 +
* Finish assembly
 +
 
 +
=== July ===
 +
* Receive badges
 +
* Bagging badges
 +
* July 8/9: Switch to emergency mode (everything in C)
 +
* July 29/30: Move hardware to SHA Storage
 +
 
 +
=== August ===
 +
* August 4: Handing out badges to visitors
 +
* August 8: End of event
 +
 
 +
== Badge ==
 +
The badge should first and foremost function as a badge.
 +
A digital name tag that functions in direct sunlight at an outdoor summer event as well as at night in a barely lit tent.
 +
 
 +
The idea is that everyone gets a badge that is primarily useful during the event, and also fun and easy to tinker with. The badge will be able to display information like a talk schedule, fahrplan, angel shifts.  
  
 
In list form:
 
In list form:
 
* Provide information during the event
 
* Provide information during the event
 
* Talk schedule + fahrplan
 
* Talk schedule + fahrplan
* Angel shift information (optionally 2-way with REST API over WiFi)
+
* Angel shift information
 
* Information on places (tracks, villages) you're near
 
* Information on places (tracks, villages) you're near
Bonus stuff (not a priority, but a 'would be nice'):
+
* Live subtitles/translations of talks!
* Control LEDs or devices in villages you're near
 
  
 
== Vacancies ==
 
== Vacancies ==
None at the moment.
+
* Embedded hardware programmer to help us:
 +
** Write hardware drivers for the e-paper / touch / peripherals in C
 +
** Link these libraries to MicroPython
  
 
== Hardware ==
 
== Hardware ==
The badge will be a creditcard-ish sized PCB with on it:
+
The badge will have:
* A ~2" e-paper display
+
* ESP32 WROOM module
* An ESP WiFi module
+
* DEPG0290B01 2.9" e-paper display (296x128)
* At least up/down/left/right/select buttons for input
+
* MPR121 I2C Capacitive touch + GPIO controller
* A decent-sized battery to last at least a day
+
* CP2102 USB UART [https://www.silabs.com/documents/public/data-sheets/CP2102-9.pdf datasheet]
* Power regulator
+
* TP4056 Battery charger
* A USB->TTL chip for programming
+
** Up/Down/Left/Right/Select/Start/A/B capacitive touch buttons for input
* ('would be nice') Proper badge clip instead of a lanyard
+
* A 1000mAh battery to last at least a day
* ('would be nice') a pager motor for notifications
+
* A pager motor for notifications
 +
 
 +
===Software===
 +
 
 +
* Two flavours of Firmware: https://github.com/SHA2017-badge/Firmware
 +
* Sprite's BPP: https://github.com/SHA2017-badge/bpp
  
At the moment we're trying to keep the budget for the badge below €15, which is still quite a lot of money. Sponsoring might help reduce this amount.
+
===Current issues===
  
== Roadmap ==
+
Time . . and money
* Proof of concept by september
 
* PCB prototype ordered by 13 september
 
* (more prototype runs)
 
* February 2017: Start mass production (design / parts finalized before this time)
 

Latest revision as of 23:35, 2 June 2017

Badge
1st line contacts: Kartoffel
Does: Design an awesome badge
Does not:
Contact: badge@lists.sha2017.org
IRC: #sha2017-badge
Deadlines:
Needed resources:
Comment:
Vacancies: 3
Current project size / amount of ppl: 8
Contact at projectleiding: User:Damnlie


Read https://wiki.sha2017.org/w/Projects:Badge for general and sponsorship information.


About

We want to make an awesome badge.

We have an irc channel at #sha2017-badge and #sha2017-badge-dev on freenode and a mailing list at badge@lists.sha2017.org

Current team members:

  • Kartoffel
  • Sebastius
  • tsd
  • Sprite_TM
  • Underhand
  • MarkusBec
  • Roosted
  • the_JinX
  • realitygaps
  • raboof

ToDo

  • Order parts
  • Assemble badges (done by assembly house in China)
  • Designing and ordering flyers
  • Send infodesk content for booklet
  • Contact logistics with weight/volume to transport badges from The Hague to event
  • Bagging badges with displays, batteries, etc.
  • Build 10/20-fold flashing station for badges

In progress

  • Finish factory FW
  • Assembling 5 more rev1.0.0 boards for development
  • Arranging assembly
  • Sourcing lanyards / bags / sticky pads / ...
  • µGFX support for the display
  • Micropython hooks for hardware drivers & µGFX

Done

  • Three prototype runs
  • Finish BOM
  • Order batteries
  • Order displays
  • Sourcing parts
  • Hardware drivers in C

Planning

May / June

  • May 27-28: Hekketon @ revspace

June

  • June 3/4: Factory firmware done (basic downloading, small eink status message 'updating')

Mid-June

  • ESP modules and last parts arrive at assembler
  • Start assembly

Mid to end of June

  • Finish assembly

July

  • Receive badges
  • Bagging badges
  • July 8/9: Switch to emergency mode (everything in C)
  • July 29/30: Move hardware to SHA Storage

August

  • August 4: Handing out badges to visitors
  • August 8: End of event

Badge

The badge should first and foremost function as a badge. A digital name tag that functions in direct sunlight at an outdoor summer event as well as at night in a barely lit tent.

The idea is that everyone gets a badge that is primarily useful during the event, and also fun and easy to tinker with. The badge will be able to display information like a talk schedule, fahrplan, angel shifts.

In list form:

  • Provide information during the event
  • Talk schedule + fahrplan
  • Angel shift information
  • Information on places (tracks, villages) you're near
  • Live subtitles/translations of talks!

Vacancies

  • Embedded hardware programmer to help us:
    • Write hardware drivers for the e-paper / touch / peripherals in C
    • Link these libraries to MicroPython

Hardware

The badge will have:

  • ESP32 WROOM module
  • DEPG0290B01 2.9" e-paper display (296x128)
  • MPR121 I2C Capacitive touch + GPIO controller
  • CP2102 USB UART datasheet
  • TP4056 Battery charger
    • Up/Down/Left/Right/Select/Start/A/B capacitive touch buttons for input
  • A 1000mAh battery to last at least a day
  • A pager motor for notifications

Software

Current issues

Time . . and money