Unless you have SNMP management tools on your network somewhere you can ignore this.

SNMP = Simple Network Management Protocol

It is a general protocol for managing networked devices.


SNMP 'community' is like a password.
There can be a general community and a read and/or write community also

SNMP 'managers' ???not sure?? might be hosts allowed to connect or another way to say read and write community strings.

YMMV


EDIT: It is a natural progression IMneverHO, KnCMiner needs a way to control a whole DC with one tool.
SNMP is one choice of tool.

*approximate equation

take the first 2 digits the '21'
convert hex to decimal to get 33
multiply 33 x 25MHz and ya get 825MHZ
(add 25MHz to your answer)
The last digit is the divisor, it's 1 so we are done.

YMMV

Disclaimer: I have Oct. ASICs.

You might try UNDER volting it or it's neighbors.
You might try UNDERclocking the sleeping Die.

No reports of success so far(that I recall) but I continue to suggest it.
It's low risk if it is already 'sleeping'

It's a long read but time well spent if it results in some coin.

https://bitcointalk.org/index.php?topic=313978.0

YMMV

Below 1B1 is 1A1 (675)
Below 1A1 is 191 (650)

There is something to be said for the efficiency increase at lower speeds.
I keep it in mind as the efficiency  tradeoff for speed becomes moot at some difficulty level.

Above 251 is 261

ignore the last digit

 950 MHz would be 25 (251)
 975 MHz would be 26 (261)
1000MHz would be 27 (271)
Increase by one

It's hexadecimal so A comes after 9 (instead of 10)


TANGENT alert!
To calculate the value in the last column
Again ignore the last digit, multiply by 2 and add 1
(determined experimentally)

ex:
using 825MHz because the hex and decimal LOOK the same and the math works.
825.0 MHz    201        412

201, drop the 1
20 x 2 = 40
40 + 1 = 41
add a 2 to the end for last column
412 is the same as 201

Think of it as 20 divided by 1
or
40 divided by 2
(plus 1 for the div by 2 instance)

Most should have a calculator with hex mode, try it on a wierd one with a letter!

The list again


First column is speed in MHz per CORE
Second or third column is setting used for speed in column 1


EX:
for 800.0 MHz you could use a setting of "1F1" _OR_ "3F2"
for 812.5 MHz you would use "402"

core speed x 48 CORES  x 4 DIE will give you the Gh/s per ASIC x # of modules  - HW error %
= what to expect @ the pool

800 x 48 = 38400 (MHz)
38400 x 4 = 153600 (MHz)
153400 x 4 (assume a Jup) = 614 400 MHz

Subtract the HW errors (percentage) from the total above and you should be close to what the pool reports.


YMMV

EDIT: spelling

It was asked earlier the location of the temp measurement IC

It is located straight in from the ribbon cable connection at the corner of the ASIC package.

Repeating.........

The corner of the ASIC is not an ideal location (it is cooler at the corners)
The ASIC is easily 10C hotter than the temp chip.
I measured back side of PCB and see higher temps.
(measured both IR (gun) and direct contact thermocouple)

The VRM's are WAY hotter than the temp chip on both sides of PCB.
The VRM's are designed for airflow in the direction of inside to outside (as placed by KnCMiner) FWIW

Don't forget you need some air to flow UNDER the PCB too, it is a heatsink also!


Thx for thr thermal pics!

YMMV

@temen

What speed is each 'die' running at?
(48 core per die, 4 die per ASIC)

clock settings ending in 5 are likely the same as ending in 1
The last digit is the divisor but may only recognise lowest 2 bits


ie: 265 prolly the same as 261 (975MHz)

I'm prepared to be proven wrong but need die speed to do so!

YMMV

Ideas on cooling

I put air obstructions in my case so all air must pass the ASIC and VRM's.

For Sat find/make a cardboard box that fits between front (towards BBB) ASIC modules.
For Jup also find/make 2 smaller boxes to fill up outside edges.

Also the air that passes over the aluminum plate is not doing much cooling I direct it towards the VRM's.

Painters masking tape or similar wrapped around the heat pipes below the aluminum radiator will direct more air to the VRM's.

You could shove a wadded paper towel in there for testing.
Beware cardboard/paper burns, might not be ideal for long term usage in a box with a history of sparks.

Folks who drop fans to bar might consider blocking top(no fan area) of aluminum radiator also.

Aluminum tape/foil might be a better choice but then beware risk of shorts, keep it neat!

Make sure the cables do not block airflow also.

Oct. GE VRM's are designed for airflow from ASIC side to edge of board side.
KnCMiner is not ideal for OC airflow but it is what it is.
I'm glad they chose shortest lowV/highA copper runs making OC possible!

YMMV

Pressing the 'Apply" button sets the clocks back to default.
Restart modified .sh again after making any changes on Advanced page.

YMMV

the 950MHz die is pulling 59A 47W 
(those are the highest readings I ever see so slightly lower average)

