Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Command reference for Zoom 2949L (Venus)?

38 views
Skip to first unread message

The King

unread,
Dec 8, 1999, 3:00:00 AM12/8/99
to
I have a Zoom 56K Dualmodem using the Lucent 1673 family (Venus)
chipset. I'd like to obtain a command and S-register summary for this
chipset. More directly how do you disable the V.90 protocol? Is there
any documentation for this chipset available on the Web? Any help would
be greatly appreciated.

"I have nothing to RTMF!"


Ed Schulz

unread,
Dec 8, 1999, 3:00:00 AM12/8/99
to
The King wrote:
>
> I have a Zoom 56K Dualmodem using the Lucent 1673 family (Venus)
> chipset. I'd like to obtain a command and S-register summary for this
> chipset. More directly how do you disable the V.90 protocol?

From http://www.56k.com/trouble/interop.shtml#k56disable

For Venus chipsets (mostly used in external
modems): S109=0 K56flex only (V.90 disabled)
S109=1 K56flex or V.90*
S109=2 V.90 only (K56Flex disabled)
S38=0 Disable K56flex and V.90 (use V.34)

* Which protocol will be used? Assuming that the ISP supports both,
it depends on the firmware. Some versions will prefer K56flex, others will
prefer V.90.

The rest of the commands are like the Lucent Win Modem. See
http://www.lucent.com/micro/K56flex/v90atcom.pdf
--
Ed Schulz
edsc...@lucent.com

Donald Hinds

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to
Connecting with the 56K

I don’t know what company coined the term ‘drivers’ for modems. The driver is
COMM.DRV in
Windows (there are 3rd party DRV like Turbocomm.drv). What are commonly
(and erroneously)
called ‘drivers’ are just *.INF files with settings for the modem. Those
settings are used by
Windows or other operating systems to set its COMM.DRV (or equivalent)
through the software.
- - - - - - - - - - - - - - - - - - - - - - - -
Normal INIT for modems on a PC is AT&F&C1&D2 (change &D2 to &D0
for
Mac) Sometimes, even though the modem seems to get a good connect
(usually with hi-speed modem) it does not actually make the connection
correctly. (It may be the OTHER end making the error). Often if you use
one of the (prefix) strings to force that connect speed the
connection may be made 'solid' on both ends. Use your normal Init
string. Or you may use the selection of the strings below (between the
AT...DT) added onto your Init string or in Extra Settings. Such as..
AT&F&C1&D2&Q6N1 Make SURE your computer is properly grounded. The
vfc/v.34 modems especially, seem to have connect problems if the
computer is not grounded right.
The normal dial Prefix is ATDT. If the number is 423-1563 then it
sends ATDT4231563 to the modem, which then dials, and connects. This
is using auto-speed or (incorrectly) autobaud negotiation as well as
negotiating Protocol (V.42bis, MNP etc.). &Q6 sets NO V42(bis) keeps
modem buffers. &Q0 for no V42(bis) and no modem buffers. S95=1 or W2
will give true modem-modem connect speed. (Default S95=0 or W1 shows
computer to modem speed).

