I've shifted the programs including the ini file to the scripts folder, but it's still leaving the isrunning file and it doesn't generate graphs when I run current_stats.
Do you mean there are multiple instances of ISRUNNING clocking up?
Are there any clues in the error log?
It should be found in the same folder as modem_stats.log.
It should look something like this, with the ISRUNNING file being deleted at the end of HG612_stats.exe:-
| Text | |
1 23 45 67 89 1011 1213 1415 1617 1819 2021 2223 2425 2627 2829 3031 3233 3435 3637 3839 4041 4243 4445 46 | 06/01/2013 21:06:00.040 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling 06/01/2013 21:06:00.040 - Temp File ISRUNNING-210600-040 was created06/01/2013 21:06:00.041 - malloc() O.K. 06/01/2013 21:06:00.041 - Initializing Winsock06/01/2013 21:06:00.043 - WSAStartup() SUCCESSFUL!!! 06/01/2013 21:06:00.043 - Starting getaddrinfo()06/01/2013 21:06:00.043 - getaddrinfo() O.K. 06/01/2013 21:06:00.043 - Starting socket()06/01/2013 21:06:00.047 - socket() O.K. 06/01/2013 21:06:00.047 - Starting connect()06/01/2013 21:06:00.048 - connect() O.K. 06/01/2013 21:06:00.850 - About to reply(xdslcmd info --stats)06/01/2013 21:06:00.850 - reply(xdslcmd info --stats) O.K. 06/01/2013 21:06:01.062 - get_data() O.K.06/01/2013 21:06:01.062 - About to determine the xDSL mode 06/01/2013 21:06:01.062 - About to parse_stats()06/01/2013 21:06:01.063 - parse_stats completed 06/01/2013 21:06:01.063 - VDSL2 mode detected so about to reply(xdslcmd info --pbParams)06/01/2013 21:06:01.063 - reply(xdslcmd info --pbParams) O.K. 06/01/2013 21:06:01.271 - get_data() O.K.06/01/2013 21:06:01.271 - About to parse_pbParams_data() 06/01/2013 21:06:01.271 - parse_pbParams_data() completed06/01/2013 21:06:01.271 - About to exit Busybox 06/01/2013 21:06:01.271 - Busybox exited06/01/2013 21:06:01.471 - About to exit ATP 06/01/2013 21:06:01.472 - ATP exited06/01/2013 21:06:01.477 - About to get_log_data() 06/01/2013 21:06:01.933 - About to calc_ES_delta()06/01/2013 21:06:01.934 - About to calc_RSCorr_delta() 06/01/2013 21:06:01.935 - About to calc_RSUnCorr_delta()06/01/2013 21:06:01.935 - About to calc_RS_delta() 06/01/2013 21:06:01.936 - About to calc_OHF_delta()06/01/2013 21:06:01.936 - About to calc_OHFErr_delta() 06/01/2013 21:06:01.937 - About to calc_HEC_delta()06/01/2013 21:06:01.937 - About to calc_CRC_delta() 06/01/2013 21:06:01.938 - About to calc_FEC_delta()06/01/2013 21:06:01.938 - Appending data to MSLOGFILE.log 06/01/2013 21:06:01.938 - Closing MSLOGFILE.log06/01/2013 21:06:01.939 - END of 1 minute sampling 06/01/2013 21:06:01.939 - About to close(sockfd)06/01/2013 21:06:01.939 - About to freeadddrinfo(res) 06/01/2013 21:06:01.939 - About to WSACleanup()06/01/2013 21:06:01.939 - About to free(txbuf) 06/01/2013 21:06:01.939 - About to free(rxbuf)06/01/2013 21:06:01.939 - End of HG612_stats.exe program, closing ERROR.LOG 06/01/2013 21:06:01.939 - ISRUNNING-210600-040 DELETED |
Just thinking the only time you really need to to run current_stats is when the modem re-synced as thats the only time they will change iirc.
Not quite.
Hlog & QLN remain as static data until the next resync.
Bitloading & SNR are dynamic throughout the duration of a connection.
I'll send you a version with progress output echoed to screen that might give us a clue as to where things are getting stuck.
I can't recall now, but are you using an OS something like Windows Server 2012?
Would it not be possible for the get stats exe to run current_stats when it see's the up time has reset, thus automatically logging those stats after every re sync?
That's a thought that I might try to implement.



Pages in this thread:
Print Thread


