tradewiz wrote:CritterDog wrote:Steve Sokolowski wrote:
That's all g=off would affect, so most likely it will not cause you increased hashrate in that case. I didn't think it would solve the problem anyway, but it was worth a shot.
Get back to Chris with the exact times the problem is occurring and he'll try to cross-reference what was going on in the database to see if any of the errors are pertinent to you.
Hi Steve I wrote Chis last night.. It seems my router has gone out completely. I am dead in the water on the A4 until I get a replacement which is on order.. Lets hope that was the problem all along.. Also on Monday I have another A4 arriving just one piece @ 136Mhs with control board. So that will put me around 400Mhs.. These A4s are going to be a hit. Way better then the A2. I expect to start seeing many come on line.. I got mine before the pre-order group.. So they are just now starting to roll in.. Be ready 
Ok thanks and I wrote Chris a PM about the failing router. So we are in a waiting mode.
I am having the same issues as you with dropping hash rate. On Litecoinpool the units are stable around 265 MH. Working on different solutions now and will share when I get some conclusions. You may know it already but one control board can be used on 3 units, while they supply a control board for every 2 units.
I did some research into this and determined that exactly half the shares you would expect to be submitted are being submitted by these miners. At first, it sends all the shares, and then the share frequency gets cut in half. Since the hashrate is a 2h average, it appears to decline over the course of 2h when the drop was actually instantaneous.
There are a few possibilities for this that I think everyone should try, and depending on what is found, this fix may be a pool software bug, a miner configuration issue, or a defective miner.
The first theory is that these miners are "forgetting" the current difficulty and getting stuck at a previous difficulty setting. The pool only sends difficulty settings when a new difficulty is required, but perhaps these miners missed the difficulty set message. The broken router or some other connection problem would cause this problem by dropping packets. The result would be that the miners think the difficulty is twice as high as the pool does, and therefore they withhold shares that they should be paid for. The issue is more likely to occur here because the difficulty never changes at a litecoin-only pool.
To try to resolve this problem, there are several choices. The first is to try omitting the "d=" password argument, so that the difficulty gets changed by the system more often. The other is to try setting "d=32768," because all of the miners I've seen this issue with have their difficulty setting at 65536. Perhaps 32768 is the setting that these miners use as default when they miss an override setting. If the problem improves, then I will modify the software to send the same difficulty every 2m to all miners, so that the longest this issue could possibly occur for is 2m instead of permanently.
Another possibility is that one of the boards in the miner goes offline because of a hardware fault. The shares coming out of the miner would drop by half, and we would see the same statistics reported, but the cause would be a hardware error. This would be a more likely cause if it's always the same miners causing the problem every time.
