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

Yes, that is correct, the node will not run and I can not tell if its syncing still or there are some issues.

I tried start node several times even restart.

CPU, Temp and other specs look fine.

https://ibb.co/GHNPFtv
https://ibb.co/ZYDFw5f

How can I get more stats about the node?

According to your screenshot your node isn't even running. You need to click the button at the top of the screen that say's "Start Node" or simply reboot the system and it will start syncing the node automatically. Either way, it takes a long time to load/sync a full unpruned node. It took me about 7-8 days with a few other bandwidth priorities sharing my internet. And don't try to mine higher than "Eco Mode" while your syncing your node because it will really stress your CPU on the Apollo. Just my 2 cents. There's a decent "getting started" manual supplied by Futurebit on the Apollo 2 that covers some of these issues: https://www.futurebit.io/apollo-btc-support
Cheers!

It has been 7 days since I got my Apollo 2 and the node is still not synced.

I have gigabit internet connection
using ethernet cable as connection
port forwarding for 8333 and 3333
ip reserved in my router
mining on ckpool on Medium settings

How long does it take for the Node to sync? How can I check how much of the blockchain has been downloaded?

https://ibb.co/0KrVmQw
Apollo Web OS v2.0.5

Thank you for your reply. I'll switch to solo on my Apollo II. It only takes legacy addresses? It sees segwit and taproot addresses as invalid but I used it (with the worker name) on solo.ckpool.org itself and on public-pool.io without problems. I also got the ckpool disconnected message. Also no ckpool screen process running. I switched back to public-pool for now.

Yes you can point your other miners to the apollo and mine to the solo ckpool built in.

I have successfully stress tested just over 10PH to the ck pool built in to the Apollo II.

If your miners are located on your (LAN) internal network then just use the IP address of the Apollo II.

The IP address which you need to setup other local miners on your LAN should be listed on the top of the solo mining page within the Apollo GUI.
****
SOLO LAN Mining
Point any Bitcoin Miner on your local network to your Solo Pool with the following URL: 192.168.X.X:3333 Username:
****

If your other miners are outside your LAN then you must either have a static IP or use DDNS so that you can always find the PUBLIC IP address (WAN).
Additionally you must then set port forwarding of port 3333 to the internal IP of your Apollo II so that it can pass traffic through your router / firewall.

Hi,
Just a question about solo mining. From what I gather, it's running a local solo ckpool instance? If so, can I point other miners to it? I am now mining on public-pool.io but wondering if I should instead mine to the Apollo II itself. Is it possible to add a backup pool?
Thanks for your replies.

Another one of my old Apollo BTC units is doing strange stuff.

It does not have  a SBC and is connected to another Apollo by USB cable, started with a terminal command.

This Apollo will only sometimes hash at the requested power level, at other times it seems to be stuck doing about half as much work as it should. This is confirmed by on-the-wall power measurement and by what hashes arrive at the mining pool over time.

Once it's in that lazy mode, it stays that way even after several reboots and when using the same command from the memory of the terminal.

In this 'lazy mode' it shows this:
*** BOARDS SYS INFO (1 boards, 44 chips):
BRD  FOUND      REV   SPI     PWR  CHIPS  ON  ON_T  inOhOsc  OhOscN  OhOscT  OhN  OhT  loI  Tc  Th    T, C              TA  RevADC   OCP     HE  osc  OSChip               U, mV               I, mA  P, Wt
  0      1  BREV:20  1x 4  2x2x11     44   1     1        0       0       0    0    0    0   0   0   41  0    0( 0)  0( 0)    4004  0x00  0 (0)    0  0:3:10   U0: 9863 U1: 1302   I0:12983 I1:12975    144


after having been started with these settings:

./apollo-miner -host... -port.... -user..... -password.....  -comport /dev/ttyACM0 -brd_ocp 80  -osc 50 -ao_mode 1 -fan_temp_low 65 -fan_temp_hi 70 -fan_pwm_low 1 -fan_pwm_hi 100

