Pages:
Author

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

legendary
Activity: 1540
Merit: 1001
Hey M, I've been thinking about this.

Even with me using the latest FW, I should still be able to web scrape right ? I mean, AFAIK it's just the SSH API the new FW messes up. That said, just how do I enter my IP ? I saw presets like 1.2.3.4:5678 & 1.2.3.4:5678:80, hell, even 1.2.3.4:5678:80:80

I tried both 1.2.3.4:5678 & 1.2.3.4:5678:80 and don't seem to be getting any info with S1 or S2.

All my IP's are like this as I previously stated.

1.2.3.4:2013
1.2.3.4:2014
1.2.3.4:2015
1.2.3.4:2016

Screenscrapes won't work if the screen isn't like an S1 or S2.  And I don't think it is.

Sad

M
legendary
Activity: 1064
Merit: 1001
Hey M, I've been thinking about this.

Even with me using the latest FW, I should still be able to web scrape right ? I mean, AFAIK it's just the SSH API the new FW messes up. That said, just how do I enter my IP ? I saw presets like 1.2.3.4:5678 & 1.2.3.4:5678:80, hell, even 1.2.3.4:5678:80:80

I tried both 1.2.3.4:5678 & 1.2.3.4:5678:80 and don't seem to be getting any info with S1 or S2.

All my IP's are like this as I previously stated.

1.2.3.4:2013
1.2.3.4:2014
1.2.3.4:2015
1.2.3.4:2016
legendary
Activity: 1540
Merit: 1001
I think it may be related to this - the info on your ants is stored in the registry I had so many that it refused to work so I had to track down where the data was kept

if you turn off the API option itll help to get some stuff though to the monitor


The 2.8 version catches everything - i used for the original setup when i was experimenting and deleting etc.  think it may be something in the registry.

I'm pretty sure there's a problem in the upgrade code. 

That, however, has nothing to do with S3s no longer working.  With the new firmware, they are no longer "just like an S1, only faster". 

M
member
Activity: 73
Merit: 10
got some input in to the monitor -

its remembering everything and i cant delete stuff out - still shows in the "ants" even when i delete and save the config.

With which version are you seeing this?  The screenshot you have shows an older version.

Quote
under the name - can we get an edit facility?

so instead of 192.168.1.101 - just rename it to "101 GALACTICA"  - this would be a good feature Wink

so ur ants list looks like



101 GALACTICA
102 ATHENA
103 ATLANTIA
104 PEGASUS

Neat idea. 

M

I think it may be related to this - the info on your ants is stored in the registry I had so many that it refused to work so I had to track down where the data was kept

if you turn off the API option itll help to get some stuff though to the monitor


The 2.8 version catches everything - i used for the original setup when i was experimenting and deleting etc.  think it may be something in the registry.
legendary
Activity: 1540
Merit: 1001
got some input in to the monitor -

its remembering everything and i cant delete stuff out - still shows in the "ants" even when i delete and save the config.

With which version are you seeing this?  The screenshot you have shows an older version.

Quote
under the name - can we get an edit facility?

so instead of 192.168.1.101 - just rename it to "101 GALACTICA"  - this would be a good feature Wink

so ur ants list looks like



101 GALACTICA
102 ATHENA
103 ATLANTIA
104 PEGASUS

Neat idea. 

M
sr. member
Activity: 362
Merit: 250
2 of my S3's have the Aug 11th firmware and I am using Antmonitor2.0 and they show up just like S1.
newbie
Activity: 17
Merit: 0
the info on your ants is stored in the registry I had so many that it refused to work so I had to track down where the data was kept

if you turn off the API option itll help to get some stuff though to the monitor
legendary
Activity: 1202
Merit: 1181
I am getting an error with new firmware antMiner_S320140811.bin. I flashed one unit just to see if it was better or worse. Now the one S3 I flashed is not showing up in the monitor. I am have used 2.6a and 2.6, but it will not show up in either.

Needs a fix for the newer firmware... won't get that until the author gets his hand on an S3 to run some testing. Hopefully soon Smiley
hero member
Activity: 857
Merit: 1000
Anger is a gift.
I am getting an error with new firmware antMiner_S320140811.bin. I flashed one unit just to see if it was better or worse. Now the one S3 I flashed is not showing up in the monitor. I am have used 2.6a and 2.6, but it will not show up in either.
member
Activity: 73
Merit: 10
got some input in to the monitor -

its remembering everything and i cant delete stuff out - still shows in the "ants" even when i delete and save the config.

under the name - can we get an edit facility?

so instead of 192.168.1.101 - just rename it to "101 GALACTICA"  - this would be a good feature Wink

so ur ants list looks like



101 GALACTICA
102 ATHENA
103 ATLANTIA
104 PEGASUS



this is way easier to recognise Cheesy
and the ability to delete a machine out of the "ants"  display - right clik and delete.

