[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

K56flex råd?



Hej sluggere!

Jeg har et råd til K56flex modem brugere, som måske 
ville gøre sig godt i sslug-artiklen om ISP-opkobling.
Hvis dem, der vedligeholder siden, mener det er 
allemandsviden, så kan i jo bare grine over min enfoldighed..
Det skal nok forfattes lidt smartere hvis det skal med.

Jeg har selv haft nogle problemer med ISP opkobling til Image
(forbindelsen var ustabil m.m.). Her kommer min løsning:

Her er et udklip fra Image support:
**********************************************************
Man kan risikere at komme ud for at ens modem kører for 
hurtigt i forhold til hvad den analoge telefonlinje kan 
klare. Dette vil resultere i at modemet undervejs
genforhandler hastighed. I de 10-15 sekunder, 
genforhandlingen finder sted, kan der ikke overføres 
andet data på linjen. Dette vil føles som huller i
datastrømmen. Senere vil man så kunne risikere at modemet 
igen kører op i hastighed, for igen at løbe ind i problemer...
**********************************************************
Og tak til Image for den oplysning...

Men hvordan stiller man så de der hastigheder?

Man kan styre det med initialiseringsstrengen
på følgende måde:

"AT+MS=<mode>,<automode>,<min_rate>,<max_rate>"

Hvor: 

<mode> er modulationsmode (11 for V.34 og 56 for K56flex)
<automode> automode flag (0 for auto off og 1 for auto on)
<min_rate> minimum bps rate
<max_rate> maximum bps rate

I K56flex kan man (på mit modem) stille følgende rates:
56K,54K,52K,50K,48K,46K,44K,42K,40K,38K,36K,34K og 32K

Hvordan finder man så den korrekte max. rate?

En god ide er at pinge een eller anden hurtigt host 
(f.eks. den som kører DNS). Lad være med at bruge 
opkoblingen til andet.

Hvis din <max_rate> ikke er for stor, vil responstiden 
for en pingpakke være næsten konstant. Stiller du <max_rate>
for stor, vil svartiden variere.

F.eks. ses her svartider ved <max_rate>=46K:

PING 212.54.64.170 (212.54.64.170): 56 data bytes
64 bytes from 212.54.64.170: icmp_seq=0 ttl=62 time=107.5 ms
64 bytes from 212.54.64.170: icmp_seq=1 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=2 ttl=62 time=110.1 ms
64 bytes from 212.54.64.170: icmp_seq=3 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=4 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=5 ttl=62 time=110.1 ms
64 bytes from 212.54.64.170: icmp_seq=6 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=7 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=8 ttl=62 time=110.1 ms
64 bytes from 212.54.64.170: icmp_seq=9 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=10 ttl=62 time=110.0 ms

Det er rimeligt konstant. Skruer vi så hastigheden op til
<max_rate>=48K fås følgende tider:

PING 212.54.64.170 (212.54.64.170): 56 data bytes
64 bytes from 212.54.64.170: icmp_seq=0 ttl=62 time=116.9 ms
64 bytes from 212.54.64.170: icmp_seq=1 ttl=62 time=109.9 ms
64 bytes from 212.54.64.170: icmp_seq=2 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=3 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=4 ttl=62 time=559.9 ms
64 bytes from 212.54.64.170: icmp_seq=5 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=6 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=7 ttl=62 time=109.9 ms
64 bytes from 212.54.64.170: icmp_seq=8 ttl=62 time=1170.0 ms
64 bytes from 212.54.64.170: icmp_seq=9 ttl=62 time=180.0 ms
64 bytes from 212.54.64.170: icmp_seq=10 ttl=62 time=720.0 ms
64 bytes from 212.54.64.170: icmp_seq=11 ttl=62 time=110.0 ms
64 bytes from 212.54.64.170: icmp_seq=12 ttl=62 time=110.0 ms

Her ses varierende svartider. Svarende til at modemet
een gang imellem forsøger at overskride telefon linjens grænse.

Så jeg har følgende chatscript:

ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT "ERROR"
ABORT "NO ANSWER"
ABORT "BUSY"
ABORT "Invalid Login"
ABORT "Login incorrect"
TIMEOUT 5
"" AT&F&C1S9=15
TIMEOUT 50
OK "AT+MS=56,1,32000,46000"
OK "ATDT104938833883"
CONNECT ""

Det virker som en drøm. Jeg håber der er nogen, 
som kan bruge mit råd.

Med venlig hilsen
-Jørgen Lorentsen


 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2005-08-10, 19:08 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *