Avalon ASIC users thread

[SolarSilver]

Where is a good place to follow the hash rate?

http://bitcoindifficulty.com/

or at the source

http://bitcoin.sipa.be/speed-lin-10k.png

[1713556681]

1713556681

[1713556681]

1713556681

[1713556681]

1713556681

[1713556681]

1713556681

[luffy]

during April it will be ~100TH with Avalon #2. (avalon earnings 3-4 BTC)
lets see if BFL will appear also. With 200TH earnings go to 1.5-2 BTC,...etc
even with 1PH avalon is profitable with current BTC value (i am expecting though btc>100$ before that)
long live Asics, long live Avalon team

[ewibit]

how to disable the blue LED?
(only with cutting?)
TIA

[arklan]

during April it will be ~100TH with Avalon #2. (avalon earnings 3-4 BTC)
lets see if BFL will appear also. With 200TH earnings go to 1.5-2 BTC,...etc
even with 1PH avalon is profitable with current BTC value (i am expecting though btc>100$ before that)
long live Asics, long live Avalon team

even with crazy difficulty numbers (like adding a 0 to go from 4.8 mil to 48 mil) even a jalepeno is profitable... assuming it's stats bear out, etc etc...

gonna be funny if i end up buying a jalepeno (i'm broke...) and using it to pay for an avalon.

[invader]

Is there someone who tried to move hashmodules lower? Does this improove cooling or not?
As i see, bottom fan just mostly passing cool air thru case (without fourth hashmodule)...

[SolarSilver]

Is there someone who tried to move hashmodules lower? Does this improove cooling or not?
As i see, bottom fan just mostly passing cool air thru case (without fourth hashmodule)...

One picture I've seen posted on a Chinese forum is this one:



but I'm not sure if this is much of an improvement, it would force all the air through the fins of the left module

[invader]

I really smiled when i seen this picture, this is a strange solution.

[SolarSilver]

I really smiled when i seen this picture, this is a strange solution.

I'm sure ngzhang will post that he puked when he saw that picture :-)

[invader]

So i moved the modules, and it seems to be better at first look.
WARNING: use your own mind when considering doing the same.

before

[2013-03-18 12:37:02] Avalon: Fan1: 0/m, Fan2: 2280/m, Fan3: 2280/m    Temp1: 22C, Temp2: -1C, Temp3: 45C, TempMAX: 46C

after

[2013-03-18 16:19:23] Avalon: Fan1: 0/m, Fan2: 2040/m, Fan3: 2040/m    Temp1: 19C, Temp2: -1C, Temp3: 44C, TempMAX: 44C

[Bogart]

I encountered the fan/temp bug again this morning.  I noticed it cycled the fans on maximum speed for about 200ms, and when I checked the cgminer status page again the temp and fanspeed readings showed non-sane values that varied rapidly and were sometimes negative.

It also stopped hashing.  I presume as a safety measure.

I let it go like this for about 3 minutes this time to see if it would recover.  It cycled the fans onto maximum for 200ms a few more times, but never did.

When I restarted cgminer via System --> Startup in the web UI, it then mined normally again and showed normal sensor values.

[johnyj]

Anyone have such high HW errors? What does this indicate?

   [Getworks] => 1963
   [Accepted] => 27062
   [Rejected] => 963
   [Hardware Errors] => 866
   [Utility] => 30.57
   [Discarded] => 3649

[Bogart]

Anyone have such high HW errors? What does this indicate?

   [Getworks] => 1963
   [Accepted] => 27062
   [Rejected] => 963
   [Hardware Errors] => 866
   [Utility] => 30.57
   [Discarded] => 3649

I did when I was overclocking with --avalon-options 115200:24:10:45:300

Changing to --avalon-options 115200:24:10:42:300 cleared it up for me (thanks to luffy for suggesting it).

Supposedly the fourth parameter is a "controller timeout".  I'm not sure why reducing it helps.

[cypherdoc]

I encountered the fan/temp bug again this morning.  I noticed it cycled the fans on maximum speed for about 200ms, and when I checked the cgminer status page again the temp and fanspeed readings showed non-sane values that varied rapidly and were sometimes negative.

It also stopped hashing.  I presume as a safety measure.

I let it go like this for about 3 minutes this time to see if it would recover.  It cycled the fans onto maximum for 200ms a few more times, but never did.

When I restarted cgminer via System --> Startup in the web UI, it then mined normally again and showed normal sensor values.

is there a way to automate the cgminer restart?

[Bogart]

I encountered the fan/temp bug again this morning.  I noticed it cycled the fans on maximum speed for about 200ms, and when I checked the cgminer status page again the temp and fanspeed readings showed non-sane values that varied rapidly and were sometimes negative.

It also stopped hashing.  I presume as a safety measure.

I let it go like this for about 3 minutes this time to see if it would recover.  It cycled the fans onto maximum for 200ms a few more times, but never did.

When I restarted cgminer via System --> Startup in the web UI, it then mined normally again and showed normal sensor values.

is there a way to automate the cgminer restart?

Probably.  I imagine the restart will be the easy part.  Detecting the failure condition programmatically will be the harder part.

[kano]

...
Probably.  I imagine the restart will be the easy part.  Detecting the failure condition programmatically will be the harder part.

Of course not ... my API has all sorts of information that will show the condition ... and if the API isn't working, you take that to mean the condition exists also.
Of course there are updates to the API but ...

[invader]

Someone asked if i moved all modules, or just one - the answer is
MOVE ALL THE MODULES

[Bogart]

...
Probably.  I imagine the restart will be the easy part.  Detecting the failure condition programmatically will be the harder part.

Of course not ... my API has all sorts of information that will show the condition ... and if the API isn't working, you take that to mean the condition exists also.
Of course there are updates to the API but ...

Cool.  I'm not too familiar with it.  Is it JSONRPC just like bitcoind?  Care to give a cookbook query string to get the current hashrate?

[johnyj]

Anyone have such high HW errors? What does this indicate?

   [Getworks] => 1963
   [Accepted] => 27062
   [Rejected] => 963
   [Hardware Errors] => 866
   [Utility] => 30.57
   [Discarded] => 3649

I did when I was overclocking with --avalon-options 115200:24:10:45:300

Changing to --avalon-options 115200:24:10:42:300 cleared it up for me (thanks to luffy for suggesting it).

Supposedly the fourth parameter is a "controller timeout".  I'm not sure why reducing it helps.

I tried different parameters, including the default 45/282 value, the result is almost the same, hardware error rate about 3% of accepted, and my ambient temp is -3 degree now
   [fan1] => 0
   [fan2] => 720
   [fan3] => 720
   [temp1] => -3
   [temp2] => -1
   [temp3] => 28
   [temp_max] => 28

[SZD]

How loud are these things? Also looks like if you have 20amp circuits you can only have 3 units per circuit  assuming you don't have a ton of other stuff already plugged in! Then maybe just 2. So much power use...

[opentoe]

I'm in the US. Will one of these work on my 15-20amp circuit? I have all 110V lines of course, regular house. Do I need to install a 240 or something?