Regarding your temps, what temps are you getting? I noticed my rig was starting to drop performance no matter what firmware I used, even going back to my faithful 0.96 firmware didn't seem to make much difference. (circa 530Gh/s av)

However I had noticed that the ambient was getting pretty bloody cold here, so I moved it to a warmer location and performance jumped around 10Gh/s, then I reloaded 0.96 (always seems better for this rig, lower voltage, more stable) but wanted more realistic output from cgminer so loaded up ckolivas' latest 3.8.2 without tuning. And low and behold, the higher temps, the best firmware and more accurate cgminer and I'm back up to 550Gh/s avg over 24 hours, with spikes up to 600+Gh/s

Thing is edgar, these machines aren't perfect, they are enthusiast level, makes sense really for the market they are in. And as such they need a bit of TLC to get the most out of them. Yes some will be broken and need RMA'ing as a last resort, but there is no hard and fast rule that works for each one, and I think that finally KnC have realised this too, the tuning suite sounds more like you will be able to tune each ASIC separately for voltage, hopefully speed and maybe some other things.

This isn't going to mean that someone will give the "magic settings" that will work for everyone, if anything it means more work to find the best "tune" for your particular rig. Its a bit like overlcocking CPU's or GPU's no-one elses settings are quite right for your particular hardware.

I mean, I guess, they could have set a generic right-for-everyone 400Gh/s firmware but I think they knew that their hardware had more potential, probably a bad move on their part shouting about the upper limit of the October batches, but it sold alot of miners I bet!

I've been pretty happy with 530Gh/s but with difficulty increasing I'm looking to squeeze as much out of this puppy as I can, so today its remove the blue power cables and plug the Pcie's straight into the boards

This is an enthusiasts forum, and people are allowed to get enthusiastic, believe it or not Phoenix and the others in here have help loads of people get their machines working nicely. I for one think they are doing a great job and should continue. I salute their successes and apply what tweaks work for my rig, sometimes I even pass on things that have worked for me.

Thats the nature of forums like this, no offence, but it doesn't seem like it suits your nature. I just wonder what you actually want from this forum? Can you spell it out? Maybe bullet point it or something so that you have a record of the things you want addressed. Can't promise anything mind but it might help us understand why you seem so angry. 

Mining Status
CGMiner Status   Running (pid=1774)
Last Checked   Mon Nov 25 09:31:45 UTC 2013
Avg. Hash Rate   563 Gh/s
Difficulty Accepted   9,110,016
Difficulty Rejected   5,120 (0.1 %)
Hardware Errors   84,158 (0.9 %)
WU   7,852
Difficulty Stale   0
Network Blocks   146
Pool Rejected   0.1 %
Pool Stale   0
Best Share   2,235,713
Found Blocks   0


these is beta 0.98.1
is ok?

thanks ckolivas

I am not sure this is the right place for this but this seems to be a catch all thread so here goes.

I have 2 late October Jupiters.  One I was able to get to 550 with all cores running under 98.1 beta.  The other has 2 cores on one board that will not work until 73C or 74C and as soon as they start the whole board shuts down (I assume thermal shutdown) so it only works at around 480.

I was living with that (not economically feasible to give up 480 hashes for 2 weeks to rma the thing just to maybe get another 60 or so).

Now the problem.  I shut the full speed unit down for a few minutes to change locations and when I restarted it cgminer fails to start.  The bone boots and I can tty into it.  I can try to manually start cgminer and I get a "cgminer failed to start: Write Error".

I tried changing firmware.  Cgminer will run on 98 but not on anything after and on 98 I have all die 0s dead.

Anyone have any clues?

TaggedYa

Trouble shooting wise.

Make sure all the power cables are correctly attached.
Do a hard reset on the device:


Also:
From the KNC support page: https://www.kncminer.com/pages/troubleshooting


Lastly, If you can isolate the bad board, then you can just return that bad board for an RMA and the miner can continue mining, you don't have to lose the entire miner and 480Gh/s just for one bad board.

write error could mean the beaglebone storage is full or corrupted.

in putty:
df -h will show the disk space
fdisk -l will show the partition info

nothing new if in some weeks means March

Reporting between the two is identical.

The tuned one simply changes the decision making process about when to turn a core off and back on. Firstly it turns all cores on every time it's starting. However it turns cores off very quickly instead of after many errors, but turns cores off in a staggered fashion a few seconds apart. Then it turns them back on after only a minute, but will only turn cores back on if no core on/off has happened for the last minute staggering them much more to turn them back on. My observations were that turning dud cores off always helps the hashrate so making it easier to turn cores off made sense, but with rapid changes to the number of cores on/off, the power going to the units changes wildly when in fact the device will be more stable if it only ever changes power requirements slowly, hence the changes. It also increases the duration cores are off every time they fail before disabling them permanently (for that run of cgminer).

Anyway I find the hashrate and consequently the hardware error rate keeps improving over time as only the decent cores are left hashing, and cores that are borderline turn on and off intermittently in a staggered way that doesn't change the power requirements dramatically.

No man ..checked already ......what could be any other reason ......

not enough power?