I don't run the whole ASIC at that speed just one die.
The neighbors are ~50A 40W (average but all similar)
Directly adjacent are @ 39W and opposite corner is @ 41W
41.5W average per die for the ASIC
My personal do not exceed is less than 45W per die AVERAGE per ASIC
I'm still under 190W at the wall per ASIC (platinum PSU's at the sweet spot of 50%)
1.2W at the wall per Gh/s

Temps is a guesstimate at best.
IR temp from backside of running module is 60C for that die.
IR temp for that VRM is 73C measured on the bottom of the PCB!
There is a part in the VRM that is much hotter!
Temps were cross checked with thermocouple and measured at location of many via's conducting heat thru PCB

The watercooling system runs about 30C (I trade some temp for lower noise)
I have parts to improve the delta C but don't want the downtime yet as I don't see much to gain from current settings based on experience to date.

The LM75 on the PCB says ~ 50-55C depending on draftiness in cold house.

as usual
YMMV

I like the way you think, but think it all the way through.

Spending lots on cooling at this point in time may not be worthwhile.
RAM blocks are expensive and you need 2 per module.

Large air cooled aluminum heatsinks might be more cost effective.

FWIW: It cost me lots more than the cost of waterblocks for a WC system.
I justified it, you may also, just please make the decision based on all the facts and set expectations accordingly.

Fun  _IS_ a good reason!


YMMV

I have one die running 950MHz  (251)  for over a month.
Most others are way slower though.

I'd try a lower clock setting first before adjusting volt.

perhaps '422' (837.5) or '201' (825)

the list again for reference

The power supply is not the cause or cure.
There are 6 wires ALL needed for every PCIe connector.
If one makes poor contact the rest have to take up the slack.
As a result if they are near their limit they will get warm.

What you have described is probably that the 850's plugs did not mate as well as the 1000's.
Removing the blue cables reduces by 6 the chances of a poor mating of the connectors.

One mans opinion!
YMMV

It could also be that one of the other wires had no connection. (insulation in crimp)
The remaining now have more load than they the can handle.

Without disparaging the choice of conductor material.
;-)

Those are the GPIO pins of the BBB nothing to do with ASICs, dies, or cores.
GPIO = General Purpose Input/Output

The miner only uses a few of them.

Can you use the Recovery File posted on the page linked below?

https://www.kncminer.com/pages/troubleshooting

You end up with 96.1, then upgrade to FW of choice.

Not sure on instructions but basic BBB reflash is copy image to SD using PC, insert in BBB and reset.
(instructions have been posted in that other huge thread a few times)

EDIT found instructions here
http://forum.kncminer.com/forum/main-category/main-forum/11263-urgent-dl-d-the-recovery-file-sd-from-knc-support-now-how-do-i-apply-it-to-my-miner?p=11985#post11985

I plead ignorance.
I have been compiling bfgminer all along I have not kept up with bertmod.
I have heard it is possible. How? I don't know.

My error
The "/config/cgminer.conf" at the end should remain the same.


Will edit above.
Thx for the feedback!

bitcoinorama mentioned KnC is planning to release PLL clock FW.
You can wait for KnCMiner and save the warranty,
or not.  

orama also mentioned that KnCMiner considers 63A per GE DC/DC OK
https://bitcointalk.org/index.php?topic=170332.msg4106143#msg4106143
Yikes!!!
That can make more heat than the ASIC can move to the heatsink IMneverHO

People wanting a different method.
This will not really lower the bar, but might help you over it.
(the sed thingy is about as easy as it can get)
More hints (a mini howto tangent)

You need vi or some other editor.
Almost every *nix system has vi on it FWIW
I only use a few commands in vi
A super abbreviated vi survival guide follows.

