🚀 go-pugleaf

In article <KARTHY.92Jul23115350@xiv.iesd.auc.dk> karthy@iesd.auc.dk (Karsten Thygesen) writes:
>
>Hi.
>
>I am forwarding this question for a friend, but please send any
>help/comments to me.
>
>Problem: We are currently developing a program to control a
>professional video recorder. The video recorder has a serial RS 232
>interface which communicates at 38400 bit/s, 8 data bits and odd
>parity (i.e. 9 bits per character plus start/stop bits). These
>communication parameters cannot be changed in the video recorder. We
>have suceeded in producing a C program which reads and a writes to one
>of the Next's serial ports at the required speed, but we can't get the
>program to send 8 bit data followed by the parity bit. We guess this
>is due to limitations in the standard serial drivers (/dev/tty) which
>can only generate a parity bit when 7 data bits are used (i.e. max. 8
>bits per character plus start/stop bits). To solve the problem, we
>would like to know:
>
>1) Are we correct in assuming the above limitation regarding the
>standard driver? If not, how do you set it to the required parameters.
>
>2) If the standard driver cannot be set to the required parameters,
>how do you access the hardware (SCC chip)? 
>
>In both cases, pieces of sample code would be very helpful. (We have a
>technical description of the SCC chip itself).
>
>Thanks in advance,
>
>Karsten.
>
>--
>--------------------------------------------------------------------
>Karsten Thygesen              I Aalborg University                 I
>Korsgade 48 2. th             I Institute for electronic systems   I
>9000 Aalborg                  I                                    I
>InterNet: karthy@iesd.auc.dk  I Fredrik Bajers vej 7, 9220 Aalborg I
>Phone (HOME): +45-98124259    I DK-Denmark.                        I
>--------------------------------------------------------------------

My favoite solution for this kind is just one 68HC11. It has EEPROM inside
which can take care of conversion as a snap.

Soo
lee@cs.wisc.edu

In article <KARTHY.92Jul23115350@xiv.iesd.auc.dk> karthy@iesd.auc.dk (Karsten  
Thygesen) writes:
> 
> Hi.
> 
> I am forwarding this question for a friend, but please send any
> help/comments to me.
> 
> Problem: We are currently developing a program to control a
> professional video recorder. The video recorder has a serial RS 232
> interface which communicates at 38400 bit/s, 8 data bits and odd
> parity (i.e. 9 bits per character plus start/stop bits). 

The NeXT serial driver is pretty adamant about 10 bit data frames.  As most  
modems will only work with a 10 bit data frame, NeXT feels this does not cause  
anyone any hardships. 

--
Michael Rutman			|	moose@svcdudes.com
Cubist				|	makes me a NeXT programmer
Software Ventures		|	maker of MicroPhone II
#include <std.disclaimer>

moose@svcdudes.com writes:
>In article <KARTHY.92Jul23115350@xiv.iesd.auc.dk> karthy@iesd.auc.dk (Karsten  
>Thygesen) writes:
>> Problem: We are currently developing a program to control a
>> professional video recorder. The video recorder has a serial RS 232
>> interface which communicates at 38400 bit/s, 8 data bits and odd
>> parity (i.e. 9 bits per character plus start/stop bits). 
>The NeXT serial driver is pretty adamant about 10 bit data frames.  As most  
>modems will only work with a 10 bit data frame, NeXT feels this does not
>cause anyone any hardships. 

For such a forward-looking organization, NeXT was certainly short-sighted
on this one. I'm a little surprised that no one there checked out the needs
of pro-video machines when writing the serial stuff.

Steve abell@netcom.com