Very interesting feature - can you please share a quick sert up for making the Apollos and Awesome miner work together?
Thanks in advance!

Hi Patrike
I just upgraded to this release and my issue with NBminer is corretly solved now, i.e. native miner working ok after logging in to the pool and all the relevant power and price info for GRIN is passed to the dashboard, thanks a lot.

[/quote]

Yea thats definitely a faulty PSU, especially if all Apollos are running fine with a bigger PSU, and the fault happens even when you switch different Apollo units.

450 W PSU should not be tripping with a 150W load.
[/quote]

I think the chances were 99:1 that I had bought a faulty PSU due to its behaviour after swapping all the boxes from the suspicious PSU to the bigger one I had, yes.

...BUT

[/quote]
I recall older ATX power supplies required some load (something in the 1A range) also on the 5V rail in order to keep the 12V rail stable. That may still apply to cheaper power supply models.
[/quote]

...I plugged to the SATA line the only thing I had at hand, i.e. a small SSD drive,  that pulls exactly  5V 1A.
And it worked!! AWESOME, the 3rd Apollo has been mining and stable for one odd hour (vs. shutting off power after a few seconds or just one minute) and I think that this smart little trick solves the issue very nicely.

The bottom line - beware of cheap non-modular PSUs but if you use one keep it "alive" by plugging something to the 5V rail.
Now I am thinking  what can I add to this set (I need to keep my SSD) for my friend so to make the whole thing work. Maybe a fancy USB gadget like a mini-vacuum cleaner or a few USB fans would do, plus a SATA to USB adapter cable of course - any ideas?

Ah, @philipma1957, thanks for the links to better PSUs, the modular ones around 500-650w are my personal bet for powering up bundles of 2-3 Apollos if I buy a few more of them.

Again , thanks to everybody for your very helpful insight.
 

Hi everybody

I have been mining non-stop 15+ days in a row with the following setup:
PSU corsair CS750M, powering up two Apollo units working in ballanced mode, all the other values set in auto (default) and via ethernet LAN.
I am very satisfied with their simple setup and robustness (restart and mine again in case of power off etc).
A few days ago my 3rd Apollo unit arrived, this one is not for me but it's a gift for a friend of mine who has an absolutely non-technical soul so it has to work unattended, forever
I bought a brand new PSU, this time a smaller 450 W corsair VS450 and prepared the initial setup as before but with only one unit attached.
To my surprise, afterwaiting a few seconds for the initial system load and get it reg/green blinking, the PSU shuts off.
I suspected a power surge or something coming from the 3rd Apollo.
The shut off happens after doing the full load and not before.
To start isolating the problem my workaround was using my former rig with the older, bigger PSU feeding all three boxes and let it run overnight. The whole system went on mining whitout any problems.
When I did further crossovers - e.g. using one of the older units with the new 450w PSU, the sudden shut off happens again so it seems that it is not something from a specific miner - unless I'm wrong of course.
I judged too unlucky that the corsair PSU could be responsible of the problem as it's a quality brand.
But the issue is driving me bonkers. I do not know how to go on.
Atm I was about to order a PSU replacement but I'd like to share with you here in case I'm missing something or there is a known incompatibility or other issues I may have oversighted before returning the 450w psu to the shop.

Your ideas will be much appreciated - Thanks in advance!

Hello Patrike,

I decided to give Grin a try, for he purpose I spared a small rig with four GTX 1060 6GB. Due to the RAM size, I have no other option left for the sw miner of choice than NBminer.  Both Gminer and Bminer require 8GB.

That said, I configured AM to mine GRIN-29 in f2pool.
When I triggered the newly created managed miner if failed to log in to the pool. I reviewed the parameters passed and found no mistakes and all seemed to be ok as per pool instructions.
Running diagnostics leads to the following:

Initialize diagnostics (10)
Starting Diagnostics. Awesome Miner version: 6.1.5
OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 417.01
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 7
Engine Type: BtMiner, Auto Download: True, EnginePath: C:\bote\NBMiner_Win\start_grin_f2pool getgrin.bat, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: BtMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\GaoFuShuai\AppData\Local\AwesomeMiner\nbminer_13.2_win_7\NBMiner_Win\nbminer.exe  -a cuckaroo -o stratum+tcp://grin29.f2pool.com:13654 -u grinworker.001 --api 0.0.0.0:4034
====================================================================================================
Mining Engine Process started, PID: 6008
> [16:06:56] INFO - ----------------------------------------------
> [16:06:56] INFO - |                   NBMiner                  |
> [16:06:56] INFO - |              NVIDIA GPU Miner              |
> [16:06:56] INFO - |                    13.2                    |
> [16:06:56] INFO - ----------------------------------------------
> [16:06:56] INFO - ALGO:  cuckaroo
> [16:06:56] INFO - URL:   stratum+tcp://grin29.f2pool.com:13654
> [16:06:56] INFO - USER:  grinworker.001
> [16:06:56] INFO - ============= Device Information =============
> [16:06:56] INFO - ID 0: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ID 1: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ID 2: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ID 3: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ==============================================
> [16:06:56] INFO - NVML initialized.
> [16:06:58] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:06:59] WARN - Failed to login mining pool, please check mining pool username.
> [16:06:59] INFO - Logout.
> [16:06:59] INFO - API:  0.0.0.0:4034
> [16:06:59] INFO - API server started.
> [16:07:01] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:02] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:02] INFO - Logout.
> [16:07:03] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:04] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:04] INFO - Logout.
> [16:07:05] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:06] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:06] INFO - Logout.
> [16:07:07] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:08] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:08] INFO - Logout.
> [16:07:09] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:10] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:10] INFO - Logout.
> [16:07:11] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:12] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:12] INFO - Logout.
> [16:07:13] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
Diagnostics completed

My workaround was to copy the contents of the automatic download zipped folder for NBMiner to a new folder outside the AM path and run a bat file for the same task, which worked ok, i.e. this time it was able to log in my user grinworker to f2pool ands start mining grin.

The bat does this:
nbminer -a cuckaroo -o stratum+tcp://grin29.f2pool.com:13654 -u grinworker.001:x -long-format -log

(grinworker is a moke ID not the real one I use)


Then I tried to make AW leverage the working bat by changing the software location in the Managed miner properties - General from "Automatic download" to "specify existing installation path" and pointing the path to the bat file I had succesfully run before.

In this case AM is able to log in and mine but unable to pull any information and display in the Dashboard screen  i.e power usage, also in the Pools, and GPU tab for the miner, nothing is shown, so I am not very happy with the outcome, which is a semi-integration only.

What should I do to have NBminer up & running by just using the default automatic download which is not loging in properly?

Thanks in advance!