Probably somewhere in the neighborhood of 12TH per machine, 0.1J/GH efficiency. A lot of the network is powered by industrial miners paying between 2 and 6 cents per kilowatt-hour.
I'd go with those numbers except use $0.10/kwh - since that is a typical home users power - and also a number that scales easily. |
|
|
|
micro USB cable makes sense to include, we will include with AUC from here forward.
Thank you. I lost a few hours wondering what I was doing wrong (it was my first experience with Avalons) until it occurred to me. Fortunately had some new long data cables, and have since ordered some more appropriate short ones. In any case, including the cables would have resulted in a bit more remaining hair on my head. |
|
|
|
I prefer to label them independently, for the sake of monitoring more precisely. If 1 miner is showing symptoms, I can easily see it on the "worker" page. Takes out ALOT of guess work.
Agreed. |
|
|
|
anyone see any issue with placing the PSU on top of each unit or would it be best to space them?
I place my Antminer APW3++ power supplies on top, on their side, with the angled section aligned to the frame of the Avalons. Looks nice, works fine. |
|
|
|
Yep but the best way is to always test it over a week or 2.
Thanks for the comprehensive info
Only if you like to gamble. Even Slushpool has good weeks and bad weeks. Its why their webpage displays their 250 block "luck" - since that should always be close to 100%. I've seen plenty of times when the other stats there were well below 100%. Likewise, if you look at the KanoPool block stats, their 500 and alltime average are around 100%, all stats under 50 blocks are well over average, the others are below. This is not a game to be played for "a week or 2". Do not confuse "luck" with "fate" - one looks backwards, the other forward, and they are only randomly in sync. Its like saying "I predict that half the time you flip a coin it will come up heads" and saying I'm good predictor for future things. |
|
|
|
Yes, you can, same as you can run 721/741's together BUT with 1 caveat: DO NOT apply any miner updates (.mcs files) to them together!
mm updates are applied to all miner on the controller and the mm update files are tailored to a specific miner. Trust me, an x21 or x41 miner will not like thinking it just became a different type. Been there, done that mixing 721/741's. Fortunately once you separate the miners it is easy to back out of the problem by flashing with the correct miner-specific files.
Excellent point. For reasons of pure aesthetics (it worked out well for me with my shelving and I have plenty of old Pi 1s) I separated mine out - but that is a great point. I've only had my Avalons for a few days, so haven't needed to do any mm upgrades yet. |
|
|
|
Got it and thank you. The room is in the basement so I won't have any issues with intakes. I do have a small window in the room though, I've cracked it now and it is cold enough outside to keep the room at a decent temp. I should be able to rig an exhaust for it pretty easily. If I make up a wood cabinet for the unit I can add the exhaust system to it at the same time.
Home Depot style stores (or Amazon) sell 8" dual window fans that work pretty well. The one I have can even have one fan running forward and the other backward - although that is naturally not particularly efficient. God news is they are cheap, like $25 or some such. |
|
|
|
|
I have diffs that vary from 10.x to 13.x - I'd consider those normal and just move on.
|
|
|
|
|
For what its worth, I use Bitmain APW3++ power supplies for my 841s (mostly because I seriously overbought them). I have them on top at a bit of an angle - aligning the APW3++ angled edge to the power connector side of the 841s - it almost looks like they were designed to do that (eg. Its aesthetically pleasing)
|
|
|
|
I did have a couple of questions.
1. What are the two numbers for hash rate I see at the top? It currently shows Hash Rate:12.16/10.78THs
2. What's a decent temp for the S9. I saw the max was 125 but where's a good spot to keep it. And I'm also guessing that number showing in my miner status is Celius?
3. Is there a good post detailing what all the stats on the kano.is site are?
1) I'm guessing your referring to the top of the Miner Status page? GH/S(RT) is "real time" - think "this moment", GH/S(avg) is "average over time". Not sure of the time period, but feels something like 5-10 minutes. Ignore RT, focus on avg - its more meaninful. 2) Chip temps in the 80s (yes Celsius) is decent. 100 is high. 115 (or possibly 125) is thermal auto-shutdown. My chip temps are in the high 60's (C), but I'm using outside air (40F right now) with some recirculation from my hot aisle to try and feed them 60F-65F air. You really need to figure a way to vent that hot air outside. Many who have a few S9s use 6" flexible ductwork to do that. If you hot air exhaust mixes with your cold air intake you are likely going to have heat problems - especially in a closed room. |
|
|
|
Over a month ago Canaan announced in the Forum that the AUC3 dongles are now sold separately. That is also clearly stated in the sales copy on all of their distributors websites. Bit of a PITA I agree but considering each dongle runs 5 miners it does make sense. I've been lucky and still had a few spare AUC's from buying my 721/741's last year.
What I *would* like to see included with each AUC is a USB-A to micro-USB data cable. A lot of times folks find that cables they have on-hand are actually charger/power cables that do not support data transfer. Ran into that last night when hooking up my new miners...
As for the controllers, aside from needing one per type (A721, 741, 821, 841) each controller will run up to 20 miners so is not that big of a deal when you have several miners...
Minor corrections: You can run 821s and 841s together on the same controller. Did that for a day while I figured out my Pi 1 issue. The firmware is the same for both. Also, some distributors are packaging things differently than Blokforge. CryptoUniverse (mostly European but ships internationally) includes an AUC3 and the USB-A to micro-USB data cable with their 841 sales ( https://www.cryptouniverse.at/shop/avalonminer-841/), but does not including shipping in their price. |
|
|
|
Honestly, almost any other pool is better than antpoo. Kano, Slush....all better choices.
U have detailed numbers of this? You can start here: https://en.bitcoin.it/wiki/Comparison_of_mining_poolsThe two key aspects are: Fee percentage (lower is better) & transaction fees being shared During the boom last December, transaction fees topped 40% of the block reward. That means pool operators that did not share those fees got rich off their miners work. After that, fee percentage rules - if you pay less, you earn more. Pretty simple. It gets a bit more complicated when you go down to the next level. PPS is straight forward, but high risk for the pool operator, so their fees typically range about 4%. PPSLNS (and various variations) pay when the pool gets a block. That raises your variance (how regular your payments are), but allows for a lower fee since the pool operator is taking less risk. Then there is size. Mining is typically a long term endeavor, but that doesn't mean you might be happy with getting a big payout once a month. If the pool is too small that is the risk (or even less often for some rather small pools). Pools like Slushpool typically find dozens of blocks a day, so the payouts are pretty smooth. Kano sized pools find a few blocks a week - not bad. Over a long enough time period, that aspect should blend out to be the same for everyone (presuming they find blocks on a reasonable schedule - not once a year!). Remember: If the pool you select is small, your payout frequency may be long, but the amount will be bigger - given everything else is equal (fees, transaction fee sharing, etc). I should also point out that any pool claiming to pay more than 100% is getting those rewards from somewhere. If you see that, read the fine-print. Pools are not free to run or maintain, they need to charge something to do so unless they are very very small and running in someones basement. Nothing wrong with that, but your not likely to get the best support, nor will the pool be able to grow much, with such an endeavor. For instance, one recent pool is advertising 105% payout. If you read the fine print, that payout is guaranteed so long as the transaction fees are AT LEAST 10% of the block reward. The 105% simply referred to the block reward, not the combined block + transaction reward. |
|
|
|
Guys is the site down?
Not for me. |
|
|
|
Cool...that will give me the opportunity to experiment w/12v battery bank power and dongles...I'll experiment on the t9, it really was a bad investment from the start. But sometimes knowledge comes w/a price too!
If it makes you feel any better, I bought (2) T9s at $2008 when you couldn't get S9s. Just really glad now they had a limit of 2 per batch. Both have been replaced once by Bitmain. The first lasted 2 weeks, the second 6 weeks. The units they sent me back are a slightly different design (they are taller). I consider both educational expenses. |
|
|
|
they are showing alive. password is x, but when i go to the site and sign in, the GH/S rate in top right corner is 0, my userne is not showing up in the worker list, on the worker shift graph, shows no workers.
I configured the miner as per instructions, using my username. I just want to make sure work is being counted and I will be paid. I dont have all 50 on line yet, still waiting on the remainder to arrive. I just want to get the first ones running correctly.
Your miner configuration should look something like this:  Of course, use your username and worker id instead of ccgllc.4100 (unless, of course, you want to donate your hash to me! <yes, that is a joke>). |
|
|
|
|
Found it. Stupid User Error.
S9s all come configured to mine on Antpool, and in fact will do so once powered up until you get around to changing it.
I expected the same behavior from the L3s, and a quick glance showed they had pool definitions. What I didn't notice is that the pool definitions were all invalid. Once I pointed the miner to my chosen pools, they came up quickly.
This was complicated by apparent support by Awesome Miner, which was a bad assumption on my part. AM can monitor them just fine, but apparently can't control them as well as it does S9s.
So just a bit of newbie growing pains.
|
|
|
|
Who are you guys using for shipping the S9's? UPS - DHL - Fedex
I have used UPS going to Michigan and my god the fees... customs crap, etc.
Have read about DHL and have heard positive things but when you select them on bitmain they say it could be a longer period for shipping.. is that true.
Any input would be helpful, appreciate the time and help... and the Great Pool!
Brickman
I use Fed-Ex exclusively now when working with Bitmain. They are less expensive than UPS and now that I'm on file with them, I've never had a customs issue. They also charge me less in customs fees than UPS (and then, somewhat randomly on orders under $2500). I also found things I ordered with Fed-ex came upwards of a MONTH before things I ordered via UPS. I have no idea why, but it happened on at least 3 orders. Has not happened recently though - but the lead times are a lot shorter now. |
|
|
|
Hi all. I run over a 100 S9s so am somewhat familiar with Bitmains front ends. Just received my first (4) L3+s. Hooked them up, powered them up (with APW3++s running on 220V), and waited. And waited. And waited some more (now 53 minutes), and all I get is the basic web screen. S9s can take over 20 minutes during their first boot to scan the cards. Figured the L3+ has 4 cards vs. the S9s 3, so it might take a half hour or so. Now its been substantially longer than that. Also find it odd that the kernel log is blank on all 4. I can web into them, but otherwise zip. Any suggestions? Zero experience with these things. Bought them because I had room in my data center, $400 coupons to burn, and a strong curiosity. Correction: Kernel log was just VERY slow to respond. Looking for errors I found the following repeating in the logs: Apr 3 23:38:37 (none) local0.err cgminer[8003]: Get [1]Temp Data Failed!
Apr 3 23:38:37 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][12]@ChainID:[0], Chip[C]
Apr 3 23:38:37 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[1], Chip[C]
Apr 3 23:38:37 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][11]@ChainID:[2], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[3], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][12]@ChainID:[0], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[1], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][11]@ChainID:[2], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[3], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][12]@ChainID:[0], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[1], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][11]@ChainID:[2], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][1][10]@ChainID:[3], Chip[C]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Chain 0 chip 0 RemoteTemp 0x12
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Chain 1 chip 0 RemoteTemp 0x10
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Chain 2 chip 0 RemoteTemp 0x11
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Chain 3 chip 0 RemoteTemp 0x10
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[0], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[1], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 0 chip 0 local 0x12 remote 0x12 offset 0xfffffffa
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 0 chip 1 local 0x0 remote 0x0 offset 0x14
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 1 chip 0 local 0x12 remote 0x10 offset 0xfffffff6
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 1 chip 1 local 0x0 remote 0x0 offset 0x14
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 2 chip 0 local 0x10 remote 0x11 offset 0xfffffff9
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 2 chip 1 local 0x0 remote 0x0 offset 0x14
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: OK Chain 3 chip 0 local 0x10 remote 0x10 offset 0xfffffff9
Apr 3 23:38:38 (none) local0.notice cgminer[8003]: Remote = 0 Chain 3 chip 1 local 0x0 remote 0x0 offset 0x14
Apr 3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][FA]@ChainID:[0], Chip[C]
Apr 3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][F6]@ChainID:[1], Chip[C]
Apr 3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][F9]@ChainID:[2], Chip[C]
Apr 3 23:38:39 (none) local0.notice cgminer[8003]: Dump IIC Data:[1][98][11][F9]@ChainID:[3], Chip[C]
|
|
|
|
|
Show Posts
