Pages:
Author

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

legendary
Activity: 3556
Merit: 1095
How to show correct price for BEAM? Coin tab shows Revenue $21,779. Coin properties appear to be correct.
When I'm looking at Beam from WhatToMine right now, it looks fine and a hashrate of 50H/s gives ~$2.7/day. Are you using all default values in the Coin Properties? Do you still experience this issue or was it only temporary?
legendary
Activity: 3556
Merit: 1095
all my profit profiles disappeared and when i go to edit them there is only one to select from... Ethereum.

it is like this for all my miners/rigs
Please open the Options dialog, Algorithms section and see if you have unchecked most algorithms. Your profit profile will only list the algorithms that are enabled on a global level (Options dialog, Algorithms section).
legendary
Activity: 3556
Merit: 1095
Hi Patrik,

question, or maybe a suggestion Smiley

Is it possible in the rules to set some trigger for a rig A, but the action (like a start/stop miner command) is for another rig B? Or maybe multiple rigs B, C, D, .....?

If this is not possible right now, it would be awesome if you could do that.
Thanks for the suggestion. This isn't possible today.

Can you give an example of when this might be useful? This would be of help for me to understand what's missing today. Thanks!

Hey Patrik,

here are two examples for my own benefit.

I have a few watercooled rigs with 2 seperated rigs in 1 water-loop. If for whatever reason the main-rig turns off, there is no waterflow anymore and I have to shutdown the second rig too. Right now that shutdown is managed by a smart socket, but if AM could handle that with just a rule and much faster, it would be awesome.

I also have multiple containers, running each 4 rigs inside, but with just 1 power line per container. If the main-rig including the power for the containers airflow turns off, I have to shut down the other 3 rigs to protect them of overheating. AM could handle that even faster than any smart socket.

I think this option can be useful for other miners too, to protect rigs in a better way without using external stuff like smart sockets or so. How could this be done? One idea would be in the rules -> actions -> "miner command" for example another line which is already set to "this miner/group", but I also can choose other miners or groups. But maybe you will find a better way like always Smiley

And patrike it is possible at the moment to shutdown many rigs if one rig goes down. You can set a rule that push an .cmd file with start/stop api commands or shutdown.

Much work at the moment, but it is possible. An easier way would be nice, but not for the strange scenario joseph32 explained.
Thanks for all feedback. I think it would be quite easy to extent the rule concept to let you manually define for which specific miners the actions should be performed. I will look into this and it can hopefully be supported soon.
full member
Activity: 1148
Merit: 132
why do i get mining interface offline when the card is mining and awesomeminer agent is running?  its happening now on phoeniexminer
newbie
Activity: 52
Merit: 0
How to show correct price for BEAM? Coin tab shows Revenue $21,779. Coin properties appear to be correct.
legendary
Activity: 2324
Merit: 2533
EIN: 82-3893490
all my profit profiles disappeared and when i go to edit them there is only one to select from... Ethereum.



it is like this for all my miners/rigs
member
Activity: 70
Merit: 10
@sx. For the few summer months yes. But for the cold months and mainly for the winter months I need it that way. But your idea is nice and much better than mine and maybe much easier to do. A rule-action to force a start/stop/whatever command to multiple rigs or groups.

Yes, each case needs individual adjustment. Wink
member
Activity: 418
Merit: 21
@sx. For the few summer months yes. But for the cold months and mainly for the winter months I need it that way. But your idea is nice and much better than mine and maybe much easier to do. A rule-action to force a start/stop/whatever command to multiple rigs or groups.
member
Activity: 1558
Merit: 69
Hi Patrik,

question, or maybe a suggestion Smiley

Is it possible in the rules to set some trigger for a rig A, but the action (like a start/stop miner command) is for another rig B? Or maybe multiple rigs B, C, D, .....?

If this is not possible right now, it would be awesome if you could do that.
Thanks for the suggestion. This isn't possible today.

Can you give an example of when this might be useful? This would be of help for me to understand what's missing today. Thanks!

Hey Patrik,

here are two examples for my own benefit.

I have a few watercooled rigs with 2 seperated rigs in 1 water-loop. If for whatever reason the main-rig turns off, there is no waterflow anymore and I have to shutdown the second rig too. Right now that shutdown is managed by a smart socket, but if AM could handle that with just a rule and much faster, it would be awesome.

I also have multiple containers, running each 4 rigs inside, but with just 1 power line per container. If the main-rig including the power for the containers airflow turns off, I have to shut down the other 3 rigs to protect them of overheating. AM could handle that even faster than any smart socket.

I think this option can be useful for other miners too, to protect rigs in a better way without using external stuff like smart sockets or so. How could this be done? One idea would be in the rules -> actions -> "miner command" for example another line which is already set to "this miner/group", but I also can choose other miners or groups. But maybe you will find a better way like always Smiley

it is maybe better to make the water flow separately and don´t let control a rig the waterpump. The same with airflow, it make no sense to control the airflow or waterflow for multiple rigs with one rig.
You look for the wrong solution my friend.



And patrike it is possible at the moment to shutdown many rigs if one rig goes down. You can set a rule that push an .cmd file with start/stop api commands or shutdown.

Much work at the moment, but it is possible. An easier way would be nice, but not for the strange scenario joseph32 explained.
member
Activity: 418
Merit: 21
Hi Patrik,

question, or maybe a suggestion Smiley

Is it possible in the rules to set some trigger for a rig A, but the action (like a start/stop miner command) is for another rig B? Or maybe multiple rigs B, C, D, .....?

If this is not possible right now, it would be awesome if you could do that.
Thanks for the suggestion. This isn't possible today.

Can you give an example of when this might be useful? This would be of help for me to understand what's missing today. Thanks!

Hey Patrik,

here are two examples for my own benefit.

I have a few watercooled rigs with 2 seperated rigs in 1 water-loop. If for whatever reason the main-rig turns off, there is no waterflow anymore and I have to shutdown the second rig too. Right now that shutdown is managed by a smart socket, but if AM could handle that with just a rule and much faster, it would be awesome.

I also have multiple containers, running each 4 rigs inside, but with just 1 power line per container. If the main-rig including the power for the containers airflow turns off, I have to shut down the other 3 rigs to protect them of overheating. AM could handle that even faster than any smart socket.

I think this option can be useful for other miners too, to protect rigs in a better way without using external stuff like smart sockets or so. How could this be done? One idea would be in the rules -> actions -> "miner command" for example another line which is already set to "this miner/group", but I also can choose other miners or groups. But maybe you will find a better way like always Smiley
legendary
Activity: 3556
Merit: 1095
Hi Patrik,

question, or maybe a suggestion Smiley

Is it possible in the rules to set some trigger for a rig A, but the action (like a start/stop miner command) is for another rig B? Or maybe multiple rigs B, C, D, .....?

If this is not possible right now, it would be awesome if you could do that.
Thanks for the suggestion. This isn't possible today.

Can you give an example of when this might be useful? This would be of help for me to understand what's missing today. Thanks!
legendary
Activity: 3556
Merit: 1095
@patrike Hi boss, why AM ver. 7.8.3 not automatic recognize Nicehash CookarooZ29 service? Nicehash side problem?
I've pushed an update where this Nicehash pool will be added automatically. It should automatically show up in your Awesome Miner within the next few hours.

@patrike I am not understand why i cant add Cortex (CTXC) coin. I have put json link: https://whattomine.com/coins/329.json where Cortex present in Statistic provider settings, but nothing happens. Please add this coin in next release.
The algorithm name used by WTM wasn't recognized by Awesome Miner. I've pushed an update for this now. This one will also automatically show up in your Awesome Miner within the next few hours.
member
Activity: 418
Merit: 21
Hi Patrik,

question, or maybe a suggestion Smiley

Is it possible in the rules to set some trigger for a rig A, but the action (like a start/stop miner command) is for another rig B? Or maybe multiple rigs B, C, D, .....?

If this is not possible right now, it would be awesome if you could do that.
legendary
Activity: 1754
Merit: 1007
@patrike I am not understand why i cant add Cortex (CTXC) coin. I have put json link: https://whattomine.com/coins/329.json where Cortex present in Statistic provider settings, but nothing happens. Please add this coin in next release.
legendary
Activity: 1754
Merit: 1007
@patrike Hi boss, why AM ver. 7.8.3 not automatic recognize Nicehash CookarooZ29 service? Nicehash side problem?

anyone know a linux command to switch off/on led lights on Nvidia RTX cards? Thanks.
legendary
Activity: 1754
Merit: 1007
dont
Hai...

any complete tutorial running awesome Linux agent on ubuntu? fresh install ubuntu and instal nvidia driver and update and install awesome miner Linux agent but miner not running at all,

Thanks...
I don't have any detailed tutorial for this at the moment - this is probably something to improve.

When you start the mining software with the Diagnostics button, what is the error message? Thanks!
you looking for difficulty ways? simple install hiveOS, this is configured Ubuntu for mining. But if you want run Awesome on fresh Ubuntu, you must install all CUDA libs and configure system path to this libs. Do you need this really?
legendary
Activity: 3556
Merit: 1095
Hai...

any complete tutorial running awesome Linux agent on ubuntu? fresh install ubuntu and instal nvidia driver and update and install awesome miner Linux agent but miner not running at all,

Thanks...
I don't have any detailed tutorial for this at the moment - this is probably something to improve.

When you start the mining software with the Diagnostics button, what is the error message? Thanks!
legendary
Activity: 3556
Merit: 1095
On the Balances tab under wallet balance I put in all my bitcoin addresses. I noticed that addresses that start with BC1 won't show a balance. I looked in settings and it is using the default https://blockchain.info/en/balance for looking up the balance. When I go to blockchain.info in a web browser I can see the balance of bitcoin addresses starting with BC1 just fine.
I think the Blockchain API may not support looking up all kind of addresses (although their web site support more).

Can you please edit balance entry and change the blockchain.info URL into using this URL instead?
https://api.blockcypher.com/v1/btc/main/addrs/[address]/balance
legendary
Activity: 3556
Merit: 1095
Hi patrike,

i have a Problem with GPU Clock Profiles. I save the GPU settings from a RIG, and sometimes if i want to change some settings from 1 GPU Profile i get an error. But this error makes no sense to me.

And other Problems:

NBminer 31.1 recognize AMD AND NVIDIA CARDS, so if i want to set some devices for the miner, the order is wrong. Awesomeminer only show nvidia cards, and will begin with device 0, but the first card is a AMD card. So the order of the devices are not correct.

Wildrig Multiminer the same problem. It will recognize AMD AND NVIDIA CARDS, but i only can choose AMD cards in Awesomeminer. So the order is wrong too.
Thanks for the report.

Although I wasn't able to reproduce the GPU Clocking save issue, I made a small change to improve and also added additional logging. In case you run into this problem again, please share the more detailed error message with me. Thanks.

I will also update the mining software GPU selections you pointed out.
copper member
Activity: 416
Merit: 105
Hai...

any complete tutorial running awesome Linux agent on ubuntu? fresh install ubuntu and instal nvidia driver and update and install awesome miner Linux agent but miner not running at all,

Thanks...
Pages:
Jump to: