Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: keyap on December 01, 2016, 06:20:31 PM
-
Hi guys, was hoping someone could have a look at my stats and give me some pointers / views. Pre a few days ago I've never bothered having a look at what was going on however, on 29th Nov a neighbour commented that an engineer had been doing some work under the small 'grate' in our front garden and there was mention of something being reset? Not sure what? I therefore though it would be a good opportunity to give one of the HG612 stats programs a try.
I've attached what BT Openreach show for the line and a couple of screen dumps from the stats program.
Thanks
[attachment deleted by admin]
-
I would be quite happy with those....I wish mine looked like that.
I'm nowhere near the BT checker. The old AL cable takes all the higher frequency's out
-
If line your line length to the Primary Connection Point cabinet is around 870 to 1000 meters then yeah that is a good connection for the longer line with no internal or external issues.
But a single snapshot of stats keyap does not show the full story of the line only when logging and getting graphs over time will it show how well it is performing.
-
Thanks both.
Length to exchange is ~4.5Km. Not sure on exact length to cabinet though? I know where it is and, as the crow flies, it's ~400m however, if I follow the road, it's nearer ~1.2KM. Is there any way to get an accurate length to cabinet?
Re ongoing monitoring. I'd ideally like to set up 24/7 MyDSLWebstats monitoring but have no idea how to do this? Next step is going to be some forum reading to see how to make this happen :-\
-
You could use dslstats on a pi if you want a low power/small foot print solution..
-
Never used a PI. Is there an 'idiots' guide covering what I need and how to set it up?
-
Is there any way to get an accurate length to cabinet?
A GEA test if your using Plusnet as your ISP shows accurate line length in those tests, and if you know each joint your line uses all the way to PCP cabinet it will give you some idea other than that the Openreach engineer during a home visit can give you this.
-
Might be of some help
http://forum.kitz.co.uk/index.php/topic,15882.0.html
-
Might be of some help
http://forum.kitz.co.uk/index.php/topic,15882.0.html
Thanks - looks like the PI is a good option. Before I read more though, just want to check there's no way of doing this via Android? Have a 'box' connected 24/7 so would be an easy option if there's some type of app?
-
Only RPi OS Debian and Linux or Microsoft OS there is no Android support
-
Dont believe so..
-
DslStats works on Windows/Linux/Pi/Mac(via wine)
HG612_stats works on Windows (looks like that's what you're using)
Your stats look decent to me. You're near the high estimates from the BTWholesale checker. You're connected to a Huawei cabinet and G.INP is enabled.
You can sign up to MyDSLWebStats here
https://www.mydslwebstats.co.uk/mdws-rg.php
Then enter your username & validation code in either of the 2 compatible stats programs mentioned above.
-
Thanks all.
DSLStats on a PI would seem the way to go :fingers:
As a complete noob to the PI world, this seems like a good starting point (I think?) - https://www.amazon.co.uk/Raspberry-Pi-Official-Desktop-Starter/dp/B01CI5879A/ref=pd_vtph_147_bs_t_1?_encoding=UTF8&psc=1&refRID=HDJQMTQ5MQXZH54RGHW5
-
If you get a New RPi with noobs installed it will guide you through the process but make sure you click on Raspbian as the OS because on noobs you can install other OS which won't with DSLstats
-
Thanks everyone ;). I'm now registered on the MyDSLWebStats site (username = keyap) and the above PI is on the way.
Using HG612 Stats and uploading via the PC seems to be working OK :fingers:
-
Not sure if I should post this here or on another section of the forum, but I've noticed that every hour, on the hour, the HG612 Stats program stops updating.
From what I can see, at this time, there's two instances of HG612_stats.exe running? Killing the processes make it work again.
This can be seen in my online stats which show a small gap in data until I do the above?
Anyone got any ideas?
-
I occasionally saw similar problems. Switching to using DslStats, I've not had any problem since.
There's a specific forum section for stats monitoring programs. Either ask for help with HG612_Modem_Stats in their specific thread, or give DslStats a go.
http://forum.kitz.co.uk/index.php/board,46.0.html
Router Monitoring Software section ^^^^
http://www.s446074245.websitehome.co.uk/downloads.html
DslStats download site ^^^^
-
Thanks John,
As I've ordered a PI, and will therefore need to switch to DsLStats, I'll give it a go on the PC.
-
I have seen this. I think it can be related to if you create a new task in hg612stats and the old one remains. You could try deleting any hg612 tasks from scheduler and the re open hgstats and then create a new task from scratch. Then check back in scheduled jobs that only one has been created/active.. worked for me..
-
You may be onto something. When I created the task in the GUI it would not accept my User Name even though the details were correct. I had to set it to run as Administrator however, although it would accept the user name it kept failing. To get it to work I then had to amend the User Name manually in windows task scheduler back to what I was trying to enter originally via the GUI. It accepted the manual entry but had the hourly disconnect bug?
As I cannot set a task with the correct user name via the GUI. I've deleted the original and manually added one to windows task scheduler myself from scratch with the right info. It looks like it's working OK for now so fingers crossed for 17:00.
Another strange thing is that I cannot get DSLStats to work on the PC? App will start fine and log but it then tries to run something called cURL which errors - 'The cURL executable has encountered a problem and needs to close...... etc'.
Not a big issue as everything should be up and running on the PI soon :fingers:
-
Think I've sorted the problem with the HG612_Stats on the PC stopping on the hour. I had 'Snapshots' enabled running on the hour at hourly intervals. Turning 'Snapshot Stats' off seems to have cured the problem :)
-
There is a bug in windows task scheduler where a task could be run twice, which because the task is run every minute is quite likely to happen on affected systems.
https://support.microsoft.com/en-gb/kb/2461249
As far as I'm aware this does not affect Windows 8 or newer.
-
I'm on XP which isn't listed as one of the impacted OS's. I think turning off 'Snapshots' seems to have sorted it - I've now been running for a few hours and it's not stopped :fingers:
-
XP is no longer supported so they wouldn't mention it as there wouldn't be a hotfix for it.
-
I'm on XP which isn't listed as one of the impacted OS's
XP is no longer supported so they wouldn't mention it as there wouldn't be a hotfix for it.
Of course :-[
Thankfully switching off Snapshots has worked
-
Did you check the scheduled jobs etc?..I use snapshots with no issue. I had the duplicate error which as I said for me was down to 2 jobs being active...
-
Yep... checked the jobs and 2 jobs running at the same time was the problem but it was triggered by snapshots (not sure why though?). Possibly a combination of my really old, slow computer and running XP?
With snapshots on (set to run each hour) there was one HG612_Stats.exe running every minute except for on the hour when two ran causing logging to stop.
With snapshots off only one HG612_Stats.exe runs, even on the hour.
-
Quiet Line and HLOG is very good and wondering what service your using 55/10 it cant be 40/10 or you would be capped at a DS sync of 39999 kbps, SNRM looks steady apart from interference noise from 15:40 to 17:15
Bits/Tones very good no RFI ingress getting into the well balanced pairs the errored seconds on the DS is very good with G.INP but US errored second rate is fair but could be better if G.INP was enabled.
-
Thanks. I'm on 80/?. When I first looked at FTTC, based on the BTWholesale estimate, I wasn't sure if I would benefit from 80 Vs 40 (55 is not available with my ISP). Thankfully the ISP I chose agreed to give me the 80 option for the same prices as their 40 packages as an introductory offer.
They let me have this for the first 6 months with the agreement that after this period I can either switch to 40 or keep the 80. At this point however, the 80 would then cost more albeit only a few £s.
Form a line perspective, it sounds like everything is OK and I should have a PI soon so 24/7 monitoring will be set up. Hopefully that won't highlight any issues!
Is there anything I should do / need to do based on the stats?
-
The SNRM looks like a concern. I want to see continuous stats really so roll-on getting your Pi set up ;)
-
Thanks Dray, is the SNRM concern due to the same reason highlighted by NewtronStar?
-
It's just that there's not enough data to go on. Is your modem plugged into the master socket?
-
Is your modem plugged into the master socket?
Yes
-
So, the PI's arrived and I'll be looking to set up over the next few days. Just a quick question:
I'm going to need to change some plugs around and this may result in the HG612 being switched off and back on. Anything I should be aware of?
Line stats are available via MyDSLWebStats under user name keyap albeit they currently aren't 24/7 given they're generated by my PC.
Thanks
-
I'm going to need to change some plugs around and this may result in the HG612 being switched off and back on. Anything I should be aware of?
Just power down the HG612 and disconnect the patch lead connecting its xDSL port to the external line. Leave the HG612 powered down whilst all other modifications are taking place.
Once the modifications/adjustments are complete and a half hour period has elapsed since you powered down the HG612, then reconnect the HG612 to the power. Once it has fully booted and stabilised, reconnect the patch lead to the external line.
-
Thanks burakkucat.
Why half an hour though?
-
The DLM process operates on data gathered in fifteen minute periods but we do not know when a fifteen minute period will start. So to ensure that the DLM process sees at least one complete fifteen minute period with CPE "loss of power" noted, double the time quantum . . . hence half an hour. :)
-
Makes sense :) Thank you