|
I also forgot to point out that I just figured out today that we were setup using the bell 208 standard. Had I known that from the beginning I would have mentioned it. Brian Ellis wrote: > > Carl, > You hit the nail on the head there. We are currently communicating with > others using the bell 208 @ 4800 bps. And yes, now I need to be able to > also connect to a site using the v.32 compliant standard @ 9600. My > modem supports both modes of communications. However, it appears I can't > switch from one format to another on the fly. > My modem is a Penril Datalink V.32 Series 14.4 kbps. Maybe I should get > another modem for this application? > Any suggestions? > Brian Ellis > > Carl Galgano wrote: > > > > Brian: > > I have been following this thread, but now have a question. You are dialing > > 4800 to several other modems and now you wish to use the same modem to > > connect at 9.6. Connecting via 4800 is a pretty old standard, What type of > > modem are you using. I suspect you are using a half duplex modem that > > support the bell 208 a/b standard. I also suspect that the new modem you > > wish to talk to supports a v.32 compliant standard. What I suspect here is > > that the modem you have, and are currently using for BSC @ 4800 is not going > > to work for 9600, no matter what you do. > > cjg > > > > Carl J. Galgano > > EDI Consulting Services, Inc. > > 550 Kennesaw Avenue, Suite 800 > > Marietta, GA 30060 > > (770) 422-2995 - voice > > (419) 730-8212 - fax > > mailto:cgalgano@ediconsulting.com > > http://www.ediconsulting.com > > AS400 EDI, Networking, E-Commerce and Communications Consulting and > > Implementation > > http://www.icecreamovernight.com > > Premium Ice Cream Brands shipped Overnight > > > > "You ain't gonna learn what you don't want to know" - rw > > > > -----Original Message----- > > From: midrange-l-admin@midrange.com > > [mailto:midrange-l-admin@midrange.com]On Behalf Of Brian Ellis > > Sent: Monday, August 27, 2001 5:44 PM > > To: midrange-l@midrange.com > > Subject: Re: CHGLINBSC LINESPEED(????) > > > > My dilemma is that our physical modem is set at 4800 bps and set not to > > change. All other systems we dial out to are to specific numbers that > > have modems on the other end set to 4800 bps and set not to change their > > communication rates. > > > > Now all of a sudden I have a requirement to dial out to another system > > at 9600. Their modem is setup not to negotiate a rate (it will only > > connect at 9600). > > > > I was hoping to be able to change the line description to 4800 or 9600 > > bps which would send the control codes to my modem and reset it's > > connection speed respectively. > > > > No such luck huh? > > > > Thanks for your help. > > Brian Ellis > > > > Pat Barber wrote: > > > > > > Generally speaking, the software will have no effect on line speed. The > > > two factors are what modem you have and the modem that answers the call. > > > > > > When the "handshake" procedure runs, the called modem decides if it can > > > run at the requested speed, and if so, it will attempt to do so. > > > > > > Sooooo... what are you calling and what is answering determines line > > > speed. Static and crummy lines will also cause the modem speed to > > > degrade, but again, both modems have to agree to "step down" in speed. > > > > > > How do you know what speed you are transmitting at ??? > > > > > > Do you have the switch setting correct for 14.4bps operations ???? > > > > > > Can the called modem run at 14.4 ?? and is he setup for 14.4 ???? > > > > > > Brian Ellis wrote: > > > > > > > > We have a modem which has the capability to transmit at 14.4 bps rates. > > > > However, all of our current incoming and outgoing communications through > > > > these modems are being done at 4800 bps. > > > > > > > > Does changing the line speed (CHGLINBSC) for a binary synchronous line > > > > attached to a controller/device for synchronous modem communications > > > > change the connection speed the modem will communicate at? > > > > > > > _______________________________________________ > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > > To post a message email: MIDRANGE-L@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > > or email: MIDRANGE-L-request@midrange.com > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.