I'm heating the bedroom with that Apollo, and I'd like it to churn through around 250W.

It has a large aftermarket PSU and a 200mm fan and a different 80mm fan that spins slower than the original, is therefore very quiet, but now also very low hashrate and very low heating.

Should I do any maintenance cleaning of my Apollo II and if yes then how often and what are the steps?

Hoping for info on if there is an updated timeframe on the new v 2.0.6 software?

Hi,

A quick sanity check  "for solo mining" on a BTC 1 and BTC 2 (full nodes).

I have historically operated a full Bitcoin Core node "Windows Server" that I have used for transactions over the last 10 years

On the Apollo BTC 1/2 do I just enter the Bitcoin Core full node "Windows Server" receive address
in the Apollo BTC wallet address.

Sorry for the noob question but I'm just checking.

That worked great. Looking forward to the update though too.
Thank you!

Yep had a bad batch of power switches that are failing for small number of units, just reply to your order email and they'll setup and RMA to have it replaced.

I typically see 72-73c while running in balanced mode, and when I tried turbo mode for a few hours, it peaked at 79. I've just been using balanced mode for the better efficiency and lower noise. Thanks for the information.

I have an issue with one of my units randomly powering off. When it happens, the power switch light turns off, but if you tap the power button (not flipping the switch), the power comes back and the light turns on. I noticed if I just tap the power button while it's running (again, not flipping the switch), the power goes off and on. I'm assuming there is a defect in the power supply. Do I just submit for an RMA to have it replaced, or what is the best course of action?

Max PCB temps should be under 80c, the silicon in our ASICS can handle 95+

PCB autocuts power once temps go over 83c in case there is something wrong with the fan/controller...we have mutiple failsafes on these and cut no corners since these are run in homes.

With that said running in turbo mode or max currents on any electronic device will shorten its lifespan.

It's just a front end bug nothing in the backend/solo/mining is affected.

Hoping to get 2.0.6 out in the next week or so to address this.

If your logged in via monitor or know how to ssh below commands will bring up the backend services/logs

sudo screen -dr miner  //miner stats
screen -dr node          //node stats (as long as you see getblocktemplate messages your solo mining)
screen -dr ckpool       //solo pool stats

Agreed, I see what you mean. With the exception of my Apollo II's most of my equipment is older and has seen better days. It very well could be I'm suffering the effects from earlier overheating and causing reduced heat thresholds on the older stuff? Just guessing. In any case, I did start to experience hash board issues such as lock-ups on the A2's at 75.5c - 76c so I've tried to keep'em a little cooler.

I appreciate the input. I understand this works for you, but it doesn't actually tell me the specifics of the PCB max or Chip max temp, which I'd like to know. You must understand that 73 is quite cool for some silicon, such as current AMD processors (95) and most ASICs, and frequently ASICs go much higher than general purpose CPUs.

BITMAIN publishes data for their miners showing PCB max values in a range from 75 to 95, with Chip max values up to 135.
https://support.bitmain.com/hc/en-us/articles/360005088914-Miner-Normal-Operating-Temperature-Range

What are you all using to monitor your solo node?  I've been keeping the stats page up via web GUI, but with the frequent SQL crashes, I end up rebooting every other day.
If the SQL bug doesn't actually take the node down, I don't mind leaving it that way but wasn't sure what else I could to do see that it's up and running.

As with most of my miners and other computer related circuit boards, my personal experience has shown the upper limits to be an average of 74c. Anything higher and I start seeing erratic behavior including lock-ups and shutdowns. Operating higher than 74c-75c and you run the risk of damaging your equipment or at the very least shortening it's lifespan considerably. My personal preference is to keep everything in the range of 67c-72c with short term spike limits of 73c. This works for me.

No, Apollo doesn't have any firewall or anything which would prevent you from accessing. Issue must be somewhere else, miner or SD card is dying, for example.
Try connecting keyboard mouse and monitor, with output in the terminal, to watch what happens when miner go offline.