Awesome Miner development version 4.3.3 (preview of 4.4)
The get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates
Hi, Is it possible to download the development version from a link? One of my rigs does not like to update through the application updater for some reason but manual update has always worked. Thanks. Same here... Also even thought the update procedure has been completed my version is still 4.3.2 and still alerts that there is a new update... Also some of my antminers seem disconnected but not really I've updated the post above with direct download links. The most common reasons for upgrades to silently fail is that either Windows has pending updates, or that the Awesome Miner related Windows service "IntelliBreeze Software Maintenance Service" isn't running correctly. Windows and Defender likes to disable these kind of application services often these days for some reason. I will implement a workaround for the next release that will launch the MSI installer manually if needed. |
|
|
|
Awesome Miner development version 4.3.3 (preview of 4.4)- A profit profile can be configured with custom pools to use, independent of the global profit switching pools. - Improved bulk edit for External Miners to include profit switching settings - Display MAC address in the Summary tab for the selected miner - A miner can be converted from between being a Managed Miner and a Managed Profit Miner from the context menu. - Awesome Miner API method to set coin properties, for setting profitability of custom coins from external applications - Added three additional highlight colors for the miner list - Show total wallet balance in column header - Show profile hash rate for each entry in the Online Services tab - New Block Explorer for Ethereum Classic balance - XMRig mining software supported for CPU, AMD and nVidia mining of Cryptonight - Cast XMR miner can be included in the profit switcher - Claymore Cryptonight Miner 11.2 - DSTM Zcash Miner 0.5.8 - Cast XMR 0.8.1 - Correction to GPU mapping order for the GPU tab. This change may result in different order on some systems. - Correction to use defined coins with value specified in USD used together with the profit switcher - Minor corrections Important: Remote Agent must be upgraded as well. Once upgrading to this version, you cannot downgrade to an older version without all configuration being lost. The get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates. Direct download links: http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msihttp://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi
|
|
|
|
Do awesome miner let you check the SOL per WATT to check the efficency? I can't find it anywhere...
Also, I am having a daily income higher with EQUIHASH zclassic in awesome miner, but for some reason awesome miner keep switching to Claymore dual miner which in fact gives me a daily incomes lower...
Shouldn't awesome miner keep choosing automatically the best mining option based on the daily income?
I know they could be noob questions but since I am planning to buy this software I would like to have all the information about it... Anyone? Sol/Watt is currently not displayed. To get insight why the profit switcher selects a specific algorithm, right click on the miner and select View Details and go to the Profit switching tab. Please note that these hashrates and profit estimates are based on what is defined in the Profit profile. They may not match the actual hashrate and profit. If they are not matching, please use the Benchmark feature or manually edit the profit profile to ensure they match, otherwise the profit switcher may select a less profitable pool. thanks a lot for your helpful reply! Is it important in the PROFIT PROFILE to set also the power? By default it's set to 0w also after the benchmark test It's mainly people running the software at medium and large scale that fill in the power settings. You can get the profit switcher to get a bit more detailed in the decisions, but it's generally not a large impact. |
|
|
|
Fan speed is possible. Please use: stats.Fan1 + " / " + stats.Fan2 Individual hash rate is not supported. thanks a lot! as for Individual chip hash rate - is it not possible to fetch using some API? I thought you can grab everything that is shown on Miner status page. In the API's that returns information about miners (either all, or one specific), you can find this information if you search for "asicList" and look at the sub entries. http://www.awesomeminer.com/help/api.aspx |
|
|
|
Do awesome miner let you check the SOL per WATT to check the efficency? I can't find it anywhere...
Also, I am having a daily income higher with EQUIHASH zclassic in awesome miner, but for some reason awesome miner keep switching to Claymore dual miner which in fact gives me a daily incomes lower...
Shouldn't awesome miner keep choosing automatically the best mining option based on the daily income?
I know they could be noob questions but since I am planning to buy this software I would like to have all the information about it... Anyone? Sol/Watt is currently not displayed. To get insight why the profit switcher selects a specific algorithm, right click on the miner and select View Details and go to the Profit switching tab. Please note that these hashrates and profit estimates are based on what is defined in the Profit profile. They may not match the actual hashrate and profit. If they are not matching, please use the Benchmark feature or manually edit the profit profile to ensure they match, otherwise the profit switcher may select a less profitable pool. |
|
|
|
I've been using AM for a month now and I'm absolutely loving it. However, after the latest update (v4.3.2) my miners restart very often. Their Uptimes used to be in hours and even days, whereas now it's a rare occasion to see them reach one full hour.
Specifics:
Running Profit Miners with MPH as the only pool selected. Only allowing two algo's(cryptonight and equihash) And it's not that they would switch between the algos when they restart. They just stop mining Equihash and then start at it again.
I'm facing the same problem, but for me the miners restart exactly every 2.5 minutes and it would happen to all running miners at the same time (GPU and CPU). It's like something is forcing the miners to restart. Profit switching still works though at the interval that I have set. So the restarts every 2.5 minutes is not due to switching to a different algorithm. Even with profit switching is off and miners setup to mine one coin only, it would behave the same way. The general answer first: A later version of Awesome Miner often includes later versions of the mining software as well and these kind of crashes that happens after a while has often very little to do with Awesome Miner. To troubleshoot, is it a specific software like EWBF or Claymore Cryptonight that is crashing? Is it the only software that is instable, or what about the others? I did see your previous post that you could see this for both CPU and GPU mining. I would recommend to take a look at the rules you have in Awesome Miner. Also, is this on a remote computer via Remote Agent? I also noticed few lines of the log file in a previous post, but it was a little too short of information what happend just before those lines. Was it a crash that Awesome Miner detected and simply restarted the mining software? Was it a rule that triggered and forced a restart? Thanks for your reply. I will try to answer as much as I can. I ran each compatible mining software for my CPU/GPU. Specifically: - ccMiner 2.2.4 - DSTM Zcash Cuda Miner - CC Miner Alexis - EWBF Zcash Cuda Miner (did not restart every 2.5mins) - Excavator - CPU Miner opt 3.7.8 Only EWBF Zcash didn't restart regularly. So I have been running EWBF and ccMiner for past few days, with Miner restarts whenever ccMiner is selected by profit switcher. No rules enabled except for the 30 minutes in profit switcher. Today, I stopped the miners and tried a few things until I got the miners to be stable again no restarts! The last thing I did before the miners started to be stable was to re-enable SLI from Nvidia control panel, then disabled SLI back again. After that, miners have been running with no restarts. Finally, I know this may be very specific issue to my hardware / software setup, but I felt like I should contribute as a way to show my appreciation for the efforts of the developer of this app. Here's a full log showing one cycle when both miners restarted: 13-Jan-18 7:21:14 PM.978 [012] [S][ManagedMiner#3 - gpu] Stopping...
13-Jan-18 7:21:15 PM.994 [012] [S][ManagedMiner#3 - gpu] Performing stop
13-Jan-18 7:21:15 PM.994 [012] [S][ManagedMiner#3 - gpu] Stopping Mining Software
13-Jan-18 7:21:15 PM.994 [012] [S] Process already closed
13-Jan-18 7:21:17 PM.978 [028] [E]Failed to process API request (time: 1016 ms): summary
No connection could be made because the target machine actively refused it 127.0.0.1:4028
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] Starting...
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] Starting Mining Software
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] Setting up Miner Engine. Instance: 2
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] Engine Type: CcMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
13-Jan-18 7:21:18 PM.009 [012] [S]EngineSetup: CcMiner
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : GetStaticSortedPools, Enginetype: CcMiner, Algorithms: Blake2s, C11, CryptoNight, Decred, Groestl, Hmq1725, Lbry, Lyra2REv2, Lyra2z, Myriad-Groestl, NeoScrypt, Nist5, Quark, Qubit, Scrypt, SHA3, Skein, Skunkhash, Timetravel, Tribus, X11, X11Gost, X13, X14, X15, X17
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : GetStaticSortedPools, ignoring pool:stratum+tcp://europe.equihash-hub.miningpoolhub.com:17023, Equihash
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17012
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://europe.lyra2z-hub.miningpoolhub.com:17025
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17016
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17018
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17004
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17003
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:17024
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17005
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17001
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17014
13-Jan-18 7:21:18 PM.009 [012] [S][ManagedMiner#3 - gpu] : Adding pool: stratum+tcp://hub.miningpoolhub.com:17007
13-Jan-18 7:21:18 PM.009 [012] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
13-Jan-18 7:21:18 PM.041 [012] [S][ManagedMiner#3 - gpu] Added rule for: C:\Users\pythus\AppData\Local\AwesomeMiner\ccminer-2.2.4_2\ccminer-x64-2.2.4-cuda9\ccminer-x64.exe
13-Jan-18 7:21:18 PM.041 [012] [S][ManagedMiner#3 - gpu] C:\Users\pythus\AppData\Local\AwesomeMiner\ccminer-2.2.4_2\ccminer-x64-2.2.4-cuda9\ccminer-x64.exe -a neoscrypt -o stratum+tcp://hub.miningpoolhub.com:17012 -u pythusminer.gpu1 -p x -b 0.0.0.0:4029 (WindowMode: ConsoleFormat, EngineType: CcMiner, IsProfitMiner: True)
13-Jan-18 7:21:18 PM.041 [012] [S][ManagedMiner#3 - gpu] Configuration:
13-Jan-18 7:21:20 PM.547 [012] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
13-Jan-18 7:21:20 PM.563 [012] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
13-Jan-18 7:21:20 PM.563 [012] [S][ManagedMiner#3 - gpu] Mining Engine Process started, PID: 18524
13-Jan-18 7:21:22 PM.567 [012] [W][ManagedMiner#4 - cpu] process not running. Restarting...
13-Jan-18 7:21:22 PM.567 [012] [S][ManagedMiner#4 - cpu] Stopping...
13-Jan-18 7:21:23 PM.568 [012] [S][ManagedMiner#4 - cpu] Performing stop
13-Jan-18 7:21:23 PM.568 [012] [S][ManagedMiner#4 - cpu] Stopping Mining Software
13-Jan-18 7:21:23 PM.568 [012] [S] Process already closed
13-Jan-18 7:21:24 PM.118 [001] [S][ManagedMiner#3 - gpu] Interface connected
13-Jan-18 7:21:25 PM.568 [012] [S][ManagedMiner#4 - cpu] Starting...
13-Jan-18 7:21:25 PM.568 [012] [S][ManagedMiner#4 - cpu] Starting Mining Software
13-Jan-18 7:21:25 PM.568 [012] [S][ManagedMiner#4 - cpu] Setting up Miner Engine. Instance: 1
13-Jan-18 7:21:25 PM.568 [012] [S][ManagedMiner#4 - cpu] Engine Type: CpuMinerOpt, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
13-Jan-18 7:21:25 PM.568 [012] [S]EngineSetup: CpuMinerOpt
13-Jan-18 7:21:25 PM.569 [012] [S][ManagedMiner#4 - cpu] : Adding pool: europe.cryptonight-hub.miningpoolhub.com:20596
13-Jan-18 7:21:25 PM.570 [012] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
13-Jan-18 7:21:25 PM.600 [012] [S][ManagedMiner#4 - cpu] Added rule for: C:\Users\pythus\AppData\Local\AwesomeMiner\cpuminer-opt_1\cpuminer-opt-3.7.8-windows-v2\cpuminer-sse2.exe
13-Jan-18 7:21:25 PM.600 [012] [S][ManagedMiner#4 - cpu] C:\Users\pythus\AppData\Local\AwesomeMiner\cpuminer-opt_1\cpuminer-opt-3.7.8-windows-v2\cpuminer-sse2.exe -a cryptonight -o europe.cryptonight-hub.miningpoolhub.com:20596 -u pythusminer.etn -p x --api-remote -b 0.0.0.0:4028 (WindowMode: ConsoleFormat, EngineType: CpuMinerOpt, IsProfitMiner: False)
13-Jan-18 7:21:25 PM.601 [012] [S][ManagedMiner#4 - cpu] Configuration:
13-Jan-18 7:21:28 PM.130 [012] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
13-Jan-18 7:21:28 PM.137 [012] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
13-Jan-18 7:21:28 PM.138 [012] [S][ManagedMiner#4 - cpu] Mining Engine Process started, PID: 18708
13-Jan-18 7:21:33 PM.191 [001] [S][ManagedMiner#4 - cpu] Interface connected
13-Jan-18 7:23:44 PM.270 [012] [W][ManagedMiner#3 - gpu] process not running. Restarting...
13-Jan-18 7:23:44 PM.270 [012] [S][ManagedMiner#3 - gpu] Stopping...
13-Jan-18 7:23:45 PM.276 [012] [S][ManagedMiner#3 - gpu] Performing stop
13-Jan-18 7:23:45 PM.276 [012] [S][ManagedMiner#3 - gpu] Stopping Mining Software
13-Jan-18 7:23:45 PM.276 [012] [S] Process already closed Thanks for sharing the details. As you probably noticed already, what is happening here is that the mining process crashes and Awesome Miner detects that the process is no longer running. Also thanks for sharing the resolution - I will actually put that one in the GPU troubleshooting guide! |
|
|
|
Thanks a lot  seemed to help! Last thing - how in the love of god do you setup the balance tab? I cant figure it out.. Right now the feature is only intended for your coin address balance. In the future it will be for pool balance as well. http://www.awesomeminer.com/help/coinbalance.aspx |
|
|
|
I am having an issue with one of my miners and because the last issue had nothing to do with AM I will be a little more humble  the box is running win10, remote AM with a 480 and a furyx with latest amd drivers (I tried blockchain as well) Problem is about every 5 minutes mining just stops, it just closes on the remote host. Diagnostics just gives a blank screen. I have so far changed drivers, uninstalled and reinstalled AMR multiple times and still can't find the issue. Cards are -15 on power but not overclocked. They are not overheating either I watched closely. Windows defender has proper exclusions set and the only other program running is afterburner. No errors in windows log. AM will restart itself after a few minutes and go through the whole routine again. Any clues? "Diagnostics just gives a blank screen". While it's true that the console window is always blank when you run the diagnostics, the actual output is captured by Awesome Miner and presented after 20 - 30 seconds in Awesome Miner. Is this output indicating anything? In general the diagnostics is more helpful to find out why mining software isn't starting correctly. In your case it's probably more difficult as it's a crash after a while. Can you have a quick look at the troubleshooting guide for this scenario, and get back to us with the indicated logs? http://www.awesomeminer.com/help/troubleshooting-gpu.aspx |
|
|
|
A lot of users of AwesomeMiner lost money because miners are not switched if they are not returning anything. If a miner does not report new hasrate it shoudl be stopped. A few thousands users of AwesomeMiner are porting that lost a lot of money because NIST5 HASREFINERY bad reporting or unresponsive pools: https://bitcointalk.org/index.php?topic=2736744.0Solution would be to have an ability to switch the mining program if it is not responsive (could not connect because of DDOS or overloaded pool or other hardware errors from the miner). Also Awesome miner is reporting a lot more than we can actually see in our real daily income fromt he pools. I advise anyone to compute teh real money from the pool every day because the values from Awesome Miner are not the real ones, and you do a lot less money ! I am asking the developers what is their solution on situations like these? Thank you When reading the thread it mainly looks like the pool didn't report the full hashrate, while it from a mining software point of view looked perfectly fine with the hashrate. If the pool also reports that the shares are accepted to the mining software, it will be even more difficult for Awesome Miner to detect that something is wrong. Awesome Miner itself doesn't have any connection to the pool. It uses the API's for profit information, but often this is a separate server compared to what the mining software connect to. If the API is down is not always the same as the pool itself is down. Looking at the actual money you make at the pool isn't a fully stable solution either. You can mine a coin where you don't find any blocks for a long time, so you will not get any payouts for a long period of time and it's still fine because when you eventually find a block you get a high payout. In the past it also happens that these pools changes their unit (MH/s vs GH/s) of reporting in their API's, so it's yet another scenario that makes it less stable to react on that from the pool API. I fully agree that it would make sense if Awesome Miner could detect these scenarios and take action, but we also need to keep in mind that it can be a quite difficult scenario to detect. If Awesome Miner tries to be "too smart", it may give unexpected behaviors as well. I will investigate this further and I'm open for any suggestions. Thanks! You are not right. Try to see what happens if one pool is under DDOS attack and no shares are submitted. AwesomeMiner remains stuck for hours with the last value submitted from the report instead of stopping that miner. An option with a value we can configure to disconnect that miner / pool if it does not report any new values for a number of minutes or is reporting the same value, will help us stop loosing thousands of dollars every minute. You have a big responsibility, you know? What pools do you use that are reliable and with good 24h stat profit ? Can you please integrate into to software other bigger and more reliable pools? Also I think price statistics could be improved to take prices from more exchang s with more volume on various less known coins that lead to bad coin mining, is it possible ? If no shares are submitted we are talking about a completely different scenario than the thread you linked to where the shares were submitted. In case of no accepted share progress, Awesome Miner can at least detect that using the predefined rule "Accept progress". You should at least be able to get notifications for this. What is required from Awesome Miner is to be able to take further action in addition to the notifications, and that's what I will look at. In addition to the most popular mining pools that are predefined in Awesome Miner, you can add any mining pool yourself. |
|
|
|
Hello all! Just started mining with AwesomeMiner with MiningPoolHub. It appears that AwseomeMiner isn't switching algos based on my settings. In Options-Profit Switching, I have it set to 45 minutes and my worker is listed correctly (username.worker name) but I've noticed where it will mine the same coin for hours.
In MPH, I have my Worker Login, Worker Password and Job set to 'Account's default job'.
Am I missing something?
Even If I manually stop the miner and restart it, It will go back mining the on the same algo (even if a different one is listed as top one to mine on MiningPoolHub).
To get insight why the profit switcher selects a specific algorithm, right click on the miner and select View Details and go to the Profit switching tab. Please note that these hashrates and profit estimates are based on what is defined in the Profit profile. They may not match the actual hashrate and profit. If they are not matching, please use the Benchmark feature or manually edit the profit profile to ensure they match, otherwise the profit switcher may select a less profitable pool. |
|
|
|
Hello, I must do something wrong with adding coin from whattomine... I want to add Bitsend to the listed coins. What i did : - Be sure Xevan algorithm is in latest AM --> OK - Added http://whattomine.com/coins/201.json in the list in Statistics --> OK On Whattomine website, coin is marked as "Active". When i click "update" in coins tab, nothing ! I tried quit AM and launch again, still nothing... What am I missing ? Awesome Miner didn't process this algorithm correctly from WhatToMine. I've made a correction for it now that will be included in the next release. |
|
|
|
I've been using AM for a month now and I'm absolutely loving it. However, after the latest update (v4.3.2) my miners restart very often. Their Uptimes used to be in hours and even days, whereas now it's a rare occasion to see them reach one full hour.
Specifics:
Running Profit Miners with MPH as the only pool selected. Only allowing two algo's(cryptonight and equihash) And it's not that they would switch between the algos when they restart. They just stop mining Equihash and then start at it again.
I'm facing the same problem, but for me the miners restart exactly every 2.5 minutes and it would happen to all running miners at the same time (GPU and CPU). It's like something is forcing the miners to restart. Profit switching still works though at the interval that I have set. So the restarts every 2.5 minutes is not due to switching to a different algorithm. Even with profit switching is off and miners setup to mine one coin only, it would behave the same way. The general answer first: A later version of Awesome Miner often includes later versions of the mining software as well and these kind of crashes that happens after a while has often very little to do with Awesome Miner. To troubleshoot, is it a specific software like EWBF or Claymore Cryptonight that is crashing? Is it the only software that is instable, or what about the others? I did see your previous post that you could see this for both CPU and GPU mining. I would recommend to take a look at the rules you have in Awesome Miner. Also, is this on a remote computer via Remote Agent? I also noticed few lines of the log file in a previous post, but it was a little too short of information what happend just before those lines. Was it a crash that Awesome Miner detected and simply restarted the mining software? Was it a rule that triggered and forced a restart? |
|
|
|
Fan speed is possible. Please use: stats.Fan1 + " / " + stats.Fan2 Individual hash rate is not supported. |
|
|
|
sgminer and compatible templates aren't setting up the api automatically and need --api-listen added to the command line. Seems to be a bug.
Awesome Miner generates a sgminer configuration file and inside all the API parameters are specified together with pool information. For that reason it's not passed via the command line. |
|
|
|
is there a way to see each and every GPU temp on this screen?
Yes. Please go to Options dialog, General section and set "Temperature display" to "All devices temperatures". |
|
|
|
A lot of users of AwesomeMiner lost money because miners are not switched if they are not returning anything. If a miner does not report new hasrate it shoudl be stopped. A few thousands users of AwesomeMiner are porting that lost a lot of money because NIST5 HASREFINERY bad reporting or unresponsive pools: https://bitcointalk.org/index.php?topic=2736744.0Solution would be to have an ability to switch the mining program if it is not responsive (could not connect because of DDOS or overloaded pool or other hardware errors from the miner). Also Awesome miner is reporting a lot more than we can actually see in our real daily income fromt he pools. I advise anyone to compute teh real money from the pool every day because the values from Awesome Miner are not the real ones, and you do a lot less money ! I am asking the developers what is their solution on situations like these? Thank you When reading the thread it mainly looks like the pool didn't report the full hashrate, while it from a mining software point of view looked perfectly fine with the hashrate. If the pool also reports that the shares are accepted to the mining software, it will be even more difficult for Awesome Miner to detect that something is wrong. Awesome Miner itself doesn't have any connection to the pool. It uses the API's for profit information, but often this is a separate server compared to what the mining software connect to. If the API is down is not always the same as the pool itself is down. Looking at the actual money you make at the pool isn't a fully stable solution either. You can mine a coin where you don't find any blocks for a long time, so you will not get any payouts for a long period of time and it's still fine because when you eventually find a block you get a high payout. In the past it also happens that these pools changes their unit (MH/s vs GH/s) of reporting in their API's, so it's yet another scenario that makes it less stable to react on that from the pool API. I fully agree that it would make sense if Awesome Miner could detect these scenarios and take action, but we also need to keep in mind that it can be a quite difficult scenario to detect. If Awesome Miner tries to be "too smart", it may give unexpected behaviors as well. I will investigate this further and I'm open for any suggestions. Thanks! |
|
|
|
Is profit switching supposed to ignore user-defined coins? It always calculates them as $0.00 even though they are the most profitable on the coins tab for the same profit profile  Profit Miners will use the Online Services tab statistics for services like Nicehash, MPH, zpool, etc. It's only if you activate the custom pool option and of course, a pool group with the coins you want to switch between that AM will use the Coins tab statistics. User-defined coins need to have all the appropriate data setup in the User Defined Coins section of the Coins & Statistics tab of the Options. AM depends on this data to help it calculate how much revenue you potentially will generate based upon your hashrate. Also, if you are going to do profit switching, it's important to do benchmarking so that AM can make some decisions on how much hashrate your rigs will run and compare that to the various coins and algos. Thanks for the reply. I promise I did all that stuff. The bug is actually that if you specify the value in USD and leave the value in BTC as Zero, the profit miner still uses the 0 BTC to calculate profit, while the coins tab correctly uses the USD. Please verify and fix if possible -- USD has more digits for shitcoins, so I assume it's more accurate to use that. ex. ITNS: $0.053555 USD / 0.00000386 BTC Also please let us use cast_xmr in the profit miner in the next release, and update it to 0.81 to fix the bug with the latest AMD drivers. It helps me get rid of one extra template, at least. 0.81 is available on the official website. http://www.gandalph3000.com/download/cast_xmr-vega-win64_081.zipThanks for reporting this I will correct the User Defined coins for the USD scenario together with the profit switcher I will also include Cast XMR 0.8.1. I actually didn't see that one before as their Bitcointalk thread only listed 0.8. It will also be possible to include in the profit switcher, even if it isn't included by default. |
|
|
|
|
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
|
|
|
|
Hi
Could you add XMRig mining software for mining cryptonight for cpu. It has a api in place which could be used with awesome miner.
Thanks
I've been receiving a number of requets on this one. So it's likely that the next mining softare added will be XMRig. |
|
|
|
I tried searching this epic thread but came up short so I apologize if this is a common easy fix...
For some reason the temperature of my AMD cards is not showing up in Awesome Miner. It was showing for all my cards when I first started using AM but somehow it has disappeared. The Nvidia temps still show up as the are supposed to.
Is there a setting somewhere I have overlooked?
Thanks!
Please check this first: http://www.awesomeminer.com/help/gpumapping.aspxThere can also be instances where Awesome Miner is unable to read the GPU sensors. |
|
|
|
|
Show Posts
