12F675 | 16F628 | 16F84 | 16f877 | 16F877A | 16F88 | 18F458 | ADC | AVR | Bootloader | CAN | CCS | CRC | EAGLE | EEPROM | ICD | ICSP | IDE | JDM | LED | Macros | Microchip | MPLAB | PCB-CAD | PIC10F | Pic12f675 | PIC16F84 | PIC16F84A | PIC16F877 | PIC18 | PIC18F452 | PicBasic | PICC | PICSTART | PWM | RS-485 | RS232 | SMT | SPI | UART | USART | USB | Wireless | Wisp628 | Xilinx

Colleagues,

In recent threads a number of you have sounded words of caution about using
C for the "smaller" PICs, such as the 12- and 16-families.

What would you recommend as a sensible PIC family for programming in C?

To put this into context, I have used C successfully with small projects,
most notably with the 16F818, and also the 12F509 and 16F84. But I'm not an
expert and appreciate that more ambitious projects might run into trouble
with these families.

Your thoughts on good PICs for C programming would be much appreciated.

Thanks,

SteveT
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

> What would you recommend as a sensible PIC family for programming in C?

Can not be answered without more details. If you want to use the full
power of C (especially recursion) 12 and 14 bit cores are definitely
out, probably 16-bit cores too. OTOH, for small projects a 10F200 might
be the prefect choice.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

--- In p...@yahoogroups.com, Wouter van Ooijen wrote:
>
> > What would you recommend as a sensible PIC family for programming
in C?
>
> Can not be answered without more details. If you want to use the full
> power of C (especially recursion) 12 and 14 bit cores are definitely
> out, probably 16-bit cores too. OTOH, for small projects a 10F200 might
> be the prefect choice.
>
> --
>
> Wouter van Ooijen

Here I thought I was missing something about the 10F series so I
grabbed the datasheet. Clearly, the 10F200 isn't going to use C with
only 256 words of flash and 16 bytes of SRAM.

The PIC18 series work pretty well with C and projects that do things
like USB and ethernet. I did a little project with one of the 18F
chips to interface a PS2 game controller to a PC by having SPI on one
side and USB on the other. It worked very well and the Microchip C18
compiler is quite good (in that it works).

But you have to take this C thing in context. You can't use a PIC to
solve world hunger or predict weather patterns. But if you just want
to write code for the hardware gadgets and control things connected to
the pins, C will work on most of the 16F series.

I have been using cc5x for years on 16F parts including my favorite,
the 16F88. Sure, the language is a subset and I can't put function
pointers in arrays and, true, it doesn't handle expressions very well,
but it works.

I have also used PIC C Lite and I could be convinced it is a better
compiler. I just reach for cc5x more often. Go with what you know, I
guess.

Richard

------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

> Here I thought I was missing something about the 10F series so I
> grabbed the datasheet. Clearly, the 10F200 isn't going to use C with
> only 256 words of flash and 16 bytes of SRAM.

Why not? If the project is simple and the compiled result is within the
chips limitations, why worry? There is no smaller/cheaper PIC, so doing
it all over in assembler to save space would be a waste of time.

> The PIC18 series work pretty well with C and projects that do things
> like USB and ethernet. I did a little project with one of the 18F
> chips to interface a PS2 game controller to a PC by having SPI on one
> side and USB on the other. It worked very well and the Microchip C18
> compiler is quite good (in that it works).
>
> But you have to take this C thing in context. You can't use a PIC to
> solve world hunger or predict weather patterns. But if you just want
> to write code for the hardware gadgets and control things connected to
> the pins, C will work on most of the 16F series.

I agree. But watch out with '16F' : some are 12-bit cores with (for
instance) only 2 stack levels. Better talk about 12, 14, 16 bit cores.

> I have been using cc5x for years on 16F parts including my favorite,
> the 16F88. Sure, the language is a subset and I can't put function
> pointers in arrays and, true, it doesn't handle expressions very well,
> but it works.

It works for you, but it would not work for someone who expects some of
the features you don't use.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

>>

I agree. But watch out with '16F' : some are 12-bit cores with (for
instance) only 2 stack levels. Better talk about 12, 14, 16 bit cores.

<<

That's a good point: I hadn't appreciated that some have just two stack
levels.

Is there a basic correlation between the 10, 12, 14, 16 and 18 families and
the 12, 14 and 16 bit cores?

The numbering system seems pretty confusing to me, especially as, in
addition to the different instruction width, there are 8, 16 and 32 bit data
busses!

Remarkably, there doesn't seem to be a basic chart or list showing the
various PICs against those two parameters anywhere on the Microchip site.

SteveT


(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

The 18F parts are nice. The 18F4620, 18F4550, etc. have worked well for me.

Alan KM6VV

---------------------------------------------------------------------------

On Behalf Of Staiger
Colleagues,

In recent threads a number of you have sounded words of caution about using
C for the "smaller" PICs, such as the 12- and 16-families.

What would you recommend as a sensible PIC family for programming in C?

To put this into context, I have used C successfully with small projects,
most notably with the 16F818, and also the 12F509 and 16F84. But I'm not an
expert and appreciate that more ambitious projects might run into trouble
with these families.

Your thoughts on good PICs for C programming would be much appreciated.

Thanks,

SteveT
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

> Is there a basic correlation between the 10, 12, 14, 16 and 18 families
> and the 12, 14 and 16 bit cores?

It is very simple!

:)

10 is for 6-pin chips, but they can be in 8-pin dip with two unconnected
pins. currently all are 12-bit cores.

12 is for 8-pin chips. Both 12 and 14 bit cores.

16 is for 12/14 bit cores with >8 pins.

18 is for 16-bit cores. no 6 or 8-pin 16-bit cores exist.

L is for low-voltage

C is for eprom/otp chips, F is for flash chips, *except* for 16c84,
which is (for all practical purposes) a flash chip

> The numbering system seems pretty confusing to me,

The guy who dreamed up the system must have been smoking some
interesting stuff.

> especially as, in
> addition to the different instruction width, there are 8, 16 and 32 bit
> data busses!

