Topic: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner - page 3. (Read 209595 times)
September 03, 2015, 02:10:43 PM
ok so I updated cgminer in my s3 to 4.9.2 from 4.6.? and now miner dosnt show up any more...did some thing change? is there a port I need to add now or something?
September 02, 2015, 10:58:57 PM
might I suggest an alert mesg for when a miner finds a block! if that gets added I will donate to the cause.
other then that this is a great program!
other then that this is a great program!
September 01, 2015, 01:04:06 AM
Try the latest beta. It fixes this problem for the S3s, and it should for the S5s.
MMinerMonitor53b1.zip
Note that I've never physically had an S5 in my possession. That combined with very limited time can make supporting every single little change an iffy proposition.
MMinerMonitor53b1.zip
Note that I've never physically had an S5 in my possession. That combined with very limited time can make supporting every single little change an iffy proposition.
It works!
Thanx!
p.s. did I say it's S5? It's S2, sorry.
August 22, 2015, 03:21:09 PM
Updated to Kano's latest cgminer [CGMiner] => 4.9.2, [API] => 3.6, details at link below.
https://github.com/kanoi/cgminer-binaries/tree/master/AntS3
Web interface works fine as does being able to SSH from PuTTy, but Miner Monitor (V5,2) can't access. Worked fine before I upgraded cgminer and the other 4 S3s work fine. All are configured the same except for IP address. Any suggestions to fix?
Always shows just 4 out of 5 responding
https://github.com/kanoi/cgminer-binaries/tree/master/AntS3
Web interface works fine as does being able to SSH from PuTTy, but Miner Monitor (V5,2) can't access. Worked fine before I upgraded cgminer and the other 4 S3s work fine. All are configured the same except for IP address. Any suggestions to fix?
Always shows just 4 out of 5 responding
August 20, 2015, 01:36:05 AM
mmonitor s5 sees, but sp20 not sees. Settings in the image below. help me.
Uncheck the "Use API" box and check the "HTTPS" box in order for it to work with SP20s. Good luck!
August 18, 2015, 01:17:38 PM
ERROR when querying S3:1.200 (step 1.4): Arithmetic operation resulted in an overflow.
its only on one s3, and that s3 is set to balanced on the pools..
does this app not support balanced?
its only on one s3, and that s3 is set to balanced on the pools..
does this app not support balanced?
I have the same error with mines. Regardless of how the pool setting is set. Its something else, as most people units seem to work just fine with Kano. Please let me know if you find what it is ..
August 16, 2015, 08:41:07 PM
ERROR when querying S3:1.200 (step 1.4): Arithmetic operation resulted in an overflow.
its only on one s3, and that s3 is set to balanced on the pools..
does this app not support balanced?
its only on one s3, and that s3 is set to balanced on the pools..
does this app not support balanced?
August 05, 2015, 04:20:38 PM
Features:
- Look at all your Bitmain Ants (S1/S2/S3/S4/S5/C1)
M
Then what can the matter be with my S5 and M's Miner Monitor 5.0 and 5.2?
https://bitcointalksearch.org/topic/m.12040882
Try the latest beta. It fixes this problem for the S3s, and it should for the S5s.
MMinerMonitor53b1.zip
Note that I've never physically had an S5 in my possession. That combined with very limited time can make supporting every single little change an iffy proposition.
M
I will try the software and report results when i get my S5.
Curiosity, are you strictly working on this in vb? I was kinda hoping to get similar software in Python for me to mess around with.
VB.Net to be precise.
There are other miner monitoring apps out there. Maybe one of them uses Python and has source code available?
M
And I didn't find one. To be honest, yours is built better. I'm just more familiar to building logic on Python, i'm not sure how it would be in VB.
Regardless i'll wait for the S5 and then i'll see if i feel like poking around stuff.
August 05, 2015, 04:15:07 PM
Features:
- Look at all your Bitmain Ants (S1/S2/S3/S4/S5/C1)
M
Then what can the matter be with my S5 and M's Miner Monitor 5.0 and 5.2?
https://bitcointalksearch.org/topic/m.12040882
Try the latest beta. It fixes this problem for the S3s, and it should for the S5s.
MMinerMonitor53b1.zip
Note that I've never physically had an S5 in my possession. That combined with very limited time can make supporting every single little change an iffy proposition.
M
I will try the software and report results when i get my S5.
Curiosity, are you strictly working on this in vb? I was kinda hoping to get similar software in Python for me to mess around with.
VB.Net to be precise.
There are other miner monitoring apps out there. Maybe one of them uses Python and has source code available?
M
August 05, 2015, 04:13:47 PM
Features:
- Look at all your Bitmain Ants (S1/S2/S3/S4/S5/C1)
M
Then what can the matter be with my S5 and M's Miner Monitor 5.0 and 5.2?
https://bitcointalksearch.org/topic/m.12040882
Try the latest beta. It fixes this problem for the S3s, and it should for the S5s.
MMinerMonitor53b1.zip
Note that I've never physically had an S5 in my possession. That combined with very limited time can make supporting every single little change an iffy proposition.
M
I will try the software and report results when i get my S5.
Curiosity, are you strictly working on this in vb? I was kinda hoping to get similar software in Python for me to mess around with.
August 05, 2015, 04:10:55 PM
Features:
- Look at all your Bitmain Ants (S1/S2/S3/S4/S5/C1)
M
Then what can the matter be with my S5 and M's Miner Monitor 5.0 and 5.2?
https://bitcointalksearch.org/topic/m.12040882
Try the latest beta. It fixes this problem for the S3s, and it should for the S5s.
MMinerMonitor53b1.zip
Note that I've never physically had an S5 in my possession. That combined with very limited time can make supporting every single little change an iffy proposition.
M
August 05, 2015, 04:08:11 PM
So i'm trying to use this with S1. Whether via shh or api, MMM never try to reboot them because of this error;
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
This has been reported before. There's apparently something awry with that logic that I have not had time to look at.
Quote
Is there a .conf i can mess around with somewhere? I dont see it in appdata or my documents and i'd really like to be able to control them remotely!
The settings are stored in the registry. See my first post - the data is stored in HKEY_CURRENT_USER\Software\MAntMonitor
M
Ahah. Thank you for enabling my lazy ass and giving me a quick reply.
I manually edited the value DoNotReboot for all miners to N and it works like a charm.
So the bug must be when you register a miner, the value is always set to Y whether Do Not Reboot is checked or not.
That's good to know, thanks!
M
August 03, 2015, 10:53:39 PM
Features:
- Look at all your Bitmain Ants (S1/S2/S3/S4/S5/C1)
M
Then what can the matter be with my S5 and M's Miner Monitor 5.0 and 5.2?
https://bitcointalksearch.org/topic/m.12040882
August 01, 2015, 06:12:17 PM
So i'm trying to use this with S1. Whether via shh or api, MMM never try to reboot them because of this error;
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
This has been reported before. There's apparently something awry with that logic that I have not had time to look at.
Quote
Is there a .conf i can mess around with somewhere? I dont see it in appdata or my documents and i'd really like to be able to control them remotely!
The settings are stored in the registry. See my first post - the data is stored in HKEY_CURRENT_USER\Software\MAntMonitor
M
Ahah. Thank you for enabling my lazy ass and giving me a quick reply.
I manually edited the value DoNotReboot for all miners to N and it works like a charm.
So the bug must be when you register a miner, the value is always set to Y whether Do Not Reboot is checked or not.
August 01, 2015, 04:45:09 PM
So i'm trying to use this with S1. Whether via shh or api, MMM never try to reboot them because of this error;
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
This has been reported before. There's apparently something awry with that logic that I have not had time to look at.
Quote
Is there a .conf i can mess around with somewhere? I dont see it in appdata or my documents and i'd really like to be able to control them remotely!
The settings are stored in the registry. See my first post - the data is stored in HKEY_CURRENT_USER\Software\MAntMonitor
M
August 01, 2015, 03:42:15 PM
So i'm trying to use this with S1. Whether via shh or api, MMM never try to reboot them because of this error;
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
Is there a .conf i can mess around with somewhere? I dont see it in appdata or my documents and i'd really like to be able to control them remotely!
01/08/2015 4:20:51 PM: Reboot of 1S7 requested
01/08/2015 4:20:51 PM: Not rebooting 1S7 because it is marked as Do Not Reboot
Whether i add the miner with Do Not Reboot checked or not, it always report the same error.
Is there a .conf i can mess around with somewhere? I dont see it in appdata or my documents and i'd really like to be able to control them remotely!
July 30, 2015, 02:05:21 PM
Just tried the cyrptoglance monitoring software, and it works with the new S3 binaries from Kano. Not sure why it works, but it does.
July 25, 2015, 02:35:32 PM
I'am a newbie and try as best to keep up with you guys here. Learned so much in a short time, thank you. S3's where factory reset when received and updated to generic bitmain firmware S320150109.bin. Then per Kano post on on GitHub AntS3 4.9.2 94e04f6-3. I noticed something odd when using putty. I'm first presented with BusyBox v1.19.4 (2014-11-21 11:07:01 CST) built-in shell and a OPENWRT Barrier Breaker banner! Not sure if these are trace left from previous firmware. Perhaps that may be the cause.
I'm not on top of bitmain firmware. My suggestion would be to apply the latest firmware from Bitmain, and then apply Kano's cgminer update.
I have very little good to say about Bitmain hardware. Usually, however, the latest firmware is best.
M
Thanks M I will give this a try with some power cycle in between as per KANO
July 25, 2015, 08:24:58 AM
I'am a newbie and try as best to keep up with you guys here. Learned so much in a short time, thank you. S3's where factory reset when received and updated to generic bitmain firmware S320150109.bin. Then per Kano post on on GitHub AntS3 4.9.2 94e04f6-3. I noticed something odd when using putty. I'm first presented with BusyBox v1.19.4 (2014-11-21 11:07:01 CST) built-in shell and a OPENWRT Barrier Breaker banner! Not sure if these are trace left from previous firmware. Perhaps that may be the cause.
I'm not on top of bitmain firmware. My suggestion would be to apply the latest firmware from Bitmain, and then apply Kano's cgminer update.
I have very little good to say about Bitmain hardware. Usually, however, the latest firmware is best.
M
July 25, 2015, 03:19:32 AM
Here is a beta of v5.3 that I believe will get the hash rate to display again for S3s after you've applied Kano's firmware. Note that I do not have any mining hardware at all at my disposal for testing, so I've tested this, but obviously not as well as I could if I had a physical S3 on hand.
Please let me know how it goes.
Download link: MMinerMonitor53b1.zip
M
Please let me know how it goes.
Code:
File: MMinerMonitor53b1.zip
CRC-32: f844a92e
MD4: b28bb390fd6d1cbf9e0149e7ac381380
MD5: 430cb4f7f475721f81690e61a908cf8c
SHA-1: d9c32098376ff724980175adeaeb27f8d17a267e
Download link: MMinerMonitor53b1.zip
M
M -- I'm still getting an error trying to add an S3 Kano updated into ms miner. Log show.. the following Arithmetic operation resulted in an overflow. Any idea ? .. Thanks
Are you using the latest firmware as well as Kano's cgminer update?
It seems to be working for others, so I'm not sure what makes yours different.
M
My S3 update steps change both.
You can also just redo the update steps but first power cycle it to be sure the overlay is correct.
Also make sure to save the settings again from both the settings pages after you've upgraded to my version or if you removed my version and downgraded to the bitmain version - just in case.
I'am a newbie and try as best to keep up with you guys here. Learned so much in a short time, thank you. S3's where factory reset when received and updated to generic bitmain firmware S320150109.bin. Then per Kano post on on GitHub AntS3 4.9.2 94e04f6-3. I noticed something odd when using putty. I'm first presented with BusyBox v1.19.4 (2014-11-21 11:07:01 CST) built-in shell and a OPENWRT Barrier Breaker banner! Not sure if these are trace left from previous firmware. Perhaps that may be the cause.
Jump to: