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

mstrongbow

sr. member

Activity: 322

Merit: 250

3D Printed!

Quote from: sciack on June 23, 2014, 11:51:22 PM

Quote from: mdude77 on June 23, 2014, 09:55:24 PM

Quote from: mstrongbow on June 23, 2014, 09:46:39 PM

Couldn't get the download link to work.

AWESOME app already and I am looking forward to any and all future changes.

Thanks!

Thanks! Apparently I need more sleep. I logged into my website, but forgot to actually upload the file. Should work now..

Download link: MAntMonitor22b.zip

M

May I suggest you one feature?

Since I monitor many S1's I would need that the selected row would highlight the entire row so I can see which miner has X easier.

thanks

Or perhaps move miners with alerts to the top of the monitor?

sciack

member

Activity: 115

Merit: 10

Quote from: mdude77 on June 23, 2014, 09:55:24 PM

Quote from: mstrongbow on June 23, 2014, 09:46:39 PM

Couldn't get the download link to work.

AWESOME app already and I am looking forward to any and all future changes.

Thanks!

Thanks! Apparently I need more sleep. I logged into my website, but forgot to actually upload the file. Should work now..

Download link: MAntMonitor22b.zip

M

May I suggest you one feature?

Since I monitor many S1's I would need that the selected row would highlight the entire row so I can see which miner has X easier.

thanks

allcoinminer

hero member

Activity: 784

Merit: 504

Quote from: mdude77 on June 23, 2014, 09:21:45 PM

Here's version 2.2b for those who might be interested in new features or doing some testing for me.

v2.2b
- Changed the hash rate, HFan, HTemp, and freq columns to be numeric fields so that they sort properly.
- Added a tooltip text for the Pools cell to show more pool info: pool #, URL, User, and status (Alive/Dead).
- Added the ability to keep separate userid/passwords for each Ant, one set for SSH, and one set for Web.
- Note that existing users will have all their web usernames/pws set to what you had stored there when it was just one field.
- If you need to change it for existing Ants, you can either remove it, then readd it, or edit the registry entry in HKCU\Software\MAntMonitor\Ants\RespectiveAnt
- Fixed the problem with multiple alerts for one Ant not being properly handled.

Download link: MAntMonitor22b.zip

Feedback is most welcome!

M

Great. Next we are looking for the feature to switch and edit pools. Also to keep more than 3 pools and put any of the 3 amount the pools in M'AntMinitor to Ant 3 pools field.

mstrongbow

sr. member

Activity: 322

Merit: 250

3D Printed!

Quote from: mdude77 on June 23, 2014, 09:55:24 PM

Quote from: mstrongbow on June 23, 2014, 09:46:39 PM

Couldn't get the download link to work.

AWESOME app already and I am looking forward to any and all future changes.

Thanks!

Thanks! Apparently I need more sleep. I logged into my website, but forgot to actually upload the file. Should work now..

Download link: MAntMonitor22b.zip

M

Working now. You rock as always Mdude!

~M

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: mstrongbow on June 23, 2014, 09:46:39 PM

Couldn't get the download link to work.

AWESOME app already and I am looking forward to any and all future changes.

Thanks!

Thanks! Apparently I need more sleep. I logged into my website, but forgot to actually upload the file. Should work now..

Download link: MAntMonitor22b.zip

M

mstrongbow

sr. member

Activity: 322

Merit: 250

3D Printed!

Couldn't get the download link to work.

AWESOME app already and I am looking forward to any and all future changes.

Thanks!

mdude77

legendary

Activity: 1540

Merit: 1001

Here's version 2.2b for those who might be interested in new features or doing some testing for me.

v2.2b
- Changed the hash rate, HFan, HTemp, and freq columns to be numeric fields so that they sort properly.
- Added a tooltip text for the Pools cell to show more pool info: pool #, URL, User, and status (Alive/Dead).
- Added the ability to keep separate userid/passwords for each Ant, one set for SSH, and one set for Web.
- Note that existing users will have all their web usernames/pws set to what you had stored there when it was just one field.
- If you need to change it for existing Ants, you can either remove it, then readd it, or edit the registry entry in HKCU\Software\MAntMonitor\Ants\RespectiveAnt
- Fixed the problem with multiple alerts for one Ant not being properly handled.

Download link: MAntMonitor22b.zip

Feedback is most welcome!

M

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: norgan on June 22, 2014, 08:12:37 PM

hey mdude, just some feedback.

I now have the monitor open with 1 second refresh as a live view of hash and error/reject rates. the api makes this possible.
thanks for adding that in and thanks for the updates.

Great!

M

norgan

sr. member

Activity: 308

Merit: 250

Decentralize your hashing - p2pool - Norgz Pool

hey mdude, just some feedback.

I now have the monitor open with 1 second refresh as a live view of hash and error/reject rates. the api makes this possible.
thanks for adding that in and thanks for the updates.

Grayson5

newbie

Activity: 60

Merit: 0

Hi,

I finally got version 2.1 to work and I have a question. I used the autoscan feature and it picked up my S2's as S1's. I'd like to correct that so I can config the Alerts correctly.

What's the best way to do this?

Also, it seems like when I add an additional miner manually I need to start and restart the program.

Is there a better way to do this?

Thanks.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: AbiTxGroup on June 22, 2014, 05:50:19 PM

Thanks for the program. I have been using it to monitor a bunch of S1's. I still end up using another program along with this one as it has the ability to show/change the current pool the miner is on.

I have found one thing in the sorting of columns that could use some code adjustment.

First off, I have three S1's that have some problems that alerted me to the sorting issue.

I have one S1 that has a bad temp sensor so it always shows it at 177 degrees celsius. This temp is erroneous but what I found is that with the leading "1" in the 177, it is sorted as the first temp, with the second temp listed at 43 and on up to 50. So, on my display, I see the following when the temp field is sorted "lowest-highest";

177
43
43
44
45
50

The same sorting error happens in the hashing field. I have two S1's that like to slow down their hash and when they get under "100", they are sorted at the end of the list in the "highest" spot. You can test this yourself by removing power to the blade opposite of the controller board on a S1. This will keep the miner running with only one blade hashing so it will show about "90GH/s". Instead of this sorting as the lowest number, it will be listed as the highest number.

Thanks for the program.

Thanks for the info. That's because the data is stored as text, not a number. I'll change that so you can sort properly.

M

AbiTxGroup

sr. member

Activity: 447

Merit: 250

Thanks for the program. I have been using it to monitor a bunch of S1's. I still end up using another program along with this one as it has the ability to show/change the current pool the miner is on.

I have found one thing in the sorting of columns that could use some code adjustment.

First off, I have three S1's that have some problems that alerted me to the sorting issue.

I have one S1 that has a bad temp sensor so it always shows it at 177 degrees celsius. This temp is erroneous but what I found is that with the leading "1" in the 177, it is sorted as the first temp, with the second temp listed at 43 and on up to 50. So, on my display, I see the following when the temp field is sorted "lowest-highest";

177
43
43
44
45
50

The same sorting error happens in the hashing field. I have two S1's that like to slow down their hash and when they get under "100", they are sorted at the end of the list in the "highest" spot. You can test this yourself by removing power to the blade opposite of the controller board on a S1. This will keep the miner running with only one blade hashing so it will show about "90GH/s". Instead of this sorting as the lowest number, it will be listed as the highest number.

Thanks for the program.

allcoinminer

hero member

Activity: 784

Merit: 504

Quote from: mdude77 on June 22, 2014, 01:47:26 PM

Quote from: allcoinminer on June 22, 2014, 09:15:15 AM

For miner who are active with many miners, pools, rental that feature is great.
Now I'm visiting the 192.168.x.xx many times a day just to see pools and change.

Got it. I'll see what I can do.

M

Thank you. The latest version's DIFF display feature is great.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: allcoinminer on June 22, 2014, 09:15:15 AM

For miner who are active with many miners, pools, rental that feature is great.
Now I'm visiting the 192.168.x.xx many times a day just to see pools and change.

Got it. I'll see what I can do.

M

mstrongbow

sr. member

Activity: 322

Merit: 250

3D Printed!

Quote from: sepehr on June 22, 2014, 01:26:01 PM

Quote from: mstrongbow on June 22, 2014, 12:46:29 PM

Quote from: sepehr on June 22, 2014, 03:58:29 AM

Quote from: sepehr on June 21, 2014, 11:43:17 PM

Quote from: mdude77 on June 21, 2014, 06:20:40 PM

Quote from: sepehr on June 21, 2014, 12:34:27 PM

Can you post a pic of the M's Ant Miner Ant tab? Are the rows for those Ants in question blank or have an error?

Thanks. The Alert routine wasn't properly checking to make sure that Ant row didn't have an error. But that doesn't help me determine why there's an error just yet. Is there nothing else in your log about those 4?

M

This is my complete one turn logs with your last update:

Code:

6/22/2014 9:02:29 AM: M's Ant Monitor v2.1 starting
6/22/2014 9:03:31 AM: ERROR when querying S1:14 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:03 AM: ERROR when querying S1:51 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:36 AM: ERROR when accessing API on 19.168.1.99: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 19.168.1.99:4028
6/22/2014 9:05:36 AM: ERROR when querying S2:99 (step 1): Value cannot be null.
Parameter name: s
6/22/2014 9:05:36 AM: ALERT: S1:39 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:49 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:64 exceeded 1 X count
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:42 AM: Alert email sent.

Solved!
The two S1 devices and one S2 device had old firmwares!
Updated the firmware and the problem solved now!
Thank you!

Heya mate, how might I go about checking what version firmware my S1 units are running? I am thinking one of my S1's is needing the update since it throws errors quite often.
Thanks

Check it here:

https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695

read the readme file and then install the flash file

Awesome and thanks mate! I know I could have easily googled but it's nice to get the info from someone with experience.

sepehr

sr. member

Activity: 399

Merit: 250

Cryptocurrency Evangelist

Quote from: mstrongbow on June 22, 2014, 12:46:29 PM

Quote from: sepehr on June 22, 2014, 03:58:29 AM

Quote from: sepehr on June 21, 2014, 11:43:17 PM

Quote from: mdude77 on June 21, 2014, 06:20:40 PM

Quote from: sepehr on June 21, 2014, 12:34:27 PM

Can you post a pic of the M's Ant Miner Ant tab? Are the rows for those Ants in question blank or have an error?

Thanks. The Alert routine wasn't properly checking to make sure that Ant row didn't have an error. But that doesn't help me determine why there's an error just yet. Is there nothing else in your log about those 4?

M

This is my complete one turn logs with your last update:

Code:

6/22/2014 9:02:29 AM: M's Ant Monitor v2.1 starting
6/22/2014 9:03:31 AM: ERROR when querying S1:14 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:03 AM: ERROR when querying S1:51 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:36 AM: ERROR when accessing API on 19.168.1.99: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 19.168.1.99:4028
6/22/2014 9:05:36 AM: ERROR when querying S2:99 (step 1): Value cannot be null.
Parameter name: s
6/22/2014 9:05:36 AM: ALERT: S1:39 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:49 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:64 exceeded 1 X count
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:42 AM: Alert email sent.

Solved!
The two S1 devices and one S2 device had old firmwares!
Updated the firmware and the problem solved now!
Thank you!

Heya mate, how might I go about checking what version firmware my S1 units are running? I am thinking one of my S1's is needing the update since it throws errors quite often.
Thanks

Check it here:

https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695

read the readme file and then install the flash file

mstrongbow

sr. member

Activity: 322

Merit: 250

3D Printed!

Quote from: sepehr on June 22, 2014, 03:58:29 AM

Quote from: sepehr on June 21, 2014, 11:43:17 PM

Quote from: mdude77 on June 21, 2014, 06:20:40 PM

Quote from: sepehr on June 21, 2014, 12:34:27 PM

Can you post a pic of the M's Ant Miner Ant tab? Are the rows for those Ants in question blank or have an error?

Thanks. The Alert routine wasn't properly checking to make sure that Ant row didn't have an error. But that doesn't help me determine why there's an error just yet. Is there nothing else in your log about those 4?

M

This is my complete one turn logs with your last update:

Code:

6/22/2014 9:02:29 AM: M's Ant Monitor v2.1 starting
6/22/2014 9:03:31 AM: ERROR when querying S1:14 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:03 AM: ERROR when querying S1:51 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:36 AM: ERROR when accessing API on 19.168.1.99: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 19.168.1.99:4028
6/22/2014 9:05:36 AM: ERROR when querying S2:99 (step 1): Value cannot be null.
Parameter name: s
6/22/2014 9:05:36 AM: ALERT: S1:39 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:49 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:64 exceeded 1 X count
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:42 AM: Alert email sent.

Solved!
The two S1 devices and one S2 device had old firmwares!
Updated the firmware and the problem solved now!
Thank you!

Heya mate, how might I go about checking what version firmware my S1 units are running? I am thinking one of my S1's is needing the update since it throws errors quite often.
Thanks

allcoinminer

hero member

Activity: 784

Merit: 504

For miner who are active with many miners, pools, rental that feature is great.
Now I'm visiting the 192.168.x.xx many times a day just to see pools and change.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: allcoinminer on June 22, 2014, 08:59:44 AM

The data in the red circle need to be included somewhere in the MAntmonitor.
See image http://pasteboard.co/YEVur51.jpg

Thanks for the example. However, I'm confused why you'd want to see that? None of that data changes from the time you set it, aside from whether the pool is up or down. And pool status already shows (UUU).

M

allcoinminer

hero member

Activity: 784

Merit: 504

The data in the red circle need to be included somewhere in the MAntmonitor.
See image http://pasteboard.co/YEVur51.jpg

Topic: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner - page 49. (Read 209500 times)