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

In older ant versions there were other login / password
admin/admin
root/root
root/admin

 I can´t configure the API access to my antminers in AWESOME MINER, but I can´t access via SSH to my miner (SSH username and password is: root / admin). How can I reset the SSH password?

If please something has to be done, since I have realized I have become paranoid and I realize the money lost every day

XAGC buy 408 sold at 588, AM shows me 588, it's not the right price

So I could give you dozens of examples of currencies that we are undermining by the sale price and not the purchase price.

Or talk to those who provide data like WTM etc ... or somehow you should give another solution to the problem. Actually the prices given by AW CU are the sales, the appropriate, and it is only an extension. I do not know if in some way you could join Awesome miner.

Today I saw a STIM currency prices 600 and 1650, AM gave me 1650 and so many coins.

I had to deactivate multiple currencies because I was undermining the sale price that will always be higher than the real, much higher. This makes money lose and should be important, because it is a fundamental part of the very essence of the program. Mine the most profitable, but the real profitable.

Please, I would urge you in this, because we are mining with incorrect data in a large part of the currencies.

Example



XACG 1º  588 satochis

exchange Crex24




More than 400 difference, and see that it is a coin added with AW CU and also does it wrong

Is it possible to make a storage of miner programs on the control computer from which to distribute updated miners to the extended clients.
This would greatly simplify the task of updating a large number of miners

This miner will be included in the next update of Awesome Miner.

I would also recommend everyone to start asking the mining software developers to provide HTTP download links for their software - instead of download sites like Mega. If you get a HTTP URL, you can enter it in Awesome Miner (Options dialog, Managed Software section) and get access to the new versions in an easy way without having to wait a few days for a new Awesome Miner release.

Thanks!

I fully understand your point here. There are however no plans (in the near future) to let Awesome Miner do the work of collecting more or better coin statistics unless provided by WhatToMine.com, Coincalculators.io and so on. It would simply be too much work.

Another way forward might be to work closer to the WhatToMine.com and Coincalculators.io teams, and see if they can provide additional exchange rates (the buy-rate) that could be used by Awesome Miner.

Hi,

1) Please go to the Options dialog, Online Services, and verify that the field "Nicehash domain matching" is set to the default value "nicehash.com" and nothing else.

2) If you still experience this issue, please contact me by mail and send your configuration file (%appdata%\AwesomeMiner\ConfigData.xml) so I can investigate in more detail why it's failing.

Thanks!

Good point. I will look into improving this.

Thanks - I've updated the documentation based on this.

I did not want to comment on it, but it is one of the great hidden problems of Awesome miner.

It depends on where the data is, WTM, Coinscalculator, CC, or even AW CU, it turns out that sometimes AM gives you the sales price and other times of purchase, and they are very different.

For simple example, PGN is really paying 1 satochi per coin, but in Awesome miner it shows 2, because it is the price at which they sell it, but the real price is for which they are already willing to pay.

The problem that Awesome in that aspect is not standardized, and directly takes all the data from those 3 sources, and each gives the prices or sale or purchase, which is a problem.

Coins with large volume, the difference is minimal, when they are coins of low volume or volume can make a purchase offer price of 300 and sale in 550, and of course I am interested in the price of purchase offer, the price for which he is already paying, which is the lowest price, but surely they will pay.

I know this is a great job, but ideally, AW miner should take the hash data, difficulty etc. from the sources mentioned, but then the prices directly from the Exchanges, as if AW CU does. And the ideal would be that if a currency is in several Exchanges, the power to choose for each currency, of which exchange I want the purchase offer price, with which everything will coincide perfectly.

While that is not a standard within Awesome miner, you will see and there are big problems of price difference. At least AW CU always gives the purchase offer price, which is REAL, and not the SALE one, which tend to be very inflated, and this happens a lot very much in Awesome miner, which is fixed in the sale price that is It is always higher, but you are not really paying for that price, the real price is the purchase offer. This has to be made a standard. The software is advancing so much that it seems incredible that it does not have an authentic control over the price of the coins.

I hope you understand what I'm trying to explain.

The coin pools you have set up, make sure they do not overlap the pools (regardless of wallet, username) that are predefined in Online Services. (eg, if you are mining some coins via custom pool, don't use Zerg/Zpool,Ahash,Blaze,Blockmasters....etc) Online Services profitability stats takes precedence over Coin Profitability stats providers. So say if you are mining RVN, and have your custom pool setup @ Zergpool, your profitablity won't be what WhatToMine or CoinCalculators show you, but will be the Zergpool's X16r Profitability (24 actual, 24 estimate, Current whichever you have set up in Options) stat.

Hello,

Thank you for your reply but that doesn't seem to be the cause. One is set to 2 minutes and the other to 3 minutes.
The 1 minute difference doesn't explain the extreme difference shown.

Also, it seems the issue only happens when you have the same pool with the same wallet/username even though the other fields are different.
I suspect that AM is not referring to each pool with its unique ID but rather seems to be identifying each pool/coin using only the wallet/user or a combination of pool url + wallet.

Hi, What's your settings in Options -> Statistics -> Update interval (minimum 2 Minutes) ?
as well as Options -> Profit Switching -> Switching interval (minimum 30 Seconds) ?

the info displayed in Coins tab is updated as per schedule set in the former (subject to API availability from providers)

the info displayed in View Details is updated as per schedule set in the latter (subject to Profit Profile Settings -> Enabled Algo, Enabled Software, Enabled Pools)

So they will almost always be out of sync in one way or another, and degree of difference is expected amplified if the interval difference of the 2 is several (tens of) minutes apart, especially if you have lots of coins with low block times and high difficulty adjust frequency enabled. (you are likely seeing lots more of mining the wrong coin scenario especially with algos such as C11, Lyra2v2, Neoscrypt, Tribus, HMQ1725, Skein ... etc. as the profitability tend to spike due to high difficulty adjustment frequency in coins that utilise these algos, many adjust difficulty every block)

Hello Patrike,

I sent you an email regarding this issue but never got a reply.
AM seems to be having issues within the profit switching calculator.
The information shown in the "Coins" tab doesn't match what is shown when you right click on the miner and you click on  "Details".
This seems to be causing AM to choose the wrong coin to mine (unless the actual issue is the "Coins" tab showing wrong info).

ah, ok, sorry thought you're trying to manage overclocking with AM and Afterburner, I'm not an AMD person btw, only have 2 RX470 vs tens of NV cards (though, my AB can set different clocks between the 2, I did let AB manage customized Fan control curves and not let AM do anything regarding GPU controls). Apart from modding BIOS timings, I left the cards with their default memclock of 1650 when booting up, and only set clock to 2000 via AB startup profile locally (not remote), gets 29MH/s each on ETH (both with Hynix VRAM) so I guess not too bad. Point being though, maybe try other OC tools like OverDriveNT, I suspect something else is causing the sync clocks rather than AM in your scenario.
[/quote]
Uhm, yes, it might helped to use overdrive, but i need to find solution within current setup, AM+Afterburner is nice combo which suits well..its just something has to be fixed within the settings, i mean..the point of AM was to manage all in one and thats what i aim for.
Thanks, hopefully this will get answered by support

[ANN] T-Rex 0.6.6 Nvidia GPU miner

New version released.

0.6.6
Speed improvements: bcd - 5%
Cosmetic change: the miner will not show duplicate hashorder messages for x16r/s, bitcore, and they are no longer labeled as WARN
To disable API altogether set --api-bind-http / --api-bind-telnet to 0.
HTTP API: new control command "shutdown" to quit the miner (see help file for details)


Downloads
v0.6.6

Linux:
CUDA 9.1: https://mega.nz/#!XMlS0CYL!ruvZvVnoRC3gTArZyzzYF-t6B-XH0UnDCN6hV227Ya4
CUDA 9.2: https://mega.nz/#!eF1Q1SJC!0hv7ZhJaOCOQQ3zPmN5AnVCEJdND7rzqkRTm-MlVca0

Windows:
CUDA 9.1/9.2:
https://mega.nz/#!TEsUSIiC!4zpoxI58Qc90bcKsFHM0RhAvA7ERsNBB5HlNYsUa9xI

ah, ok, sorry thought you're trying to manage overclocking with AM and Afterburner, I'm not an AMD person btw, only have 2 RX470 vs tens of NV cards (though, my AB can set different clocks between the 2, I did let AB manage customized Fan control curves and not let AM do anything regarding GPU controls). Apart from modding BIOS timings, I left the cards with their default memclock of 1650 when booting up, and only set clock to 2000 via AB startup profile locally (not remote), gets 29MH/s each on ETH (both with Hynix VRAM) so I guess not too bad. Point being though, maybe try other OC tools like OverDriveNT, I suspect something else is causing the sync clocks rather than AM in your scenario.

T-Rex 0.6.6 (mostly for those interested in bcd)
Speed improvements: bcd - 5%
Cosmetic change: the miner will not show duplicate hashorder messages for x16r/s, bitcore, and they are no longer labeled as WARN
To disable API altogether set --api-bind-http / --api-bind-telnet to 0.
HTTP API: new control command "shutdown" to quit the miner (see help file for details)

Linux
CUDA 9.1:
https://mega.nz/#!XMlS0CYL!ruvZvVnoRC3gTArZyzzYF-t6B-XH0UnDCN6hV227Ya4

CUDA 9.2:
https://mega.nz/#!eF1Q1SJC!0hv7ZhJaOCOQQ3zPmN5AnVCEJdND7rzqkRTm-MlVca0

Windows (x64)
CUDA 9.1/9.2:
https://mega.nz/#!TEsUSIiC!4zpoxI58Qc90bcKsFHM0RhAvA7ERsNBB5HlNYsUa9xI

FTP mirror:
http://ftp://radio.r41.ru/t-rex-0.6.6-linux-cuda9.1.tar.gz
http://ftp://radio.r41.ru/t-rex-0.6.6-linux-cuda9.2.tar.gz
http://ftp://radio.r41.ru/t-rex-0.6.6-win-cuda9.1.zip

Hi, i just thought i made myself clear enough, but this may help a bit more, please see:
1. I am not clocking up the system with AM. Clocks are set via BIOS directly. Only FANs are set and that is related to "Miner template" not GPU.
2. I already run through various videos, also official documentation, and did some re-installation of system to start from blank. None of this helped.
3. Here are screens just so you have the full picture:
https://imgur.com/7SU9Cpq
You can see there that there is only one clocking profile with FANs only set - that is working correctly.
Also you can see that the memory clocks are available, means they can be read.
One GPU is missing, because it is disconnected now, but it would show the same memory clock - HOWEVER GPU Z default clock(out of bios) is set to 1950Mhz!! Only somehow it is re-clocked to 2100 with others.
As stated, on SINGLE GPU TEST RIG this issue is not happening.

Hope this helps. Thanks for the suggestion anyways!  

https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclocking

Check the section on "Clocking Profile Groups", this allows you to set clocks in a mixed GPU system and apply clocking per GPU / group of GPUs