Topic: KnCMiner Jupiter Miner First Impressions - page 3. (Read 65993 times)

Because if you run asic_test there is the possibility that one or more boards doesn't work... and the solution is to delete asic_test file and reboot

Can someone recap the reason why some are saying to rename/delete the asic-test file? Is it because
some cores were tagged in it for permanent disablement and when you upgrade the firmware
you want to start with a fresh slate? Or is it some other reason altogether? Downloaded WinSCP
last night and I can finally see all the files.  :-D

Thanks for the advice Sitarow!  I'll look for another fan as suggested.  I've noticed that even just taking the case off makes a big difference.

I've ordered a 24U quiet rack cabinet, and when it arrives I plan to put my Jupiter in there.  It is an "active" cabinet, meaning that it has fans at the rear to create airflow.  I wonder whether I should run my Jupiter in the cabinet with case on or off?  If case off, should I have an additional fan on top of the Jupiter, blowing down?  I have no problem with that concept, I'm just worried about how much rack space the extra top fan will take (maybe it won't be much).

Am I right in saying that you have proven that a top fan blowing down is the best set up?

same times (really the most time...) one of the for board
doesn't work at full speed ( in fact temp is lower then others). It's
seam to be random when cgminer restart, 95% of time start low and 5%
start at full speed.

http://imgur.com/mHMYaep


EDIT. same tips for overclock?

thanks

Congrats and thanks for the review.

As far as your system performance it seems on par at the moment with the standard observations.

You can set additional pools via the cgminer interface by pressing "P" and then after setting the link, miner, and password details, you also have to enable failover if you wish to have that setting. Finally you have to write the config to the file.

To get to the cgminer interface you can use putty.exe and then ssh into the unit via its ip address. By default the username is root and the default password is admin.

If your ambient temps are low and you have the case off and the GH/s is above 510 then I would let it run for a good 24 hours to see if it is stable before attempting to put the case cover back on.

P.S. Do yourself the favor and point a fan at the unit so as to move the air around the components on the PCB. You do not want the hot air to remain stagnant.

DHL finally delivered my Jupiter today (25th October 2013 New Zealand Time), after being picked up in Sweden on the 16th.  Super excited, I took half a day off work so I could un-box and set up.  Grateful to The Avenger for the excellent Checklist Of Things To Do When Your KNC Miner Arrives.  

Very glad I followed the guide: when I opened the case, the front left heat sink fan had come loose (also, the fan itself had come out of the shroud).

Setup was smooth, exactly as described in the KnC Miner Manual.  Once up and running, it immediately started mining on my chosen pool (which I had pre-selected via the KnC web site) - nice job KnC.

It came with Firmware version 0.95, which I upgraded to 0.97.

Currently running with case off.  I plan to put case on at some stage.  As of this post I haven't been running it long, maybe an hour?

HW Status
ASIC slot #1   46.5 ℃
ASIC slot #2   -
ASIC slot #3   56.5 ℃
ASIC slot #4   47.5 ℃
ASIC slot #5   45.5 ℃
ASIC slot #6   -

Power consumption
Approx 540W at the wall (varies +/- a few Watts).

Questions
I have two noob questions:

1) How do I set up backup pools?  I'm used to Minepeon, which has a simple web interface where you can enter up to four pools (main pool and three backup pools).

2) Should I be worried about all the "core disabled" messages?

 cgminer version 3.4.0 - Started: [2013-10-25 03:21:59]
--------------------------------------------------------------------------------
 (5s):353.9G (avg):490.9Gh/s | A:208482  R:1668  HW:70174  WU:7468.2/m
 ST: 2  SS: 0  NB: 6  LW: 275912  GF: 0  RF: 0
 Connected to stratum.bitcoin.cz diff 231 with stratum as user XXX
 Block: 0005a863951dea69...  Diff:268M  Started: [03:58:34]  Best share: 78.9K
--------------------------------------------------------------------------------
 [P]ool management (S)ettings [D]isplay options [Q]uit
 KnC 0:                | 443.7G/492.0Gh/s | A:208944 R:1668 HW:70291 WU: 7480.9/m
