View Single Post
  #5   Spotlight this post!  
Unread 15-03-2004, 11:54
KenWittlief KenWittlief is offline
.
no team
Team Role: Engineer
 
Join Date: Mar 2003
Location: Rochester, NY
Posts: 4,213
KenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond repute
Re: SW bug has ME stumped!!!

yes we searched on the variable to makesure it was not initialized somewhere else to a different value, or changed somewhere else in the code

we didnt have any time to debug it at the pittsburgh regional - to busy fixing things that needed fixin

I guess we could put printf statements in and see what the inputs and variables are on powerup - or maybe put a poweron counter in the code that increments for a second on powerup, blocking this code until the link has booted?

cause if the input switches from the OI are invalid on powerup, then the diable signal would be invalid too - you wouldnt even be able to skip the code while the bot is disabled, cause all it takes is one invalid cycle and our variable will be changed.

BTW our bot is in a crate somewhere between pittsburgh and cleveland, so I have no way to test this until next thrusday - Im hoping someone would be able to explain the erratic ways of the input signals at powerup, or spot a bug in our code.