Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Thread

testing uart using atmega16

testing uart using atmega16

2005-12-12 by spotwl8

hi!

i'm new here. i need your help. i'm currently having a project on 
avr. i would like to communicate data from pc to microcontroller. 
the transmitter is connected to the pc through serial port. and the 
receiver is connected to the microcontroller. I used atmega16.

when i programmed the atmega16, I tested it. when i applied source 
to it, after a while, the leds light up..it formed different 
combination.so i assumed that the receiver receive data. however the 
problem is there is no transmitter yet. here's the link for my code:

 http://h1.ripway.com/greenadik_101/uarttest16.c

so i edited my program. i added an end character. here's the code:

 http://h1.ripway.com/greenadik_101/uart16.c

after that, leds doesnt light up. so i send data from pc. the 
problem is it doesn't work at all.

is my program the problem?

Re: testing uart using atmega16

2005-12-12 by spotwl8

hello thanks for the reply! yes I'm using an RF transceiver operates 
at 433MHz specifically BIM2 of radiometrix. I verified it already and 
its working.. I just used com port toolkit for sending data from pc. 
also yes I make sure that baud rate/parity/ stopbits are the same.

--- In AVR-Chat@yahoogroups.com, Zack Widup <w9sz@p...> wrote:
>
> First off, I'm not sure about your configuration.  When you say the 
> transmitter is connected to the computer's serial port and the 
receiver is 
> connected to the AVR, what kind of transmitter and receiver are you 
> using? Do you mean RF transmitter and receiver?  What frequency? 
Have you 
> verified that they are working together? What kind of program are 
you 
Show quoted textHide quoted text
> using in the computer to generate the baud rate? Are the sending and 
> receiving ends both set for the same baud rate/parity/stop bits?
> 
> Zack
>

Re: testing uart using atmega16

2005-12-12 by spotwl8

hello thanks for the reply! yes I'm using an RF transceiver operates 
at 433MHz specifically BIM2 of radiometrix. I verified it already and 
its working.. I just used com port toolkit for sending data from pc. 
also yes I make sure that baud rate/parity/ stopbits are the same.

--- In AVR-Chat@yahoogroups.com, Zack Widup <w9sz@p...> wrote:
>
> First off, I'm not sure about your configuration.  When you say the 
> transmitter is connected to the computer's serial port and the 
receiver is 
> connected to the AVR, what kind of transmitter and receiver are you 
> using? Do you mean RF transmitter and receiver?  What frequency? 
Have you 
> verified that they are working together? What kind of program are 
you 
Show quoted textHide quoted text
> using in the computer to generate the baud rate? Are the sending and 
> receiving ends both set for the same baud rate/parity/stop bits?
> 
> Zack
>

Re: testing uart using atmega16

2005-12-12 by spotwl8

hello thanks for the reply! yes I'm using an RF transceiver operates 
at 433MHz specifically BIM2 of radiometrix. I verified it already and 
its working.. I just used com port toolkit for sending data from pc. 
also yes I make sure that baud rate/parity/ stopbits are the same.

--- In AVR-Chat@yahoogroups.com, Zack Widup <w9sz@p...> wrote:
>
> First off, I'm not sure about your configuration.  When you say the 
> transmitter is connected to the computer's serial port and the 
receiver is 
> connected to the AVR, what kind of transmitter and receiver are you 
> using? Do you mean RF transmitter and receiver?  What frequency? 
Have you 
> verified that they are working together? What kind of program are 
you 
Show quoted textHide quoted text
> using in the computer to generate the baud rate? Are the sending and 
> receiving ends both set for the same baud rate/parity/stop bits?
> 
> Zack
>

Re: [AVR-Chat] testing uart using atmega16

2005-12-12 by Zack Widup

First off, I'm not sure about your configuration.  When you say the 
transmitter is connected to the computer's serial port and the receiver is 
connected to the AVR, what kind of transmitter and receiver are you 
using? Do you mean RF transmitter and receiver?  What frequency? Have you 
verified that they are working together? What kind of program are you 
using in the computer to generate the baud rate? Are the sending and 
receiving ends both set for the same baud rate/parity/stop bits?

Zack
Show quoted textHide quoted text
On Mon, 12 Dec 2005, spotwl8 wrote:

