DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=j+aWpR2wTZCXfWSxtG9I8fpMn40T2XLncsxO1ulvutWL/PyVWfhmkkvlVB5pezsCI0
         EeoO7Zvn3ucpe79+27bqsp0DHZRmX0YThHLkM/gN2vB6Rqvjiyl16ZxuvLbSwtmdlDgh
         y2akZY7Gw+5IwffQh4hRHWZcWZHBWfLIuQTP0=
MIME-Version: 1.0
In-Reply-To: <4D36FF68.2060009@iup.uni-heidelberg.de>
References: <4D36FF68.2060009@iup.uni-heidelberg.de>
Date: Wed, 19 Jan 2011 17:39:15 +0000
Message-ID: <AANLkTinkUpRpQBUjT11k2nYEerS38o16sKp1JocbE+NS@mail.gmail.com>
From: Andy Talbot <andy.g4jnt@gmail.com>
To: rsgb_lf_group@blacksheep.org
DomainKey-Status: good (testing) 
Subject: Re: LF: Pic or Atmel?
Content-Type: multipart/alternative; boundary=00221534c927ed7148049a367e7a
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


--00221534c927ed7148049a367e7a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Well, I know nothing about the Atmel aprat from teh fact that is exists :-=
)
There are plenty that love the range and won't touch PICs, but as you say
its like Linux / Windows - never the twain...

Everything you want to do is quite straightforward and can all be done by
the low end 16F series of PICs.  The 16F628 is a good workhorse to start
with, the 16F819 is much the same, but has an on-board 4 channel 10 bit
A/D.  The 16F870 is again much the same but has more I/O lines.

Another of my favourites is the 12F629 and the similar 12F675 with 10 bit
A/D converter.- both very cheap, especially in bulk.   Same code as the 16=
F
family, but only 8 pins,and internal oscillator (with oscilator calibratio=
n
facility) making them ideal for simple standalone tiny modules and a
for jobs like fire-and-go-to-sleep-doing-nothing-more synthesizer
programming.

There's a lot of 16F and 12f family source code on my website (people have
said I've given away too much code over the years)
http://www.g4jnt.com/pics.htm

For programming its difficult to beat the Microchip PicKit programmer - if
you shop around its usually possible to get it bundled with a development
board for one of the more upmarket device- sometimes at a bargai
nprice.   The PicKit is upwards compatible and will programm all tke highe=
r
range and DSPPic as well.

I have ONLY EVER programmed in native assembler - everyone says its old ha=
t,
complicated etc, but it isn't.  And gives you far more versaility that usi=
ng
C or Basic PIC dialects.   And in 15 years of PIC programming have built=
 up
a good set of libraries that do everything a high level language can
offer.

Andy
www.g4jnt.com





2011/1/19 Stefan Sch=E4fer <Stefan.Schaefer@iup.uni-heidelberg.de>

> Dear group, especially Andy/G4JNT,
>
> Maybe a little out of topic but very useful for LF/VLF devices: Programm=
ing
> microcontrollers.
>
> Before some years i worked with some PIC controllers, assembler. But in=
 the
> German ham radio newspaper you rather find circuit examples programmed=
 on an
> Atmel device. Now i want to buy some software and programming devices fo=
r
> microcontrollers and asking myselfe what i should choose, Pic or Atmel.
> Maybe its a question like Windows or Linux? ;-)
>
> My question would be what is the difference and the
> advantages/disadvantages. Is there a preferred device for practical
> purposes?
>
> Examples for what i want to do with a Pic or At,mel
>
> -Programming a DDS VFO
> -A/D / D/A conversion of LF/VLF signals
> - Programming a beacon TX for 8970 Hz, directly driving a psuh-pull FET
> stage
> - Maybe a DCF-77 RX for generating a reference signal?
> -Regulators for battery charging
> -combinations of the above
>
> and and and
>
> I would be thankful for useful comments and hints.
>
> 73, Stefan/DK7FC
>
>
>
>

