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

Cool ty. Ya for Dark Mode it would be the mass of white. It seems like more and more apps are starting to have this type of toggle and its been nice ever since. Blue Light filters work but I stare at screens all day. Doesnt need to be like gray or black, crex24''s green template is nice as well.

Thanks for the update. I will try to reproduce again.

Just a thought (I've not explored this idea in detail) - if there are unique cases where you have one algorithm with two coins that perform different. Maybe it could be possible to add one of them as its own user defined algorithm, like NeoscryptX where you could force a coin to belong to this algorithm instead, and configure the mining software to handle NeoscryptX just like Neoscrypt. You could then benchmark it individually. Again, I've not really tested a setup like this, just sharing some ideas.

It's a quite special scenario here, so it might not make sense to redesign the entire profit switcher to handle individual coins if this only happens to a very few coins for very few users.

First of all, welcome back puwaha!

You are correct that Awesome Miner depends on sources like WhatToMine.com and Coincalculators.io here, and once coins are added to their sites it automatically shows up in Awesome Miner as well. It's a significant effort (at least a part time job) if I would have to keep up with all coins, block explorers and exchanges myself. I do appreciate these community efforts and everyone contributing to make the overall mining experience better.

Yes, this is a very small change and I've had other users pointing out the same. This will be supported in one of the next releases.

1) Awesome Miner stores all configuration in the file ConfigData.xml located in the folder %appdata%\AwesomeMiner. To copy the configuration from one computer to another, make sure that Awesome Miner isn't running and copy the file ConfigData.xml to the other computer.

2) Yes, that will be added in the future.

3) It's not configurable today, but I do know that some users use the "Customize Progress Field" feature to put the uptime in the progress field and configure it to have different colors depending on if the uptime is low or not.

4) That might get supported, but it's not prioritized right now. Today you can change the color theme, but the miner list is still white. I assume it's these white areas you want in a darker color as well.

My guess is that "--p" should be "-p"

Thanks for all details. This is a unique behavior on the Z9 miner and you are correct that it's actually a bug in the API output from the miner itself. One of the API methods called "coins" is used by Awesome Miner to get the Network Difficulty from the ASIC miner. It's probably the least important of all API calls. The Z9 miner is responding with a invalid JSON format that simply cannot be parsed correctly. Awesome Miner considers the miner to not be working when this happens, but it should instead ignore the issue and move on.

I had a similar report yesterday from another Z9 user where it also started to act up after performing some pool operation. Thanks to your details here as well, I'm confident about the scenario now.

In the next update of Awesome Miner I will simply let Awesome Miner continue with all other API requests even if this one isn't valid. You can expect a new release within the next few days.

About the "sha256" part, there are actually many non-sha256 miners that do report sha256 here for some reason. This information is however not used by Awesome Miner.

Hello, patrike!

See screenshots below:

https://ibb.co/g3eWNT Device Profile Settings
https://ibb.co/fW1NU8 Managed Miner Properties
https://ibb.co/j9cwp8 Details ver 5.3
https://ibb.co/mqhkhT Details ver 5.2.2

I did not change setup of a profile of the device neither before up-dating nor after up-dating of the program. Therefore a problem definitely not in incorrect values of my parameters. The problem arises only in case of up-dating of the version of the Awesome Miner Remote Agent program installed on the device. In version 5.2.2 everything works, in version 5.3 - does not work. The version of the main Awesome Miner program does not matter.

Congrats!  I just got a Z9 Mini myself yesterday.



Did you create a profit profile for the Z9 mini and apply it to the external miner?

I think Patrike has done a fine job adding new coins as they become popular.  You have to realize that Awesome Miner has to depend on outside resources to get accurate coin data.  Many websites can't even agree on that data, so you have to strike a balance of quality versus quantity.

The plugin that Sootha created works really well, and I've contributed a couple of very large config.json files to the thread.  The problem is that most coins end up dying, and more importantly, their explorers go dead, or the coin gets deslisted, etc.