> hi!
> 
> i'm new here. i need your help. i'm currently having a project on
> avr. i would like to communicate data from pc to microcontroller.
> the transmitter is connected to the pc through serial port. and the
> receiver is connected to the microcontroller. I used atmega16.
> 
> when i programmed the atmega16, I tested it. when i applied source
> to it, after a while, the leds light up..it formed different
> combination.so i assumed that the receiver receive data. however the
> problem is there is no transmitter yet. here's the link for my code:
> 
> http://h1.ripway.com/greenadik_101/uarttest16.c
> 
> so i edited my program. i added an end character. here's the code:
> 
> http://h1.ripway.com/greenadik_101/uart16.c
> 
> after that, leds doesnt light up. so i send data from pc. the
> problem is it doesn't work at all.
> 
> is my program the problem?
>

Re: [AVR-Chat] Re: testing uart using atmega16

2005-12-12 by Zack Widup

OK, thanks.  Is there any way you can hook up the mega16 directly to the 
computer with an RS-232 level converter or some such?

I don't write programs in C at this point, I do them all in assmebler.  
But I like to do them in stages to verify each part is working.  For 
instance, I wrote a program for the mega8 that controls an AD9835 DDS 
chip.  I first wrote a program just to send a fixed frequency to the DDS 
chip to make sure that part of the program was working.  Then I added in 
the serial comm routines.  It's a half-duplex routine, so I made it send a 
sign-on message to the computer when the mega8 is reset, i.e. "AVR DDS 
controller v. 1.0". When I see that appear on the computer screen I know 
that part is working properly.

Then I add in the transmit/receive routines without interrupts and make 
sure they are working.  Once that is established, I add in the interrupts.

That way I know just what part of the program is faulty.

Zack
Show quoted textHide quoted text
On Mon, 12 Dec 2005, spotwl8 wrote:

> hello thanks for the reply! yes I'm using an RF transceiver operates
> at 433MHz specifically BIM2 of radiometrix. I verified it already and
> its working.. I just used com port toolkit for sending data from pc.
> also yes I make sure that baud rate/parity/ stopbits are the same.
>

Re: [AVR-Chat] Re: testing uart using atmega16

2005-12-12 by David Kelly

On Mon, Dec 12, 2005 at 10:00:43AM -0600, Zack Widup wrote:
> OK, thanks.  Is there any way you can hook up the mega16 directly to the 
> computer with an RS-232 level converter or some such?
> 
> On Mon, 12 Dec 2005, spotwl8 wrote:
> 
> > hello thanks for the reply! yes I'm using an RF transceiver operates
> > at 433MHz specifically BIM2 of radiometrix. I verified it already and
> > its working.. I just used com port toolkit for sending data from pc.
> > also yes I make sure that baud rate/parity/ stopbits are the same.

As Zack says, only test one thing at a time. Make the async serial work,
*then* attach the RF.

The BIM2 is typical of low cost data transceivers in that it simply
tries to replicate the logic state on its local RxD pin as found on the
distant TxD pin. It knows nothing of what is trying to be transmitted.
It doesn't attempt to reclock the data. As a result your data can be
skewed beyond the ability of a hardware UART to recover.

At the very least you will need robust error detection in your data
packets.

Serious RF data transmission is done with synchronous bit protocols
rather than asynchronous.

-- 
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.

Re: testing uart using atmega16

2005-12-14 by sheena licarte

Mr. David and Mr. Zack thanks for the advice. i'll try to test things one at a time. by the way is it possible to connect avr directly to the rs232 level converter such as max 232 and then to pc?

David Kelly wrote:
On Mon, Dec 12, 2005 at 10:00:43AM -0600, Zack Widup wrote:
> OK, thanks. Is there any way you can hook up the mega16 directly to the
> computer with an RS-232 level converter or some such?
>
> On Mon, 12 Dec 2005, spotwl8 wrote:
>
> > hello thanks for the reply! yes I'm using an RF transceiver operates
> > at 433MHz specifically BIM2 of radiometrix. I verified it already and
> > its working.. I just used com port toolkit for sending data from pc.
> > also yes I make sure that baud rate/parity/ stopbits are the same.

As Zack says, only test one thing at a time. Make the async serial work,
*then* attach the RF.

The BIM2 is typical of low cost data transceivers in that it simply
tries to replicate the logic state on its local RxD pin as found on the
distant TxD pin. It knows nothing of what is trying to be transmitted.
It doesn't attempt to reclock the data. As a result your data can be
skewed beyond the ability of a hardware UART to recover.

At the very least you will need robust error detection in your data
packets.

Serious RF data transmission is done with synchronous bit protocols
rather than asynchronous.

--
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.

Yahoo! Shopping
Find Great Deals on Holiday Gifts at Yahoo! Shopping

Re: [AVR-Chat] Re: testing uart using atmega16

2005-12-14 by Zack Widup

On Tue, 13 Dec 2005, sheena licarte wrote:

> Mr. David and Mr. Zack thanks for the advice. i'll  try to test things 
> one at a time. by the way is it possible to connect  avr directly to the 
> rs232 level converter such as max 232 and then to  pc?
> 

Yes, the MAX232 series all have TTL inputs/outputs for the device and 
RS-232 level inputs/outputs for the line.  They are very easy to use.

Zack

Re: [AVR-Chat] Re: testing uart using atmega16

2005-12-14 by Ralph Hilton

On Tue, 13 Dec 2005 23:11:14 -0600 (CST) you wrote:

>On Tue, 13 Dec 2005, sheena licarte wrote:
>
>> Mr. David and Mr. Zack thanks for the advice. i'll  try to test things 
>> one at a time. by the way is it possible to connect  avr directly to the 
>> rs232 level converter such as max 232 and then to  pc?
>> 
>
>Yes, the MAX232 series all have TTL inputs/outputs for the device and 
>RS-232 level inputs/outputs for the line.  They are very easy to use.

www.olimex.com sell a variety of AVR boards for which they publish the schematics. They
show the connections for a max232 and other RS232 interfaces.
--
Ralph Hilton
http://www.ralphhilton.org
C-Meter: http://www.cmeter.org
FZAOINT http://www.fzaoint.net

PC COM Ports - was: testing uart using atmega16

2005-12-14 by Bruce Parham

Zack Widup wrote:

> On Tue, 13 Dec 2005, sheena licarte wrote:
> 
> 
>>Mr. David and Mr. Zack thanks for the advice. i'll  try to test things 
>>one at a time. by the way is it possible to connect  avr directly to the 
>>rs232 level converter such as max 232 and then to  pc?
>>
> 
> 
> Yes, the MAX232 series all have TTL inputs/outputs for the device and 
> RS-232 level inputs/outputs for the line.  They are very easy to use.
> 
> Zack

Just a little heads up about comm ports on PC's. The RS-232 spec defines
valid levels for the data line to be > +3V and < -3v. So you would think
a MAX232 type device running on 3.3V and outputting a +/-6V signal would work
just fine with a PC. Not so... The PC folks (maybe IBM 20 years ago?) decided
to attenuate the inputs by a factor of 2, setting the switching thresholds
at +/- 6v.

This bit me in the rear a couple years back when I fired up a new prototype
board and connected it to my desktop Dell box. Comm was dead but the scope said
it was working... A bit of fiddling with a function generator revealed that all
the desktop and laptop Dells and Sony boxes needed about +/- 6.2V to switch!

Just by luck I found an old HP desktop that switched at +/- 5.5V. That one is still
connected to my prototype.

Bruce

Re: [AVR-Chat] PC COM Ports - was: testing uart using atmega16

2005-12-14 by Ralph Hilton

On Wed, 14 Dec 2005 07:42:58 -0800 you wrote:

>Zack Widup wrote:
>
>> On Tue, 13 Dec 2005, sheena licarte wrote:
>> 
>> 
>>>Mr. David and Mr. Zack thanks for the advice. i'll  try to test things 
>>>one at a time. by the way is it possible to connect  avr directly to the 
>>>rs232 level converter such as max 232 and then to  pc?
>>>
>> 
>> 
>> Yes, the MAX232 series all have TTL inputs/outputs for the device and 
>> RS-232 level inputs/outputs for the line.  They are very easy to use.
>> 
>> Zack
>
>Just a little heads up about comm ports on PC's. The RS-232 spec defines
>valid levels for the data line to be > +3V and < -3v. So you would think
>a MAX232 type device running on 3.3V and outputting a +/-6V signal would work
>just fine with a PC. Not so... The PC folks (maybe IBM 20 years ago?) decided
>to attenuate the inputs by a factor of 2, setting the switching thresholds
>at +/- 6v.
>
>This bit me in the rear a couple years back when I fired up a new prototype
>board and connected it to my desktop Dell box. Comm was dead but the scope said
>it was working... A bit of fiddling with a function generator revealed that all
>the desktop and laptop Dells and Sony boxes needed about +/- 6.2V to switch!
>
>Just by luck I found an old HP desktop that switched at +/- 5.5V. That one is still
>connected to my prototype.

Another option available if you have a suitable program on the PC is to power the PC side
of an interface from the RTS/DTR lines. In one application I set RTS and clear DTR and use
a couple of optocouplers with only 3 volts on the microcontroller.
The bottom right of the circuit on http://www.cmeter.org/schematic.gif shows connections.
--
Ralph Hilton
http://www.ralphhilton.org
C-Meter: http://www.cmeter.org
FZAOINT http://www.fzaoint.net

Re: PC COM Ports

2005-12-14 by Don Kinzer

--- In AVR-Chat@yahoogroups.com, Bruce Parham <obparham@j...> wrote:
> ... switching thresholds at +/- 6v.

I have been able to send serial data to many different PCs using TTL 
outputs (mark=0V, space=+5V, nominally).  No problems yet.

Don
ZBasic Microcontrollers
http://www.zbasic.net

Re: [AVR-Chat] Re: PC COM Ports

2005-12-14 by David Kelly

On Wed, Dec 14, 2005 at 06:02:05PM -0000, Don Kinzer wrote:
> --- In AVR-Chat@yahoogroups.com, Bruce Parham <obparham@j...> wrote:
> > ... switching thresholds at +/- 6v.
> 
> I have been able to send serial data to many different PCs using TTL 
> outputs (mark=0V, space=+5V, nominally).  No problems yet.

Ditto.

The problem I have run across is sometimes even a premium brand PC
doesn't bother to provide negative voltage on the so-called no-longer
RS-232 ports. The result was about 0.25 volts for logic true, 3 volts
for logic false (RS-232 is inverted). Laptops are particularly bad about
this.

0/+3 happens to work on classic 1488/1489 buffers, "but its not right."

Super serious workstations used to rigidly ahere to +-10 volts. Many put
pullup or pulldown resistors on handshake inputs to set their desired
state if the line was not connected as some ancient UARTs would flat out
not run unless all the handshake lines were correct.

Have never seen the switching thresholds raised to 6 volts as some
have stated.

-- 
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.

Re: PC COM Ports

2005-12-14 by Don Kinzer

--- In AVR-Chat@yahoogroups.com, John Samperi <samperi@a...> wrote:
> + - 25V being the 'right' voltage :-)

I believe that the standard specifies the following:
mark: -3 to -25 volts
space: +3 to +25 volts

The range between -3 and +3 is indeterminate.

Don
http://www.zbasic.net

Re: [AVR-Chat] Re: PC COM Ports

2005-12-14 by John Samperi

At 05:52 AM 15/12/2005, you wrote:
>0/+3 happens to work on classic 1488/1489 buffers, "but its not right."
>
>Super serious workstations used to rigidly ahere to +-10 volts.


+ - 25V being the 'right' voltage :-)



Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Email: john@ampertronics.com.au
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

Re: [AVR-Chat] Re: PC COM Ports

2005-12-14 by Peter Harrison

John Samperi wrote:
> At 05:52 AM 15/12/2005, you wrote:
> 
>>0/+3 happens to work on classic 1488/1489 buffers, "but its not right."
>>
>>Super serious workstations used to rigidly ahere to +-10 volts.
> 
> 
> 
> + - 25V being the 'right' voltage :-)
> 

The RS232 Standard specifies signals as between +-3V and +-25V.

Equipment must be able to withstand as much as +-25V and should be able 
to guarantee at least +-3V at the receiver. Consequently higher voltages 
than the minimum specified are used to overcome anticipated transmission 
line losses. +-10V is a convenient middling value.