--00221534c927ed7148049a367e7a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Well, I know nothing about the Atmel aprat from teh fact that is exis=
ts :-)</div>
<div>There are plenty that love=A0the range=A0and won&#39;t touch PICs, bu=
t as you say its like Linux / Windows - never=A0the twain...</div>
<div><br>Everything you want to do is quite straightforward and=A0can all=
 be done by the low end 16F series of PICs.=A0 The 16F628 is a good workho=
rse to start with, the 16F819 is much the same, but has an on-board 4 chan=
nel 10 bit A/D.=A0 The 16F870 is again much the same but has more I/O line=
s.=A0=A0 </div>

<div>=A0</div>
<div>Another of my favourites is the 12F629 and the similar 12F675 with 10=
 bit A/D converter.- both very cheap, especially in bulk.=A0=A0 Same code=
 as the 16F family, but only 8 pins,and internal oscillator (with oscilato=
r calibration facility)=A0making them ideal for simple standalone tiny mod=
ules and a for=A0jobs like fire-and-go-to-sleep-doing-nothing-more=A0synth=
esizer programming.=A0=A0 </div>

<div>=A0</div>
<div>There&#39;s a lot of 16F and 12f family source code on my website (pe=
ople have said I&#39;ve given away too much code over the years) <br><a hr=
ef=3D"http://www.g4jnt.com/pics.htm">http://www.g4jnt.com/pics.htm</a></di=
v>

<div>=A0</div>
<div>For programming its difficult to beat the Microchip PicKit programmer=
 - if you shop around its usually possible to get it bundled with a develo=
pment board for one of the more upmarket device- sometimes at a bargai npr=
ice.=A0=A0=A0The PicKit is upwards compatible and will programm all tke hi=
gher range and=A0DSPPic as well.</div>

<div>=A0</div>
<div>I have ONLY EVER programmed in native assembler - everyone says its=
 old hat, complicated etc, but it isn&#39;t.=A0 And gives you far more ver=
saility that using C or Basic PIC dialects.=A0=A0 And in 15 years of PIC=
 programming have built up a=A0good set of libraries=A0that do everything=
 a high level language can offer.=A0=A0 </div>

<div>=A0</div>
<div>Andy </div>
<div><a href=3D"http://www.g4jnt.com/">www.g4jnt.com</a></div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div class=3D"gmail_quote">2011/1/19 Stefan Sch=E4fer <span dir=3D"ltr">&l=
t;<a href=3D"mailto:Stefan.Schaefer@iup.uni-heidelberg.de">Stefan.Schaefer=
@iup.uni-heidelberg.de</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8e=
x; PADDING-LEFT: 1ex" class=3D"gmail_quote">Dear group, especially Andy/G4=
JNT,<br><br>Maybe a little out of topic but very useful for LF/VLF devices=
: Programming microcontrollers.<br>
<br>Before some years i worked with some PIC controllers, assembler. But=
 in the German ham radio newspaper you rather find circuit examples progra=
mmed on an Atmel device. Now i want to buy some software and programming=
 devices for microcontrollers and asking myselfe what i should choose, Pic=
 or Atmel. Maybe its a question like Windows or Linux? ;-)<br>
<br>My question would be what is the difference and the advantages/disadva=
ntages. Is there a preferred device for practical purposes?<br><br>Example=
s for what i want to do with a Pic or At,mel<br><br>-Programming a DDS VFO=
<br>
-A/D / D/A conversion of LF/VLF signals<br>- Programming a beacon TX for=
 8970 Hz, directly driving a psuh-pull FET stage<br>- Maybe a DCF-77 RX fo=
r generating a reference signal?<br>-Regulators for battery charging<br>-c=
ombinations of the above<br>
<br>and and and<br><br>I would be thankful for useful comments and hints.<=
br><br>73, Stefan/DK7FC<br><br><br><br></blockquote></div><br>

--00221534c927ed7148049a367e7a--