Quote from: cyberunknown on May 08, 2019, 03:36:31 PM

My suggestions:
1. Displaying miner version eg. PhoenixMiner 4.2c;
2. Displaying hashrate for each card in the rig;
3. Displaying accepted / stales / incorrect shares;
4. Abillity to view / edit / send config.txt (like Claymore's EthMan do) directly to the rig (phoenix miner -cdmrs -cdm 2).

Thanks for using rig.cards! Cheesy

First of all I must to say that I making an easy to use monitoring service. Simple as possible. So I'm trying to not overload user interface.

1) I think it's possible, maybe some later I add it.

2) Here is the problem, because I take GPU data not from miner. And even if miner not launched or you use not supported miner or miner without API, you anyway can monitor your rig. But i this case any miner has list of GPUs and sequence of it not equals to sequence that getting by client app. Even more, the sequence GPUs in the list can depends on each miner, or even on miner settngs. So it's impossible to detect which GPU on which place and I can't match these two lists...

3) It's maybe also possible, but as I undertand it can depends on mining algo. On ethash, yes, we have accepted/stales/incorrect shares, but on any other algo is it exists anyway or can be different? The question is in identical working of rig.cards for any algo.
So it's need to analyze this request but anyway it is not a priority task for now.

4) As I said before the main function of rig.cards it's excelent monitoring service. Only after all main functions will implemented we can talk about management tools.
So stay tuned!

Thanks for help on improving rig.cards!