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

been invited out to dinner  will let u know when i get home

Beta #4 of 3.4.

This fixes the problem with the cgminer 4.6.0 update on older S3 firmware causing the API to fail.
It also fixes a bunch of little things introduced with the config UI change.
It also adds the ability to define to start/finish range for scanning for new Ants.
It also fixes the problem with Web scraping failing if you have less than 3 pools configured.  This was fixed before, but my change to add the reject rate and other fields broke it again.

This version should be pretty stable and should fix most, if not all, of the outstanding problems that have been reported to me.

Download link: MAntMonitor34b4.zip

As always, feedback is most welcome!

M

I only have One ants

Oops.  Right you are.  Try this one..

Download link: MAntMonitor34b3.zip

M

hi there M - downloaded and installed,  but now getting this error message, went in to regedit and deleted all "mantmon" related stuff - reinstalled, still getting same error.
absolutely wont let me add any new ants to the system, just keeps coming up with this error.




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

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at MAntMonitor.frmMain.AddOrSaveAntLogic(Boolean bAndNewAnt, Int32 ID)
   at MAntMonitor.frmMain.cmdAddAnt_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.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.1008 (RTMGDR.030319-1000)
    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[Suspicious link removed]
----------------------------------------
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.1001 built by: RTMGDR
    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.233 built by: RTMGDR
    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.1002 built by: RTMGDR
    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.1001 built by: RTMGDR
    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.1015 (RTMGDR.030319-1000)
    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.1015 built by: RTMGDR
    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.237 (RTMGDR.030319-2300)
    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
----------------------------------------

************** 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.

Here's another beta of v3.4.  This one has the significant Ant config UI changes I was talking about.  It is not fully tested, so there is probably something that doesn't work properly.

Each Ant now has it's own configuration for:
- Name (defaults to type: last two quads of your IP, eg, S3:0.92)
- IP Address
- SSH username, password, and port
- Web (http) username, password, and port
- Whether or not to use API or Web scraping (you should be able to mix and match - currently untested)
- API port
- Whether to reboot via SSH or via web
- Active or not

I intend to add more right click options to the output display and completely test it, but I'm out of time for the weekend.

This is a beta version, so don't be surprised if something doesn't quite work right.

I'd appreciate it if you let me know what you find plus any other feedback.

MoreBloodWine: I think this might finally work for your unique configuration, and actually save it.

Download link: MAntMonitor34b3.zip


Note: When you initially run it, it'll convert your existing Ants into the new format.  The old format remains untouched, so you should be able to revert to an older version if necessary.  The new config is stored in HKCU\Software\MAntMonitor\AntsV2.  Each entry gets a unique ID number, starting at zero.  The ID is listed on the configuration screen, so you can locate it that way, or use the registry search to find it.

M

Ok will try that Thx again

Actually I do .. probably not enough though.


There's apparently a cgminer/firmware combination out there I haven't encountered yet.  Once I get my next round of UI changes stable, I'll try a few more combinations of firmware/cgminer.  I have two S3s now, so it's a little easier, and I have some S3+ units on the way.


I doubt it's the same process.  I recommend using Kano's S1 patch.  It's not the latest version of cgminer, but it's probably newer than what Bitmain has made available.

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

M

wow You never sleep

It worked THX

Now I have 2 other questions;

1- My Ant Monitor V3.3 gives me this error since the cgminer update:

tried the beta version..no fix...

2- Did anyone updated the cgminer in their S1 s ? same procedure ? or not

The value listed there is wrong.  Back in the command prompt, run /usr/bin/cgminer-api.  Scroll to the top, the version is there.

M

Tried to update my S3s cgminer.. everything seemed ok when executing commands..

however after reboot in my system/software tab I still have the old cgminer version.....any clues ?

This.

I've been moaning on to Bitmain about this for ever. They insist on using an outdated version of cgminer in all their firmware releases, even the new S3+ - why? It's almost as if they want to keep this version for some (well known) reason......

I know people are probably sick and tired of me harping on about it, but why the hell don't Bitmain just include the latest cgminer version in their firmware?

Life would be so much easier.....

Im now running 5 of 16 on 250 - and intensively monitoring that 5 - it appears with the new cgminer (4.6) that my rigs that were at best problematic and always needing restarting at 225 and 231 are easily handling 250 and 243 now.

That might be the missing combination.  I don't think I put cgminer 4.6.0 on that firmware yet.

M

Remember i upgraded my cgminer as well to this version which makes the rigs much faster in response times -


It is valuable to note, also in doing this - my rigs have really settled down and require far less intervention.  All 16 now running this version - my S3's are batch 2 and batch 3

I'm perplexed.  I know I flashed my Ant with that version, made a one line change, and all works.  What could be different between ours?

M

Hey there,

No Joy - error come back -

"20/09/2014 11:19:56 p.m.: M's Ant Monitor v3.4b1 starting
20/09/2014 11:20:32 p.m.: Initiated Ant refresh
20/09/2014 11:20:33 p.m.: ERROR when querying S3:1.101:80 (step 1): After parsing a value an unexpected character was encountered: {. Path 'STATS[0]', line 1, position 180."

Great!

M

Try the latest beta.  I believe I added support for that version here.

Download link: MAntMonitor34b1.zip

M

I've been using this version,  antMiner_S320140721.bin - I've been doing analysis on the other 2 since this one, they are harder to operate and i like the ability to adjust the clock setting,
I've run different versions on all 16 of my miners - 4 on each release, i find overall, that that version of firmware, is the most stable, i'm getting stable mining at 7.5TH for 16 miners, or 469.82Gig average.

I like that, can live with it.  

Love your work too btw. cant wait for the next release.

Hawk