Avalon A7 announced

[727miner]

My 741 showed up today a day early and it's happily hashing away. I'm very pleased with the turnaround from Canaan. What do you guys recommend setting the voltage and fans at to keep it quieter? I have it running in my home office and the ambient room temperature is about 78.

I tested

 0  higher speed of hash  fan and watts then -1                       1200 watts
-1  higher  speed of hash fan and watt then -2                       1100 watts
-2   lowest speed of hashlowest fan speed watts. are lowest.  1000  watts


if noise is key -2 is the way to go.

Thanks Phil, I'll try that out. She's screaming right now, so I'll need to quiet it down or host it somewhere else.

[1713536710]

1713536710

[1713536710]

1713536710

[NotFuzzyWarm]

snip
Thanks Phil, I'll try that out. She's screaming right now, so I'll need to quiet it down or host it somewhere else.

Well as rule#5 in Bitcoin Mining 101 states: Bitcoin miners are LOUD.

Ya can be toned down a bit but no getting around it.

[727miner]

snip
Thanks Phil, I'll try that out. She's screaming right now, so I'll need to quiet it down or host it somewhere else.

Well as rule#5 in Bitcoin Mining 101 states: Bitcoin miners are LOUD.

Ya can be toned down a bit but no getting around it.

Yeah, I've had plenty of miners in the past (S1 - S5 & SP20) so I know the drill on noise. In my ideal world it'd sound like an S3, which I could keep next to me on the desk  .

[philipma1957]

snip
Thanks Phil, I'll try that out. She's screaming right now, so I'll need to quiet it down or host it somewhere else.

Well as rule#5 in Bitcoin Mining 101 states: Bitcoin miners are LOUD.

Ya can be toned down a bit but no getting around it.

Yeah, I've had plenty of miners in the past (S1 - S5 & SP20) so I know the drill on noise. In my ideal world it'd sound like an S3, which I could keep next to me on the desk  .

If you do -2 try setting fan minimum at 35

It will prevent ramp up and down .

I get it to stay near 55 percent with those settings.

Loud but not unbearable.

[fusion0389]

Sent off my BTC payment. Apparently Avalon sold out of their 741's however they will be receiving in another shipment "whatever that means" this weekend. My order is supposed to ship on monday :| wish it was going out this week but, whatever, still faster than BITMAIN.

On a side note, is there a pro\con to daisy chaining all of the miners off of one controller? I understand each one can handle up to 20 miners. Does this pose any problems?

[NotFuzzyWarm]

Sent off my BTC payment. Apparently Avalon sold out of their 741's however they will be receiving in another shipment "whatever that means" this weekend. My order is supposed to ship on monday :| wish it was going out this week but, whatever, still faster than BITMAIN.

On a side note, is there a pro\con to daisy chaining all of the miners off of one controller? I understand each one can handle up to 20 miners. Does this pose any problems?

Only 3 cons:
1.All miners on 1 controller show up in the pools and monitor sw like Awesome Miner as 1 big device
2.Single point of failure if RasPi dies
3.When updating the MM firmware it is applied to ALL miners on the controller. NP if they all are the same model, not good if you mix say 721 and 741 miners on the 1 controller. Been there - done that and 721's don't like thinking they became 741's....

[Vyazhan]

snip

Did you receive your presents yet from Canaan?

[NotFuzzyWarm]

re: ^^
Maybe look back a page or 2 for the pretty pictures... 

[fusion0389]

Only 3 cons:
1.All miners on 1 controller show up in the pools and monitor sw like Awesome Miner as 1 big device
2.Single point of failure if RasPi dies
3.When updating the MM firmware it is applied to ALL miners on the controller. NP if they all are the same model, not good if you mix say 721 and 741 miners on the 1 controller. Been there - done that and 721's don't like thinking they became 741's....

1. So, I guess from a management perspective if one miner in the chain goes down you've gotta dig into figuring out which miner is having the issue. Is that the main con?
2. Valid point, I don't really have any experience with raspi, are they generally reliable or are they more prone to failure?
3. I will have 741's only, so not an immediate issue, but good to know.

[Vyazhan]

re: ^^
Maybe look back a page or 2 for the pretty pictures... 

Doh! Thanks, I was sure I had a thorough look, but all the splitting must have had me in a swirl pretty neat!

[NotFuzzyWarm]

Only 3 cons:
1.All miners on 1 controller show up in the pools and monitor sw like Awesome Miner as 1 big device
2.Single point of failure if RasPi dies
3.When updating the MM firmware it is applied to ALL miners on the controller. NP if they all are the same model, not good if you mix say 721 and 741 miners on the 1 controller. Been there - done that and 721's don't like thinking they became 741's....

1. So, I guess from a management perspective if one miner in the chain goes down you've gotta dig into figuring out which miner is having the issue. Is that the main con?
2. Valid point, I don't really have any experience with raspi, are they generally reliable or are they more prone to failure?
3. I will have 741's only, so not an immediate issue, but good to know.

