Pixy2 BeagleBone Black API

So, let’s talk about the BeagleBone Black—it’s kind of like the Raspberry Pi but comes with its own set of features.
First, you’ll want to connect to your BeagleBone Black using SSH.
Once that’s done, update your package manager list and check for any available updates.
After that, go ahead and install the essential packages like USB, libboost, and CMake without having to worry about agreeing to prompts manually.
Now it’s time to download the source code files and build them using the Pixy script you have.
Don’t forget to run a shell script that builds the USB-related libraries, following those clear step-by-step instructions.
Finally, wrap things up by using the ‘sudo install’ command to install the built library and check out the ‘HelloPixie’ example to confirm everything is working smoothly..

So, when you head to the top of your project directory, you’ll stumble upon the build folder .
This folder is your treasure chest, packed with all the files you need for your project.
If you give HelloPixie a run, it’ll show you the version, but don’t panic if the data isn’t showing up right away—it only kicks in once you put an object in front of it.
After you connect the Pixy to the BeagleBone Black through USB, you’ll start seeing data pop up on the terminal as soon as you introduce an object.
And for those keen developers out there, you can dive into the HelloPixie source code by heading to the source folder, where a wealth of comprehensive C++ code awaits you to explore..

So, when you fire up the program, it shows you some specific block info, which comes through as an array.
You’ll need to add the Pixy header and call up the Pixy library, which is pretty similar to what you did with the Raspberry Pi or Arduino setup.
The whole process involves setting up interrupts, showing the version as it runs, and checking if the Pixy library kicked off successfully.
Depending on how that initialization goes, your program might either quit or keep going, and it’s also gonna ask for the firmware version..

Let’s dive into the world of conditional statements! So, there are these things called macro constants that relate to conditional statements, but right now their value is set to 0, which means that part doesn’t run.
If you switch it to 1, though, you’ll get a load of detailed debugging info! The video also explains how to recognize blocks, mentioning that the rumble flag keeps checking for new blocks in a loop, just like how the Raspberry Pi operates.
Speaking of blocks, the block buffer can handle up to 25 blocks at a time, and it gets all that info into the ‘blocks’ variable as an array.
To figure out how many blocks are recognized, they use Gap Blocks; if the result is minus one, it means there’s an error.
Otherwise, the program goes through each block to show you in-depth information.
And hey, when you wrap things up by hitting Ctrl-C, the PC closes down, and they even tease us with what’s coming next about controlling PC2 through various interfaces!.