Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[willc]

[Moderator note: These posts have been split from the original thread and moved so that they are in a more appropriate location.]

Does anybody know what's the meaning of the parameter PER in ms?

this is my stats for upstream in g.inp mode but without inp because the modem is broken and doesn't apply inp:
OR = 0.000 (Kbps)
NDR = 21599.863 (Kbps)
TDR = 24221.384 (Kbps)
msgOR = 0.000 (Kbps)
PER = 0.000 ms ----->?
CRCsec = 0.00
INP = 0.00 (symbols)
delay = 0.00 ms

this is the line of a guy in fastpath https://pastebin.com/DGUC2GFF
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 2.41 10.95
OR: 76.12 23.36
AgR: 51263.81 4111.93
as u can see he has PER 10.95 ms for the upstream and 2.41 ms for the downstream.
it looks like without error correction there is a bigger PER, because the guy has even the R parameter Reed Solomon set to 0.
thanks

[Dray]

packet error rate ?

[willc]

packet error rate ?

it's ms so i don't think so.i think it's some kind of delay or something.

[ejs]

From the ITU-T G.993.2 document:

PER_p The duration of the overhead frame in ms

With G.INP active in a direction, all the overhead data in that direction gets moved into Bearer 1.

Where did those stats come from, we don't usually see TDR and CRCsec?

[willc]

From the ITU-T G.993.2 document:
With G.INP active in a direction, all the overhead data in that direction gets moved into Bearer 1.

Where did those stats come from, we don't usually see TDR and CRCsec?

can you be more detailed how it works regarding that parameter?it's ms,does it add delay or something? why is ms?

the parameters are from my asus dsl ac 68u,for some reason the admin did move the post,i posted in the ixel's thread regarding the ac68

dunno how to add a spoiler to make it cleaner 

anyway you are right,the PER has delay on the bearer 1


<<< RX PMSTC Parameters >>>
MSGLP     = 0
MappingLp = 0x1f
Nlp       = 2
Nbc       = 1
Path[0]   = ENABLE
Path[1]   = ENABLE
Bearer[0] =  1 (mapped onto LP #1)
Bearer[1] = ff (disabled)
B[0]      = 235
B[1]      = 0
PMSTC Primary Parameters
T[0]      = 4
G[0]      = 32
F[0]      = 1
M[0]      = 4
L[0]      = 16
R[0]      = 16
I[0]      = 48
D[0]      = 1
q[0]      = 1

PMSTC Derived Parameters
Lmin[0]   = 0
Lmax[0]   = 0
ceil(G/T) = 8
MDF       = 8
K         = 32
N         = 48
PERB      = 96 (bytes)
U         = 2
SEQ       = 64
MSGc      = 58
S         = 24.000
OR        =  42.500 (Kbps)
NDR       =      0.000 (Kbps)
TDR       =     63.750 (Kbps)
msgOR     =  38.516 (Kbps)
PER       = 12.046 (ms)
CRCsec    = 0.80
INP       =  4.00 (symbols)
delay     =  0.00 (ms)
PMSTC Primary Parameters
T[1]      = 1
G[1]      = 1
F[1]      = 0
M[1]      = 1
L[1]      = 25013
R[1]      = 16
I[1]      = 252
D[1]      = 1
q[1]      = 1

PMSTC Derived Parameters
Lmin[1]   = 0
Lmax[1]   = 0
ceil(G/T) = 1
MDF       = 236
K         = 236
N         = 252
PERB      = 0 (bytes)
U         = 0
SEQ       = 0
MSGc      = 0
S         =  0.080
OR        =   0.000 (Kbps)
NDR       =  93186.601 (Kbps)
TDR       =  99662.695 (Kbps)
msgOR     =   0.000 (Kbps)
PER       =  0.000 (ms)
CRCsec    = 0.00
INP       =  0.00 (symbols)
delay     =  0.00 (ms)

<<< RX Line Bit Information >>>
TCM       = ENABLE
Nsc       = 2399
Seg_Num   = 19
nc_load   = 2398
nc_used   = 2399
nc_1bit   = 0
tcm_tones = 2398
line_bits = 26256
tcm_ovhd  = 1203
L_total   = 25053

[ejs]

The overhead data is used to send messages between your modem and the DSLAM for things such as reporting the various stats to the other end and organising bit swapping.

I think PER is basically the length of time it takes to send a fixed amount of data, one overhead frame. It doesn't add delay to your general use of the Internet connection, although I suppose it might impose a certain amount of latency on actions arranged by overhead messages, so it might affect exactly how quickly a bit swap could be done.

Even without G.INP, I think it can be done so that all the overhead data goes over a separate channel.

[willc]

The overhead data is used to send messages between your modem and the DSLAM for things such as reporting the various stats to the other end and organising bit swapping.

I think PER is basically the length of time it takes to send a fixed amount of data, one overhead frame. It doesn't add delay to your general use of the Internet connection, although I suppose it might impose a certain amount of latency on actions arranged by overhead messages, so it might affect exactly how quickly a bit swap could be done.

Even without G.INP, I think it can be done so that all the overhead data goes over a separate channel.

ok thanks for the answer