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

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

Simply Awesome!!

thank you, now I have many more coins, finally I enter coinwarz.

Hi PAtrike I wanted to call attention to a known problem that the weeks go by and there is no solution.

MSI REMOTE, the program is not yours is from a third party, but it is not going well. In the configuration of AW you have to put the exact path where you will be in all the machines, that is, the same folder. Through another user I commented much higher, that sometimes it goes crazy and when the remote starts it closes, and the only way to fix it is to change the folder in the AW configuration, then change it in all the rigs and also change the rule of the programmer of tasks of each rig so that it starts well.

Well, this is happening to me at least once a week. If I take out a rig and change a card, it does not work anymore. Sometimes even without changing anything, just a restart, since it does not load at the beginning.

I have the version to be able to handle the OC, and I see myself many times leaving an Aftherburner in a fixed OC, because I do not feel like doing all that work.

Please have to find a more RELIABLE solution, this is now a patch that gives a lot of work at times. I can not imagine who has 10, 20, 30 rigs each time they fail and have to change the remote in ALL rigs and the rules of the task scheduler.

I do not ask you, mada, I only remind you that this mistake is and it drives me crazy. And that the fault is of the remote server, but it is in your hand to choose another software or develop one of its own that communicates afther burner (or other software) with the central machine, and it is not being deconfigured every few days.

Or you can tell us a faster real solution for when a computer falsely loads the Remote Server, so it appears in the notification box but when you put the mouse on it, it disappears. You have to give us a solution, because it is very annoying, and besides, not managing the OC is a waste of money and I pay more for having that control.

This is not a suggestion of new functions, nor do I ask the moon, I only ask you that what works is fine, and more now in summer that many of us have to change to softer OC in all the protocols.

I think it would be better to make separate entries for Excavator 1.4 and 1.5 (and remove the old excavator). Version 1.4 works fine with other pools and is the fastest software for some algorithms. Version 1.5 could then be Nicehash only.

Could you please change the "update remote" right-click option to be available on the group level at all times?  Would be much more convenient than having to update each miner individually.  Right now it appears to be available only if all miners are enabled and out of date.  If even one miner is disabled or offline the option is not available.

Ok.. ever since I used the free version of awesome miner (now on enterprise version ), Ive always wondered one thing.... Why is not ALL of the coin information on ALL coins entered and automatically updated? I mean, lets get honest, to maximize profits, a user would have to fill out ALL of the stats for all of the coins, and even find the pool with highest hash rates. This would take WEEKS.  Im SURE this could be done automatically with awesome miner.  I know there is a free plugin for awesome miner, but as its free, its very quirky, and even then, leaves tons of coins without data. Can someone please explain?

Vegas

patrike,

Hello! New user / "Premium Edition" licensee.

I'm managing Z9s.

I've added the Z9s, set the default pools, set up API access, enabled auto-detect of ant miners...

The basic monitoring is working, however I'm unable to switch pools. When I try to switch pools by selecting a miner, right clicking, and choosing the new pool in the list, the miner goes offline as it appears to be reconfiguring, but it comes back up with whatever the first pool is every time.

If I manually send a "switchpool" command to the miners, it switches immediately without going offline and AwesomeMiner seems to show the change quickly.

I assume I'm missing something configuration wise for being able to switch it from awesome miner itself (not worried about profit switching yet, just want to get the basic functionalities going). This is with version 5.3.

So, 2 questions:

1) If "switchpool" works when I send it manually, what else is required on the Z9 configuration beyond (A) enabling API access, (B) configuring pools under Options->Pools [not pool groups], (C) Under Antminer->Default Pools, configuring the pools from B in the menu, and then (D) trying to manually change the running pool on each Z9 (or the group of, but still), (E) setting each miner for equihash algorithm and cgminer compatible

2) In the log file, there is an error I am not sure how to track down that may be related:

Here is a snippet:


As an aside, here's an interesting Z9 cgminer bug(?).. asking for the details of 'coin' via the API says that the hash method is sha256 despite it being an equihash device.


Thank you!

Hi.

I tried to reproduce the issue by defining a Device Profile where I set "Max Fan Speed" to 66. I referenced this device profile from a Managed Miner that is based on Claymore Ethereum. When I start the mining software, I do see that "-fanmax 66" is being added to the command line.

Is there a specific property from the device profile that isn't passed correctly? Are you running with a Managed Miner or Managed Profit Miner? Please let me know as it might be of help in trying to find the specific issue you run into.

Awesome Miner version 5.3.1

- User defined Managed Software can be configured for automatic download
- Improved display of mining software in the Edit Profit Profile dialog
- Adjustment to the hash rate unit reported by iBeLink DSM6T ASIC miner
- Updated list of algorithms for predefined pools
- Added mining software: JCE CPU Miner
- Excavator 1.5 supported. This mining softare only works with the Nicehash pools.
- Prevent too frequent API calls to Coinwarz
- Correction to sorting in Options dialog, Managed Hosts section
- Minor corrections

I use Claymore Dual GPU Miner 11.8. In the new Awesome Miner 5.3 version parameters of tuning of video cards from Device Profiles are not inserted into command line arguments of the Claymore Miner program any more!!!!  Because of it video cards overheat, lose productivity and glitch. 

Rollback on Awesome Miner and Awesome Miner Remote Agent to version 5.2.2 solves a problem.

Please, correct it!

Hi Ralf,
I think I need to see some screenshots on this scenario, to get the complete picture of what View Details are showing compared to the miners list. Can you please send me by e-mail? Thanks!