AndyMark Pixy Camera FTC Allowed?

[Andrewiski]

AndyMark sent out a promotional email advertising the Pixy Camera as an i2c Vision Sensor. Will this camera sensor be allowed for 2016-2017 FTC competitions. Running into some limitation in Vuforia object detection trying not to kill the processor on our ZTE speed with open CV and Vuforia running at the same time. ALready crashes if you rotate to quickly brings vuforia targets into view to fast. I have already written a couple I2C custom modules just wonder if they will rule this legal since its more of a processor wired to a camera?

http://www.andymark.com/Pixy-CMUcam5-Smart-Vision-Sensor-Camera-p/am-3477.htm?utm_source=FRC-PixyCam%2C+3%2F8+Hex+Shaft%2C+DoD+Daily&utm_campaign=FRC+PixyCam+3%2F8+Hex+DotD&utm_medium=email

Thanks

[JohnMcDonnell]

Last year it was allowed:

01-14-2016, 11:42 AM
Thanks for the earlier reply related to the Pixy.
Assuming:
a) it is the sole device on a DIM;
b) it draws less than the 150ma DIM maximum current;
c) it is in this context only an I2C device
Would the Pixy be a permitted sensor?
See also http://www.cmucam.org/projects/cmucam5
Thanks,
Martin Haeberli
Mentor, FTC 7593, TigerBots

A: Assuming all the above can be done without violating any other rules, yes, the Pixy would be a legal sensor

[GearTicks]

AndyMark sent out a promotional email advertising the Pixy Camera as an i2c Vision Sensor. Will this camera sensor be allowed for 2016-2017 FTC competitions. Running into some limitation in Vuforia object detection trying not to kill the processor on our ZTE speed with open CV and Vuforia running at the same time. ALready crashes if you rotate to quickly brings vuforia targets into view to fast. I have already written a couple I2C custom modules just wonder if they will rule this legal since its more of a processor wired to a camera?

http://www.andymark.com/Pixy-CMUcam5...m_medium=email

Thanks

I am not sure it is possible to implement this I2C in the FTC SDK due to the assumptions the DIM makes about how you will use I2C. Specifically, the Arduino library for the Pixy (see I2C implementation here and its usage here) does reads without specifying a register. This is valid I2C, but the DIM requires you to specify what register(s) you want to read from.

[Andrewiski]

I am not sure it is possible to implement this I2C in the FTC SDK due to the assumptions the DIM makes about how you will use I2C. Specifically, the Arduino library for the Pixy (see I2C implementation here and its usage here) does reads without specifying a register. This is valid I2C, but the DIM requires you to specify what register(s) you want to read from.

I ran into this last year when I wrote an I2C wrapper for a 4" Adafruit 7 Segment Backpack, as we wanted a big count down timer on our robot so our drivers always knew the time with out looking at the board. I used a Wire like wrapper for FTC

Comments look like this in Wire wrapper File Can't remember where exactly I got it but it made it a lot easier to use Arduino Source as a template for making wrappers for FTC hardware.

/**
* Created by Olavi Kamppari on 10/25/2015.
*
* Revisions:
* 151107 by OAK:
* 1) in portIsReady fixed problem related to repeated read of same address
* 2) in executeCommands added missing line to stop idle polling
*/

Then I wrote register with a zero length payload and it put what I needed onto the i2c bus. Its been a year Since I did that but the source is in our github project (Andrewiski/ControlFreaks_ftc_app) and I do not believe I changed Wire source at all but honestly been so long don't remember.