look at this settings
https://bitcointalksearch.org/topic/m.660594
you should set MaxTemp, MinTemp and MaxClock
if not-try to delete aoclbf.ini and then reset all settings
Topic: AOCLBF 1.8.4 by WinD - Dynamic clocks adjusting Completely AUTOfanspeed - page 3. (Read 39960 times)
February 03, 2012, 09:17:40 AM
February 03, 2012, 08:14:27 AM
I used to mine on 5870.
I get strange problem. The miner mines with correct clock speed, then clock speed gradually reduces & mining also reduces.
I set 930/300 & from 930 it went down to 360 mhz in less than 3 minutes.
February 02, 2012, 08:13:10 PM
TESTING
February 02, 2012, 03:41:38 PM
done some optimizations in getting data from drivers
aoclbf_1.83b2_by_WinD
aoclbf_1.83b2_by_WinD
February 02, 2012, 10:26:19 AM
FRanz33
Can you launch a script itself? I wanna know what line in script causes an error.
p.s. seems to be an old error https://bitcointalksearch.org/topic/autoit-or-aoclbf-pheonix-rising-error-cant-open-21380
Can you launch a script itself? I wanna know what line in script causes an error.
p.s. seems to be an old error https://bitcointalksearch.org/topic/autoit-or-aoclbf-pheonix-rising-error-cant-open-21380
February 01, 2012, 09:52:20 AM
Dont know how to insert screen shots buuut.
Line 8708 (file "c:\Phoenix\aoclbf 1.83b.exe"):
Error: Array Variable subscript badly formatted.
on 5870 plus 5770 x2
Aggression 12 9 9 phatk2 256 930/300
5 min restart
Only unit with 3 cards (for now) only unit to fire an error even when pool was down for 12hrs
good Job. Almost there
Line 8708 (file "c:\Phoenix\aoclbf 1.83b.exe"):
Error: Array Variable subscript badly formatted.
on 5870 plus 5770 x2
Aggression 12 9 9 phatk2 256 930/300
5 min restart
Only unit with 3 cards (for now) only unit to fire an error even when pool was down for 12hrs
good Job. Almost there
January 30, 2012, 05:16:36 PM
so many changes in algorithm were done that I decided to start 1.83 number 
After testing it is 3-4 times lower in memory leak when a lot of disconnects occur.
Welcome aoclbf_1.83b_by_WinD
Thx After testing it is 3-4 times lower in memory leak when a lot of disconnects occur.Welcome aoclbf_1.83b_by_WinD
January 30, 2012, 04:57:55 PM
so many changes in algorithm were done that I decided to start 1.83 number After testing it is 3-4 times lower in memory leak when a lot of disconnects occur.
Welcome aoclbf_1.83b_by_WinD
After testing it is 3-4 times lower in memory leak when a lot of disconnects occur.Welcome aoclbf_1.83b_by_WinD
January 30, 2012, 03:32:30 PM
Yea that was a problem with 1.75 but you can get around it i think with longer reconnect times. Phoenix is no where near as prone to idle as it was in the past so this feature isn't as important. 1.75 is lacking so many features compare to 1.82b3 but i think the array error lies in one of those features you added because i dont remember seeing it until before then. I will be trying a test soon tho. Im getting new cards and will see if the array error comes up when i switch the cards out like it does with 1.82. Keep at it. i think your close!
January 30, 2012, 03:26:14 PM
conducted research for aoclbf 1.75 too. Result is that memory leak occurs! For testing I changed pools to wrong ones so miner was unable to connect and was continuously restarting. I watched for Commit charge By procexplorer and it was growing up very quickly. Now I did some changes in code to minimize leak but can't completely remove it while..
January 30, 2012, 08:42:45 AM
been using 1.75 on my 2x5870@930/300 for a couple days. NO array error...still testing. using Phoenix 1.7.5..will update in another 3 days
January 25, 2012, 04:31:43 PM
conspirosphere.tk
hashrate refreshes once per 2 sec
FRanz33
i'm close to fixing this ... but have no much time..may you launch 1.75 version on one machine for comparison?
hashrate refreshes once per 2 sec
FRanz33
i'm close to fixing this ... but have no much time..may you launch 1.75 version on one machine for comparison?
January 25, 2012, 09:47:42 AM
FRanz33
pity...how about your internet connection? Are there frequent breaks? How stable pools you are on? Are you sure your system memory is ok?
pity...how about your internet connection? Are there frequent breaks? How stable pools you are on? Are you sure your system memory is ok?
System Memory is fine..great in fact. Internet connection is ok to. I actually have multiple boxes on the same router in office spaces and at home and alot of times all of them on the same network are affected while other networks aren't. Sometimes only half on the same network while the other half are not. But i will say this. the more cards in the box the more likely the error. and i had another array error today and we solved to blocks early morning maybe there is a connection or something to do with the way long polling works idk. Im going to upgrade to Phoenix 1.7.4 from 1.7.2 to see if that helps. Im running half of my units with beta and the other half on release version. No difference.
January 24, 2012, 05:06:07 PM
I like it, but I wonder why the OSD shows an hash rate quite lower than what I get with Phoenix 1.7.x (with phatk2, same aggression).
On a 5870@970/300 I get 410-420 Mhs against 440 Mhs with Phoenix. Similar difference with a 5830 and a much smaller one with 2 5750.
Maybe it is just because hash rate does not seem to refresh frequently?
On a 5870@970/300 I get 410-420 Mhs against 440 Mhs with Phoenix. Similar difference with a 5830 and a much smaller one with 2 5750.
Maybe it is just because hash rate does not seem to refresh frequently?
January 24, 2012, 04:03:22 PM
FRanz33
pity...how about your internet connection? Are there frequent breaks? How stable pools you are on? Are you sure your system memory is ok?
pity...how about your internet connection? Are there frequent breaks? How stable pools you are on? Are you sure your system memory is ok?
January 24, 2012, 02:28:18 PM
Sorry to say still get an Array error with beta 3 however i did notice something that may help. The array error happened right after we solved a block and i think I caught it early on. The auto hide OSD helped alot tho!
January 22, 2012, 09:17:52 PM
brilliant. the hide osd by default is enough to mkae me deploy this beta on on my units! thanx will post results soon. also swtiching bck to my default restart times of 60 sec.
January 22, 2012, 03:29:23 PM
BigBobo
it seems to work with 7970. Unfortunately i am unable to test it.
2All
Catch aoclbf 1.82b3 by WinD
Another try to fix an array error
it seems to work with 7970. Unfortunately i am unable to test it.
2All
Catch aoclbf 1.82b3 by WinD
Another try to fix an array error
January 20, 2012, 07:52:20 PM
so how about those 7970 optimizations? 
January 20, 2012, 03:50:50 PM
FRanz33
farfiman
thanx for testing. i'm now working on optimizing the code . it'll be faster when disabling OSD and may be array and memory problem will be solved..i hope..
in plans is smth kinda sheduler to change aggression-useful for machines a user works on
farfiman
thanx for testing. i'm now working on optimizing the code . it'll be faster when disabling OSD and may be array and memory problem will be solved..i hope..
in plans is smth kinda sheduler to change aggression-useful for machines a user works on
Any chance of being able to save the hide OSD command? kinda annoying to hit hide osd every time it starts up. esp with array bug and having to restart every few days.
will be done Jump to: