Search content
Sort by

Showing 14 of 14 results by potentabit
Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 20/04/2024, 16:14:02 UTC
FYI Main support page for Apollo II/BTC is up that has consolidated a lot of the info found here in an easy to read page with relevant links etc

https://www.futurebit.io/apollo-btc-support



Very good!!
Post
Topic
Board Hardware
Re: Nicehash Pool
by
potentabit
on 16/04/2024, 12:22:06 UTC

EDIT: No luck with asicboost..


Make sure you have the latest update installed.
Post
Topic
Board Hardware
Re: Nicehash Pool
by
potentabit
on 16/04/2024, 01:31:37 UTC
MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.


Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?


I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.


I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.


I got both (MCU1 and Apollo II S) sending data at the same time to to NiceHash by using "stratum+tcp://sha256asicboost.auto.nicehash.com:9200" instead of stratum+tcp://sha256.auto.nicehash.com:9200. However they do appear to be inversely labeled as displayed on the "Hashboards and Pools" page.
Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 15/04/2024, 20:57:30 UTC
Hi, it looks like the Unit opened up port 8333 via UPnP, but I still see only 10 connections...Is it because it is still syncing with the Blockchain?
Any thoughts? Thanks.

It take a while!
Post
Topic
Board Hardware
Re: Nicehash Pool
by
potentabit
on 15/04/2024, 02:03:11 UTC
MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.


Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?


I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.


I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.


Currently when more Standard units are connected it looks like a single miner as far as the pool is concerned. We only test on standard pools, but will check nice hash and mining rentals to see what the issue is, but these are notoriously buggy pools since they just send the connection to a downstream pool anyway.

Would be good if we can have an option to control (on-off) each miner attached to main Apollo.
Post
Topic
Board Hardware
Re: Nicehash Pool
by
potentabit
on 14/04/2024, 00:35:06 UTC
MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.


Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?


I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.


I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.
Post
Topic
Board Hardware
Re: Nicehash Pool
by
potentabit
on 13/04/2024, 15:41:43 UTC
MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.


Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?


yeah.
your btcaddress.apollo1
your btcaddress.apollo2

may be better


or

yourbtcaddress.0001
yourbtcaddress.0002

may even be best.

I'm still getting familiar with the software settings, do I add each one in the same "User Name" field or is there a setting where each attached unit can be named as you describe?
Thanks.

Post
Topic
Board Hardware
Re: Nicehash Pool
by
potentabit
on 13/04/2024, 15:01:51 UTC
MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.


Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?
Post
Topic
Board Hardware
Nicehash Pool
by
potentabit
on 12/04/2024, 17:56:09 UTC
MCU1 full node with Apollo 2 Standard attached to USB.
Using  v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.



Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 12/04/2024, 15:48:29 UTC
Link to download MCU1 Apollo OS 2 below.

Want to get this tested here by a few of you since we dont have a lot of MCU1 devices left to test.

Below feedback would be appreciated:
OS detects internal board and starts up fine
OS detects and starts up external USB Standard units (both Apollo BTC or if any MCU1 owners have an Apollo II standard yet)

https://www.dropbox.com/scl/fi/j4o3rcwe88emzsuwe4wm7/apollo-2-mcu1_110424.img.xz?rlkey=cu3i66xtl5n4ln8ji7mct3zth&dl=0

This includes latest v2.0.4-beta release

Reminder MCU1 controllers are Batch 1/2 Apollos with the longer GPIO pins on the board (check link below if you are not sure which you have).

https://mega.nz/file/dghWnKJC#J2kkpfH5RVKynf0OvuE5mKojXdUqAFCczHMyv6mDrM4

Finally found the "Power button" LOL...
Just started MCU1 up. Looks and working well. It recognized Apollo2 S. and mining in ECO mode @ 7.8TH and 307W
GUI is a bit slow and jerky but manageable. I'm assuming it's the MCU1, otherwise working well so far.
Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 12/04/2024, 01:04:53 UTC


Had to fix some issues with board detection on older Batch 1/2 units. Should have the image out in a few hours.

FYI we just pushed 2.0.4 out that fixes solo page issues when you find a share higher than 2.1 Billion (it will crash the UI on versions lower than this)

Press the power button and go down to the version number to force an update

Updates now reboot the system, so you will need to refresh the page after it reached 90% complete if you are accessing from another computer(update can take 10-15m so dont do anything until progress reaches 90%).

Not sure what you mean by "Press power button"
Is the "power button" on the MCU2 software and do I download it from the last MCU2 update link?
Or is there a separate MCU1 software update link?

Thanks
Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 10/04/2024, 23:45:24 UTC

I believe 4TB drives should work with it, only tested up to 2TB though.

2TB will last nearly 10 years before you need to upgrade. Anything higher is overkill since these drives will be a fraction of the cost when you need top upgrade.

We are hesitant to add USB/custom locations for node drive since they are notoriously slow. Would not do this especially if you want to solo mine.

I that case, I agree then. 2TB is plenty.
Still have a few GB's on the 1TB NVMe for now.


Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 08/04/2024, 21:17:42 UTC
Any chance on hardware DIY upgrade?
[MCU1----->MCU2]

Looking forward to the MCU1 software update. I've had my Apollo 2 plugged in ready to go for a few days :-)

Thanks!!


Should have the MCU1 update out by tomorrow. There is no point to update the MCU, its the exact same hardware MCU2 just has slightly different pinouts and configuration that was custom designed for our application.

OK, great! Thanks for update.
What is the max replacement VNMe capacity for the V1 Apollo unit?
Can the new software (V2) include option to use USB SSD instead of internal VNMe?

Thanks again.
Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
potentabit
on 07/04/2024, 16:28:22 UTC
Any chance on hardware DIY upgrade?
[MCU1----->MCU2]

Looking forward to the MCU1 software update. I've had my Apollo 2 plugged in ready to go for a few days :-)

Thanks!!


Sorry guys dropped the ball on this one, obviously focused on making sure we had a shippable OS for all our Apollo II units going out.

Good news is that all the work we have done for the Apollo II translates to all Apollo BTC units, we just finalized a stable release for Apollo II and BTC/MCU2 units and will have an image for MCU1 units hopefully by tomorrow/sunday.

We are all working overtime to get the OS and all Apollo IIs out to you all!