Hi-resolution (CAM_MODE0)

209 views
Skip to first unread message

Richard Hall

unread,
Sep 13, 2015, 9:41:37 AM9/13/15
to pixy_firmware_sdk
Hi Rich,

I want to try the Pixy in the higher-resolution/lower frame rate mode as that might suit my soccer tracking application better.  In a moment of wishful thinking I tried changing:
cam_setMode(CAM_MODE1);
to
cam_setMode(CAM_MODE0);
in 
progblobs.cpp line 43 to see if that was sufficient.  That compiled OK but when uploaded to the pixy it gives the following in pixymon:
Pixy detected. 
error: Unable to connect to device.
I've spent a bit of time going through the code but any pointers on how to get this mode working would be appreciated.

Keep up the great work!

Rich

Rich LeGrand

unread,
Sep 15, 2015, 9:54:53 AM9/15/15
to Richard Hall, pixy_firmware_sdk
HI Richard, 
The current code uses the 640x400 mode mostly due to RAM constraints, but there are some timing constraints too.  If you use mode 0, it will crash because the pixel timing is 2x faster and there isn't enough RAM.  It's not straightforward to make this mode work with the current code...  Sorry :(

--rich

--
You received this message because you are subscribed to the Google Groups "pixy_firmware_sdk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pixy_firmware_...@googlegroups.com.
To post to this group, send email to pixy_fir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pixy_firmware_sdk/6962dde2-1e0c-44fc-8094-e8fed68b01e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Richard Hall

unread,
Oct 11, 2015, 3:31:05 PM10/11/15
to pixy_firmware_sdk
Thanks Rich,

I've been thinking about this. You say not straightforward but not impossible right? Providing I can crack the pixel timing and work around the RAM constraint in my algorithm? I like a challenge!

Cheers,

Richard

Rich LeGrand

unread,
Oct 16, 2015, 11:41:45 AM10/16/15
to Richard Hall, pixy_firmware_sdk
Hi Richard, 
Sorry for not replying sooner!  

Pixy has 264K of RAM, much of it isn't contiguous and much is used to store code and various buffers.  The largest contiguous RAM is 128K.  That is a fairly big constraint if you want to do a standard grab-raw-frame then process-raw-frame.  At 1280x800, 128K doesn't get you much.  We use the M0 to filter out lots of pixels so we don't need a lot of ram for frame store. 

What kind of algorithm did you have in mind?

best,
--rich
   

--
You received this message because you are subscribed to the Google Groups "pixy_firmware_sdk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pixy_firmware_...@googlegroups.com.
To post to this group, send email to pixy_fir...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Reply all
Reply to author
Forward
0 new messages