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
"Adnan"
om> Para
Enviado Por: p...
piclist@yahoogroups. cc
com
Assunto
[piclist] Re: Which family would
29/09/2008 03:49 suit better for this?
Favor responder a
piclist@yahoogroups.
com
Hello,
PIC for autopilot. While taking about AHRS or gyro+accelerometer
based system i would also recomend you to go for DSPIC. If you go
for the one i have worked on like .. seprate Hight hold module with
gps and pressure sensor, A gps tracker plus angular rate based gyro
for turn control or horizon sensor based wing leveler. I had used
18F452. It was ok with these pics and they gave me good results in
CCS-C programming.
regards
Dani
--- In p..., Onestone wrote:
>
> 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
>
> rodrigobasniak.plena@... 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...
> >
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..., 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 responsel por seu conteo e
enderemento. Cabe ao destinatio cuidar quanto ao tratamento
adequado. Sem a devida autorizao, a divulgao, a reproduo, a
distribuio ou qualquer outra ao em desconformidade com as normas
internas do Sistema Petrobras s proibidas e passeis de sano
disciplinar, cel 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, su divulgaci, reproducci,
distribuci o cualquier otra acci no conforme a las normas
internas del Sistema Petrobras est prohibidas y ser pasibles de
sanci disciplinaria, civil y penal."
> >
> >
> >
> >to unsubscribe, go to http://www.yahoogroups.com and follow the
instructions