<< return to Pixycam.com

Possible to make Pixy expect only white dot/blob objects? (IR objects seen through IR filter)

Hi Scott,

Maybe you can help me with understanding a related issue. When we release the modified Pixy code (for IR detection), could it possibly be compatible with the upcoming open-source development toolchain. We are currently working in Keil, but we would like for other folks to be able to modify/improve the IR-detection code using freely available development tools.

Thanks,
Thomas

Hey Thomas,
Sure— your code might need some tweaks, especially if you have any assembly code, but just tweaks to make it compile correctly under gcc.

Thanks Rich. It probably will not work on the first try, but it sounds like I will eventually be able to ensure gcc compatibility … This will be very helpful for users with specialized applications.

-Thomas

Thomas, that sounds super great. I’m already a backer of your campaign, looking forward to it!

Being able to use Pixy to track IR blobs is frankly my ideal use case.

Awesome. Thanks!

It looks like we have some very talented people ‘backing’ us. I REALLY look forward to seeing the cool projects that will start up in December.

One group will be floating large ‘IR spheres’ in the Alpine River, and then using a Drone + IR-LOCK to track particle flows … wow.

-Thomas

I think m_lut is a 320-by-200 table.
Matt M wrote:

Could someone quickly let me know if I’m on the right track, and where the m_lut is evaluated? I’d really appreciate the help! Thanks!

Tiger He wrote:

I think m_lut is a 320-by-200 table.

want to chime in here— that’s not correct. Read the text above that’s really well stated:

m_lut is a 256-by-256 table of color values which covers a space whose axes are the color properties “u” (red minus green1 intensity) and “v” (blue minus green2 intensity). This is what ColorLUT::map does in ColorLUT::generate. m_lut maps each point in that color space to one of up to seven color signatures, as determined in ColorLUT::add.

Thomas Stone wrote:

Hi Donald,

This is Thomas from the IR-LOCK project. We are working on firmware that helps Pixy reliably track IR blobs (essentially, ‘white blobs’). It seems like a simple problem, but we have some serious improvements to make before the first release in December:

Allowing the user to easily select an Exposure Value based on the operating environment
Disabling auto-exposure control (while also selecting a good Exposure Value)
Not ‘breaking too many things’ in the process of modifying the code. Essentially, de-bugging
Enhancing performance based on experiments with our IR hardware (lens, filter, IR markers) and modified firmware
… a long of list of other features we would like to add

I am super-busy nowadays, but I will try to reply as soon as possible if you have questions about the IR-tracking capabilities of Pixy: thomas a t irlock d o t com

Best,
Thomas

Thomas,
Will the firmware that helps Pixy reliably track IR blobs you are working on be open-source and available publicly? Also, since your using the Pixy in your project did you replace the lens with one that does allow IR in? If so would you be willing to share which one?

Hi Adam,

The custom firmware and source code is located here (link below). However, editing and compiling the code is not straightforward. You will find some comments about this on the Pixy forum somewhere.

We use a 3.6mm lens without an IR-cut filter. Our supplier is not m12Lenses.com, but you can find lenses on their website (http://www.m12lenses.com/).

The most expensive part is actually the optical filter. We sell all of the parts in a kit here: http://irlock.com/products/ir-lock-filter-for-pixy

Let me know if you have any more questions.

Best,
Thomas

Thomas,
Thanks of the quick response and the info. I ordered the parts kit to add to my Pixy, so thanks for that. I also registered for the IR-Lock forums, but I can’t seem to find the thread on editing and compiling the code. Can you possibly point me in the right direction?

Those comments are somewhere in the Pixy forum, not the IR-LOCK forum. Basically, the firmware compilation requires an expensive software, but they are working on fixing this.

-Thomas

I think this is maybe the most informative thread.
http://www.cmucam.org/boards/9/topics/4336

Also, if you are doing work at a university, you may be able just go ahead and get a license for the compiling software.

-Thomas