|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||||
|
|||||
|
Re: Programming the PSoC
It's not required.
It's only necessary if you want to do something non-game controller-ish. |
|
#17
|
||||
|
||||
|
Re: Programming the PSoC
you only have to attach the PSoC to the classmate if you want to program in extra buttons. You can, however, use it on the robot with custom circutry and software, if you want.
|
|
#18
|
|||
|
|||
|
Re: Programming the PSoC
Teams are not required to use the I/O board. In fact the new DS now allows for virtual inputs to autonomous and virtual LEDs without using a soldering iron and electronics. On the other hand, the I/O board is very functional and actually very fun to play with. You can use a breadboard or other breakout board to make some very cool custom driving circuits.
The I/O tab on the DS can be used in several ways. If the I/O board is not connected, it is virtual. Numeric and digital values will be sent to the robot code simply by entering them onscreen. Digital output values will be displayed onscreen. If the I/O board is attached, reprogrammed, and connected to switches and knobs, the HW values will be displayed on the I/O tab to assist with debugging, and the HW values will be sent to the robot code. When plugged into the computer, there are actually two modes to choose between. The I/O board can be used in compatibility mode which will work pretty well with the API used last year, and which will give you four analogs and either digital inputs and eight digital outputs. This should allow it to work pretty well with code written for last year's robot, or to be used by teams already familiar with the system who want something familiar. Or, the I/O board can be Configured to be in enhanced mode. This opens up a lot of additional types of I/O as well as just having more I/O. I won't repeat everything in the manuals, but this is certainly worth exploring even if just to learn about sensors and circuits. Greg McKaskle |
|
#19
|
||||
|
||||
|
Re: Programming the PSoC
I don't really think there is any need for it. It's unimportant enough to wait until the season is over to program unless you've managed to use up all the buttons on whatever controller you're going to use.
|
|
#20
|
||||
|
||||
|
Re: Programming the PSoC
Thanks for all the replies... Looks like I'll wait until the offseason before attempting this. Thanks again for everyone's help.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| PSOC Interface Card | Lafleur | Technical Discussion | 4 | 09-02-2010 13:26 |
| Programming the IR | Pi Boy | Sensors | 3 | 21-01-2008 15:47 |
| Programming the vex microcontroller to respond to commands on the serial port | crashoverride02 | Programming | 1 | 20-10-2006 14:17 |
| Programming The CMUcam for the Vex controller | 987HighRoller | Programming | 3 | 24-06-2006 15:27 |
| Programming the IR | James Hine | Programming | 1 | 10-03-2004 14:08 |