Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: Ronski on May 15, 2014, 08:44:52 PM
-
V2.1 of the GUI has just been released, along with V2.1 of the stats logging program, there will be new thread for the logging programs shortly.
The GUI can be updated via auto update, but you'll need to download the V2.1 logging program (http://www.freewarefiles.com/HG612-Modem-Stats_program_84567.html) to take advantage of some of the new features. Please see the new thread regarding v2.1 of the stats logging program. (http://forum.kitz.co.uk/index.php?topic=13974.msg262659#msg262659)
Changes in V2.1 of the GUI.
2.1.5246.34669 13-05-2014
V2.1 release version - please ensure you are using V2.1 of the stats logging programs.
2.0.5242.34533 09-05-2014
Altered padding on writing to ini files
Added PC speed option
Added Extra debugging info option
2.0.5225.30626 22-04-2014
Changes to accommodate slightly different format in Zyxel modem xlogfile
2.0.5221.19990 18-04-2014
Version 2.1 of the stats logging programs must be used with this update.
Added button to Help & About page to open Error Logs Folder.
Added link to Kitz forum for stats logging program updates.
2.0.5218.35661 15-04-2014
ZyXel VMG8324-B10A to list of modems
Enabled password entry when above modem is selected
Added check as to whether Event & Error Logs directory exists before writing GUI error file.
2.0.5207.35846 05-04-2014
Altered task detection as Windows Ultimate returns a slightly different error (Path instead of File) message when the task did not exist.
2.0.5196.35895 24-03-2014
Added check at start up to see if folders are missing
2.0.5195.37343 23-03-2014
GUI error log is now written to the Event & Error Logs folder
Xlogfile now read from Modem Log location
2.0.5190.41808 18-03-2014
Added modem log folder selection - defaults to ongoing folder location
Altered modem stats watcher to monitor location specified for modem log folder
2.0.5160.16788 16-02-2014
Added dropdown list to select modem type on modem settings tab.
-
All updated to V2.1 many thanks ;)
-
Minor update for the release version.
2.1.5251.16282 18-05-2014
Added additional information to error log when error occurs reading modem_stats.log
2.1.5249.33569 16-05-2014
Fixed unhandled exception when updating all folder names and modem log folder didn't exist.
-
I got a unhandled exception.
Procedure that caused it.
I renamed my folder when I run the stats from (made sure old service stopped first).
Copied new files over old but preserved old ini files.
Started the new gui app, which warned me folders were mismatched.
I set the folder for the first box and it asked me if I wanted the other boxes auto updates, I selected yes.
Then the unhandled exception occured, clicking continue the boxes are not auto updated.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: The directory name F:\Drivers\HG612\HG612_Modem_Stats_CURRENT\HG612\HG612_Modem_Stats_Programs-r2.0\Ongoing_Stats\ is invalid.
at System.IO.FileSystemWatcher.set_Path(String value)
at HG612_Setup.Form1.btnMainFolder_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
HG612 Stats logging GUI
Assembly Version: 2.1.5246.34669
Win32 Version: 2.1.5246.34669
CodeBase: file:///F:/Drivers/HG612/HG612_Modem_Stats_CURRENT/Scripts/HG612%20Stats%20logging%20GUI.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 11.0.50938.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
note - I just seen the above changelog, to say this bug fixed, but the app wont let me update with the mismatched folders. So Ronski I need a download link to the fixed version thanks.
-
ok another update, I renamed my folder back so I could auto update, after it updated I renamed folder again and tried to set the new path.
This time no exception error, however the auto configuration sets wrong paths (this used to work fine on old version before 2.1).
Here is the first folder which I set manually.
F:\Drivers\HG612\HG612_Modem_Stats_Programs-CURRENT
Here is what it auto configured to.
F:\Drivers\HG612\HG612_Modem_Stats_Programs-CURRENT\HG612\HG612_Modem_Stats_Programs-r2.0\Ongoing_Stats
So something broken somewhere still on this function, it somehow appended part of the old path that was set on initial execution instead of just appending '\Ongoing_Stats'
Also is the 2nd box (modem logs) supposed to be ongoing_stats or the new event & error logs folder?
-
further update. (after manually setting all folders)
Automatic stats collection works - but I had to reconfigure, my ini file was reset.
Graphd works, I can make ongoing graphs.
Snapshot graphs fails - this worked on the previous version I was using. The snapshot graph folder it creates has a plink log but no graphs.
-
Is this failure from scheduled or manual attempts to produce snapshot graphs?
Could we see your ini file, the data from GRAPH6_ERROR.LOG from when graphing fails & CURRENT_ERROR.LOG_file_ERROR.TXT from a sheduled and/or manually initiated event when snapshot graphs should have been produced, but failed?
Is the Plink log complete i.e. around 330KB in size?
EDIT:
Just another question......................
Is the snapshot graphing program (GRAPH6.exe) stuck in Task Manager?
-
I am talking about on demand when I hit the snapshot button in the gui.
graph6 doesnt get stuck.
I guess I need to enable the extra logs for those logs as they dont exist, I wanted to keep them off as is some huge logs, will turn them on and try again to get those logs.
-
okay.
With "enable extra debug info logging" ticked, I hear a beep when it runs, and the graphs work.
With that option disabled the graphs dont work ;)
when the option is disabled plink is about 57kb, with it enabled its 330kb.
The attached ini file is after I enabled extra debug info logging, rest is left alone.
-
ok another update, I renamed my folder back so I could auto update, after it updated I renamed folder again and tried to set the new path.
This time no exception error, however the auto configuration sets wrong paths (this used to work fine on old version before 2.1).
Here is the first folder which I set manually.
F:\Drivers\HG612\HG612_Modem_Stats_Programs-CURRENT
Here is what it auto configured to.
F:\Drivers\HG612\HG612_Modem_Stats_Programs-CURRENT\HG612\HG612_Modem_Stats_Programs-r2.0\Ongoing_Stats
So something broken somewhere still on this function, it somehow appended part of the old path that was set on initial execution instead of just appending '\Ongoing_Stats'
I can see why this is happening, when the GUI was written I only took into account the folders being one directory deep, so the path for the main folder replaces the first directory depth, thus retaining the rest of the directories. I've now updated the release version, so it will change the folder locations correctly, IE all the folder use the path of the main folder, so become sub folders of the main folder.
Also is the 2nd box (modem logs) supposed to be ongoing_stats or the new event & error logs folder?
You can have you modem log where you want, I prefer mine in the event and error logs folder, but the default is the ongoing folder.
Additional update to the release version today.
2.1.5251.34440 18-05-2014
Added additional information to error log when error occurs reading modem_stats.log
Minor correction to the way folder locations are updated when changing the main folder. IE all the folders use the path of the main folder, so become sub folders of the main folder.
-
okay.
With "enable extra debug info logging" ticked, I hear a beep when it runs, and the graphs work.
With that option disabled the graphs dont work ;)
Could I see your CURRENT_ERROR.LOG_file_ERROR.TXT when "enable extra debug info logging" is ticked.
I should be able to stop it beeping when it is ticked & also make the graphs work when it is unticked (but I need to see the log file first).
I don't have this issue at my end (Windows 7).
Are you running Windows 8 / 8.1?
-
I attached full logs which include old data, 18 may (today) I installed 2.1 and the last successful snapshot graph with the box ticked was done at 18:18.
Also there is 3 CURRENT_GET_DATA_ERROR files now in the scripts folder as well, did you adjust the throttling from the working version you gave me some weeks back in 2.1?
Ok I think we can ignore those 3 files, the timstamps match when I was doing manual snapshot runs so was probably conflicts.
I am running windows 7 64bit ultimate SP1.
-
<snip>
Additional update to the release version today.
2.1.5251.34440 18-05-2014
Added additional information to error log when error occurs reading modem_stats.log
Minor correction to the way folder locations are updated when changing the main folder. IE all the folders use the path of the main folder, so become sub folders of the main folder.
Thanks Ronski, updated gui. The paths are fine as is, I am leaving on the default, I just wanted to check if thats how its set default.
-
I attached full logs which include old data, 18 may (today) I installed 2.1 and the last successful snapshot graph with the box ticked was done at 18:18.
Also there is 3 CURRENT_GET_DATA_ERROR files now in the scripts folder as well, did you adjust the throttling from the working version you gave me some weeks back in 2.1?
Ok I think we can ignore those 3 files, the timstamps match when I was doing manual snapshot runs so was probably conflicts.
I am running windows 7 64bit ultimate SP1.
When snapshot graphing failed & "enable extra debug info logging" was unticked, which PC Speed setting were you using?
the xdslcmd info --linediag command made 500 attempts to get the data before quitting & generating the CURRENT_GET_DATA_ERROR-XXXXXX-XXX.TXT files.
The FAST PC Speed setting adds some pauses to slow down the PC to the speed of the modem & generating log files also slows down the PC each time a line of data is written.
I'm 'guessing' that your PC Speed setting was SLOW, which means no pauses.
That's the setting I use at my end.
Even with Extra debugging info OFF, it only takes 227 attempts to get all the linediag data.
With Extra_debugging info ON, it only takes 66 attempts.
Just in case I need to make any more allowances for FAST PCs, would you mind trying to generate the snapshot graphs with these settings in the GUI & ini file:-
PC Speed FAST
Extra debugging info OFF
Extensive error logging OFF
When you have tried that, please post the relevant data from CURRENT_ERROR.LOG_file_ERROR.TXT
If it takes anywhere near 500 attempts to get the data with those settings, I'll either increase the pauses or increase the maximum number of attempts.
From memory, I think the highest number of attempts actually made on your setup (before v 2.1) was around 400 or so.
-
it was already fast so the data you need should be in existing logs.
it still fails now e.g. if I try it without the box ticked.
Can I ask why it needs more than 1 attempt, do you forcefully close the connection after a short time or something? or is the modem rejecting connections?
-
Can I ask why it needs more than 1 attempt, do you forcefully close the connection after a short time or something? or is the modem rejecting connections?
The modem reports the stats relatively slowly.
So, even a SLOW PC tries to get the data quicker than the modem can report in one go.
Each time a pause is added, it gives the modem chance to report more data in each attempt.
Could you try the attached HG612_current_stats.exe with "enable extra debug info logging" ticked & then unticked & post the relevant parts of CURRENT_ERROR.LOG_file_ERROR.TXT for me to see what differences it has made?
We know it works on your setup with it ticked, but I have added some more pauses to see if that helps when it is unticked.
The beep should also now have stopped when "enable extra debug info logging" is ticked.
-
Ok thanks.
With it unticked I have 11 items in folder and plink is around 330kb, so looks good.
I will post the logs again.
-
That's good news.
I look forward to viewing your logs.
Just for fun, I have been updating GRAPH6.exe.
It now includes a reasonably high resolution Biits loaded & SNR combined graph as per the attachment.
I have also attached the updated version of GRAPH6.exe for use with snapshot logging, if you wish to try it out.
It still needs a little more work (The key is in the wrong place etc.)
-
Bug fix update of release version, which caused modem type to default to HG612 regardless of what was shown in the GUI in certain circumstances.
2.1.5253.9955 20-05-2014
Added code to modify Modem_Type key in ini file, should be Modem_type. This is fully automated and transparent to the user.
-
As per my post in your other thread ( http://forum.kitz.co.uk/index.php?topic=13974.msg262991#msg262991 ), I can confirm it works.
-
Couple of amendments to the beta version.
2.1.5255.33352 22-05-2014
Alteration to code that reads modem log file - experiment to see if it cures a problem one user was having, should make no difference to other users.
2.1.5253.34057 21-05-2014
Added code to correctly name new Bits with SNR graph
-
here is logs, I did both snapshots within last 2 mins, was unticked first.
-
Thanks for that Chrys.
It works, but it does slow your PC down quite a bit.
When you have a couple of minutes to spare, would you mind trying the snapshots unticked & ticked again, but with PC Speed set at MEDIUM to see what happens?
The problem here is that not having such a fast PC as yours, I'll have to rely on users such as yourself to provide data for me to get to the optimal balance between program speed & reliability.
-
its slower but not slow enough to be an issue, takes about 20 secs or so to run, I highly suggest do not speed it up, if people's pc isnt fast enough they can select slow,medium :)
-
Any old PC is fast enough. It's only really a problem with PCs that are faster than the modem.
You may find that the MEDIUM setting is sufficient to speed up the program on your PC without causing any issues.
Each pasue on MEDIUM is 0.25 seconds & it is 0.50 seconds per pause on FAST.
On the SLOW setting that I use, there are no pauses at all.
But we have seen that your PC is far to fast for that setting.
-
I will test medium and get back to you but am hoping you dont speed it up.
-
Chrys, I know you posted it before, but I cant find it atm.. what is your system?
I have an i7-3770 @ 3.4gHz 3.9GHz and the medium setting works fine on mine. Even with extensive logging on or off.
I even ran modem stats on slow for a trial period which was ok, but have decided medium is best (with the help of BE's judgement).
BE was getting regular reports and feedback on how it was coping on various settings.. and he was monitoring how long it took my system to produce stats from the logs I was sending.
-
i5-4670k clocked at 4.3ghz although it doesnt turbo up during the stats creation. Medium looks ok for snapshot.
-
According to this (http://cpuboss.com/cpus/Intel-Core-i7-3770K-vs-Intel-Core-i5-4670K), both are much of a muchness. (Depending on whether you are using just one core or all cores). Is your PC busy or does it have long periods of idle?
-
I don't wish to derail this thread, but what might be a useful comparison is to run Super Pi (attached - just extract and run) on your machines to 1 million decimal places and compare the results.
My PC here at work (Pentium G3420 @ 3.2Ghz) takes about 12.8 seconds, although the quickest has been 12.1 seconds.
It only uses a single core, and doesn't take into account hard disk speed or network speed, but I doubt that makes any difference to the logging programs, but it does give a very good indication of CPU processing speed.
Edit: My server which runs HG612 stats at home takes 17.5 seconds, which is an i3 540 @ 3.07Ghz although it probably is doing other things, but that represents normal usage.
-
in my mind snapshot performance isnt important, its important it works however.
I run it once a day auto, and it will run if the line resyncs (rare).
-
hmmm but the graphing runs several times per day in default mode?
Bearing in mind Im also what would be classed as a fast PC, I think I would prefer to work with BE to see if we can get these settings right No?
Whilst atm there appears to be only you and me that have the fast PC problems, as time progresses and more people will be updating their PCs.. so I feel its important to get this right whilst BaldEagle is kindly willing to work on it. Some people may not be so happy to see it tie up resources for as long as it does.
... go on send him your logs... they will help him to sort it this issue :)
Ive just looped during a snapshot period a short while ago.. unless we send the error logs, BE has no idea whats happening, or how best to fix it.
----------
ETA for BE's info
I've just noticed that DSLstats had crashed too - presumably that loop was what caused it.
-
Did you two run Super Pi, it'll give a good idea of how your machines compare?
-
Actually Ronski I just downloaded it and was looking at it about to run it... but atm I have a one of the progs running which I know can be a resource hog. In fact just looking I have rather a lot open atm :(... its one of the reasons why I went for the i7 cause my usage is weird.. at times the PC can be left unhindered, yet when Im working on something, a lot of those applications are hogs.
From what I can gather Chrys's should be faster on a single core, but mine faster when multi-tasking.
----
ETA
Just run it even though I do have other things running atm result = 9.453s
-
----------
ETA for BE's info
I've just noticed that DSLstats had crashed too - presumably that loop was what caused it.
Ahah. I suspected that may be the case as you started the test at 19:04:35.70 (just after DSLStats would have started sampling).
In fact, I've just asked you about it in the email I sent a minute or so ago.
-
Did you two run Super Pi, it'll give a good idea of how your machines compare?
Just for fun, I ran it at my end during a Malwarebytes full system scan that was using up to 20% CPU resource.
15.568 seconds for 1M decimal places.
-
its one of the reasons why I went for the i7 cause my usage is weird.. at times the PC can be left unhindered, yet when Im working on something, a lot of those applications are hogs.
Look Kitz you could go for i20 if there was one it won't help the weird usage, most PC's I come across to fix these days have crap right up to the hilt and when I talk about crap it's those Internet Browser plugins and the silly start up programs (3rd party) that load in the background during bootup, Don't blame MS blame the user that's my motto ;)
-
----------
ETA for BE's info
I've just noticed that DSLstats had crashed too - presumably that loop was what caused it.
Ahah. I suspected that may be the case as you started the test at 19:04:35.70 (just after DSLStats would have started sampling).
In fact, I've just asked you about it in the email I sent a minute or so ago.
Yes as soon as I saw that dslstats had crashed and not been running I realised that was most likely the case and added the extra info. Ive not downloaded my mail as Ive been distracted by other posts for the past few hours ::) will do so now :)... although tbh Im exhausted :paperbag: - which is when Im most likely to make mistakes.
-
My comments are based that I think its right to realise there be faster pcs than mine and also the software will be subject to variance sso for those reasons we shiouldnt aim to have the fast setting to run as fast as possible on my rig, I think needs to be headroom?
Also I havent been well lately, got some health issues flaring up, so in a lot of discomfort currently, hence lack of further testing.
My pc is clocked to 4.3ghz turbo, and 1600fsb ram. These chips can be clocked to over 4.8 by some people and with higher spec ram as well. Plus we factor in the graphs can be made on ssd and I have on a hdd.
Something else to report but as I said I cant do muich in terms of testing currently, the gui was left running for some days but earlier today it crashed out.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hg612 stats logging gui.exe
Problem Signature 02: 2.1.5251.34440
Problem Signature 03: 53790aa6
Problem Signature 04: System
Problem Signature 05: 4.0.30319.18408
Problem Signature 06: 52311185
Problem Signature 07: 3cb5
Problem Signature 08: 8f
Problem Signature 09: System.NullReferenceException
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
-
Chrysalis, I've found some info (http://www.codeilove.com/2012/09/debugging-using-windows-error-reporting.html) relating to the error log, but it suggests the actual error happened in 'System' so I think it's beyond my capabilities to find the cause at the moment.
-
My comments are based that I think its right to realise there be faster pcs than mine and also the software will be subject to variance sso for those reasons we shiouldnt aim to have the fast setting to run as fast as possible on my rig, I think needs to be headroom?
With the SLOW PC setting, there are no restrictions/pauses & the programs run as fast as the PC can handle.
The FAST PC setting slows the programs down the most.
I agree there should be sufficient headroom & that's what I'm trying to determine (i.e. just how much/little is actually needed).
The versions that work just fine at your end were worst case scenario.
The aim was to try different variations until we found the absolute limit of reliability & then add back in an appropriate 'safety' margin before I release an update (v 2.11) rather than simply slow everything down unnecessarily for everyone.
You & Kitz appear to have the fastest PCs of anyone using my programs that subscribes to these forums.
Your joint feedback is essential as I can't actually get the programs to fail on my slower system.
Kitz has already conducted a lot of testing for me, firing the resulting logs over accordingly for which I extend my gratitude.
We now have a clear idea of what works 'best' on her system, but she is using a different CPU than you (not overclocked) & other factors may also come into play.
Also I havent been well lately, got some health issues flaring up, so in a lot of discomfort currently, hence lack of further testing.
I'm sorry to hear that & I understand that testing programs & sending logs might be the lowest priority for you at the moment.
My pc is clocked to 4.3ghz turbo, and 1600fsb ram. These chips can be clocked to over 4.8 by some people and with higher spec ram as well. Plus we factor in the graphs can be made on ssd and I have on a hdd.
Something else to report but as I said I cant do muich in terms of testing currently, the gui was left running for some days but earlier today it crashed out.
I'm sure Ronski will look into that aspect for you & when you are feeling a bit better he might also wish to see the same logs as I do as they may give him an indication as to the cause.
I'm aiming to post updated programs this evening, so again, (when you are feeling better) it would be most helpful if you could give them a go & post/email the relevant logs for me.
-
I have attached updated v 2.11 beta test versions of HG612_stats.exe & HG612_current_stats.exe.
From testing so far, it does appear that these versions now manage things 'better' for faster PCs without too much of a program running time penalty.
Subject to any feedback received (relevant comments along with extracts from CURRENT_ERROR.LOG_file_ERROR.TXT and ONGOING_ERROR.LOG_file_ERROR.TXT), I may be be able to make further speed improvements without compromising program reliability.
The most relevant tests would be to try the various PC Speed settings (SLOW, MEDIUM, FAST) firstly with Extra debugging info logging switched ON & then again with it switched OFF.
In 'normal' & unattended everyday use, Extra debugging info logging will not be needed.
However, for testing purposes, it does need to be switched between ON & OFF to get a full picture of what is happening & whether further improvements can/need to be made.
I have also made some slight improvements to the graphing programs, but those are not relevant for these tests, so I haven't attached them.
@ Ronski:-
As this thread started off for discussions regarding your GUI, would you prefer that any further discussions regarding the data harvesting/logging programs themselves were moved to a different thread?
-
Hi BE1, it probably would be better to split the thread please.
-
Okey Dokey,
Please note:-
As this particular topic is intended for discussions regarding Ronski's GUI, any further discussions regarding the stats harvesting & graphing programs should be continued starting here:-
http://forum.kitz.co.uk/index.php?topic=13974.msg263365#msg263365
-
Hi
I am using my own scheduled task to run the hg612run.exe, and have selected "Use my own task".
I then cannot click on the buttons "Ongoing stats" and "SnapShot stats", or I can click on them but they do not switch the stats on.
I have edited the HG612_stats.ini file to enable monitoring.
Ian
-
Thanks for the bug report, I can duplicate the problem here, I'll take a look when I get chance.
-
Another small beta update, ones a bug fix the other is a tab to show program version numbers for the main programs. Currently this won't show version numbers for BE1's programs, but he is building version numbers in to the very latest programs.
Eventually we hope to have the ability to automatically update all the main programs.
2.1.5267.38646 03-06-2014
Fixed problem with Ongoing and Snapshot buttons not toggling when using own task
Added tab with program version numbers and abilty to copy to clipboard - will require programs from BE1 to have version info, which he's implementing.
-
Nevermind sorted.
-
It works for me - .Net 4.5
-
Would anybody like to volunteer to test v3 of the GUI please? If so please read the information below.
Basically I've rewritten a lot of the update code so that it now updates BE1's side of things as well.
Please be aware that when you check for beta updates, it will say that updates are available, and download them, BUT the only file which is a newer version is the modems file, the others are V3 files. So once you have the V3 files it will still always tell you there are new beta updates for the others even after updating, this is just for testing purposes.
I believe it will also handle updating programs which are running, it will wait until they close, so please try and break it,but not too much though ;-)
This beta version is not available via automated updates at the moment, but can be downloaded from here (http://www.ronski.me.uk/Downloads/HG612_Stats_logging_GUI-Beta-V3.zip) for anybody brave enough to try it, preferably if you can add it to a version 2 install of BE1's programs and see what happens please.
Important. Once testing is complete, if you used this on your live installation please delete the modems.txt file from the editor directory in the scripts folder, failure to do this will mean you'll have a version 4 file, so won't receive any new modem files until we hit version 5. The GUI will offer to download the correct file when you start it next time.
Once a few people have said everything is fine I'll add it as a general beta update, then if that's OK move it to a full release.
Any suggestions or problems then please by all means post them, thanks.
Change Log.
3.0.5294.35009 30-06-2014
Major rewrite of update interface and code, now capable of updating all the major programs.
New updater program to update all programs.
Updating is now done via the Program versions & Updates tab on the Help & About tabs.
Backups of programs are now stored in Program Backups folder in the designated scripts folder.
The old backup folder can be deleted if you want to.
Minor alterations to the About tab
Minor alterations to the help tab
PC Speed default is now Medium.
2.1.5272.39120 08-06-2014
Added code to read modems.txt list
2.1.5270.34252 06-06-2014
Created tab control on Help & About Tab
Moved program versions to Help & About tab
-
Running the Beta version of GUI V3 and don't see any problems as yet, I have uploaded an image of the GUI working away.
Not sure if i need to do anything else, I just copied the new Beta GUI into scripts folder and rename GUI version 2.1 to old.
Edit: I have just ticked the receive beta updates and installs then keeps saying there is a new one and installs it then keeps saying there is new i click ok this keeps going on it's seems stuck in a loop until i select NO do you want to install them
-
Thank you very much NewtronStar for testing it, glad to hear it works entirely as expected.
Edit: I have just ticked the receive beta updates and installs then keeps saying there is a new one and installs it then keeps saying there is new i click ok this keeps going on it's seems stuck in a loop until i select NO do you want to install them
The above is entirely expected, the version numbers listed in the version list on my server for the beta versions are higher than the ones it actually downloads, so it always thinks there are newer beta versions. I've done this purely for testing (mentioned in my previous post), although I have now edited the file so the version numbers are correct.
You'll need to delete the modems.txt file from the editor folder located in your scripts folder, when you restart the GUI it will offer to download the replacement file for you, you only need to do this once - see my previous post as to why.
-
You'll need to delete the modems.txt file from the editor folder located in your scripts folder, when you restart the GUI it will offer to download the replacement file for you, you only need to do this once - see my previous post as to why.
Yes I have done that and its does download and installs the replacement file Modems 3.0.4.0
Thanks for your reply
-
Are you sure you have version 3.0.4.0, you should have 3.0.1.0 ?
-
Are you sure you have version 3.0.4.0, you should have 3.0.1.0 ?
I think so that's what it looks like in the programs & updates :-\ have a look ->
-
Ok, strange. But this gives us a chance to test a little mod I've just made.
- Without exiting the GUI please delete the modems.txt file and refresh/update the version information
- It should show that the modems.txt file is missing, and you'll have a beta update for the GUI.
- Please then install the updates
- It should download the indicated files and replace the missing file
- Check the versions once it's restarted
You should then have modems.txt version 3.0.1.0 if all goes to plan, with no updates available.
-
I have refreshed without exiting the GUI but the modems.txt file is not showing this time ???
-
It's in the editor folder.
-
It's in the editor folder.
Yes that works removed modem.txt in the editor folder then refreshed GUI stats is says the file is missing, then I click update it then installs Modems 3.0.1.0
Thanks Ronski the little mod works :)
-
I've created a new thread for V3, it can be found here (http://forum.kitz.co.uk/index.php?topic=14162.0).
Anybody can update to V3 by selecting beta updates.