Thus, nearly all of the above are 'right' in the sense that they are 
nominally compliant with the standard. Voltages in the range -3 < V < +3 
are forbidden and may generate indeterminate results. However the DS1489 
line receiver has a reverse diode to ground at the input and so anything 
less than about 1.25V will be detected as a low signal.

Pete Harrison

Re: [AVR-Chat] Re: PC COM Ports

2005-12-15 by David Kelly

On Dec 14, 2005, at 3:36 PM, John Samperi wrote:

> At 05:52 AM 15/12/2005, you wrote:
>> 0/+3 happens to work on classic 1488/1489 buffers, "but its not  
>> right."
>>
>> Super serious workstations used to rigidly ahere to +-10 volts.
>
>
> + - 25V being the 'right' voltage :-)

The specified range is 3 to 30, positive and negative, with -3 to +3  
being the "keep out zone".

+-5 and +-12 used to be very common voltages to have inside a  
computer as Once Upon A Time common DRAM memory required negative  
voltage bias to operate.

The 1488 driver dropped about 2 volts so when driven with +-12 its  
output would swing +-10.

+-25 was much harder to drive a clean signal any interesting distance  
so the RS-232 spec is limited to 19,200 and 50'. Lower voltages work  
longer distances and higher data rates which prompted the move to LVD  
drivers.

--
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.

Re: [AVR-Chat] Re: PC COM Ports

2005-12-15 by Peter Jakacki

David Kelly wrote:
> The specified range is 3 to 30, positive and negative, with -3 to +3  
> being the "keep out zone".
>
> +-5 and +-12 used to be very common voltages to have inside a  
> computer as Once Upon A Time common DRAM memory required negative  
> voltage bias to operate.
>
> The 1488 driver dropped about 2 volts so when driven with +-12 its  
> output would swing +-10.
>
> +-25 was much harder to drive a clean signal any interesting distance  
> so the RS-232 spec is limited to 19,200 and 50'. Lower voltages work  
> longer distances and higher data rates which prompted the move to LVD  
> drivers.

Well, the reason lower voltages work longer distances is usually because 
of the lower threshold voltages specified, not any magic property of low 
voltages. Every signal takes a finite amount of time to "slew" through 
from one voltage to another, the more voltage, the longer it takes to 
get there.  Ask a driver to slew from -12V to +12V and it takes about 5 
times longer than an equivalent driver would take to go from 0V to +5V. 
BTW, RS-232 drivers have a built-in series drive resistance of 300 ohm 
(per the standard) which definitely prevents it from driving long lines 
with any real punch or ability to slew rapidly.

The reality is that not only the old 1489 receivers but also the newer 
MAX232 genre all have switching thresholds which are non-RS-232. The 
1489's input is a grounded emitter bipolar npn with a 4K series base 
resistor and a 10K base pulldown. There is also a reverse diode from 
base to emitter but this tends to be a by-product of integrating 
circuits on a common semiconductor substrate (hence the term IC). What 
does this all mean? The turn-on threshold of such a configuration is 
above 0.6V or so and needs a bit higher to saturate the transistor so 
that it can turn on fully. Go below this voltage and the transistor will 
be turned-off. Simple as that, no rocket science in this. So unless you 
are driving "relatively" long lines at "relatively" higher baud rates 
(say 20 metres plus at above 19.2K) then there is absolutely no problem 
with driving a common RS-232 receiver with 0 to +5V (even +3.3V dare I say).

Not standard you say? There is nothing standard about RS-232, even in 
it's heyday of the 60's and perhaps 70's (they didn't have much else 
then). We may have to make a professional product RS-232 compliant more 
out of legacy then out of compatibility, but that does not make it any 
better IMHO than a low-voltage interface. If I ever want distance, 
speed, noise-immunity etc then RS-232 is definitely not the choice 
anyway. I only use it for simple hook-ups to equipment such as PCs that 
usually span no more than a few metres. If you don't think that 0 to +5V 
is suitable for this distance then you had better design RS-232 drivers 
into your PS/2 keyboard and mouse and so on and so on, good luck.

Anyone who can quote an example of where 0 to +5V wouldn't work with 
some equipment is probably working in a deep dark basement at the 
Smithsonian Institute where the paper-tape reader still requires all 25 
blessed-blinking-RS232-%^*#! pins hooked-up as well :)

