M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner

[mdude77]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

[MoreBloodWine]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone.

Ty.

[mdude77]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone.

Ty.

It doesn't fix most of your issues.  That's coming when I redo the config UI.

M

[MoreBloodWine]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone.

Ty.

It doesn't fix most of your issues.  That's coming when I redo the config UI.

M

Gotcha, thx for all your hard work ;-)

[mdude77]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone.

Ty.

It doesn't fix most of your issues.  That's coming when I redo the config UI.

M

Gotcha, thx for all your hard work ;-)

It should fix your "it doesn't reboot" problem though.

M

[MoreBloodWine]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone.

Ty.

It doesn't fix most of your issues.  That's coming when I redo the config UI.

M

Gotcha, thx for all your hard work ;-)

It should fix your "it doesn't reboot" problem though.

M

Cool, well here's hoping I don't need to find out since I haven't seen any X's since. Which kinda sucks for being able to test it lol

[wlz2011]

I'm declaring 3.2 stable enough to publish.

v3.2
- Fixed the problem with not being able to save the config if you've never used it before.
- Changed to query the Ants via the API on background threads.  The numbers of threads is configurable.  The more Ants you have, the higher you likely want
  this value to be.  It defaults to 4.
- Changed to refresh the display grid X numbers of seconds after the Ant refresh has started.  This value is configurable. If you have a large number of 
  Ants, or have slow video, you'll benefit from setting this to a larger value.  It defaults to 1.
- Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory.
- Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters.

Download link: MAntMonitor32.zip

M

[mdude77]

(pictures)

Are all your ants at the latest firmware?  I've been told it doesn't work with older firmware.  I suppose I could flash my firmware back a version and see if I can address that.

M

Actually, I think you're saying when they are entered without the leading zeros, they work.  Otherwise they do?

M

[mdude77]

I confirmed, for some reason the microsoft tcpclient doesn't know what a leading zero is in IP address.

I should be able to fix this quickly.

M

[mdude77]

Here's v3.3. 

This fixes the problem with leading zeros in Ant addresses not working.  ie, 192.168.000.091 doesn't work, but 192.168.0.91 does.
This also starts the process of removing the theoretical code to support DNS addresses instead of pure IP addresses.

Download link: MAntMonitor33.zip.

M

[norgan]

I only have two ants but I have the refresh set at 1 second. since the update to 3.3 I get every second response only 1 of 2 responded.

[mdude77]

I only have two ants but I have the refresh set at 1 second. since the update to 3.3 I get every second response only 1 of 2 responded.

Try setting the display delay to 0.

M

[norgan]

I only have two ants but I have the refresh set at 1 second. since the update to 3.3 I get every second response only 1 of 2 responded.

Try setting the display delay to 0.

M

do you mean the refresh every: or Display refresh?

Currently I have refresh every 1 seconds and display refresh 0

[mdude77]

I only have two ants but I have the refresh set at 1 second. since the update to 3.3 I get every second response only 1 of 2 responded.

Try setting the display delay to 0.

M

do you mean the refresh every: or Display refresh?

Currently I have refresh every 1 seconds and display refresh 0

I think you might have to change your refresh to every 2 seconds.  Prior to the multithreaded change, the "responded" message would be based on the round of checking all the Ants.

Now there's no longer a round.  Each time an Ant refresh completes, it checks to see how many have "" and that becomes the responded message.  Because you're running every second, there will be times when one has because it was just submitted.

M

[wlz2011]

V3.2b version of the test results
253 ants around 10-12 seconds to refresh
No problems to found.

V3.2b2,V3.2 official version of the test results
I set up 24 threads, refresh time: 5-10 seconds
It can not work properly, and many machines are not shown.
Totally confused, half machine can not be found.
Please correct this problem, the speed does not necessarily to be very fast.
Stable and effective work is the best.

Mr. M, thank you for your hard work always.

[mdude77]

V3.2b version of the test results
253 ants around 10-12 seconds to refresh
No problems to found.

V3.2b2,V3.2 official version of the test results
I set up 24 threads, refresh time: 5-10 seconds
It can not work properly, and many machines are not shown.
Totally confused, half machine can not be found.
Please correct this problem, the speed does not necessarily to be very fast.
Stable and effective work is the best.

Mr. M, thank you for your hard work always.

Hello, see version 3.3.  It addresses the issue with Ants not found when you enter the addresses with leading zeros, which you did by my suggestion for them to sort properly.

MAntMonitor33.zip

M

[shadow2]

When using the non-api method to get the info I get in the log - and nothing in the ants tab

"04/09/2014 10:49:09: S3:1.102:80 responded with status page
04/09/2014 10:49:09: An error occurred when parsing the web output for http://192.168.1.102/cgi-bin/luci/;stok=/admin/status/minerstatus/: Object reference not set to an instance of an object."

It appears using that link even if you are logged in to your Ant it wants you to log in again

I know it's easy enough to swap to API, but if you swap from API to web then api (and then in this case back to web) the Ant section gets filled with error details rather than overwriting the bad one

http://oi61.tinypic.com/2wnsoc8.jpg

[mdude77]

When using the non-api method to get the info I get in the log - and nothing in the ants tab

"04/09/2014 10:49:09: S3:1.102:80 responded with status page
04/09/2014 10:49:09: An error occurred when parsing the web output for http://192.168.1.102/cgi-bin/luci/;stok=/admin/status/minerstatus/: Object reference not set to an instance of an object."

You're the 2nd person to report this.  I must have something broken there.  Is this an S1 or S3?

M

[shadow2]

S3  - would the login page that initially comes up in place of the status page cause the error?

[mdude77]

S3  - would the login page that initially comes up in place of the status page cause the error?

No, that's expected.

M