Author

Topic: How do i config a number for each avalon 921 machine? (Read 83 times)

newbie
Activity: 39
Merit: 0
Yes, it would need a different version of the OpenWRt firmware. Hmm, looking at Canaan's download site for their latest OpenWRt firmware I see nothing for the RiPi-4 but do see a link for Libre's H3 computer. Pretty sure that I've seen info about using a RiPi-4 here in the Forum but don't see it offhand.

See my post in your other thread about AM's pricing.

Libre's H3 computer this is better than rasb 3?
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Yes, it would need a different version of the OpenWRt firmware. Hmm, looking at Canaan's download site for their latest OpenWRt firmware I see nothing for the RiPi-4 but do see a link for Libre's H3 computer. Pretty sure that I've seen info about using a RiPi-4 here in the Forum but don't see it offhand.

See my post in your other thread about AM's pricing.
newbie
Activity: 39
Merit: 0
A) Reduce the number of miners per controller.
For best performance, no more than 2 miners per AUC chain. It will drastically lower your number of Stales.
A couple reasons for that: the main one is that the RasPi-1, 2, and 3 LAN circuits goes through the USB coms. BTW, RasPi-4 fixed that and uses a dedicated connection between the network interface and the CPU - part of the reason they have better performance. The other reason is that is takes a fair bit of time to send/receive data from a miner and having that more than 2 on a chain slows things down a lot. The baud rate of each AUC is 400,000 B/sec. That is a large cause of Stales seen by a pool. A cluster produces significantly more stales as opposed to what say an A10/A11/A12 produces or even a 921 by itself.

B) Use a program such as Awesomeminer to monitor the miners.
Along with looking at each cluster on a controller as 1 big miner, AM has a toggle to let you look at each machine by itself. I highly recommend it. Their support thread in the Forum is https://bitcointalksearch.org/topic/awesome-miner-powerful-windows-gui-to-manage-and-monitor-up-to-200000-miners-676942

Thanks for your awesome reply and information.... this really helped me alot. I am definitely gonna buy 2 more rasberri controllers to reduce the number of miners on an AUC chain. Do you recommend Raspi-4? Anything different rom needed to flash?

Will also definitely try out awesome miner. Does awesome miner charge by 1 controller as a big miner? Or they charge by each individual avalon 921?
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
A) Reduce the number of miners per controller.
For best performance, no more than 2 miners per AUC chain. It will drastically lower your number of Stales.
A couple reasons for that: the main one is that the RasPi-1, 2, and 3 LAN circuit goes through the USB com channels. BTW, RasPi-4 fixed that and uses a dedicated connection between the network interface and the CPU - part of the reason they have better performance. The other reason is that is takes a fair bit of time (several 10's of ms per-miner on the AUC) to send/receive data between a miner and controller. Having more than 2 on a chain slows things down a lot. The baud rate of each AUC is 400,000 B/sec. That is a large cause of Stales seen by a pool. A cluster produces significantly more stales as opposed to what say an A10/A11/A12 produces or even a 921 by itself.

B) Use a program such as Awesomeminer to monitor the miners.
Along with looking at each cluster on a controller as 1 big miner, AM has a toggle specifically for handling how the Avalon 7xx, 8xx, and 9xx work in clusters to let you look at each machine by itself. I highly recommend it. Their support thread in the Forum is https://bitcointalksearch.org/topic/awesome-miner-powerful-windows-gui-to-manage-and-monitor-up-to-200000-miners-676942
newbie
Activity: 39
Merit: 0
I am currently running 20 avalon 921 per controller...

whats the best way to monitor to see which rigs are down or not mining properly?

Anyway to set up alerts for avalon 921?
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
If you are running a cluster with more than 1 miner per-controller, no. DNA is much like a serial number and is hard coded at the factory.
If you are only running 1 per-controller just add a tag to the worker name. eg, one of mine is called Fuzzy.Avalon841_Insp
newbie
Activity: 39
Merit: 0
I saw that DNA is what is used to identify each machine. Is there anyway i can set my own numbers for each machine?
Jump to: