Is a Hero Member mudwrestling match coming to On Demand soon?  lol

Here you go: https://www.kncminer.com/pages/support

Hi guys,

so I played a little with firmware settings, voltage (0.7 0.9) and after a few restarts I now have my Mercury running stable at 130 GH/s and only have ~15 cores disabled instead of 40 cores with firmware 0.90 and enablecore.bin.

I made a few photos from the ASIC board and found out that the VRM with an output voltage from 0.9V they reach temperatures over 89°C.

Here is an album I made:

http://imgur.com/a/wVSbq

No worries, sent you a nice response in PM.

Yes, and the efficiency looks quite good.  

I see that using 0.90, which I believe uses the most energy and produces a high percentage of duplicate shares that count as rejects, this on a Mercury, using a cheap 12vdc switching supply (the output voltage of which I can adjust) and an inexpensive BBB supply, I'm drawing 259½ watts (174 watts on BertMod) at the wall so it's an efficiency of 67% so that's not great.  Of course the BBB draws and it's 1 BBB to 1 module while with a Saturn it's 1BBB to 2 modules.  

I may be able to increase my efficiency even more by dropping the ASIC PCIE voltage down.  The onboard vrms aren't completely efficient and lowering that voltage might find a sweeter spot.  That's the only advantage of this cheap supply designed for powering a huge load of LEDs, the output is adjustable.  That and its cost, $27.88 free shipping and a few bucks for tantalum capacitors I added.

Still, 600 watts on 2 Saturns, that's 150watts per.  

I'm getting 134GH/s as the final settling point on 0.90 at 174watts on BertMod.  If you're getting 150watts at the wall per then I suspect you aren't getting 134GH/s per avg.  Of course you could be if the efficiency of the later firmware versions is great but I've heard that's at a cost of hashrate.  Eliminating the duplicate shares would have gone a long way to increasing efficiency.  I'll know later today when I go to higher versions of the firmware until the duplicate shares stop.

Well I am at a total loss why my Jupiter does not get above 410Gh/s. (380 at BTC Guild)

Tried every firmware, tried the Enable cores patch and still the same.

Look at the results from bertmod, I have 1 Asic #4 showing (192 Cores all on hashing at 130Gh/s)

The other 3 Asics (# 0 , 2 , 3)

#0=80.58Gh's , #2=93.36Gh/s , #3=88Gh/s

The DC/DC are all showing 4 on and ok apart from Aisc #3 only showing 3 DC/DC on and ok , no other found.

Temps are as Follows

HW status:

ASIC slot #1: 53.5 ℃
ASIC slot #2: -
ASIC slot #3: 54.0 ℃
ASIC slot #4: 61.0 ℃
ASIC slot #5: 58.5 ℃
ASIC slot #6: -

Thought this was to be plug and play, I have spend Hours upon Hours trying to nurse this Lemon back into life.

Got in Mining on the Day it arrived Wednesday the 16th at 14:00 (UK time), Mining via BTC-Guild I have the grand total of :-

2.25 BTC's

Any Suggestions on what KNC should be offering to do when I call them again tomorrow.

It's up to firmware what Output Voltage are used. Now I use 0.94 with 0.9V (194W power output). If your boards are running fine with 0.7V I recommend you to use it. With 0.7V I only have half the output power (about ~100W) but more cores disabled (40 cores of 192 disabled).

When I fuss with my cardboard and fans, I sometimes get a reboot.  Since I run, at the present, without the top, center cardboard cooling the BBB, a 12v fan sitting inside blowing on the left side of the module, another 12v fan outside the case blowing on the right side of the 1 module (Mercury), I added another piece of cardboard to the right of the BBB, to the side and up to the module, taking the air pushed out the side and directing it to the module.  The miner white light came on and off as I moved the fans, perhaps a loose pin in an added fan connector, but it started again right away.  Put Bertmod back but earlier tried the 0.2.1 and found it works well with firmware 0.90, looked at my cores, which I could with the 0.2.1, and earlier their was a single core not up, but now there are four 100% cores and the BertMod says the power change from adding that one core on firmware 0.90 with ~0.9v to the 4 vmr's, was 174 watts with one core down and 180 watts with all cores running.

Nah, that can't be right as (4dies)(48cores)(6watts)=1152 watts.

So, at 100%, 180watts/(4dies)(48cores)=.9275watt/core.