Please reply to your order email with stuff like this. Multiple orders are combined, so thats why one of your orders was canceled.

Yep, any hiccups with the standard units just power cycle them and restart in the dashboard...that should solve most issues.

Awesome...could have been a weird type of ethernet cable that the Apollos network controller couldn't handle. The USB connected hashboards is a known issue we are trying to figure out if its a firmware or general STM32 USB driver issue. Usually a power cycle on the standard unit will fix it if its taking a really long time to connect.

We were going to have it this week, but most of the team will be down in Miami for the conference so will probably get pushed to next week.

If you pop in a fresh SD card at the same time as a new SSD it will automatically format and set it up.

You can do it manually as well by launching the gparted app installed in the system, and initializing it with a single partition. You then need to add a folder called "Bitcoin" in the root directory of the partition.

Adding a "format and setup new SSD" button in the UI is on our list.

Ok so it has successfully booted, your just not getting an internet connection. Id double check your ethernet wire (ie check if you plugged it in a WAN port instead of LAN port) and router settings in case something is not configured correctly there.

Are the yellow LEDs on the bottom flashing rapidly? This means its connected to your network and hashing.

If so you need to do double check your router or IP scanner, one of the IPs is the Apollo.

For monitor out issues, try powering off your display and power it back on when its connected to HDMI port on the Apollo, this has worked on some displays we tested. Some displays won't work at all, so try another display if you have one or your TV and see if it works that way.

Thanks! We had to stop the line to catch some issues from the first deliveries, but starting back up today. Will probably push into next week to get the rest of the orders out.

If I could I would. The backend software runs Exahashes worth of hashrate, and finds BTC blocks everyday. Of course you have to take my word for it, and I wish you didn't but I think I have built enough reputation around here that im not some bad actor. Unfortunately to be able to provide a product like this I had to make some compromises I did not want, but we weighed those to be worth being able to get a product like this out to market.

Of course the more successful this product is, the less compromises we have to make...would love to port the firmware over to cgminer and hopefully we can get there soon.

The software is designed for stratum pool implementation. Its not a solo miner, and the solo miner implementation will piggy off open source stratum proxy that connects directly to the node.

Prove how my statement is completely false? Oh wait you cant. As long as our software submits valid shares > pool diff then it will submit a valid share > network diff.

If you want to attack me then attack me with correct arguments, like "since the software is closed sourced I could be throwing out valid shares >= network diff"

Now that im thinking about it that would be a fun way to attack these centralized chinese pools 

Well thats the beauty of Bitcoin, you dont need to trust anyone, just verify. Bitcoin's POW is simple on purpose. Your hardware can either solve SHA256 hashes or it can not.

Sure I can lie about the hashrate on the dashboard, but I cant make up valid shares to a pool unless I am actually performing that work (or I have broken SHA256 which is a possibility, but then your all screwed anyway haha).

Ahh thats where phillip's confusing question comes from in the other thread....should have known better. 

So we went from me making shitty vaporware, to me selling pre-orders ill probably never deliver, to now that I have actually delivered working hardware making baseless attacks on the software that make no sense? Whats your agenda here anyway?

From someone who runs a pool its pretty concerning that you dont know how blocks are found. If our software can submit a valid share to a pool, it can also find a valid block and thats all the proof you need. But you already know that or should know that...so once again whats your agenda?

uh what?

You dont need to "prove" it can hit a block, the proof is in the valid share submission.

Submit enough shares of a certain difficulty over time and you have "proved" your hashrate.

Submit a share higher than the network diff you found a block, simple as that.

Yes the top temp is the ARM cpu temp. It will stay in the 80s while its syncing the node and should come back down to 50-60c once it completes.

Not currently, wanted to keep things as simple as possible since a large portion of our customers are first time miners.

If you want to do this in the meantime, you can start up the hashboard manually. Its a little involved but here are the steps:
-Disconnect the usb cable of the hashboard you want to point to a different pool.  
-Start the miner in the dashboard so UI configured pool and connected hashboards start mining to that pool
-Connect the hashboard you want to mine to a different pool
-Open up a terminal and figure out the serial port by typing "ls /dev/ACM*" ....the hashboard you just connected will be the highest number
-Go to the directory the internal apollo-miner is installed at "cd /opt/apolloui/backend/apollo-miner"
-Startup that hashboard manually with the serial port you found above and its own pool using instructions found here:   https://github.com/jstefanop/Apollo-Miner-Binaries/blob/main/linux-aarch64/start_apollo.sh

(ie ./apollo-miner -host us-east.stratum.slushpool.com -port 3333 -user jstefanop.x -pswd x -comport /dev/ttyACM0 -brd_ocp 48  -osc 30 -ao_mode 1)

If you do it this way the hashboard should also be added to the UI stats and you should be able to see it there (fyi i havent tested this so could break the UI if its using a different pool).

We left the system open so you power users can poke around and configure it to your hearts desire...you can also do the above by editing the start script in the miner folder and you can do lots of stuff this way like per board power settings, per board pools, etc etc (all the start script does now is find all the /dev/ACM serials connected and loops through all of them and starts a miner instance for each board using settings from UI....you can just explicitly point to each serial and put your own settings for each board if you want).

                                                                  

Not true.

If your mining at 3TH/s (turbo mode) you have ~ a 1/340,000 daily odds of hitting a BTC block.

Way better odds than the lottery, but of course the cash prize is "only" 200 grand 

Will be adding a direct solo mine option to your node in the coming months.

Yea were still dialing in the torque settings for all the screws. Sorry to hear you had to disassemble it to get to the CPU fan. Im happy that most people are not having issues with the hardware...few loose screws we can deal with 

Ok if it does not start flashing at all when you do stop or restart on the miner dashboard then that means the system does not see it at all. Shoot an email to us by replying to your order email and well go over some other troubleshooting steps.

Start them up and leave them be for 10-15 minutes. They will start up eventually. As long as you see the front LED start flashing slowly it will show up in the dashboard.

Yea its already optimized for the RAM size...fact that you can sync a full BTC blockchain in under 2 days with this is already impressive for a sub 200 dollar "computer", and is already way faster than what even a Pi 4 can do. You cant expect this to do it in 12 hours lol