Ya. The only way to easily see the status of each miner is to use the Avalon GUI. It will ID the AUC adapters and the miners attached to them, tell you how fast each is running, etc. There you can make a miner's LED blink so you can pinpoint which is which.

Can't say I've ever had a RasPi fail but is still the Achilles heel to what can be a very large amount of hash power. Then again, easy enough to have a spare Pi already configured as you want to just plug in.

My biggest issue would be that because all the miners are reported to pools as 1 worker if there are say 10 miners on the 1 controller and 1 miner drops out or loses speed it will not be apparent for a while if you only look at the pool stats for that (huge) worker.

[fusion0389]

Only 3 cons:
1.All miners on 1 controller show up in the pools and monitor sw like Awesome Miner as 1 big device
2.Single point of failure if RasPi dies
3.When updating the MM firmware it is applied to ALL miners on the controller. NP if they all are the same model, not good if you mix say 721 and 741 miners on the 1 controller. Been there - done that and 721's don't like thinking they became 741's....

1. So, I guess from a management perspective if one miner in the chain goes down you've gotta dig into figuring out which miner is having the issue. Is that the main con?
2. Valid point, I don't really have any experience with raspi, are they generally reliable or are they more prone to failure?
3. I will have 741's only, so not an immediate issue, but good to know.

Ya. The only way to easily see the status of each miner is to use the Avalon GUI. It will ID the AUC adapters and the miners attached to them, tell you how fast each is running, etc. There you can make a miner's LED blink so you can pinpoint which is which.

Can't say I've ever had a RasPi fail but is still the Achilles heal to what can be a very large amount of hash power. Then again, easy enough to have a spare Pi already configured as you want to just plug in.

My biggest issue would be that because all the miners are reported to pools as 1 worker if there are say 10 miners on the 1 controller and 1 miner drops out or loses speed it will not be apparent for a while if you only look at the pool stats for that (huge) worker.

Thats a good point. I am also trying to think ahead about scalability issues. If i theoretically were to buy 20 of the miners and send them off to hosting, or build out my own version of a gigapod i am not sure the best way to set that up. Buy a controller for each unit? I think while i have the equipment here, locally, 4 per controller would be pretty simple.

[philipma1957]

Only 3 cons:
1.All miners on 1 controller show up in the pools and monitor sw like Awesome Miner as 1 big device
2.Single point of failure if RasPi dies
3.When updating the MM firmware it is applied to ALL miners on the controller. NP if they all are the same model, not good if you mix say 721 and 741 miners on the 1 controller. Been there - done that and 721's don't like thinking they became 741's....

1. So, I guess from a management perspective if one miner in the chain goes down you've gotta dig into figuring out which miner is having the issue. Is that the main con?
2. Valid point, I don't really have any experience with raspi, are they generally reliable or are they more prone to failure?
3. I will have 741's only, so not an immediate issue, but good to know.

Ya. The only way to easily see the status of each miner is to use the Avalon GUI. It will ID the AUC adapters and the miners attached to them, tell you how fast each is running, etc. There you can make a miner's LED blink so you can pinpoint which is which.

Can't say I've ever had a RasPi fail but is still the Achilles heal to what can be a very large amount of hash power. Then again, easy enough to have a spare Pi already configured as you want to just plug in.

My biggest issue would be that because all the miners are reported to pools as 1 worker if there are say 10 miners on the 1 controller and 1 miner drops out or loses speed it will not be apparent for a while if you only look at the pool stats for that (huge) worker.

Thats a good point. I am also trying to think ahead about scalability issues. If i theoretically were to buy 20 of the miners and send them off to hosting, or build out my own version of a gigapod i am not sure the best way to set that up. Buy a controller for each unit? I think while i have the equipment here, locally, 4 per controller would be pretty simple.

if buy solar and I end up with say 18   741's  we would use  6 rasp pi's   3x   741's per rasp pi  .

this gives you spare usb to 4 pin translation dongles  

along with finksy 4 k psu's 3  pieces per rasp pi is a working plan for our future build out ( if we do it)

Set 1 of 3 741's
power brick
usb cable
rasp pi
usb cable
dongle for translating usb to 4 pin signal.
four pin
avalon --1
four pin
avalon --2
four pin
avalon --3
a finksy 4k psu
------------------------------

Set 2 of 3 741's
power brick
usb cable
rasp pi
usb cable
dongle for translating usb to 4 pin signal.
four pin
avalon --1
four pin
avalon --2
four pin
avalon --3
a finksy 4k psu

------------------------------------




that dongle is hard to source.

when you buy an avalon

you get
1 dongle
1 usb
1 four pin wire
1 avalon


by using 3 to   a rasp pi    you conserve your translation dongles

[tbonetony]

My four A741 arrived yesterday but I am only running two in a daisy chain due to lack of PSU's.

