People Counter: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| 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 | *'''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== | ||
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 | ||
*a few custom PCBs, the pads are captouch (the heart board is a TTP229 breakout) | |||
a few custom PCBs, the pads are captouch (the heart board is a TTP229 breakout) | *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 | ||
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 | *but it reads buttons and processes them according to the planned UX flow | ||
but it reads buttons and processes them according to the planned UX flow | *it's A4-sized and 3mm, designed to be easily cuttable on a K40. also, designed to collect anonymous data, of course | ||
it's A4-sized and 3mm, designed to be easily cuttable on a K40 | *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 | ||
also, designed to collect anonymous data, of course | *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 | ||
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 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] | ||
Revision as of 13:44, 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.
|
Culteejen Proposal
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
- 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
- a few custom PCBs, the pads are captouch (the heart board is a TTP229 breakout)
- 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
- but it reads buttons and processes them according to the planned UX flow
- it's A4-sized and 3mm, designed to be easily cuttable on a K40. 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 code, and mail the assembled&tested custom PCBs I have
- 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
- lasercut button box prototype picture
