bobsag3
|
|
October 23, 2013, 05:13:55 PM |
|
I think he just applied .97 to fix the flushwork problems. Don't know how they're running with it - it takes a few hours for things to settle down and stabilize.
Yeah both are running .97 smooth.
|
|
|
|
Thyatis
|
|
October 23, 2013, 07:10:08 PM |
|
Is there some easy way to see our hash rate?
|
|
|
|
|
mootinator
|
|
October 23, 2013, 07:23:23 PM |
|
If the 24 hour BTC looks low, keep in mind there's a delay on PPLNS before the BTC gets credited, so it might still be a few more hours before that doesn't include shifts where one of the units was being shipped.
|
No
|
|
|
Ashitank
|
|
October 23, 2013, 07:41:00 PM |
|
Worker 1 Hash Rate 229.523 Gh/s Worker 2 Hash Rate 282.208 Gh/s
Worker 1 is not as happy as worker 2 on 0.97 firmware it seems but we can wait for few more hours to conform this , probably best revert to 0.95 for worker 1 Jupiter.
|
|
|
|
thomas_s
|
|
October 23, 2013, 08:58:36 PM |
|
If the 24 hour BTC looks low, keep in mind there's a delay on PPLNS before the BTC gets credited, so it might still be a few more hours before that doesn't include shifts where one of the units was being shipped.
Updated to your newest version, thanks to mootinator it now shows USD ROI / amount of money made in USD
|
|
|
|
mootinator
|
|
October 23, 2013, 09:13:42 PM |
|
If the 24 hour BTC looks low, keep in mind there's a delay on PPLNS before the BTC gets credited, so it might still be a few more hours before that doesn't include shifts where one of the units was being shipped.
Updated to your newest version, thanks to mootinator it now shows USD ROI / amount of money made in USD Darnit, I missed adding an empty td tag. So annoying, and yet so... not urgent.
|
No
|
|
|
Ashitank
|
|
October 24, 2013, 03:53:57 AM |
|
Worker 1 Hash Rate 238.228 Gh/s Worker 2 Hash Rate 269.533 Gh/s
Bobsage worker 1 hashrate is still not-up to the mark & also earner btc for 24 hours is still not 1.xx which it should be, I suppose we should revert to firmware 0.95 on worker 1 Jupiter only , worker 2 Jupiter is very happy on 0.97 firmware.
We are loosing out on 0.2xx ~ 0.3xxx btc due to worker 1 rather low hashrate on 0.97 firmware.
|
|
|
|
thomas_s
|
|
October 24, 2013, 04:14:20 AM |
|
Worker 1 Hash Rate 238.228 Gh/s Worker 2 Hash Rate 269.533 Gh/s
Bobsage worker 1 hashrate is still not-up to the mark & also earner btc for 24 hours is still not 1.xx which it should be, I suppose we should revert to firmware 0.95 on worker 1 Jupiter only , worker 2 Jupiter is very happy on 0.97 firmware.
We are loosing out on 0.2xx ~ 0.3xxx btc due to worker 1 rather low hashrate on 0.97 firmware.
The 24 hour bitcoin is an average from BTC Guild it has to do on open shifts which one of the machines went down for a little while which lowered the average 24 hour BTC gathered, someone did post when those shifts close the 24 hour BTC will grow.
|
|
|
|
Ashitank
|
|
October 24, 2013, 04:26:48 AM |
|
Worker 1 Hash Rate 238.228 Gh/s Worker 2 Hash Rate 269.533 Gh/s
Bobsage worker 1 hashrate is still not-up to the mark & also earner btc for 24 hours is still not 1.xx which it should be, I suppose we should revert to firmware 0.95 on worker 1 Jupiter only , worker 2 Jupiter is very happy on 0.97 firmware.
We are loosing out on 0.2xx ~ 0.3xxx btc due to worker 1 rather low hashrate on 0.97 firmware.
The 24 hour bitcoin is an average from BTC Guild it has to do on open shifts which one of the machines went down for a little while which lowered the average 24 hour BTC gathered, someone did post when those shifts close the 24 hour BTC will grow. Ok Thomas , but what about worker 1 hashrate being much lower than Normal for 24 hours or more now
|
|
|
|
thomas_s
|
|
October 24, 2013, 05:17:47 AM |
|
Worker 1 Hash Rate 238.228 Gh/s Worker 2 Hash Rate 269.533 Gh/s
Bobsage worker 1 hashrate is still not-up to the mark & also earner btc for 24 hours is still not 1.xx which it should be, I suppose we should revert to firmware 0.95 on worker 1 Jupiter only , worker 2 Jupiter is very happy on 0.97 firmware.
We are loosing out on 0.2xx ~ 0.3xxx btc due to worker 1 rather low hashrate on 0.97 firmware.
The 24 hour bitcoin is an average from BTC Guild it has to do on open shifts which one of the machines went down for a little while which lowered the average 24 hour BTC gathered, someone did post when those shifts close the 24 hour BTC will grow. Ok Thomas , but what about worker 1 hashrate being much lower than Normal for 24 hours or more now I've just talked with bobsag3 about it, he said that the two miners R5/R6 (worker1 and worker2) are averaging 520 / 556, its possible that the site isn't displaying the correct info its not updated in real time and the information isn't gathered from the miner.
|
|
|
|
bobsag3
|
|
October 24, 2013, 05:28:04 AM |
|
Worker 1 Hash Rate 238.228 Gh/s Worker 2 Hash Rate 269.533 Gh/s
Bobsage worker 1 hashrate is still not-up to the mark & also earner btc for 24 hours is still not 1.xx which it should be, I suppose we should revert to firmware 0.95 on worker 1 Jupiter only , worker 2 Jupiter is very happy on 0.97 firmware.
We are loosing out on 0.2xx ~ 0.3xxx btc due to worker 1 rather low hashrate on 0.97 firmware.
The 24 hour bitcoin is an average from BTC Guild it has to do on open shifts which one of the machines went down for a little while which lowered the average 24 hour BTC gathered, someone did post when those shifts close the 24 hour BTC will grow. Ok Thomas , but what about worker 1 hashrate being much lower than Normal for 24 hours or more now I've just talked with bobsag3 about it, he said that the two miners R5/R6 (worker1 and worker2) are averaging 520 / 556, its possible that the site isn't displaying the correct info its not updated in real time and the information isn't gathered from the miner. Also not all units were created equal. The first Jupiter I got down here has been solid 550+ the entire time, the other is more like 520. + 3 small downtimes for firmware updates (.94/.95 > .96 > .97 with reboots in between) would account for the small difference.
|
|
|
|
Ashitank
|
|
October 24, 2013, 05:32:03 AM |
|
Thank you guys , I think we can re-group in 6 hours time to check on 24 hours BTC earned by that time pool shift e.t.c should be done ? , if 24 hours BTC earned is still lower that 1.xx BTC then we have a problem Capitan.
|
|
|
|
DyslexicZombei (OP)
|
|
October 24, 2013, 08:01:07 AM |
|
I've been in the line of work of Test & Evaluation and R&D for 10 years at mostly low TRL numbers, and I can tell you that these miners are all essentially prototypes.
There was no long term testing so it's natural to have variability in chip yield and board performance. Firmware and software are still in a huge state of flux.
It sucks, but that's the kinds of risks we all take going in. IIRC, Jupiters were sold as 400GH/s units so looking at it from a glass half full perspective would probably be more realistic. In this case as we're talking about the world's first 28nm chips in a super short time frame to get to market, bumps and weirdness along the way are to be expected.
|
|
|
|
Ashitank
|
|
October 24, 2013, 08:44:50 AM Last edit: October 24, 2013, 10:31:34 AM by Ashitank |
|
I've been in the line of work of Test & Evaluation and R&D for 10 years at mostly low TRL numbers, and I can tell you that these miners are all essentially prototypes.
There was no long term testing so it's natural to have variability in chip yield and board performance. Firmware and software are still in a huge state of flux.
It sucks, but that's the kinds of risks we all take going in. IIRC, Jupiters were sold as 400GH/s units so looking at it from a glass half full perspective would probably be more realistic. In this case as we're talking about the world's first 28nm chips in a super short time frame to get to market, bumps and weirdness along the way are to be expected.
If we have chance of earning 0.3xxx btc more every day by just changing firmware why loose this opportunity , if any other investors in this group buy think other wise please share your opinion , after all it is your BTC at stake here Sorry but a professional group buy should not be looked at as half glass full investment , not doing this for hobby.
|
|
|
|
-Redacted-
|
|
October 24, 2013, 11:28:37 AM |
|
Quote from: FeedbackLoop on Today at 03:58:54 AM
0.97 also shows a continuous drop of hashrate for me from 500 to 470 (3 hour average eligius).
Actually.. it doesn't seem to be coming back in any previous firmware. Last value was 450 and that's where it stayed. I read compatible reports on KNC's forum. I fear 0.97 might damage Jupiters... Careful upgrading yours.
So - it may well be the case that following the suggestion to upgrade the firmware to .97 has damaged the Jupiter at least semi-permanently. This is why I never attempt to fix things that aren't broken. And please recall that these units were sold as by KnC as guaranteed to hash at "at least 400 Gh/s", so anything above and beyond that is a bonus. And you might want to also consider the recent lucky (for us) announcement that HashFast shipping will be delayed for "a few weeks" - meaning we get at least two extra weeks of hashing in before the difficulty increases due to HashFast boxes shipping kicks in. -R-
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4270
Merit: 8662
'The right to privacy matters'
|
|
October 24, 2013, 12:22:31 PM |
|
I've been in the line of work of Test & Evaluation and R&D for 10 years at mostly low TRL numbers, and I can tell you that these miners are all essentially prototypes.
There was no long term testing so it's natural to have variability in chip yield and board performance. Firmware and software are still in a huge state of flux.
It sucks, but that's the kinds of risks we all take going in. IIRC, Jupiters were sold as 400GH/s units so looking at it from a glass half full perspective would probably be more realistic. In this case as we're talking about the world's first 28nm chips in a super short time frame to get to market, bumps and weirdness along the way are to be expected.
YOU ARE WRONG THE GLASS IS 52/55 FULL! LOL At Ashitank : The current mining difficulty is 267,731,249. The next difficulty is estimated to change by 42.16% to 380,608,553 on block #266,111. That should be 1 days 18 hours 7 mins 18 seconds from now. from https://bitclockers.com/calc I am 56 years old and have worked with computers since I am 18. They vary, they vary a lot. I have used more then 500 intel cpu chips. When overclocking they vary, they vary a lot. If you want to f with our 520 miner trying to get it to be as good as our 550 miner I get that. I have toyed around with pc gear tweaked it to make it bigger, faster ,stronger . Sometimes it works sometimes it does not work. So risking 520 to get 30 more does not appeal to me. 520 is .97 btc a day. 30gh is .056 btc a day I do not like those odds. in a day difficulty goes to 387 mill (est) 520 will earn 6.744btc in 10 days 30 will earn .389btc in 10 days . So down time would be a bad thing you are chasing after .4 coins and using 6.8 coins to get it. The next 2 diff adjustments will be big 99% up time for the next 20-25 days is very important. Most of us took a shot that diff would be a little less then 40% each jump. I for one do not want to send "good money after bad" a 550 machine is 5% faster then a 520 machine. the next jump is 40% while the 5% would be nice we could create weeks of down time chasing the 5% just not worth it.
|
|
|
|
Ashitank
|
|
October 24, 2013, 12:39:10 PM |
|
Thank you philipma1957 , its just that 0.3 BTC x 15 days = 1.5 btc lost , a single restart wont loose as much. But after reading what Redacted posted , I think we should just go back to 0.95 & not touch the machines there after , I am fully confident that organizers of this group buy are genuine good people & will take care of things fine.
|
|
|
|
|
Adeel06
|
|
October 24, 2013, 12:57:14 PM |
|
Jungle_dave, you are the man, helping others out all the time. Thanks again for the help you provided me through PM's !
|
|
|
|
|