Swedish ASIC miner company kncminer.com

[Xialla]

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

hey Kano, here is very strong base of blind KNC fans, really recommend you to stop this kind of discussion.)

[mmitech]

So anywhere up to 300 a day you think?

At 469GH/s ( less than a BFL Minirig ) that's 140TH a day

Current difficulty is 148,819,199.80509263 = 1065.289327 TH/s

So if they ONLY spend a week making them, difficulty will go up ... 92%

So the next 2 difficulty changes should together be over 184% ...

Lets see who doesn't stop mining in 4 weeks

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

I was thinking about the same thing, BTW do not forget that bitfurystrikesback is massively shipping October pre-orders, some 400GH/s devices are coming online as well.
add to them what BFL and ASICMINER is shipping and you get some interesting times coming soon  

[arlekyn13]

So I guess my probably last order for Oct delivery from Sep 1st will be delivered next week? After the difficulty increase (ouch!) though...

[Mota]

So anywhere up to 300 a day you think?

At 469GH/s ( less than a BFL Minirig ) that's 140TH a day

Current difficulty is 148,819,199.80509263 = 1065.289327 TH/s

So if they ONLY spend a week making them, difficulty will go up ... 92%

So the next 2 difficulty changes should together be over 184% ...

Lets see who doesn't stop mining in 4 weeks

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

I was thinking about the same thing, BTW do not forget that bitfurystrikesback is massively shipping October pre-orders, some 400GH/s devices are coming online as well.
add to them what BFL and ASICMINER is selling and you get some interesting times coming soon  

Still not convinced that BFL will ship anything worthwile and in numbers....

[vesperwillow]

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

hey Kano, here is very strong base of blindness KNC fans, really recommend you to stop this kind of discussion.)

Lol, it truthfully sucks more people don't look into the numbers this way. I've maintained for awhile that difficulty is going to get stupid. For some reason, folks believe KNC only had a few orders. The magnitude of their actual order quantity is going to send them into shock. Kano's numbers are extremely conservative compared to reality.

The most profitable mining is occuring at this very moment. It's all downhill once the UPS trucks arrive at folks' doorstep around the world.

BFL isn't a major player anylonger, even with the few large miners they have to ship. The Monarch isn't a reality for awhile, aside from the lack of tapeout success, they haven't worked out the heating issues and are already projecting higher power consumption (lolz).

[Its About Sharing]

April 08 to Sep 30 is 4 months? Right. It's 5.75 months ... anyone got their September delivery yet?

If it wasn't cgminer, I'd wonder about the hash rate being correct ...
... except ... the driver can get it wrong easily enough.
They should have displayed 2^32 * A / Elapsed after about an hour ... hopefully they do run for an hour ...
... unless they don't know how cgminer works ... oh right they only wrote a 1 or 2k line driver, they probably didn't know about the rest of the other 40k+ lines of code in there ...

I doubt they would provide official numbers on a product they're going to release which would then be heavily scrutinized against said numbers, without verifying their data so they don't end up with a foot in their mouth.

No idea, but we've seen a lot of this happen ...
I guess we'll find out when someone finally gets one and reports the numbers.

OK, so just to point out that they really don't understand what the numbers there on the screen mean ...
It's hashing at 469GH/s

Picture: (click to see bigger)


Firstly the screen says: 497.0GH/s (the number on the right is what the driver produces)

Calculation:
Start = 00:06:40
Share that just happened says: 00:28:46
Elapsed = 22:06 = 1326 seconds

Accepted + Rejected = 144587 + 260 = 144847 1diff shares

Hash rate = 2^32 * 1diff / Elapsed
= 2^32 * 144847 / 1326
= 469,165,254,844 or 469GH/s

So yeah they really should learn what the numbers mean ... ... ... ...
... and I have assumed the Rejects are valid shares and included them in the hash rate ... though that's a guess, they may not be valid?

Also note:
HW: 28517 is an awesome ... 28517 / (28517 + 144587 + 260) = 28517/173364 = 16.46% ...

Edit: lastly that WU: number there at the top of 8001.3 means 8001.3 * 2^32 / 60  = 572,755,363,758
So they are losing >100GH/s of work vs the replies they are getting back from the device ...

Thanks for sharing that.
I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

Thanks Kano,
IAS

[erk]

So anywhere up to 300 a day you think?

At 469GH/s ( less than a BFL Minirig ) that's 140TH a day

Current difficulty is 148,819,199.80509263 = 1065.289327 TH/s

So if they ONLY spend a week making them, difficulty will go up ... 92%

So the next 2 difficulty changes should together be over 184% ...

Lets see who doesn't stop mining in 4 weeks

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

The 110nm miners and the BFL boys will be the first to switch off, well before KNCminer users. I wouldn't want to be holding ASICminer shares right now.

[vulgartrendkill]

So anywhere up to 300 a day you think?

At 469GH/s ( less than a BFL Minirig ) that's 140TH a day

Current difficulty is 148,819,199.80509263 = 1065.289327 TH/s

So if they ONLY spend a week making them, difficulty will go up ... 92%

So the next 2 difficulty changes should together be over 184% ...

Lets see who doesn't stop mining in 4 weeks

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

The 110nm miners and the BFL boys will be the first to switch off, well before KNCminer users. I wouldn't want to be holding ASICminer shares right now.

My poor little block erupters are already haemorraging with all the effort, poor loves....

[-ck]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

[electrox]

My very second post in this fantastic forum!  (First one was in the newbies' forum)
Thanks to most people for valuable inputs...

Anyone who knows how we will be able to adjust our miner settings?
Pools, worker names, passwords etc.

Does the Beagle bone board has a video connection or do we have to use SSH or a web interface?
And what about keyboard connection?

It would be great if someone who actually knows could answer. Wild guesses are not so helpful.

The reason for asking is because I am not a genuine computer wizard and am hoping for a relatively user friendly interface.

On the KNC forum I once asked if the miner will come with a user manual but no reply from KNC as of yet.
Though I am glad KNC used their time to work instead of wasting time on silly questions and FUD.

If my questions were already answered earlier I apologize for it escaping my attention. I have followed this thread for months now but I do not remember this question has been answered clearly.

[Xialla]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

ahh, and you are planning to do it? will you receive some KNC miner for testing and driver development?

[erk]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

What does a hardware error actually represent, is it a fault or something else?

[ASIC-K]

My very second post in this fantastic forum!  (First one was in the newbies' forum)
Thanks to most people for valuable inputs...

Anyone who knows how we will be able to adjust our miner settings?
Pools, worker names, passwords etc.

Does the Beagle bone board has a video connection or do we have to use SSH or a web interface?
And what about keyboard connection?

It would be great if someone who actually knows could answer. Wild guesses are not so helpful.

The reason for asking is because I am not a genuine computer wizard and am hoping for a relatively user friendly interface.

On the KNC forum I once asked if the miner will come with a user manual but no reply from KNC as of yet.
Though I am glad KNC used their time to work instead of wasting time on silly questions and FUD.

If my questions were already answered earlier I apologize for it escaping my attention. I have followed this thread for months now but I do not remember this question has been answered clearly.

you will ssh into web interface of beaglebone.

[kano]

...
Thanks for sharing that.
I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

Thanks Kano,
IAS

It's up to the driver to be able to calculate it.
Some devices you can't actually count how many hashes it has done.
Others the calculations can be wrong or done badly.
Most have to estimate something in there - the better the estimate the more accurate the result.

The "nonce" calculation I've used in my post above (like is used in the Avalon and BitBurner drivers) is how you tell if the driver calculation is correct - but you need to do lots of hashes to consider it reliable.

Bottom line is that I put a lot of effort into the Icarus driver (ICA, AMU, BLT, LLT, CMR) to make it more reliable reporting the MH/s.
However, it itself is doing an estimate on a bit over 1/3 of the work it does also.

My 3 AMUs do 335MH/s ...

Working on the Klondike project, I recently changes the driver to use the "nonce" calculation and found that the original BKK code + the firmware together were not actually getting it right, they were getting it way UNDER what it was really doing for some configurations.
So I switched that driver over to the "nonce" calculation and suddenly everyone was happy to see that indeed it was hashing as it should be

[The Avenger]

you will ssh into web interface of beaglebone.

How will this be done?

I found a guide to this
http://learn.adafruit.com/ssh-to-beaglebone-black-over-usb/overview
however, it requires a USB.

KNC have said they are disabling the USB on the beaglebone in their build, so is there another way?

[Mota]

Great... Called them and asked about the delivery. Today day 1 orders will be shipped and tomorrow afternoon day 2. So I get my units on Friday, even though Germany should be the fastest delivery -.-

[sickpig]

Great... Called them and asked about the delivery. Today day 1 orders will be shipped and tomorrow afternoon day 2. So I get my units on Friday, even though Germany should be the fastest delivery -.-

fantastic !

[Kuroth]

So anywhere up to 300 a day you think?

At 469GH/s ( less than a BFL Minirig ) that's 140TH a day

Current difficulty is 148,819,199.80509263 = 1065.289327 TH/s

So if they ONLY spend a week making them, difficulty will go up ... 92%

So the next 2 difficulty changes should together be over 184% ...

Lets see who doesn't stop mining in 4 weeks

So lets say they only make them for 2 weeks - 184% - what will the return on them be? ...

Careful kano..  You are making way too much damn sense..   Something that is frowned upon in this thread

[kano]

Also note:
HW: 28517 is an awesome ... 28517 / (28517 + 144587 + 260) = 28517/173364 = 16.46% ...

Edit: lastly that WU: number there at the top of 8001.3 means 8001.3 * 2^32 / 60  = 572,755,363,758
So they are losing >100GH/s of work vs the replies they are getting back from the device ...

The difficulty is 127, so the error rate is fine. Unless you or the team fixed that in the cgminer, in the older miners 3.2.x I had to divide the errors by the difficulty.

No.
The error rate is 16.46% using the numbers there on the screen

[erk]

...
Thanks for sharing that.
I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

Thanks Kano,
IAS

It's up to the driver to be able to calculate it.
Some devices you can't actually count how many hashes it has done.
Others the calculations can be wrong or done badly.
Most have to estimate something in there - the better the estimate the more accurate the result.

The "nonce" calculation I've used in my post above (like is used in the Avalon and BitBurner drivers) is how you tell if the driver calculation is correct - but you need to do lots of hashes to consider it reliable.

Bottom line is that I put a lot of effort into the Icarus driver (ICA, AMU, BLT, LLT, CMR) to make it more reliable reporting the MH/s.
However, it itself is doing an estimate on a bit over 1/3 of the work it does also.

My 3 AMUs do 335MH/s ...

Working on the Klondike project, I recently changes the driver to use the "nonce" calculation and found that the original BKK code + the firmware together were not actually getting it right, they were getting it way UNDER what it was really doing for some configurations.
So I switched that driver over to the "nonce" calculation and suddenly everyone was happy to see that indeed it was hashing as it should be

Been meaning to ask for ages, which of the ASIC chips do you find the best/easiest to develop your code for?