BTW, anyone want to go and update README with all these tips I've been dropping on the forum thread(s)? :p
I added info to the U3 section of your readme-asic: ANTMINER U3 -----------
The U3 does not support autodetection, so you will want to use --scan-serial to manually probe it. For example, to scan all devices, you can use:
-S antminer:all --set antminer:chip=BM1382
Additionally, for optimal performance you will need to set voltage, clock, and timing. Voltage format for the U3 is not documented by the manufacturer, thus must be provided as hexadecimal configuration codes. Timing is provided in the number of nanoseconds each hash takes at the given configuration. A known-working configuration is:
--set antminer:voltage=x800 --set antminer:clock=237.5 --set antminer:timing=0.022421
To set different frequency and voltage settings for multiple U3 miners on a single BFGMiner process use:
--set antminer@\\.\COM10:voltage=xNNNN
or
--set antminer@/dev/ttyUSB1:voltage=xNNNN
Another option is to program the CP2102 chip so they have unique serial numbers; this method would avoid problems with the device showing up on different tty/COM locations after reboot/hotplug:
/cp210x-program -w -F eeprom-content.AntU3-custom.hex --set-product-string='Antminer U3' --set-serial-number=myveryown0001
Then you can use --set antminer@myveryown0001:voltage=xNNNN I also added the RPC command to adjust frequency to the compac part or readme-asic: COMPAC ------
These USB sticks are based on Bitmain's BM1384 chip, and use the antminer driver. You can set the clock frequency with
--set compac:clock=200
You can also adjust the clock real-time while the stick is hashing using RPC's pgaset:
bfgminer-rpc "pgaset|0,clock,x0982" | ^^^^^ hex frequency ^ device number
Added a few more suggested uses for --set-device from readme: --set-device|--set <arg> Set default parameters on devices; eg, NFY:osc6_bits=50, bfl:voltage=<value>, compac:clock=<value>
|
|
|
- Pool option #cksuggest to use CKPool-compatible mining.suggest_difficulty stratum extension.
Could you please explain how to use this command? I do not see it in the readme and it does not appear to be a command line option. Thank you!
|
|
|
I like the look of v1 way, way better than v2. v2 looks unfinished to me, v1 looks like a little ufo and is almost cool. I took the metal cover off for a while but the bottom heak sink was still really warm. The extra fan beneath is the best way to cool them that I have found.
I agree, ck, Bitmain should have made improvements to v2 that everyone had repored with v1, then this little usb miner might have actually been worth something. For now I await gekko sciences's pod miner, we know that one will work!
|
|
|
6 hours later and still unconfirmed, that's odd.
|
|
|
That is really impressive, especially given all the problems people reported with the S5. It's like they brought back the S1 bullet proof-ness for the S5+. I hope their S7s run as smoothly. Now if only my electricity was priced such that I could run any of these new machines...
|
|
|
I important thing on that link on their website: Difficulty: Hard Work should be performed by a licensed electrician Check local ordinances but most places will require a licensed electrician and possibly permits. Or you might be lucky and live in a place with not much ordinances. Upgrading to a 200 amp is not really a DIY thing. I am good at diy. my home was built during the Vietnam era many homes built in New Jersey at that time used interior aluminum wire due to a war copper shortage. I wired my entire home in copper. I put in 32 new circuits but when it came time to put in a 200 amp 120/240 box with room for forty single pole or 20 double pole breakers I called in a pro. The reason is simple I would not trust myself with 2 wires from the outside transformer that are hot and carry 48000 watts of power. The licensed electrician went to my roof disconnected the lives wires from the meter put the box in did all the inside work and then attached the two outside wires well worth the money I paid him. I'm a big DIY guy myself also. I do basically all of my own auto maintenance/repairs and home improvements, build my own computers, etc. etc. There are some things that, even though I know I am technically capable of, I still leave to a professional. Generally it's anything that could kill me if I do it wrong. It only takes one slip up working with a main breaker and BAM, your heart will get stopped instantly. There's also the risk that something you wired up could cause a fire and that not only puts you and your belongs in danger, but your neighbors as well.
|
|
|
Its like the U3 gets stuck in some sort of initialization loop and some of the circuitry is allowing spikes by design. I really dont feel like making a schematic for this thing to look for possible culprits...
<snip>
To keep it a little cooler, I have it balanced on the top of a powered on gridseed 5chip. The gridseed fan helps keep it much cooler.
I chatted with a member here who took one of my U3s apart and he mentioned something about how crappy the circuitry is regarding the power and usb. I don't know enough about hardware tech to repeat what he told be, but yes, I think there is a "short cut" somewhere in Bitmains schematic that causes most of the issues with these devices. I also performed a similar cooling mod. I run my U3 at 237.5freq 785volt, and even that makes the bottom heat sink almost uncomfortably hot. With this mod it's barely warmer than ambient.
|
|
|
Now, I need to find the way, how much will be daily power consumption.. :-( I have no idea
It's easy to figure out. You know how many watts the S7 uses. Multiply that by how many hours per day you will mine with it and divide by 1000, that is how many kilowatt hours/day you will use. Multiply that by 30 and that's how many KWh you will use in a month. Multiply that by your electricity rate and that's what it will cost you to run an S7 per month. Omit the x30 step and that will give you per day cost. For me to run one 24/7 for a month it would cost = 1.25KW * 24h * 30d * $0.30 = $270 a month. My daily cost would be = 1.25KW * 24h * $0.30 = $9 a day. That's also why I will never own one.
|
|
|
Upgrade to version 5.4.0 complete, successfully able to adjust compac frequency on the command line via the --set compac:clock command, thanks for the update!
|
|
|
If you guys are interested to see and hear what I experience, I will record and post the video here next time when I get that.
I would also be interested where the sound is coming from on the device specifically. As far as I know there are no speakers on the circuit board or anything. Is it some sort of feed back sounds from the electronics, or is it a honest beep from a speaker?
|
|
|
300 to stay without jumping all around is going to take quite a bit of sells to happen I think personally before it sticks. I would love to see 300 as a solid price though.
I like 300, too. It's a nice round number, and it looks much better than 200. I'm not sure exactly what is driving the recent price increase, but it's nice to see the price getting back up to where it was before XT launched. That really threw a monkey wrench into everything and was part of the reason we lost all that ground price-wise I think. So maybe not so much making head way as it is gaining lost ground.
|
|
|
The hashrate may drop at some point as we plan to sell a bunch of miners to make room for the new ones that we have already paid for.
Oh, very exciting! What gear are you bringing online? You have been very successful so far using "older" gear that others have sold off, so I was wondering if this is new new gear, meaning more efficiency, or more previous generation gear? Hi yslyung,
Your deposit of -----...BTC was added to your balance and the ------ BTC correctly reflected your balance.
Should you really be publishing user's balances and transaction details in a public forum?
|
|
|
I had an old burnt up bfl jalapeno, so I took the heat sink fan combo and mounted it onto a GS stick.
Holy cow, that looks awesome! How warm to the touch does that massive sink get when you crank up the stick? Weird question, but is it too much weight for the usb port? All that mass at the end of the stick will produce a relatively big moment where it plugs in. Sorry, the engineer in me wonders these things.
|
|
|
I've had multiple V1 U3s (solid dome) and still have 1 that I play with. I have never heard them beep, I didn't even know they had that capability.
|
|
|
Sadly, i do not see how to measure amperage to figure out what the maximum clock i should set it to with a y-splitter on an USB3.0 hub. I only have a multi meter.
Get a usb tester: http://www.amazon.com/DROK-Multimeter-Capacity-Charging-Alignment/dp/B00J3JSEG6I just ordered 4 sets of Y cables so I can really start playing with my sticks. Highest freq. I can get on hub right now is 262.5 without exceeding the amp rating for each port.
|
|
|
is it safe to turn the knob while the thing is hashing to find the sweet spot?
Yes, you can adjust voltage while it is hashing and stop once the HW error stop. Very nice for real-time feed back rather than having to edit a command line, stop and restart hashing, etc.
|
|
|
Cyrus, can you update the OP to have the full release notes? Bitcoin.org didn't have the full release notes when they initially posted the new release. They were missing the information about the minrelaytxfee default increase. This has been fixed now.
If by "fixed" you mean 30x higher, then yes, they were "fixed". A tx I sent to a company a few weeks ago has a fee of like 2000 satoshi. I sent another tx for the same amount to the same company yesterday and the default fee added was over 60,000 satoshi. Yikes!
|
|
|
Using 5.3.0 to run a couple gekko compac sticks and no matter what value I input for --set compac:clock= the sticks hash as if they were set to 225 (x0882), so at about 11GH/s each. Any idea why the sticks are not taking the frequency setting?
Found this bug. Will fix in 5.4. Workaround: Use --set cbm:clock=x0783 instead. I forgot to set the "compac" name on the driver... :| Wonderful, thank you! Now I have to dig up my usb tester and start dialing these sticks up. edit - I have been unable to produce successful results with the revised cbm command, my sticks still hash at default frequency. Hmm, I did test that it works on my Compac pre-prod sample before posting it here :/ Does it work any better if you use RPC's pgaset? bfgminer-rpc 'pgaset|cbm0,clock,x0783' Cross posting to follow up. Note --set cbm:clock=xNNNN will also work; you just need to abbreviate it "cbm" and can't spell out "compac". (That's what is being fixed in 5.4 - being able to spell it out)
I was unable to get --set cbm:clock=xNNNN to work. I believe you said you used it on the pre-production stick that was sent to you, but I cannot duplicate your success on the production stick. I assumed that your problem was the extra leading zero... no? :/ Can anyone else with a prod unit confirm/deny a problem? I can't imagine what would be different.. :| Ahh, could be. I was thinking the leading 0 issue was with the RPC command, I do not recall if I used a leading 0 on the --set as well. I will confirm tomorrow. As an aside, the RPC way of adjusting frequency is pretty darn cool since you can do it while they are running. Couple that with the adjustable voltage, also while running, and you've got real time feedback from a very customizable piece of hardware! You were right, I must have been using the leading 0 in my command line because without it --set cbm:clock worked perfectly. But like I said above, I still think the RPC way to do it is cool and useful.
|
|
|
Note --set cbm:clock=xNNNN will also work; you just need to abbreviate it "cbm" and can't spell out "compac". (That's what is being fixed in 5.4 - being able to spell it out)
I was unable to get --set cbm:clock=xNNNN to work. I believe you said you used it on the pre-production stick that was sent to you, but I cannot duplicate your success on the production stick. I assumed that your problem was the extra leading zero... no? :/ Can anyone else with a prod unit confirm/deny a problem? I can't imagine what would be different.. :| Ahh, could be. I was thinking the leading 0 issue was with the RPC command, I do not recall if I used a leading 0 on the --set as well. I will confirm tomorrow. As an aside, the RPC way of adjusting frequency is pretty darn cool since you can do it while they are running. Couple that with the adjustable voltage, also while running, and you've got real time feedback from a very customizable piece of hardware! You were right, I must have been using the leading 0 in my command line because without it --set cbm:clock worked perfectly. But like I said above, I still think the RPC way to do it is cool and useful.
|
|
|
I am assuming you are offering a private party transfer through a licensed gun dealer, right? At least here in Kalifornia you cannot sell any firearm without using a dealer unless it's an antique. I carry a S&W M&P 40c when I'm out in the desert. Yes they are called FFL dealers. I mentioned this above. Read it. Ask nicely... I didn't see it in the OP, so thought I would ask. I did find it a couple posts down, but it would be more appropriate to put that info up top for people like me who browse for sale posts by the top post only. GL with the sale.
|
|
|
|