Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
comp.sys.3b1
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
ACU @ 110 & 150 bps w/ BNU (svr3.2)
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
SDF Poster  
View profile  
 More options May 23 2008, 7:14 pm
Newsgroups: comp.dcom.modems, comp.sys.att, comp.sys.3b1, comp.mail.uucp
From: marti...@sdf.lNoOnSePsAtMar.org (SDF Poster)
Date: Fri, 23 May 2008 23:14:09 +0000 (UTC)
Local: Fri, May 23 2008 7:14 pm
Subject: ACU @ 110 & 150 bps w/ BNU (svr3.2)
Forward | Print | Individual message | Show original | Report this message | Find messages by this author
I'm using a WE 103 ACU which can answer at 110 and 150 bps with
out problems, however the slowest speed the dialer will work
with the ACU in the 103 is 300bps.  Debugging using the BNU shows the
call to open the TTY and setting the speed of the line but then the
Dialer times out.  I'm using the PENRIL generic which works fine at
300bps.  Is it not possible to originate a call below 300bps?  Even using
'cu' to open a connection to the TTY fails when the line is being set to
anything slower than 300.  From what I can tell so far this is a software
limitation in the BNU set and not the 103 itself.  

    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Reed  
View profile  
 More options May 24 2008, 6:15 pm
Newsgroups: comp.dcom.modems, comp.sys.att, comp.sys.3b1, comp.mail.uucp
From: Reed <re...@rmi.net>
Date: Sat, 24 May 2008 16:15:11 -0600
Local: Sat, May 24 2008 6:15 pm
Subject: Re: ACU @ 110 & 150 bps w/ BNU (svr3.2)
Forward | Print | Individual message | Show original | Report this message | Find messages by this author

SDF Poster wrote:
> I'm using a WE 103 ACU which can answer at 110 and 150 bps with
> out problems, however the slowest speed the dialer will work
> with the ACU in the 103 is 300bps.  Debugging using the BNU shows the
> call to open the TTY and setting the speed of the line but then the
> Dialer times out.  I'm using the PENRIL generic which works fine at
> 300bps.  Is it not possible to originate a call below 300bps?  Even using
> 'cu' to open a connection to the TTY fails when the line is being set to
> anything slower than 300.  From what I can tell so far this is a software
> limitation in the BNU set and not the 103 itself.  

Well, generically, calls can be originated at any speed.

The question is how, and at what speed, is the modem/acu configured to
accept dial strings from a DTE ? Or can it automatically detect (auto-baud)
the speed of dialing commands (Hayes AT, or WE103 specific) ?? Some modems can.

Is the "WE 103 ACU" a "real" Western Electric 103 with built-in Auto Call
Unit, or a clone by some other brand ??

I can well imagine some design engineer deciding that "no one could
possibly need to dial at 110 or 150 (or 75 or 134.5 or other vintage TTY
speeds)".

Do you have user manual for it (I suspect not)

--Reed


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
SDF Poster  
View profile  
 More options May 24 2008, 6:53 pm
Newsgroups: comp.dcom.modems, comp.sys.att, comp.sys.3b1, comp.mail.uucp
From: marti...@sdf.lNoOnSePsAtMar.org (SDF Poster)
Date: Sat, 24 May 2008 22:53:54 +0000 (UTC)
Local: Sat, May 24 2008 6:53 pm
Subject: Re: ACU @ 110 & 150 bps w/ BNU (svr3.2)
Forward | Print | Individual message | Show original | Report this message | Find messages by this author

Reed  <re...@rmi.net> wrote:

>Is the "WE 103 ACU" a "real" Western Electric 103 with built-in Auto Call
>Unit, or a clone by some other brand ??

Its a real 103.  The HDB dialer can access it at 300 baud and it can dial
successfully.  However, at 110 or 150 the line seems to be setup but the
dialer immediately exits without an obvious error.

I've also confirmed this with a real WE 212A which HDB was able to dial
out on at 300 and 1200.   Again, using getty or uuget with a definition at
110 or 150 bps for incoming calls works fine, its just dialing out at
those speeds that fails.

Based on this, I'm guessing that its merely a software issue and that I'll
just need to write my own dialer.

>I can well imagine some design engineer deciding that "no one could
>possibly need to dial at 110 or 150 (or 75 or 134.5 or other vintage TTY
>speeds)".

Its possible that the HDB UUCP never thought anyone would need to dial out
at speeds lower.  I could try Version 7 UUCP on an SVR2 machine and see
if I have better luck.

>Do you have user manual for it (I suspect not)

Actually, we have a wall of BSTJs.  You are welcome to visit some time
if you are in the Seattle are: http://museumofcommunications.org/

I appreciate your response!


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2010 Google