Print

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

[Bald_Eagle1]

The format of the data in a HG612 with its firmware updated by BT is 'different' to that in a pre-updated modem.

It just needs the data to be parsed & a few tab spaces removed here & there to make it 'readable' again.

As obtained directly from the modem:-

Code: [Select]

Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1196)
DS: (33,859) (1216,1846)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:      4586 kbps     22884 kbps
Actual Aggregate Tx Power:        6.9 dBm      12.6 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 8.2 54.4   N/A   N/A   N/A 21.9 66.9   N/A
Signal Attenuation(dB): 8.2 53.7   N/A   N/A   N/A 30.9 66.8   N/A
SNR Margin(dB): 8.4 6.0   N/A   N/A   N/A 6.1 6.1   N/A
TX Power(dBm): 0.1 5.9   N/A   N/A   N/A 11.6 6.1   N/A


After it has been 'munged' a little:-

Code: [Select]

Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1198)
DS: (33,859) (1216,1772)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:      4896 kbps     22236 kbps
Actual Aggregate Tx Power:        6.8 dBm      12.6 dBm
====================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 8.1 53.5   N/A   N/A   N/A 21.7 65.7   N/A
Signal Attenuation(dB): 8.1 52.8   N/A   N/A   N/A 30.5 65.5   N/A
SNR Margin(dB): 6.0 6.0   N/A   N/A   N/A 4.8 5.1   N/A
TX Power(dBm): -0.8 5.9   N/A   N/A   N/A 11.6 5.7   N/A


[roseway]

Thanks for that, BE1. I was tearing my hair out trying to understand why it didn't tab properly.

[NewtronStar]

don't laugh but here is the way i have parsed and tab it via text editor ->

[roseway]

I wouldn't dream of laughing. That's what I need to do in code, but only (at present) for the HG612 new firmware. I guess I'll be counting tabs and removing the excess ones.

[burakkucat]

don't laugh but here is the way i have parsed and tab it via text editor ->

I would smile and say "resourceful kitteh". 

[Mark1]

I don't know if this has been mentioned before, but the graphs FEC and CRC per min misrepresent actual error rate if the sample interval is less than one minute. For example, if I set the sample interval to 15 seconds then it appears that dslstats multiplies the errors by 4 to give a per minute error count which is much higher than actual errors. Would it not be better to update these graphs per minute to match actual error rate or on a per sample interval basis?

Other than that, the program is excellent, and works in Linux which I am grateful for.

[roseway]

the graphs FEC and CRC per min misrepresent actual error rate if the sample interval is less than one minute.

What DSLstats does is take the number of FECs or CRCs between the previous sample and the current one, and convert it to a per-minute value. So, for example, if there were 20 FECs in 15 seconds, this would be displayed as 80 FECs per minute. It represents the rate of FECs or CRCs, not the total number.

Perhaps this isn't the best way to display it, but it's not practical to sample just these values at a different rate to everything else.

[roseway]

Hello kind of new to DSLstats and have been using V4.1 to watch my evening SNR's and Errors in realtime, my question is can you update to 4.11 and keep the current graphing going as i did try but have to start recording all over again, the errors seconds graphs are very good and held in a file to look back on previous days

I'm sorry, but I've just noticed that I never answered this. The only way to keep the graphs (sort of) alive would be to use the Save/Restore XML option to save the graph information before closing DSLstats, and then restore them from the saved XML files when you wanted to revisit them.

(Sorry I took nearly three weeks to reply, it wasn't intentional )

[Mark1]

Perhaps this isn't the best way to display it, but it's not practical to sample just these values at a different rate to everything else.

Fair enough. I'll stick to a one minute sample interval as it is more than sufficient.

[roseway]

Perhaps this isn't the best way to display it, but it's not practical to sample just these values at a different rate to everything else.

Fair enough. I'll stick to a one minute sample interval as it is more than sufficient.

It's been in the back of my mind to redo this section, but at present I can't decide how best to rearrange it. I will give it some more thought when I'm able.