One hashboard has 44 cores (thousands? where does that number come from? 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 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. Right, right, it's confusing since the website says 44 ASIC cores  Still confused about how a few dead cores result in a number of 70% 'error rate' in GUI, somehow the given explanation didn't clear it up much for me at least. Each of our ASICs have ~4k SHA256 engines in them (so ~175k in each Apollo). Only one of these need to be bad to throw a really high error rate. Error rate is calculated against good solutions based on an internal solution difficulty, not ALL solutions produced by the ASIC (would be impossible/waste of resources to do integrity check on each SHA256 pass). What happens with a bad logical core is that ALL solutions it produces are spit out as valid solutions, then the miner software does a check on them which are determined to be bad solutions, so the calculated error rates ends up inflating higher than it really is. Normally each core produces an random amount of error that just has to do with spontaneous logical errors that happen in the chip due to low gate voltage, this is what the error rate is supposed to convey, but we cant easily catch the kind of errors that have to do with a bad logical cores. Hope that explains it a bit. |
|
|
|
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?  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. |
|
|
|
Hi,
I haven't received any reply, so asking again:
Any news on standalone apollo-miner binary? It's been now 3 months since the release. Miner binary crashes a lot for everyone. GUI full package uses the same binary, so problems exist for everyone. Also miner not stopping mining and using power full power when no connection to the pool, it should be idling. Furthermore, Mining Rig rentals pool is not supported, because of "::: ROLLING_MASK ::: Not supported" error (cgminer works just fine). These two problems have been reported on github, but has not been acknowledged. For standalone miner users, Raspberry Pi binaries were promised, still no sight of it. I can't use Apollo miner on perfectly fine and supported (by manufacturer) Raspberry Pi 1, zero, and other devices.
I know GUI is important, but no reason to delay fundamental part of Apollo which is miner software?
When can we expect update to apollo-miner? Thanks.
Considering that your request is getting constantly ignored, along with other feature requests like solo mining, I tend to believe there won't be any updates available in the foreseeable future. They are not ignored, we have other priorities. Lots of software work will be complete in the fall, most of it is being worked on now. |
|
|
|
Better to not run at 100% of the PSU capacity though. I run turbo but use an off the shelf 500W PSU.
Also correct, yes, maybe FutureBit has more info about the actual rating of their PSU's - maybe the product pages just say 200W but there's a little headroom built in still? Edit: From product pics it seems the absolute max that can be pulled from it, is indeed 16,7A, which is 200.4W... Maybe suggestion to FutureBit to upgrade their PSUs to e.g. 220W units for the next iteration  I also always over-spec PSU's when building PCs for example, it's really common practice and they also run more efficient at around 70-80%, I think. It can run in turbo and is rated for that, but there is little headroom, OCP will kick in at about 210-220 watts. Next gen PSU will be able to run at ~300 watts. |
|
|
|
Any updates when next shipments start?
Everyone should have received an update email that has a Batch 2 order. We received final materials this week and will start shipments next. Have all the batch 2 orders been shipped? I was able to get an order in for batch 2 when orders opened up in late June. I received an email update about batch 2 orders shipping soon in late July but it's been radio silence since. I'm in Canada, if it matters. All the original Batch 2 orders are out, only ones left are the later ones ordered end of June, those always had an august ship date. All orders should be out by end of the week/early next. |
|
|
|
Alright I got my new Apollo today and have tried to set it up! It seems to be running but I can't get it to mine. I have put in my pool information, but it still shows just the generic pool information with (jstefanop.apollodefault). My hash rate is 0 and power usage is 0. I tried setting up with slushpool so far. What is wrong? Node shows it is still sinking at 56% after about 4 hours since I plugged it in. I am using a wired connection.
Make sure you have not changed the default timezone in the desktop time and date settings as well. If your still having issues just reach out to our support email (reply to your order email). |
|
|
|
How long does it take for the package to make it to FedEx once I get the shipping notification. I got the shipping notification and tracking number on Tuesday, but looking at the FedEx tracking page, it still says they're waiting for the package.  Tracking numbers are issued when your unit is first built, it can take a bit before it ends up in fedex possession. If you dont see movement this weekend it will definitely be by Monday latest. Still no movement The package status is still at "Label Created" We had some issues with Fedex pickups last week, they were supposed to be picked up on Friday but our shipment was too large and could not be picked up. All remaining packages from last weeks shipments will go out today. |
|
|
|
I've noticed now that I have a second miner I cannot forward another IP address to 8333 for the new node. Does anyone have a solution? I have a new deco mesh router and it makes you pick the IP address when forwarding. Can the port the node uses be changed?
There is no practical reason to run more than one node from a single external IP address. As you found out you cant forward the same port to more than one device in your network. As for as the outside world is concerned it only sees one "service" per IP address. Obviously you can do complicated internal network switching to make it work but its not worth it for a full node. If you have two full node devices, its better to run the second device from a different location with a different internet connection/IP address. |
|
|
|
Is there an API available so that we can monitor the miner from another system? Awesome Miner, HiveOS, etc. I like to see all my miners in one location.
Raw json data is available in the API, I believe one of them already added Apollo LTC support, so should be pretty easy for them to add BTC version. They usually add them if they get enough requests. |
|
|
|
How long does it take for the package to make it to FedEx once I get the shipping notification. I got the shipping notification and tracking number on Tuesday, but looking at the FedEx tracking page, it still says they're waiting for the package. Tracking numbers are issued when your unit is first built, it can take a bit before it ends up in fedex possession. If you dont see movement this weekend it will definitely be by Monday latest. |
|
|
|
Hello, I just got my miner yesterday, and was able to get to the dashboard and attempt to connect to a pool and start mining. Couldn't get it to connect quite right, it would look good on the Hashboard, but the pool would show inactive, and nothing would show up on the pool side of things (Slushpool). But now this morning I decide to start trying again, and the miner is just making a weird sound and I can't access the dashboard anymore. Rebooting, starting, restarting seems to do nothing. It just sits there making a weird sound. Would appreciate some help on this.
#Update I adjusted the username in the pool section of the miner (had tried to put a space in there because it looked like there was one on the example from slushpool) and now everything looks to be working! On the miner side at least, still too soon probably for slushpool to say anything. But just thought I would put this out there if anyone else puts a space in your username it seems to cause the miner to have a meltdown. Yes credentials are case sensitive on most pools...the username field will take whatever you put in it so if its not exactly what you have set up at the pool it won't authenticate. FYI congrats on all Batch 2 users coming online...sync those nodes and forward that 8333 port! Lets show the world Bitcoin users DGAF about any US government laws trying to stifle this revolution. |
|
|
|
I updated my Apollo and 1 of them BTC node is ok and the miner inactive but I see he is online and mining on the pool. The other same thing, node ok and miner inactive in the dashbord but online and mining on slush pool in my account. on this one I see jstefanop.worker1 on the dashboard page. weird!  Does a reboot fix this? Are you updating via local network or a connected monitor? Shoot an email if your still have this issue, want to see where the update is breaking. FYI should have an updated image out later today as well. Reboot change nothing and I made the update via local network I'm also having this issue. It started after the upgrade to 0.3.1 (but not immediately after; I was running on 0.3.1 for some time before the issue manifested itself). It hasn't righted itself after several power cycles. The miner is still attached to the pool and hashing, but the local web UI shows no data whatsoever. FYI we figured out what is causing this round of UI stats bug, this only occurs if you are logged in directly through the system and change the system timezone in the date and time panel. For the time being just reset the timezone back to default (london timezone) and your stats will start working again. This is what happens when your used to embedded systems all your life when users typically cant touch the system settings Will push a quick fix for this hopefully in the next week. |
|
|
|
If I installed a 1tb drive before using the miner would I need to install any software on it first?
No, as long as you power on the device with the SSD installed and a freshly imaged SD card, it will take care of setting up the drive for you. |
|
|
|
I did not receive email. Orders 4420 and 4492. Are these considered Batch 3? Thanks! Edit-  Nevermind, I found it. What was the final outcome? On the website, you can pre-order Batch 2. Wouldn’t we be waiting on batch 3? Confused. @jstefanop - Can you provide some insight? Thanks. We are purging some scalpers we have come across from our order system. Didn't announce anything as we wanted the people that religiously check our site every day to have a chance to grab one. Batch 3 will most likely start next week...and those will ship sometime in Q4. Some ICs we need we dont even a ship date yet so we cant pinpoint a month yet. |
|
|
|
Any shipping updates on Batch 2? Will they come with the latest software or will ne need to update them? Looking forward to getting started. BTC
Batch 2 is shipping with the latest image/updates. We already started shipments and the whole Batch should be out in 3-4 weeks. |
|
|
|
I flashed my microSD card with the latest update, so I'm running Apollo v0.3.1. I've decided to try the lottery and use ckpool. When I check the pool stats for ckpool, I can see my hash rate reporting at like 1.78T, but my problem is that the dashboard on the Apollo says otherwise. All indicators to the pool say 'inactive', and says I'm hashing at rate of 0.0. I've tried, stopping, starting, restarting a few times, but all mining dashboard representations look like nothing is happening even though the pool is reporting otherwise. Any suggestions? The node dashboard looks OK and looks to be displaying accurate information.
Send us an email with this issue, looks like the webui bug fixed the issue the majority of users were having, but there seems to be a small number of users still having this and could be pool related. |
|
|
|
My fan sounds like its bearings are burning out. My LED doesn't work either. Can I send it to you for repair? I reached out on the previous support chat w a video.
Yes, just reach out to our email for support (you can reply to your order email). |
|
|
|
Latest Image has been added Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_QRelease 7/31/21 d6f820869268383883db4741dcfcade8f57ad1a1c20c359fd7a3015c78ffe3dd apollo-btc_310721.img.xz -Updated Apollo UI to latest 0.3.1 -Image no longer wipes SSD if it detects it has already been formatted -Added additional swap memory to prepare for Lightning network/block explorer apps -System level fixes/tweaks for stability Thanks for the image mate! Any differences between this and what was released the other day via the OTA (like the system level fixes - are they for the underlying OS?) Not really most of the big changes/bug fixes were pushed over the OTA update. Main difference in this image is it includes extra swap memory on the nvme drive, so it can handle additional apps we will introduce in future updates. |
|
|
|
So now that the release day bugs are all ironed out; how goes adding LN functionality? Was the main reason I bought the full node version. Alternatively has anyone installed an LN client themselves?
We are already working on native lightning + blockexplorer apps in the dashboard, but there is nothing stopping you from installing them yourself. You can connect them to the node using futurebit/futurebit rpc username/pass |
|
|
|
Latest Image has been added Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_QRelease 7/31/21 d6f820869268383883db4741dcfcade8f57ad1a1c20c359fd7a3015c78ffe3dd apollo-btc_310721.img.xz -Updated Apollo UI to latest 0.3.1 -Image no longer wipes SSD if it detects it has already been formatted -Added additional swap memory to prepare for Lightning network/block explorer apps -System level fixes/tweaks for stability |
|
|
|
|
Show Posts
