Other than a few test flights, I’ve now put Phoebe on hold so as not to break her before the CotswoldJam at the end of September. I’ve bought her a new case so I can carry her around safely:
So this morning, I picked up doing motion processing using the RaspiCam YUV macro-block output – kitty++.py, partly triggered by a pingback yesterday. The motion processing (in a very simple form) is working fine, but it only produces a CSV file as output allowing me to see the data as a graph in Excel:
Ideally for testing, I’d want a small screen to show the direction / speed the motion processing is detecting. And as she’s headless, I’d like to add a button to press so that I can do various tests on demand while she’s headless. In one of the twists of fate, the post brought my new E-paper HAT. Here’s it installed on Kitty:
The camera is stuck underneath in one of the super-slim cases I found.
I now need to install the drivers, and update the code to draw variable length arrows for the orientation / speed vector.
After that, I need to add the ultrasonic range finder to get the distance from the ground. I’ve got a few of these – they’ll do for Kitty, but with their 100kbps I2C baudrate, they’re not good for Phoebe who needs 400kbps I2C baudrate to capture all the sensor data.
Should keep me out of trouble for a while!