>I stored the data as integers, which means *2* bytes per
>square= 2178 bytes for the whole maze!
>
>What does it mean to store the data as _bits_? Is that like
>NESW    > directions
>1010    >gap or wall

I'd ask Roman about this, since he seems to know the Micromouse specs, but I
think you'd have an array of 16 x 16 bytes (32 bytes total) for a grid of
256 positions.  Every position would have either a "1" if there was
something present at that location (a wall), or a "0" if that point in the
maze was empty.  If you moved the mouse through the maze, you'd only be able
to move through the "0"s.  If you tried to move one direction and
encountered a "1" at that position, it would be a wall.

>I think that unless  I radically alter my algorithm or data
>storage method, I will have to use a PIC with more memory
>or EEPROM as suggested. Is EEPROM easy to use in a
>existing program, or will it require lots of rehashing of
>the program and new code ( I'm running out of time for my
>project!)? Does anyone know of any good idiot's guides to
>EEPROM on the web??

You'd need a 4KB EEPROM, or a "32k" EEPROM.  Note that they're specified in
number of bits, not bytes, that they hold.  I'm not sure about the access
time that you need, but at 4MHz the I2C would require ~0.5ms to read a byte
from the chip, or at least ~2ms to write a byte to the chip (1.5ms is the
MINIMUM time, regardless of frequency, that you need to write a byte/page to
the EEPROM.  Sometimes needs 10ms, I think it depends on supply voltage).

--Andrew

--Andrew
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics