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.
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 <ETC-ADDRESS> --password x --algorithm sha512_256d_radiant --pool stratum+tcp://stratum-eu.rplant.xyz:7086 --wallet <RADIANT-ADDRESS> --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, looks like in your example, you use Managed Miner mode, but i am try in Managed Profit mode. Arguments for secondary coin (Radiant) i put in Profit profile in "command line parameters" field for algorithm Dynex. And this combination not work for me. Miner start mining only Radiant. Diagnostic show me, that the generated command string contains only one --algorithm parameter and this is Radiant, which i have put in "command line parameters". If i try to add a additional --algorithm dynex in "command line parameters" (before radiant) then i recive error from SRBMulti: You defined less pools than algorithms. I simple cant use dual mining due AM overwrite first --algorithm with --algorithm from my command line instead to add next algo defenition. Normaly, i am awaiting that the AM use main algo from my pool definition and additional algo i define in command lines parameters field. Try self this scenario in Managed Profit mode. Regards Thanks for the update. I think we run into the limitation of the Profit switcher and dual mining with other primary algorithms than EtHash. It's unfortunately limited here to reduce the number of possible combinations. These days I understand that it may not be good enough where more and more algorithm combinations are supported for dual mining via a number of mining software.
|
|
|
wrong syntax for dualmining ironfish with teamredminer. The argument for mining ironfish alone is -a ironfish. This is ok, but for dual mining the arguments are --iron and --iron_end but awesomeminer use --ironfish and --ironfish_end but thats wrong and doesn´t work.
Thanks for the report - this will be corrected in the next release.
|
|
|
Awesome Miner version 9.9.7
Corrections - Correction to profit switching start command
|
|
|
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
Hello. After this update, the launch, the restart button and the profit switching do not work. I will publish v9.9.7 in a moment that hopefully will resolve this issue.
|
|
|
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
|
|
|
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.
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 <ETC-ADDRESS> --password x --algorithm sha512_256d_radiant --pool stratum+tcp://stratum-eu.rplant.xyz:7086 --wallet <RADIANT-ADDRESS> --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?
|
|
|
For the correctness of the profit (like in wattomine), I set the profit factor for the pool 4300000000
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.
|
|
|
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!
Hello and thanks for the comments. I've pushed a mining software definition for this.
|
|
|
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.
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.
|
|
|
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
|
|
|
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.
Good point. I will make sure the next release will support 10-04 and similar expressions. Like you noticed it isn't supported today.
|
|
|
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.
In the next release you will find "Algorithm" as one of the properties in the "Miner Property" trigger.
|
|
|
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*<?xml version="1.0" encoding="utf-16"?> <StatusUpdate xmlns:xsd=" http://www.w3.org/2001/XMLSchema" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"> <MinerId>60</MinerId> <Privileged>false</Privileged> <ResponseTime>0</ResponseTime> <MinerStatus> <SecondsSinceStart>303149</SecondsSinceStart> <KHashAvg>0</KHashAvg> <KHash5s>0</KHash5s> <SecondKHash5s>0</SecondK...... and so on. The rest look like it should. It look like the API report is not complete, maybe that is the reason for no stats? Hi, Yes, that API response is broken and this cannot be resolved from an Awesome Miner point of view.
|
|
|
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.
Thanks for testing the new OneZeroMiner. I will make sure this will be corrected in the next update.
|
|
|
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
- 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?!? 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.
|
|
|
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
|
|
|
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.
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?
|
|
|
Aye... Thanks.
Errr... I don't think the variable change thing really solves the original problem. The problem was it would constantly trigger if conditions were met, not only once when they're first met.
So I have two different variables, and a rule that triggers turning miners off if one variable is true. Then I have another rule when both variables are false that turns things back on. However, if it's setup normally the miners will keep resetting (turning off) as long as one of the variables is true and with the 'detect change' wont be able to know the correct state that both need to be in to turn things back on.
Thanks for the feedback. If I understand correctly, your rules looks something like this today. Rule#1: If Var1=true or Var2=true -> Stop miners Rule#2: If Var1=false and Var2=false -> Start miners Do you think this concept could work? Rule#1: If Var1=true or Var2=true -> Set Var3=true Rule#2: If Var1=false and Var2=false -> Set Var3=false Rule#3: If Var3=true and Var3 has changed -> Stop miners Rule#4: If Var3=false and Var3 has changed -> Start miners This way the actions for Rule#3 and #4 should only run once. 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. 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!
|
|
|
Hi Patrike, noncerpro miner have rebranding, now this miner is onezerominer. Supports DynexSolve algo. Please integrate in Awesome Miner this miner. Hashrate is much better with this miner. https://github.com/OneZeroMiner/onezerominerRegards Thanks for the request - this one will be supported in the near future.
|
|
|
Hi Patrik, or anyone who knows this And sorry if this was answered already somewhere, couldn't find it... Just playing around with the good old Profit Profiles and the Profit Switcher. How does AM knows the second coin to calculate the profit in the Profit Switcher if I can only set the hashrates and wattages? Just as an example: I want to use Gminer to dual mine ERGO (Autolykos 2) and KASPA together, but also solo mine just KASPA, whatever combination is just the highest. The Profit Switcher only shows me the profit of ERGO and the profit of KASPA, but not the profit of ERGO+KASPA. Sorry, but I don't get it... Is this possible with the profit switcher right now? Or do I have to use the Managed Miner and switch it by hand with my profiles? What you point out here is simply a limitation in the profit switching design right now. It was initially for the days where Ethereum was the primary coin and in addition to this could could set a dual hashrate/power for a few secondary coins. Today some software like SrbMiner-Multi can do dual mining of almost any combination of coins - so in theory you could have something like 1000 combinations. The idea is to improve the profit switcher to handle scenarios where the primary coin is something else than EtHash.
|
|
|
|