View Single Post
  #5   Spotlight this post!  
Unread 30-01-2011, 19:07
sircedric4's Avatar
sircedric4 sircedric4 is offline
Registered User
AKA: Darren
no team (The SS Prometheus)
Team Role: Mentor
 
Join Date: Jan 2008
Rookie Year: 2006
Location: Lousiana
Posts: 245
sircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond reputesircedric4 has a reputation beyond repute
Re: Enhanced IO Error

Quote:
Originally Posted by Mark McLeod View Post
Changing the pins does not enable Enhanced mode.

Did you choose the Enhanced radio button in the bottom left of the Configure I/O screen?
Yes, that then brought up the new screen with all buttons and leds and digital inputs and such. It is a very busy screen compared to the old I/O screen.

Still getting the same error.

UPDATED: I figured out why we were dropping communciation during the teleoperated period. It had to do with creating a new build target when I copied my workspace for a new version. Apparantly the defaults for a new build target are not setup properly for a FIRST robot. I am instead creating a new Example each time and then dragging my code into the new example for each version. If your code drops communications during enabling, your build target may be setup wrong.

Still can't get the Enhanced IO to work though, and still receiving the IO error. Still need help figuring that out.

Last edited by sircedric4 : 31-01-2011 at 07:36. Reason: Added Update
Reply With Quote