I'm also interested in coupons, 2 or 3.  If you don't need them, or are willing to part with them, please PM me your offer, or if you're feeling really generous, I'm mdude on bitmaintech.

I'm going to be away for most of today, probably returning right when sales open. which is about 4 hours after sales open.  I hope there are some left.

Thanks!

M

You should be able to use the same credentials and pools for all 3.

M

Yes you can.  Add /1024 I believe to end of your payout address.  That'll force it to the highest difficulty supported by the current version of p2pool.

Note this won't at all affect your payout, as this is just the psuedoshare difficulty.  The "real" difficulty is much much higher.

M

Not only that, p2pool.org unfortunately has a deservedly bad reputation.

M

Thanks.  That makes sense based on how I have it designed.  I should be able to add the 3rd qualifier to the listing pretty easily, so it'd list as S3:1.90 and S3:2.90.

I was originally thinking in cases like this DNS names would be used instead of IP addresses.  I see now that's not always the case.

M

Unfortunately the debug output from .Net isn't the most useful.  This gives me a clue - it's happening on the HandleAlerts routine.  What it doesn't like in there, I don't know just yet.

When you say regular, do you mean all the time?  Or regularly, but not all the time?

If it's all the time, then it might be a case where something went awry with an upgrade routine and the config got mangled.  Would you be able to rename the registry key hkey_current_user\software\MAntMonitor and then fire up the app again, reconfigure it, and see what happens?

If it's not all the time, then I would guess some alert is being triggered that causes the error to occur.  Any idea which alert that might be?  If you click continue, perhaps more than a few times, you should be able to get to the log to see what was last recorded.

I'm thinking it's somehow related to the addon that I'm using for SSH, but I added that in v2.2.  2.2 and 2.3 work okay for you?

M

Depending on your hashrate, your variance might have actually decreased.  It's the small guys, like those with one S1 Ant, that are hurting.  I used to have two on my pool and they both bailed.

M

Careful what you ask for.  That'll put the pool rate around 10PH/s, and share difficulty will be about 33 million.

M

I've been wondering.  Is it really worth trying to OC these?  Is the risk worth the result?

By OCing you:

1 - void your warranty
2 - risk damaging your Ant
3 - use more electricity
4 - generate more heat
5 - need to use 2x the PSU cables

All for a measly increase in hashrate?

M

This will be the big test of Bitcoin.  If we get a bunch of halvings, price doesn't increase significantly, and/or transaction fees don't increase, Bitcoin has a problem.

In other words, hang on tight.  It'll be a wild ride, and no one knows where it'll end.

M

The share difficulty keeps increasing.  I saw it almost at 4m earlier today.  That's going to mean less shares, but theoretically more blocks.

M

I have a question for you. 

If you're 5 feet from a wall, and each step you take, you cover half the distance, how many steps will it take before you're there?


(the block reward will never reach 0)

M

Here's a minor bug fix release.

v2.6a
- Added some exception logic to the routine that retrieves the Ant userid and passwords.  There appears to be some cases where somehow those entries
are completely missing, which can cause problems in multiple places.  Those places include rebooting your Ants, or clicking on an Ant in the config grid.  
Now if those routines are called and the data is missing, it'll create it with the defaults.

Download link: MAntMonitor26a.zip

M

EDIT: Fixed the annoying problem caused by a Visual Studio bug that causes all the controls to forget they are bound to the container, leading to the Ant grid being whacky.

I think you have that backwards?

256 would be about 4x as fast as 1024.

M

I'm not sure.  You can check the API.  Look at the cgminer API docs, login to your Ant, and start using cgminer-api and see what it spits out.

M

EDIT: I just checked the API.  I don't see anything in the output about the voltage.

Looks like something isn't stored right in your registry for the Ants.  Can you check your registry under HKCU\Software\MAntMonitor\Ants and make sure there's an entry in there for each one, and that there's data in there for each one?

M

Thanks!  Looks like all I'll need to do is add some recognition logic to it to properly label it as an S3.. or something like that.

M

Yes I do.  The initial pricing of S3s was too high, I can't see them making an ROI.  I'm hoping the next round will be better.

That said, I thought I saw someone say my AntMonitor was giving good readings on their S3.  Although I did post in my thread if anyone had tried it yet, as they seem to be basically identical, just faster, than the S1, so I suspect they'll work when added as an S1... but not a single person has responded.

M

EDIT: I haven't been feeling the best recently, and my posts show it.  What I meant to say was I don't have any S3s yet because I believe they were overpriced.

No.  I tried stacking them and they rapidly overheated.  Maybe with the S3s enclosed that would work better.

This way I was able to use less space compared to just laying them horizontally.

M

No I don't.  And I only have one S1 now.

Here's a diagram...



The tricky part was finding the best spot for the PSU.  Fortunately the cables are just long enough to fit everything as depicted here, perhaps with the PSU a little further in.

M