I have done something else now which seems to make sense, I am testing it on a small number now: I use "Awesome miner" - a program to control your miners. Every 30 mins the program will reboot any controller that is below 240 MH. Seems to work quite well, but its early days. At least a temp patch ...

Well I think the lesson to learn is to stay on prohashing!

This may be a stupid question, but I actually dont know the answer:
Prohashing generally mines other coins than LTC although sometimes it does LTC as well. I realize there is a correlation between other scrypt coins difficulity and LTC difficulity, but would it be better for the overall LTC ...

I do get a lot of variation on the miners myself, and its very batch dependent. I have been travelling for a week so I will go back to fine tuning them now. I did reduce the mhz last night on some of the miners that was historically dropping and they stay on overnight at least.

I am back after some days of travelling. I have set one unit on the dev pool please let me know how that goes.
I see the "worker history" chart is pretty much "out there" - all the units except the first batch seems to make the graphs look weird, but it does not matter to me if the hash rate is ok ...

If you email me the details I will do that now.

After running now for a couple of days most machines seems to "fall off". I am not sure what to do. Trying to reboot them now, I guess they will go back up.

Hi tradewiz,
How do I you see the temperature? On my software the temperature box is blank. Also what are your rejects looking like. Thanks


PS Oh wait I just found temperature..LOL Here is what I am running right now I was running 810. I am going to go down to 805 for a bit

STATS ID Elapse TEMP ...

Hi tradewiz,
How do I you see the temperature? On my software the temperature box is blank. Also what are your rejects looking like. Thanks


PS Oh wait I just found temperature..LOL Here is what I am running right now I was running 810. I am going to go down to 805 for a bit

STATS ID Elapse TEMP ...

Because of a communication error I was not able to change the settings last night, however I had a few different settings working.
Setting one: Running d=1024 on two units. They don't seem to "stall" after a few hours, but one of them only had 188 MH in hash this morning.
Two units running H=100 d ...