|
Ja. It takes n+1 PSU's to pull/replace one without shutting down... A single PSU cannot be 'hot-swap'. Simple slide out/in for (power off) replacement, sure.
|
|
|
|
<snip> Using the Advanced Avalon config -- Perfect results. Visually now with top end of the graph at 15THs vs 50+THs is FAR easier to see a few THs drop from any 1 miner. Kudos for that  edit: Query, when using the Advanced Avalon config and reporting per-miner does the Restart button do a global restart of cgminer (all miners on controller) or just restart the 1 miner? Since the Avalon API does has provision for it the ability to actually reboot the individual miner would be nice. I will change the next release to display all individual miners on the ASIC tab for the case where you don't run with the Avalon-mode enabled. I'm also trying to get documentation on the Avalon unique reboot API from the vendor, as the API do have some parameters you can specify what to reboot, but it may not be on the individual miner level but on the AUC level. Upgraded main farm to 5.4.1 and Default Avalon mode ASIC's now display perfectly as they of course do when broken out using Advanced mode. As for Canaan's API call for individual miner reboot, all I can suggest is looking at their GIT for the code they use for their OpenWRT-based controller 'firmware' Odds are that part of their code is the same for all the Avalon series or at least A7-8's. |
|
|
|
Would this support asicboost?
Or more to the point, does it REQUIRE using a pool that supports AB? |
|
|
|
|
The problem is that perhaps up to recently, there has been little to no reason to ever change firmware. I've ran total of 78 Ants from the s1 up to s9 batch25 and never had reason to change it.
BM follows no rhyme or reason in the fan connection numbers. Numbering and what is what varies from batch to batch. That said - the fan connections are labeled on the board if one looks.
|
|
|
|
thinking mehh, they won't be that loud. So someone has not read anything about current miners for the past few years eh? Pretty much the first things mentioned in reviews are the noise and heat. They *are* industrial miners after all.... Before you ask about quieting them down: read through the hardware area about it first. |
|
|
|
... Why on earth fiddle with the firmware?  Yes the fan is dead. There are MANY threads about this in the Support thread... Try reading them |
|
|
|
w00t!  About freaking time.... |
|
|
|
Ok. I just bought an antminer s9 b22 with last firmware, very noisy, does awesome miner configure frequency is working with this batch?
No, Awesome Miner cannot change the speed. These are INDUSTRIAL miners and not intended to be ran where there noise is a problem. Perhaps try reading about them in the S9 thread located in the BTC hardware area... The miners use auto-tune and without modification their speed cannot be changed. That said, look in the BTC Mining software section for how this has been addressed with custom firmware for them. |
|
|
|
<snip>
Thanks for your feedback. This scenario is actually like in previous versions of Awesome Miner, where each of the "Avalon devices", not "Avalon devices status", listed in the web interface is represented as a device in the Awesome Miner ASIC tab.
The new implementation for Avalon must be enabled via the Properties of an External Miner, Advanced section. This will make the entire External Miner represent a single Avalon miner (instead of the entire controller).
What I will look into as well is to change the devices listed on the ASIC tab, as you pointed out with your screenshot. Instead of listing for example 2 "Avalon devies" like today, I could make it list all 6 "Avalon devices status" instead. Please note that this is only for the scenario where you use a single External Miner and looking at the entire controller. The main point with the new implementation was the new setting to make the entire External Miner represent a single miner.
As I pointed out, those results were using the default Avalon reporting with the main error being the number of miners reported per AUC (Device). As the one set of sshots shows in 1 case the 2 AUC's are correctly reported but number of miners attached to them is not. For default Avalon display I'd either leave it as just reporting the # of AUC's (original way) or if miners attached is presented then needs to be the right#. Using the Advanced Avalon config -- Perfect results. Visually now with top end of the graph at 15THs vs 50+THs is FAR easier to see a few THs drop from any 1 miner. Kudos for that edit: Query, when using the Advanced Avalon config and reporting per-miner does the Restart button do a global restart of cgminer (all miners on controller) or just restart the 1 miner? Since the Avalon API does has provision for it the ability to actually reboot the individual miner would be nice. |
|
|
|
Awesome Miner Version 5.3.11 (Development preview of 5.4)
The main content for this update (compared to 5.3.10):
1) Performance improvements in general and performance improvements related to when the profit switcher is making decisions, to make the user interface run smoother when you have a larger number of profit profiles
2) Avalon ASIC miners can be monitored individually even when Awesome Miner is connected to a controller with multiple miners. This can be configured via the External Miner Properties, Advanced section.
The public release 5.4 will be made available within the next few days.
You can also expect an early Beta version of Remote Agent for Linux within the next few weeks.
Thanks for responding so quick re the Avalons That said, there are now some new issues with them: When left in default (all on controller reported as 1 miner) the AISIC tab now is very inconsistent with what it reports... bank of 6 A741's as reported from GUI  Same bank as reported by AM -- only 3 are reported  Bank of 4 841's as reported via GUI  Same bank as reported by AM  And a real winner, bank of 4 841 reported A7's...  |
|
|
|
I might just do that or simply use the gimpy 741 as a donor miner for my others. I already have a 841 that should arrive today that will be taking the 741's power allocation so will actually be ahead in THs when I put it online and take the 741 off. One example of the thermal circuit boards are these from Epic https://www.epectec.com/pcb/aluminum-circuit-boards.html |
|
|
|
|
And the person who created the self-moderated thread is by definition -- the moderator. I can see the 'real mods' getting copies but again, aside from vile egregious and offensive post that the creator of said thread does nothing about then ja. they damn well should step in. Baring that -- hands off.
|
|
|
|
|
Query: In a self-moderated thread, when a post is Reported to Moderator, isn't the person who created the thread the one that gets the report and deals with it?
Aside from something pretty egregious why would the regular mods have any input? Do they also get a copy of the reported post?
|
|
|
|
Cool. Sounds/looks like they are using TLam(R) which is an aluminum-backed circuit board material made just for high power apps like this. Once again, as with the heat sink design just goes to show that Canaan has some pretty sharp designers. |
|
|
|
I did some homework before I posted, and then I did more homework as I waited. Hopefully it helps someone somehow
+ 1million for that  You are one of the few newbs here in a long long time who knows how to learn: 1st research and *then* ask questions. Most just say "give me a fish!" (a single answer). Ja, we'll give you a fish - a fish smack in the head. You asked "teach me to fish" (how does is work), lo and behold -- you get teachers. |
|
|
|
|
My guess is that his RasPi is DOA. 2 out of 3 that I've gotten last month (both branded Avalon ones from Blokforge, separate orders) were dead. In 1 the CPU instantly got literally smokin' hot, the 2nd no signs of life at all. BF of course promptly replaced both.
|
|
|
|
We luvz our BLOCKZ!
|
|
|
|
|
No, only 1 fan is working. The one reading 720 is only spinning because of the other fan forcing air through it. Usually it is the exhaust fan that dies.
|
|
|
|
|
Quick question: I'll find out when I get the replacement 841 next week sometime and open up the 741 but you mention repasting the chips - but only the top side. What does the back of the boards look like? Bare filled thermal vias (bumps) w/paste directly against the large back side heat sinks or is there layer of TIM between board and heatsink?
When repasting the top side of chips and their smaller heat sink, any reason not to do the backside as well? Aside from needing to when doing board swaps of course.
|
|
|
|
|
Show Posts
