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

While I do not own one should be safe to assume there are 44 chips per-hashboard. Each chip has hundreds of cores in it. Even the A1 chip from 2014 had 256 cores per-chip and no doubt jstefanop can tell folks how many are in chip. Along that line, who's and what chip is used?

And yes, it is not uncommon for not all cores in a chip to not work though it should at worst be just a few dead cores. That said, most chips should have 100% functional cores.

I am not the one with the issue, but I don't fully understand what you're saying. One hashboard has 44 cores (thousands? where does that number come from?  ). If one of them has 70% bad solutions, that's what will be reported for the whole hashboard in the GUI? So just the core with the highest error rate is reported, is what you're saying?

No how error rate is being reported is a little deceptive right now. It counts all bad solutions coming from a core even if one core is bad out of the thousands of cores inside one ASIC (ie producing 100% bad solutions). This causes the error rate to be higher than it really is. Error rate is there to find bad solutions due to low voltage for tuning purposes. We should be filtering out bad cores but this is complicated to do in practice.

For now its better to look at your hashrate, ie if your hashrate is 70% lower than your other units then your unit is really defective, if hashrate matches your good which is what your seeing. This only affect a very small number of units. 

If you haven't done yet, try unplugging the good unit and only let the one with the 70% error rate stay connected to the node. If the faulty board is hashing good now, it's likely a power supply issue.
You could also try swapping USB cables and/or switch the ports on the node vice versa between the units. Principle of exclusion always helps to pinpoint the problem.

If nothing helps, it may be a hardware or manufacturing issue. In that case, best contact the futurebit customer support.

Posted earlier about instability issues in balanced and a high error rate.  

Screenshot from my dashboard today.  The one with the ~70% error rate is also the one that fails.  It has consistently been that unit, and the error rate has remained consistently around that.

Is this a defective unit or something I can fix?

https://i.postimg.cc/jjG8XkL4/Screenshot-20210829-062730-2.png

Hey there, LN node operator here! Don't expect to make any significant amount of money from routing LN payments.

I am quite sure you can install lnd or c-lightning on the Apollo (don't have mine yet), and you should definitely do it, it always helps! But payments are meant to be cheap, so users usually pay 1 satoshi per hop, some node operators even run their nodes fee-less.

A payment takes a max. of 10 hops in my experience, so you're looking at 'locking in' millions of satoshis in channels just to gain a few (single-digit amounts we're talking about) satoshis in fees. So you won't really 'earn BTC' - you'd earn more Bitcoin working 1hr as a waiter and buying BTC with the money you got there  (rough calculation: 10$ ~ 20KSat)

For Question #5 What can we do with our Node?
Can we choose to designate our Node into a Lightning Network Node?
This will help us earn extra BTC and Devs can take a fee from it.

For anyone experiencing issues connecting to pools, this info might help...

If, in your house you happen to own an ASUS wifi router/firewall, check and see if your model has a feature called 'Two-Way IPS' - which is part of the firewall and packet filtering settings and if you do, try disabling it.

I run an ASUS GT-AX11000 Router - one of their high end gaming routers and evidently the 'Two-Way IPS' logic inside the router was blocking the connection to slushpool. Of course there was NOTHING in the firewall's network protection dashboard that indicated this to be the case, but as soon as I disabled 'two-way IPS' the miner worked.

The background on this is as follows... I was pulling my hair out for two weeks or more trying to understand why I couldn't connect to any pool and then tried testing it using a VPN and discovered the connections were successful if using a VPN.

Since I knew that running the miner inside a VPN tunnel works, the question is, what is not 'seeing' the traffic due to the VPN? - Well, Comcast isn't seeing it, that's true and my ISP was what I was afraid was causing the issue. But with the VPN in use, the port filtering on my firewall/router ALSO isn't seeing traffic to e.g. slushpool, and that's why subsequent connection attempts worked. Turns out it wasn't Comcast, it was my firewall.

Turns out other miners also have experienced this issue. Check this old post on Reddit:  https://www.reddit.com/r/MoneroMining/comments/m1g0y1/cannot_reach_any_pool_without_tls/

Any off the shelf ATX PSU (sized appropriately) should work fine. You just need to be aware that for the PSU to power itself up when the power switch is moved to the ON position requires you to jump two pins on the 24-PIN motherboard cable. This of course means that in addition to the PCIe power cables, if it's a modular PSU you also need to connect the 24-pin cable to the PSU.

reference:  https://www.instructables.com/How-to-power-up-an-ATX-Power-Supply-without-a-PC/

-good luck!

Questions:

1. How many Standard (hashboard only) units can be managed from the Full package (controller) unit? I already have one full package unit which I ordered in Batch 1, and have two standard hashboard-only units on order from Batch 2. I want to know if I could manage a third standard unit from my existing controller unit, or is two the maximum?

2. I am currently using the Futurebit PSU in Turbo mode. Is there a significant advantage to upgrading the PSU to achieve 3.8Th/s or does running the Apollo BTC at this level dramatically reduce their lifespan, and cause them to overheat?

3. On the basis that the answer to question 2 is Yes, can anyone recomend a PSU that can power three Apollo BTC devices (one full package unit and two hashboard-only units)?

4. Is there any news when the Batch 2 Units will reach Europe?

Thanks in advance.

This is no longer an issue since 0.3.1

Yea reflash the sd card with a new image. Take out the m.2 drive until after the first boot otherwise you will restnc the whole blockchain. After first boot shut it down put the m.2 back in then start it up.

So I accidently update the desktop OS and now my apollo won't boot. If I reflash an SD disk, will that solve the problem?

Thanks for reply.

Can you at least compile binary for Raspberry Pi zero? It shouldn't take longer than 10 minutes to post it to github.

Re: power rating - I mentioned '80+ Gold' and no wattage because I meant the percentage at which such a PSU should maximally be loaded in 24/7 scenario. You said 80%, thanks for that!

But bottom line: 2 Apollos is 400W if they run at the normal mode, 73% of the capacity, why should I get a higher wattage PSU?

And Futurebit PSU's should also not run at 100% in 24/7 or are they made for it? I would assume they're made for it since they come bundled with it, but I might be wrong, after all they're only 200W unfortunately.

No PSU should be loaded to more than 80% of its max rating 24x7. For that matter that 80% rule applies to all power devices and the circuits feeding them.

is a useless description without saying what the power rating of it is. ATX is a physical form design the PSU is built to as a 'universal' device. It also includes the specs of all voltages it produces and the connectors it has. It has nothing to do with its power output ratings.

As for Seasonic saying their PSU's have what is better called a reserve capacity that can be called on for short times does not mean you can run them at full load 24x7.

In short - to run multiple miners get a higher wattage PSU!

I'm wondering: you said you were running an ATX PSU yourself as well for your Apollos, but also saying that they're not made to do 24/7 loaded. What would you say (roughly) is a good upper limit to run a good 80 PLUS Gold (or higher) ATX PSU at 24/7 workloads like mining?

Also, I heard especially Seasonic executives mention that their PSUs go easily above the specified wattage. So, should a Seasonic 550W 80+ GOLD work fine with 2 Apollos? I mean specced, it should only pull 400W total. I preordered one batch 3 Apollo and looking to add a second Apollo hashboard or maybe some Compac F's or so.

Thanks for the feedback.  This was my first time playing with a PSU. I shot for a 25% over 200x3 with the 750s but sounds like the 850 would be a better choice.

These are running in balanced (160x3) and I have no intention of running Turbo anytime soon.

1)  Multiple pools arent available yet but I think the dev team are working on it.

2) No Donation option.

3) The SBC in the Full Unit is an Orange Pi but not sure what flavour of OS its running but I'm sure you could install it. From what I've seen the Dashboard runs through firefox so if you have a viewer installed it should show you that.

4) Node will store all data upto the point at which it was turned off. Then once powered on again it will update from the last known block. So the longer its off the longer it will take to update.

5) Node is just there to help the network for now. I think jstefanop has said you can use various apps etc to utilise the node but not sure how to do any of that myself.