Anyway, why argue, use what works.

my2cents
*Peter*

Re: [AVR-Chat] PC COM Ports - was: testing uart using atmega16

2005-12-15 by Thomas Keller

Bruce Parham wrote:

> Zack Widup wrote:
>
> > On Tue, 13 Dec 2005, sheena licarte wrote:
> >>Mr. David and Mr. Zack thanks for the advice. i'll  try to test things
> >>one at a time. by the way is it possible to connect  avr directly to 
> the
> >>rs232 level converter such as max 232 and then to  pc?
> > Yes, the MAX232 series all have TTL inputs/outputs for the device and
> > RS-232 level inputs/outputs for the line.  They are very easy to use.
> Just a little heads up about comm ports on PC's. The RS-232 spec defines
> valid levels for the data line to be > +3V and < -3v. So you would think
> a MAX232 type device running on 3.3V and outputting a +/-6V signal 
> would work
> just fine with a PC. Not so... The PC folks (maybe IBM 20 years ago?) 
> decided
> to attenuate the inputs by a factor of 2, setting the switching thresholds
> at +/- 6v.
>
> This bit me in the rear a couple years back when I fired up a new 
> prototype
> board and connected it to my desktop Dell box. Comm was dead but the 
> scope said
> it was working... A bit of fiddling with a function generator revealed 
> that all
> the desktop and laptop Dells and Sony boxes needed about +/- 6.2V to 
> switch!
>
  Still better than what IBM offered on the PC for serial originally.  
Drove us nuts in a vertical software environment.  I was writing code to 
query and download data from electronic theodolites, and massage the 
data into a standard format for input to a CoGO (Coordinate Geometry) 
package our company sold.  Damned thing would NOT work with IBM PCs 
(whihc, at the time, was a minor inconvenience, because the vast 
majority of our customers were still using CP/M systems.  Biut the 
writing was already on the wall...if you expected to remain successfu;l 
on the market, you *HAD* to be PC compatible).

  it turned out that IBM, in yet anohter oif their infamous and 
braindead noves to "save costs" implemented their serial ports with +5V 
and 0V.  SOME RS-232C transceivers could talk to them, many could not.  
We finally had to locate an addon serial card for the PC, and include it 
with the software for PC purchasers.  What a pain in the arse.

   IBM, like  Mickey$lu$h, only believes in "standards" that THEY create.

tp,

Re: [AVR-Chat] Re: PC COM Ports

2005-12-15 by Thomas Keller

John Samperi wrote:

> At 05:52 AM 15/12/2005, you wrote:
> >0/+3 happens to work on classic 1488/1489 buffers, "but its not right."
> >
> >Super serious workstations used to rigidly ahere to +-10 volts.
>
>
> + - 25V being the 'right' voltage :-)

  Uhm...IIRC correctly, the RS-232C specification reads that the signal 
voltages are to be +/- 12.5 VDC (25 v total across the two).

tom

Re: [AVR-Chat] Re: PC COM Ports

2005-12-15 by David Kelly

On Thu, Dec 15, 2005 at 10:34:00AM -0600, Thomas Keller wrote:
> John Samperi wrote:
> 
> > At 05:52 AM 15/12/2005, you wrote:
> > >0/+3 happens to work on classic 1488/1489 buffers, "but its not right."
> > >
> > >Super serious workstations used to rigidly ahere to +-10 volts.
> >
> >
> > + - 25V being the 'right' voltage :-)
> 
>   Uhm...IIRC correctly, the RS-232C specification reads that the signal 
> voltages are to be +/- 12.5 VDC (25 v total across the two).

There are a lot of places in the net with a lot of conflicting EIA-232
information. Most likely due to the $100 fee for downloading the real
document. Maybe why there are so many bad implementations. +-15 and +-25
volts are the most common max voltages quoted.

The MC1488 driver is rated for up to +-15 volt supply. The MC1489
receiver is rated for +-30 so that goofballs can wire a -+15V source to
ground and a +-15V source to an input and not hurt the part.

http://www.onsemi.com/pub/Collateral/MC1488-D.PDF
http://www.onsemi.com/pub/Collateral/MC1489-D.PDF

In practice driving the MC1488 with +-12V resulted in +-10V outputs.

-- 
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.