XMR STAK Setup.
Has anyone set this up? Can you please advise if so.
Thank you
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 341. (Read 703146 times)
May 29, 2018, 08:56:12 AM
May 29, 2018, 06:10:57 AM
Hi,
Many thanks for the detailed description.
For pools that only should use the miner specific worker name part in the password field, and you don't want this added after the wallet for example, you can open the Properties of the pool and go to the Advanced section. Please try to check "Ignore 'Add to worker name' on miner" and see if that resolves any of your scenarios.
For the difficulty configuration, I agree that something should be added to each miner for this. Maybe it should even be a general concept of variables you can define on each miner, so you can add your [UserDefinedDifficulty] and assign it values - and then be able to reference it from either the worker name or the password field in the pool.
Thanks!
Thank you for consideration! yes, currently I have those problematic unconventional pools all with ignore checked
May 29, 2018, 04:08:05 AM
Hi Patrik,
One request in addition to "add to workername" that's already implemented, is the passing of difficulty parameter in a similar fashion
a good number of pools allow passing of the static difficulty parameter (or suggested difficulty) through mostly the password field with (d=xxx), some pools, especially lots of the cryptonight implementations, append them to the worker name field (-u parameter in common miners) via their own defined parameters (some uses "+", some uses "." for the ones I've came across)
I managed to use the [MinerWorker] method to assign worker names, it works perfectly but is also buggy atm:
For example, the pool (Cryptoknight.CC) uses the following format (which I use in the pool setup):
Worker name: WalletAddress.[UserDefinedDifficulty]
Password: [MinerWorker]
if I specify the difficulty with custom delimiter (field left empty), AM will parse the command as follows:
As you can see, that worker name is being parsed twice and result in pool reading (probably "null") error on the difficulty and I get rejected shares as well as 10min IP ban LoL if I kept this carry on long enough.
If I specify using default "." delimiter in the pool setting, AM parses following:
This time, [MinerWorker] still gets parsed twice, but the pool in this case will simply give me an auth error and I will not be able to mine as well.
***
Proposal:
1. In pool settings, if [MinerWorker] is defined in the password field, steps are taken to eliminate double parsing the parameter to the Worker field entirely
2. adding new parameter [UserDefinedDifficulty] in the mechanics similar to [MinerWorker] that we can specify for each Miner in the same way as worker name, this sometimes helps when pool's vardiff changes too erratically (say, optimal for 1 AM miner is 150000 in CN-Heavy, the pool shoots it up to 1mil results in no shares found for 10 min till it drops slowly), this is supposedly very useful when rigs/miners have varying hash power but profit switching interval becomes > than share submitted = losing efficiency. Also (haven't tested out yet) ppl say it's good to define a (suggested) static difficulty where pool supports it for chaotic algos like X16R per rig/miner.
Cheers!
Hi,One request in addition to "add to workername" that's already implemented, is the passing of difficulty parameter in a similar fashion
a good number of pools allow passing of the static difficulty parameter (or suggested difficulty) through mostly the password field with (d=xxx), some pools, especially lots of the cryptonight implementations, append them to the worker name field (-u parameter in common miners) via their own defined parameters (some uses "+", some uses "." for the ones I've came across)
I managed to use the [MinerWorker] method to assign worker names, it works perfectly but is also buggy atm:
For example, the pool (Cryptoknight.CC) uses the following format (which I use in the pool setup):
Worker name: WalletAddress.[UserDefinedDifficulty]
Password: [MinerWorker]
if I specify the difficulty with custom delimiter (field left empty), AM will parse the command as follows:
Code:
-u WalletAddress.[UserDefinedDifficulty][MinerWorker] -p [MinerWorker]
As you can see, that worker name is being parsed twice and result in pool reading (probably "null") error on the difficulty and I get rejected shares as well as 10min IP ban LoL if I kept this carry on long enough.
If I specify using default "." delimiter in the pool setting, AM parses following:
Code:
-u WalletAddress.[MinerWorker] -p [MinerWorker]
This time, [MinerWorker] still gets parsed twice, but the pool in this case will simply give me an auth error and I will not be able to mine as well.
***
Proposal:
1. In pool settings, if [MinerWorker] is defined in the password field, steps are taken to eliminate double parsing the parameter to the Worker field entirely
2. adding new parameter [UserDefinedDifficulty] in the mechanics similar to [MinerWorker] that we can specify for each Miner in the same way as worker name, this sometimes helps when pool's vardiff changes too erratically (say, optimal for 1 AM miner is 150000 in CN-Heavy, the pool shoots it up to 1mil results in no shares found for 10 min till it drops slowly), this is supposedly very useful when rigs/miners have varying hash power but profit switching interval becomes > than share submitted = losing efficiency. Also (haven't tested out yet) ppl say it's good to define a (suggested) static difficulty where pool supports it for chaotic algos like X16R per rig/miner.
Cheers!
Many thanks for the detailed description.
For pools that only should use the miner specific worker name part in the password field, and you don't want this added after the wallet for example, you can open the Properties of the pool and go to the Advanced section. Please try to check "Ignore 'Add to worker name' on miner" and see if that resolves any of your scenarios.
For the difficulty configuration, I agree that something should be added to each miner for this. Maybe it should even be a general concept of variables you can define on each miner, so you can add your [UserDefinedDifficulty] and assign it values - and then be able to reference it from either the worker name or the password field in the pool.
Thanks!
May 29, 2018, 03:26:10 AM
Thank you very much for this great update, I love seeing so many coins to try.
I'm going to tell you a little bug, which is very annoying, at least for me.
A few days ago I suggested that there be a form to adapt the pool gain, since some estimate low and others high. So if you estimate 100 coins and get 50, it would be 0.5 to have 50%. Something like this capture
It works well, the program takes it into account for the Auto switch. You can see in the following image, where I display the autoswitch menu and make PRTX 0.0033 but just in the window below, where are the rigs, mark 0.13 or similar, it does not look very good. I mean, if you take it into account but it is not reflected in the statistics of the rigs, that leads to confusion.
And in the main dashboar it is not updated either. In this case this pool needs a correction of 73%, it gives me an exaggeratedly high number.
I insist that for the Switch if you get the price correctly with the change that I make in the pool, but in the other places it does not, and that does not make sense. The earnings information by day, month, or by rig should be in line with the correction you have applied to the group.
I hope you understand what I want to explain, it is incongruous, it has no logic.
Right now this setting is only for making a pool more/less profitable from a profit switcher point of view, which is also the reason why it's listed below a section called "Profit switching settings".I'm going to tell you a little bug, which is very annoying, at least for me.
A few days ago I suggested that there be a form to adapt the pool gain, since some estimate low and others high. So if you estimate 100 coins and get 50, it would be 0.5 to have 50%. Something like this capture
It works well, the program takes it into account for the Auto switch. You can see in the following image, where I display the autoswitch menu and make PRTX 0.0033 but just in the window below, where are the rigs, mark 0.13 or similar, it does not look very good. I mean, if you take it into account but it is not reflected in the statistics of the rigs, that leads to confusion.
And in the main dashboar it is not updated either. In this case this pool needs a correction of 73%, it gives me an exaggeratedly high number.
I insist that for the Switch if you get the price correctly with the change that I make in the pool, but in the other places it does not, and that does not make sense. The earnings information by day, month, or by rig should be in line with the correction you have applied to the group.
I hope you understand what I want to explain, it is incongruous, it has no logic.
I do understand your point and the idea is to expand this concept to be for profit display as well. This is however a bit complex, because if you have two pools with the same URL but different factors defined, Awesome Miner needs to figure out which pool you actually are mining on. For External Miners that's close to impossible, but for Managed Miners it's possible to make good guesses.
May 29, 2018, 03:14:55 AM
Patrike, I won't tested the SRB's config yes (i'm at work) but I want to ask for somethin I couldn't find:
Is there a way to track the "worker path" through the day/week?
Explaining:
Sometimes I think pool isn't being "fair" with me. I can see the satoshis earned in the last 24h, but I can't see (easily) if my cards was full time at that pool or I dont want to check every pool to check how many time i mined for each.
Sorry my bad english?
This is currently not supported, but I understand your request. Is there a way to track the "worker path" through the day/week?
Explaining:
Sometimes I think pool isn't being "fair" with me. I can see the satoshis earned in the last 24h, but I can't see (easily) if my cards was full time at that pool or I dont want to check every pool to check how many time i mined for each.
Sorry my bad english?
May 29, 2018, 03:13:55 AM
Thanks for the updates! Love the new dashboard.
For BMiner, can AM somehow incorporate this automatically? It's in the release notes for BMiner 8.0.
* Add scripts to download third party software OhGodAnETHlargementPill to improve Ethereum mining performance on GTX 1080/1080Ti.
https://www.bminer.me/releases/
Possibly, but I've not investigated this one in detail yet. Already today you can run any command before and after stopping a miner. Using the Upload Software feature it should also be possible to deploy this exe-file to a large number of miners. For BMiner, can AM somehow incorporate this automatically? It's in the release notes for BMiner 8.0.
* Add scripts to download third party software OhGodAnETHlargementPill to improve Ethereum mining performance on GTX 1080/1080Ti.
https://www.bminer.me/releases/
May 29, 2018, 03:11:32 AM
Thank you for the frequent and regular updates.
Since bminer now supports Ethereum and also Dual-Mining, would it be possible to add support for this?
Yes, Bminer Ethereum will be supported at some point. It's on the list of features to implement. Since bminer now supports Ethereum and also Dual-Mining, would it be possible to add support for this?
May 28, 2018, 09:33:17 PM
Hi Patrik,
One request in addition to "add to workername" that's already implemented, is the passing of difficulty parameter in a similar fashion
a good number of pools allow passing of the static difficulty parameter (or suggested difficulty) through mostly the password field with (d=xxx), some pools, especially lots of the cryptonight implementations, append them to the worker name field (-u parameter in common miners) via their own defined parameters (some uses "+", some uses "." for the ones I've came across)
I managed to use the [MinerWorker] method to assign worker names, it works perfectly but is also buggy atm:
For example, the pool (Cryptoknight.CC) uses the following format (which I use in the pool setup):
Worker name: WalletAddress.[UserDefinedDifficulty]
Password: [MinerWorker]
if I specify the difficulty with custom delimiter (field left empty), AM will parse the command as follows:
As you can see, that worker name is being parsed twice and result in pool reading (probably "null") error on the difficulty and I get rejected shares as well as 10min IP ban LoL if I kept this carry on long enough.
If I specify using default "." delimiter in the pool setting, AM parses following:
This time, [MinerWorker] still gets parsed twice, but the pool in this case will simply give me an auth error and I will not be able to mine as well.
***
Proposal:
1. In pool settings, if [MinerWorker] is defined in the password field, steps are taken to eliminate double parsing the parameter to the Worker field entirely
2. adding new parameter [UserDefinedDifficulty] in the mechanics similar to [MinerWorker] that we can specify for each Miner in the same way as worker name, this sometimes helps when pool's vardiff changes too erratically (say, optimal for 1 AM miner is 150000 in CN-Heavy, the pool shoots it up to 1mil results in no shares found for 10 min till it drops slowly), this is supposedly very useful when rigs/miners have varying hash power but profit switching interval becomes > than share submitted = losing efficiency. Also (haven't tested out yet) ppl say it's good to define a (suggested) static difficulty where pool supports it for chaotic algos like X16R per rig/miner.
Cheers!
One request in addition to "add to workername" that's already implemented, is the passing of difficulty parameter in a similar fashion
a good number of pools allow passing of the static difficulty parameter (or suggested difficulty) through mostly the password field with (d=xxx), some pools, especially lots of the cryptonight implementations, append them to the worker name field (-u parameter in common miners) via their own defined parameters (some uses "+", some uses "." for the ones I've came across)
I managed to use the [MinerWorker] method to assign worker names, it works perfectly but is also buggy atm:
For example, the pool (Cryptoknight.CC) uses the following format (which I use in the pool setup):
Worker name: WalletAddress.[UserDefinedDifficulty]
Password: [MinerWorker]
if I specify the difficulty with custom delimiter (field left empty), AM will parse the command as follows:
Code:
-u WalletAddress.[UserDefinedDifficulty][MinerWorker] -p [MinerWorker]
As you can see, that worker name is being parsed twice and result in pool reading (probably "null") error on the difficulty and I get rejected shares as well as 10min IP ban LoL if I kept this carry on long enough.
If I specify using default "." delimiter in the pool setting, AM parses following:
Code:
-u WalletAddress.[MinerWorker] -p [MinerWorker]
This time, [MinerWorker] still gets parsed twice, but the pool in this case will simply give me an auth error and I will not be able to mine as well.
***
Proposal:
1. In pool settings, if [MinerWorker] is defined in the password field, steps are taken to eliminate double parsing the parameter to the Worker field entirely
2. adding new parameter [UserDefinedDifficulty] in the mechanics similar to [MinerWorker] that we can specify for each Miner in the same way as worker name, this sometimes helps when pool's vardiff changes too erratically (say, optimal for 1 AM miner is 150000 in CN-Heavy, the pool shoots it up to 1mil results in no shares found for 10 min till it drops slowly), this is supposedly very useful when rigs/miners have varying hash power but profit switching interval becomes > than share submitted = losing efficiency. Also (haven't tested out yet) ppl say it's good to define a (suggested) static difficulty where pool supports it for chaotic algos like X16R per rig/miner.
Cheers!
May 28, 2018, 04:50:43 PM
Patrike, thanks a lot for minimizing bottom tab!
May 28, 2018, 04:27:21 PM
Thank you very much for this great update, I love seeing so many coins to try.
I'm going to tell you a little bug, which is very annoying, at least for me.
A few days ago I suggested that there be a form to adapt the pool gain, since some estimate low and others high. So if you estimate 100 coins and get 50, it would be 0.5 to have 50%. Something like this capture
It works well, the program takes it into account for the Auto switch. You can see in the following image, where I display the autoswitch menu and make PRTX 0.0033 but just in the window below, where are the rigs, mark 0.13 or similar, it does not look very good. I mean, if you take it into account but it is not reflected in the statistics of the rigs, that leads to confusion.
And in the main dashboar it is not updated either. In this case this pool needs a correction of 73%, it gives me an exaggeratedly high number.
I insist that for the Switch if you get the price correctly with the change that I make in the pool, but in the other places it does not, and that does not make sense. The earnings information by day, month, or by rig should be in line with the correction you have applied to the group.
I hope you understand what I want to explain, it is incongruous, it has no logic.
I'm going to tell you a little bug, which is very annoying, at least for me.
A few days ago I suggested that there be a form to adapt the pool gain, since some estimate low and others high. So if you estimate 100 coins and get 50, it would be 0.5 to have 50%. Something like this capture
It works well, the program takes it into account for the Auto switch. You can see in the following image, where I display the autoswitch menu and make PRTX 0.0033 but just in the window below, where are the rigs, mark 0.13 or similar, it does not look very good. I mean, if you take it into account but it is not reflected in the statistics of the rigs, that leads to confusion.
And in the main dashboar it is not updated either. In this case this pool needs a correction of 73%, it gives me an exaggeratedly high number.
I insist that for the Switch if you get the price correctly with the change that I make in the pool, but in the other places it does not, and that does not make sense. The earnings information by day, month, or by rig should be in line with the correction you have applied to the group.
I hope you understand what I want to explain, it is incongruous, it has no logic.
May 28, 2018, 01:33:55 PM
Patrike, I won't tested the SRB's config yes (i'm at work) but I want to ask for somethin I couldn't find:
Is there a way to track the "worker path" through the day/week?
Explaining:
Sometimes I think pool isn't being "fair" with me. I can see the satoshis earned in the last 24h, but I can't see (easily) if my cards was full time at that pool or I dont want to check every pool to check how many time i mined for each.
Sorry my bad english?
Is there a way to track the "worker path" through the day/week?
Explaining:
Sometimes I think pool isn't being "fair" with me. I can see the satoshis earned in the last 24h, but I can't see (easily) if my cards was full time at that pool or I dont want to check every pool to check how many time i mined for each.
Sorry my bad english?
May 28, 2018, 12:03:13 PM
Thanks for the updates! Love the new dashboard.
For BMiner, can AM somehow incorporate this automatically? It's in the release notes for BMiner 8.0.
* Add scripts to download third party software OhGodAnETHlargementPill to improve Ethereum mining performance on GTX 1080/1080Ti.
https://www.bminer.me/releases/
For BMiner, can AM somehow incorporate this automatically? It's in the release notes for BMiner 8.0.
* Add scripts to download third party software OhGodAnETHlargementPill to improve Ethereum mining performance on GTX 1080/1080Ti.
https://www.bminer.me/releases/
May 28, 2018, 09:47:48 AM
Hi,
After applying fan fix firmware, awesomeminer doesn't show the temperature anymore for B3 miners.
https://support.bitmain.com/hc/en-us/articles/360004733393-B3-Firmware-Upgrade-Instructions
Thank you
From what I noticed a few days ago, the latest B3 firmware changed these miners from telling they are "Antminer B3" to only say "Antminer" and I think this is a bug in the firmware.After applying fan fix firmware, awesomeminer doesn't show the temperature anymore for B3 miners.
https://support.bitmain.com/hc/en-us/articles/360004733393-B3-Firmware-Upgrade-Instructions
Thank you
The latest development version (v.5.0.4) included a adjustment to this, so it should show the correct temperature readings again.
Thank you very much, it did fix the issue.
May 28, 2018, 09:05:57 AM
Thank you for the frequent and regular updates.
Since bminer now supports Ethereum and also Dual-Mining, would it be possible to add support for this?
Since bminer now supports Ethereum and also Dual-Mining, would it be possible to add support for this?
May 28, 2018, 07:12:58 AM
I and other people are suffering some erratic failures with the AW api, with the extension of AW coin update. I know it's a separate development, but it seems that AW sometimes fails, and when it happens it's a failure that stays for days.
I have reinstalled the AWCU extension, I have reinstalled the latest version of AW beta. And it does not work.
This afternoon the system worked, but when I was mining with the same machine that has AW installed, I launched the AWCU currency updater, and gave that error, and I can not eliminate it.
The other time was an error that also disappeared only after the last update. I do not know if there will be a relationship with your API.
This is an exception in the coin updater so it needs to be invetigated from that point of view.I have reinstalled the AWCU extension, I have reinstalled the latest version of AW beta. And it does not work.
This afternoon the system worked, but when I was mining with the same machine that has AW installed, I launched the AWCU currency updater, and gave that error, and I can not eliminate it.
The other time was an error that also disappeared only after the last update. I do not know if there will be a relationship with your API.
patrike, In the new version is SRBMiner's config.txt override allowed per algorithm?
EDIT: At the "mining software" section my question is answered.
Please give the new feature to configure the config.txt file per algorithm a try, and let me know any feedback you have. In the SRBMiner configuration, the "Default" section will be used unless you override it for one of the other algorithms.
May 28, 2018, 06:33:30 AM
I and other people are suffering some erratic failures with the AW api, with the extension of AW coin update. I know it's a separate development, but it seems that AW sometimes fails, and when it happens it's a failure that stays for days.
I have reinstalled the AWCU extension, I have reinstalled the latest version of AW beta. And it does not work.
This afternoon the system worked, but when I was mining with the same machine that has AW installed, I launched the AWCU currency updater, and gave that error, and I can not eliminate it.
The other time was an error that also disappeared only after the last update. I do not know if there will be a relationship with your API.
patrike, In the new version is SRBMiner's config.txt override allowed per algorithm?
EDIT: At the "mining software" section my question is answered.
May 28, 2018, 06:27:02 AM
Awesome Miner Version 5.1
GPU mining
--- Improved CcMiner API processing for differents units of reporting for GPU clock, memory clock and power usage
--- SRBMiner configuration page to override config.txt via a Profit profile
ASIC mining
--- Improved detection of Antminer B3 with latest firmware
Configuration
--- Included predefined profit profile for Intel CPU mining
--- Managed Hosts can be disabled, resulting in all related Managed Miners being disabled will be ignored by the rules and no remote connection will be made
--- The list of Managed Hosts in the Options dialog has been improved to include the number of related Managed Miners and a button to find hosts without miners
--- Added variable [MinerWorker] for the password field of pools, to include the 'Add to worker name' part of a miner in the password field
--- The Bulk Edit feature for miners in the Options dialog are accessible directly from the miner list
--- Profit profile can be configured to be excluded from the global setting to ignore pools with no accepted shares
--- Changed predefined Bytecoin algorithm to Cryptonight
--- Improved detection of Managed Hosts duplicates
--- API connection retry can be configured via the Options dialog, Advanced section, to better handle poor network connections
Features and integration
--- CoinCalculators.io added as a new coin statistics provider
--- Multiple coin statistics providers can be selected and used at the same time
--- Tags for miners, where each miner can be assigned one or more tags and the miner list can be filtered based on tags
--- New source for exchange rates for display currencies (fiat currencies) as the current exchange rate provider will terminate their services June 1st 2018
--- Added a number of new block explorers for wallet balance
--- Automatic backup of the Awesome Miner configuration file two times per month
User interface
--- Preview of new web interface included, but not default. The new web interface must be activated via the Options dialog, Web section. In the future, this will be the new default web interface.
--- Dashboard improved to display up to 8 top coins and algorithms for the active miners. Sorting is by number of active miners
--- Display the income as coins per day via the Customize Progress Field feature (see web site for usage example)
--- Display the current pool name in the miner list when using user defined mining software with API compatibility with known mining software
--- Default sort order for Online Services tab is on the Profit column and if sorted on another column, the Profit column is always used for secondary sort order
--- Benchmark results can be copied to clipboard
--- Added additional coin images
--- Automatically select the new miner added via the wizard, to make it easier to find
--- Improved display of small coin values in Coins&Profit section of Options dialog
--- The bottom panel of the main window can be made smaller
--- Support Tensority / Bytom profitability calculations
--- Indicate source of coin statistics for each entry in the Coins tab
--- Improved validation of GPU clocking values in Clocking Profile
Rules and API
--- Added Awesome Miner API for removing Managed Miners and Managed Hosts
--- Added software type and hashrate value per device for /api/miners
Mining software
--- SRBMiner 1.5.5 with additional Cryptonight algorithms and configuration per algorithm
--- Bminer 8.0
--- DSTM ZCash miner 0.6.1
--- CpuMiner-Opt 3.8.8.1
Corrections
--- Correction to Innosilicon A6 hash rate unit
--- Correction to display of name of custom Online Services where multiple custom services uses the same algorithm
--- Correction to Wait Action in rules, for scenarios with longer wait times
--- Correction to benchmark to include the 'Additional command line' configured per algorithm in the profit profile
--- Correction to network scan to allow including IP addresses ending with 255
--- Correction to profit factors for a few predefined pools, including Nicehash and zpool X13
--- Correction to SIA block explorer integration for the wallet balance feature
--- Minor corrections
GPU mining
--- Improved CcMiner API processing for differents units of reporting for GPU clock, memory clock and power usage
--- SRBMiner configuration page to override config.txt via a Profit profile
ASIC mining
--- Improved detection of Antminer B3 with latest firmware
Configuration
--- Included predefined profit profile for Intel CPU mining
--- Managed Hosts can be disabled, resulting in all related Managed Miners being disabled will be ignored by the rules and no remote connection will be made
--- The list of Managed Hosts in the Options dialog has been improved to include the number of related Managed Miners and a button to find hosts without miners
--- Added variable [MinerWorker] for the password field of pools, to include the 'Add to worker name' part of a miner in the password field
--- The Bulk Edit feature for miners in the Options dialog are accessible directly from the miner list
--- Profit profile can be configured to be excluded from the global setting to ignore pools with no accepted shares
--- Changed predefined Bytecoin algorithm to Cryptonight
--- Improved detection of Managed Hosts duplicates
--- API connection retry can be configured via the Options dialog, Advanced section, to better handle poor network connections
Features and integration
--- CoinCalculators.io added as a new coin statistics provider
--- Multiple coin statistics providers can be selected and used at the same time
--- Tags for miners, where each miner can be assigned one or more tags and the miner list can be filtered based on tags
--- New source for exchange rates for display currencies (fiat currencies) as the current exchange rate provider will terminate their services June 1st 2018
--- Added a number of new block explorers for wallet balance
--- Automatic backup of the Awesome Miner configuration file two times per month
User interface
--- Preview of new web interface included, but not default. The new web interface must be activated via the Options dialog, Web section. In the future, this will be the new default web interface.
--- Dashboard improved to display up to 8 top coins and algorithms for the active miners. Sorting is by number of active miners
--- Display the income as coins per day via the Customize Progress Field feature (see web site for usage example)
--- Display the current pool name in the miner list when using user defined mining software with API compatibility with known mining software
--- Default sort order for Online Services tab is on the Profit column and if sorted on another column, the Profit column is always used for secondary sort order
--- Benchmark results can be copied to clipboard
--- Added additional coin images
--- Automatically select the new miner added via the wizard, to make it easier to find
--- Improved display of small coin values in Coins&Profit section of Options dialog
--- The bottom panel of the main window can be made smaller
--- Support Tensority / Bytom profitability calculations
--- Indicate source of coin statistics for each entry in the Coins tab
--- Improved validation of GPU clocking values in Clocking Profile
Rules and API
--- Added Awesome Miner API for removing Managed Miners and Managed Hosts
--- Added software type and hashrate value per device for /api/miners
Mining software
--- SRBMiner 1.5.5 with additional Cryptonight algorithms and configuration per algorithm
--- Bminer 8.0
--- DSTM ZCash miner 0.6.1
--- CpuMiner-Opt 3.8.8.1
Corrections
--- Correction to Innosilicon A6 hash rate unit
--- Correction to display of name of custom Online Services where multiple custom services uses the same algorithm
--- Correction to Wait Action in rules, for scenarios with longer wait times
--- Correction to benchmark to include the 'Additional command line' configured per algorithm in the profit profile
--- Correction to network scan to allow including IP addresses ending with 255
--- Correction to profit factors for a few predefined pools, including Nicehash and zpool X13
--- Correction to SIA block explorer integration for the wallet balance feature
--- Minor corrections
May 28, 2018, 06:23:48 AM
Hi this is my first post here and may have been answered but after a lot of searching I can’t find the answer I’m looking for, I can edit my json file for xmrig for a managed miner to get the best from my 1060s for the cryptonight algos, but is there a way to edit it for profit manager miner? It always seems to revert back 🤷🏼♂️🤷🏼♂️
Hi and welcome!For the XMRig mining software, Awesome Miner is not generating a configuration file. All configuration is made via command line. For some other mining software a configuration file is generated (for example SRBMiner, sgminer, Excavator), but not for XMRig.
Have you specific a configuration file to use via the command line?
May 27, 2018, 04:42:51 AM
I and other people are suffering some erratic failures with the AW api, with the extension of AW coin update. I know it's a separate development, but it seems that AW sometimes fails, and when it happens it's a failure that stays for days.
I have reinstalled the AWCU extension, I have reinstalled the latest version of AW beta. And it does not work.
This afternoon the system worked, but when I was mining with the same machine that has AW installed, I launched the AWCU currency updater, and gave that error, and I can not eliminate it.
The other time was an error that also disappeared only after the last update. I do not know if there will be a relationship with your API.
May 27, 2018, 04:42:01 AM
I was surprised to switch to X13 on GPUs (and CPU) 
And I just found this :
https://twitter.com/_zpool_/status/1000484163672248321
If you have zpool enabled in your profit switching change the profit factor of online service for X13. Apply your current profit factor divided by 1000
I will adjust to this change in the next release. And I just found this :
https://twitter.com/_zpool_/status/1000484163672248321
If you have zpool enabled in your profit switching change the profit factor of online service for X13. Apply your current profit factor divided by 1000
Jump to: