Remember i upgraded my cgminer as well to this version which makes the rigs much faster in response times - Confirm. Both my S3s Batch 7 were upgraded well this way. CPU load now is about 90% instead of 99-100% with old cgminer. WebGUI is a bit quicker. Niiice!  p.s. I suspect that it will not work for S2?.. 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 That might be the missing combination. I don't think I put cgminer 4.6.0 on that firmware yet. M |
|
|
|
|
Planning on adding some basic API stats? That way I can see when we get that block without having to F5 the site.
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 Try the latest beta. I believe I added support for that version here. Download link: MAntMonitor34b1.zipM 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." 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 |
|
|
|
me bad.. I didn't read that file...thx for your patience  Just updated and now no more error thx Great! 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 Try the latest beta. I believe I added support for that version here. Download link: MAntMonitor34b1.zipM |
|
|
|
Maybe you can try a miner, let it find one share then stop it. I can guarantee its not valid not much more than 24 hours!!! Or if thats too difficult see with your eyes - http://p2pool.servebeer.com:9332/static/sharetime.jpg the last share in graps wasnt valid for a single block.... That's why I left p2pool. I was squeezed out. The one share I got rolled off within 36 hours before a block was found (it was one of those long streaks). M |
|
|
|
Any one get B9 tracking numbers yet?
Yes. However when I plug it in to the UPS site, it tells me it's created, nothing else. so I'm guessing I'll get it mid next week. M |
|
|
|
Hi there M - I am using 3.12.0-1 for my CG Miner,
is there anything preventing me from using the program?
just 3.3 still erroring, i read that someone was having success with 3.1 is there a downloading area to get the older version or will u be making a newer one soon ?
regards
hawk
I don't think the cgminer version matters so much, it's the firmware version. I've tested it with the last 2 versions of the firmware, haven't tested the latest yet, or the earliest. I also upgraded cgminer to 3.6.0 and my code continues to work. What version are you using? I'll be getting a "S3+" soon (from batch 9). I'm knee deep in my UI changes, the next version will likely contain the UI changes and support "S3+". M |
|
|
|
Here's hoping we get lucky a get a block! M |
|
|
|
|
Looks promising. Just need some big guys "whales" to hop on so we little guys aren't spending a month on a block.
M
|
|
|
|
The link I provided above has a FAQ I believe that shows you how.
My S1 is turned off atm else I'd look.
M
It's not what I meant.. I know how to upgrade... Just don't want to do it without knowing if I already have the latest firmware.. Don't want to mess with it for nothing as it's always risky... and I'm a kind of person that believes that if it's not broken, don't fix it and my miners hash very well and stable.... however I like the utility of Your soft and would love to fully profit from it's features The readme.pdf in the link above describes how to find out what firmware version you're using. https://www.bitmaintech.com/files/download/readme.pdfM |
|
|
|
And is not tell that max 3 blocks can be paid? As far I understand, every share is valid 8640 shares of time but up to 3 blocks found in mean time. So if we will found more than 1 block per day, and your power is not enough to get more than one share per 3 days you will not get payout from every block. No, it is not a hard limit of 3 blocks, it is 3 times the average work required to solve a block. In other words, if the average time to block is 8 hours, then your shares will fall off the payout after 24 hours. So, if p2pool happens to get lucky and solve 10 blocks in that 24 hour period, your share will be paid for all 10 blocks. That explains why it dropped from 3 days to 1 to 1.5 days. I know very well I saw my sole share fall off within 36 hours. It also means as the pool hashrate increases, this value gets smaller and smaller. Say we get to 2hrs per block. That means 6 hours, it rolls off. Ouch. Thanks. M |
|
|
|
Is the p2pool share difficulty node specific, or it's whole p2pool blockchain specific?
The pseudo share size is node specific. The "alt chain" share size (currently at 12.3 million) is p2pool wide. M |
|
|
|
Hey I really like your soft. I'm getting this error: [b]ERROR when querying S1:1.222:80 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.[/b] Do You know what causes this ? Is it an S1, or an S3 labeled as an S1? Are you using the most recent firmware for it? M S1...however I don't know how to check the firmware version.... is it the Kernel Version 3.10.12 ?? I think the important thing is the date. Have you ever upgraded the firmware? See here: https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695M I got them used....they hash well and without issue.... I don't want to change firmware just to change and even without knowing that I already might have the latest... there must be a way of checking the version out....I just don't know where and how... The link I provided above has a FAQ I believe that shows you how. My S1 is turned off atm else I'd look. M |
|
|
|
I'm having some questions about P2Pool mining, I'm mining on http://elizium.name node with 2 Antminer S3+'s, at about 920GH/s. But I've been mining for 12+ hours now, and I still have nothing. I added after my payout address "+518" but still nothing. Is this normal or...? Because P2pool is PPLNS so it takes around 3 days to build up enough shares to start seeing payment. conversely when you stop mining you'll still receive payments for a few days. have a little patience, it'll come and when it does it'll be sweet. p2pool has been finding quite a few blocks lately. I don't think the 3 day thing is true anymore. I've watched my 1 share roll off in 36 hours or less. Also, at 920 GH/s, your variance is going to be bad. Be patient, and expect lots of time without shares. M |
|
|
|
Hey I really like your soft. I'm getting this error: [b]ERROR when querying S1:1.222:80 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.[/b] Do You know what causes this ? Is it an S1, or an S3 labeled as an S1? Are you using the most recent firmware for it? M S1...however I don't know how to check the firmware version.... is it the Kernel Version 3.10.12 ?? I think the important thing is the date. Have you ever upgraded the firmware? See here: https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695M |
|
|
|
Odd. Miners were running okay last night. This morning one was running at 20GH/s. ssh'd in and /etc/init.d/cgminer stop and /etc/init.d/cgminer start. Runs file. No reason in system log for hashing having dropped to 20GH/s.
My S1 does that when it's powered off for a period of time. It's like it includes the downtime in its hashrate calculation. Rebooting it (non power cycle) fixes it. M |
|
|
|
Holy Moly!! That's a monster share my man - a true block solver!  It's barely big enough! Next increase and it'll be too small! M |
|
|
|
Hey I really like your soft. I'm getting this error: [b]ERROR when querying S1:1.222:80 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.[/b] Do You know what causes this ? Is it an S1, or an S3 labeled as an S1? Are you using the most recent firmware for it? M |
|
|
|
I found Corsair CX500M 80+ Bronze...is this good enough to power Antminer S3 (24/7)?
Yes, although some people say the M version is junk. M |
|
|
|
|
Show Posts
