MIME-Version: 1.0
In-Reply-To: <56C4DEFF.5060709@freenet.de>
References: <56BDED97.5060308@freenet.de>
	<56BE0364.6070503@gmx.net>
	<56BE1134.7060205@freenet.de>
	<CAA8k23S4yT+pAfLGGaMH8XnPGa4WPNS4YZHJNKc4WQpydSsu9g@mail.gmail.com>
	<56BE1D9E.6060200@freenet.de>
	<CAA8k23SSF0vfOaRgwU_56yFmksVYLsZ-yfGpFvP9=-LEDCxHCA@mail.gmail.com>
	<56C4DEFF.5060709@freenet.de>
Date: Fri, 19 Feb 2016 15:12:53 +0000
Message-ID: <CAA8k23S1AEBcp2bE9wrpwZ=0ZJ+T-6ynAtLBVoED17gpgyztdg@mail.gmail.com>
From: Andy Talbot <andy.g4jnt@gmail.com>
To: rsgb_lf_group@yahoogroups.co.uk
Cc: rsgb_lf_group@blacksheep.org
Subject: Re: [rsgb_lf_group] Re: LF: PIC-based GPSDO with A/D converter /
 supported serial baudrates ?
Content-Type: multipart/alternative; boundary=047d7bf0d2dec8bdeb052c20eada
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

