From: Robert Roland on
On Fri, 5 Mar 2010 03:30:46 -0800 (PST), SPow
<guillaume.quere(a)estaca.eu> wrote:

>I have been reviewing farnell's shop to get an idea of existing PICs,
>but I am clueless regarding which one i should choose.

Microchip have an online parts selector application. I find it quite
useful:

http://www.microchip.com/maps/microcontroller.aspx
--
RoRo
From: Jamie on
SPow wrote:

> Hi,
>
> I have been reviewing farnell's shop to get an idea of existing PICs,
> but I am clueless regarding which one i should choose.
>
> The PIC is connected to an accelerometer (input) and has 2 outputs,
> one that is either 0 or 1 (solenoid command) and an additional EEPROM
> to store measurements from the accelerometer (associated to time
> measured by the PIC itself)
>
> I guess i have to take a 16 pins-PIC in case there are additionnal
> input we forgot about. Is it a problem if you only use a half of the
> pins ?
> I read that an I�C bus is an easy way to communicate between
> accelerometer/PIC/EEPROM, but it's not singlely available for a 16-pin
> PIC.
>
> On farnell mainpage, i searched for '16-pins' which leave 'AUSART,
> I2C, SPI' / 'EUSART, I2C, SPI' and a few others selectable. There
> doesn't seem to be any I2C only 16pins PIC, so which additionnal
> interfaces should i select ?
>
> What i know from my system is that it doesn't have to be very quick,
> 10 to 20 measurements a second is pretty enough. It needs a timer for
> 2 reasons : at a specified time, it'll have to force a solenoid open,
> and keep track of the time on the additional EEPROM.
>
> I'm pretty clueless about how i am to choose the controller, and would
> much appreciate help on this subject.
> Thanks for reading.
You can write your own I2C protocol in the PIC via an INT and unused IO
lines.

That is what's great about this whole thing..