Topic: Swedish ASIC miner company kncminer.com - page 1272. (Read 3049528 times)

In Berlin, will ask when next in Stkhlm.

If you filled in your pool info on KNCsite it will be already filled on miner, so if you plug and start it, it will start mining. On web interface (you run it just like router options) you can change your pool info and on .96 you can see some stats + can add backup pool. People configure SSH to look at CGminer for more stats.

Good news, Slush now has the Merc up to 128268.002MH/s!  and climbing.....

 KnC 0:| 141.4G/133.7Gh/s | A:157213 R:9815 HW:14340 WU:2160.9/m

Also, I just noticed that my power consumption at the wall, which had been up to 160 watts @99GH/s, is now up to 271watts @133.9GH/s.

But then I'm using a cheap switching supply the efficiency of which isn't great.  When I would read 140 watts at the wall I'd see 94 watts on BertMod.  Then again I have a 120VAC fan plugged into the power strip and 2 additional 12v fans on the supply all of which is (all of which are?) being read at the wall by kill-a-watt.

Imagine a world where 250 Giga-Hash means you receive 250 Giga-Hash and where 1.6 Watts per Gigahash means 2 watts per Giga-Hash at the wall instead of 500 Giga-Hash and 1.1 Watts/Giga-Hash at the wall....

What a Brave New World we live in!

yeah, no unplugging was necessary
it helped the slowest saturn...by about 22 gh/s and 1000 WU's, but not the others

Ah, those of us with FAH experience have fond memories of WUs.

I ran the enablecores thru the upgrade screen without disconnecting anything.

The basic concept of WU is that you can hash all you want, but if you don't find anything shareworthy then it is meaningless. Imagine a gerbil in a wheel. lol

you were correct in assuming the enablecores.bin does not work with 0.96....it runs, but no results or difference......but

I did it your way....0.90...and..

it worked.
my slowest saturn was 255, now 280...

trying the others now...

edit...lt Did NOT help Saturn #2...  slowed it from 265ish to 255ish....
sat 3 is ok at 276 all the time, so ill leave it be...  but coolz it worked on the slowest one, its still saying 277 avg, when it was always 255 before... with 1000 more WU's

I was getting high 90'sGH/s on 0.95 then went to 0.96 and ran enablecores.bin and overnight only got to 99GH/s.

Of course it could have been something less clear.  Since I'm using a cheap 12vdc switching supply along with a BeagleBone barrel connector power supply patched to a 4 pin molex that also had the 12v from the other supply, I had shut down for a short time to try an old computer switching supply only to the 4 pin molex - this because the voltage from the BBB wall wart was 5.18v or so and the old supply put out 5.02v and the BBB needs cooling and I thought it would need less cooling with 5.02v instead of 5.18v.  It didn't work out and wouldn't bring up a web page.  So I went back to my earlier configuration and went to the 0.90 and enablecores.bin

Earlier today I tried running for an hour at 12.5v to the PCIE and then an hour at 10.0v to the PCIE.  With the 0.96 and no BertMod I could only tell there was not much difference, it stayed around 99.xGH/s avg on cgminer never reaching 100GH/s avg and with 50% HW error rate.  WUs dropped at 10.0v from 1508 on 12.5v down to 1500 on 10.0v.

WUs are stable 2151 then up to 2154 then back to 2151 @ 133.6GH/s avg.  Slush: 84651.455

The high rejects seem to increment up with a Duplicate Share notice.  I believe that was corrected in a later firmware but I'm sticking with what I have now for now.

Cloudhashing would never see ROI for himself so therefore it would never be a good deal either as he will try to sell you at a much higher $ per GH.  All cloud mining companies will do this.

I would watch the recent price increase and have funds ready at an exchange.  I think there will be a correction.  Everyone should get refunds and consider this.  You will get yourself far more BTC and be much happier in 2-3 years from now.

Sorry for the noob question, Everyone in the crypto world assumes everyone can program 

I am getting my first KNC unit soon, I am not used to IP mining, Is it really as "plug and play" as I assume?

As far as I can tell, I look up the IP of the unit via my router,  put this in my browser, and click on mining and put in my pool details directly, and i'm done?

If I can see the stats via the IP address and the pool, Why are people configuring it to show on CGminer.

Cool, that sounds easy...
is it made to run with 0.90, or can I try it with 0.96?

 KnC 0: | 154.0G/133.7Gh/s | A:78562 R:4469 HW:6893 WU:2150.3/m  Slush: 82625.522

Shut down, let sit a minute, unplug the ASIC modules at the modules (the PCIE power), restart and only BBB will be running, go to the Sat. web page, upgrade to 0.90, shutdown, let sit a minute, plug the ASIC modules back in, start, go to web page, run Upgrade with enablecores.bin.  At least that's how I did it.

thanks I always appreciate your advice my speed is going past 550gh now so I'm still gonna sit on my hands...i'll eventually upgrade to .96 or beyond..but hey i'd like to get thru 1 full day w/o mucking something up which is usually the case....

what i'm really interested is in what the tweaks will be when the bfgminer version comes out

anyway has been quite the last couple days....looking at the hash rate and diff seems I made the right choice on getting rid of my 2nd unit Saturn ..because it would ship after the 16th the 520x..they allowed a full refund which I promptly took.....prob would not have gotten it till end of month at best w/shipping and of course all that low priced stuff nov 15th going out the door ...same tune next month....(arg shipping shudder feel the need to fly to Sweden and get next unit..the horror of my destroyed pkg by dhl)..anyway....already burnt by bfl and bailed out by the 150 some extra free GH from kncminer....breaking even is looking good maybe a bit better fyi....(still no units from bfl april order they do 1 day of order per day at current rate sometime in December.....the stuff is doorstops)

anyway knc has been very good on my Saturn return chased it down from processing and everything..i may just sit stuff out till feb/march ...by that time it will probably be all shares in cloudhashing....who could keep up at this rate with the purchase of miners vs delivery vs holding the bag on risk?.....interesting times

Searing

Slush changes slowly.  The overnight hashrate was about 75GH/s and it's just gone up to 79.92GH/s in a half hour.

so how to get the enablecores.bin to run on the slo sat?
i have it (the file) on my desktop...
using putty I imagine,...

I say quit the bickering you two, 0.90 with enablecores.bin dropped my error rate from 50% to 8.6% and WU's from ~1500 up to 2125.3, max avg hashrate from 99GH/s to presently 131.1GH/s!

How much at pool?

Run along now...lol
did you bother to look at the pic...?
can you explain why the 3 sats don't jive with that statement?
I'd like to try enablecores on the slowest one...
could someone post a crude procedure?