Swedish ASIC miner company kncminer.com

[sickpig]

Yup! I've my PSU unboxed, cables ran, firmwares downloaded (0.97 being released today  ), list of hardware checks, immediate fan mod- I'm ready to roll.  

good for you!

fw 0.97? are you sure ?

[sickpig]

Yup! I've my PSU unboxed, cables ran, firmwares downloaded (0.97 being released today  ), list of hardware checks, immediate fan mod- I'm ready to roll.  

good for you!

fw 0.97? are you sure ?

According to KnC, yep

ok so they're planning to release 0.97 today, but it hasn't been released yet.

[sickpig]

Yup! I've my PSU unboxed, cables ran, firmwares downloaded (0.97 being released today  ), list of hardware checks, immediate fan mod- I'm ready to roll.  

good for you!

fw 0.97? are you sure ?

According to KnC, yep

ok so they're planning to release 0.97 today, but it hasn't been released yet.

Correct. I had e-mailed them regarding the status of my order(s) and had inquired on the performance issues people were having and Emilia stated a new FW will be on their site later today.

So Customer Support said that they'll release a new fw later this day, hopefully Emilia's right. Last CS said something like that we spent 3 days waiting

[the-skeptic]

So I am in Beijing for business and get my tracking number today (#3523 July 10). Good thing my brother is camping out on my couch waiting for the yellow truck full of magic

[markm]

This time UPS did phone back, they say I can go pick the thing up after 5pm at their depot in Dartmouth.

Why they couldn't do that back on Friday they didn't say.

-MarkM-

[soy]

Can anyone assist me?

Im trying to bridge the ethernet connection on my computer so I can login to my Mercury unit.
But I dont know what IP to hit in order to get into the config.

So say I directly connect my Jupiter to my laptop via ethernet, does anyone know what IP the machine will try to assign itself and what Windows might give it. Say if I try to bridge ethernet to ethernet?

1. undo the bridge
go to your connection properties on the laptop(of the actual internet connection, not ethernet), and turn DHCP ON under the ipv4 settings. assign it an ip address.
2.download advanced ip scanner, and prep it to scan the range you just used on the laptop.
3. cold start the miner.
4. Run the IP Scanner.. it will show knc after it finds it...takes about 30 seconds. you will need to scroll down the list to find it.
If it doesnt show right away, scan again right away.
once you have the IP, type it into chrome address bar, use admin/admin, and go directly to the networking page to program your IP in before anything else, or you will have to sniff it out all over again if you reboot for any reason.

IMPORTANT: remember to turn DHCP OFF (uncheck the box)on the miners GUI Networking page before you attempt to save the info.

Might try to get bridging working on an RPi but there's work to do on the truck, on the car, on the pumphouse roof, and a cold front is heading south this way, not to mention adding tantalum caps to the Merc Asic module and testing.

[The Avenger]

So I am in Beijing for business and get my tracking number today (#3523 July 10). Good thing my brother is camping out on my couch waiting for the yellow truck full of magic

They are only at #35xx? And today is the 4th day after their "3-5 days behind" on production announcement? The bullshit from KNC continues.

[DPoS]

I JUST GOT 48 F'ing cores online/a dead die is ALIVE, first try with enablecores.bin on firmware .94!

Was getting a 486ghs(avg) in CG now getting after a few min 516ghs(avg) WOAH!! All I did was stop CGminer by pressing q inside it, then I applied the enablecores.bin and rebooted. I'm an 8 VRM Jupiter guys DO THIS, stop waiting.

hope it lasts.. I brought one sickly die back twice and the second time it lasted about 8 hours and just went back to sleep.

Nothing can bring it back now, I think when this happens it is not really the chip but part of the board's other components (VRMs/caps) that fail it

but who knows, they are releasing another firmware - wish they gave release notes

[soy]

Got a RMA Number for 3 Faulty (under performing boards) on my Jupiter.

I asked about comp for my loss and for my Time , they will not offer any compensation.

Also the worrying thing is they Said and I Quote " The replacement boards can not be guaranteed to run at the Advertised speed as they are untested".

Well better go get some Thermal paste and await their return.

So they can''t test replacements before sending them? You could return bad boards and get more bad ones in return? That's poor.

Piss Poor.

Well the Boards are on the way to the post office.

My now 1 Board Jupiter is Hashing away at a Happy 140Gh/s on CGMiner and reporting 137Gh/s at BTC-Guild.

*Tip  T20 required for Case, T8 required for Board to case and a PH1 required for Heat-Sink cross bar.

My module took a T10.

[soy]

Looking at the rise in the bitcoin exchange rate I cant help but wonder if people are seeing that mining won't break even, or is unaffordable and are buying instead to a greater extent?

Maybe the miners arent selling.  Supply vs demand.

Possibly. Saving up for another round of nail biting on the next gen of rigs? lmao

ditto to get ROI back or double down say in feb for next round of "Searing vs the ASIC BEAST from non-fiat land"

Yes, I think it's go big or go home.  Will have to keep adding to hash power to stay up while those faint of heart or broke fold.

[DPoS]

You know, a lot of the problems people have had could have been prevented by a decent burn in period. It would be fine with buyers if it meant a day late delivery because the rigs would be hashing on the pool details given so it wouldn't mean any lost income. They would just be hashing there instead of at our end but where faults are so much easier to fix.

That's my thoughts exactly.

The Testing before shipping, should be against your Pool details (as provided for configuration) and then Shipped when the Unit achieves the advertised Hash Rate.

KNC has employed us all as unpaid beta testers.

Things didn't work well til version 95 for many, do you really want them to hold onto the units til then???   Would be better to hash at 380 and then boost to 525 via firmware.

THAT was because of the quick switch to 4 VRMs...  THEN they were in the situation you mentioned.

why they don't do burn in now on people's pool accounts is anyone's guess after .95 was released.  Probably too much of a logistic hassle

[soy]

Would really appreciate it if anyone getting a miner with fans knocked off in transit mark those ASIC modules some way that if later there's one or more modules with failing cores it can be noted as previously had the fan knocked off or not.

Theory: if a shock separated a solder point on the ball grid array of the ASIC module but still makes physical contact tho not flowed-solder contact, it will make a somewhat higher resistance point under current and raise temperature and that raised temperature will cause cores with gates at the hot spot to have more errors.

[DPoS]

Would really appreciate it if anyone getting a miner with fans knocked off in transit mark those ASIC modules some way that if later there's one or more modules with failing cores it can be noted as previously had the fan knocked off or not.

Theory: if a shock separated a solder point on the ball grid array of the ASIC module but still makes physical contact tho not flowed-solder contact, it will make a somewhat higher resistance point under current and raise temperature and that raised temperature will cause cores with gates at the hot spot to have more errors.

would be easier to mark the ones that the fans stayed on... but since they bounce around, anything can be hit from any fan

[soy]

Would really appreciate it if anyone getting a miner with fans knocked off in transit mark those ASIC modules some way that if later there's one or more modules with failing cores it can be noted as previously had the fan knocked off or not.

Theory: if a shock separated a solder point on the ball grid array of the ASIC module but still makes physical contact tho not flowed-solder contact, it will make a somewhat higher resistance point under current and raise temperature and that raised temperature will cause cores with gates at the hot spot to have more errors.

would be easier to mark the ones that the fans stayed on... but since they bounce around, anything can be hit from any fan

Would ROFL except it made me sad.

[DPoS]

Would ROFL except it made me sad.

 

your theory seems to be true though..  my one board with the dead die runs significantly hotter than the rest and that is with it hashing at 75%

can't see anything with the eyes that stands out, and while it hashes at 75% not really worth it to keep shutting things down to fudge with it for now

maybe RMA it when KNC gets out of the woods

[adrd]

Would really appreciate it if anyone getting a miner with fans knocked off in transit mark those ASIC modules some way that if later there's one or more modules with failing cores it can be noted as previously had the fan knocked off or not.

Theory: if a shock separated a solder point on the ball grid array of the ASIC module but still makes physical contact tho not flowed-solder contact, it will make a somewhat higher resistance point under current and raise temperature and that raised temperature will cause cores with gates at the hot spot to have more errors.

would be easier to mark the ones that the fans stayed on... but since they bounce around, anything can be hit from any fan

Would ROFL except it made me sad.

I had 2 fans knocked off and I have 2 boards underperforming, but it might be coincidence.

[sickpig]

Would ROFL except it made me sad.

 

your theory seems to be true though..  my one board with the dead die runs significantly hotter than the rest and that is with it hashing at 75%

can't see anything with the eyes that stands out, and while it hashes at 75% not really worth it to keep shutting things down to fudge with it for now

maybe RMA it when KNC gets out of the woods

me too have a completely dead die but all my fans were in place (i've checked while unboxing).

this happens for the two jupiters I own. (so one bad asic slot ech jup)

the common thing is that both the "flaky" asics are marked with a #3 stickers.


edit1: i've asked to hno (OrSoC eng) on irc channel it there's a relation between number on sticker and quality and he said a "weak one", but he didn't say everything he knows imho (and I can understand him)


 

[Crypto_Cumbrian]

[/quote]

My module took a T10.
[/quote]

My Mistake it is a T10 , I guessed at T8 it fitted and worked.

[xuemike]

Just an update for everyone who doesn't couldn't get all their asics up and running.

I ordered 3 jupiters from KNCminer and they arrived last friday.  And my cowoker ordered 1 jupiter. 

These are great products once you get them up and running, but boy was it a painful experience.
The issues I had with them are below.

1.  The fans on the heat sink falls off easily.  When You hear things rattling in the box, you have to open them up and put the fans on the heat sinks properly.  And they use torx screw drivers so that was a pain in the ass, luckily I had a torx set around the house.  I had to open all 3 jupiter boxes to put the fans back on at least 1 of the heat sinks on each of the units.

I had only 1 unit with all 4 asic boards running properly the others did not report any status on the status page.  After resetting the fans, I took a closer inspection.

2.  On 1 of the asic boards, the serial cable (not the power cable) CRUSHED one of the pins on the asic board.  I took the unit off line and straightened the pin on the board and then the ASIC came on.  I was pretty happy about taht.

3. Another asic board on another unit, the asic board's serial cable was defective or had some impedance issue.  I swapped the 2 cables (the ones that were the same length) and brought that asic online.  At this point all my asics were working properly.

However One of my coworkers who purchased an jupiter as well couldn't get his controller board to power on.  The asics were all powered though since he saw the fans were spinning.

4.  My coworker debugged on the on board pins and realized that there was no power going in to the controller.  So he took apart his unit and looked at the soldering on the power connector and realized it was faulty.  He touched up on the Power connector solder and the controller now came online.  the man spent a good 6 hours on this.

These were some of the issues that came up.  I hope this helps some of the people having similar problems.

[FiatKiller]

Wow. Seems like they are not testing them at all or the shipping is doing lots of damage by finding the weaknesses.