Quote from: Muppet007 on May 03, 2022, 06:17:51 AM

Quote from: nullama on May 02, 2022, 10:23:50 AM

Quote from: CochnocherCrypto on May 01, 2022, 05:35:09 PM

So I've had my Apollo's for a little while now and like most people here, I am thrilled to have them in my apartment! Currently running 4 of them - 1 with a controller, 3 without. My question it this - I have them connected to a pool but using the controller's UI via FireFox - I am only able to have these connect to a pool as 1 worker. All of the other miners I use have individual assignable worker names - so should there be an issue, its easy to identify which miner is problematic without actually being at home and staring at the screen. Is there a way to have each apollo connect to the pool as it's own miner while running them all connected to the unit with a controller? Or would I have to use external controllers for each standard unit to achieve this.

Not sure if it's supported in the web UI, but you can name each worker using the pool username field.

Usually pools allow you to give names to each worker by appending a dot(.) and then the worker name to the username of the pool. Something like this:

Quote

./apollo-miner -host POOL_URL -port POOL_PORT -user POOL_USERNAME.WORKER1_NAME -pswd x -comport /dev/ttyACM0 etc...

./apollo-miner -host POOL_URL -port POOL_PORT -user POOL_USERNAME.WORKER2_NAME -pswd x -comport /dev/ttyACM1 etc...

./apollo-miner -host POOL_URL -port POOL_PORT -user POOL_USERNAME.WORKER3_NAME -pswd x -comport /dev/ttyACM2 etc...

etc...

You would only need one computer to name those 4 workers. Each one would just be another call of the apollo-miner binary with its name and specific parameters.

Try not to over-fit a solution to a problem that for the most part does not exist given the maturity of the OS and software..
If you really want these worker alerts via your pool then test if you can run multiple instances of Apollo-Miner v1.1 on the controller unit.
One may have to use a terminal only barebones OS to do this. Would suggest a separate 'TEST' SD card if going this path.

That makes sense! I will see about doing that. For whatever reason, it seems like the Apollo I have with the integrated OrangePi always has a higher HW Error % than the other 3 (nothing major - my 3 standard units generally report an HW error rate of 0.4-0.7% while the unit with the SBC is closer to 3.5-4%) - Wondering if it is because, looking at the way the unit was designed, the OrangePi looks to be drawing it's power from the hashboard, slightly lowering the power the board has at it's disposal. The same unit also runs just a tiny bit hotter with the fan spinning just a tiny bit faster (I guess this is to be expected with the controller attached...). All the same - having them set up in a way that they can be individually tweaked would be great. I will see about launching multiple instances of the Apollo-Miner and will report back!

I appreciate everyone who chimed in and offered their thoughts!!!!