Register (or login) on our website and you will not see this ad.
|
|
FWIW, I've not had much time to play about yet, so the best I've been able to obtain from an unlocked ECI modem on a live (remotely accessed) VDSL2 connection so far, using an amended version of one of my scripts is as follows:-
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
5051
5253
5455
5657
5859
6061
6263
6465
6667
6869
7071
7273
7475
76 | =~=~=~=~=~=~=~=~=~=~=~= Plink log 2012.10.13 23:00:51 =~=~=~=~=~=~=~=~=~=~=~=
login as: adminpassword:
BusyBox v1.00 (2011.08.09-03:28+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.
Alpha # Alpha # echo "g997lspbg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack nReturn=0 nDirection=0 LATN[0]=132 LATN[1]=305 LATN[2]=489 LATN[3]=-32768 LATN[4]=-32768 SATN[0]=117 SATN[1]=302 SATN[2]=484 SATN[3]=-32768 SATN[4]=-32768 SNR[0]=57 SNR[1]=56 SNR[2]=59 SNR[3]=-32768 SNR[4]=-32768
Alpha #
Alpha # echo "g997lspbg 0" > /tmp/pipe/dsl_cpe0_cmdAlpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 LATN[0]=2 LATN[1]=225 LATN[2]=364 LATN[3]=-32768 LATN[4]=-32768 SATN[0]=1 SATN[1]=223 SATN[2]=362 SATN[3]=-32768 SATN[4]=-32768 SNR[0]=68 SNR[1]=69 SNR[2]=63 SNR[3]=-32768 SNR[4]=-32768
Alpha # Alpha # echo "g997listrg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack nReturn=0 nDirection=1 G994VendorID=IFTN SystemVendorID=ECI tele VersionNumber= SerialNumber=7035497883 SelfTestResult=0 XTSECapabilities=(00,00,00,00,00,00,00,00)
Alpha #
Alpha # echo "g997lsg 1 1" > /tmp/pipe/dsl_cpe0_cmdAlpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nLineState=0x801
nReturn=0 nLineState=0x801
Alpha # Alpha # echo "g997lsg 0 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack nReturn=0 nDirection=0 nDeltDataType=1 LATN=0 SATN=0 SNR=64 ATTNDR=21918632 ACTPS=-901 ACTATP=125
Alpha #
Alpha # echo "g997csg 1 1" > /tmp/pipe/dsl_cpe0_cmdAlpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=-22Alpha # Alpha # echo "g997csg 0 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack nReturn=0 nChannel=0 nDirection=1 ActualDataRate=67868000 PreviousDataRate=73992000 ActualInterleaveDelay=975 ActualImpulseNoiseProtection=30
Alpha #
Alpha # echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmdAlpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0010,0031),(0010,0031))
(01,(0882,1193),(0882,1193))
(02,(1984,2770),(1984,2770))
"
Alpha # Alpha # echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack nReturn=0 nDirection=1 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0857),(0033,0857))
(01,(1218,1959),(1218,1959))
(02,(2795,3950),(2795,3935))
"
Alpha #
Alpha # exit |
Obtaining the stats seems rather unreliable & having quickly read through the released source code, I readily admit to being rather stumped at this stage.
|
|
|
Hopefully I'll have better luck, I've been studying the source code today, interesting. Hopefully the modem will arrive tomorrow morning.
A command that interests me (g997cdrtcg / g997cdrtcs)...
AKA G997_ChannelDataRateThresholdConfigGet / G997_ChannelDataRateThresholdConfigSet:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
26 | static const DSL_char_t g_sG997cdrtcg[] =
#ifndef DSL_CPE_DEBUG_DISABLE "Long Form: %s" DSL_CPE_CRLF
"Short Form: %s" DSL_CPE_CRLF DSL_CPE_CRLF
"Input Parameter" DSL_CPE_CRLF#if (DSL_CPE_MAX_DEVICE_NUMBER > 1)
"- DSL_uint32_t nDevice (optional, not used in the 'backward compatible' mode)" DSL_CPE_CRLF#endif
"- DSL_uint8_t nChannel" DSL_CPE_CRLF "- DSL_AccessDir_t nDirection" DSL_CPE_CRLF
" upstream = 0" DSL_CPE_CRLF " downstream = 1" DSL_CPE_CRLF
DSL_CPE_CRLF "Output Parameter" DSL_CPE_CRLF
"- DSL_Error_t nReturn" DSL_CPE_CRLF#if (DSL_CPE_MAX_DEVICE_NUMBER > 1)
"- DSL_uint32_t nDevice (optional, not used in the 'backward compatible' mode)" DSL_CPE_CRLF#endif
"- DSL_uint8_t nChannel" DSL_CPE_CRLF "- DSL_AccessDir_t nDirection" DSL_CPE_CRLF
" upstream = 0" DSL_CPE_CRLF " downstream = 1" DSL_CPE_CRLF
"- DSL_uint32_t nDataRateThresholdUpshift" DSL_CPE_CRLF "- DSL_uint32_t nDataRateThresholdDownshift" DSL_CPE_CRLF
DSL_CPE_CRLF ""; |
Is this possibly a command that will restrict the maximum downstream/upstream to what you specify (specifically the set command that is)?
For example, I imagine if I wanted to set on the downstream a max rate of 70,000 Kbps and a min rate of 60,000 Kbps I would do the following...
| Text | 1
| g997cdrtcs 0 1 70000 60000 |
That's assuming that's what it does, and that's also assuming I'm right in believing it's channel 0.
Edited by Ixel (Mon 05-Nov-12 18:30:57)
|
|
|
Just an update to say to others that I've received the unlocked ECI modem this morning and so far (touch wood) there has been absolutely no errors on the upstream or downstream, unless the GUI is wrong (which I hope not). I usually have errors within at least 5 minutes of sync, but I've been synced for nearly 30 minutes without any so far.
At this time, it appears true that you should use an ECI modem on an ECI cabinet, my Fritz!Box 7390 and HG612 both produced errors within 5 minutes of sync uptime. My attainable rates are slightly different however, downstream is virtually identical to the HG612 for me (85000Kbps or so), but the upstream has lost about 7 megabits (attainable is just below 20000Kbps). Nevermind though, so long as it remains stable (virtually error free), keeps me on fastpath and doesn't drop further, I'm happy  .
I will begin my hunt for commands on telnet and update again once I know more for those who are interested, probably in a different thread though.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Did you end up with the old version - it has 4 rubber feet where the new one has two rubber feet, the other two being solid plastic?
I'm sure that Bald Eagle said that the graphic user interface didn't report correctly, or was just blank, I'm sure he'll be along soon to confirm the situation.
|
|
|
Old version of the modem. Trying to find out what the command for dsl_pipe is to fetch the error stats. Once I have I'll see what they say as opposed to the GUI.
EDIT:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
| Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh pmcctg 0 1
nReturn=0 nChannel=0 nDirection=1 nElapsedTime=4201 bValid=1 nCodeViolations=0 nFEC=0
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh pmcctg 0 0nReturn=0 nChannel=0 nDirection=0 nElapsedTime=4221 bValid=1 nCodeViolations=0 nFEC=0
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh g997lsg 1 1
nReturn=0 nDirection=1 nDeltDataType=1 LATN=178 SATN=170 SNR=112 ATTNDR=85765760 ACTPS=-901 ACTATP=-3
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh g997lsg 0 1nReturn=0 nDirection=0 nDeltDataType=1 LATN=0 SATN=0 SNR=61 ATTNDR=19633716 ACTPS=-901 ACTATP=103
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh g997lspbg 1
nReturn=0 nDirection=0 LATN[0]=125 LATN[1]=285 LATN[2]=454 LATN[3]=-32768 LATN[4]=-32768 SATN[0]=134 SATN[1]=283 SATN[2]=453 SATN[3]=-32768 SATN[4]=-32768 SNR[0]=111 SNR[1]=108 SNR[2]=115 SNR[3]=-32768 SNR[4]=-32768
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh g997lspbg 0nReturn=0 nDirection=0 LATN[0]=11 LATN[1]=211 LATN[2]=334 LATN[3]=-32768 LATN[4]=-32768 SATN[0]=15 SATN[1]=209 SATN[2]=334 SATN[3]=-32768 SATN[4]=-32768 SNR[0]=60 SNR[1]=61 SNR[2]=61 SNR[3]=-32768 SNR[4]=-32768
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh g997csg 0 1
nReturn=0 nChannel=0 nDirection=1 ActualDataRate=59996000 PreviousDataRate=0 ActualInterleaveDelay=0 ActualImpulseNoiseProtection=0
Alpha # /ifx/vdsl2/dsl_cpe_pipe.sh g997csg 0 0nReturn=0 nChannel=0 nDirection=0 ActualDataRate=19460000 PreviousDataRate=0 ActualInterleaveDelay=0 ActualImpulseNoiseProtection=0 |
Edited by Ixel (Tue 06-Nov-12 10:39:34)
|
|
|
I'm sure that Bald Eagle said that the graphic user interface didn't report correctly, or was just blank, I'm sure he'll be along soon to confirm the situation.
This is what can be seen on the connection that I have remote access to:-
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
| Traffic Statistics
Traffic Statistics display Receive and Transmit packets passing through the Device.
STATISTICSInterface Transmit Receive
Pkts Drops PktsLAN 14063 0 14713
WAN 0 0 0VDSL2 Line Status
Line Status showtime
Band Upstream Downstream
US0 Line Attn 0 0US1/DS1 Line Attn 0 0
US2/DS2 Line Attn 0 0US3/DS3 Line Attn 0 0
US4/DS4 Line Attn 0 0US0 Signal Attn 0 0
US1/DS1 Signal Attn 0 0US2/DS2 Signal Attn 0 0
US3/DS3 Signal Attn 0 0US4/DS4 Signal Attn 0 0
US0 Actual SNR 0 0US1/DS1 Actual SNR 0 0
US2/DS2 Actual SNR 0 0US3/DS3 Actual SNR 0 0
US4/DS4 Actual SNR 0 0
Channel Status Upstream DownstreamActual Net Data Rate 20000000 kbps 73992000 kbps
Actual Interleave Delay 0 ms 0 msActual INP 0 Symbols 0 Symbols
Attainable Net Data Rate 22204773 kbps 79386368 kbpsTransmit Power 119 dBm 61 dBm
Current 15 mins Near End Far End
CRC 0 0 FEC 4294967252 0
ES 0 0 SES 0 0
UAS 0 0
24 hours Near End Far EndCRC 4294967291 0
FEC 4294967243 0 ES 0 0
SES 0 0 UAS 0 0 |
Some of that lot looks a bit wrong, too many decimal places or complete zeros that can't be correct, can it?
As it's a live connection & not my own, I can't mess about with it too much in the way of experimenting.
I'm also rather busy with other things at this time, so don't really have time to play about with scripts etc.
I might get some time after Christmas, but hopefully it will all be sorted by then anyway 
|
|
|
|
Some of that is definitely wrong. Interestingly if you study the HTML source of the inner frame you'll see JavaScript variables for things such as SATN, but not used in the GUI. The values given in the GUI for sync rate/attainable rate are actually bps, not Kbps, so divide them by 1000 and round for the Kbps value. This is what I did in my ECIModem Plotter (preview screenshot on the forum I posted it on).
|
|
|
|
guys this sounds scary to me.
it sounds like FTTC DLM is worse than ADSL DLM in that it constantly reboots connections either to relax settings or tighten them up. So a line eg. might get interleaved after a flood of noice, is stable but then DLM itself a week later will put a gap in the uptime by forcing a resync back to fast path, then might be another set of line errors back to interleaving again so the line is forced unstable by DLM itself.
About half of FTTC graphs I have seen (tbb graphs) have a red line showing a resync.
|
|
|
ADSL DLM runs for the life of a connection too, and adjusts target margins / interleaving options if left to run in auto mode
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
guys this sounds scary to me.
it sounds like FTTC DLM is worse than ADSL DLM in that it constantly reboots connections either to relax settings or tighten them up. So a line eg. might get interleaved after a flood of noice, is stable but then DLM itself a week later will put a gap in the uptime by forcing a resync back to fast path, then might be another set of line errors back to interleaving again so the line is forced unstable by DLM itself.
About half of FTTC graphs I have seen (tbb graphs) have a red line showing a resync. This antiquated idea used for adsl and now FTTC clearley does not work for some customers and there should be an option for DLM to be disabled/over ridden by the ISP , whilst the reasoning behind dlm is mainly to save on tech support costs for some if not all the big mass market isp's there are plenty of smaller niche isp's out there too, and the option should be given by BT openreach/wholesale ect ect to all Isp's buying the product wholesale from them ,Giving the isp the choice to use or not use this method of capping the connection. as BT are no longer the ones libable to provide the end user with Tech support, if i was to consider FTTx it would be the on demand product as a connection with induced lag is not worth the money IMO
Edited by tommy45 (Sun 25-Nov-12 19:32:12)
|
|
|
Pages in this thread: 
Print Thread
