View Single Post
  #13   Spotlight this post!  
Unread 10-03-2010, 12:55
heydowns's Avatar
heydowns heydowns is offline
Registered User
AKA: Jeff Downs
FRC #1511 (Rolling Thunder)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2005
Location: Ra-Cha-Cha
Posts: 142
heydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond repute
Re: Cypress / First touch I/O module recognition by DS after suspend

I had access to our team's school (and, hence, our OI) for some time last night to experiment with this in a more controlled environment than competition.

While it was happening 100% of the time at competition, I could not reproduce with 100% success rate at our home facility. Significant here is that I did not have the same robot from which to send commands to the board (I had linked it to our 2009 cRIO, but the code on such does not use the extended io as we do in 2010). I could, however, still reproduce it about 60-75% of the time.

Happened more often than not when on battery power than plugged in. Still same configuration I mentioned above (right classmate port plugged into hub, which has 2 kit joysticks and the Cypress on it).



Quote:
Originally Posted by Greg McKaskle View Post
Does this happen if you plug the Cypress directly into the laptop, then close and reawaken?
We tried this scenario last night; it seemed to alleviate the issue, but we didn't have time to put in enough tests to consider it fixed. We modified our physical setup to allow us to keep this configuration and use at our next competition in a few weeks.

Quote:
Can you report the version of the driver?
I don't have access to the board until next week, but I'll be glad to report it when I can.

Quote:
Can someone with a failure on awaken try this without the I/O board connected? With the board connected, but without any outputs connected, with outputs and no inputs?
We did not try any of these scenarios yet - I can try them next week if no one else reports results.


Quote:
Also, if you awaken and the board doesn't work, can you verify whether the Control Panel>>Admin Tools>>Services shows the PSOC service running or not?
The service is running (I have never seen it not running after telling Windows to start it automatically). Confirmed in Services CP and also in task manager.



Quote:
Originally Posted by Mark McLeod
You can get the I/O board back by terminating the Cypress service and restarting it
This did work for us in testing last night, too. Thanks for that tip.
Reply With Quote