Search content
Sort by
Showing 20 of 24 results by mikxxy
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Yes it's still stable since i started it, even though i OC it a little to kompensate for the dead card.
That is good news, temps look good too, I will try the trick soon, I will need to go the farm to pick up all the dead 17 series, I have a lot of them, since the trick is cheap and easy it's worth the try.
Quote
By the way is miners.eu a trusted vendor?
Nop, they are likely scammers, there are a few accusations against them in this thread , also their Trustpilot reviews aren't great, see one thing to notice about Trustpilot is that positive reviews can be faked easily because they require no proof, while negatives require verifications such as emails, screenshots and all that, the seller can dispute against your negative feedback and have it deleted, so negative feedback outweighs a 100 positive once.
Here is one recent feedback:
Quote from: John https://www.trustpilot.com/review/miners.eu
You wont get any items from them
I paid my order 8 weeks ago, product should be "in stock, shipped in 5 days" no product, no refund so far.
Chat on their website mysteriously closes after you have made your payment. No answer to phone and to email rarely, telling to wait more.
I have made police report of them.
They reply in 10 min when it's on their favor, 2-4weeks when yours.
They offered to pay me to get my previous review off so I did but ofc they didn't paid so its here again.
They will threat you with lawsuit for sure if you share your negative experience.
I paid my order 8 weeks ago, product should be "in stock, shipped in 5 days" no product, no refund so far.
Chat on their website mysteriously closes after you have made your payment. No answer to phone and to email rarely, telling to wait more.
I have made police report of them.
They reply in 10 min when it's on their favor, 2-4weeks when yours.
They offered to pay me to get my previous review off so I did but ofc they didn't paid so its here again.
They will threat you with lawsuit for sure if you share your negative experience.
Nobody knows or trusts John, but the fact that his verified negative feedback is still there simply means that the accused party failed to prove that John is lying, which means they have indeed scammed him.
I'm thinking most conviinient is to freeze the whole miner:) and pick up used freezer cheap on the way???
miners.eu have good prices on etherum miners, much better than Prominerz, which seem to "trusted" pricing policy by up to 20% compared to miners.eu. It seems there some talking regarding "negative elements" making it hard to distinguish inbetween the vendors, scamers i.e unhappy buyers, competitors trying to miscredit each other as scammers. Whats your opion on that? Is asicminervalue.com to be a trusted as non afiliated party? They have markings "trusted" on some vendors (obviously based on some simple algortim, but still they are risking to discredit thier trademark if they are deviating with their "Trusted" marks to much.
Just my 2 cents
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
So how is the frozen hashboard doing now? I know the freezing trick works on weakening the adhesive and make the heatsink easier to remove, not exactly sure how it would help to make it stick harder!! I would love to hear more from other members, NFW and wndsnb can perhaps shed some light on the subject.
Yes it's still stable since i started it, even though i OC it a little to kompensate for the dead card.Code:
Chain# ASIC# Frequency(avg) Voltage Consumption (W) GH/S(ideal) GH/S(RT) Errors(HW) Temp(PCB) Temp(Chip) ASIC status
1 24 0 15.8 15 0.00 0.00 0 0-0-0-0 0-0-0-0 Failed to detect ASIC chips
2 30 750 15.8 684 15,120.00 14,789.48 1 54-59-52-57 76-82-76-79 ooo ooo ooo ooo ooo ooo ooo ooo ooo ooo
3 30 750 15.8 684 15,120.00 15,022.88 2 52-56-51-55 75-78-73-75 ooo ooo ooo ooo ooo ooo ooo ooo ooo ooo
Total 84 750 1383 30,240.00 29,812.36 3
1 24 0 15.8 15 0.00 0.00 0 0-0-0-0 0-0-0-0 Failed to detect ASIC chips
2 30 750 15.8 684 15,120.00 14,789.48 1 54-59-52-57 76-82-76-79 ooo ooo ooo ooo ooo ooo ooo ooo ooo ooo
3 30 750 15.8 684 15,120.00 15,022.88 2 52-56-51-55 75-78-73-75 ooo ooo ooo ooo ooo ooo ooo ooo ooo ooo
Total 84 750 1383 30,240.00 29,812.36 3
going to try to fix the dead card once i get the board fixture, but i thnk it will require a lot of expirience and gear to rework the ASIC chip. Anyone that did this operation with good outcome?
By the way is miners.eu a trusted vendor?
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
So you put the thermal solder on the chip? Do I need to put anything on the heat sink such as flux or something else?
This video shows a method of cleaning up and applying solder to attach the heat sinks: https://youtu.be/F6L9hCQ4OhY
A bit of tacky flux can help to get the solder to flow and adhere to the chip surface. Flux plus solder wick is used to clean up excess solder. This is the solder paste, flux, and solder wick I use and have had good results with:
https://www.chipquik.com/store/product_info.php?products_id=310001
https://www.chipquik.com/store/product_info.php?products_id=470006
https://www.chipquik.com/store/product_info.php?products_id=640003
I took the hash board board
- from the T17, that droped off or didn't start, that on irregular bases, (in awesom showing ...4 of 30 asic...) and put it in the freezer for a couple of hours, and it felt stable there after, now on day 2, been minning normal and also starts normal on multible power cycles.
I dont know the exact mechanism for this phenomena, as the dude couldn't explain to well, but as its known that bad quality of solder composition/flux, migth be affected by prolonged heat exposure, resulting in bad solder joints due to crystallic changes in the solderit self. The process of freezing migth some how mediate some transformation the solder. Let see how long this fix will hold... Worth trying on such boards.
To the other board [1] i attached the heat sink with thermal glue but to no awail, still showing (..24 of 30 ASICS..) freezing did not help on this one,
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Ok i'll find something. Another reliable shop is Prominerz in Switzerland. I bougth some miners there to in 2019, i donnu their ability in spares, maybe on reguest as service?
You lose nothing if you contact them, it's just doesn't line up perfectly, Switzerland and mining don't seem to blend well, I mean who on earth would start a mining business in that expensive country? were prices near the reasonable back in 2019 when you bought the gears? I think what you should look for is a supplier in Eastern Europe, mining there is a thing and probably the supplier's option is much better on that side of the continent.
I agree that Switcherland is a odd place for a Crypto miner outlet, but on the other hand crypto have no borders no time zones. Back then it was one of the few reliable outlets in Europe. They mainly profited on antminer customers, that either missed out on ordering or got to few from Bitmains batches,and saw crypto prices surge. I think prices then was like 25% higher compared to Bitmain, but i was able to buy excl. VAT. got some z11 there. From my point of veiw, ordering, paying in advance, from a Swiss company, on wich i could get info on the net and so on, contra an Asian company (ex Bitmain) was no brainer
But idont agree on that eastern europe, should be a more reliable and/or convient, chances to be scammed is in my opion higher in east EU. In general (not crypto bussinessin particular) It still carries a shady reputation from the past. Corruption is higher (maybee not everyone will agree with but lif its out of topic i'll remove it) But on the other han eastern europe is expirienced regarding crypto, land got a larger crypto community then in west, mainly becuase of the historical mistrust towards gowerments, insitutions and banks.
In some west Eu countries, like Sweden, knowledge about crypto, in mainstream population is almost non existing.
Sorry for massive of typos, but tired lika dog, becuase of a rough day, tuning all the miners to a maximum. Unfortianly i went one step to high in the auto tunning, and in the end i blow the main fuses, 4x80amps, supplying the farm, then i just threw in the towel and went home.
l
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
I dont know if tare afiliated with Bitmain, or not.
They are not, also their website looks scammy but the prices seem legit and more to the upside than the opposite.
Seems like mining in EU is dying, if not already dead (power cost-related issue for the most part), and not so many Europeans discuss suppliers, EU tax, and all the stuff that are related to EU, unlike how the U.S folks here do, maybe one of you should start a topic dedicated to EU miners so you all can share resources, news and anything else that you might find useful, there are probably at least 5-6 EU based miners around this board.
Ok i'll find something. Another reliable shop is Prominerz in Switzerland. I bougth some miners there to in 2019, i donnu their ability in spares, maybe on reguest as service?
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
But before it used to drop another board after been mining for a wihle. So there migth be another bad soldered Heat sink missbehaving when heating up
Yes, that is exactly the cause, one or more heatsink are not glued perfectly, sometimes they will contact and read and sometimes they don't, I have a few boards that behave this way, just mine with it until it longer functions, the bad heatsink will eventually fall off or at least becomes so loose that you can identify it with your bare eyes/hands.
I will try to contact their support to see if I can get in contact with someone from Poland.
go to this page > https://www.zeusbtc.com/Repair.asp, scroll down and you will see a list of some cities/countries, looks like you have to keep your contact information and they should contact you.
The site also mentions
Quote from: https://www.zeusbtc.com/Repair.asp
Attention: The miner repair points shown on the map below are independent individuals. This site only offers a free display. Please contact the maintenance point for specific matters. If there is any dispute, please resolve it by negotiation. Any consequences will not be related to this site.
So it doesn't seem like they are a branch of Zuesbtc, but I can only assume that Zeusbtc must have done at least a basic check on these guys to confirm their integrity, some of them might have got some training in China from Zeusbtc, I tend to think that they can be trusted, but I would still. deal with caution
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
⭐ Merited by frodocooper (3)
Take it easy, we all have lost many gears, the failure rate on these 17 series is much more than you can imagine, I would have been more than happy if I got 6 months of all my 17 series gears, so you are not in the worst situation one can be.
Recap:
1- I assume the T17 is done with and you are going to try and solder the heatsinks?
2- You have 2*T17+ , one is fine another one has a bad control board, when you try them on a working control board you get the errors you posted in the last post? is that the case or am I missing something?
If I am on the right track, you should know that mixing hash boards from different miners will cause many issues, so while you are trying to fix all this please keep track of the different hash boards and to which control board they belong.
Status is now 1-T17 about to solder the poped heat sink, the other 2 cards seem to work ok! But before it used to drop another board after been mining for a wihle. So there migth be another bad soldered Heat sink missbehaving when heating up a bit, standing i the farm?. Been knocking around with a pen, I ordered a fixture, so we will see.Recap:
1- I assume the T17 is done with and you are going to try and solder the heatsinks?
2- You have 2*T17+ , one is fine another one has a bad control board, when you try them on a working control board you get the errors you posted in the last post? is that the case or am I missing something?
If I am on the right track, you should know that mixing hash boards from different miners will cause many issues, so while you are trying to fix all this please keep track of the different hash boards and to which control board they belong.
2-T17+ the original 'dead one', is now working fine, after it received' a working control board
3- T17+ (the control board donor) Seem to have 2 boards working ok, and the third one not startng due to problem with pic processor. i'll will try to change around hash board cables to isolate problem. The control board came from the 'dead' T17+, so i migth have some issues. It came up with a connection error last night, so i'll check if it remains.
After identifying a bad ribbon cable the other T17+ also works fully, the connection issue was becuase of some instability caused by the faulty hashboard connection!
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Take it easy, we all have lost many gears, the failure rate on these 17 series is much more than you can imagine, I would have been more than happy if I got 6 months of all my 17 series gears, so you are not in the worst situation one can be.
Recap:
1- I assume the T17 is done with and you are going to try and solder the heatsinks?
2- You have 2*T17+ , one is fine another one has a bad control board, when you try them on a working control board you get the errors you posted in the last post? is that the case or am I missing something?
If I am on the right track, you should know that mixing hash boards from different miners will cause many issues, so while you are trying to fix all this please keep track of the different hash boards and to which control board they belong.
Status is now 1-T17 about to solder the poped heat sink, the other 2 cards seem to work ok! But before it used to drop another board after been mining for a wihle. So there migth be another bad soldered Heat sink missbehaving when heating up a bit, standing i the farm?. Been knocking around with a pen, I ordered a fixture, so we will see.Recap:
1- I assume the T17 is done with and you are going to try and solder the heatsinks?
2- You have 2*T17+ , one is fine another one has a bad control board, when you try them on a working control board you get the errors you posted in the last post? is that the case or am I missing something?
If I am on the right track, you should know that mixing hash boards from different miners will cause many issues, so while you are trying to fix all this please keep track of the different hash boards and to which control board they belong.
2-T17+ the original 'dead one', is now working fine, after it received' a working control board
3- T17+ (the control board donor) Seem to have 2 boards working ok, and the third one not startng due to problem with pic processor. i'll will try to change around hash board cables to isolate problem. The control board came from the 'dead' T17+, so i migth have some issues. It came up with a connection error last night, so i'll check if it remains.
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
So what could by wrong with this controller?
When a control board is bad, you would expect all kind of weird problems, and honestly, things now are becoming confusing and hard to follow
, can you just not test the bad control board so we all can focus on the good one?Quote
i'm located within the EU
That is unfortunate, I don't know of any trusted suppliers there, but should you need one I think you should contact one of these guys (in no particular order)
-favebook
-thierry4wd
-o_solo_miner
There might be others, but those are off the top of my hand for a list of EU based miners that can be trusted.
Quote
Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity?
More explanation is needed, I don't seem to understand why exactly are you planning on doing.
Code:
[2020/11/27 23:38:58] INFO: eFUSE protection is active
This line is very strange, I did text Marc (Asic.to) on telegram, let's see what he knows, it seems like a power-related issue, are you sure the PSU you using is APW9+ and the input voltage is 200-240v?
Also, it shows this
Code:
Pool connection FAILED. Check INTERNET, POOL URL or WORKER
Are you sure your pool settings are in place? is Asicboost is activated make sure the pool is AB compatible if this log comes from the bad control board and all this info can be misleading.
i have no outher means to test of the bad card by any other means than trail and error. with the apprieciated help from you guys. All the equipment mentioned, has been running att smal miningpark for at least 6 mounths , and all the settings are also the origional against Poolin. So all the odd behavior described herein emmenate from known and reliable mining conditions. The Antminer T17+ is out of stock and those few contrilers that find their way to Ebay, are very expensive. //Mixy----------------------------------------------------------
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
http://[img][img][img][img][/img][/img][/img][/img]
That is strange, I don't think the firmware knows the number of chips i.e it isn't hard coded into it, it probably gets the information from the hash board itself, the reasoning behind my point is that using the same control board and the same firmware you can run different hashboards, for an example if you take S17 hash boards and put them in your S17 pro they will work just fine despite having different asic count.
But with that being said you should reach out to Patrike and explain the issue to him.
Yes im with you,. when i try run the bad controler in the second maschine it behaves exactly as in the previous setting, by not beeing able to detect correct asic valuse but in addition, now also giving error of not detecting any fans, even though the are spinning accordingly to pre setting of 30% (awesom FW), could it be affected by any virus in any of processors? A leds onboard are behaving as expected, boot sequenceas as it should, then it tries to initialize the hash bords iindefinitely. So what could by wrong with this controller?
Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity?
By joggling the controller back and forth, i started to catch on Awesom, detecting asic chains but the first one, also it warns if try to raise freq some steps above 500Mhz
whats confusing as said is the T17+ and none with different amount of chips on each board, 44 and 64?, should they need a designatet FW depending on asic count on each hash bord? Awesom issued two different FW's 1.00 and 2.0.3? Ill try the first one on the faulty card, may be it will run?
That is strange, I don't think the firmware knows the number of chips i.e it isn't hard coded into it, it probably gets the information from the hash board itself, the reasoning behind my point is that using the same control board and the same firmware you can run different hashboards, for an example if you take S17 hash boards and put them in your S17 pro they will work just fine despite having different asic count.
But with that being said you should reach out to Patrike and explain the issue to him.
Yes im with you,. when i try run the bad controler in the second maschine it behaves exactly as in the previous setting, by not beeing able to detect correct asic valuse but in addition, now also giving error of not detecting any fans, even though the are spinning accordingly to pre setting of 30% (awesom FW), could it be affected by any virus in any of processors? A leds onboard are behaving as expected, boot sequenceas as it should, then it tries to initialize the hash bords iindefinitely. So what could by wrong with this controller?
Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity?
By joggling the controller back and forth, i started to catch on Awesom, detecting asic chains but the first one, also it warns if try to raise freq some steps above 500Mhz
Code:
N: chain[0] - Failed to reset pic (attempt = 2), resp: 0x90 0x90
[2020/11/27 23:45:34] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x90 0x90
[2020/11/27 23:45:35] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:38] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:39] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:41] INFO: chain[2] - 44 chips detected
[2020/11/27 23:45:41] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:41] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:43] INFO: chain[1] - 44 chips detected
[2020/11/27 23:45:44] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:46] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:47] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:48] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:34] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x90 0x90
[2020/11/27 23:45:35] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:38] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:39] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:41] INFO: chain[2] - 44 chips detected
[2020/11/27 23:45:41] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:41] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:43] INFO: chain[1] - 44 chips detected
[2020/11/27 23:45:44] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:46] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:47] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:48] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
Code:
2020/11/27 23:39:24] INFO: Initializing
[2020/11/27 23:39:22] INFO: eFUSE protection is active
[2020/11/27 23:39:00] INFO: Initializing
[2020/11/27 23:38:58] INFO: eFUSE protection is active
[2020/11/27 23:38:34] INFO: Initializing
[2020/11/27 23:38:34] INFO: Pool connection FAILED. Check INTERNET, POOL URL or WORKER
[2020/11/27 23:38:32] INFO: eFUSE protection is active
[2020/11/27 23:38:00] INFO: Mining
[2020/11/27 23:36:38] INFO: Initializing
[2020/11/27 23:36:36] INFO: eFUSE protection is active
[2020/11/27 23:36:30] INFO: Initializing
[2020/11/27 23:36:28] INFO: eFUSE protection is active
[2020/11/27 23:35:59] INFO: Initializing
[2020/11/27 23:35:59] INFO: Pool connection FAILED. Check INTERNET,
[2020/11/27 23:39:22] INFO: eFUSE protection is active
[2020/11/27 23:39:00] INFO: Initializing
[2020/11/27 23:38:58] INFO: eFUSE protection is active
[2020/11/27 23:38:34] INFO: Initializing
[2020/11/27 23:38:34] INFO: Pool connection FAILED. Check INTERNET, POOL URL or WORKER
[2020/11/27 23:38:32] INFO: eFUSE protection is active
[2020/11/27 23:38:00] INFO: Mining
[2020/11/27 23:36:38] INFO: Initializing
[2020/11/27 23:36:36] INFO: eFUSE protection is active
[2020/11/27 23:36:30] INFO: Initializing
[2020/11/27 23:36:28] INFO: eFUSE protection is active
[2020/11/27 23:35:59] INFO: Initializing
[2020/11/27 23:35:59] INFO: Pool connection FAILED. Check INTERNET,
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
whats confusing as said is the T17+ and none with different amount of chips on each board, 44 and 64?, should they need a designatet FW depending on asic count on each hash bord? Awesom issued two different FW's 1.00 and 2.0.3? Ill try the first one on the faulty card, may be it will run?
That is strange, I don't think the firmware knows the number of chips i.e it isn't hard coded into it, it probably gets the information from the hash board itself, the reasoning behind my point is that using the same control board and the same firmware you can run different hashboards, for an example if you take S17 hash boards and put them in your S17 pro they will work just fine despite having different asic count.
But with that being said you should reach out to Patrike and explain the issue to him.
Yes im with you,. when i try run the bad controler in the second maschine it behaves exactly as in the previous setting, by not beeing able to detect correct asic valuse but in addition, now also giving error of not detecting any fans, even though the are spinning accordingly to pre setting of 30% (awesom FW), could it be affected by any virus in any of processors? A leds onboard are behaving as expected, boot sequenceas as it should, then it tries to initialize the hash bords iindefinitely. So what could by wrong with this controller?
Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity?
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
i'm located within the EU, whats confusing as said is the T17+ and none with different amount of chips on each board, 44 and 64?, should they need a designatet FW depending on asic count on each hash bord? Awesom issued two different FW's 1.00 and 2.0.3? Ill try the first one on the faulty card, may be it will run?
Yes rigth, the T17 with a poped heatsink present it self at initial phase of power cycling, 000000 and then it wanish from the Gui, so i migth be alive, lets see what will happen as i glue i back then.
Yes rigth, the T17 with a poped heatsink present it self at initial phase of power cycling, 000000 and then it wanish from the Gui, so i migth be alive, lets see what will happen as i glue i back then.
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
JES, problem identified! The culprit is the control board, looks normal, there seems to be some problem in or out coming signals to the net,it does not identify itself on a IP scanner. changed inbetween the healthy one an d the bad one, so no problem with the hashboards. Awesom was inndicating 44 of 66, wich is wrong as there is only 44 chips on each board. Bitmain has produced several models of the T17+ this particular one has 58Th, so the Awesom FW got confused. Regardind the control board it may just be something with RJ45 connector, but i think its easier to just get a replacement board?
I open up another one, a T17 it had actually a heatsink off! there is some videos in Russian language, about fixing this, but i semm not to understand if the chip is replaced or resolderd? i should be burnt shortly after heatsink falling off, while in mining mode? Isnt there a way to just "short" the bad chip out and thus restoring integrety of the chain?
I open up another one, a T17 it had actually a heatsink off! there is some videos in Russian language, about fixing this, but i semm not to understand if the chip is replaced or resolderd? i should be burnt shortly after heatsink falling off, while in mining mode? Isnt there a way to just "short" the bad chip out and thus restoring integrety of the chain?
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Should be a separate power circuit for the boards.
There are indeed two different circuits and this is so confusing to most people, they see the LEDs turn on and they think it's a confirmation that the PSU is in perfect shape which sadly isn't really the case.
Quote
I have another, a T17 that lost one (occasionly one more), but controler detects the faulty board, some data as voltage is shown
If I understood you correctly, you have another working T17 PSU (APW9) that is powering a single hash board, and sometimes two, and we know you "most likely" have a dead PSU and 3 working hash boards, wouldn't it be wise to take the working PSU and instal it on the "potentially" working 3 hash boards?
Quote
ill disassemble the psu to check if theres any visual damage, dont know anything about testpoints or so, would appreciate any suggestions for where to search.
We milked this topic quite a bit, but long story short these PSUs were not really meant to be fixed, it's not that it's impossible to fix them, but once you open it you will get the point, to me, anything except for a simple fan change on those PSU isn't working looking into, and I doubt you will find many resources regarding the subject, so if you are not an expert in this field, chances are you should be looking for a PSU replacement.
Now i changed the PSU took it from a working T17+. Same problem persists . Inotice this message in Awesom miner
Code:
[2020/11/27 07:56:00] INFO: Auto-tuning
[2020/11/27 07:55:58] INFO: eFUSE protection is active
[2020/11/27 07:54:49] INFO: Auto-tuning
[2020/11/27 07:54:47] INFO: eFUSE protection is active
[2020/11/27 07:53:24] INFO: Auto-tuning
[2020/11/27 07:53:17] INFO: eFUSE protection is active
[2020/11/27 07:55:58] INFO: eFUSE protection is active
[2020/11/27 07:54:49] INFO: Auto-tuning
[2020/11/27 07:54:47] INFO: eFUSE protection is active
[2020/11/27 07:53:24] INFO: Auto-tuning
[2020/11/27 07:53:17] INFO: eFUSE protection is active
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Thanks 
It was indeed a button to press for takning the top cover off, never seen this one. I dissassembled the miner and all the hashboards look fine no lose heatsinks. im leaning towards psu, as it happend simutaniusly.I conclude that theres power to the boards and fans, but its not powering up hashboards. Should be a separate power circuit for the boards. I have another, a T17 that lost one (occasionly one more), but controler detects the faulty board, some data as voltage is shown, and also a asic count before powering it off
ill disassemble the psu to check if theres any visual damage, dont know anything about testpoints or so, would appreciate any suggestions for where to search.
It was indeed a button to press for takning the top cover off, never seen this one. I dissassembled the miner and all the hashboards look fine no lose heatsinks. im leaning towards psu, as it happend simutaniusly.I conclude that theres power to the boards and fans, but its not powering up hashboards. Should be a separate power circuit for the boards. I have another, a T17 that lost one (occasionly one more), but controler detects the faulty board, some data as voltage is shown, and also a asic count before powering it offill disassemble the psu to check if theres any visual damage, dont know anything about testpoints or so, would appreciate any suggestions for where to search.
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Jup, all 3 spinn when powerd by both cords. Regarding PSU its way around, APW9 instead of the plus version, for testing. the miner stopped rigth after i powered back one of the cords due to the powercut, red led came upp instead of the green in end of power cycle, so that seems indicate a total sudden loss of function, rather then a progressive problem?. Seems to be a new design of the top cover, no 4 screws holding top down, this one have screws on the sides and something looking as a "button" on backside, how do i unmount the topcover on this miner?
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Sorry about the annoyance with code format 
but im still a newbie , seems as a plausible explanation, as the the power cut only involed one of the two powercords. icould try with a psu from a T17 40 Th would that be sufficient for the test of the faulty T17+ 58th? Upgraded to latest Bitmain orginal FW, and now flashed the awesom SD 2.03.
but im still a newbie , seems as a plausible explanation, as the the power cut only involed one of the two powercords. icould try with a psu from a T17 40 Th would that be sufficient for the test of the faulty T17+ 58th? Upgraded to latest Bitmain orginal FW, and now flashed the awesom SD 2.03.Please use the code function to post kernel logs, it's really annoying and hurts the eyes. 
, use something like this
What the kernel log suggests is that all 3 hashboards have only 44 asics, which means the signal at chip 45 gets interrupted, it is unlikely that all 3 hash boards will have the exact same problem, so my guess is your PSU got a problem, can you test the miner with another working PSU?
, use something like thisCode:
[2020/11/25 14:09:43] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
What the kernel log suggests is that all 3 hashboards have only 44 asics, which means the signal at chip 45 gets interrupted, it is unlikely that all 3 hash boards will have the exact same problem, so my guess is your PSU got a problem, can you test the miner with another working PSU?
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
An AntminerT17+ been running perfect for some months suddenly and after some power cuts, did not restart.
Flashed it with Awesom FW and getting this in kernel log, is all boards dead or just the hashboard? Thanks Mike
[2020/11/25 14:09:25] INFO: Power ON
[2020/11/25 14:09:27] INFO: Starting FPGA queue
[2020/11/25 14:09:27] INFO: Initializing hash boards
[2020/11/25 14:09:27] INFO: chain[2] - Initializing
[2020/11/25 14:09:27] INFO: chain[1] - Initializing
[2020/11/25 14:09:27] INFO: chain[0] - Initializing
[2020/11/25 14:09:43] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:09:54] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:57] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:10:00] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:10:06] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:10:06] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips
[2020/11/25 14:10:06] INFO: chain[2] - Shutting down the chain
[2020/11/25 14:10:06] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed
[2020/11/25 14:10:09] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:10:09] ERROR: driver-btm-chain.c:488 chain[1] - Failed to detect ASIC chips
[2020/11/25 14:10:09] INFO: chain[1] - Shutting down the chain
[2020/11/25 14:10:09] ERROR: driver-btm-base.c:356 chain[1] - Initialization failed
[2020/11/25 14:10:12] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:10:12] ERROR: driver-btm-chain.c:488 chain[0] - Failed to detect ASIC chips
[2020/11/25 14:10:12] INFO: chain[0] - Shutting down the chain
[2020/11/25 14:10:12] ERROR: driver-btm-base.c:356 chain[0] - Initialization failed
[2020/11/25 14:10:12] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards
[2020/11/25 14:10:12] INFO: Shutting down the miner
[2020/11/25 14:10:12] INFO: Stopping FPGA queue
[2020/11/25 14:10:12] INFO: chain[0] - Shutting down the chain
[2020/11/25 14:10:12] INFO: chain[1] - Shutting down the chain
[2020/11/25 14:10:12] INFO: chain[2] - Shutting down the chain
[2020/11/25 14:10:12] INFO: Power OFF
Flashed it with Awesom FW and getting this in kernel log, is all boards dead or just the hashboard? Thanks Mike
[2020/11/25 14:09:25] INFO: Power ON
[2020/11/25 14:09:27] INFO: Starting FPGA queue
[2020/11/25 14:09:27] INFO: Initializing hash boards
[2020/11/25 14:09:27] INFO: chain[2] - Initializing
[2020/11/25 14:09:27] INFO: chain[1] - Initializing
[2020/11/25 14:09:27] INFO: chain[0] - Initializing
[2020/11/25 14:09:43] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:09:54] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:57] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:10:00] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:10:06] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:10:06] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips
[2020/11/25 14:10:06] INFO: chain[2] - Shutting down the chain
[2020/11/25 14:10:06] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed
[2020/11/25 14:10:09] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:10:09] ERROR: driver-btm-chain.c:488 chain[1] - Failed to detect ASIC chips
[2020/11/25 14:10:09] INFO: chain[1] - Shutting down the chain
[2020/11/25 14:10:09] ERROR: driver-btm-base.c:356 chain[1] - Initialization failed
[2020/11/25 14:10:12] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:10:12] ERROR: driver-btm-chain.c:488 chain[0] - Failed to detect ASIC chips
[2020/11/25 14:10:12] INFO: chain[0] - Shutting down the chain
[2020/11/25 14:10:12] ERROR: driver-btm-base.c:356 chain[0] - Initialization failed
[2020/11/25 14:10:12] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards
[2020/11/25 14:10:12] INFO: Shutting down the miner
[2020/11/25 14:10:12] INFO: Stopping FPGA queue
[2020/11/25 14:10:12] INFO: chain[0] - Shutting down the chain
[2020/11/25 14:10:12] INFO: chain[1] - Shutting down the chain
[2020/11/25 14:10:12] INFO: chain[2] - Shutting down the chain
[2020/11/25 14:10:12] INFO: Power OFF
What happened::
Waring for Crypto Brigde exchange. Was to make an regular exchange on CMM on this site after noticing on whatstomine.com that they where paying most. BUT as DEFUALT they put their own BTS coin in in the trading pair, i didnot notice that and ended with 50BTS cions for CMM wort of $130. Guess how much the 50 BTS was worth!! less then 0,5cents.!!!!! They set a trap. SCAM WARING!!!! Whatstomine should not mention them. PRICE CMM BTS DATE
0.00510 9,950.457835 50.74833 4/09 00:40:3
#crypto-bridge.org #crypto bridge #exchange
Scammers Profile Link: wwwcrypto-bridge.org
Reference Link:
https://bitcointalk.org/index.php?topic=3001040.new#new
Amount Scammed: TOTAL: 0.02BTC
Payment Method: CMM 9500
Proof of Payment: https://drive.google.com/file/d/1c4przAQxOl3CAKzgRcsrrgtoEEzc21d8/view?usp=sharing
Additional Notes: Their respons on Discord:
its just like when you trade on a exchange that has a extra decimal and you don t notice that and get a lot less always triple check and when i doubt just sell a little and check if its correct
you could try to put in a buy order at the same pair and hope you get filled by someone who also didn t notice it(SIC!)
STAY SAFE FROM THESE BASTARDS GUYS, DON'T FALL VICTIM. HELP SPREAD THE WORD
Waring for Crypto Brigde exchange. Was to make an regular exchange on CMM on this site after noticing on whatstomine.com that they where paying most. BUT as DEFUALT they put their own BTS coin in in the trading pair, i didnot notice that and ended with 50BTS cions for CMM wort of $130. Guess how much the 50 BTS was worth!! less then 0,5cents.!!!!! They set a trap. SCAM WARING!!!! Whatstomine should not mention them. PRICE CMM BTS DATE
0.00510 9,950.457835 50.74833 4/09 00:40:3
#crypto-bridge.org #crypto bridge #exchange
Scammers Profile Link: wwwcrypto-bridge.org
Reference Link:
https://bitcointalk.org/index.php?topic=3001040.new#new
Amount Scammed: TOTAL: 0.02BTC
Payment Method: CMM 9500
Proof of Payment: https://drive.google.com/file/d/1c4przAQxOl3CAKzgRcsrrgtoEEzc21d8/view?usp=sharing
Additional Notes: Their respons on Discord:
its just like when you trade on a exchange that has a extra decimal and you don t notice that and get a lot less always triple check and when i doubt just sell a little and check if its correct
you could try to put in a buy order at the same pair and hope you get filled by someone who also didn t notice it(SIC!)
STAY SAFE FROM THESE BASTARDS GUYS, DON'T FALL VICTIM. HELP SPREAD THE WORD
my 12 batch 1s can all run at 750Mhz and in my setup range from a stable 63C to 74C across them; a lot of variance.
2 of mine run fastest at 725Mhz.
All of them run "best" at 700Mhz or less -- best is a combination of heat vs. hashrate.
At max (750), mine do a stable 192kSol/sec with variance up to ~195.
At 700Mhz, mine do a stable 186kSol/sec with temps in a managable 72C or less.
My setup: https://imgur.com/a/6SBUt2S
(copying my setup as is would be a bad idea for reasons I don't have time to get into at the moment, but you cannot egress 1000cfm out of your house without other problems...).
The most ideal configuration is for 650Mhz across all of mine -- they are stable and cool with minimal (relative) airflow across them (and thus minimal impact to the house environment).
My point here is... even though I can make the batch1s not crash at 750Mhz, that isn't their ideal point. Any unit alone, I can get to 725/750, but when I combine them all together and their heat impacts each other, 650-700 is ideal with minimal 'loss' in hashrate.
... Which puts them in line with the ~681mhz folk are seeing now.
Once my Z9s come in, I'll see how those chips work in comparison....
-j
2 of mine run fastest at 725Mhz.
All of them run "best" at 700Mhz or less -- best is a combination of heat vs. hashrate.
At max (750), mine do a stable 192kSol/sec with variance up to ~195.
At 700Mhz, mine do a stable 186kSol/sec with temps in a managable 72C or less.
My setup: https://imgur.com/a/6SBUt2S
(copying my setup as is would be a bad idea for reasons I don't have time to get into at the moment, but you cannot egress 1000cfm out of your house without other problems...).
The most ideal configuration is for 650Mhz across all of mine -- they are stable and cool with minimal (relative) airflow across them (and thus minimal impact to the house environment).
My point here is... even though I can make the batch1s not crash at 750Mhz, that isn't their ideal point. Any unit alone, I can get to 725/750, but when I combine them all together and their heat impacts each other, 650-700 is ideal with minimal 'loss' in hashrate.
... Which puts them in line with the ~681mhz folk are seeing now.
Once my Z9s come in, I'll see how those chips work in comparison....
-j
Very nice set up