Thread: Detecting and handling sensor failure gracefully
View Single Post
  #8   Spotlight this post!  
Unread 20-04-2004, 14:03
Astronouth7303's Avatar
Astronouth7303 Astronouth7303 is offline
Why did I come back?
AKA: Jamie Bliss
FRC #4967 (That ONE Team)
Team Role: Mentor
  
Join Date: Jan 2004
Rookie Year: 2004
Location: Grand Rapids, MI
Posts: 2,071
Astronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud of
Re: Detecting and handling sensor failure gracefully
I like this, but it also sounds incredibly complex. The current sensor we used on our hand just made it complicated. That was just a pot and a current sensor. If the pot failed, the driver can work around it. if the current sensor fails, it's screwed. (it's based off a limit-trip. after 5 loops of tripped, it won't move until you reverse). However, i did not include anything for detecting failure.

And what about telling the drivers about failure? OI LEDs or dashboard? what about 3rd party transmitter/reciever setups? I mean, a tablet PC in the driver's station would be cool, but I can think of a thousand other things to spend that money on (Like a second bot!).

One other thing: is there a reliable way to setup so that a computer can send stuff to the RC through the OI? Does the dashboard port take input, too? My thought is you have a computer that monitors the system, and if something goes wrong, you can tell the computer what to do, and it rellays it to the RC.