I love my 2.6~!!! Cheesy
member
Activity: 91
Merit: 10
It only gets better and better.. thanks a bunch!!! Smiley
legendary
Activity: 1540
Merit: 1001
Hey M, were you ever able to get and S3 ordered ? Saw one guy here in this thread offer ya a loan.

I'm having a very hard time finding one outside of eBay/Amazon.  I have some PMs out that folks haven't responded to yet.  Another day or two and I'll give up and buy one from eBay/Amazon. Sad

M
legendary
Activity: 1064
Merit: 1001
Hey M, were you ever able to get and S3 ordered ? Saw one guy here in this thread offer ya a loan.
legendary
Activity: 1540
Merit: 1001
Here's v2.8:

v2.8
- Fixed the problem with one of the saves duplicating the Ants.
- Added the ability to reboot your Ant if it triggers a low/high hash alert.

Download link: MAntMonitor28.zip

M
legendary
Activity: 1064
Merit: 1001
Just published v2.7:

v2.7
- Fixed a problem with the web code that would trigger if you have less than 3 Ants.
- Fixed multiple problems with the web reboot code.  I don't see how it would have ever worked.  Apparently I broke this at some point.
- Added more exception handling logic to hopefully catch odd errors instead of throwing the awful .Net default messages.
- Hopefully addressed some issues that would occur if you entered your Ant's DNS name (antminer1) instead of the IP address.  This is theoretical
  functionality, for best results use an IP address.
- Changed to use the last two parts of the IP address (0.90) instead of the last part (90) to allow you to have Ants on multiple subnets without
  them walking on each other.  That is, 192.168.0.90 and 192.168.0.91 will now work properly.
- Changed to use and store the port of the Ant address, so those using the Web scraping API on a non standard port will still be able to use it.  Enter the address as 192.168.0.91:port if you're using a nonstandard port.
- Changed the pushing of pool info to work if you don't have all 3 pools populated. 


Download link: MAntMonitor27.zip

There were some decent changes in here, it's possible I missed something.  Feedback is always welcome.

M
I would love to use his but have the new FW on all of my S3's ;-(
legendary
Activity: 1540
Merit: 1001
I found one minor problem, I think in certain circumstances, when you save your settings it'll duplicate your ant listing, so everything shows up twice.

M
legendary
Activity: 1540
Merit: 1001
Just published v2.7:

v2.7
- Fixed a problem with the web code that would trigger if you have less than 3 Ants.
- Fixed multiple problems with the web reboot code.  I don't see how it would have ever worked.  Apparently I broke this at some point.
- Added more exception handling logic to hopefully catch odd errors instead of throwing the awful .Net default messages.
- Hopefully addressed some issues that would occur if you entered your Ant's DNS name (antminer1) instead of the IP address.  This is theoretical
  functionality, for best results use an IP address.
- Changed to use the last two parts of the IP address (0.90) instead of the last part (90) to allow you to have Ants on multiple subnets without
  them walking on each other.  That is, 192.168.0.90 and 192.168.0.91 will now work properly.
- Changed to use and store the port of the Ant address, so those using the Web scraping API on a non standard port will still be able to use it.  Enter the address as 192.168.0.91:port if you're using a nonstandard port.
- Changed the pushing of pool info to work if you don't have all 3 pools populated. 


Download link: MAntMonitor27.zip

There were some decent changes in here, it's possible I missed something.  Feedback is always welcome.

M
newbie
Activity: 17
Merit: 0
nope same program you just say your S3 is a S1.  as it says they are almost the same (or at least were until this latest S3 firmware)
legendary
Activity: 1593
Merit: 1004
Is there a new download link for this program?  I downloaded from the link on the OP but the version just appears to support S1 and S2.  Or I'm just dumb.
newbie
Activity: 17
Merit: 0
M

I've managed to get a new S3 firmware version antminer to talk to your program by unchecking the USE API box.

in my log  when starting up

"6/08/2014 20:24:24: M's Ant Monitor v2.6a starting
16/08/2014 20:25:27: Initiated refresh
16/08/2014 20:25:27: ERROR when querying S1:101 (step 1): After parsing a value an unexpected character was encountered: {. Path 'STATS[0]', line 1, position 212."

got the same when I tried rechecking the USE api box.

managed to reboot the S3 even thought it's not using the API

hope this helps

in mm when requesting version type

"Request":"version","Response":"STATUS=S,When=1408218399,Code=22,Msg=CGMiner versions,Description=cgminer 3.12.0|VERSION,CGMiner=3.12.0,API=3.1,Miner=7.0.0.3,CompileTime=Thu Aug  7 10:56:26 CST 2014,Type=S3|\u0000","CoinName":"","Machine":"192.168.1.101:4028"}

in comparison to an unupdated one
"Request":"version","Response":"STATUS=S,When=1408218579,Code=22,Msg=CGMiner versions,Description=cgminer 3.12.0|VERSION,CGMiner=3.12.0_7.0.0.3,API=3.1|\u0000","CoinName":"","Machine":"192.168.1.102:4028"}

if my count is right it's something in the bold above I'd expect "S3" is the issue


Pages:
Jump to: