G'day John!



 -=> In a message on 17 Mar 96 <=-

 -=> John Piper said this to Stephen Lennie <=-



 JP> CONNECT 28800/LAP-M/V.42bis/LAPM/V42BIS

 

 JP>> and instead report them as CONNECT 28800/LAP-M/V.42bis/V.FC?

 

 SL> If you have "S95=47" change it to "S95=0" as
multi-line CONNECT strings

 SL> are rarely needed and tend to confuse most comms and BBS software.



 JP> Hmmm. I always used S95=47 to report the DCE speed. Maybe it's

 JP> superfluous since I'm using the %U2 and \V1 (or whatever it was that

 JP> you suggested). 



All NetComm SmartModems report the DCE speed by default ("W2")
and there also

seems to be a lot of confusion regarding "S95" - read on...



The S95 S register is a Bit-Mapped register which controls the CONNECT string

and can generate multi-line CONNECT messages.



To enable various Functions add the numbers in the Value column of the table

below.



Bit  Value  Function



 0     1    CONNECT message indicates DCE speed instead of DTE speed (1)

 1     2    Appends /REL to the CONNECT - indicates Error Correction (2)

 2     4    CARRIER message indicates line speed

 3     8    PROTOCOL message indicates type of Error Correction in use

 4    --    Reserved

 5    32    COMPRESSION message indicates type of Data Compression in use

 6    --    Reserved

 7    --    Reserved



NOTES: (1) The modem always reports Line (DCE) speed in the CONNECT message

           by default.  This setting will only indicate Terminal (DTE) speed

           if the "W0" or "W1" command is issued.

       (2) The "\V" and "%U" commands override this setting.





This is how a CONNECT message looks with "S95=47" (also "W2
\V1 %U2")...



CARRIER 28800



PROTOCOL: LAP-M



COMPRESSION: V.42BIS



CONNECT 28800/LAP-M/V.42bis/V.FC





 SL> Does the "ATI9" command respond with something like this?...

 

 SL> Series 5  V.FAST Class 28800 Modem DFS(K)-V7 V2.61L NetComm Ltd. (C) 1995



 JP> Series 5  V.FAST Class 28800 Modem DFS(B)-V7 V2.61L NetComm Ltd. (C) 1995

 JP>                                    ^^^^^^^^^

 JP> Not sure what this means, but it's certainly different from yours.



Don't worry, the "K" on mine and the "B" on yours
probably just indicate the

revision level of the board - as mine's an M34F and yours is an M11F.  I was

only guessing anyhow.



 SL> Also, does the "ATI2" command return "OK"?  If
not, time to reload the

 SL> firmware.



 JP> ATI2 returned two OKs. Normal?



Yes, that's normal.  The "I2" command checks the firmware checksum and

responds with "OK" or "ERROR".  The second
"OK" is just the standard response

from any successfully executed "AT" command.

 

 SL> I used exactly the same setup (S95=47 too) on my M34F to try to duplicate

 SL> the problem but all I got was the proper response...

 

 SL> atdl

 SL> RINGING

 

 SL> CARRIER 28800

 

 SL> PROTOCOL: LAP-M

 

 SL> COMPRESSION: V.42BIS

 

 SL> CONNECT 28800/LAP-M/V.42bis/V.FC

     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 JP> That's what I want. :-(



You want *all* of that ?!  Most people, and their software, are happy with

just the last line - the *actual* CONNECT message.



 SL> All I can suggest is that you ensure that you have the correct firmware

 SL> code file and reload it by following this procedure...



 JP> Procedure chomped, but filed in case I need it. I did exactly as the

 JP> manual told me, all except for specifying a DTE rate with /C=19200. 

 

 SL> 2 19200 bps is slow but sure



 JP> Dunno why -- the thing's capable of 115k2. I lock it at 57k6 anyhow.



The modem's maximum DTE rate *is* 115k2 but the firmware loader program only

allows a maximum of 57k6 - and that's only recommended if you have a 16550

UART in your serial port.  As all UARTs support 19k2, it's a safe bet if

serial port problems are suspected.





BFN

  _

 (_`

 ._)teve







___ E-mail: slennie{at}cin.gov.au

~~~ PGPWave v1.22a Gamma / PGP 2.6.3i

... Our Father UART in heaven; I/O'd be thy name.

--- Blue Wave/386 v2.30