Speaking of connectors: I was trying to find the list of bands & performers endorsing Neutrik and I couldn't find it. Maybe they discontinued the endorsement program because nowadays if any well-known national or worldwide act is performing on stage they have their equipment plugged in through the Neutrik connectors. Take a look at the Neutrik's version of Ethernet, USB and power plugs: http://www.neutrik.us/en-us/ethercon/http://www.neutrik.us/en-us/multimedia/http://www.neutrik.us/en-us/powercon/and compare them to the stuff available at Amazon or your local electronics retailer. I'm not going to try to post the prices, because some readers could get a heart attack and some others could choke laughing. But think of Neutrik next time you'll be warming your glue gun to fix loose connectors. For USB hubs (yes using the dreaded type-a for fanout) we finally changed over to Triplite's line of industrial hubs. God alone knows how many off-the-shelf ones - Brand name ones mind you - we and our customers have gone through at the operator stations... Search for them through Amazon. Not cheap but so far bullet-proof. Even accept up to 24v power in. |
|
|
|
<snip>
I will have to look into the 2980s. If they are that much better, it may be well worth the investment.
I don't think the 24 hour test is necessary. I would say 1/2 hour to 1 hour (whenever steady state temperature has been achieved).
I need to acquire said hardware for that test. Not likely, given my current build. I am finding that more copper isn't necessarily better. Again, the bottleneck (on the breakout) is at the board to connector interface. I would have to inspect/measure the sidehack board to make a clear case to switch, but in my case I didn't see a 6-pin PCI-e connector breakout like this from sidehack. I will dig and see what I can find.
-Optim
Or, to gain a few 10's of watts in eff, ya can always lose the PSU fans entirely like this https://i.imgur.com/cf5IRyB.jpg running 3 of my s5's off of a DPS 2000. PSU is on the suction side of course. Kills a couple birds with 1 stone  I'll look tomorrow to see if the pcb holes for the connector pins match their profile to reduce the path thru solder or are just round. |
|
|
|
Looks like this is his BF address no? 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr I hope so as I send funds there.  Personally I was hoping for a 'yes' from someone before I send... or have ya before and it's right ? |
|
|
|
'Prolly should say that my extreme conservative approach to pcb layout comes from first making boards using tape on Mylar then cut Rubylith back in the 60's through pretty much the late 80's, virtually all analog from damn near DC through RF. You learn fast to be up on best-practices eg. Be Damn Careful and never assume - verify it. When them durn newfangled PC's showed up and eventually combined with photoset machines for making the layout masks it made correcting problems/errors a lot less painful... Nowadays, just get a 4-board proto run from PcbExpress or whoever and not bad at all to make changes. But Lessons learned stick. My favorite and now deceased columnist who perfectly mirrors my views on the electronics design process http://electronicdesign.com/author/bob-pease Pay special attention on using sims like Spice. eg, how-to and how not-to. His works should be mandatory coverage in any EE program. |
|
|
|
Looks like this is his BF address no? 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr |
|
|
|
1 Firewire cable from the PC feeds first drive, that drive and all other drives is also a repeater (hub) with extra 2 ports. Each port from that drive feeds 2 more drives which also have 2 extra ports, those feed 2x more drives, rinse and repeat. Think of a tree, first FW cable from the PC is the trunk which branches out at each drive and the branches have branches. Any other name for that branching config?
I will not negate your on-the-bench experience with your turnkey solution. Please post how many devices you control and what connectors and cable lengths you are using. I have broader experience with systems deployed in many office environments. Macintoshes were actually comparatively all right. Some on the motherboard IEEE 1394 controllers (Dell) were so bad that they couldn't reliably handle single 3-meter cable to a single device across the desk and would only work with a 3-feet cable. We had to specify that customers buy a PCI expansion card with particular controller brand (TI? can't recall anymore) to accommodate fairly large office desks from regular office furniture vendors. The Macintosh deployment I mentioned in my earlier post did partial downgrade to parallel SCSI enclosures and partial upgrade to FibreChannel enclosures. They used Firewire setups only in training where the downtime/slowness wasn't a real obstacle and some trainees actually enjoyed it. last OT on this.. Our most complex systems have 14 devices talking through the 1 FW cable between the PC and 1st drive. Our vendor says up to 32 can be connected this way (branching out). For main axes the data update rates to/from each drive is 8kHz, and the high-speed galvo drives run with 48kHz update rate. Given that setup the total rate between the host to 1st drive should be update rate(s) x number of drives = a heap o'data.... The smart drives have 32-bit cpu's in them so not sure of packet size but for performance reasons I'd think they are as big as possible (maybe a FW data spec limitation there?) ... Connectors are "the big ones' vs the mini connectors, cable length from PC to 1st drive is 2meters long, branches from there are very short. This is the only pic I have here at home http://imgur.com/8nKGIUA And yes, I am not thrilled with the connectors but being buried inside a cabinet at least they are not subject to abuse or constant mating cycles. As for the chipset used.. ya that can be a bugger, not sure chip# but we use cards from SIIG with a TI chip on it. The controls system vendor (Aerotech) Has a very short list of compatible chipsets due to the fanout limitations you mentioned along with other gotcha's. The one time I tried using a mobo FW port (on ASUS Extreme mobo) it worked fine here. Got to Taiwan to install the system and no-go. Timing errors all over the place and had to plug in a spare SIIG FW card they luckily had.  |
|
|
|
Hello, Newbie here. I'm sorry if this question has been asked and answered, but in scouring the board and searching different keywords, I haven't found the answer. I have 1 S7 running off a EVGA Gold 16000 and am having no problems and setting up the cabling was a breeze. Now I have come across another S7 B10. So I ordered one of the BITMAIN AntMiner APW3-12-1600 PSU's. I have all the primary cables hooked into the S7 boards and to the controller. BUT, what are the red and black single wires with a small connector coming from the PSU that are left over? What are they for and what do I do with them? Also, there is a single yellow and green pair of single wires coming from the PSU that seemed to be jumper'd together or capped. What are these for and what do I do with them if anything. I have not powered on that S7 or PSU yet as my electrician friend is coming tomorrow to put in new lines for 240V. Thanks for any information!  Never investigated the red/black pair but the green/yellow are for switching the DC output on/off. Handy point to put a switch or a remote hard-boot control of some sort. |
|
|
|
Here are Firewire stats from one of our systems that has been running 24x7 for the past 3 weeks. It has 14 axes of motion with the motor drives fed via Firewire in a daisy-chained star config. 1 main feed to 1st driver, branching out to 2 more drives, branching out to two more, etc. https://imgur.com/kvWcSM1Perfect with zero errors. Then again, they are fed by the motion systems RTOS which WIndoze rides on top of... "daisy-chained star config?" What is that? Iron butter? Daisy-chained and star(hub & spoke more generally) are polar opposites. Not sure what you are trying to say here. 1 Firewire cable from the PC feeds first drive, that drive and all other drives is also a repeater (hub) with extra 2 ports. Each port from that drive feeds 2 more drives which also have 2 extra ports, those feed 2x more drives, rinse and repeat. Think of a tree, first FW cable from the PC is the trunk which branches out at each drive and the branches have branches. Any other name for that branching config? |
|
|
|
Funny, because I have exactly the opposite experience. I've never had USB-B problems, but mini are decent (though sometimes the connector comes off the board) and micro tend to disconnect, or more likely break, all over. I will never deliberately put a micro USB connector on something I want to work for very long. My first preference is USB-B, followed by mini.
I'm not really sure if your experience is indicative. The broad industry reliability statistics are: Standard Type-A < Standard Type-B < Mini-B < Micro-B The Mini-A and Micro-A weren't deployed widely enough. Also if it connector durability really becomes an issue one can always use industrial grade high-retention force USB sockets. Exceeding reliable but also cost around 5x what you can get normal USB sockets for... |
|
|
|
what about the ability to run them with a nic on each miner
or run 1 nic to a switch then the others would connect via usb to miner 1 and make a usb hub style where they could daisy chain down the line with less clutter of going mass into a switch with alot of cat 5 cables ? just a idea i had kinda like the old firewire days where you could keep chaining devices down the line till u needed another hub to boost the power
I would like to see the actual error statistics from those daisy-chained Firewires. I saw some stats from high-end MacIntoshes driving stacks of 5-6 external disks each through Firewire 400. This wasn't anything good and they did run in very clean offices not garages, like the mining farms. Here are Firewire stats from one of our systems that has been running 24x7 for the past 3 weeks. It has 14 axes of motion with the motor drives fed via Firewire in a daisy-chained star config. 1 main feed to 1st driver, branching out to 2 more drives, branching out to two more, etc. https://imgur.com/kvWcSM1Perfect with zero errors. Then again, they are fed by the motion systems RTOS which WIndoze rides on top of... |
|
|
|
Yes if you see any "snake" type traces its because they are parallel IO traces to some other longer traces, so they need to make the traces the same lengths hence the snakes. If you check out your PC motherboard you'll see them all over the place on the PCIe and RAM lanes. When your talking about throughputs in the muti Gigabits/s even the speed of light works against you This does not matter on anything bitcoin related though, since these are very dumb chips IO rates coming to/from them are in the order of sub 1Mb/s, since nothing larger than a couple hundred bytes is ever sent to the chips( and return IO is even less...just an 8 byte nonce return and maybe a few bytes of chip info data). You completely forgot about SSN (Simultaneous Switching Noise). <snip> Exactly. As in point 3 of http://powerelectronics.com/power-electronics-systems/five-things-every-engineer-should-know-about-pdn "Low rates have higher probability of issues While it might appear that the higher the signal frequency, the more prominent the PDN issue might be, this is not always the case. The increased signal frequency certainly does carry with it an increase in signal integrity concerns, but not necessarily for the PDN. " If the lines are long I'd want to see guard traces between each of the address and data lines running together. Short lines, say just a couple inches should be good but if np to have them there - do it. As for the PDN itself it is a matter of the buck regulators switching freq vs the low speed coms. A buck will typically run between 50-250kHz, switching spikes from low speed coms can easily fall into that range if not looked after. Good part is that the lit on the BitFury website for the 16nm chip says that all the needed supply bypassing is already present inside of the chip package so hopefully that will never be an issue when using the BitFury chips |
|
|
|
I avoided the voltage adjustment based on the issues I've read about with the A6's. I find adjusting the supply while measuring the unit voltage yields the best performance. Though my experience is limited.
<snip>
-Optim
Do correct me if I'm wrong but if you are talking about remote sensing at the load these supplies can do that using the same pins called our for voltage adjustment, pins A1 and A2 so v drop across the PCIe leads can be compensated for by tacking a light gauge twisted pair to those pins and to one of the PCIe sockets where it joins the hashboard. Better yet - a separate pair coming from the board's input power planes to the remote sense in... The pic does label it as 'sense' and to me at least that means remote load sense vs v.adj. Just as with the HP DP1200 Commonn Slot Proliant supplies I have found it IMPOSSIBLE to get hold of a schematic for the power backplane these PSU's are used with. That would take all guesswork out of these. Prints for the various server boards or at the server boards backplane pinouts - no problem to find . grumble brumble. |
|
|
|
Well poop! Yer, right, everywhere it's about the 2kw supply - except for the performance curves..... Post edited to reflect that.  |
|
|
|
NJ power is 13 cents in the winter and 17 cents in the summer.
So solar or no mining. Plus the excess power can be sold back at 5 cents rather then mine. Note NJ is very good this way we are one of the better states with goverment subsidies for solar.
Well I'm sure you've though of this but for now just figure overall daily miner kwh usage and subtract how much of that the solar provided each day. Use that figure against the daily kWh rate to see what you pay the electric company each day of mining 24x7x365. No matter what the contribution made by the solar should be substantial. |
|
|
|
No, the wire losses would be greater than any inverter inefficiencies, plus you would need ALOT of copper. You have to remember even in a 150w 12v panel you looking at 12.5 Amps of current. 60kw would need copper that can support 5 THOUSAND AMPS of current lol...ill let you do the math on the copper thickness you need for that This is why most solar setups are wired in series, and some have muti kilovolts running into their main inverters, or simply have an 120v inverter directly on the panel. So very true. But assuming part of the idea is to allow it to run at night there are of course well established commercial ways around it. Disclaimer: I cannot say I've delved into this subject deeply. Only have good knowledge of how current large power systems work overall. To me the easiest is to first ask: What commercial power storage devices are being used for small (yes, even 16kw is still 'small') setups to allow running after dark when one is fully off the grid? Look to there for ideas. My guess is that it is a DC storage system be it batteries (bulky, insanely heavy, maint & lifetime issues), supercaps (very good but high initial expense), or whatnot rated at what the inverter/panels combo runs at be it 12, 48, or 600v. All involve robbing Peter to pay Paul. Can't forget that the power used to charge up for the night time comes from the daytime power budget. |
|
|
|
|
Only a heap of Avalon 6 chips so far for Kilo's commissioned project.
But, folks are working on BitFury to pitch-in with the Community aspect of it by lower the MOQ for this project. After all, they DO keep on talking about helping to spread and decentralize BTC along with helping grow the Community to do it...
By how much BitFury or any other 14/16nm miner chip maker helps or even if at all remains to be seen.
|
|
|
|
<snip> I focused on the pi because I've got some laying around that i'd love to put to use. What I meant for the new hardware is that I like the idea of making high powered hardware usb manageable so you could just plug it into existing or cheap hardware and upgrade your farm.
You still get to use your PI's. The boards would plug into a USB hub or ports on a computer running CGminer, the computer connects to the 'net. Can be an old laptop, an el'cheapo fanless Atom(R), or a PI. Anything that will run CGminer and has USB and LAN ports. |
|
|
|
<snip>
I bought a male stove plug to attach to my cable. I had 25 feet of cable to run from my kitchen to the balcony where i set up my rigs. I didn't use a surge surpressor at all as the PDU i bought had it's own protection. If the PDU doesn't have it's own protection, I'm not sure if the surge supressor would go before the PDU or after it.
If you have one a surge suppressor is always first in line with the PDU or power strip or UPS plugged into it. |
|
|
|
|
Nor I for a BTC Community miner. If the failed WASP project teaches anything it is to stay focused on 1 thing at a time whenever possible.
|
|
|
|
|
Show Posts