I have no experience with the >8 bits data PICs.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

----- Original Message -----
From: "Wouter van Ooijen"
To:
Sent: Friday, September 19, 2008 2:06 PM
Subject: Re: [piclist] Re: Best PIC family for C programming

> I have no experience with the >8 bits data PICs.

The dsPIC30F's were the first of the 16 bit parts, and as a result, they
keep the same semi-random numbering of the 8 bit parts. However, the 3.3
volt parts (33F, 24F, 24H) actually have some rhyme and reason.

The HJ parts are "high-speed". 24H's are very fast, much faster than 24F's,
but only a little faster than 33F's

The next digits represent the number of K-bytes of flash

Then there are letters which represents the application. This really has to
do with the emphasis of the peripherals. A motor control (MC) PIC will be
heavier on PWM outputs and encoder inputs than a general purpose (GA) part.
There will then be a digit to differentiate between several parts with the
same intended application.

Finally, there will be two digits indicating the pin count.

Thus, you have ten dollar names like PIC24FJ128GA010

The PIC32's aren't really PICs at all, and I get the impression from their
numbering that they may well be temporary.

By the way, as I mentioned before, if you are bound and determined to do
your programming in C, I would strongly suggest the 16 bit parts. Memory is
large enough that you can actually write C instead of some vague
approximation, the instruction set is far more friendly to C compilers than
the 8 bit parts, the compiler is free, and the parts cost barely more than
the 8 bit parts. Plus, some of the 16 bit peripherals are way cool.

72/73 de WB8RCR http://www.qsl.net/wb8rcr
didileydadidah QRP-L #1446 Code Warriors #35
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

>>

By the way, as I mentioned before, if you are bound and determined to do
your programming in C, I would strongly suggest the 16 bit parts. Memory is
large enough that you can actually write C instead of some vague
approximation, the instruction set is far more friendly to C compilers than
the 8 bit parts, the compiler is free, and the parts cost barely more than
the 8 bit parts. Plus, some of the 16 bit peripherals are way cool.

<<

That is very handy advice, thanks.

To be fair, though, I must tell you that I've done lots of small projects in
C on stuff like the 16F84 and the 12F509. Of course, these have been simple
applications, but it's still all done in C rather than assembler.

Having said that, I'm going to take a close look at the 16-bit parts.
Thanks again for that steer.

SteveT


