Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2 3

Author Topic: snapshot graphs broky :(  (Read 14147 times)

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
snapshot graphs broky :(
« on: April 15, 2014, 04:40:08 AM »

Bald Eagle I need urgently asap please to look into snapshot graphs on the programs you sent.

When I try to run from gui the command window briefly appears and exits, going way too fast for successful run.

Also the auto snapshot's are failing as well.

Reason I want asap if possible is a force resync was carried out on my line at 1am, and my sync speed shot up by over 10mbit.  I think was forced because I dont know of lines resyncing of their own accord if they have plenty of snrm and no errors.

Now I dont think this will hold, because the line now only has a 4.3db snrm on the downstream and the modem is now reporting a lower attainable for my US than previos (although still full 20mbit sync), my line characterstics have completely changed,  So i am very curious to see a graph.

Found graph6 error log
Code: [Select]
04/04/2014 07:00:08.842 - Start of GRAPH6.exe
04/04/2014 07:00:08.912 - The program full path is      F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Scripts\GRAPH6.exe
04/04/2014 07:00:08.912 - The program directory path is F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Scripts
04/04/2014 07:00:08.912 - DEBUG_COMMENTS = YES
04/04/2014 07:00:08.912 - Using F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Current_Stats\Current_Stats_20140404-0700-SCHEDULED\Plink_20140404-0700.log
04/04/2014 07:00:08.920 - About to change folder to the one with the log file stored in it
04/04/2014 07:00:08.920 - Successfully changed directory to F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Current_Stats\Current_Stats_20140404-0700-SCHEDULED
04/04/2014 07:00:08.920 - About to parse Bits data
04/04/2014 07:00:08.926 - About to parse SNR  data
04/04/2014 07:00:08.933 - About to parse QLN  data
04/04/2014 07:00:08.940 - About to parse Hlog data
04/04/2014 07:00:08.946 - About to parse pbParams data
04/04/2014 07:00:09.013 - About to parse show data
04/04/2014 07:00:12.555 - About to delete temporary files
04/04/2014 07:00:12.556 - The Plink log being used came from a RESYNC or SCHEDULED event, so any pauses were disabled
04/04/2014 07:00:12.556 - End of GRAPH6.exe program, closing ERROR.LOG[/code[

and current error log

[code]04/04/2014 07:00:00.897 - Start of Current Stats Harvesting
04/04/2014 07:00:01.055 - The program full path is      F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Scripts\HG612_current_stats.exe
04/04/2014 07:00:01.055 - The program directory path is F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Scripts
04/04/2014 07:00:01.055 - DEBUG_COMMENTS = YES
04/04/2014 07:00:01.055 - Temp File CURRENT-ISRUNNING-070000-897 was created
04/04/2014 07:00:01.055 - Before checking for RESYNC or SCHEDULED events, Delay_snapshot_data_harvest_seconds = 0
04/04/2014 07:00:01.055 - A SCHEDULED run was detected via HG612_stats.exe. Initial Pause setting from ini file = NO
04/04/2014 07:00:01.055 - Pause setting for this instance only has been forced to be NO
04/04/2014 07:00:01.055 - After checking for RESYNC or SCHEDULED events, Delay_snapshot_data_harvest_seconds = 0
04/04/2014 07:00:01.055 - malloc() O.K.
04/04/2014 07:00:01.055 - Initializing Winsock
04/04/2014 07:00:01.055 - WSAStartup() SUCCESSFUL!!!
04/04/2014 07:00:01.056 - Starting getaddrinfo()
04/04/2014 07:00:01.056 - getaddrinfo() O.K.
04/04/2014 07:00:01.056 - Starting socket()
04/04/2014 07:00:01.056 - socket() O.K.
04/04/2014 07:00:01.056 - Starting connect()
04/04/2014 07:00:01.056 - connect() O.K.
04/04/2014 07:00:01.122 - About to reply(xdslcmd info --stats)
04/04/2014 07:00:01.122 - reply(xdslcmd info --stats) O.K.
04/04/2014 07:00:01.132 - get_data() for --stats O.K.
04/04/2014 07:00:01.132 - Modem in use = HG612
04/04/2014 07:00:01.132 - About to determine the xDSL mode
04/04/2014 07:00:01.132 - About to parse_stats()
04/04/2014 07:00:01.134 - parse_stats completed
04/04/2014 07:00:01.134 - VDSL2 mode detected so about to reply(xdslcmd info --pbParams)
04/04/2014 07:00:01.134 - reply(xdslcmd info --pbParams) O.K.
04/04/2014 07:00:01.156 - get_data() for --pbParams O.K.
04/04/2014 07:00:01.156 - About to parse_pbParams_data()
04/04/2014 07:00:01.156 - parse_pbParams_data() completed
04/04/2014 07:00:01.156 - reply(xdslcmd info --Bits) O.K.
04/04/2014 07:00:02.555 - get_data() for --Bits O.K.
04/04/2014 07:00:02.557 - reply(xdslcmd info --linediag) O.K.
04/04/2014 07:00:08.680 - get_data() for --linediag O.K.
04/04/2014 07:00:08.681 - reply(xdslcmd info --show) O.K.
04/04/2014 07:00:08.715 - get_data() for --show O.K.
04/04/2014 07:00:08.715 - reply(xdslcmd --version) O.K.
04/04/2014 07:00:08.757 - get_data() for --version O.K.
04/04/2014 07:00:08.758 - parse_version() completed
04/04/2014 07:00:08.773 - About to exit Busybox
04/04/2014 07:00:08.773 - Busybox exited
04/04/2014 07:00:08.776 - About to exit ATP
04/04/2014 07:00:08.776 - ATP exited
04/04/2014 07:00:08.777 - About to close (sockfd)
04/04/2014 07:00:08.777 - About to WSACleanup()
04/04/2014 07:00:08.777 - About to free(txbuf)
04/04/2014 07:00:08.777 - About to free(rxbuf)
04/04/2014 07:00:08.777 - CURRENT-ISRUNNING-070000-897 DELETED
04/04/2014 07:00:08.777 - Auto_graph_Snapshot_data = YES, now graphing snapshot stats
04/04/2014 07:00:08.777 - Successfully changed directory to F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Current_Stats\Current_Stats_20140404-0700-SCHEDULED
04/04/2014 07:00:08.778 - Pause_after_obtaining_snapshot_data = NO
04/04/2014 07:00:08.778 - GRAPHING_COMMAND = "F:\Drivers\HG612\HG612_Modem_Stats_Programs-r2.0\Scripts\GRAPH6.exe"
04/04/2014 07:00:08.836 - Snapshot graphs should now have been plotted
04/04/2014 07:00:08.836 - End of HG612_current_stats.exe program, closing ERROR.LOG
« Last Edit: April 15, 2014, 04:43:53 AM by Chrysalis »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #1 on: April 15, 2014, 04:49:03 AM »

ongoing graphs work, the changes on that are.

attenuation very slightly increased
ds signal power large jump O_o
us snrm down a bit
ds attainable speed up a lot
ds sync speed up a lot

no errors or ES at time of sync drop.
still on fast path.

I am guessing I need a new graph exe to go with the new hg612 stats.exe?
« Last Edit: April 15, 2014, 04:52:15 AM by Chrysalis »
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: snapshot graphs broky :(
« Reply #2 on: April 15, 2014, 06:36:31 AM »

Latest versions of the programs are attached.

Unzip ALL of them to the Scripts folder.

The log data you posted is from 4th April, Do you have anything from when it failed?

Assuming the folder locations & other settings are correct in the ini file, these should work, but it does need all of them to be together in the Scripts folder.

Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #3 on: April 15, 2014, 03:02:13 PM »

thanks they in place, running the snapshot graph now seems to start to work but it crashes.

What info you need to debug?
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #4 on: April 15, 2014, 03:08:26 PM »

ok I had to put the 10 april binary back, the stats stopped updating also on this new one.

so now i have 10 april hg612 stats exe, and the rest of the exe's from the 14 april left in place.

here is why investigating, got almost 80meg sync again. albeit with now a lower snrm, I am wondering if was outage in my area and I synced before disturbers resynced.
« Last Edit: April 15, 2014, 03:11:17 PM by Chrysalis »
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: snapshot graphs broky :(
« Reply #5 on: April 15, 2014, 06:43:43 PM »

With the latest versions I posted you need to include this at the bottom of your ini file to specify the modem type:-

[Event/Error_logging]
Extensive_event_logging=      YES


[Modem]
Modem_type =            HG612


Alternatively, use the attached version of HG612_current_stats.exe & HG612_stats.exe that default to HG612 if the modem type has NOT been specified.


I'm sure I had included RONSKI's version of his GUI that would include the modem type setting a while ago.

Maybe I didn't ???

« Last Edit: April 15, 2014, 06:46:00 PM by Bald_Eagle1 »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #6 on: April 15, 2014, 08:47:27 PM »

already got those lines.

will try the newest binaries you just posted.

are these new binaries needed for snapshot graphs to work?
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: snapshot graphs broky :(
« Reply #7 on: April 15, 2014, 11:08:26 PM »

The other versions worked at this end, but I have made a slight amendment that may help.

You do also need these in the Scripts folder (note the file dates & times):-

13/04/2014  22:38           146,079 GRAPH6.exe
01/04/2014  23:30           142,279 graphpd.exe


Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #8 on: April 16, 2014, 01:35:47 AM »

yes thats the exact date times of what I have.

if its any help it crashes on 3 of 16 everytime, it isnt random.

Code: [Select]
Problem signature:
  Problem Event Name: APPCRASH
  Application Name: HG612_current_stats.exe
  Application Version: 0.0.0.0
  Application Timestamp: 534c6742
  Fault Module Name: HG612_current_stats.exe
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp: 534c6742
  Exception Code: c0000005
  Exception Offset: 000068d3
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 2057
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

thats for the 14 april binaries, the newer ones now work, I not tested hg612 stats exe yet tho just the current stats one.
« Last Edit: April 16, 2014, 01:39:20 AM by Chrysalis »
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33884
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: snapshot graphs broky :(
« Reply #9 on: April 16, 2014, 08:25:04 AM »


if its any help it crashes on 3 of 16 everytime,


sorry for butting in, but just wanted to eliminate the obvious.

   Check the file paths carefully in the .ini

Particularly the folders, ie current_stats v current stats.
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #10 on: April 16, 2014, 02:30:40 PM »

kitz paths are fine, his latest binaries graphs now work.
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #11 on: April 16, 2014, 05:18:06 PM »

I am curious if openreach have added a 4db snrm profile.

My attainable should be lower than my sync speed if my target snrm is 6db but isnt.  My data does NOT show I initially synced at 6db then it dropped to 4db, it started at 4db.

I do feel this is too agressive for my line tho.  when I checked earlier had about 1500 crc errors for one and half days not too bad.  But now a couple of hours later its 2600 errors and the SES has accrued by 1.  I feel I am vulnerable to a burst of errors at one point which may shift me on interleaving for a couple of weeks.

In terms of the snapshot graphs I have observed the following.

Lower QLN across most of the range about 20db lower.
Higher bitloading across most of the range, so the entire range higher bitloading.  Although I think the 3rd DS channel seems to have the biggest gains.
« Last Edit: April 16, 2014, 05:21:54 PM by Chrysalis »
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33884
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: snapshot graphs broky :(
« Reply #12 on: April 16, 2014, 05:25:06 PM »

Rather strange.

>> I am curious if openreach have added a 4db snrm profile

Highly unlikely, if it was 3dB then it could be a possibility. 
Any profiles would always be 3,6,9 etc due to the fact that it takes 3dB of SNR for 1 bit of data.

Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: snapshot graphs broky :(
« Reply #13 on: April 16, 2014, 05:36:53 PM »

kitz paths are fine, his latest binaries graphs now work.

That's good news.  :)
Thanks for the confirmation.


Just for curiosity, what size are the snapshot Plink logs?

They should be around 330KB or so.

If they are significantly larger, it would indicate that auto-detection of a HG622 isn't working as intended.

That's why the final release of v 2.1 will include a drop down list to select the modem in use (hopefully including Kitz's ZyXel VMG8324-B10A).

If a particular modem isn't selected or if still using an older version of the ini file & an older version of RONSKI's GUI, the default will be to assume a HG612.



Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7405
  • VM Gig1 - AAISP CF
Re: snapshot graphs broky :(
« Reply #14 on: April 16, 2014, 07:06:41 PM »

Rather strange.

>> I am curious if openreach have added a 4db snrm profile

Highly unlikely, if it was 3dB then it could be a possibility. 
Any profiles would always be 3,6,9 etc due to the fact that it takes 3dB of SNR for 1 bit of data.



although its db of snr per bit a drop to 4db will still increase bitloading but I agree it would be odd for them to pick 4db given previous profiles used.

This whole event is weird, a resync event out of the blue during DLM hours at a lower snrm with a different PSD mask applied.

BE plink log is 332KB.
Logged
Pages: [1] 2 3