ESC     = escape key, I start every vi command with escape to make sure I am not in insert mode.
i       = insert
a       = append
r       = replace chr under cursor
cw      = change word under cursor
x       = delete chr under cursor
dd      = delete line cursor is on (deleted line is copied to buffer (similar to CTL-x))
Y       = yank(copy) line to buffer
P       = pop(paste) line from buffer
:       = start of command to vi (file ops etc.)
:w      = write current file to disk
:q      = quit
:wq     = write file and quit editor
:q!     = quit without saving changes(it's all fucked up start over
/       = search

Ex:
'cp /etc/init.d/cgminer.sh /config/zzz.001.sh'
'vi /config/zzz.001.sh'
hit the slash key '/' then type D1 and hit enter
Your cursor should now be on the line most reading this seek.
Yank the line to the buffer with 'Y'
Pop a copy of the buffer back into the file with 'P'
now you have 2 lines exactly the same
hit 'i' to insert text
put a '#' at the beginning of one the copies  (turn it into a comment/reminder)
hit the ESCape key to get out of insert mode
move the cursor to the other copy of the line and over the 'D' in 0xD1
hit the 'r' key and replace the 'D' with a 'C'(slower) or an 'E' or an 'F'
hit Esc then ':wq'
thats it !
It's not hard just cryptic

It is possible to edit on a Win box and xfer the edited file with 'scp'
Google 'man scp' to learn more.

bfgminer is needed to adjust all die for best results.
With temp and HW error% seperated by ASIC no need for other Status webpage.
You still need the Advanced web page though.
cgminer can run the 'result' too but not provide much feedback during discovery.
I am a fan of BOTH cgminer and bfgminer FWIW both work well on KnCMiners.

Most of you lazy fornicators will try the seemingly easier softer way without bfgminer.
You will find it is not easier and softer if you cook an ASIC or VRM.
(permanent high HW error or worse)
bfgminer will not save the ASIC but it might let you know something is amiss in time to manually intervene.
KEY WORD = might

Clock specific mini bfgminer howto:
Use your newly minted vi skills
Go to this webpage
https://github.com/luke-jr/bfgminer
Click on README.ASIC --> https://github.com/luke-jr/bfgminer/blob/bfgminer/README.ASIC
Scroll to the bottom and find and READ the KnC section
Copy the text with your mouse
Then on the miner do the following (in a SSH window)
'vi /config/BFG_build.sh'
hit the 'i' key to insert text
Right click and paste text copied from webpage

Look at the bottom of the file for 2 lines

/etc/init.d/cgminer.sh stop
./bfgminer -S knc:auto -c /config/cgminer.conf

They stop cgminer and start bfgminer as soon as it is built
You may not want to do this automatically as it does not use the mods this way.
To change this behavior,
move your cursor to the beginning of one of the lines,
hit 'i' and comment it out by inserting a '#' at the beginnig
move to the other line and hit '#' again.
Then they will look like this

#/etc/init.d/cgminer.sh stop
#./bfgminer -S knc:auto -c /config/cgminer.conf

hit Esc key
hit ':' (colon)
hit 'w'
hit 'q'
hit enter

Now run it to build bfgminer
'source /config/BFG_build.sh'

Wait (might be 10 minutes or so)

When it is done cd into the new bfgminer folder
'cd /config/bfgminer'

For our purposes we need the startup stuff cgminer uses (the file with the clock info)
'cp /etc/init.d/cgminer.sh /config/bfgminer/bfgminer.sh'
edit the file with
'vi /config/bfgminer/bfgminer.sh'
change the
DAEMON=/usr/bin/cgminer
to
DAEMON=/config/bfgminer/bfgminer

Change every instance that reads 'cgminer' so it reads 'bfgminer' instead.

EDIT*** except for the config file part.
Thx CYPER for pointing it out.
Should look like
Save the file ':wq'

Prepare your workspace
Treat every test as a pit stop with a plan A and a plan B
Test plan B first!!!!!
A good plan B might be
'/config/bfgminer/bfgminer.sh stop ; /etc/init.d/cgminer.sh restart'

open 3 SSH windows or tabs per miner
One for vi (just use Esc-colon-w and stay in the editor for fast fixes) or scp
One to start and stop modified and unmodified shell scripts (up arrow is your friend)
One to run screen -r (after you do it once just use up arrow and Enter)

One web page ALREADY open to the Advanced tuning page for temp/volt/current/watt
After starting the modified shell script this is the first place to tell how it works
A few seconds is all it takes.
3 flavors to look for
        0 or very low die (ANY die)
        10-15 watts (ANY die)
        30 watts or more (ALL die)

The first 2 require immediate action,  Plan B!
You might first QUICKLY try just restarting.

The third indicates some degree of success requiring further investigation.
Wasting power and punishing ASIC without extra hash at the pool is non productive.
Sometimes a die can show power consumption and not be contributing.

***
*** This can happen after it has been running OK for a while and be hard to find.
***

Review the pitstop plans one more time!!!

NOW stop cgminer and start bfgminer
'/etc/init.d/cgminer.sh stop'
'/config/bfgminer/bfgminer.sh restart'
(I always use restart even though it may not be running and start would be more correct, for easy reuse with the arrow keys for speed during pit stop)

In your ssh that was running the screen showing cgminer it drops back to command line

hit the up arrow and Enter(or type 'screen -r' again) and view bfgminer hashing

Suggest first run with bfgminer use unmodified clocks
If you got this far you are ready to add a section for each ASIC and die to COPY_OF.bfgminer.sh

!!!Also note!!!
The miner has a DC/DC monitor that is occasionally unhelpful.
(possibly because you are stopping cgminer and starting bfgminer when it looks)
If it does this it will start cgminer.
This can occasionally happen when restarting bfgminer.
The solution is '/etc/init.d/cgminer.sh stop ; /config/bfgminer/bfgminer.sh restart'
(Advanced web page shows it running but bfgminer says nada or 'screen -r' says already running or somesuch)

MAKE NOTES!!!
16 different die in one box can be confusing.

Other fun toys are in the bfgminer(or a cgminer) source directory too.
read the file README.RPC
'less /config/bfgminer/README.RPC'
then look at
miner.php
^^^^^^^^^
(I run this on my PC,
it collects all miners into one place,
and shows more status of each core)

also look at
api-example
api-example.php
api-example.py

A lot can be done with just api-example (and grep)

Don't reboot, rarely needed, else rebuild bfgminer again after.
Just 'q'uit and run unmodified
'/etc/init.d/cgminer.sh restart'
instead.
(ways around this limitation exist but are beyond the already large scope of this post)

Hope this helps someone get over the hump and wake a sleeper and possibly into new GH territory.