feat: Split the Counter from the Peeper #7
Conversation
Also: - Add pyproject.toml - Add CI checks - Introduce new project structure - Add some initial tests
DoomHammer
force-pushed
the
outsource-counting
branch
4 times, most recently
from
0c368f5 to
d27c74f
Compare
DoomHammer
force-pushed
the
outsource-counting
branch
from
d27c74f to
55fcce2
Compare
|
Fixes #6 |
|
@DoomHammer can you explain what the plan is? Remove the AI away from the PI (leaving a camera with a counting 7seg LED), or something else? I think right now I'm the one who has te deploy it through Balena; does it make sense to move it to your account (or make a HS3 account)? |
|
I checked the Count and the guy is hot! I mean, even for our standards. The enclosure looks a bit melted as well. Throttling the fan won't get us far. Probably just closer to meltdown. We would then have nice Count-looking stalactites. So the idea is to split the logic in two. The Pi Count is peeping and displaying, but there's another more powerful Count that does the actual counting. The Powerful Count has fans that could probably put down fire, so we're kinda safe with that. As for the Balena account, a dedicated HS3 account would work the best. |
|
OK, makes sense. Good then I know what I'm looking at :) 
|
|
I've tested the counting part and it seems to be fine. The peeping part is what I'm concerned about, especially since there are no libcamera2 and gpiozero mocks or fakes to test without actual hardware. |
|
I've actually created an account for us on Balena but I'm not sure what the next steps should be. Flash the OS they provide and then select the payload in the UI? That's it or do we need to do some tweaking first? |
|
Yes, no better way than to test on the real hardware. Indeed create a project and download the os. Voncount uses a wired connection so no need to do anything special. Then boot up front that sd, and it should install your project. You can use local mode but I find that not all that useful; pushing through balena usually goes well. Balena cli is very useful though |
|
One more thing: I remember we had a problem with DNS server. How can we configure Balena to use only local DNS when resolving .hs3? |
|
Good point. I will check the balena config I used when I get home. Things are either in there, or in the repository. |
|
Just showing you all the things that were set in Balena:
(values: `192.168.0.44`, redacted, but I think well known, and `hs3`)
(Note that these items can be set as device of fleet configs; if you only have a single device there is really no difference. |
4 participants
Also: