Search content
Sort by
Showing 20 of 198 results by E
Re: [ANN] TeamRedMiner 0.9.4.6 - Ethash/FiroPow/Kawpow/Etchash/Autolykos2 and More
R Mode memory allocation question on Instinct MI25 and MI60. Is the memory allocation acting as expected, leaving ~10 / 26GiB free on the MI25s and MI60?
TRM 0.9.4.7
Linux 5.10.0-hiveos #83.hiveos.211201 SMP Wed Dec 1 11:51:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
AMD Driver 20.40 (5.11.1001)
0 04:00.0 Radeon Pro V320 16368 MB · 113-D0515300-101
1 08:00.0 Radeon Pro V320 16368 MB · 113-D0515300-101
2 0c:00.0 Radeon Pro VII 32752 MB · 113-D1630600-107
Thanks for trm!
TRM 0.9.4.7
Linux 5.10.0-hiveos #83.hiveos.211201 SMP Wed Dec 1 11:51:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
AMD Driver 20.40 (5.11.1001)
0 04:00.0 Radeon Pro V320 16368 MB · 113-D0515300-101
1 08:00.0 Radeon Pro V320 16368 MB · 113-D0515300-101
2 0c:00.0 Radeon Pro VII 32752 MB · 113-D1630600-107
Code:
Team Red Miner version 0.9.4.7
[2022-05-13 21:16:27] Linux kernel vm mode parameters are already correct.
[2022-05-13 21:16:27] Auto-detected AMD OpenCL platform 0
[2022-05-13 21:16:28] Initializing GPU 0.
[2022-05-13 21:16:28] Initializing GPU 1.
[2022-05-13 21:16:28] Initializing GPU 2.
[2022-05-13 21:16:28] GPU 0 Vega boost applied.
[2022-05-13 21:16:28] GPU 0 Starting tuning.
[2022-05-13 21:16:28] GPU 1 Vega boost applied.
[2022-05-13 21:16:28] GPU 1 Starting tuning.
[2022-05-13 21:16:28] GPU 2 Radeon VII boost applied.
[2022-05-13 21:16:28] GPU 2 Starting tuning.
[2022-05-13 21:16:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 04:00.0)
[2022-05-13 21:16:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 08:00.0)
[2022-05-13 21:16:28] Successfully initialized GPU 2: Vega2 with 64 CU (PCIe 0c:00.0)
...
[2022-05-13 21:16:33] GPU 0 DAG allocation trying 16368.0 - 9712.0 = 6656.0 MiB.
[2022-05-13 21:16:33] GPU 2 DAG allocation trying 32752.0 - 26096.0 = 6656.0 MiB.
[2022-05-13 21:16:33] GPU 1 DAG allocation trying 16368.0 - 9712.0 = 6656.0 MiB.
...
[2022-05-13 21:16:36] GPU 0 Starting DAG generation for epoch 492, 4.84 GB (single buffer mode).
[2022-05-13 21:16:37] GPU 1 Starting DAG generation for epoch 492, 4.84 GB (single buffer mode).
[2022-05-13 21:16:37] GPU 2 Starting DAG generation for epoch 492, 4.84 GB (single buffer mode).
[2022-05-13 21:16:41] GPU 2 DAG generation finished in 3.498 seconds.
[2022-05-13 21:16:41] GPU 0 DAG generation finished in 5.149 seconds.
[2022-05-13 21:16:42] GPU 1 DAG generation finished in 5.150 seconds.
[2022-05-13 21:16:27] Linux kernel vm mode parameters are already correct.
[2022-05-13 21:16:27] Auto-detected AMD OpenCL platform 0
[2022-05-13 21:16:28] Initializing GPU 0.
[2022-05-13 21:16:28] Initializing GPU 1.
[2022-05-13 21:16:28] Initializing GPU 2.
[2022-05-13 21:16:28] GPU 0 Vega boost applied.
[2022-05-13 21:16:28] GPU 0 Starting tuning.
[2022-05-13 21:16:28] GPU 1 Vega boost applied.
[2022-05-13 21:16:28] GPU 1 Starting tuning.
[2022-05-13 21:16:28] GPU 2 Radeon VII boost applied.
[2022-05-13 21:16:28] GPU 2 Starting tuning.
[2022-05-13 21:16:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 04:00.0)
[2022-05-13 21:16:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 08:00.0)
[2022-05-13 21:16:28] Successfully initialized GPU 2: Vega2 with 64 CU (PCIe 0c:00.0)
...
[2022-05-13 21:16:33] GPU 0 DAG allocation trying 16368.0 - 9712.0 = 6656.0 MiB.
[2022-05-13 21:16:33] GPU 2 DAG allocation trying 32752.0 - 26096.0 = 6656.0 MiB.
[2022-05-13 21:16:33] GPU 1 DAG allocation trying 16368.0 - 9712.0 = 6656.0 MiB.
...
[2022-05-13 21:16:36] GPU 0 Starting DAG generation for epoch 492, 4.84 GB (single buffer mode).
[2022-05-13 21:16:37] GPU 1 Starting DAG generation for epoch 492, 4.84 GB (single buffer mode).
[2022-05-13 21:16:37] GPU 2 Starting DAG generation for epoch 492, 4.84 GB (single buffer mode).
[2022-05-13 21:16:41] GPU 2 DAG generation finished in 3.498 seconds.
[2022-05-13 21:16:41] GPU 0 DAG generation finished in 5.149 seconds.
[2022-05-13 21:16:42] GPU 1 DAG generation finished in 5.150 seconds.
Thanks for trm!
Re: [ANN] TeamRedMiner 0.8.0 - Ethash/Kawpow/Nimiq/Etchash and More
0.8.0 on Radeon VII -- !
Code:
[2021-01-19 11:51:26] ------------------------------------------------------------------------------------------------
[2021-01-19 11:51:26] Mining ethash with 1 GPU workers
[2021-01-19 11:51:26] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC ETH Cfg
[2021-01-19 11:51:26] 0 04:00.0 60 1940 971 1200 52C 84C 69C 82.75% 3207 1025 mV C320
[2021-01-19 11:51:26]
[2021-01-19 11:51:26] Stats Uptime: 0 days, 00:17:00
[2021-01-19 11:51:26] ----------------------------------------- GPU Status -------------------------------------------
[2021-01-19 11:51:26] GPU 0 [52C, fan 82%] ethash: 120.0Mh/s, avg 119.0Mh/s, pool 123.2Mh/s a:87 r:0 hw:0
[2021-01-19 11:51:26] Total ethash: 120.0Mh/s, avg 119.0Mh/s, pool 123.2Mh/s a:87 r:0 hw:0
[2021-01-19 11:51:26] ----------------------------------------- Pool Status ------------------------------------------
[2021-01-19 11:51:26] daggerhashimoto.usa.nicehash.com ethash: 120.0Mh/s, avg 117.8Mh/s, pool 123.2Mh/s a:87 r:0
[2021-01-19 11:51:26] ------------------------------------------------------------------------------------------------
[2021-01-19 11:51:26] Mining ethash with 1 GPU workers
[2021-01-19 11:51:26] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC ETH Cfg
[2021-01-19 11:51:26] 0 04:00.0 60 1940 971 1200 52C 84C 69C 82.75% 3207 1025 mV C320
[2021-01-19 11:51:26]
[2021-01-19 11:51:26] Stats Uptime: 0 days, 00:17:00
[2021-01-19 11:51:26] ----------------------------------------- GPU Status -------------------------------------------
[2021-01-19 11:51:26] GPU 0 [52C, fan 82%] ethash: 120.0Mh/s, avg 119.0Mh/s, pool 123.2Mh/s a:87 r:0 hw:0
[2021-01-19 11:51:26] Total ethash: 120.0Mh/s, avg 119.0Mh/s, pool 123.2Mh/s a:87 r:0 hw:0
[2021-01-19 11:51:26] ----------------------------------------- Pool Status ------------------------------------------
[2021-01-19 11:51:26] daggerhashimoto.usa.nicehash.com ethash: 120.0Mh/s, avg 117.8Mh/s, pool 123.2Mh/s a:87 r:0
[2021-01-19 11:51:26] ------------------------------------------------------------------------------------------------
Re: [25+PH] KanoPool kano.is NO FEE TIL 2018 PPLNS US,DE,SG,JP,NL,NYA 🐈
Looking at the logs, there was only one time that the command included a hashed password (the last time) - so it would seem the password field was always blank (except the last time)
Do you mean in your miner configuration? Just use 'x' or '123' or similar.
At the risk of sound really really stupid...what do I enter as the password for my BTC address? Blank obviously doesn't work, and coinbase does not issue me a password for my BCT address. Where do I get a password for a BTC address? Thanks in advance for your reply...eager to try out KanoPool!
Greetings,
I'm using psu from bladecenter and I wonder if theres a chance to manage eg. fans in this unit. After turning them on, they're spinning at max speed (after while) even when nothing is connected to the PSU. Air blowing from the back is cold. I have few questions about that:
1. Is there any way to manage fan speed (reduce it)?
2. PSU only connected to AC draws about 70W (fans turned off) from the wall - is it normal?
I'm using psu from bladecenter and I wonder if theres a chance to manage eg. fans in this unit. After turning them on, they're spinning at max speed (after while) even when nothing is connected to the PSU. Air blowing from the back is cold. I have few questions about that:
1. Is there any way to manage fan speed (reduce it)?
2. PSU only connected to AC draws about 70W (fans turned off) from the wall - is it normal?
1. No straightforward way to reduce fan speed. You can talk PMBus to the power supply and convince it it is in a healthy chassis or splice into the fan supply lines and control them that way, but no easy method that I'm aware of.
2. None of the IBM bladecenter supplies I have experience with are happy being plugged in but not running. Their standby consumption is high enough that internal components can easily overheat without the fans running. I've lost DPS-2000BB and DPS-2980AB supplies to this.
Re: [Unofficial] Modded NiceHashMiner (v1.7.5.15-mod) (3rd party miners support)
Thanks so much for this - working great here. I suggest -dcri 225 for DaggerSia on 1080Ti right now btw 
One issue:
I had to multiply my Lyra2REv2 speed by 1000 to get sensible numbers out of this build (and sorting is broken for profit > $9.99):
One issue:
Update version: 1.7.5.15-mod
Changelog:
...
Changelog:
...
- Fix Lyra2REv2 Algorithm returning crazy ass numbers (i.e: 2000 USD/day)
I had to multiply my Lyra2REv2 speed by 1000 to get sensible numbers out of this build (and sorting is broken for profit > $9.99):
Code:
Profits for GPU#1 ASUS GeForce GTX 1080 Ti:
PROFIT = $10.32 (SPEED = 754 | NHSMA = 4847.135) [ewbf_Equihash]
PROFIT = $10.98 (SPEED = 3300000000 | NHSMA = 0.00117783) [ccminer_Sia]
PROFIT = $11.78 (SPEED = 28300000/2114000000 | NHSMA = 0.059396/0.00117783) [ClaymoreAMD_DaggerSia]
PROFIT = $2.04 (SPEED = 433830 | NHSMA = 1.662647) [experimental_NeoScrypt]
PROFIT = $3.77 (SPEED = 11510000 | NHSMA = 0.11591) [ccminer_X11Gost]
PROFIT = $5.56 (SPEED = 33164250 | NHSMA = 0.059396) [ethminer_DaggerHashimoto]
PROFIT = $6.68 (SPEED = 33000000/330000000 | NHSMA = 0.059396/0.00122464) [ClaymoreAMD_DaggerPascal]
PROFIT = $6.68 (SPEED = 5266660000 | NHSMA = 0.00044877) [ccminer_Decred]
PROFIT = $6.70 (SPEED = 1937340000 | NHSMA = 0.00122464) [excavator_Pascal]
PROFIT = $7.53 (SPEED = 23000000 | NHSMA = 0.11591) [ccminer_alexis_X11Gost]
PROFIT = $8.13 (SPEED = 27000000/2837000000 | NHSMA = 0.059396/0.00044877) [ClaymoreAMD_DaggerDecred]
PROFIT = $9.10 (SPEED = 664.733373 | NHSMA = 4847.135) [excavator_Equihash]
PROFIT = $9.44 (SPEED = 73550000000 | NHSMA = 0.045437) [ccminer_Lyra2REv2]
PROFIT = $9.61 (SPEED = 541990000 | NHSMA = 0.00627472) [ccminer_Lbry]
PROFIT = $9.88 (SPEED = 27600000/296000000 | NHSMA = 0.059396/0.00627472) [ClaymoreAMD_DaggerLbry]
MOST PROFITABLE ALGO: ClaymoreAMD_DaggerSia, PROFIT: $11.78
PROFIT = $10.32 (SPEED = 754 | NHSMA = 4847.135) [ewbf_Equihash]
PROFIT = $10.98 (SPEED = 3300000000 | NHSMA = 0.00117783) [ccminer_Sia]
PROFIT = $11.78 (SPEED = 28300000/2114000000 | NHSMA = 0.059396/0.00117783) [ClaymoreAMD_DaggerSia]
PROFIT = $2.04 (SPEED = 433830 | NHSMA = 1.662647) [experimental_NeoScrypt]
PROFIT = $3.77 (SPEED = 11510000 | NHSMA = 0.11591) [ccminer_X11Gost]
PROFIT = $5.56 (SPEED = 33164250 | NHSMA = 0.059396) [ethminer_DaggerHashimoto]
PROFIT = $6.68 (SPEED = 33000000/330000000 | NHSMA = 0.059396/0.00122464) [ClaymoreAMD_DaggerPascal]
PROFIT = $6.68 (SPEED = 5266660000 | NHSMA = 0.00044877) [ccminer_Decred]
PROFIT = $6.70 (SPEED = 1937340000 | NHSMA = 0.00122464) [excavator_Pascal]
PROFIT = $7.53 (SPEED = 23000000 | NHSMA = 0.11591) [ccminer_alexis_X11Gost]
PROFIT = $8.13 (SPEED = 27000000/2837000000 | NHSMA = 0.059396/0.00044877) [ClaymoreAMD_DaggerDecred]
PROFIT = $9.10 (SPEED = 664.733373 | NHSMA = 4847.135) [excavator_Equihash]
PROFIT = $9.44 (SPEED = 73550000000 | NHSMA = 0.045437) [ccminer_Lyra2REv2]
PROFIT = $9.61 (SPEED = 541990000 | NHSMA = 0.00627472) [ccminer_Lbry]
PROFIT = $9.88 (SPEED = 27600000/296000000 | NHSMA = 0.059396/0.00627472) [ClaymoreAMD_DaggerLbry]
MOST PROFITABLE ALGO: ClaymoreAMD_DaggerSia, PROFIT: $11.78
Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion
Mainstream getting up & running with propaganda countermeasures.
https://www.ft.com/content/b5d66ed8-d1b3-11e6-b06b-680c49b4b4c0
https://www.technologyreview.com/s/603295/why-bitcoins-1000-value-doesnt-matter/
From the Technology Review article:
Quote
The structure of Bitcoin means that if a small number of users hold the majority of the currency, as is the case with these Chinese companies, then they are able to veto changes to the underlying technology.
/eyeroll
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
19th nov firmware is the best one
stable fan speed and low temp
stable fan speed and low temp
Somehow I was unable to find this??? Do you have a link?
Thank you
Here it is:
https://shop.bitmain.com/files/download/Antminer-S9-all-201611190345-autofreq-user.tar.gz
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
for those of you wandering if this is the auto tune version. This pic seems to be a stock 14TH model. so it will be set to hash at 650M frequency by the firmware.
Fan speed is much better handled for me - slight variations in speed, gently ramped, instead of the bang-bang controller in the previous autotune FWs.
Seeing much lower reported temps (~10C lower) but I haven't dug into whether that is just a cosmetic change or a change in setpoint for target temp.
Hashrate is good - 13.904avg over3025 hours on a batch 1 set to 650MHz (theoretical speed 14.004):
Nice of you to jump in, and still be following the thread.Has anyone tried the firmware from 11-19? I'm giving it a shot on one machine right now. Curious how it is working for others?
Fan speed is much better handled for me - slight variations in speed, gently ramped, instead of the bang-bang controller in the previous autotune FWs.
Seeing much lower reported temps (~10C lower) but I haven't dug into whether that is just a cosmetic change or a change in setpoint for target temp.
Hashrate is good - 13.904avg over
but please, can we discuss the elephant in the room? wtf is with these fans
They idle so low one minute, and the next minute my neighbors can hear them.
I have no issue with noisy miners, but this seems like it's just unrequired noise.
One minute they blast at 110% the next they are cruising at 25%. than boom back up again.
If they idled Higher, at 60% maybe? they would need to spike as often, and this would help with the noise greatly.
takagari - This is what I posted about re: the 19 Nov firmware. For me, this firmware stops the fan cycling and replaces it with much subtler changes in speed. Higher average speed over all, but barely perceptable speed changes.
It's a big improvement on my S9, which is a Batch 1 / 14TH/s as BitmainWarranty suggested.
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
Has anyone tried the firmware from 11-19? I'm giving it a shot on one machine right now. Curious how it is working for others?
Fan speed is much better handled for me - slight variations in speed, gently ramped, instead of the bang-bang controller in the previous autotune FWs.
Seeing much lower reported temps (~10C lower) but I haven't dug into whether that is just a cosmetic change or a change in setpoint for target temp.
Hashrate is good - 13.904avg over
That's awesome, so does it allow fan tweaking or tweaking of the Hastrate?
Nope :\ At least not through the web UI and I haven't the time to poke through the config files and see where that's being handled now.
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
Has anyone tried the firmware from 11-19? I'm giving it a shot on one machine right now. Curious how it is working for others?
Fan speed is much better handled for me - slight variations in speed, gently ramped, instead of the bang-bang controller in the previous autotune FWs.
Seeing much lower reported temps (~10C lower) but I haven't dug into whether that is just a cosmetic change or a change in setpoint for target temp.
Hashrate is good - 13.904avg over
Here are the revisions and corresponding production dates I'm aware of for the BladeCenter H 2880 and 2980 power modules.
If you've got one of these supplies with a revision not listed below, or a known revision that extends the date range, it'd be great if you could post an image of the label in this thread.
I have all of the revisions marked * on hand; if anyone in the Seattle area has a revision I don't I'd love to make efficiency measurements and take the cover off for a few photos.
The revision and date code can be located as indicated on the labels:
If you've got one of these supplies with a revision not listed below, or a known revision that extends the date range, it'd be great if you could post an image of the label in this thread.
I have all of the revisions marked * on hand; if anyone in the Seattle area has a revision I don't I'd love to make efficiency measurements and take the cover off for a few photos.
Code:
Astec AA23920L (2880W)
Revision Date Code Range (YYWW)
------------------------------------------
7 0610
8* 0617 -> 0640
9 0716 -> 0720
10* 0737 -> 0833
11* 0912 -> 0928
12* 0945 -> 1012
13* 1012 -> 1022
14 1033
15* 1036 -> 1042
Revision Date Code Range (YYWW)
------------------------------------------
7 0610
8* 0617 -> 0640
9 0716 -> 0720
10* 0737 -> 0833
11* 0912 -> 0928
12* 0945 -> 1012
13* 1012 -> 1022
14 1033
15* 1036 -> 1042
Code:
Delta DPS-2980AB A (2980W)
Revision Date Code Range (WWYY)
------------------------------------------
S4F 2710 -> 3110
S5F Not Observed
S6F 4410
S7F 4710 -> 4910
S8F* 0611 -> 1211
S9F* 4111 -> 3313
S10F 3714
Revision Date Code Range (WWYY)
------------------------------------------
S4F 2710 -> 3110
S5F Not Observed
S6F 4410
S7F 4710 -> 4910
S8F* 0611 -> 1211
S9F* 4111 -> 3313
S10F 3714
The revision and date code can be located as indicated on the labels:
- 6THash @ 900W @ $888
- 0.15J/GHash or 150W/THash/s
- $0.15/GHash/s or .21BTC/THash/s
"Aluminum PCB" -> Presumably a MCPCB
72 A3212 Chips per miner -> 83GHash/s per chip -> Each chip is equivalent to an up-clocked Avalon 1.
- 0.15J/GHash or 150W/THash/s
- $0.15/GHash/s or .21BTC/THash/s
"Aluminum PCB" -> Presumably a MCPCB
72 A3212 Chips per miner -> 83GHash/s per chip -> Each chip is equivalent to an up-clocked Avalon 1.
I wanted to add some DPS-2000BB efficiency numbers to this thread, as I've recently been measuring DC and AC draw on my S9 at various clock speeds.
Counting 12V cable losses, I'm seeing 88.3 to 88.7% efficiency everywhere from 800W up to 1400W DC. Ignoring cable losses the efficiency is 89.7 to 90%.
This is all at a 208V input voltage... efficiency should be higher with higher input voltage but I haven't been able to test that yet.
Counting 12V cable losses, I'm seeing 88.3 to 88.7% efficiency everywhere from 800W up to 1400W DC. Ignoring cable losses the efficiency is 89.7 to 90%.
This is all at a 208V input voltage... efficiency should be higher with higher input voltage but I haven't been able to test that yet.
Higher input voltage, implies lower input current (Usually). If your losses are dominated by I^2 * R, then it will help.
For example, an unspecified HP PSU measured in 2007:
BTW I'm making my measurements with a calibrated Xitron 2503AH (http://www.xitrontech.com/products/general-purpose-power-analyzers/#2503ah) with an external 500A precision shunt for the DC current; the Xitron is good to better than 0.05% on the internal I/V measurements but the shunt is only spec'd to 0.1% so that dominates the error.
One cool thing you can observe with this is how current draw from a miner increases by 10s of watts as everything warms up to operating temperature. I'll try to get a video of that because it is pretty interesting to watch!
So if there is no link for batch 4 firmware where did you find the info?
That screenshot is from the bitmain firmware site; the file descriptions are:
Quote
S9 firmware-20160608-650M
s9firmware-20160608-600M,12.93T
s9 firmware -20160608-550M,11.85T
s9firmware-20160608-600M,12.93T
s9 firmware -20160608-550M,11.85T
The last line showed up most recently. Like I said - speculation, but it is pretty suggestive.
I wanted to add some DPS-2000BB efficiency numbers to this thread, as I've recently been measuring DC and AC draw on my S9 at various clock speeds.
Counting 12V cable losses, I'm seeing 88.3 to 88.7% efficiency everywhere from 800W up to 1400W DC. Ignoring cable losses the efficiency is 89.7 to 90%.
This is all at a 208V input voltage... efficiency should be higher with higher input voltage but I haven't been able to test that yet.
Counting 12V cable losses, I'm seeing 88.3 to 88.7% efficiency everywhere from 800W up to 1400W DC. Ignoring cable losses the efficiency is 89.7 to 90%.
This is all at a 208V input voltage... efficiency should be higher with higher input voltage but I haven't been able to test that yet.
Re: Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order
I've taken some calibrated DC draw and other power measurements on my one S9. I've taken some care with these and everything should be accurate to at least the precision I give.
Short version of results:
S9 DC Draw at 12.1V == 1.89W/MHz + 57W
The 1.89W/MHz holds across at least 450 to 668.75 on this unit; the 57W is the controller and fans at 100%.
At 650 w/ 100% fan I see 106.67A @ 12.051V for 1285.5W.
50% fan reduces this to 1275W, hitting the S9 specification.
PSU is a DPS-2000BB being fed 208V; voltage at PSU ranged from 206.8 to 208.7 during these tests.
All measurements taken simultaneously - Dedicated sampling for I & V on both AC & DC
+12V measured at the S9 board inputs ranged from 12.051 to 12.146, depending on load.
These DC Power draw measurements below _do not_ include loses in the 12V cables - these are dependent on your setup but may be around 10W; actual PSU efficiency is accordingly around 1% higher.
Short version of results:
S9 DC Draw at 12.1V == 1.89W/MHz + 57W
The 1.89W/MHz holds across at least 450 to 668.75 on this unit; the 57W is the controller and fans at 100%.
At 650 w/ 100% fan I see 106.67A @ 12.051V for 1285.5W.
50% fan reduces this to 1275W, hitting the S9 specification.
| MHz | | DC W | | AC W | | PSU Eff. | | W @ Wall w/ Fan | | J/GH @ Wall |
| 450 | 855 | 968 | 88.3 | 1033 | 0.107 |
| 550 | 1040 | 1175 | 88.5 | 1240 | 0.105 |
| 600 | 1133 | 1281 | 88.4 | 1346 | 0.104 |
| 625 | 1179 | 1333 | 88.4 | 1398 | 0.104 |
| 650 | 1229 | 1391 | 88.4 | 1456 | 0.104 |
| 668.75 | 1265 | 1433 | 88.3 | 1498 | 0.104 |
PSU is a DPS-2000BB being fed 208V; voltage at PSU ranged from 206.8 to 208.7 during these tests.
All measurements taken simultaneously - Dedicated sampling for I & V on both AC & DC
+12V measured at the S9 board inputs ranged from 12.051 to 12.146, depending on load.
These DC Power draw measurements below _do not_ include loses in the 12V cables - these are dependent on your setup but may be around 10W; actual PSU efficiency is accordingly around 1% higher.
I don't want to take this too far
it says 1275 dc + 7% at wall based on a plat psu. that 1200 watt can do 1320 watts at the wall as I think it is a gold not a plat.
a 1275 dc x 1.1 = 1402 at the wall.
so you need a better psu then those 1200 watt hp dps 1200 and remember the spec up are for the batch 2 and batch 3 s-9's
the s-9 batch 1 was specced to run at freq 650 and use 1390 watts dc +7% if a plat psu.
there is no way the hp dps1200 should be used on an s-9 unless you really clock low like 450 to 500 or so.
I've finally managed to take some direct measurements of DC draw on an S9.
Even though it's mining on kano.is during the measurements, I don't want to go too far o/t with details, but:
The DC draw for this unit is 1.89W*MHz + 57W for fans/controller everywhere from 450MHz to 668.75MHz.
At 650 w/ 100% fan the DC draw is 106.67A @ 12.051V = 1285.5W
50% fan only saves about 10W, but does take the unit exactly to its spec of 1275W.
Hello,
Technically, if the S9 really use 1275W At the wall, it's use 1275 x 0.93 = 1185W on 12V. So a good quality 1200W PSU is enough but be the smallest unit you can use.
But usually, best efficiency is obtain at the half of power. At full power, you usually loose between 1 and 2% efficiency.
So a gold PSU used at 50% is very near a platinum PSU used at 100% (and will probably be more reliable)
Technically, if the S9 really use 1275W At the wall, it's use 1275 x 0.93 = 1185W on 12V. So a good quality 1200W PSU is enough but be the smallest unit you can use.
But usually, best efficiency is obtain at the half of power. At full power, you usually loose between 1 and 2% efficiency.
So a gold PSU used at 50% is very near a platinum PSU used at 100% (and will probably be more reliable)
it says 1275 dc + 7% at wall based on a plat psu. that 1200 watt can do 1320 watts at the wall as I think it is a gold not a plat.
a 1275 dc x 1.1 = 1402 at the wall.
so you need a better psu then those 1200 watt hp dps 1200 and remember the spec up are for the batch 2 and batch 3 s-9's
the s-9 batch 1 was specced to run at freq 650 and use 1390 watts dc +7% if a plat psu.
there is no way the hp dps1200 should be used on an s-9 unless you really clock low like 450 to 500 or so.
I've finally managed to take some direct measurements of DC draw on an S9.
Even though it's mining on kano.is during the measurements, I don't want to go too far o/t with details, but:
The DC draw for this unit is 1.89W*MHz + 57W for fans/controller everywhere from 450MHz to 668.75MHz.
At 650 w/ 100% fan the DC draw is 106.67A @ 12.051V = 1285.5W
50% fan only saves about 10W, but does take the unit exactly to its spec of 1275W.
Block by ginex! Welcome to the Acclaim Board with your first Kano Block! 
That is our 7th of the day! Rolling!
That is our 7th of the day! Rolling!
Sitting at 0.01CDF for last 5 blocks!