Cypress Layout (over wires?)

[jhersh]

Originally Posted by Mark McLeod

My mistake is confirmed. The Digital Outputs were reversed.
In the LabVIEW code the I/O counts begin at 0 not 1, so just be aware that Digital Output 1 is referenced in the code by "0". In C++ the reference matches as 1-8.
These labels are how the Driver Station sees them.

The pinout you show is accurate for the compatibility mode. However, if you click "Configure..." on the I/O tab, you can switch to enhanced mode at the bottom and then you can make all 16 digital lines input, or all 16 digital lines outputs or any mixture in between (in addition to a ton of other features).

I'm not sure what LabVIEW code you are referring to. If you mean that the array index is 0 for digital input 1, for instance, then you are correct, but that is simply because the index array primitive in LabVIEW is 0-based. Nothing in the API (compatibility or enhanced) is "0-based".

[Randy Forgaard]

The way I read the <R82> rule change in Team Update #4, posted yesterday, it appears that we are no longer required to use the breadboard with the Cypress PSoC 3 FirstTouch Kit I/O module, and we can now use the eStop Cypress Carrier and Enclosure available from AndyMark for more safe and robust mounting and I/O pin access. It would also appear that the Jan. 18 posting by the Game Design Committee on the FIRST Q&A Forum, saying that we can only use the breadboard, is now out of date. Does anyone disagree? (I am hoping to post this question also to the FIRST Q&A Forum through our Team Rules Expert, who has access.)

Please let me know if you read this rule change differently. Many thanks!

[jhersh]

I believe that does obsolete the posting on Q&A.

[eugenebrooks]

It does appear that they have drawn a line through
"the breadboard," removing it as a requirement,
and refer to "carrier board" now. Clarification via
QandA would be important, but the plain English of
the reworded rules is what it is.

Eugene