My team has run into a little difficulty… :ahh:
Whenever we try to use floats, longs, doubles, or anything else besides integers…our robot does all kinds of weird things it shouldn’t be doing…
As long as we use int’s, our coding runs the way it should…however, it would be very nice if we didn’t have to round everything of to an integer!
HELP!!! :eek:
Please read this thread.
That thread is about floatingpoint operations. I don’t think it applies to longs and stuff.
In reply, to the first post, It may be possible that you are running out of memory because of using too many floats, longs, doubles, etc. Can you use chars? If not then something is really wrong, because your pwms are chars.
When we tried to use ints (to print the joystick’s x and y axis values onscreen) we had nothing but the default code and those few lines! —Later though I realized that we were putting “%i” in the printf statements, only "%d"s are supported!
The other times we’ve had problems so far also have been with the default code and only a few extra variables…
Note: We’re using the team robot from last year (2004) to test our coding on…could some kind of conflict (between 05 MPLAB+default code and the 2004 robot) be causing the trouble? The idea of doing trig functions and accurate autonomous navigation with only ints and chars is not very nice… :ahh:
One word: CORDIC.