Official FutureBit Apollo BTC Software/Image and Support thread - page 42.

MrMik

member

Activity: 203

Merit: 37

Quote from: crypto_curious on December 25, 2022, 11:05:39 AM

Polli at arms length.
Why not removing Apollo from its original case? I did that, and it's been running fine for many months. Still using original fan. Without the case, air intake is excellent and it may lower your fan speeds/temperature.

https://imgur.com/a/3D2Cvsa

The noise from your naked Apollo does not matter where you have installed it. All the other components in the PC case make noise anyway.

I am aiming at much quieter operation, to gently heat a bedroom in Winter, for example, without noise. The limiting factor is still that I cannot get a fan that will run slower than 1800rpm but will also run very fast when needed.

And I think that maybe (only maybe, I have not systematically tested that) removal of the housing makes part or all of the Apollo hotter:
- the entire metal housing is a heat sink
- the hottest components I can find are located on the circuit board close to the 12V connectors. See IR photo below. This area receives forced airflow when the housing is in place, the air must flow over these hot components to enter the large heatsink. Without the housing, those 2 hottest components might have to rely on more passive convection cooling and maybe they get hotter than with the housing in place.

crypto_curious

full member

Activity: 933

Merit: 175

Quote from: MrMik on December 03, 2022, 02:50:36 AM

Same contraption shown in infra-red. Very handy to find hot-spots.

The ASIC temperature appears stable at 79degC with only the Noctua NF-A9 running (but I have turned the added PSU fan back on low to keep the PSU happy).

This is what happens when I also turn on the Noctua 200mm fan:

- It gets quieter while the internal fan slows down and the ASIC temp eventually settles at around 61degC;
- the Noctua NF-A9 slows down to 1150rpm or less
- the noise level at arm's length (0.5m) is clearly lower than the noise from a practically unmodified Full Package Apollo operating about 3.5m away from me (with an ASIC temp of 59degC and the stock fan running at 2905rpm).
- the wildlife, birds, crickets etc outside are seriously interfering with my ability to hear the modded Polli at arms length.

Grin

But the problem remains that the Noctua NF-A9 does not have the Oooompf to cope with a heat wave, and I want Polli to stay at least as safe as it was when I started to deconstruct it's warranty! Cheesy

Why not removing Apollo from its original case? I did that, and it's been running fine for many months. Still using original fan. Without the case, air intake is excellent and it may lower your fan speeds/temperature.

https://imgur.com/a/3D2Cvsa

crypto_curious

full member

Activity: 933

Merit: 175

Quote from: MrMik on November 05, 2022, 09:05:48 PM

It seems like there is a minimum speed of about 1800rpm for the built-in ASIC fan, no matter what settings I choose for the Fan Temp Settings.

Is that true or am I missing something?

My lowest reads:

Code:

Apollo Miner
Hashrate: 2011 GH/s
Error rate: 0.3%
Power draw: 126 W
Temperature: 54°C
Fan: 1558 RPM
Uptime: 16d:5h:7m
Process memory: 1.4 MiB

That's with very cold ambient temperature.

MrMik

member

Activity: 203

Merit: 37

Quote from: 100knot2dae on December 19, 2022, 04:54:21 PM

For some reason beyond my understanding, this malfunctioning Standard Apollo connects to and hashes for a Full Package Apollo again, but it still will not work when connected to my laptop in the same way that it used to work before it started to play up.

Assuming a permission issue on the device file /dev/ttyACM0, try the command with sudo prefixed (so it runs as root). According to your code snippet you run the miner as non-privileged user (which is absolutely recommended!), but in this case you need to add the user to the dialout group.
[/quote]

Spot on!

Thank you very much!

I made the same error on my newly built armbian system (running in a FP Apollo) and on my laptop at the same time, because I was renaming the .sh files so they tell me which ACM* will be used without opening the file. Then I pasted the new name into the terminals and forgot the sudo. And then I used the up-arrow to repeat the same faulty command without sudo over and over again. Roll Eyes

That made it appear as if the Standard Apollo was broken.
Then it did not connect when I tried to run it (just once) via a FutureBit FP Apollo with stock SD-card in it and I assumed it does not work, anywhere. But sometimes it does not boot immediately (or at all) and needs to be restarted.

I hope I'll remember that one, it should come in handy many times.

100knot2dae

member

Activity: 100

Merit: 29

Quote from: MrMik on December 19, 2022, 05:37:46 AM

One of my Standard Apollo's is suddenly refusing to play nicely.

I have rebooted all and sundry a few times and I have tried 2 different cables.

Any ideas what is going wrong here, anyone?

Added:
For some reason beyond my understanding, this malfunctioning Standard Apollo connects to and hashes for a Full Package Apollo again, but it still will not work when connected to my laptop in the same way that it used to work before it started to play up.

Assuming a permission issue on the device file /dev/ttyACM0, try the command with sudo prefixed (so it runs as root). According to your code snippet you run the miner as non-privileged user (which is absolutely recommended!), but in this case you need to add the user to the dialout group.

MrMik

member

Activity: 203

Merit: 37

One of my Standard Apollo's is suddenly refusing to play nicely.

I cannot get it to connect to a Full Node Apollo nor to my Ubuntu laptop.

It seems to make contact on the USB cable:

Code:

/Apollo/Apollo-Standard_software/linux-x86_64$ ls /dev/ttyACM*
/dev/ttyACM0

When I unplug it, I get this:

Code:

Apollo-Standard_software/linux-x86_64$ ls /dev/ttyACM*
ls: cannot access '/dev/ttyACM*': No such file or directory