--047d7bf0d2dec8bdeb052c20eada
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I modified an existing module containing a 16F688 (a 14 pin PIC with UART
and A/D converter  very useful chip) and SP485 driver.
Wrote some code to send all the letters of the alphabet and the numbers and
[formatting- something immediately recognisable on a screen at various fast
baud rates.    The characters are sent contiguously with absolutely no gaps
between serial words   With a 16MHz clocked chip, the maximum baud rate is
1MB/s

Using an FTDI RS485 module and my existing  serial port monitor written in
Visual Basic , I then tested at various speeds.   Initially I had the UART
set for 1 stop bit, and things began to go a bit flakily with errors even
at 250000 baud, then very wrong at  500k and 1M locked up my monitor
prog. completely!

Then I realised that  there was no leeway for clock slippage having just
one stop bit,  and wondered how to set the PIC's USART for two stop bits.
Finally realised the 9 bit data option was the way to do it, with the 9 bit
=3D '1'

The result is perfect!   Watching the letters of the alphabet and
numbers whip up the screen there are no errors to be seen at rates up to
the maximum with this crystal - 1MB/s.   8 bit data with one start and two
stop =3D 11 symbols per byte so nearly 91000 bytes per second.   So 12 or
even possibly 14 bit data could be sent (with some framing) at 45kS/s.
16 bit at 30kS/s or a bit more with careful format frigging

I'm also pleased to discover that the serial terminal programme, 'PUTTY'
allows 1Mbaud to be set and again gives perfect reception at that speed.

So it looks like the FTDI chipset gives us a decent easy to implement
interface at speeds sufficient for our purposes.

The spec'ed maximum the 16F688 can run at is 20MHz, so even if that were
thrashed it couldn't reach the next speed option the FTDI232R can go at,
which is 3MBaud.   Your faster device with multiplier may manage that
though...   if it uses the same USART hardware as the 16F688.  You will
need to clock at 48MHz to get 3Mbaud

Andy  G4JNT


  (In all my bit banging RSxxx implementation I have always used two stop
bits, so never thought that the USARt would be implementing this by default

On 17 February 2016 at 20:58, Wolfgang B=C3=BCscher dl4yhf@freenet.de
[rsgb_lf_group] <rsgb_lf_group@yahoogroups.co.uk> wrote:

>
>
> Ok then - so the FTDI-chip based interfaces are the ones to use.
> In the meantime I got the serial port adapter working at 460800 bits per
> second (where the communication with the PIC16F1783 looks good) but not a=
t
> 500000 bits/sec (where the PIC could realize the bitrate without any
> error). The rise- and fall time of the RS232 level converters seem to be
> different, so when sending a loop of 0x55 bytes the '0101010' pattern
> doesn't look like a square wave with 50 % duty cycle at all.
>
>

--047d7bf0d2dec8bdeb052c20eada
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I modified an existing module containing a 16F688 (a =
14 pin=C2=A0PIC with UART and A/D converter=C2=A0 very useful chip) and SP4=
85 driver. </div><div>Wrote some code to send all the letters of the alphab=
et and the numbers and [formatting- something immediately recognisable on a=
 screen at various fast baud rates.=C2=A0=C2=A0=C2=A0 The characters are se=
nt contiguously=C2=A0with absolutely no gaps between serial words=C2=A0=C2=
=A0 With a 16MHz clocked chip, the maximum baud rate is=C2=A0 1MB/s</div><d=
iv><br></div><div>Using an FTDI RS485 module and my existing=C2=A0 serial p=
ort monitor written in Visual Basic , I then=C2=A0tested at various speeds.=
=C2=A0=C2=A0 Initially I had the UART set for 1 stop bit, and things began =
to go a bit flakily=C2=A0with errors even at 250000 baud, then very wrong a=
t=C2=A0 500k and 1M locked up my monitor prog.=C2=A0completely!</div><div><=
br></div><div>Then I realised that=C2=A0 there was no leeway for clock slip=
page having just one stop bit, =C2=A0and wondered how to set the PIC&#39;s =
USART for two stop bits.=C2=A0 Finally realised=C2=A0the 9 bit data option=
=C2=A0was the way to do it, with the 9 bit =3D &#39;1&#39;=C2=A0 </div><div=
><br></div><div>The result is perfect!=C2=A0=C2=A0 Watching the letters of =
the alphabet and numbers=C2=A0whip up the screen there are no errors to be =
seen at rates up to the maximum with this crystal - 1MB/s.=C2=A0=C2=A0 8 bi=
t data with one start and two stop =3D 11 symbols per byte so nearly 91000 =
bytes per second.=C2=A0=C2=A0 So 12 or even possibly 14=C2=A0bit data could=
 be sent (with some framing) at 45kS/s.=C2=A0=C2=A0=C2=A0 16 bit at 30kS/s =
or a bit more with careful format frigging</div><div><br></div><div>I&#39;m=
 also pleased to=C2=A0discover that the serial terminal programme, &#39;PUT=
TY&#39;=C2=A0 allows 1Mbaud to be set and again gives perfect reception at =
that speed.</div><div><br></div><div>So it looks like the FTDI chipset give=
s us a decent easy to implement interface at speeds sufficient=C2=A0for our=
 purposes.</div><div><br></div><div>The spec&#39;ed maximum the 16F688 can =
run at is 20MHz, so even=C2=A0if that=C2=A0were thrashed it couldn&#39;t re=
ach the next speed=C2=A0option the FTDI232R can go at, which is 3MBaud.=C2=
=A0=C2=A0 Your faster device with multiplier may manage that though...=C2=
=A0=C2=A0 if it uses the same USART hardware as the 16F688.=C2=A0 You will =
need to clock at 48MHz to get 3Mbaud</div><div><br></div><div>Andy=C2=A0 G4=
JNT</div><div><br></div><div><br></div><div>=C2=A0 (In all my bit banging R=
Sxxx implementation I have always used two stop bits, so never thought that=
 the USARt would be implementing this by default<br></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On 17 February 2016 at 20:58, Wolf=
gang B=C3=BCscher <a href=3D"mailto:dl4yhf@freenet.de">dl4yhf@freenet.de</a=
> [rsgb_lf_group] <span dir=3D"ltr">&lt;<a href=3D"mailto:rsgb_lf_group@yah=
oogroups.co.uk" target=3D"_blank">rsgb_lf_group@yahoogroups.co.uk</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-wi=
dth:1px;border-left-style:solid">


<u></u>


=20
<div style=3D"background-color:rgb(255,255,255)">
<span>=C2=A0</span>


<div>
  <div>


    <div>
     =20
     =20
      <p>
 =20
 =20
    Ok then - so the FTDI-chip based interfaces are the ones to use.<br>
    In the meantime I got the serial port adapter working at 460800 bits
    per second (where the communication with the PIC16F1783 looks good)
    but not at 500000 bits/sec (where the PIC could realize the bitrate
    without any error). The rise- and fall time of the RS232 level
    converters seem to be different, so when sending a loop of 0x55
    bytes the &#39;0101010&#39; pattern doesn&#39;t look like a square wave=
 with 50
    % duty cycle at all.<br>
=C2=A0=C2=A0=C2=A0 </p></div></div></div></div></blockquote></div><br></div=
></div>

--047d7bf0d2dec8bdeb052c20eada--