Thanks.  I wasn't planning on adding additional functionality to the old style screenscraping process.  What exactly do you need this for that isn't on the API side?

M

Oops!  Good idea.  I added that in M's Pool Monitor, forgot to implement it here.

M

At the moment I'm not selling them.  They are just collecting.  The hope is someday there will be enough to sell and distribute, and/or they get valuable enough to sell.

M

I'll look, I think it's in the API.

M

If I understand it correctly, the payout queue is based on the age of the payout since that payout started.  So your minimum payout really doesn't mean anything if it's set too low, others who took longer to get to the queue will pop ahead of you, until your payout gets old enough to be ahead of everyone else.

For me the magic time period seems to be around 3 days.  I have my min value set to trigger around 2 days, but I end up getting paid on the 3rd day, roughly.

M

No there isn't.  I'm using Microsoft's built in SMTP support, which, in Microsoft fashion, works best (or only?) with Microsoft servers.  Sometime I may write my own code for it, but time is one thing I don't have a lot of anymore.

M

Notes on email logic:

- My 2.0 release missed a step, the code was there, but not referenced.  2.0a has it.
- Last I tested this, it didn't work with all SMTP servers.  It worked with Google's servers, but not Verizon's.  Didn't have any others to check.
- There aren't any governors on the email logic to prevent "spam".  That means if it's set to check your ants every 5 minutes, and there's an alert every 5 minutes, you'll get an email every 5 minutes.  You might want to enable the email feature with caution!   I intend to add a governor "only send an email once every x minutes" in next version.

M

It does that already!  Added in v1.9 I believe.

M

Yes, I realized this morning that I added the code, but forgot to reference it!   Just put out an update to fix that..

Download link: MAntMonitor20a.zip

Will look at that logic, must have missed something.  Thanks!

M

Thanks!

I almost have 0.1 BTC worth!

M

I just published v2.0.  In light of the odd errors some folks are having with the new alert logic, this version was published before SSH support was added.

v2.0
- Added more errorhandling and logging, especially around the new alert logic.  
- Added email support.  This is untested (in the interest of time), but working code that came M's Pool Monitor.

Download link: MAntMonitor20a.zip

PLEASE NOTE:

Assuming no additional odd errors come up, next version should have SSH and reboot functionality.  After that, unless there is some really feature that folks are looking for that I overlooked, I need to move on to my next project for some time.  So if you have a feature request that I've missed, please speak up!

M

The annoying popup is a separate window that comes up when there's an error, and it tries to get your attention.  It could probably be more annoying..

M

What newcomers to p2pool usually don't immediately grasp is there are two types of shares in p2pool.  The type that you see your miner submitting all the time, and the type that really count. It's the second type that you aren't getting many of.

To elaborate, p2pool uses an "alt chain" of shares to keep track of who's submitted shares.  You can consider that "alt chain" to be like another coin, with a much much lower difficulty.  p2pool adjusts the difficulty required to get on that chain so that miners are getting shares on the chain roughly 30 seconds.  (I think that's the number, the wiki might be outdated).  That means the more people there are mining, the faster shares are found, so difficulty goes up.

Right now that share difficulty is at 1,809,778.  Your 171gh/s needs to find a share of that value or greater (at the time of this post), to get on that chain.  That's why it's estimating it'll take you 12.6 hours to find a share.

The good news is once you get a share, it's good for 3 days.  So, at current numbers, making it 12 hours per share to make it easy, you should have 6 shares on the chain at any given point, assuming average luck.  That's where variance comes in ... sometimes that number will be higher, sometimes that number will be lower.

M

It doesn't do anything itself.  It just tells Windows to run it.  So anything your PC supports should work.

There must be some logic flow I missed in there.

Thanks for the report.  I suspect once you pick something, it'll work fine?

M

I have some ideas. 

M

Looks like something funny is up with 51.  I did put error handling around an ant not responding properly, but I didn't fully test it.  Does everything seem normal with 51?

M

Is that part I put in bold accurate?  Most pools, to my knowledge, pay entirely based on luck.

M

Also... SSH functionality for auto reboots and on demand reboots is planned for next version.

M


P.S.  Happy Father's day to the dads out there!

Also, I'm looking for feedback from folks on the alert functionality.  Please let me know what you think, including anything you'd like to see added/changed. 

Thanks!

M

I just published v1.9.

v1.9
- Added basic alert functionality:
   - You can trigger alerts on Fan speed being too high, Hash speed being too low, Temperature being too high, or XCount too High.
   - There are separate thresholds for S1s and S2s.
   - Alerts can show a notification popup from the notification bar (on by default), an annoying separate window popup (off by default), highlight the field that triggered the alert (on by default), and/or start a process (off by default). 
   - The process can be anything Windows recognizes that you can run from the Start menu, like a sound clip.
   - Alerts only apply to queries done via the API.  The web (screen scrape) functionality does not have it, and unless someone says they need it, I likely won't be adding it. 
   - Alerts counts also show in the title bar.
- This now uses a notification icon and will minimize to your notification bar when you close it.  To exit it, right click it and click Exit.
- Fixed a problem that could cause an infinite loop if an Ant partially responded to an API request.
- Added more text to the title bar, indicating how many Ants responded to the poll request.




Download link: MAntMonitor19.zip


Note: I intend to add more alert functionality as well (like email alerts - same as I have in M's Pool Monitor), but this is all I had time for this weekend.

M