May I suggest you stop tinkering so much.  At some point, you have to make your rigs stable.  Constantly tweaking the overclocks, moving cards, all of this leads to instability.



People who have a large number of rigs do not constantly tweak settings.  As I mentioned, you want to make your rigs stable.  It's ok to experiment, but go for the changes that really make a difference.

Trucobit... you have some crazy ideas and really edge-case problems... keep them coming.  I've been taking a break from posting, but I'll go back and see if we can help you.

I've been thinking a lot about AW and it's a great software that requires a lot of attention, but it has a huge weak point.

They are the Benchmark that are made by protocol. I can see that I have a different HASH in two coins of the same protocol. It is very noticeable, I mino much neoscrypt, the same rig for a coin can give 5mhs, but for another currency neoscrypt can give a rate of 7 mhs.

Then thinking one realizes that it does not make sense that the switch is done only by the hash of the protocol, that's fine for the pools type Zpool and auto change.

But if I have 80 coins added, I need to know the hash for each of them, because although many are from the same protocol, they get different hashes. This difference can be by the ping, it can be by the stratum, by configuration of the Vardiff etc ...

Consequently, it would not be unreasonable PAtrike that you are considering in your programming that we can also save the hash for currency, and that this is the one chosen to make the Auto Switch.

I think the problem is perfectly understood, and is the culprit that some currency changes are worse instead of better, something that should not happen, and that only happens because of what I just commented.

A program of this price and this level, with so many added functions (and many other bugs), should be closer to the reality of each currency, being able to obtain that hash per currency / pool, instead of only Protocol HASH, which in the end it is not precise at all.

It is that if you also give the coins you give everything done. The ideal is not to add all the currencies of the world or you will have excessive changes of mining and loss of time.

Ideally, choose about 30 coins and keep your information. If you add it from Coincalculator, it is already updated alone.

It is the work in which I have been several weeks and I have not yet finished, because to know if a coin is good or not, apart from adding it, as you say you have to look for the pool with more hash and then measure the pool, that is to say Testing hours to see if what is estimated in profits is what really gives you. Do not forget to choose the best Exchange, not all have the same price, there you can also lose money.

The program is an interface precisely to facilitate the work, and it is a lot of work, worse would be at hand. It's impossible to give you all that information.

The peculiar plugin that you say is AW CU, and if it's weird and difficult, and you have to update the reward.

But pay attention to me, if it does not appear in Coincalculator, Coinwarz or What to mine, it is a new currency without volume, and if your idea is to sell every day, get away from those coins of little volume and exaggerated price.

As you will see, it is a lot of work. It's like buying a van to deliver, you have to drive hours and hours every day to deliver packages, they will not be delivered alone. Well, this program is the interface and database that you have to complete in data, and this changes depending on what style of mining you do, speculative, hodl or sell day by day.

https://bitcointalksearch.org/topic/hsrminer-neoscrypt-fork-by-justaminer-high-hashrate-api-all-gpus-supported-2765610
a strange fork of hsrminer, compatible with api ccminer and with very good hash rate. A very good alternative to Klaust for Neoscrypt, right now I put it on all my machines

It's getting about 20% more than Klaust, and 100% compatible CCminer api, it's fabulous.

1. There a way to backup all the custom info we have inputed into the software for re installation purposes?

2. Do you think having mining for "X amount of time each pool" will be in this programs future?

3. Is there anyway to change the gray text for the time active under the hash rate from gray to a more legible color? Or at least be able to customize it. When there is an update needed the red text is fantastic and very clear to read. I kinda dont like updating it because it makes it so much easier to read. Though I have old eyes.

4. Do you think "Dark Mode" will be in this programs future?

Amazing. While Klaust works well in rig1,2,3 and 4, in addition to being a miner by default. As I have already shown, in the rig5 no.

I have downloaded the Klaust from the same url that you have in Kalust, I have added it to the Rig5 as a miner managed by me, and that works perfectly.

I have not changed anything else, neither oc, nor intensity nor anything. All the same, I only added it separately, and while he brings AW to work with 4 rigs, he does not do it with the fifth one. And this happens to me relatively often sometimes.

You have already seen in the videos when it fails, call Klaust as a miner but at the same time call a coin that is not. I have put FTC to mine in two miners, in one goes, and in another it does not go.

When this happens several times, it is no longer a matter of something that the client has done, it happens sometimes and needs to be revised.

https://www.dropbox.com/s/hydf3jj7mx0agyr/IMG_2289.MOV?dl=0

Now I have a problem with another one of the failures of the program, which has already happened to me several times and I never find a solution.

In this case it is the RIG5, I choose a Neoscrypt coin as Zcore, I teach you in the video that NEoscrypt does with Klaust since basically it is the only good miner of neo, when there are hundreds of coins for this something.

And when I launch it fails, it refers to Neo, to Klaust and I do not know why it also refers to BSD in PHI. In the RIG5 team, Klaust really opens but fails. Now I leave you under the diagnosis. When this happens, it is difficult to fix, and I do not feel like formatting the computer again.

In the rest of RIGS with Neoscrypt and Klaust I have no problems. Other times it has been another RIG and another Something, but sometimes it crosses the information of two coins at a time and fails. because it is clear that what I have chosen from Zcore currency, and I show you the miner and everything.

Let's see if you can dedicate a little time to solve these problems because they become very annoying and they particularly make me lose a lot of time and I only have 5 rigs

DIAGNOSTIC
Initialize diagnostics (20)
Starting Diagnostics. Awesome Miner Remote Agent version: 5.3
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcKlaustMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Set clocking start profile: 36, 80 100--150 (when stopping, the following will be used: 5, type: Single, Use: False)
C:\Users\truco\AppData\Roaming\AwesomeMinerService\ccminer-821-cuda91-x64_1\ccminer.exe   -i 15 --p d=1024 -a neoscrypt -o stratum+tcp://eu.bsod.pw:2130 -u GWS3EYWeoHPv8TkoxPv1YhB3qhJgy6Djvd.rig4 -b 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: CcKlaustMiner, IsProfitMiner: True)
Configuration:

Configured command line:
 -i 15 --p d=1024
Mining Engine Process started, PID: 3260