And it re-app[ears when I plug the USB cable back in.

But when I use my familiar

Code:

/Apollo-Standard_software/linux-x86_64$ ./start_Poll-i-i-i_Turbo_60-80C-Fan_Quiet_20221219_ACM0.sh

then this happens:

Code:

80 0 0 0.0% 0 0 0 0.0% 0 0 0 0

Total packets: 80 in 40000 ms, speed: 2.00 packets/sec
Exporting stat... >>> Waiting for USB /dev/ttyACM0 [80] !!!
>>> Waiting for USB /dev/ttyACM0 [81] !!!
>>> Waiting for USB /dev/ttyACM0 [82] !!!
>>> Waiting for USB /dev/ttyACM0 [83] !!!
>>> Waiting for USB /dev/ttyACM0 [84] !!!
>>> Waiting for USB /dev/ttyACM0 [85] !!!
>>> Waiting for USB /dev/ttyACM0 [86] !!!
>>> Waiting for USB /dev/ttyACM0 [87] !!!
>>> Waiting for USB /dev/ttyACM0 [88] !!!
>>> Waiting for USB /dev/ttyACM0 [89] !!!
>>> Waiting for USB /dev/ttyACM0 [90] !!!
>>> Waiting for USB /dev/ttyACM0 [91] !!!
>>> Waiting for USB /dev/

I have rebooted all and sundry a few times and I have tried 2 different cables.

Any ideas what is going wrong here, anyone?

Added:
For some reason beyond my understanding, this malfunctioning Standard Apollo connects to and hashes for a Full Package Apollo again, but it still will not work when connected to my laptop in the same way that it used to work before it started to play up.

Here is what happens on starting up (some Xxx edited for privacy):

Code:

./start_Poll-i-i-i_Turbo_60-80C-Fan_Quiet_20221219_ACM0.sh
apollo-miner 09bb0bf 2021-11-22, msp ver 0xd166
Use "--help" switch to print command line options.

Global tracing is OFF.
Init env
Init slave MCU
Starting Xxx Pool...
Pool: Xxxx.com:3333 (user Xxx.Xxx)

Enter main cycle.
Xxx Pool started.
Initial difficulty: 1024EVENT: 2022-12-20 06:22:51 ::: MINER_START ::: Enjoy your mining!

Connecting to Xxx.com:3333...
>>> Waiting for USB /dev/ttyACM0 [0] !!!
Connection successful
>>> Waiting for USB /dev/ttyACM0 [1] !!!
Server setup for us extranonce1: 0165060017c7bd
Server setup for us size of extranonce2: 8
Pool changed difficulty to 8192
EVENT: 2022-12-20 06:22:52 ::: DIFF_CHANGE ::: Difficulty changed: 1024 => 8192
EVENT: 2022-12-20 06:22:52 ::: POOL_CLEAN_JOB ::: jobIdCounter = 100, JOB: jobName: 194376dc4, prevHash: ea02daed48bb1b12c12e57cef084598923d4eb77000512ff0000000000000000, nTime: 0x63a0c81c, cleanJobs: 1
Queued job 101 [194376dc4], job count = 1
>>> Waiting for USB /dev/ttyACM0 [2] !!!
Authorization succeeded.
Pool in-service, we can send shares!
EVENT: 2022-12-20 06:22:52 ::: POOL_INFO ::: Pool in-service
>>> Waiting for USB /dev/ttyACM0 [3] !!!
>>> Waiting for USB /dev/ttyACM0 [4] !!!
>>> Waiting for USB /dev/ttyACM0 [5] !!!
>>> Waiting for USB /dev/ttyACM0 [6] !!!
>>> Waiting for USB /dev/ttyACM0 [7] !!!
>>> Waiting for USB /dev/ttyACM0 [8] !!!
>>> Waiting for USB /dev/ttyACM0 [9] !!!
>>> Waiting for USB /dev/ttyACM0 [10] !!!
>>> Waiting for USB /dev/ttyACM0 [11] !!!
>>> Waiting for USB /dev/ttyACM0 [12] !!!
>>> Waiting for USB /dev/ttyACM0 [13] !!!
>>> Waiting for USB /dev/ttyACM0 [14] !!!
>>> Waiting for USB /dev/ttyACM0 [15] !!!
>>> Waiting for USB /dev/ttyACM0 [16] !!!
>>> Waiting for USB /dev/ttyACM0 [17] !!!
>>> Waiting for USB /dev/ttyACM0 [18] !!!
>>> Waiting for USB /dev/ttyACM0 [19] !!!
------------------------------------------------------------
----- STATISTIC -----
------------------------------------------------------------
*** MASTER STATS PER INTERVAL:
INTERVAL sec bySol byDiff byPool byJobs CHIP GHs W/GHs SOL ERR ERR(%) CR
  30 sec 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
   5 min 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
  15 min 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
  1 hour 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
   total 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0

*** MASTER STATS:
Date: 2022-12-20 06:23:01, UpTime: 10 secs, mbHwVer: 0x0, osc: 50
Smooth osc: step: 1, ignore broken pwc: 0
Found boards: 0
Broken SPI: 0

*** POOL STATS:
Pool: host:port: Xxx.com:3333, user: Xxx.Xxx, diff: 8192, reconnects: 1
extraNonce1: 0165060017c7bd, extraNonce2Size: 8, jobs: 1, rollingEnabled: 0, rollingMask: 00000000
INTERVAL sec JOBS clean SHARES ok err POOL sol minRespT avgRespT maxRespT loss INSERVICE %
  30 sec 10s 1 1 0 0 0 0 0 0 0 0.0% 9s 89.4%
   5 min 10s 1 1 0 0 0 0 0 0 0 0.0% 9s 89.4%
  15 min 10s 1 1 0 0 0 0 0 0 0 0.0% 9s 89.4%
  1 hour 10s 1 1 0 0 0 0 0 0 0 0.0% 9s 89.4%
   total 10s 1 1 0 0 0 0 0 0 0 0.0% 9s 89.4%

*** EVENT STATS:
Legend: SE - subbsribe error (initialising issue)
   DIFF - diff changes, REC - reconnects, RECE - reconnects on error
   SHARES - sent to pool, PSS - pwc shares sent, PSD - pwc shares dropped
   DJS - default job shares, SJS - stale job shares, DUP - duplicates, LDS - low diff shares
   BDS - big diff shares, BTS - below target shares, PR - pwc restart, SO - stat overflow
INTERVAL sec SE DIFF REC RECE SHARES PSS PSD DJS SJS DUP LDS BDS BTS PR SO
  30 sec 10s 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
   5 min 10s 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
  15 min 10s 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
  1 hour 10s 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
   total 10s 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0

FAN INFO:
Slave RPM
   0 0

Temp(C) (min/avr/max): 0 / 0 / 0

*** MASTER-SLAVE SPI BUS STATS:
SLAVE UID B-LEN B-CRC-C B-CRC-L VER TIME PING M=>S rx err % S=>M rx err % SS SD Rst LastRstT Packets Time msec. Speed(pack./sec)
   0 000000000000000000000000 0 00000000 00000000 0x00000000 0 666666 20 0 0 0.0% 0 0 0 0.0% 0 0 0 0

Total packets: 20 in 10001 ms, speed: 2.00 packets/sec
Exporting stat... >>> Waiting for USB /dev/ttyACM0 [20] !!!
>>> Waiting for USB /dev/ttyACM0 [21] !!!
>>> Waiting for USB /dev/ttyACM0 [22] !!!
>>> Waiting for USB /dev/ttyACM0 [23] !!!
>>> Waiting for USB /dev/ttyACM0 [24] !!!
>>> Waiting for USB /dev/ttyACM0 [25] !!!
>>> Waiting for USB /dev/ttyACM0 [26] !!!
>>> Waiting for USB /dev/ttyACM0 [27] !!!
>>> Waiting for USB /dev/ttyACM0 [28] !!!
>>> Waiting for USB /dev/ttyACM0 [29] !!!
>>> Waiting for USB /dev/ttyACM0 [30] !!!
>>> Waiting for USB /dev/ttyACM0 [31] !!!
>>> Waiting for USB /dev/ttyACM0 [32] !!!
>>> Waiting for USB /dev/ttyACM0 [33] !!!
>>> Waiting for USB /dev/ttyACM0 [34] !!!
>>> Waiting for USB /dev/ttyACM0 [35] !!!
>>> Waiting for USB /dev/ttyACM0 [36] !!!
>>> Waiting for USB /dev/ttyACM0 [37] !!!
>>> Waiting for USB /dev/ttyACM0 [38] !!!
>>> Waiting for USB /dev/ttyACM0 [39] !!!
------------------------------------------------------------
----- STATISTIC -----
------------------------------------------------------------
*** MASTER STATS PER INTERVAL:
INTERVAL sec bySol byDiff byPool byJobs CHIP GHs W/GHs SOL ERR ERR(%) CR
  30 sec 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
   5 min 20s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
  15 min 20s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
  1 hour 20s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
   total 20s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0

THIS CONTINUES FOR A FEW MINUTES AND THEN ENDS WITH:

>>> Waiting for USB /dev/ttyACM0 [177] !!!
>>> Waiting for USB /dev/ttyACM0 [178] !!!
>>> Waiting for USB /dev/ttyACM0 [179] !!!
------------------------------------------------------------
----- STATISTIC -----
------------------------------------------------------------
*** MASTER STATS PER INTERVAL:
INTERVAL sec bySol byDiff byPool byJobs CHIP GHs W/GHs SOL ERR ERR(%) CR
  30 sec 10s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
   5 min 90s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
  15 min 90s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
  1 hour 90s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0
   total 90s 0.0 0.0 0.0 0.0 0.00 0.000 0 0 0.0% 0

*** MASTER STATS:
Date: 2022-12-20 06:24:22, UpTime: 90 secs, mbHwVer: 0x0, osc: 50
Smooth osc: step: 1, ignore broken pwc: 0
Found boards: 0
Broken SPI: 0

*** POOL STATS:
Pool: host:port: Xxx.com:3333, user: Xxx.Xxx, diff: 1638, reconnects: 1
extraNonce1: 0165060017c7bd, extraNonce2Size: 8, jobs: 2, rollingEnabled: 0, rollingMask: 00000000
INTERVAL sec JOBS clean SHARES ok err POOL sol minRespT avgRespT maxRespT loss INSERVICE %
  30 sec 10s 1 0 0 0 0 0 0 0 0 0.0% 10s 100.0%
   5 min 90s 4 2 0 0 0 0 0 0 0 0.0% 89s 98.8%
  15 min 90s 4 2 0 0 0 0 0 0 0 0.0% 89s 98.8%
  1 hour 90s 4 2 0 0 0 0 0 0 0 0.0% 89s 98.8%
   total 90s 4 2 0 0 0 0 0 0 0 0.0% 89s 98.8%

*** EVENT STATS:
Legend: SE - subbsribe error (initialising issue)
   DIFF - diff changes, REC - reconnects, RECE - reconnects on error
   SHARES - sent to pool, PSS - pwc shares sent, PSD - pwc shares dropped
   DJS - default job shares, SJS - stale job shares, DUP - duplicates, LDS - low diff shares
   BDS - big diff shares, BTS - below target shares, PR - pwc restart, SO - stat overflow
INTERVAL sec SE DIFF REC RECE SHARES PSS PSD DJS SJS DUP LDS BDS BTS PR SO
  30 sec 10s 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
   5 min 90s 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0
  15 min 90s 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0
  1 hour 90s 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0
   total 90s 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0

FAN INFO:
Slave RPM
   0 0

Temp(C) (min/avr/max): 0 / 0 / 0

*** MASTER-SLAVE SPI BUS STATS:
SLAVE UID B-LEN B-CRC-C B-CRC-L VER TIME PING M=>S rx err % S=>M rx err % SS SD Rst LastRstT Packets Time msec. Speed(pack./sec)
   0 000000000000000000000000 0 00000000 00000000 0x00000000 0 666666 180 0 0 0.0% 0 0 0 0.0% 0 0 0 0

Total packets: 180 in 90001 ms, speed: 2.00 packets/sec
Exporting stat... ERROR: Unknown error.
Disconnected from pool.
EVENT: 2022-12-20 06:24:22 ::: RECONNECTION :::

quickmr2

newbie

Activity: 15

Merit: 0

Quote from: n0nce on December 16, 2022, 07:29:32 PM

Quote from: quickmr2 on December 16, 2022, 07:12:45 PM

why isn't my node connecting to any other nodes? Had a power outage and had to reflash on the sd card now no connections.

If you got a power loss, the blockchain files may have been corrupted and are now reindexing.

Do you have no connections to other nodes or no connection to your Apollo? Your question is pretty vague. Try to give as many details as you can to get the best help possible.

I have no connections to other nodes.

I can connect to my miner.

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: quickmr2 on December 16, 2022, 07:12:45 PM

why isn't my node connecting to any other nodes? Had a power outage and had to reflash on the sd card now no connections.

If you got a power loss, the blockchain files may have been corrupted and are now reindexing.

Do you have no connections to other nodes or no connection to your Apollo? Your question is pretty vague. Try to give as many details as you can to get the best help possible.

Sledge0001

full member

Activity: 626

Merit: 159

Quote from: quickmr2 on December 16, 2022, 07:12:45 PM

why isn't my node connecting to any other nodes? Had a power outage and had to reflash on the sd card now no connections.

Maybe your devices IP address changed on your local network. If it did the port forwarding IP needs to be updated on your firewall/router to allow the port to route correctly the devices internal ip.

Just a guess

quickmr2

newbie

Activity: 15

Merit: 0

why isn't my node connecting to any other nodes? Had a power outage and had to reflash on the sd card now no connections.

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: MrMik on December 14, 2022, 04:49:12 PM

No matter what search terms I use, the search results seem to show that everyone wants to run their miners as hard as possible to break them before the warranty runs out and before more efficient machines turn the miner into an outdated money pit.

The 'strategy' varies a lot depending on the chip, the device the chip is in, and the financial situation & intentions of the miner (including price of electricity).

Some industrial ASIC miners actually need some heat to get started & if you cool them too much, they won't work, or won't work efficiently.
Others, like apparently the Bitfury chips used here, shouldn't run too hot to prevent damage.

Quote from: MrMik on December 14, 2022, 04:49:12 PM

How can one maximise TH/s x Total-life-running-time ?
Or in other words, at what temperature will the miner likely produce the highest number of hashes across its lifetime?

To my knowledge, this can vary a lot; so there is no general answer, and you'd need an answer from Futurebit or Bitfury.

MrMik

member

Activity: 203

Merit: 37

Quote from: jstefanop on December 13, 2022, 01:25:31 PM

Just watch your temps, running at 100% board power with high temps (over 70-75c) will significantly reduce the lifespan.

Thanks for bringing that up, it is a question I have not been able to answer by Duck-ducking, so far: How much does heat reduce the lifespan of a miner?

No matter what search terms I use, the search results seem to show that everyone wants to run their miners as hard as possible to break them before the warranty runs out and before more efficient machines turn the miner into an outdated money pit.

But I want my miners to run for as many years as possible, with free electricity.

There must be some sort of curve for temperature vs expected time to failure, that would help to estimate at which temperature to pick a sweet spot.

How can one maximise TH/s x Total-life-running-time ?

Or in other words, at what temperature will the miner likely produce the highest number of hashes across its lifetime?

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: MrMik on December 09, 2022, 09:13:42 PM

I used -brd_ocp 95 rather than -brd_ocp 100 because that seems to be the maximum setting possible in the GUI of the Full Package Apollo. It reports that it is using 266W with that setting.

Would there be anything wrong with cranking it up to -brd_ocp 100 ?

Not if you're using an external power supply. Limitation is there for the stock 200W PSU since we need overhead for the controller and fan power.

Just watch your temps, running at 100% board power with high temps (over 70-75c) will significantly reduce the lifespan.

MrMik

member

Activity: 203

Merit: 37

Quote from: itskeule on December 10, 2022, 01:10:21 AM

Quote from: MrMik on December 09, 2022, 09:32:42 PM

I have a question about using 2 PSU's on a single Apollo miner:

Now that I have a spare original 200W Apollo PSU, could I plug 2 of these PSU's into a single Apollo, with one cable each?

Or is that asking for trouble?

In the first post of this thread there is a warning in Bold red:

WARNING: Always make sure both PCIE plugs are plugged into the Apollo, even if you are using your own PSU
NEVER Plug in two separate power supplies into the same Apollo THIS IS A FIRE HAZARD

https://bitcointalksearch.org/topic/m.57091049

Cheers, I thought I had seen something like that, somewhere... Grin

itskeule

newbie

Activity: 14

Merit: 4

Quote from: MrMik on December 09, 2022, 09:32:42 PM

I have a question about using 2 PSU's on a single Apollo miner:

Now that I have a spare original 200W Apollo PSU, could I plug 2 of these PSU's into a single Apollo, with one cable each?

Or is that asking for trouble?

In the first post of this thread there is a warning in Bold red:

WARNING: Always make sure both PCIE plugs are plugged into the Apollo, even if you are using your own PSU
NEVER Plug in two separate power supplies into the same Apollo THIS IS A FIRE HAZARD

https://bitcointalksearch.org/topic/m.57091049

MrMik

member

Activity: 203

Merit: 37

I have a question about using 2 PSU's on a single Apollo miner:

Now that I have a spare original 200W Apollo PSU, could I plug 2 of these PSU's into a single Apollo, with one cable each?

Or is that asking for trouble?

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on December 09, 2022, 02:33:08 PM

One Apollo draws between 250W and 300W, so you should use 2 (8-pin!) cables per hashboard and a 750W-900W PSU.
Unfortunately, it appears to me that your PSU model only has 3 8-pin connectors, so even if its power rating is enough for 2 Apollos, you may physically only be able to power a single one off this power supply.

I would honestly recommend to get something like the Seasonic Prime GX 1000W; that comes with 6 PCIe cables, so all ready to go to power 3 Apollos.

Looks like this is a good PSU for a single Apollo then. I will run at about 50% of it's capacity when cranking the Apollo to max power, which means the PSU is then running in it's optimum efficiency band.

Also, I prefer to have one PSU for each miner, so that I can be flexible about where and how I run them. From extremely quiet to maxed out for most Sats mined.

I will design a spacer to place this PSU underneath the Apollo without restricting air flow.

Now I can run the Apollo (in 26C air temp) using

Code:

-brd_ocp 95 -osc 50 -ao_mode 1 -fan_temp_low 40 -fan_temp_hi 60 -fan_pwm_low 1 -fan_pwm_hi 100

for noisy operation (fan at 4800rpm, ASIC temp 59C),

or

Code:

-brd_ocp 95 -osc 50 -ao_mode 1 -fan_temp_low 65 -fan_temp_hi 70 -fan_pwm_low 1 -fan_pwm_hi 100

for higher power mining with noise level not much different from standard Turbo mode noise levels (fan at 2980rpm, ASIC temp 65C)

Code:

*** MASTER STATS PER INTERVAL:
INTERVAL sec bySol byDiff byPool byJobs CHIP GHs W/GHs SOL ERR ERR(%) CR
30 sec 10s 3470.4 3588.0 3588.0 3603.8 78.87 0.076 8080 81 1.0% 9
5 min 101s 3512.6 3374.9 3197.3 3565.2 79.83 0.075 82601 891 1.1% 53
15 min 303s 3513.1 2901.2 2842.0 3567.9 79.84 0.075 247839 2707 1.1% 141
1 hour 1214s 3517.4 3635.3 3620.6 3566.4 79.94 0.075 994195 11204 1.1% 548
total 4756s 3510.2 3557.5 3542.4 3560.4 79.78 0.075 3886937 44494 1.1% 2128

I used -brd_ocp 95 rather than -brd_ocp 100 because that seems to be the maximum setting possible in the GUI of the Full Package Apollo. It reports that it is using 266W with that setting.

Would there be anything wrong with cranking it up to -brd_ocp 100 ?

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: MrMik on December 09, 2022, 07:24:53 AM

12.5A x 12V x 3 positive cables = 450W per 6-pin PCIe connector maximum??? Meaning one of the PCIe cables could provide double the power required to run one Apollo in Turbo mode???

No, that's wrong. One 'cable' is a whole 8-pin cable. That would be 150W per 6-pin PCIe connector.
The Apollo has two such connectors, allowing for up to 300W power draw (safely).

Quote from: MrMik on December 09, 2022, 07:24:53 AM

12v x 58A combined max at +12V = 696W ; meaning that it could run 3 Apollos mining in turbo mode, each connected to one of the three PCIe/CPU 8-pin outlets???

One Apollo draws between 250W and 300W, so you should use 2 (8-pin!) cables per hashboard and a 750W-900W PSU.
Unfortunately, it appears to me that your PSU model only has 3 8-pin connectors, so even if its power rating is enough for 2 Apollos, you may physically only be able to power a single one off this power supply.

I would honestly recommend to get something like the Seasonic Prime GX 1000W; that comes with 6 PCIe cables, so all ready to go to power 3 Apollos.

100knot2dae

member

Activity: 100

Merit: 29

Quote from: MrMik on December 09, 2022, 07:24:53 AM

Is my assessment correct when I say that I could run a maximum of 3 Apollos in Turbo mode on this power supply?

12.5A x 12V x 3 positive cables = 450W per 6-pin PCIe connector maximum??? Meaning one of the PCIe cables could provide double the power required to run one Apollo in Turbo mode???

12v x 58A combined max at +12V = 696W ; meaning that it could run 3 Apollos mining in turbo mode, each connected to one of the three PCIe/CPU 8-pin outlets???

I would definitely not run more than two units on this PSU. This is a 700W PC PSU, which is not intended to run maxxed out 24/7, otherwise you risk an early breakdown or even more! As per the PCI-E connector spec, you must not draw more than 12.5A per connector (due the internal wire gauge)! So connect one Apollo unit to two PCI-E connectors, and the other one to a PCI-E connector and a Molex connector (with a seperate PCI-E to Molex adapter attached).
Better safe than sorry

MrMik

member

Activity: 203

Merit: 37

Polli is now Turbo-purring quietly (enough for now) and I can get started on learning how to program it while sitting next to it.

Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 42. (Read 48695 times)