Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 13. (Read 703060 times)

Hello. After this update, the launch, the restart button and the profit switching do not work.

Awesome Miner version 9.9.6

 ASIC mining
  - Added support for Antminer HS3
 Features
  - Include ASIC miner fan speed in Awesome Miner API response
 Changes
  - Remove legacy MSI Afterburner integration
 Mining software
  - BzMiner 14.3.2
  - Gminer 3.39
  - Lolminer 1.75
  - Rigel 1.4.6
  - SrbMiner-Multi 2.2.5
  - TeamRedMiner 0.10.12

Thanks for your question. I'm not really able to understand this issue: "AM overwrite all definitions with the last value"

If I have a miner with dual configured, where I select one Pool and one Secondary Pool, the command line I get from Awesome Miner is for example:
--algorithm etchash
--pool stratum+tcp://us1-etc.ethermine.org:4444
--wallet
--password x
--algorithm sha512_256d_radiant
--pool stratum+tcp://stratum-eu.rplant.xyz:7086
--wallet
--password x
--api-enable
--api-port 4039

This starts the dual mining perfectly fine. I don't see what kind of parameters that would be overwritten here. Awesome Miner simply adds a second set of algorithm+pool+wallet+password parameters when you enable dual mining.

The example above is without any manually configured command line arguments. Are you using any manual parameters as well?

Hi Patrike, SRBMulti 2.2.5 realised, user now can dual mine Dynex+Radiant, but with AM this is imposible.
In SRBMulti can be defined algorithm, pool, wallet, password values for each involved in mining algorithm separatly. User can multiple times define --algorithm --wallet --password --pool arguments, SRBMulti create a collection and add every similar parameter definition to this collection, but  AM overwrite all definitions with the last value. This made imposible to start dual mining with this method of parameters definition.
I have maqnually created a command string where every algorithm, pool, wallet, etc. was defined with individual --algorithm --pool --wallet parameters and executed over terminal and this allow me to mine in dual mode. But if AM create command line, then only last defined values will be used. Please clear this bug. Regards.

Everything works correctly
Thanks

I've pushed an update for the IronFish calculation. It will automatically be picked up by your Awesome Miner within the next few hours and will resolve the issue.

For the correctness of the profit (like in wattomine), I set the profit factor for the pool 4300000000

Hi all
Have you noticed that ironfish does not calculate profit correctly?
Wattomine gives statistics correctly
What do you think?

3070ti
Electricity at 4 cents
Wattomine - Day   0.000000   0.087446   0.000016   $0.47   $0.14   $0.32

Hello and thanks for the comments. I've pushed a mining software definition for this.

Thanks for the feedback. I pushed these mining software definitions yesterday so hopefully you found them by now.

BzMiner has some issue with terminating under certain conditions - I'm trying to figure out exactly when this happens.

Hi Patrik,

GMiner 3.35 added X+Radiant dual mining:
Ergo+Radiant
ETC+Radiant
Conflux+Radiant

Can you please add Radiant to the Dual Mode in the Managed Miner Properties? Thanks!

BZminer does not close if i run it in admin mode in some cases. Also not with ctrl+c activated in options.

Missing BZminer stats is solved, it was an failure in BZminer API with specific gpu+driver combinations.

Ironfish dual mining options are missing for: Teamredminer, SRBminer, Rigelminer
Also missing dual mining option is alephium for Rigelminer.

Awesome Miner version 9.9.5

 ASIC mining
  - Goldshell integration improved with LED flash and change web password
 GPU mining
  - Improved detection of more recent CUDA versions
 Features
  - Miner Property trigger can be configured to trigger on the current mining algorithm
  - Improved firmware version trigger to also detect firmware date on Bitmain firmware
  - Improve Time trigger to support month of year expressions like 11-04, for November to April
 Mining software
  - BzMiner 14.3
  - CpuMiner-Opt 3.22.2
  - Gminer 3.34
  - Lolminer 1.74
  - Miniz Miner 2.0c5
  - Rigel 1.4.4
  - OneZeroMiner 1.1.0
  - TeamBlackMiner 1.94
  - TeamRedMiner 0.10.11
 Corrections
  - Correction to device list for OneZeroMiner

Good point. I will make sure the next release will support 10-04 and similar expressions. Like you noticed it isn't supported today.

In the next release you will find "Algorithm" as one of the properties in the "Miner Property" trigger.

It seems as though there is a bug with the Time Rule Trigger. If you select a month range that is lets say late in the year till the next year, it doesn't properly read it. Like 10-04, so from Oct to April. It works fine in the opposite direction. So 1-8 or 4-12, but not 5-1 or whatever range you want that moves across the year till next year.

Hi Patrike, can you please add a rule triger for mining algoritm. I want realise logic, when specifed algo will be choosed from profit switching, the specified profit profile must be also choosed. Regards.

Hi,
Yes, that API response is broken and this cannot be resolved from an Awesome Miner point of view.

Hi patrike,

i see no stats (no hashrate, nothing in gpu tab, no shares.....) when i use Bzminer. Here is the API report

API command: /status
{"method":"fullstatus","rig_name":"test","bzminer_version":"BzMiner/v14.1.1","os_name":"Windows","architecture":"x64","used_memory":3923.15015625,"total_memory":32692.91796875,"used_storage":88629.59375,"total_storage":228319.99609375,"cuda_driver_version":0,"opencl_driver_version":0,"processor_count":24,"cpu_usage":1.0,"cpu_name":"AMD Ryzen 9 3900X 12-Core Processor            ","hdd_name":"Intenso SSD Sata III","ram_name":"Unknown","uptime":"3:12:12:25","uptime_s":303145,"intensity":1013777312,"http_address":"0.0.0.0","http_port":4030,"http_enabled":true,"logfile":"","nvidia_only":false,"amd_only":false,"launch_on_boot":false,"verbosity":2,"update_frequency":15000,"lock_config":false,"watchdog_restarts":0,"watchdog_enabled":true,"pools":[{"id":0,"algorithm":"radiant","wallet":"xxxxxxxxxx","url":["pool.eu.woolypooly.com:3122"],"username":"290","lhr_only":false,"test":false,"test_diff":1,"test_iteration_ms":120000,"max_connection_retries":0,"delay_before_connection_retry":3000,"current_url":"pool.eu.woolypooly.com:3122","status":-1589992416,"message":"","uptime":"3:4:40","uptime_s":276054,"epoch":0,"block":-1,"difficulty":34360262664.0,"pending_solutions":1,"valid_solutions":1230,"invalid_solutions":0,"rejected_solutions":9,"total_solutions":1230,"stale_solutions":0,"average":0.26733899889152126,"accepted_avg_seconds":224.33170731707319,"power":7.9496286016e-312,"hashrate":147174016.0,"average_latency":104},{"id":1,"algorithm":"zil","wallet":"xxxxxxxxxxxxx","url":["zmp://zil.flexpool.io"],"username":"test","lhr_only":false,"test":false,"test_diff":1,"test_iteration_ms":300000,"max_connection_retries":0,"delay_before_connection_retry":3000,"current_url":"zmp://zil.flexpool.io","status":-1589992416,"message":"","uptime":"3:12:12","uptime_s":303142,"epoch":0,"block":27986,"difficulty":1073725440.0,"pending_solutions":1,"valid_solutions":103,"invalid_solutions":0,"rejected_solutions":4,"total_solutions":103,"stale_solutions":0,"average":0.02038648554142943,"accepted_avg_seconds":2874.9417475728157,"power":7.94962861836e-312,"hashrate":0.0,"average_latency":2294250}],"devices":[{"name":"AMD Radeon R9 200 Series","index":3900,"uid":"39:0","cuda":false,"pci_bus_id":39,"pci_device_id":0,"vendor":2,"device_id":"0x67B11002","subsystem_id":"0x92951682","lhr":false,"pool":[0,1],"hashrate":[147174016.0,0.0],"efficiency":[   *it look like here is something missing*


http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  60
  false
  0
 
    303149
    0
    0
    0

It look like the API report is not complete, maybe that is the reason for no stats?






 

Tools > Rule History

Maybe it's not a normal log that gets saved, however with variable triggers it only keeps about a hour worth of data before it gets pushed out due to the variable activating every 6s.