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

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.

Looks like all work normal. Simple AM need some time (arround 1min.) after i change some params in Profit Profile and then convert to managed miner mode. This got me confused. Now after you have integrated OneZeroMiner, no more needed to convert in managed miner mode))). Regards.

Thanks for testing the new OneZeroMiner. I will make sure this will be corrected in the next update.

Hi Patrike, thanks for quick integration of OneZeroMiner. Small bug found in onezerominer: GPU tab show hashrate only for first GPU and no process information output to console. Regards.

allright...so it just to have ability to install stock FW via awesome miner - not injecting custom FW stuff into this installation process

Bitmain provides firmware files for Antminer S19 with "merge" in the filename, where they have included/merged firmware files for a number of different control boards into a single large file. In the past the provided it as separate firmware files for each control board.

In order to install one of these merged firmware files you download from the Bitmain web site, Awesome Miner can now read the firmware file and pick the part that matches your Antminer and install it. This concept is only applied if Awesome Miner finds the word "merge" in a firmware file with the .bmu file extension.

- Support firmware updates for Antminer S19 with merged firmware files from Bitmain

what does this means in detail?
i can now update also amlogic via webinterface without signature check error?!?

Awesome Miner version 9.9.4

 ASIC mining
  - Added LED flash for Bitmain firmware for Antminer S19, KA3 and K7
  - Support firmware updates for Antminer S19 with merged firmware files from Bitmain
 Integrations
  - Added regions for MagicPool.co
 Mining software
  - Added mining software: OneZeroMiner
  - BzMiner 14.1.1
  - Rigel 1.3.11
  - SrbMiner-Multi 2.2.4
  - XmRig 6.19.2

In the Options dialog, GPU Settings section, is the "Automatically reset GPU clocking parameters" set? If set, when you stopping the mining software the Core Clock should be reset.

On the GPU Clocking tab for a selected miner - is the correct Core Clock not displayed even if you click the "Reload" button to update the display of the current clocking settings?

Thanks for the feedback.

Is it entries in the Awesome Miner log file you are referring to? I did find a few related to triggers but not many. Can you give an example and I will look into it in more detail? Thanks!

Thanks for the request - this one will be supported in the near future.

Hi Patrike, something wired if miner in "Managed Miner" mode. If i set a "GPU Clocking Profile when starting" (for example i set core offset 210) all ok, offset will be applied. Then i stop miner, uncheck "GPU Clocking Profile when starting" checkbox (or recreating "Managed Miner" and field "GPU Clocking Profile when starting" is empty) the old value for core ofset will be showed in "GPU clocking" tab. Looks like AM not clear old values if value will not be explicit overriden in this mode. Please check. AM 9.9.3
Regards.

This does work, I feel as though the 'detect change' or 'comparison' should instead be checkboxes, instead of radial buttons and could eliminate this, while being more intuitive and simplistic. So it could do both in one or either/or.

I don't know if you can do anything about the rulespam, but the comparison activates every 6s and keeps hitting the logs, which buries anything of value.