Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We were able to work around it by not using printf or Kevin's serial code. We successfully used IFI's blocking serial libraries without triggering the bug. I do not beleive that Kevin's serial code is the entire problem, as we tried reproducing the problem with just his code several times. Rather, we've decided that it is some wierd interaction between his code and our code.


We replaced all our printfs with DEBUG statements like Kevin's camera code so we could easily disable all printfs before doing anything important.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

I find it scary that the linker is allocating variables such that problems that bad are appearing, and you're using code that could do that.

All variables are statically allocated.

Pointers and arrays are used only a few times in the code.

Issues that bad would suggest that something is very, very wrong at a fundamental level. Try it on another RC.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We are having the same problem that you guys speak of in this thread, and we can't understand from this thread what the exactly is the solution...
Can anyone please clarify to us what exactly we shoud do?
We are using Kevin's most updated code...

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Whoa, really? Can you zip up your entire build directory and e-mail it to me?

-Kevin

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

I'm sorry for the confusion, everything is ok now.
Thanks a lot though =]

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

What do you mean everything is okay now? Given the pain the 8.2 bug caused teams in the past, you need to let me know if you actually had this problem, so that I can try to understand it and hopefully provide a fix.

-Kevin

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We experienced this bug earlier this year. We changed the size of our autonomous code and it went away.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Is this with my code? If you happen to have an archive copy of the malfunctioning code, can you e-mail it to me? Has anyone else seen the 8.2 bug this year (yes, that includes you, over there in the corner)? If you have, please post here.

-Kevin

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We are using your gyro + encoder code integrated into last years ifi default code.

We didn't remove any functional code when we did our clean up - we deleted some old procedures that we were not even calling. We were not close to the memory limits. That's the best information i can give you as we only keep the last 4 days of code - the rest gets deleted.

We're using MPLAB 7.20.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We experienced this bug, I think, twice for the first time tonight. We'll be driving the robot around normally and, without warning and for no obvious reason, it will stop in place and cease responding to all inputs. The OI shows 8.3V and the Code Error light illuminates.

Since I'm not a programmer, I can't say too much about how we have things set up. We're coding manually within EasyC and using two Chicklets for control, if that makes any difference.

I've pointed our programming mentor to this thread, as well as to the document provided by IFI about changing the information in the linker file. I'll update this with more information from him as I come across it.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

We have gotten the 8.2 bug on multiple occasions. Sometimes we'll turn on the robot and it'll go freaking crazy (right track at full speed and drive the arm all the way up, fortunately it seems to obey the limit switch and not overdrive it). We'll hit the disable switch and read the OI, lo' and behold it reads 8.2.
After a complete power cycle (kill main breaker and hit the reset button to power off the RC), sometimes we have to do it twice, it'll work just fine.

I believe this code is the 2007 default plus all of the changes we've made. We did not get this bug in any previous years and we don't know what made this happen this year.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Before this happened had you completed all the steps mentioned in this document?

-Kevin

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Help!

We now figured out why the 8.2V bug went away last time - it's because we stopped using our practice bot + controller and switched to our new one.

Today we went back to the practice bot, loaded the code that works perfectly well on our competition bot, and it immediately went into the 8.2V bug.

I've deleted and commented out huge chunks of code in an attempt to change the compiled memory footprint however it does not seem to make a difference. Nothing we do with this code seems to correct the problem.

The issue immediately goes away upon loading the IFI default code. Can someone take a look at this and see if there's anything that jumps out at you as to the cause of the issue? Thank you!

We updated the master code to check if that fixed the issue and it did not.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Just for fun, we got our 2006 board out and used that - no 8.2 error. So we get 8.2 on the 2007 board, but not the '08 or the '06.

That makes me lean toward a silicon issue.

Kevin, if you would like our code, I can email it to you.

Re: The 8.2 (or 8.3) Battery Voltage Bug
 

Yes, please.

-Kevin