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

mdude77

legendary

Activity: 1540

Merit: 1001

Thanks everyone for the tips!

M

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: mdude77 on August 24, 2014, 12:11:41 PM

Quote from: MoreBloodWine on August 24, 2014, 12:04:58 PM

Quote from: daddyfatsax on August 24, 2014, 12:00:54 PM

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

The only thing not working is the web scraping. but M wanted to understandably work on the API first since it's what most people use. Except in cases like me with people who have machines outside of the home network that need monitoring.

I think you missed a message?

https://bitcointalksearch.org/topic/m.8513191

Web scraping works for me. But I'm not able to simulate your environment, so I'm not 100% certain it'll work with your config. Just waiting for you to try it and tell me.

M

Looks like it works, is there a way to omit the full URL and just show the IP ?

So right now the Name might look like this...

1.2.3.4:5678/cgi-bin/luci/;stok=etc. etc. etc.

I think all we rally need shown is just 1.2.3.4:5678.

Also, I noticed when web scraping these fields are blank...

Diff, Rej%, Stale%

Here's some other things I noticed.

The freq values are rounding up and not showing true values... like 237.25 shows as 238 and 243.75 shows as 244. I know this might not be a big deal to a lot of people but I'd like it if it shows true and not rounded values.

There's a few other curiosities I will touch on later, don't want to overload one reply lol

This also keeps coming up from time to time...

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Conversion from type 'DBNull" to type 'String' is not valid.

Here's details...

Quote

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Conversion from type 'DBNull' to type 'String' is not valid.
at Microsoft.VisualBasic.CompilerServices.Conversions.ToString(Object Value)
at MAntMonitor.frmMain.dataAnts_CellToolTipTextNeeded(Object sender, DataGridViewCellToolTipTextNeededEventArgs e)
at System.Windows.Forms.DataGridView.OnCellToolTipTextNeeded(DataGridViewCellToolTipTextNeededEventArgs e)
at System.Windows.Forms.DataGridView.OnCellToolTipTextNeeded(Int32 columnIndex, Int32 rowIndex, String toolTipText)
at System.Windows.Forms.DataGridViewCell.GetToolTipText(Int32 rowIndex)
at System.Windows.Forms.DataGridViewCell.OnCellDataAreaMouseEnterInternal(Int32 rowIndex)
at System.Windows.Forms.DataGridViewCell.OnMouseMoveInternal(DataGridViewCellMouseEventArgs e)
at System.Windows.Forms.DataGridView.OnCellMouseMove(DataGridViewCellMouseEventArgs e)
at System.Windows.Forms.DataGridView.UpdateMouseEnteredCell(HitTestInfo hti, MouseEventArgs e)
at System.Windows.Forms.DataGridView.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.DataGridView.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.1 (RTMRel.030319-0100)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MAntMonitor
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Owner/My%20Documents/Ant%20Monitor/MAntMonitor.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
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.1 built by: RTMRel
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.1 built by: RTMRel
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.1 built by: RTMRel
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.1 built by: RTMRel
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.1 (RTMRel.030319-0100)
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Newtonsoft.Json
Assembly Version: 6.0.0.0
Win32 Version: 6.0.4.17603
CodeBase: file:///C:/Documents%20and%20Settings/Owner/My%20Documents/Ant%20Monitor/Newtonsoft.Json.DLL
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.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:

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.

daddyfatsax

hero member

Activity: 857

Merit: 1000

Anger is a gift.

Quote from: mdude77 on August 24, 2014, 01:21:57 PM

Quote from: daddyfatsax on August 24, 2014, 01:06:04 PM

All my old S3's are still showing up in my monitor. Do I just need to delete the registry files and start over, or is there another way to delete them?

You can select them individually from the config and remove them.

Or delete/rename hkey_current_user\software\mantmonitor\ants

Another short cut for those who were using them as S1s, you can just rename the S1 entries to S3 in that subkey. If you don't feel comfortable editing the registry, you should delete them through the interface.

M

Restarting the monitor fixed it. It kicked all the S1's out and just the S3's show up now.

DimensionsOfHell

full member

Activity: 346

Merit: 100

Deleting all the S3 and testing with two, the S3 with the old FW now no longer works, but the one with the new fw does work.

So I guess I'll just upgrade all of them now.

Thanks

I'll send some tip your way for all your hard work on this project, M

bronan

hero member

Activity: 774

Merit: 500

Lazy Lurker Reads Alot

Send you the gift
Nice work on the fix

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: daddyfatsax on August 24, 2014, 01:06:04 PM

All my old S3's are still showing up in my monitor. Do I just need to delete the registry files and start over, or is there another way to delete them?

You can select them individually from the config and remove them.

Or delete/rename hkey_current_user\software\mantmonitor\ants

Another short cut for those who were using them as S1s, you can just rename the S1 entries to S3 in that subkey. If you don't feel comfortable editing the registry, you should delete them through the interface.

M

daddyfatsax

hero member

Activity: 857

Merit: 1000

Anger is a gift.

All my old S3's are still showing up in my monitor. Do I just need to delete the registry files and start over, or is there another way to delete them?

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: DimensionsOfHell on August 24, 2014, 12:58:46 PM

I'm more than fairly certain those are the ones that have the newest fw, as those are the ones I actually have issues with. They tend to slow down every few hours, and I have to restart them every few hours to get the hash back up. They rarely get to 440gh/s, and slowly crawl to mid to low 300's after a full day, so I upgraded those to see if it had any improvements. 2 of them had a slight improvement, but two still slow down a lot. I've seen one go down to the low 200's after 3 days. I don't know if it has any hardware issues that conflict with it. I can try also upgrading some other ones to see if it causes the same issues, but I suspect it'll have the same issues.

I even deleted all the old versions, then unzipped the new version and ran it. Same issue. I haven't restarted my computer in a while either, so I'll try that as well. Maybe it's an issue with my computer. I'll update this post in a bit as soon as I get some time to do all that.

Wait, I see what's wrong!

They're entered as S1s. Remove them and add them as S3s, and you should be fine.

M

DimensionsOfHell

full member

Activity: 346

Merit: 100

I'm more than fairly certain those are the ones that have the newest fw, as those are the ones I actually have issues with. They tend to slow down every few hours, and I have to restart them every few hours to get the hash back up. They rarely get to 440gh/s, and slowly crawl to mid to low 300's after a full day, so I upgraded those to see if it had any improvements. 2 of them had a slight improvement, but two still slow down a lot. I've seen one go down to the low 200's after 3 days. I don't know if it has any hardware issues that conflict with it. I can try also upgrading some other ones to see if it causes the same issues, but I suspect it'll have the same issues.

I even deleted all the old versions, then unzipped the new version and ran it. Same issue. I haven't restarted my computer in a while either, so I'll try that as well. Maybe it's an issue with my computer. I'll update this post in a bit as soon as I get some time to do all that.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: DimensionsOfHell on August 24, 2014, 12:22:38 PM

Not sure why it won't work for me. I didn't bother upgrading the rest of my S3's because of the monitoring issues.

Hope these help.

It does. Is it just those with the newest firmware "Thu Aug 7 10:56:26 CST 2014" that have the problem? Are you sure it's those that are upgraded that have the problem, and not the other way around?

I didn't bother testing it with the older firmware, just the new. It wouldn't surprise me at all if it doesn't work anything but the newest firmware.

That "unexpected character" is why it broke as an S1, that's the malformed output that the new firmware creates. I correct it before I pass it to the parsing routine, and I tried to not correct it if it wasn't necessary, but it's possible I mangled that.

M

DimensionsOfHell

full member

Activity: 346

Merit: 100

Not sure why it won't work for me. I didn't bother upgrading the rest of my S3's because of the monitoring issues.

Hope these help.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MoreBloodWine on August 24, 2014, 12:04:58 PM

Quote from: daddyfatsax on August 24, 2014, 12:00:54 PM

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

The only thing not working is the web scraping. but M wanted to understandably work on the API first since it's what most people use. Except in cases like me with people who have machines outside of the home network that need monitoring.

I think you missed a message?

https://bitcointalksearch.org/topic/m.8513191

Web scraping works for me. But I'm not able to simulate your environment, so I'm not 100% certain it'll work with your config. Just waiting for you to try it and tell me.

M

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: daddyfatsax on August 24, 2014, 12:00:54 PM

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

The only thing not working is the web scraping. but M wanted to understandably work on the API first since it's what most people use. Except in cases like me with people who have machines outside of the home network that need monitoring.

daddyfatsax

hero member

Activity: 857

Merit: 1000

Anger is a gift.

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: DimensionsOfHell on August 24, 2014, 10:54:04 AM

Is the 3.0 supposed to be working with the new S3 FW? Because it still isn't working for me. The S3's I have with the new FW show up as "ERROR".

Yes, it works for me and others. One fix I added in here was properly handling cases where the Ant doesn't respond/isn't reachable. Before it would throw nasty .Net messages.

Check the log. Maybe it'll tell you something? Maybe the addresses are wrong?

If you don't see what's wrong, can you post a screenshot of your config? Maybe it can be spotted that way.

M

DimensionsOfHell

full member

Activity: 346

Merit: 100

Is the 3.0 supposed to be working with the new S3 FW? Because it still isn't working for me. The S3's I have with the new FW show up as "ERROR".

Morblias

hero member

Activity: 576

Merit: 500

Thanks mdude77! This is amazing! I was getting annoyed logging into each and every one of my antminers to see how they were doing.

mdude77

legendary

Activity: 1540

Merit: 1001

Here's version 3.0:

v3.0
- Added support for S3 Web scraping (non API)
- Fixed a problem that would cause Ants to duplicate on their own

Download link: MAntMonitor30.zip

MoreBloodWine: Give this a whirl. Since I can't replicate your environment, I'm not sure this will work. If it doesn't, hopefully I can work through it.

M

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: PatMan on August 24, 2014, 06:48:44 AM

OK, I think it's because you're using the set diff (+512) command - I'm letting p2pool decide the diff (I found no advantage in manually setting it).

Try it out Wink

You're right. That's odd, especially since my S1 doesn't mind it.

M

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

OK, I think it's because you're using the set diff (+512) command - I'm letting p2pool decide the diff (I found no advantage in manually setting it).

Try it out Wink

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