Ouch... that looks nasty. I hope you get your warranty sorted out. Make sure to document everything, which you seem to be doing already. And despite what Bitmain tries to tell you I would inspect all remaining heatsinks before powering them up... something seriously wrong there. Ran out of glue or used wrong glue or something. Thanks. I have asked for permission from Bitmain to allow me to remove and inspect all hashing boards before proceeding any further. Thanks for sharing that is very very scary to see. Only thing funny is photobucket offering prints of photos.... i doubt that is a memory you care to mount on the wall. Most likely I bet Bitmain say's no and asks to ship it back looking at the damage. If they do surprise me and let you open it up please share. Honestly mate, that is all I have been wanting. The damage is 100% due to faulty equipment. I purposely bought all Bitmain PSU's. I just want to sent them back so they can check it out. It just seems way too coincidental that my shipping was delayed for 3 weeks and then this happens. Is it just me having this problem or was batch 1 a disaster? you are using the BITMAIN 1600W psu? looks like the connectorsd are all 18awg, is it possible a loose connection or poor contact with the socket caused the issue? it seems to be right at the connector |
|
|
|
Klondike gets busy, he'll get back at you Phil don't worry.
they are on the way. as of today. Yeah, Klondike is a class act (and so is Finksy by the way). He will not let you down. He is a busy guy, but very professional. thanks for the kindness  I have a 'real world' job, so some days i don't have as much opportunity to get back to PM's or hit the post office by the cutoff time. Typically though, i'll ship next-day on most orders. ps: I respond more quickly to PM then to checking posts in this thread. |
|
|
|
I have connected up a fan and have been pushing up the frequency Today.  Have now got up to 225MHz giving 12.375GH/s using a setting of "2:225:0882" This as high as you can go with the Core voltage at it's standard setting of 0.61V. Actually this is better than I expected as the data sheet calls for about 0.67V. At this point I am seeing a few too many HW errors and at 250MHz there are a lot of errors. I will fit a pot Tomorrow, adjust the voltage up a little and push on up. This is BTW with an external 5V PSU as I suspect the built in one would have run out of steam by now? Rich damn, thats impressive. I stopped at ~8.5GH because the unit began making a bit of buzzing noise (AC/DC?) and I did not know the amperage available to the chip. Impressive to see it can actually keep cranking up. with a few stick-on heatsinks to the R1 case and a nearby fan, 8.5GH ran quite cool |
|
|
|
I can tell you that gaining serial access to the PCB is going to be tough. I tried/failed to open up my R1 and its very well assembled, no screwholes and parts dont easily pry free |
|
|
|
super good news everyone!!!!
with the help of LDP and some trial and error.. i got wired <> wireless bridge working and im seeing if i can do a wireless <> wireless bridge.
ill keep you guys informed.
That is good news. Now can you figure out how to change the pool? thats easy. just ssh into the device and change the /etc/init.d/cgminer script to point to another pool. That is good news. Does it reset if power is lost I'm guessing? Also what does status screen look like when you change it to another pool? AFAIK its saved (but if you use the reset button, EVERYTHING returns to default which is good to prevent bricking), and the status screen wont look any different, but may show your pool username in the email entry box That is great news! I like that it is saved, was not expecting that. Can't wait till we see some modded firmware eventually. And reset fixing it is nice in case of messing up. seems to run quite comfortably at 7GH using 137MHz |
|
|
|
super good news everyone!!!!
with the help of LDP and some trial and error.. i got wired <> wireless bridge working and im seeing if i can do a wireless <> wireless bridge.
ill keep you guys informed.
That is good news. Now can you figure out how to change the pool? thats easy. just ssh into the device and change the /etc/init.d/cgminer script to point to another pool. That is good news. Does it reset if power is lost I'm guessing? Also what does status screen look like when you change it to another pool? AFAIK its saved (but if you use the reset button, EVERYTHING returns to default which is good to prevent bricking), and the status screen wont look any different, but may show your pool username in the email entry box |
|
|
|
I thought that the first figure was the Delay, bigger number for lower frequencies / longer delay with 6 being about 19ms & 5 about 16ms? The frequency I thought was effectively Text that is displayed but does not set anything? And the hex number set up the divider for the frequency?
Rich
pretty much, just not sure how the first value (seems to accept decimals?) calculate to a delay in ms (which could then easily match to a clock frequency) ps: i hit 8.52GH (3hrs) on my R1 but am afraid to push it further (not because of heat or chip limits, but for the sake of the AC/DC and DC/DC) |
|
|
|
any link to your nanofury failure (which IIRC is actually a fitfury chip, hence the "56bit max"), curious if the chip, PCB, or something else failed.
No, unfortunately. It happened before I found this forum and I dealt directly with crytorig via ebay. I threw the bad stick out, I should have saved it but it was before I knew better. Maybe someone will sacrifice an R1 in the name of science and see how long it will run oc'd until it burns out. Like 1 week at each incremental step up until the unit dies. well I think I set the record at 8.52GH (156Mhz) with almost 3hrs run time. I know the chip can do more but i dont know what the other components are and at a 55% overclock assume they are near thier limits. Im backing down for now, seeing if i can find a sweet spot around 7GH that does not require heatsinks or active cooling |
|
|
|
no internal temp, at least not seen by cgminer.  how did you pull that up? interested to see what hw error rate is at 8.55GH (2hrs sample) |
|
|
|
I burned out a nanofury usb stick by overclocking it from "50 bits" to "52 bits" (56 bits max), I would be wary of overclocking these little chips, especially since they do not have any active cooling. It would only be a matter of time (couple weeks in the case of my stick) before the mining chip burns itself out. And for a gain of ~2GH, is it really worth it?
technically i have two antrouters (1 still BNI[sealed]B) so would not be devestated. any link to your nanofury failure (which IIRC is actually a fitfury chip, hence the "56bit max"), curious if the chip, PCB, or something else failed. I think bitmain is better system and am curious if there is an internal temperature probe to shutdown at 65C (or 80C, whatever it is on the S-series). My attitude is that if the R1 surface isn't TOO hot (ie stickminer hard-to-touch) then thermal failure is unlikely. the chip can push way further, my concern is what the DC/DC and AC/DC component limits are. I tried to open the case with a pair of thin screwdrivers, but its surprisingly well-assembled. It seems like the case is a singular aluminum shell, and the hardware is slotted in from one end, capped with a plastic section (that refuses to pry/pop loose). There are no screwholes or other points of access to dissassemble. Its a great device physically, I just want to see the UI improved with R1 asic stats, ability to change pools, and simplified network setup/instructions (I want it to be a wifi repeater, but changing that isnt easy) I'm surprised on all the setup complaints. I have not got mine yet. But it seems like BM should have had a screen select X as mode. And pick what mode you want R1 to be in. But sounds like that is not happening. If you get it hot it appears to have holes on the case. So likely you could push air though the case, and worry a little less about OCing. no holes, just a pattern of raised bumps (which dont do much, only 1-2mm). I used some small adhesive heatsinks to try and aid it at higher modes (7GH is probably the safe limit of passive) |
|
|
|
I burned out a nanofury usb stick by overclocking it from "50 bits" to "52 bits" (56 bits max), I would be wary of overclocking these little chips, especially since they do not have any active cooling. It would only be a matter of time (couple weeks in the case of my stick) before the mining chip burns itself out. And for a gain of ~2GH, is it really worth it?
technically i have two antrouters (1 still BNI[sealed]B) so would not be devestated. any link to your nanofury failure (which IIRC is actually a fitfury chip, hence the "56bit max"), curious if the chip, PCB, or something else failed. I think bitmain is better system and am curious if there is an internal temperature probe to shutdown at 65C (or 80C, whatever it is on the S-series). My attitude is that if the R1 surface isn't TOO hot (ie stickminer hard-to-touch) then thermal failure is unlikely. the chip can push way further, my concern is what the DC/DC and AC/DC component limits are. I tried to open the case with a pair of thin screwdrivers, but its surprisingly well-assembled. It seems like the case is a singular aluminum shell, and the hardware is slotted in from one end, capped with a plastic section (that refuses to pry/pop loose). There are no screwholes or other points of access to dissassemble. Its a great device physically, I just want to see the UI improved with R1 asic stats, ability to change pools, and simplified network setup/instructions (I want it to be a wifi repeater, but changing that isnt easy) |
|
|
|
I've been working on trying to calculate the reg_data for BM1382/4 on demand, and have an algorithm that seems to mostly work... But there's 6 exceptional cases in Gekko's cgminer table that don't fit it: For 181.25 MHz, Gekko is using 0e83, but this seems to actually be 187.5 MHz, while 181.25 MHz should be 0e 03. For 412.5 MHz, Gekko is using 1006, but this seems to actually be 206.25 MHz, while 412.5 MHz should be 100 5. In four cases, Gekko is using what appears to me to be an overly-precise divider out of the norm pattern: - For 143.75 MHz, Gekko is using 1687, but 0b03 seems like a better choice.
- For 168.75 MHz, Gekko is using 1a87, but 0e03 seems like a better choice.
- For 212.5 MHz, Gekko is using 1086, but 0802 seems like a better choice.
- For 237.5 MHz, Gekko is using 1286, but 0902 seems like a better choice.
Can anyone shed some light on these differences? IIRC (from s1/s3 tuning) its quite possible to have 2+ codes for the same frequency, as long as you still follow the 'rule sets' that define the code right now im tinkering with the R1, and might try to utilize your codes to test out smaller increments. however, timing code is relayed as such: 6:125:0983 = ~6.35GH (9.5hr sample) 6:150:0B83 = ~6.81GH (2hr sample) 5.5:150:0B83 = ~6.94GH (20min sample) 5:150:0B83 = ~7.62GH (20min sample) obviously the middle is frequency value (ie 150), and the last is the relvant hex code. what is the first value though? timing? |
|
|
|
actually, seemed to be related to other parts of the frequency instruction.
8:125:0983 = ~4.5GH (8min sample)
6:125:0983 = ~6.4GH (30min sample)
connect to antpool: its your login email. mining takes up to an hour to show up (which is a bit annoying)
I look forwards to a modified firmware with actual asic stats/details like on the U3 page, since this minimalistic bullshit isnt particularly useful
6:125:0983 = ~6.35GH (9.5hr sample) 6:150:0B83 = ~6.81GH (2hr sample) 5.5:150:0B83 = ~7.02GH (30min sample) 5:143:1687 = ~7.55GH (1.5hr sample) 5:150:0B83 = ~7.62GH (20min sample) 4.5:143:1687 = ~8.00GH (30min sample) 4:143:1687 = ~7.92GH ( 2.5hr sample) 4.2:156:0c03 = ~8.54GH (1.25hr sample) 55.3% overclock with a heatsink and fan its at a comfortable temperature, but the buzzing noise that starts at >7.5GH is present constantly (sounds slightly like a noise wall wart) so while the chip could go a lot further I don't know if the AC/DC and DC/DC can anyone able to explain the function of the first value (ie: 6 vs 7 vs  ? I assume timing |
|
|
|
actually, seemed to be related to other parts of the frequency instruction.
8:125:0983 = ~4.5GH (8min sample)
6:125:0983 = ~6.4GH (30min sample)
Do these things have a small fan on the mining chip? I would be hesitant to turn up the clock at all. You example is a very small increase comparatively, however it represents and increase of over 40% in hashing speed and I have to think this little chip will be producing much more heat as a result. Kudos to diving in and figuring this stuff out, though. the whole unit except for the part the plug sticks out is made from aluminum.. i think its acting like a huge heat sink. it doesnt get very hot, just a little warm. Does it feel warm with original freq? Or is it completely cool to the touch? I'm excited to see overclock though. That shows some promise. its warm, but not hot at default. at 6.4GH its a little toastier, but nothing major. I put on a few tiny heatsinks from USB miners to help carry the heat. as mentioned, the unit is a sturdy aluminum case/heatsink. no vent holes, but the entire thing is evenly warm |
|
|
|
Yes, you definitely need to restart the process, or just reboot the router. Just type in "reboot"
actually, seemed to be related to other parts of the frequency instruction. 8:125:0983 = ~4.5GH (8min sample) 6:125:0983 = ~6.4GH (30min sample) cant quite figure out the antpool mining method. I tried my bitmain subuser ID "xxxxxxxxx" as well as my actual email address ' xxx@xxx.com" and cant tell where my hashrate is actually going. theres a lag of at least a few minutes it seems I look forwards to a modified firmware with actual asic stats/details like on the U3 page, since this minimalistic bullshit isnt particularly useful |
|
|
|
|
^would love to see the modified exerts of /etc/init.d/cgminer since no matter what i do theres no effect, hashrate just seems to direct at antpool or something other than what i try to input
same for overclocking, i tried the 0983 for 125MHz, but it appears to have no effect
|
|
|
|
Ok, I decided to play around with one tonight. Tricking the R1 into solo mining on another pool didn't take too long. I also have a U3 plugged in and running at full speed so we'll see how long it stays up...
You'll note that the self contained chip runs under a different instance of cgminer than the U3s, both kicked off by scripts in the /etc/init.d directory. /etc/init.d/cgminer and /etc/init.d/cgminer-u3 respectively.
You can edit the cgminer script, setting the pool user, 3 pools, and comment out the user prefix added to pooluser1 to unleash your R1. Make sure to make a backup and don't blame me if you brick your device!
This tinkering around with it myself now, my solution didn't seem to work though what i did: ssh -> "vi /etc/init.d/cgminer" -> modified "local _pool1url=stratum.mining.eligius.st:3334" then put my bitcoin address in the box on the r1 mining page still trying to find an easy way to make the device act either as a wireless bridge or as a wired access point to my existing wireless network (ie to run a miner in the garage without needing a 50' ethernet cord) ps: i ordered two, got stuck with $21 charge by UPS, and the box they shipped in could have held 12-16 units. actual design is quite solid (could not seem to dissassemble it easily) and it works in a typical north american outlet (might be a loose fit for some receptacles though) |
|
|
|
I keep getting happier I decided to skip the S7.
8-)
was not such a big temptation for me at 13.5c kwh and 100 amp service (2 titans at 2500w already) ie poof goes the panel in a puddle if I'd plug one of them S7's in also the RMA to china w/o a pay and swap components option (ie you pay for say controller board to be shipped soonest and you get credit when it arrives off credit card) also not thrilled by 90 day warranty so yeah ...would be an evil temptress thou .if they had like a 'store front' of them like too blocks over thou (I've done dumber stuff impulse buying) but alas home mining is all over for me (sits in bleachers watches the asic parade go buy) Wait for the price rally. If/when bitcoin price is rising faster than difficulty, hardware prices drop significantly (ie: <0.8btc/TH) and mining is profitable almost anywhere |
|
|
|
|
Show Posts
