People Counter: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
Lxpk (talk | contribs)
No edit summary
CRImier (talk | contribs)
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:


{{headerbox}}'''PROPOSAL:''' People Counter would track how many people are in the space for occupancy safety monitoring.
{{headerbox}}'''PROPOSAL:''' People Counter would track how many people are in the space for occupancy safety monitoring.
*'''DOERS:''' [[User:Culteejen]], CRImier#2925
*'''DOERS:''' [[User:Culteejen]], [[User:CRImier]]
{{boxend}}
{{boxend}}


Line 13: Line 13:
*[https://cdn.discordapp.com/attachments/720514857094348843/928871222073245776/unknown.png screenshot prototype]
*[https://cdn.discordapp.com/attachments/720514857094348843/928871222073245776/unknown.png screenshot prototype]


==CRimier Proposal==
==CRImier Proposal==
It's an entry panel kiosk, with a quick (and, hopefully, intuitive) workflow to answer "entering/leaving, how many people, for how long, which rooms" questions
*It's an entry panel kiosk, with a quick (and, hopefully, intuitive) workflow to answer "entering/leaving, how many people, for how long, which rooms" questions
Image
*[https://www.youtube.com/watch?v=8j_pyLVx2Rc Demo video]
a few custom PCBs, the pads are captouch (the heart board is a TTP229 breakout)
*Uses a few custom PCBs, the pads are captouch (the heart board is a TTP229 breakout), designed to be easy to source and assemble independently
runs on ESP8266/32, I have MicroPython firmware written for everything except the actual "send data somewhere" part because I never defined the API I'd be interacting with
*It runs on ESP8266/32, MicroPython firmware is complete for everything except the actual "send data somewhere" part because I never defined the API I'd be interacting with.
but it reads buttons and processes them according to the planned UX flow
*The firmware reads buttons and processes them according to the planned UX flow, and has quite a few nifty features for usability. Also, designed to collect anonymous data, of course
it's A4-sized and 3mm, designed to be easily cuttable on a K40
*The panel design is A4-sized and designed for 3mm lasercut wood, so, should be easily cuttable on a K40. The touch pads have 2mm acrylic spacers in front of them - also easily lasercuttable!
also, designed to collect anonymous data, of course
*So if such a workflow would help you, I can publish the non-yet-published design files, and mail the assembled&tested custom PCBs I have if that'd be helpful
so if such a workflow would help you, I can publish the non-yet-published design files and code, and mail the assembled&tested custom PCBs I have
*I've designed this to be useful for other hackerspaces, it's just that I've never gotten to actually getting my shit together and publishing it all
I've designed this to be helpful to other hackerspaces, it's just that I've never gotten to actually getting my shit together and publishing it all
*[https://cdn.discordapp.com/attachments/720514857094348843/928874916747554827/photo5962911158593763345.jpg Lasercut button box prototype picture]
*[https://cdn.discordapp.com/attachments/720514857094348843/928874916747554827/photo5962911158593763345.jpg lasercut button box prototype picture]
*[https://cdn.hackaday.io/images//3109751641678761591.jpg Box internals picture - with a random ESP32 devboard]
*[https://github.com/CRImier/SaferSpaceEntryPanel/blob/master/main.py MicroPython code for an ESP8266/32 controller]
*[https://github.com/CRImier/MyKiCad/tree/master/Fluff/touch_pcb_24mm Touch electrode PCB design] - FR4 pieces can be used
*[https://github.com/CRImier/MyKiCad/tree/master/Breakouts/ttp229bsf_breakout TTP229 breakout PCB design] - a generic TTP229 (16-key capacitative touchpad breakout) can be used instead
*[https://github.com/CRImier/MyKiCad/tree/master/ESP8266/esp12_ss_breakout ESP12-based controller PCB design] - a generic ESP8266/32 devboard can be used instead
*Sample JSON output: <pre>{'time': 0, 'locations': [2, 1], 'guests': 2, 'leaving': false}'</pre>

Latest revision as of 15:27, 8 January 2022

Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate E
Projects | Concepts | Proposals | Art | Spacebridge | PFA Template V · T · E


PROPOSAL: People Counter would track how many people are in the space for occupancy safety monitoring.


Proposals to improve Noisebridge. Edit

Culteejen Proposal

[edit | edit source]

Proposal for y'all:

  • As mentioned before, I wanted to create an app that can show people if / how many people in the space. I whipped up the server side stuff tonight (I tested it on my bot channel) to demonstrate what it would look like.
  • I'm thinking there would be something like a button you would press at the space to increment / decrement the number, and it would update the number on the server
  • screenshot prototype

CRImier Proposal

[edit | edit source]
  • It's an entry panel kiosk, with a quick (and, hopefully, intuitive) workflow to answer "entering/leaving, how many people, for how long, which rooms" questions
  • Demo video
  • Uses a few custom PCBs, the pads are captouch (the heart board is a TTP229 breakout), designed to be easy to source and assemble independently
  • It runs on ESP8266/32, MicroPython firmware is complete for everything except the actual "send data somewhere" part because I never defined the API I'd be interacting with.
  • The firmware reads buttons and processes them according to the planned UX flow, and has quite a few nifty features for usability. Also, designed to collect anonymous data, of course
  • The panel design is A4-sized and designed for 3mm lasercut wood, so, should be easily cuttable on a K40. The touch pads have 2mm acrylic spacers in front of them - also easily lasercuttable!
  • So if such a workflow would help you, I can publish the non-yet-published design files, and mail the assembled&tested custom PCBs I have if that'd be helpful
  • I've designed this to be useful for other hackerspaces, it's just that I've never gotten to actually getting my shit together and publishing it all
  • Lasercut button box prototype picture
  • Box internals picture - with a random ESP32 devboard
  • MicroPython code for an ESP8266/32 controller
  • Touch electrode PCB design - FR4 pieces can be used
  • TTP229 breakout PCB design - a generic TTP229 (16-key capacitative touchpad breakout) can be used instead
  • ESP12-based controller PCB design - a generic ESP8266/32 devboard can be used instead
  • Sample JSON output:
    {'time': 0, 'locations': [2, 1], 'guests': 2, 'leaving': false}'