Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Please post what you know, but i doubt the fix is as simple as you seem to think it is.

On a side note i just found out are RC is back from competition so hopefully i can test the tempurature stuff more.

EDIT: WOW, 105 posts in this thread.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

NOWHERE NEAR as bad.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Come'On guys, the someone used RC for "Robot Controller"
in posts above and then someone distorted it to "RC" circuit for
timing. Lets get back on topic...

Its not the Crystal... It is likely the R and the C in the CMOS
wiring...

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

If you had the 8.2[3] battery voltage problem, and you applied the
high priority interrupt patch, and the linker patch, and it fixed the problem,
WE REALLY WANT TO KNOW!

Eugene

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We've never had this problem.. I patched the linker script Thursday, when I found out there was a patch. I don't know if it fixed problems that would have occured, or if we never would have had them.

I can't see any reason why you shouldn't use both patches.. What more can you do? Patch both and hope for the best.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

I am positive that we had the 8.3 Volt battery problem. I dont know what was fixed but I do know that it was fixed by a moderate programmer in 5 minutes. I also know it had something to do with switching ports and making our robot shiver but not work. The person who fixed it(Brandon Heller, Tim Emerson also knows about it) is a regular to this site and i am very surprised he hasnt read this thread. I dont know where he got the fix or anything, I heard something about a team update and a new version of something. I wish I could be of more help. I will try to get a hold of somebody who knows what they are talking about.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Ok all, just back from GLR. I was in terror of the 8.2V bug thursday night and saw the patch in here. I was going to rebuild and dump code to make sure we wouldn't get hit, but figured the odds were low that it'd happen in the first match, and we had a lot of robot work to do. So, of course, I see the dreaded 8.2V on the OI when we're out on the field. Tried to cycle the power, but the match was starting, so that sucked. Rebuilt the code and dumped it, and didn't have the problem for the rest of the regional.

However, this is such an intermittent problem, that I'd sort of like to have a statistically significant sample of people this has worked for.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

I talke dto one of our programmers at school today and I sent an email to a mentor, so one of them should be on here soon.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

IFI has posted the patch already.. It's on their web site. You don't have to know any programming to do it..

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

I am curious about this subject. We had some troubles in AZ, seemed like our bot was glitching. Very sporadic, we were never able to trace it.
What were the symptoms of this voltage bug?

Thanks in advance

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Typical symptoms are your robot just plain not working. It tends to hit as soon as you power the bot on and won't ever rectify itself once it happens. Atleast until you completely power the bot down. When it happened to our bot, we just ran back and forth and the joysticks wouldn't do anything.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

On our controller the problem never occurred on startup although most of the others I've personally seen occurred immediately at startup.

It hit us after the robot had been on awhile. The symptoms will differ with your individual control setup. In one instance ours suddenly began attempting to rapid fire our poof balls all on it's own. The more common case was the gunner would suddenly find himself controlling the left drive train, or when idling the robot suddenly began driving away slowly. You will see mechanisms moving without orders and controls that won't control.

No recurrence for us in competition with the IFI library update and blocking out bank 15. But the controller doesn't run very long in matches.

I did see the problem in a couple of other robots at competition, but they didn't have the newest patches in.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We patched our code with the interrupt related patch, and the linker script patch, and although we did not see 8.2 displayed on the controller for the battery voltage our code refused to load and run on the 2006 controller. Retrofitted to the 2005 controller our custom code loaded and ran without any problems.

Depending on your use of interrupts and timers, you may, or may not see problems continue after patching your libraries and linker script. Several teams at the San Jose regional remained dis-functional after patching.

The only sure cure seems to be a 2005 controller upgraded to V12 master code. The upgrade is required and checked by the technical inspectors. If you are having problems with the 2006 controller, I would like to suggest that you use a fix-it window to retrofit your custom code to the 2005 controller, squeezing it to fit if required, so that it is ready to go if you need it. Don't forget to have a copy of the V12 master code to load into your controller.

Have fun, and don't forget that it all about fun and nothing else...

Eugene

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Nope.. The 2006 RC is required this year.

Post on QA about it too: http://forums.usfirst.org/showthread.php?t=788