(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

--- In p...@yahoogroups.com, "John J. McDonough, WB8RCR"
wrote:
>
> ...
>
> By the way, as I mentioned before, if you are bound and determined
> to do your programming in C, I would strongly suggest the 16 bit
> parts. Memory is large enough that you can actually write C instead
> of some vague approximation, the instruction set is far more
> friendly to C compilers than the 8 bit parts, the compiler is free,
> and the parts cost barely more than the 8 bit parts. Plus, some of
> the 16 bit peripherals are way cool.

John, what compiler is that, and where can we find it?

In past searches of the Microchip site, I must have missed it. Perhaps
I saw it, but didn't realize that there is no charge for it.

Best regards,
John
Germantown, Ohio
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

> John, what compiler is that, and where can we find it?
>
> In past searches of the Microchip site, I must have missed it. Perhaps
> I saw it, but didn't realize that there is no charge for it.

C18 for 16F's (8bit) (student edition)
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014

for PIC24 and dsPIC (student edition)
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010065

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Wouter beat me to it.

There is a difference between the 16 bit and 32 bit "Student Edition'. The
16 bit student edition has some optimizations that expire after 90 days. As
best I can tell, these optimizations don't make a huge difference for most
apps. I have heard some people indicate that in their particular space the
optimizations make a huge difference, but I've never encountered such an
app.

The 32 bit compiler has a code size limitation for the student edition.
Since you are tempted to do much more involved applications on the larger
PICs, this looks to me to be a show stopper, especially since the paid
version of the compiler is really expensive.

If money isn't a huge issue, I would suggest picking up the Explorer 16
board to experiment. It comes with a very fat 24F and 33F, has the typical
peripherals you find on an experimenter's board, and has a plug in connector
for perfboards with all the PIC pins brought to the connector. Microchip's
perfboards ar 3/$21, which I consider to be pretty reasonable, and are very
nice high quality boards with clear markings for all the PIC signals etc.
The Explorer 16 is like $160 or so, tho, so a little pricey for a hobbyist.
It has connectors for both the ICD2 and the PICkit2. It also has an 18F on
board for USB http://wb8rcr.multiply.com/photos/album/7/

72/73 de WB8RCR http://www.qsl.net/wb8rcr
didileydadidah QRP-L #1446 Code Warriors #35

----- Original Message -----
From: "Wouter van Ooijen"
To:
Sent: Saturday, September 20, 2008 9:56 AM
Subject: Re: [piclist] Re: Best PIC family for C programming
>> John, what compiler is that, and where can we find it?
>>
>> In past searches of the Microchip site, I must have missed it. Perhaps
>> I saw it, but didn't realize that there is no charge for it.
>
> C18 for 16F's (8bit) (student edition)
> http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014
>
> for PIC24 and dsPIC (student edition)
> http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010065
>
> --
>
> Wouter van Ooijen
>
> -- -------------------------------------------
> Van Ooijen Technische Informatica: www.voti.nl
> consultancy, development, PICmicro products
> docent Hogeschool van Utrecht: www.voti.nl/hvu
> ------------------------------------
>
> to unsubscribe, go to http://www.yahoogroups.com and follow the
> instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Actually C18 is for the 18F parts. MC doesn't have a C compiler for 16F
parts.

have fun,
DLC

Wouter van Ooijen wrote:
>> John, what compiler is that, and where can we find it?
>>
>> In past searches of the Microchip site, I must have missed it. Perhaps
>> I saw it, but didn't realize that there is no charge for it.
>
> C18 for 16F's (8bit) (student edition)
> http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014
>
> for PIC24 and dsPIC (student edition)
> http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010065
>

--
-------------------------------------------------
Dennis Clark TTT Enterprises
www.techtoystoday.com
-------------------------------------------------

------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

> Actually C18 is for the 18F parts. MC doesn't have a C compiler for 16F
> parts.

Sorry, Typo. For 14-bit cores I use the free HiTech C. Generates
horrible code, but who cares?

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

----- Original Message -----
From: "Wouter van Ooijen"
To:
Sent: Saturday, September 20, 2008 2:33 PM
Subject: Re: [piclist] Re: Best PIC family for C programming
> Sorry, Typo. For 14-bit cores I use the free HiTech C. Generates
> horrible code, but who cares?

Have you noticed how the various 14 bit compilers each generate horrible
code for some things, and really creative code for others. Seems like each
compiler is different. None seems to do everything well or poorly.

72/73 de WB8RCR http://www.qsl.net/wb8rcr
didileydadidah QRP-L #1446 Code Warriors #35
------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Hello guys...

I'm kinda new to the PIC world , and I'm designing an autopilot for an RC
model. I'm planning on using PICs. Do you have any suggestions on which
family to pick? All I learned was with the 16F family and assembler. Now
I'm upgrading to the 18F and C. I was thinking on using the 18F family on
the autopilot. Do you think this could handle or should I get a more
advanted family?

Thanks for the attention....
Rodrigo Basniak

=
=20
"rtstofer" =
=20
=20
> Para=
=20
Enviado Por: p...@yahoogroups.com =
=20
piclist@yahoogroups. cc=
=20
com =
=20
Assunto=
=20
[piclist] Re: Best PIC family =
=20
19/09/2008 12:07 for C programming =
=20
=
=20
=
=20
Favor responder a =
=20
piclist@yahoogroups. =
=20
com =
=20
=
=20
=
=20

=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
--- In p...@yahoogroups.com, Wouter van Ooijen wrote: =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> > What would you recommend as a sensible PIC family for programming =
=20=20=20=20=20=20=20=20=20
in C? =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Can not be answered without more details. If you want to use the full =
=20=20=20=20=20=20=20=20=20
> power of C (especially recursion) 12 and 14 bit cores are definitely =
=20=20=20=20=20=20=20=20=20
> out, probably 16-bit cores too. OTOH, for small projects a 10F200 might =
=20=20=20=20=20=20=20=20=20
> be the prefect choice. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> -- =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Wouter van Ooijen =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
Here I thought I was missing something about the 10F series so I =
=20=20=20=20=20=20=20=20=20
grabbed the datasheet. Clearly, the 10F200 isn't going to use C with =
=20=20=20=20=20=20=20=20=20
only 256 words of flash and 16 bytes of SRAM. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
The PIC18 series work pretty well with C and projects that do things =
=20=20=20=20=20=20=20=20=20
like USB and ethernet. I did a little project with one of the 18F =
=20=20=20=20=20=20=20=20=20
chips to interface a PS2 game controller to a PC by having SPI on one =
=20=20=20=20=20=20=20=20=20
side and USB on the other. It worked very well and the Microchip C18 =
=20=20=20=20=20=20=20=20=20
compiler is quite good (in that it works). =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
But you have to take this C thing in context. You can't use a PIC to =
=20=20=20=20=20=20=20=20=20
solve world hunger or predict weather patterns. But if you just want =
=20=20=20=20=20=20=20=20=20
to write code for the hardware gadgets and control things connected to =
=20=20=20=20=20=20=20=20=20
the pins, C will work on most of the 16F series. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
I have been using cc5x for years on 16F parts including my favorite, =
=20=20=20=20=20=20=20=20=20
the 16F88. Sure, the language is a subset and I can't put function =
=20=20=20=20=20=20=20=20=20
pointers in arrays and, true, it doesn't handle expressions very well, =
=20=20=20=20=20=20=20=20=20
but it works. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
I have also used PIC C Lite and I could be convinced it is a better =
=20=20=20=20=20=20=20=20=20
compiler. I just reach for cc5x more often. Go with what you know, I =
=20=20=20=20=20=20=20=20=20
guess. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
Richard =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=20
=20
"O emitente desta mensagem =E9 respons=E1vel por seu conte=FAdo e endere=E7=
amento. Cabe ao destinat=E1rio cuidar quanto ao tratamento adequado. Sem a =
devida autoriza=E7=E3o, a divulga=E7=E3o, a reprodu=E7=E3o, a distribui=E7=
=E3o ou qualquer outra a=E7=E3o em desconformidade com as normas internas d=
o Sistema Petrobras s=E3o proibidas e pass=EDveis de san=E7=E3o disciplinar=
, c=EDvel e criminal."
=20
"The sender of this message is responsible for its content and addressing. =
The receiver shall take proper care of it. Without due authorization, the p=
ublication, reproduction, distribution or the performance of any other act=
ion not conforming to Petrobras System internal policies and procedures is =
forbidden and liable to disciplinary, civil or criminal sanctions."
=20
"El emisor de este mensaje es responsable por su contenido y direccionamien=
to. Cabe al destinatario darle el tratamiento adecuado. Sin la debida autor=
izaci=F3n, su divulgaci=F3n, reproducci=F3n, distribuci=F3n o cualquier otr=
a acci=F3n no conforme a las normas internas del Sistema Petrobras est=E1n =
prohibidas y ser=E1n pasibles de sanci=F3n disciplinaria, civil y penal."

------------------------------------

to unsubscribe, go to http://www.yahoogroups.com and follow the instruction=
s



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Are you doing an autopilot (basically quite simple) or an
autonavigation (much moe complex). For the former almost any of the PICs
will do, although if you really must write in C then the 18 family is
better than the samller parts. If you're going autonav and are
insisitent on C then I'd personally favour one of the dsPICs or 24H
series dependng upon the peripheral mix you use for positional data. If
your using just GPS any old micro will do justr about. If you're using a
basic INS ie 5-6sensors then a 24H might do. If you're looking for a
really precise system then I would implem,ent multiple methods of
determning each type of axial data and then run all of these combination
s throuhg a variety of filters, which would take a dsPIC in C.

Cheers

Al

r...@petrobras.com.br wrote:

>Hello guys...
>
>I'm kinda new to the PIC world , and I'm designing an autopilot for an RC
>model. I'm planning on using PICs. Do you have any suggestions on which
>family to pick? All I learned was with the 16F family and assembler. Now
>I'm upgrading to the 18F and C. I was thinking on using the 18F family on
>the autopilot. Do you think this could handle or should I get a more
>advanted family?
>
>Thanks for the attention....
>Rodrigo Basniak
>
>
> "rtstofer"
> > > Para
> Enviado Por: p...@yahoogroups.com
> piclist@yahoogroups. cc
> com
> Assunto
> [piclist] Re: Best PIC family
> 19/09/2008 12:07 for C programming
>
>
> Favor responder a
> piclist@yahoogroups.
> com
>
>
>
>
>
>
>
> --- In p...@yahoogroups.com, Wouter van Ooijen wrote:
> >
> > > What would you recommend as a sensible PIC family for programming
> in C?
> >
> > Can not be answered without more details. If you want to use the full
> > power of C (especially recursion) 12 and 14 bit cores are definitely
> > out, probably 16-bit cores too. OTOH, for small projects a 10F200 might
> > be the prefect choice.
> >
> > --
> >
> > Wouter van Ooijen
>
> Here I thought I was missing something about the 10F series so I
> grabbed the datasheet. Clearly, the 10F200 isn't going to use C with
> only 256 words of flash and 16 bytes of SRAM.
>
> The PIC18 series work pretty well with C and projects that do things
> like USB and ethernet. I did a little project with one of the 18F
> chips to interface a PS2 game controller to a PC by having SPI on one
> side and USB on the other. It worked very well and the Microchip C18
> compiler is quite good (in that it works).
>
> But you have to take this C thing in context. You can't use a PIC to
> solve world hunger or predict weather patterns. But if you just want
> to write code for the hardware gadgets and control things connected to
> the pins, C will work on most of the 16F series.
>
> I have been using cc5x for years on 16F parts including my favorite,
> the 16F88. Sure, the language is a subset and I can't put function
> pointers in arrays and, true, it doesn't handle expressions very well,
> but it works.
>
> I have also used PIC C Lite and I could be convinced it is a better
> compiler. I just reach for cc5x more often. Go with what you know, I
> guess.
>
> Richard
>
>
>
>"O emitente desta mensagem é responsável por seu conteúdo e endereçamento. Cabe ao destinatário cuidar quanto ao tratamento adequado. Sem a devida autorização, a divulgação, a reprodução, a distribuição ou qualquer outra ação em desconformidade com as normas internas do Sistema Petrobras são proibidas e passíveis de sanção disciplinar, cível e criminal."
>
>"The sender of this message is responsible for its content and addressing. The receiver shall take proper care of it. Without due authorization, the publication, reproduction, distribution or the performance of any other action not conforming to Petrobras System internal policies and procedures is forbidden and liable to disciplinary, civil or criminal sanctions."
>
>"El emisor de este mensaje es responsable por su contenido y direccionamiento. Cabe al destinatario darle el tratamiento adecuado. Sin la debida autorización, su divulgación, reproducción, distribución o cualquier otra acción no conforme a las normas internas del Sistema Petrobras están prohibidas y serán pasibles de sanción disciplinaria, civil y penal."
>
>------------------------------------
>
>to unsubscribe, go to http://www.yahoogroups.com and follow the instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Hello,=20

PIC for autopilot. While taking about AHRS or gyro+accelerometer=20
based system i would also recomend you to go for DSPIC. If you go=20
for the one i have worked on like .. seprate Hight hold module with=20
gps and pressure sensor, A gps tracker plus angular rate based gyro=20
for turn control or horizon sensor based wing leveler. I had used=20
18F452. It was ok with these pics and they gave me good results in=20
CCS-C programming.

regards
Dani
--- In p...@yahoogroups.com, Onestone wrote:
>
> Are you doing an autopilot (basically quite simple) or an=20
> autonavigation (much moe complex). For the former almost any of=20
the PICs=20
> will do, although if you really must write in C then the 18 family=20
is=20
> better than the samller parts. If you're going autonav and are=20
> insisitent on C then I'd personally favour one of the dsPICs or=20
24H=20
> series dependng upon the peripheral mix you use for positional=20
data. If=20
> your using just GPS any old micro will do justr about. If you're=20
using a=20
> basic INS ie 5-6sensors then a 24H might do. If you're looking=20
for a=20
> really precise system then I would implem,ent multiple methods of=20
> determning each type of axial data and then run all of these=20
combination=20
> s throuhg a variety of filters, which would take a dsPIC in C.
>=20
> Cheers
>=20
> Al
>=20
> rodrigobasniak.plena@... wrote:
>=20
> >Hello guys...
> >
> >I'm kinda new to the PIC world , and I'm designing an autopilot=20
for an RC
> >model. I'm planning on using PICs. Do you have any suggestions on=20
which
> >family to pick? All I learned was with the 16F family and=20
assembler. Now
> >I'm upgrading to the 18F and C. I was thinking on using the 18F=20
family on
> >the autopilot. Do you think this could handle or should I get a=20
more
> >advanted family?
> >
> >Thanks for the attention....
> >Rodrigo Basniak
> >
> >
> >
>=20
> =
=20
=20=20=20=20=20=20=20
>=20
> "rtstofer" =
=20
=20=20=20=20=20=20=20
> >=20=20=20=20=20=20=20=20=20=20=20=20=20
=20
> >=20=20=20=20=20=20=20=20=20=20=20=20=20
> Para=20
> > Enviado Por: =
=20
p...@yahoogroups.com=20=20=20=20=20=20=20=20=20=20
> >=20=20=20=20=20=20=20=20=20=20=20=20=20
piclist@yahoogroups. cc=20
> >=20=20=20=20=20=20=20=20=20=20=20=20=20
com =
=20
>=20
> =
=20
Assunto=20
> > [piclist] Re: Best PIC=20
family=20=20=20=20
> > 19/09/2008 12:07 for C=20
programming=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20
> > Favor responder=20
a =
=20
> >=20=20=20=20=20=20=20=20=20=20=20=20=20
piclist@yahoogroups. =
=20
> >=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
com =
=20
>=20
> =
=20
=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20
> >
> >
> >
> >
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > --- In p...@yahoogroups.com, Wouter van Ooijen =20
wrote:=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > > > What would you recommend as a sensible PIC family for=20
programming=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > in=20
C? =
=20
=20=20=20=20=20=20=20=20=20=20=20
> >=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > > Can not be answered without more details. If you want to use=20
the full=20=20=20=20=20=20=20=20=20=20=20=20
> > > power of C (especially recursion) 12 and 14 bit cores are=20
definitely=20=20=20=20=20=20=20=20=20=20=20=20=20
> > > out, probably 16-bit cores too. OTOH, for small projects a=20
10F200 might=20=20=20=20=20=20=20=20=20=20
> > > be the prefect=20
choice. =
=20
> >=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > > --
=
=20
=20=20=20=20=20=20=20=20=20=20
> >=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > > Wouter van=20
Ooijen =
=20
=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > Here I thought I was missing something about the 10F series so=20
I=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > grabbed the datasheet. Clearly, the 10F200 isn't going to use C=20
with=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > only 256 words of flash and 16 bytes of=20
SRAM. =
=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > The PIC18 series work pretty well with C and projects that do=20
things=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > like USB and ethernet. I did a little project with one of the=20
18F=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > chips to interface a PS2 game controller to a PC by having SPI=20
on one=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > side and USB on the other. It worked very well and the Microchip=20
C18=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > compiler is quite good (in that it=20
works). =
=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > But you have to take this C thing in context. You can't use a=20
PIC to=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > solve world hunger or predict weather patterns. But if you just=20
want=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > to write code for the hardware gadgets and control things=20
connected to=20=20=20=20=20=20=20=20=20=20=20=20=20
> > the pins, C will work on most of the 16F=20
series. =
=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > I have been using cc5x for years on 16F parts including my=20
favorite,=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > the 16F88. Sure, the language is a subset and I can't put=20
function=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > pointers in arrays and, true, it doesn't handle expressions very=20
well,=20=20=20=20=20=20=20=20=20=20=20=20=20
> > but it=20
works. =
=20
=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > I have also used PIC C Lite and I could be convinced it is a=20
better=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > compiler. I just reach for cc5x more often. Go with what you=20
know, I=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >=20
guess. =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >=20
Richard =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>=20
> =
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >=20
> >
> >
> >=20
> >"O emitente desta mensagem =E9 respons=E1vel por seu conte=FAdo e=20
endere=E7amento. Cabe ao destinat=E1rio cuidar quanto ao tratamento=20
adequado. Sem a devida autoriza=E7=E3o, a divulga=E7=E3o, a reprodu=E7=E3o,=
a=20
distribui=E7=E3o ou qualquer outra a=E7=E3o em desconformidade com as norma=
s=20
internas do Sistema Petrobras s=E3o proibidas e pass=EDveis de san=E7=E3o=20
disciplinar, c=EDvel e criminal."
> >=20
> >"The sender of this message is responsible for its content and=20
addressing. The receiver shall take proper care of it. Without due=20
authorization, the publication, reproduction, distribution or the=20
performance of any other action not conforming to Petrobras System=20
internal policies and procedures is forbidden and liable to=20
disciplinary, civil or criminal sanctions."
> >=20
> >"El emisor de este mensaje es responsable por su contenido y=20
direccionamiento. Cabe al destinatario darle el tratamiento=20
adecuado. Sin la debida autorizaci=F3n, su divulgaci=F3n, reproducci=F3n,=20
distribuci=F3n o cualquier otra acci=F3n no conforme a las normas=20
internas del Sistema Petrobras est=E1n prohibidas y ser=E1n pasibles de=20
sanci=F3n disciplinaria, civil y penal."
> >
> >------------------------------------
> >
> >to unsubscribe, go to http://www.yahoogroups.com and follow the=20
instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Al,

I only saw your answer on the history of Dani's mail right now... =3D(
Yahoogroups trick me this time =3D\

I'm planning on doing an full autonavigatin system, with 6 degrees of
freedom. It will have a GPS, 3-axis accelerometer, 2 2-axis gyros, and
3-axis magnetometer.

The system doesn't have to be that much precise, its purposes is for
learning only, nothing commercial, so precision will not be a big issue.
But I'm planning on using kalman filter at least.

What would be the basic main difference from dsPIC and 24H?

Regards,
Rodrigo Basniak

Rodrigo Basniak
PETROBRAS / UN-REPAR / Engenharia / PLENA - Administrador de PDMS

=
=20
"Adnan" =
=20
=20
om> Para=
=20
Enviado Por: p...@yahoogroups.com =
=20
piclist@yahoogroups. cc=
=20
com =
=20
Assunto=
=20
[piclist] Re: Which family would=
=20
29/09/2008 03:49 suit better for this? =
=20
=
=20
=
=20
Favor responder a =
=20
piclist@yahoogroups. =
=20
com =
=20
=
=20
=
=20

=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
Hello, =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
PIC for autopilot. While taking about AHRS or gyro+accelerometer =
=20=20=20=20=20=20=20=20=20
based system i would also recomend you to go for DSPIC. If you go =
=20=20=20=20=20=20=20=20=20
for the one i have worked on like .. seprate Hight hold module with =
=20=20=20=20=20=20=20=20=20
gps and pressure sensor, A gps tracker plus angular rate based gyro =
=20=20=20=20=20=20=20=20=20
for turn control or horizon sensor based wing leveler. I had used =
=20=20=20=20=20=20=20=20=20
18F452. It was ok with these pics and they gave me good results in =
=20=20=20=20=20=20=20=20=20
CCS-C programming. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
regards =
=20=20=20=20=20=20=20=20=20
Dani =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
--- In p...@yahoogroups.com, Onestone wrote: =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Are you doing an autopilot (basically quite simple) or an =
=20=20=20=20=20=20=20=20=20
> autonavigation (much moe complex). For the former almost any of =
=20=20=20=20=20=20=20=20=20
the PICs =
=20=20=20=20=20=20=20=20=20
> will do, although if you really must write in C then the 18 family =
=20=20=20=20=20=20=20=20=20
is =
=20=20=20=20=20=20=20=20=20
> better than the samller parts. If you're going autonav and are =
=20=20=20=20=20=20=20=20=20
> insisitent on C then I'd personally favour one of the dsPICs or =
=20=20=20=20=20=20=20=20=20
24H =
=20=20=20=20=20=20=20=20=20
> series dependng upon the peripheral mix you use for positional =
=20=20=20=20=20=20=20=20=20
data. If =
=20=20=20=20=20=20=20=20=20
> your using just GPS any old micro will do justr about. If you're =
=20=20=20=20=20=20=20=20=20
using a =
=20=20=20=20=20=20=20=20=20
> basic INS ie 5-6sensors then a 24H might do. If you're looking =
=20=20=20=20=20=20=20=20=20
for a =
=20=20=20=20=20=20=20=20=20
> really precise system then I would implem,ent multiple methods of =
=20=20=20=20=20=20=20=20=20
> determning each type of axial data and then run all of these =
=20=20=20=20=20=20=20=20=20
combination =
=20=20=20=20=20=20=20=20=20
> s throuhg a variety of filters, which would take a dsPIC in C. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Cheers =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Al =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> rodrigobasniak.plena@... wrote: =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> >Hello guys... =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >I'm kinda new to the PIC world , and I'm designing an autopilot =
=20=20=20=20=20=20=20=20=20
for an RC =
=20=20=20=20=20=20=20=20=20
> >model. I'm planning on using PICs. Do you have any suggestions on =
=20=20=20=20=20=20=20=20=20
which =
=20=20=20=20=20=20=20=20=20
> >family to pick? All I learned was with the 16F family and =
=20=20=20=20=20=20=20=20=20
assembler. Now =
=20=20=20=20=20=20=20=20=20
> >I'm upgrading to the 18F and C. I was thinking on using the 18F =
=20=20=20=20=20=20=20=20=20
family on =
=20=20=20=20=20=20=20=20=20
> >the autopilot. Do you think this could handle or should I get a =
=20=20=20=20=20=20=20=20=20
more =
=20=20=20=20=20=20=20=20=20
> >advanted family? =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >Thanks for the attention.... =
=20=20=20=20=20=20=20=20=20
> >Rodrigo Basniak =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> "rtstofer" =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> Para =
=20=20=20=20=20=20=20=20=20
> > Enviado Por: =
=20=20=20=20=20=20=20=20=20
p...@yahoogroups.com =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
piclist@yahoogroups. cc =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
com =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
Assunto =
=20=20=20=20=20=20=20=20=20
> > [piclist] Re: Best PIC =
=20=20=20=20=20=20=20=20=20
family =
=20=20=20=20=20=20=20=20=20
> > 19/09/2008 12:07 for C =
=20=20=20=20=20=20=20=20=20
programming =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > Favor responder =
=20=20=20=20=20=20=20=20=20
a =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
piclist@yahoogroups. =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
com =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > --- In p...@yahoogroups.com, Wouter van Ooijen =
=20=20=20=20=20=20=20=20=20
wrote: =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > > What would you recommend as a sensible PIC family for =
=20=20=20=20=20=20=20=20=20
programming =
=20=20=20=20=20=20=20=20=20
> > in =
=20=20=20=20=20=20=20=20=20
C? =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > Can not be answered without more details. If you want to use =
=20=20=20=20=20=20=20=20=20
the full =
=20=20=20=20=20=20=20=20=20
> > > power of C (especially recursion) 12 and 14 bit cores are =
=20=20=20=20=20=20=20=20=20
definitely =
=20=20=20=20=20=20=20=20=20
> > > out, probably 16-bit cores too. OTOH, for small projects a =
=20=20=20=20=20=20=20=20=20
10F200 might =
=20=20=20=20=20=20=20=20=20
> > > be the prefect =
=20=20=20=20=20=20=20=20=20
choice. =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > -- =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > Wouter van =
=20=20=20=20=20=20=20=20=20
Ooijen =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > Here I thought I was missing something about the 10F series so =
=20=20=20=20=20=20=20=20=20
I =
=20=20=20=20=20=20=20=20=20
> > grabbed the datasheet. Clearly, the 10F200 isn't going to use C =
=20=20=20=20=20=20=20=20=20
with =
=20=20=20=20=20=20=20=20=20
> > only 256 words of flash and 16 bytes of =
=20=20=20=20=20=20=20=20=20
SRAM. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > The PIC18 series work pretty well with C and projects that do =
=20=20=20=20=20=20=20=20=20
things =
=20=20=20=20=20=20=20=20=20
> > like USB and ethernet. I did a little project with one of the =
=20=20=20=20=20=20=20=20=20
18F =
=20=20=20=20=20=20=20=20=20
> > chips to interface a PS2 game controller to a PC by having SPI =
=20=20=20=20=20=20=20=20=20
on one =
=20=20=20=20=20=20=20=20=20
> > side and USB on the other. It worked very well and the Microchip =
=20=20=20=20=20=20=20=20=20
C18 =
=20=20=20=20=20=20=20=20=20
> > compiler is quite good (in that it =
=20=20=20=20=20=20=20=20=20
works). =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > But you have to take this C thing in context. You can't use a =
=20=20=20=20=20=20=20=20=20
PIC to =
=20=20=20=20=20=20=20=20=20
> > solve world hunger or predict weather patterns. But if you just =
=20=20=20=20=20=20=20=20=20
want =
=20=20=20=20=20=20=20=20=20
> > to write code for the hardware gadgets and control things =
=20=20=20=20=20=20=20=20=20
connected to =
=20=20=20=20=20=20=20=20=20
> > the pins, C will work on most of the 16F =
=20=20=20=20=20=20=20=20=20
series. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > I have been using cc5x for years on 16F parts including my =
=20=20=20=20=20=20=20=20=20
favorite, =
=20=20=20=20=20=20=20=20=20
> > the 16F88. Sure, the language is a subset and I can't put =
=20=20=20=20=20=20=20=20=20
function =
=20=20=20=20=20=20=20=20=20
> > pointers in arrays and, true, it doesn't handle expressions very =
=20=20=20=20=20=20=20=20=20
well, =
=20=20=20=20=20=20=20=20=20
> > but it =
=20=20=20=20=20=20=20=20=20
works. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > I have also used PIC C Lite and I could be convinced it is a =
=20=20=20=20=20=20=20=20=20
better =
=20=20=20=20=20=20=20=20=20
> > compiler. I just reach for cc5x more often. Go with what you =
=20=20=20=20=20=20=20=20=20
know, I =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
guess. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
Richard =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >"O emitente desta mensagem =E9 respons=E1vel por seu conte=FAdo e =
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
endere=E7amento. Cabe ao destinat=E1rio cuidar quanto ao tratamento =
=20=20=20=20=20=20=20=20=20=20=20=20=20
adequado. Sem a devida autoriza=E7=E3o, a divulga=E7=E3o, a reprodu=E7=E3o=
, a=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
distribui=E7=E3o ou qualquer outra a=E7=E3o em desconformidade com as norm=
as=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
internas do Sistema Petrobras s=E3o proibidas e pass=EDveis de san=E7=E3o =
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
disciplinar, c=EDvel e criminal." =
=20=20=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >"The sender of this message is responsible for its content and =
=20=20=20=20=20=20=20=20=20
addressing. The receiver shall take proper care of it. Without due =
=20=20=20=20=20=20=20=20=20
authorization, the publication, reproduction, distribution or the =
=20=20=20=20=20=20=20=20=20
performance of any other action not conforming to Petrobras System =
=20=20=20=20=20=20=20=20=20
internal policies and procedures is forbidden and liable to =
=20=20=20=20=20=20=20=20=20
disciplinary, civil or criminal sanctions." =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >"El emisor de este mensaje es responsable por su contenido y =
=20=20=20=20=20=20=20=20=20
direccionamiento. Cabe al destinatario darle el tratamiento =
=20=20=20=20=20=20=20=20=20
adecuado. Sin la debida autorizaci=F3n, su divulgaci=F3n, reproducci=F3n, =
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
distribuci=F3n o cualquier otra acci=F3n no conforme a las normas =
=20=20=20=20=20=20=20=20=20=20=20=20=20
internas del Sistema Petrobras est=E1n prohibidas y ser=E1n pasibles de =
=20=20=20=20=20=20=20=20=20=20=20=20=20
sanci=F3n disciplinaria, civil y penal." =
=20=20=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >------------------------------------ =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >to unsubscribe, go to http://www.yahoogroups.com and follow the =
=20=20=20=20=20=20=20=20=20
instructions



(You need to be a member of piclist -- send a blank email to piclist-subscribe@yahoogroups.com )

Thanks Dani, second answer on dsPIC's side. I guess I'll just stop learning
the 18F and start learning the ds family.

Mine major concerning is about memory for the program, since I never did
anything that complex with PICs I don't have idea of how much memory should
I be looking for on the PICs. I'm writing some algorithms in Labview to
control a plane on X-Plane and test various approachs for the system. As
soon as I decide wich logic I'll be following I'll start writing to the
PIC, maybe by then I can have an idea of how much memory I'll be needing.

If I was using 18F family I was thinking on a PIC for the main program, 1
for filtering, processing and logging the sensor data and a 3rd one to
interpret and log gps data. Those 2 would transmit to the main PIC wich
would make the decisions. Any thoughts?

Regards,
Rodrigo Basniak

=
=20
"Adnan" =
=20
=20
om> Para=
=20
Enviado Por: p...@yahoogroups.com =
=20
piclist@yahoogroups. cc=
=20
com =
=20
Assunto=
=20
[piclist] Re: Which family would=
=20
29/09/2008 03:49 suit better for this? =
=20
=
=20
=
=20
Favor responder a =
=20
piclist@yahoogroups. =
=20
com =
=20
=
=20
=
=20

=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
Hello, =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
PIC for autopilot. While taking about AHRS or gyro+accelerometer =
=20=20=20=20=20=20=20=20=20
based system i would also recomend you to go for DSPIC. If you go =
=20=20=20=20=20=20=20=20=20
for the one i have worked on like .. seprate Hight hold module with =
=20=20=20=20=20=20=20=20=20
gps and pressure sensor, A gps tracker plus angular rate based gyro =
=20=20=20=20=20=20=20=20=20
for turn control or horizon sensor based wing leveler. I had used =
=20=20=20=20=20=20=20=20=20
18F452. It was ok with these pics and they gave me good results in =
=20=20=20=20=20=20=20=20=20
CCS-C programming. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
regards =
=20=20=20=20=20=20=20=20=20
Dani =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
--- In p...@yahoogroups.com, Onestone wrote: =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Are you doing an autopilot (basically quite simple) or an =
=20=20=20=20=20=20=20=20=20
> autonavigation (much moe complex). For the former almost any of =
=20=20=20=20=20=20=20=20=20
the PICs =
=20=20=20=20=20=20=20=20=20
> will do, although if you really must write in C then the 18 family =
=20=20=20=20=20=20=20=20=20
is =
=20=20=20=20=20=20=20=20=20
> better than the samller parts. If you're going autonav and are =
=20=20=20=20=20=20=20=20=20
> insisitent on C then I'd personally favour one of the dsPICs or =
=20=20=20=20=20=20=20=20=20
24H =
=20=20=20=20=20=20=20=20=20
> series dependng upon the peripheral mix you use for positional =
=20=20=20=20=20=20=20=20=20
data. If =
=20=20=20=20=20=20=20=20=20
> your using just GPS any old micro will do justr about. If you're =
=20=20=20=20=20=20=20=20=20
using a =
=20=20=20=20=20=20=20=20=20
> basic INS ie 5-6sensors then a 24H might do. If you're looking =
=20=20=20=20=20=20=20=20=20
for a =
=20=20=20=20=20=20=20=20=20
> really precise system then I would implem,ent multiple methods of =
=20=20=20=20=20=20=20=20=20
> determning each type of axial data and then run all of these =
=20=20=20=20=20=20=20=20=20
combination =
=20=20=20=20=20=20=20=20=20
> s throuhg a variety of filters, which would take a dsPIC in C. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Cheers =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> Al =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> rodrigobasniak.plena@... wrote: =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> >Hello guys... =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >I'm kinda new to the PIC world , and I'm designing an autopilot =
=20=20=20=20=20=20=20=20=20
for an RC =
=20=20=20=20=20=20=20=20=20
> >model. I'm planning on using PICs. Do you have any suggestions on =
=20=20=20=20=20=20=20=20=20
which =
=20=20=20=20=20=20=20=20=20
> >family to pick? All I learned was with the 16F family and =
=20=20=20=20=20=20=20=20=20
assembler. Now =
=20=20=20=20=20=20=20=20=20
> >I'm upgrading to the 18F and C. I was thinking on using the 18F =
=20=20=20=20=20=20=20=20=20
family on =
=20=20=20=20=20=20=20=20=20
> >the autopilot. Do you think this could handle or should I get a =
=20=20=20=20=20=20=20=20=20
more =
=20=20=20=20=20=20=20=20=20
> >advanted family? =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> >Thanks for the attention.... =
=20=20=20=20=20=20=20=20=20
> >Rodrigo Basniak =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> "rtstofer" =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> Para =
=20=20=20=20=20=20=20=20=20
> > Enviado Por: =
=20=20=20=20=20=20=20=20=20
p...@yahoogroups.com =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
piclist@yahoogroups. cc =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
com =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
Assunto =
=20=20=20=20=20=20=20=20=20
> > [piclist] Re: Best PIC =
=20=20=20=20=20=20=20=20=20
family =
=20=20=20=20=20=20=20=20=20
> > 19/09/2008 12:07 for C =
=20=20=20=20=20=20=20=20=20
programming =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > Favor responder =
=20=20=20=20=20=20=20=20=20
a =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
piclist@yahoogroups. =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
com =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > --- In p...@yahoogroups.com, Wouter van Ooijen =
=20=20=20=20=20=20=20=20=20
wrote: =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > > What would you recommend as a sensible PIC family for =
=20=20=20=20=20=20=20=20=20
programming =
=20=20=20=20=20=20=20=20=20
> > in =
=20=20=20=20=20=20=20=20=20
C? =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > Can not be answered without more details. If you want to use =
=20=20=20=20=20=20=20=20=20
the full =
=20=20=20=20=20=20=20=20=20
> > > power of C (especially recursion) 12 and 14 bit cores are =
=20=20=20=20=20=20=20=20=20
definitely =
=20=20=20=20=20=20=20=20=20
> > > out, probably 16-bit cores too. OTOH, for small projects a =
=20=20=20=20=20=20=20=20=20
10F200 might =
=20=20=20=20=20=20=20=20=20
> > > be the prefect =
=20=20=20=20=20=20=20=20=20
choice. =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > -- =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > > Wouter van =
=20=20=20=20=20=20=20=20=20
Ooijen =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > Here I thought I was missing something about the 10F series so =
=20=20=20=20=20=20=20=20=20
I =
=20=20=20=20=20=20=20=20=20
> > grabbed the datasheet. Clearly, the 10F200 isn't going to use C =
=20=20=20=20=20=20=20=20=20
with =
=20=20=20=20=20=20=20=20=20
> > only 256 words of flash and 16 bytes of =
=20=20=20=20=20=20=20=20=20
SRAM. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > The PIC18 series work pretty well with C and projects that do =
=20=20=20=20=20=20=20=20=20
things =
=20=20=20=20=20=20=20=20=20
> > like USB and ethernet. I did a little project with one of the =
=20=20=20=20=20=20=20=20=20
18F =
=20=20=20=20=20=20=20=20=20
> > chips to interface a PS2 game controller to a PC by having SPI =
=20=20=20=20=20=20=20=20=20
on one =
=20=20=20=20=20=20=20=20=20
> > side and USB on the other. It worked very well and the Microchip =
=20=20=20=20=20=20=20=20=20
C18 =
=20=20=20=20=20=20=20=20=20
> > compiler is quite good (in that it =
=20=20=20=20=20=20=20=20=20
works). =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > But you have to take this C thing in context. You can't use a =
=20=20=20=20=20=20=20=20=20
PIC to =
=20=20=20=20=20=20=20=20=20
> > solve world hunger or predict weather patterns. But if you just =
=20=20=20=20=20=20=20=20=20
want =
=20=20=20=20=20=20=20=20=20
> > to write code for the hardware gadgets and control things =
=20=20=20=20=20=20=20=20=20
connected to =
=20=20=20=20=20=20=20=20=20
> > the pins, C will work on most of the 16F =
=20=20=20=20=20=20=20=20=20
series. =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > I have been using cc5x for years on 16F parts including my =
=20=20=20=20=20=20=20=20=20
favorite, =
=20=20=20=20=20=20=20=20=20
> > the 16F88. Sure, the language is a subset and I can't put =
=20=20=20=20=20=20=20=20=20
function =
=20=20=20=20=20=20=20=20=20
> > pointers in arrays and, true, it doesn't handle expressions very =
=20=20=20=20=20=20=20=20=20
well, =
=20=20=20=20=20=20=20=20=20
> > but it =
=20=20=20=20=20=20=20=20=20
works. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > I have also used PIC C Lite and I could be convinced it is a =
=20=20=20=20=20=20=20=20=20
better =
=20=20=20=20=20=20=20=20=20
> > compiler. I just reach for cc5x more often. Go with what you =
=20=20=20=20=20=20=20=20=20
know, I =
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
guess. =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> > =
=20=20=20=20=20=20=20=20=20
Richard =
=20=20=20=20=20=20=20=20=20
=
=20=20=20=20=20=20=20=20=20
> =
=20=20=20=20=20=20=20=20=20
>