I have noticed the first A741 (immediate to AUC) consistently rebooting itself every once a while (10 ~ 60 minutes) for unknown reasons. I have swapped module and this issue persists so I started to think if the controller has some issues.

Does anyone share my experience here?

[philipma1957]

My four A741 arrived yesterday but I am only running two in a daisy chain due to lack of PSU's.

I have noticed the first A741 (immediate to AUC) consistently rebooting itself every once a while (10 ~ 60 minutes) for unknown reasons. I have swapped module and this issue persists so I started to think if the controller has some issues.

Does anyone share my experience here?

What volt setting are you on +1 and 0 May stress the psu.

Try -1 or -2

[tbonetony]

My four A741 arrived yesterday but I am only running two in a daisy chain due to lack of PSU's.

I have noticed the first A741 (immediate to AUC) consistently rebooting itself every once a while (10 ~ 60 minutes) for unknown reasons. I have swapped module and this issue persists so I started to think if the controller has some issues.

Does anyone share my experience here?

What volt setting are you on +1 and 0 May stress the psu.

Try -1 or -2

Thanks, Phil. I think you nailed it. It did seem to relate to the power.

I had a pair of HP PSU that i used to power S9. Their spec is 800w @ 110V and 1200w @ 220V. On my newly installed 240V circuit, it may be getting marginal when using one to power A741 @ Voff = -1.
I have thrown both PSU's on that A741 and now it can run stably @ Voff=0.

[Michael20]

How is the hashrate and the wattage on the different volt settings?

[PeaMine]

My 741 showed up today a day early and it's happily hashing away. I'm very pleased with the turnaround from Canaan. What do you guys recommend setting the voltage and fans at to keep it quieter? I have it running in my home office and the ambient room temperature is about 78.

I tested

 0  higher speed of hash  fan and watts then -1                       1200 watts
-1  higher  speed of hash fan and watt then -2                       1100 watts
-2   lowest speed of hashlowest fan speed watts. are lowest.  1000  watts


if noise is key -2 is the way to go.

Thanks Phil, I'll try that out. She's screaming right now, so I'll need to quiet it down or host it somewhere else.

Pretty much this, though in cooler temps I see a bit higher rates and energy usage, but optimal efficiency.

[fusion0389]

Only 3 cons:
1.All miners on 1 controller show up in the pools and monitor sw like Awesome Miner as 1 big device
2.Single point of failure if RasPi dies
3.When updating the MM firmware it is applied to ALL miners on the controller. NP if they all are the same model, not good if you mix say 721 and 741 miners on the 1 controller. Been there - done that and 721's don't like thinking they became 741's....

1. So, I guess from a management perspective if one miner in the chain goes down you've gotta dig into figuring out which miner is having the issue. Is that the main con?
2. Valid point, I don't really have any experience with raspi, are they generally reliable or are they more prone to failure?
3. I will have 741's only, so not an immediate issue, but good to know.

Ya. The only way to easily see the status of each miner is to use the Avalon GUI. It will ID the AUC adapters and the miners attached to them, tell you how fast each is running, etc. There you can make a miner's LED blink so you can pinpoint which is which.

Can't say I've ever had a RasPi fail but is still the Achilles heal to what can be a very large amount of hash power. Then again, easy enough to have a spare Pi already configured as you want to just plug in.

My biggest issue would be that because all the miners are reported to pools as 1 worker if there are say 10 miners on the 1 controller and 1 miner drops out or loses speed it will not be apparent for a while if you only look at the pool stats for that (huge) worker.

Thats a good point. I am also trying to think ahead about scalability issues. If i theoretically were to buy 20 of the miners and send them off to hosting, or build out my own version of a gigapod i am not sure the best way to set that up. Buy a controller for each unit? I think while i have the equipment here, locally, 4 per controller would be pretty simple.

if buy solar and I end up with say 18   741's  we would use  6 rasp pi's   3x   741's per rasp pi  .

this gives you spare usb to 4 pin translation dongles  

along with finksy 4 k psu's 3  pieces per rasp pi is a working plan for our future build out ( if we do it)

Set 1 of 3 741's
power brick
usb cable
rasp pi
usb cable
dongle for translating usb to 4 pin signal.
four pin
avalon --1
four pin
avalon --2
four pin
avalon --3
a finksy 4k psu
------------------------------

Set 2 of 3 741's
power brick
usb cable
rasp pi
usb cable
dongle for translating usb to 4 pin signal.
four pin
avalon --1
four pin
avalon --2
four pin
avalon --3
a finksy 4k psu

------------------------------------




that dongle is hard to source.

when you buy an avalon

you get
1 dongle
1 usb
1 four pin wire
1 avalon


by using 3 to   a rasp pi    you conserve your translation dongles

Meaningful conversations like this one is the reason I love this place I had no idea those USB dongles were hard to source. That is good to know, I can now plan for that.

[Jarkss]

I am thhinking, is it really more in advantage to mine bitcoins thhan to just buy them in exchanges? Can we mine Bitcoin Cash with this miner?