--------------------------------------------------------------------------------

 [2013-10-25 03:57:47] Accepted 00298e53 Diff 1.58K/231 KnC 0
 [2013-10-25 03:57:48] Accepted 008172e3 Diff 506/231 KnC 0
 [2013-10-25 03:57:49] Accepted 008dfc3d Diff 461/231 KnC 0
 [2013-10-25 03:57:52] Accepted 000a46e1 Diff 6.38K/231 KnC 0
 [2013-10-25 03:58:00] Accepted 0108c8e1 Diff 247/231 KnC 0
 [2013-10-25 03:58:03] Accepted 00afd501 Diff 372/231 KnC 0
 [2013-10-25 03:58:03] KnC: core 3-41 was disabled due to 10 HW errors in a row
 [2013-10-25 03:58:07] Accepted 00b135e9 Diff 369/231 KnC 0
 [2013-10-25 03:58:07] Accepted 00d1a09d Diff 312/231 KnC 0
 [2013-10-25 03:58:09] Accepted 003510b0 Diff 1.23K/231 KnC 0
 [2013-10-25 03:58:11] Accepted 0035dd8c Diff 1.22K/231 KnC 0
 [2013-10-25 03:58:12] KnC: core 3-159 was enabled back from disabled state
 [2013-10-25 03:58:12] Accepted 001ac0ba Diff 2.45K/231 KnC 0
 [2013-10-25 03:58:13] Accepted 008e6b5d Diff 460/231 KnC 0
 [2013-10-25 03:58:17] KnC: core 3-182 was enabled back from disabled state
 [2013-10-25 03:58:21] KnC: core 3-181 was enabled back from disabled state
 [2013-10-25 03:58:21] Accepted 00d7ed6b Diff 303/231 KnC 0
 [2013-10-25 03:58:23] Accepted 00f9aa2b Diff 262/231 KnC 0
 [2013-10-25 03:58:23] Accepted 01163683 Diff 235/231 KnC 0
 [2013-10-25 03:58:26] Accepted 00244769 Diff 1.81K/231 KnC 0
 [2013-10-25 03:58:29] Accepted 0094b334 Diff 440/231 KnC 0
 [2013-10-25 03:58:34] Stratum from pool 0 detected new block
 [2013-10-25 03:58:34] KnC running flushwork
 [2013-10-25 03:58:34] KnC: accepted by FPGA 1 works, but only 0 submitted
 [2013-10-25 03:58:34] Rejected 0001c3cb Diff 37.1K/231 KnC 0  (Job '77159' not found)
 [2013-10-25 03:58:35] Accepted 0101617d Diff 254/231 KnC 0
 [2013-10-25 03:58:36] Accepted 0025d212 Diff 1.73K/231 KnC 0
 [2013-10-25 03:58:37] Accepted 00c9ad70 Diff 324/231 KnC 0
 [2013-10-25 03:58:38] Accepted 01002390 Diff 255/231 KnC 0
 [2013-10-25 03:58:41] Accepted 00093e6a Diff 7.09K/231 KnC 0
 [2013-10-25 03:58:42] Accepted 0048a77e Diff 902/231 KnC 0
 [2013-10-25 03:58:47] Accepted 002e03a0 Diff 1.42K/231 KnC 0
 [2013-10-25 03:58:48] Accepted 006e1320 Diff 595/231 KnC 0

1 Day results Firmware v0.9.7




1 Day Results Firmware v0.9.6



1 Day Results Firmware v0.9.5

Yessir, me too!

539 on cgm/puTTy - 499 on BTCG = .97

i flashed back to .96.1 and now have 532 on cgm/puTTY - 503 on BTCG

still not as 'good' as .95 but need to calc the HW errors to make it more accurate.

After how many hours? I would advise you to wait at least 6-12 hours for good measurements.

On .97 Jupiter anyone seeing a big difference between what CGminer is reporting and what BTCGuild is reporting for hash rate?

Seeing 513GH cgminer and 440GH on BTCGuild.

All the firmware's were run at least 24 hours without any reboot.
For that reason firmware 0.90 to 0.93 aren't listed.

--------------------	0.94	0.95	0.96	0.97
Average CGminer	270Gh/s	274Gh/s	280Gh/s	284Gh/s
Average Pool	275Gh/s	263Gh/s	278Gh/s (link)	283Gh/s (link)
Consumption	485 Watts	305 Watts	313 Watts	313 Watts
Temputure	54 & 62°C	42 & 47°C	42 & 47°C	40 & 44°C
Rejected	1.5%	0.22%	0.38%	0.48%
HW	2.81%	0.79%	1.08%	1.47%
WU	3975/m	3717/m	3933/m	4021/m

0.94	0.95	0.96	0.97

wow, you are really running hot - do you still have the cover on?

It is obvious that each module should be able to run its own version of FW until they have tight variance on production

Wish they would sell extra controllers - maybe once expansion rolls around.  Hashfast is delaying until mid Nov so it might get interesting what KNC decides to do. 

Just a little sample of my Jupiter on 0.97.  After stabilizing (30 minutes or so) this seems pretty solid:



Was around 530-540 on 0.95, so I'm happy with this update.  My pool says 557GH/s, and is peaking as high as 600GH/s on good luck.

.97 seems to throw more HW errors than .96

I switched my good miner back to .96   - it is about 30Gh difference on avg  (small sample size)

Firmware V0.9.7
2 Hour Results

Results after 1 hour with Firmware v0.9.7.



Compare with results after 1 hour with Firmware v0.9.6


Compare with results after 1 hour with firmware v0.9.5


Note: Test results had the system case cover on for all Jupiter units 1-4. Due to poor performance Jupiter units #1 and #3 have had the intake fans were replaced with 140mm 171CFM fans. The added air movement in and out of the case helped improve performance and stability even when ambient room temps reached 19°C.

Ambient temp is a big factor. Woke-up to 35F outside and 6 more hash.

I will be testing firmware 0.97 shortly I am attempting to see if the miners performance will improve if I lower the ambient room temp in the room over the same miner session.

Thus far it seems lowering the ambient room temperature from 19°C to 16°C helped to improved performance.

Firmware v0.96 1 Day 13 Hours


Firmware v0.96 2 Days

the latest knc branch gives control of the cores.  type M to get there
to quickly turn on cores, still use enable_cores.  If a core can't be turned on by that after a few times it is best to usually leave it off, but giving control for each one now you can turn off any (seen some with 30% HW error rate)  if you like but it seems that doesn't really hurt performance as much as when cgminer takes the time to keep enabling and disabling cores.  that seems like the big hit for people who have flaky cores