 Show Posts
|
|
Pages: [1] 2 »
|
|
Hey HagssFIN,
What about the thermal paste at the back of the hashing board? Hash boards seem physically and thermally connected to the back plate as well and from the look of it; there is thermal paste involved. Should I disconnect it and change the paste at the back as well?
|
|
|
|
Hash board unit.
Thank you HagssFIN. Brought it home and tested it again in the 27c environment and it seemed ok. So it must be thermal paste on 3 of the boards that made them fail hot in 40c; even tho 40c is hot and I know it; still, other miners work alright when downclocked. Note to myself and others; the error codes are bit flags. So something like 193 is 128 + 64 + 1 and therefore means (in the same order): was too hot before; is too hot now; is idle now Topic marked as solved |
|
|
|
Please see 'Table 4. CGMiner API Log error codes' in my troubleshooting guide. Link: https://bitcointalk.org/index.php?topic=3224256Does cooling it down and rebooting it make the hash board units work ok again? In worst case scenario those hash board units are broken because of the extreme temperature in your environment. Yeah; I already read your post. This error seems similar to the `131072` but I just don't get the description. What is HU that I need to replace? I will test it in lower temperatures tomorrow since I need to bring it home for further testings and probably tearing apart to replace the HU; whatever it is. |
|
|
|
Hey, It's hot here so I decided to undervolt and underclock my miners to try to keep them a little more cold in the summer but I am afraid I can't do that very well. By searching the forums I figured that apparently I have the worst possible models to underclock in all the history of miners so here I am asking if anybody had some success with underclocking these miners. Please keep in mind that the only important thing here is the temperature of the miner and therefore the power burned by the miner and not necessarily the efficiency of it. For example, A921 is normally like 100w/Th and takes 2Kw from plug to generate 20Th; but I don't care if it generates 15TH at 120w/Th as long as it decreases the overall power usage and therefore the temperature while decreasing the hash rate to a reasonable extent. My A921s are currently on the latest MM and controller FW and using the following config: --avalon9-voltage-level -2 --avalon9-voltage-level-offset -2 I get around 18Th for 1.9kw I failed to underclock my 851s which are on the latest MM and controller FW properly. I can get down to 1.5Kw but the hash rate drops to like 6Gh which is insane. Didn't tried the `Balanced` or the `PowerSaving` modes introduced in the latest firmware yet. It seems that whatever `--avalon8-voltage-level` I try (even 0) produces the same result. |
|
|
|
Hey guys, It's hot here. So hot in fact that some days it reaches 40c temperature and I expect it to become hotter (its late spring yet and summer is coming!) and therefore it's hard to keep miners cold. I have an AC unit installing right now and expect it to become online in the next day or two and hope to be able to decrease the temperature by at least 7c. Meanwhile; one of my Avalon A921 units shows error 131073 (HUFAILED*) for three of the hash boards and the other one works alright. So here I am asking if anybody had some prior experiment with this error message and if this can be solved. I don't have any idea what HU means but I guess its about temperature. Please feel free to speculate.  Thanks Elapsed[1398]
MW[3006 6168 942439 3057]
LW[954670]
MH[0 0 0 0]
HW[0]
DH[10.735%]
Temp[39]
TMax[106]
Fan[6180]
FanR[100%]
Vi[1251 1251 1246 1246]
Vo[4089 4060 4082 4095]
GHSmm[5173.94]
WU[63344.80]
Freq[194.33]
PG[15]
Led[0]
MW0[0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0]
MW1[0 0 1 0 0 0 0 1 0 0 0 0 0 1 0 3 0 0 0 0 0 0 0 0 0 0]
MW2[24 19 21 24 18 25 25 6 23 24 19 13 25 22 0 14 27 12 16 12 18 19 23 21 18 21]
MW3[0 2 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 1 0 0 1]
TA[26]
ECHU[[b]131073 [/b][b]131073 [/b]0 [b]131073[/b]]
ECMM[0]
FM[1]
CRC[0 0 0 0]
*: https://canaan.io/downloads/query_a7_ec_status.html |
|
|
|
|
I think you should add this to the main post:
Never buy unshielded USB cables for connecting AUCs to the controller. Keep a multimeter around and check if the resistance of shielded USB cable you want to use is lower than 1ohm. If possible, check all connections, power should be around 0.1ohm, data (two pins in the middle) should be lower than or around 0.2ohm. Unfortunately, there is no way to find out if the cable is actually shielded or not unless you want to cut the actual cable and see the inside. A lot of USB cables out there just short the shield to the ground to make it impossible to know if it is actually shielded or not. Almost ALL cheap USB cables are not shielded properly.
Wasted a week trying to find out the reason behind random disconnects as I used two 3meter USB cable from Anker (yeah!!) to connect two of AUCs to the controller.
|
|
|
|
How did you wire your place with three phases? Something similar might happen if the PSU can't provide enough power to the miner. I heard trying to run the miner off 120v input, for example, can cause a similar problem as the PSU is able to provide enough power to turn the miner on but not enough to keep mining. Please get a multimeter and put it in AC voltage mode ( ⏦1000V) and check the power input at the plug. It should be in the range of 210v-240v anything more or less (especially less) can cause a similar problem. Then put your multimeter in DC voltage mode ( ⎓200v) and check the output of the power supply to the miner. It should be like 12v to 12.8v, anything less shows that either power supply can't get enough from the plug and wirings or that the power supply itself is faulty. If this happened after you upgraded your power wiring and happened to all of the devices, I believe you should try checking if this is in fact caused by this change or not. Maybe move one of the bad devices to your home and check it there. I personally keep a power meter around to check the connections. This is especially useful to see how much voltage you lose due to the resistance of wirings when the miner is running. I suggest you also keep one around if you have like 10 or 20 miners. It's super useful. Something like this (I never had nor did I ever tested this specific brand and model tho): https://www.amazon.com/ETbotu-Consumption-Electricity-Analyzer-regulations/dp/B07MMLJ9S3/ |
|
|
|
|
Read the logs to see why CGMiner crashed. This is not about the connection to the internet but rather the connection between the UI and the CGMiner's API.
|
|
|
|
|
Flashing an SDCard with the ROM provided by Canaan fixed the VidToo Controller and I am going to replace my RP3 with VidToo especially because I had some issues with one of the AUCs keep disconnecting randomly to see if this fixes the problem. Tried multiple 2.5a and 3a power adapters and no success.
A good thing about the VidToo controller I believe is that it doesn't use a USB Hub (need to double check it to be sure, but the processor used has 4 separate USB duel pins), but RP3B uses a USB Hub internally shared by the ethernet controller and all 4 full sized USB ports; so that might be the reason for my problem. Or maybe 1200ma (max supported USB current in RP3B) is not enough for 3 AUC and I need a powered USB Hub.
As for OrangePi, unfortunately, my OrangePi One didn't boot up with the ROM provided by the Cannan for H2-H3 even tho they are similar. You can still install the OpenWRT and then install the necessary packages manually. But the release ROM is not compatible out of the box.
|
|
|
|
|
I just found a PSU supporting both 180v-250v and 264v-380v ranges from a local vendor capable of providing 12v 200a with overcurrent, overvoltage and overheat protection. But it was priced at 600$. So there are PSUs capable of that. But with 600$ you can buy a miner (or up to 3 if you go with used miners) instead of a PSU.
|
|
|
|
You can easily troubleshoot if it is the AUC3 which is faulty, if you have a ten miners or more in your setup. six miners or more? |
|
|
|
|
You should just give your electrician your requirements. A lot of topics discussed here and are valuable, but lets just the expert does it as he sure knows better, has more experience and unlike us actually can see the wirings and check the lines, etc, etc.
Tell him you got X number of devices that each need around 8A 220V single phase, continuously through the night and day in winter and summer, and is concerned about the fluctuations of voltage in lines especially when a new device connects (a 2000w device can take up to 10000w for a short amount of time very easily. So he should be aware of that to be able to plan accordingly when all devices start to become online after a power outage or other situations). Also, describe the fact that these devices are expensive and the safety of them as well as the fire hazard is important for you.
And you got a 110v source 3 phase (or any other input you have at your warehouse)
If you want to be really sure, you can bring another electrician later to check the work of the first one in respects to your requirements.
In regard to price; get more than one quotes and compare them. Considering the fact that this setup is actually not overly complicated, it should be easy to compare what they are going to do. You can also ask them to specify how they want to handle the job and compare those in regard to the amount of money they ask for. Maybe someone can offer better protection but you don't really need, or someone makes is with the least cost but his setup is not the safest. You can then find a balance.
|
|
|
|
Weird. Wonder why they went with that controller vs a good old RasPi-3B?
Obviously the price. This board is way cheaper than an RP3. Smaller RAM, a cheap small internal memory instead of an 8GB SDCard, a slow and cheap chipset and no unnecessary interface like HDMI, GIO Pins, Wifi, etc. I bet this cost them 1/10 of what a RP cost especially as these seems custom made for Canaan. To be honest; RP3 is way too overpowered for OpenWRT; my PR3 was always under 0.01 load in the past two days. That's what, around 1% of one core? Along that line, if you do pick up another Pi, be aware that (at least in the past) the 3B+ version does NOT work.
Didn't expect this. Thanks for informing me. |
|
|
|
This is just some technical information so don't take my word in regard to miner specific use cases or even all computer PSUs. But; all computer PSUs (at least since 1998; and this is as far as I remember xD) are switching power supplies which means that they are internally changing the frequency of the input power based on the output voltage and current. So essentially they are regulators by themselves and they usually have a range of 180v-250v; some even supports voltages as low as 100v. The only problem is that less voltage means higher frequency for the internal board and some of these boards have frequency limitations. Also added current to compensate for lower voltage sometimes results in melting connectors and wires. So they usually have a circuit to limit the current if the voltage drops by a lot or even turn off. A >220v input voltage is actually good for switching PSUs as this means that they can run on a lower frequency and less current is drowned at the input. This also makes them more efficient as less energy is wasted. The regulation is achieved in switching power supplies by measuring the output voltage and trying to correct it by changing the frequency (all PC PSUs have this, only very simple low-end PSU have fixed frequency). This happens quite fast (way faster comparing to a relay). Therefore you don't need a regulator on the line; you are just wasting more money and more energy as this regulators at best (Switching Regulators) convert AC to DC and then again to AC while this is internally done by your PSU once again and each time you lose some energy in form of heat. Simple in-line regulators are also useless as they have low efficiency because they regulate voltage or current by converting excess to heat; again. In my small farm (24 devices; ~15KW three phases) I have a device (We call them Power Protector here in my country) measuring voltage and current and turns off all devices if the voltage drops to lower than 180v or reaches higher than 250v and this worked well for me in the last year. Had zero PSU failure but then again my power source is quite stable and the device never triggered except once due to a cable failure resulting in loss of one phase. It costs me like 70$ (including the Contactor used to turn power on and off). I also have a RasberryPi connected to 3 relay boards each of them connected to 8x15A relays allowing me to turn each device on and off separately and this part cost me like 14$ per each device and some 4$ for a separate cable to each device. Wrote a small application for the RP to turn devices on one by one after a blackout and this allows me to regulate the power usage on the three-phase power source and also I like to think this minimizes the risk of current drop (even tho all of miners if turned on with each other without mining take a total of 3amp on each line; so not much; however I heard that switching PSUs tend to drow a lot of current when first turned on but I need an oscilloscope to confirm this; so not sure.) when all of them get in line. ALSO: Having a relay in line to switch power source is dangerous; being it in a UPS or any other device; these switching power supplies are huge; providing like 100amp power 12v to the miner and a sudden loss of power is less damaging than a complete 240v -> 0v -> 220v transition. Also, any other device using any sort of silicon-based relay is also dangerous as these devices tend to allow some current to pass through even in off stage and this confuses the switching power supply and might damage it. I strongly suggest a setup similar to mine and nothing more. A UPS is alright for a computer as it draws little current in daily usages and a 15ms transition is barely noticeable by the power supply as it has internal capacitors and they can happily run your system for 100ms to 200ms when used normally. But these capacitors can't do much when you run a miner drawing 100A and 15ms is enough for them to turn off and on again. In conclusion, don't be scared of losing a PSU; these things have an expected lifetime and they tend to die sooner or later. Adding a regulator is a waste of money; adds more heat and the only thing it's going to change is that instead of your PSU it gonna die after some time and it isn't actually much cheaper than the PSU anyway. And even with it, you still have the possibility of your PSU dying. And don't be scared of miners and PSUs dying due to loss of power. They are far more sensitive to voltage fluctuations; therefore just put a device there to turn them all off when the line has a lot of fluctuations and you are good to go and spend the extra money on a better quality PSU for your miners so they work for longer duration of time and also keep your miner safe in case they decided its time to die anyway. Server PSU are strongly recomended.
Btw if anyone is interested in a similar setup I found the following parts in Amazon with a quick search. To control the input line you need a device capable of measuring voltage and preferably current and has an output relay like this: https://www.amazon.com/YOKDEN-Multifunction-Electric-Frequency-Generator/dp/B07DCTX7K5This is for three phases tho, for single phase, you probably can find a cheaper version. You also need 3 CT (one per each line) so you can measure the current: https://www.amazon.com/Morning-Group-Current-Transformer-Alternating/dp/B07BGSBW52/For the contactor you can take this: https://www.amazon.com/Replacement-TELEMECANIQUE-LC1-D65-Contactor-LC1D6511-M6/dp/B00J9TTHAW/For single phase, just buy a cheaper version (1/3 current rating of your farm) and use all three poles in series. If you want to control each device separately, then you need to have one relay per each device, this is a good relay, but you also need a connector outlet for this relay that I couldn't find in Amazon: https://www.amazon.com/Enclosed-Power-Relay-240VAC-SPDT/dp/B007ULO7FGYou can also find a cheaper one with lower current rating and use the connectors in series (10A with 2 Pole can happily pass 15A current when poles are used in series) Then you can control these relays with a relay module like this: https://www.amazon.com/chen499401077-Modbus-Protocol-Serial-Control/dp/B07MPBJQ3LThis module can be controlled over an RS485 connection and if you have a RP you need the following module to be able to communicate with these devices: https://www.amazon.com/SMAKN%C2%AE-Adapter-Serial-Converter-Module/dp/B010723BCEThen you need to write a custom application in RP to turn each relay after a delay; another good thing about a custom application if you are a software developer is that you probably can find a multimeter with RS485 port and get information about power quality to your RP and best of all view these values and control your devices remotely; you can also skip this part and buy multiple timers and use them instead of the relay board and RP to just turn them one by one after a predefined delay. Couldn't find a single pole timer relay on Amazon but these are available at your local electric store as these are quite frequently used with stairway lights. |
|
|
|
Got them all working. First I tried my RP3 with the latest firmware ( 20190103: https://canaan.io/downloads/software/avalon921/openwrt/20190103/rpi3-modelb/) and this managed to get those 3 miners with newer firmware working, but failed to get other 9 with an older version of firmware to work. So the statement about Avalon miners and controllers being picky about the firmware version is completely right and it happens both ways. Then I tried updating the Vidtoo H2 to the latest controller firmware and used the 20190103 ext4 SysUpgrade ( https://canaan.io/downloads/software/avalon921/openwrt/20190103/h3/) file system but this resulted in controller failing to boot up and stuck in an infinite restart. So my Vidtoo controller is dead at this point. Brought it home to see if I can fix it. Meanwhile, I used my RP3 to update the other 9 miners to the 9211901-faf6d80 ( https://canaan.io/downloads/software/avalon921/mm/2019-01-03/) firmware after disconnecting the 3 miners that are already up to date and each time with 3 of them connected to minimize the risk in case I mess something up. And it went well. RP3 now successfully runs all 12 miners all being on the latest firmware. One thing to keep in mind is that Vidtoo H2 probably uses SquashFS filesystem so if anyone got a Vidtoo H2 controller you should be extra cautious with upgrading the firmware especially as it seems to have internal memory (along with an SDCard slot) and the default firmware is probably on the internal memory because in my case the SDCard Slot is empty. I need to add that I am not totally sure if it is in fact formatted with SquashFS; what I know is that the 20190103 ext4 SysUpgrade, when applied without removing old settings, will fail. It might be also because I missed something. ... I hadn't heard of anyone using other controllers, where did you order your gear from...
I got my devices from a local distributor; I also failed to find any information about this board. In fact, even Canaan only provides roms for this device in their latest firmware and there is no mention of this device with their older firmwares. My distributor mentioned that these controllers are new so my guess is either Canaan is sending this controller instead of RP with their 2019 batches or that my distributor just jumped on the opportunity to buy a cheaper board as soon as Canaan added support. However, with the controller having a private firmware (a version not available anywhere publicly) there is more chance that this was what Canaan sent to them. Thank you all guys, specially Steamtyme and NotFuzzyWarm; your suggestions were priceless. Also everyone else for taking the time reading the log file; I know it wasn't easy to follow things and it probably took a lot of time. I am yet to receive a response from Canaan btw. |
|
|
|
It's most likely the case that your Controller's older OpenWrt firmware is not communicating properly with the newer MM firmware of your three non-functioning A921s. Canaan made some changes and added some new parameters post-20180929 that may cause communication issues between the older Controller firmware and the newer MM firmware. I do not see any other apparent issues in your logs. I therefore suggest a clean install of version 20190103 of the Controller firmware and then a reflash of all of your A921s to version 2019-01-03 of the MM firmware. The thing is that the controller I got with the miners is a Vidtoo H2 and there is no older firmware for it; only the latest version. And I can't check the firmware on the controller as I don't know where to look in to see the version inside the OpenWRT control panel (there is only one version for OpenWRT itself); therefore I have a feeling maybe controller is the latest version and in that case I might need to downgrade those 3 miners instead of upgrading the other 9. Canaan is yet to respond to my ticket and I am little scared to change anything before getting an ok from them; however, I am going to try some of your suggestions this evening guys anyway to see if I can get them all working. Have my RP3 ready with the latest firmware to see if I can get those 3 to work with the new controller before trying to upgrade the main controller and then all miners. A lot of confusions here. If the firmware is, in fact, the number I get at the top of CGMiner API Log, then it is 20180929 which is, two versions old; but this version is not even available in their download repository (nearest being 20180926). |
|
|
|
Well, based on this page: https://github.com/Canaan-Creative/avalon9-docs/wiki/AvalonMiner-921-firmware-downloadsThere is no 9211901-faf6d80 firmware version at all (latest being the one already installed on the other 9 miners) and if number here means anything, the version installed on these 3 is newer. The thing is, this is my first batch of Avalons and I have no prior experience with them. I only had S9 to this point. Do I need to use the "MM Upgrade" option in the control panel? Does it matter that this controller is not even fully compatible with these devices? Should I worry about this fact that the faulty MM version seems higher? and do I need to disconnect other miners before updating the firmware? Avalons are both good (less Lan cable, no software needed to change settings globally, easier reporting and settings when working with one WebUI) and a pain in the a**; mixed feelings already. xD
Edit: Just as I expected, the firmware installed on these 3 miners are in fact newer. Github page is outdated, but the firmware is available to download from their download directory: https://canaan.io/downloads/software/avalon921/mm/2019-01-03/If this is, in fact, the case, I need to update my controller firmware to this version which is released on the same day as the MM firmware: https://canaan.io/downloads/software/avalon921/openwrt/20190103/I might need to upgrade my other 9 miners to the newer firmware before moving on with the controller as I have only one controller at the time. |
|
|
|
|
Thanks for replying.
I also suspected a problem with cables and even maybe AUCs having a problem with not supporting more than 3 miners (I know it might be silly, but at first I got one faulty miner per each AUC, so that was a valid guess) However cables should be alright as miners further the line get the signal and work alright; I also tried changing cables, trying with one miner directly connected to and AUC again directly connected to the controller and in summery, every combination I thought might be useful to isolate the problem. No success tho.
I am using the same adapter provided by the controller in my case; don't know the specifications tho; I might try to find a 3A adapter I know I have lying around somewhere that I used for my RP3 plex setup to see if it changes anything. But I doubt it is an undervoltage problem with USB ports as all three AUC are powered and each has 3 miners connected to them working alright.
At this stage, considering the fact that all faulty miners have the same MM version, I think it might be a firmware or a hardware problem. I am now going to open a ticket with Canaan; but does anyone here used a miner with MM Version 9211901-faf6d80 before? Couldn't find anything about it by googling it.
|
|
|
|
|
Thanks for replying, I checked the PDF version of this topic and couldn't troubleshoot it myself, that's why I am asking here for help.
"ECHU" is zero for all boards, "ECMM" is zero for all miners, "PVT_T"s are all within range, "CRC"s are all zero.
The fan is working at 10% (with rpm reading; and I can see and hear it); power is above 12v (multimeter and log reading), AUC is working and the controller detects the miner, so the MM should be alright. Also, controllers work with other miners so no problem there. PMU board reports ~12.3v input and ~4.1v output which is in line with other miners working correctly. So PMU should be fine. "PVT_T"s are also within reason. "MV" values are also similar.
However, I don't know what some values mean, for example, there are some >90% values for "ERATIO" and there is no description in the documentation. In the summary following is the difference between a working miner and a faulty miner for me:
"DH" > 90%
"TMax" is low comparing to a healthy miner due to the fact that there is no mining going on
"Fan" is at 1650 (10%) but this is expected, again, as there is no mining going on
"PLLX" for all healthy miners start with "0 0 0 0" but this isn't the case with faulty miners; but guessing this is the performance state of chips, this should be expected as the frequency is lower
"GHSmm" for all faulty miners are around 10TH, but this isn't true as I can clearly see power usage is too low for real 10TH mining.
"WU" is zero for faulty miners
"Freq" is around ~380 for faulty miners comparing to ~740 for healthy ones
"MW0", "MW1", "MW2" and "MW3" values are all zero in faulty miners
"PVT_V" values in a healthy miner are all around 4v, but this isn't the case for faulty ones, there are values ranging from 1.8v to 7.3v
"ERATIOX" values are between 2% to 6% for healthy miners, but faulty ones have a lot of 0% and some >90%
"C_XX_XX" values for faulty miners have a lot of 0 and low values in general (<60, <1000)
"GHSmmXX" lot of zeros and low values for faulty miners here comparing to healthy ones
The thing is, I have no Idea how to interpret these values and the troubleshooting thread or PDF don't provide an answer.
EDIT: I also just noticed that all three faulty miners have 9211901-faf6d80 MM version.
|
|
|
|
|