====================================================================================================
> [2018-07-10 21:35:43] Intensity set to 15, 32768 cuda threads
> ambiguous option -- p
> ccminer 8.21-KlausT (64bit) for nVidia GPUs
> Compiled with Visual Studio 2015 using Nvidia CUDA Toolkit 9.1
>
> Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
> CUDA support by Christian Buchner, Christian H. and DJM34
> Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.
>
> Usage: ccminer [OPTIONS]
> Options:
>   -a, --algo=ALGO specify the hash algorithm to use
>          bitcoin     Bitcoin
>          blake       Blake 256 (SFR/NEOS)
>          blakecoin   Fast Blake 256 (8 rounds)
>          c11         X11 variant
>          deep        Deepcoin
>          dmd-gr      Diamond-Groestl
>          fresh       Freshcoin (shavite 80)
>          fugue256    Fuguecoin
>          groestl     Groestlcoin
>          jackpot     Jackpot (JHA)
>          keccak      Keccak-256 (Maxcoin)
>          luffa       Doomcoin
>          lyra2v2     VertCoin
>          myr-gr      Myriad-Groestl
>          neoscrypt   neoscrypt (FeatherCoin)
>          nist5       NIST5 (TalkCoin)
>          penta       Pentablake hash (5x Blake 512)
>          quark       Quark
>          qubit       Qubit
>          sia         Siacoin (at pools compatible to siamining.com)
>          skein       Skein SHA2 (Skeincoin)
>          s3          S3 (1Coin)
>          x11         X11 (DarkCoin)
>          x13         X13 (MaruCoin)
>          x14         X14
>          x15         X15
>          x17         X17 (peoplecurrency)
>          vanilla     Blake 256 8 rounds
>          whirl       Whirlcoin (old whirlpool)
>          whirlpoolx  Vanillacoin
>   -d, --devices         Comma separated list of CUDA devices to use.
>                         Device IDs start counting from 0! Alternatively takes
>                         string names of your cards like gtx780ti or gt640#2
>                         (matching 2nd gt640 in the PC)
>   -i  --intensity=N     GPU intensity 8-31 (default: auto)
>                         Decimals are allowed for fine tuning
>   -f, --diff-factor     Divide difficulty by this factor (default 1.0)
>   -m, --diff-multiplier Multiply difficulty by this value (default 1.0)
>   -o, --url=URL         URL of mining server
>   -O, --userpass=U:P    username:password pair for mining server
>   -u, --user=USERNAME   username for mining server
>   -p, --pass=PASSWORD   password for mining server
>       --cert=FILE       certificate for mining server using SSL
>   -x, --proxy=...       [PROTOCOL://]HOST[:PORT]  connect through a proxy
>   -t, --threads=N       number of miner threads (default: number of nVidia GPUs)
>   -r, --retries=N       number of times to retry if a network call fails
>                           (default: retry indefinitely)
>   -R, --retry-pause=N   time to pause between retries, in seconds (default: 30)
>   -T, --timeout=N       network timeout, in seconds (default: 270)
>   -s, --scantime=N      upper bound on time spent scanning current work when
>                           long polling is unavailable, in seconds (default: 5)
>   -n, --ndevs           list cuda devices
>   -N, --statsavg        number of samples used to display hashrate (default: 30)
>       --no-gbt          disable getblocktemplate support (height check in solo)
>       --no-longpoll     disable X-Long-Polling support
>       --no-stratum      disable X-Stratum support
>   -e                    disable extranonce
>   -q, --quiet           disable per-thread hashmeter output
>       --no-color        disable colored output
>   -D, --debug           enable debug output
>   -P, --protocol-dump   verbose dump of protocol-level activities
>       --cpu-affinity    set process affinity to cpu core(s), mask 0x3 for cores 0 and 1
>       --cpu-priority    set process priority (default: 0 idle, 2 normal to 5 highest)
>       --cuda-schedule   set CUDA scheduling option:
>                         0: BlockingSync (default)
>                         1: Spin
>                         2: Yield
>   -b, --api-bind=...    IP address and port number for the miner API (example: 127.0.0.1:4068)
>       --logfile=FILE    create logfile
>   -S, --syslog          use system log for output messages
>       --syslog-prefix=... allow to change syslog tool name
>   -B, --background      run the miner in the background
>       --benchmark       run in offline benchmark mode
>       --no-cpu-verify   don't verify the found results
>   -c, --config=FILE     load a JSON-format configuration file
>   -V, --version         display version information and exit
>   -h, --help            display this help text and exit
>       --mem-clock=N     Set the gpu memory max clock (346.72+ driver)
>       --gpu-clock=N     Set the gpu engine max clock (346.72+ driver)
>       --pstate=N        (not for 10xx cards) Set the gpu power state (352.21+ driver)
>       --plimit=N        Set the gpu power limit (352.21+ driver)

====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration
Diagnostics completed


and to clarify that I have it right, I'm going to mine it with another RIG and I show you the Zcore configuration, or any NEO currency, so you can see that it's a rare failure, in the same diagnosis there are weird things. I am losing precious time lately with so many failures.

You must find the fault, because this is very sporadic. will see in the video, the same currency in another rig without problems, in rig5, failure. And klaust is a miner by default. I'm going to have to add it separately as mine to try to fix this.

Between the problems with the OC and this, they make me waste a lot of time and therefore money. It seems that I am the only one who finds mistakes or mistakes.

https://www.dropbox.com/s/qvynqh58j6y50v5/IMG_2290.MOV?dl=0