R=Rockwell L=Lucent (ISA=external/PCMCIA)
AT&F :Default -> negotiate all protocols/speeds
AT+MS=12,0 :R-ISA - V.90 Only
AT+MS=56,0 :R-ISA - K56Flex Only
ATS109=1 :L-ISA - negotiate V90/Flex
ATS109=2 :L-ISA - V90 only
ATS109=0 :L-ISA - Flex only
AT+MS=V90 :R-PCI - V90 Only
AT+MS=K56FLEX :R-PCI - K56FLEX Only
AT-V90=1 S38=1 :L-PCI - negotiate V90/Flex
AT-V90=1 S38=0 :L-PCI - V90 Only
AT-V90=0 S38=1 :L-PCI - K56Flex Only
AT+MS=V90 :R-PCI - V90 Only
AT+MS=K56FLEX :R-PCI - K56FLEX Only
AT+MS=11,1 :R-ISA negotiates v34 speeds
AT+MS=V34 :R-PCI negotiate v34 speeds
ATS37=0 :L negotiates v34 speeds
AT+MS=11,1,19200,28800 :R-ISA negotiates V.34 19200-28000 only
AT+MS=10,1 :R-ISA negotiates V32bis (4800-14400)
AT+MS=V32B :R-PCI negotiates v32bis 14400
ATS37=11 :L connect v32bis 14400
AT+MS=10,1,9600,14400 :R negotiates V32bis 9600/14400 only
AT+MS=V32 :R-PCI negotiates v32 9600
AT+MS=2,1 :R-ISA negotiates V22bis 1200/2400
ATS37=6 :L connect 2400
AT+MS=2,0,1200,1200 :R-ISA connect V22bis 1200 only
AT+MS=1 :R-ISA connect V22 1200
ATS37=2 :L connect 1200 V.23
AT+MS=69 :R-ISA connect Bell 212 (1200)
AT+MS=0 :R-ISA connect V21 300
AT+MS=64 :R-ISA connect Bell 103 (300)
An example string: AT&F&C1&D2S95=1+MS=11,1

NOTE 1: The above strings are using buffering which allows the computer
to have a higher speed than the modem. If you still have trouble try
&Q0 and set your computer speed the same as the modem speed. 38400,
19200 or 9600. &Q6 will let the modem negotiate speed without V42bis.

NOTE 2: I discovered when a user couldn't connect to a 300bps modem,
that if I did AT&F&C0&D0 before using the dial prefix, then it
would connect. This is worth a try on stubborn 1200bps modems too.

NOTE 3: If none of these work, give the number, protocol and emulation
and we will test it to see if we can connect, and at what speed.

NOTE 4: If you try to force a speed higher than the other modem
can connect, you will get NO CARRIER. Set your modem speed to the
software speed just above the modem's highest speed and let the
modem negotiate whenever possible.

NOTE 5: If you are answering, you can replace the DT with A (don't
use autoanswer but type the string to answer). Or put the string
in the autoanswer string of the software. ATA will manually answer.

NOTE 6: The string to make sure you are in Data mode is AT+FCLASS=0

NOTE 7: Phone lines won't always support the highest speeds of V34/56K.
You may drop lower, you may disconnect. Most often this will happen with
local calls like to your Internet provider. Try forcing slower speeds,
until you stay on line OK.

NOTE 8: With a 56K modem you may need an additional command to connect
at 56K speeds. ATS202=32

NOTE 9: %Cn compression command has the following values for n. 0=no
compression, 1=Mnp5, 2=V42bis, 3= both

NOTE 10: %En retrain command has the following values for n. 0=no
retrain, 1=monitor and fallback, 2=monitor and fall back/forward,
3=fallback/forward and fast hangup (3-Rockwell only).

Connecting to X2/V90 one user says:: For your information I had a customer
down on
Cape Cod that has a 2948 Lucent modem with the latest flash. We forced
the modem with AT\N3 (only). He made a solid connection at 46666 and his
download speed for a large file was 5.4k. I don't know if this will
work with all V90/X2 servers but at least this worked.

Connect result messages / modem speed

S95=0 or W1 gives you CONNECT speed (modem to computer). If you
need CONNECT speed the same as CARRIER (modem to modem) use S95=1 or
W2.
When running a BBS, try S95=3 and you will get only CONNECT
(carrier) message, with \ARQ for error correcting modems. Always
set your speed in your program to a high computer-modem speed
(56K/115K) The modem will take care of modem to modem speed.

Don Hinds - Zoom Tech

In article <0704d53bfaa9b93e...@elvis.jpunix.com>,
nob...@elvis.jpunix.com says...


>
> I have a Zoom 56K Dualmodem using the Lucent 1673 family (Venus)
>chipset. I'd like to obtain a command and S-register summary for this

0 new messages