Latest posts of: patrike

Awesome Miner version 6.5.5

ASIC mining
- Adjust the reported pool priority for BW L21 ASIC
GPU mining
- Improved detection of environment variables for nVidia commands via Remote Agent on Linux
Features
- Added a way to detect duplicated IP addresses for External Miners in the Options dialog, External Miner section
Mining Software
- CcMiner KlausT 1.25
Corrections
- Correction to exact IP address match in the Find Miner dialog
- NbMiner console correction for Remote Agent on Linux and disable watchdog
- Correction to the console tab to correctly clear the display when selecting a miner without any console output

my antivirus keeps on blocking the miners...never had any problems with any miners except those downloaded by your program....

When using the automatic download feature in Awesome Miner, a zip-file will be downloaded from the official download location if still available. As a fallback, an identical copy of the original zip-file can be automatically downloaded from the Awesome Miner web site.

However, most anti-virus software warn about cgminer and similar mining software because they are being used by trojans and other malware. If you run into this problem, you can always manually download cgminer / sgminer and configure Awesome Miner to that use that downloaded instance instead.

Thanks for your great software. There is a feature that I think Awesomeminer lacks. Please consider adding “Auto Update" feature to Awesomeminer, like any other applications even with schedule. It is a pain in the neck if you have multiple rigs, and every week, you use a remote session to go and click on update manually with high pings and delays. It is so easy for you to add this feature.

Thanks for the suggestion.

The general idea is to have a single Awesome Miner installed on one computer, and then run Remote Agent on all other computers you do GPU mining on. Then you only need to have one Awesome Miner to upgrade, and upgrading each Remote Agent is only a matter of clicking the 'Upgrade Remote Agent' button in the toolbar.

Quote from: Stryfe on June 11, 2019, 07:33:53 PM

patrike -

thanks! it does now show the hash rate and thus the estimated revenue/profit for the BW L21 now - the only other thing I notice is that the pool that shows is the pool #2 - it does not show what pool the miner is actually on. for example, if I put one pool in - it shows nothing. If I put two pools in, it shows the second one, even if the miner is mining on the first one.

I do understand your point here. The priority of the first pool has a higher number (crazy high as in 16842752) when reported from the ASIC miner, when it in fact should be priority 0. The second pool has priority 1. For this reason Awesome Miner will consider the second pool to be active.

This is another case where the BW L21 ASIC doesn't report correct information, but I will adjust Awesome Miner to consider very high priority numbers to be 0 instead. Priority 0 is the current active pool.

Awesome Miner version 6.5.4

ASIC mining
- Improved support for recent revisions of BW L21 ASIC
GPU mining
- Show nVidia fan speed as RPM (in addition to percent) when running Remote Agent on Linux
User interface
- Dark mode for the main window of Awesome Miner. Configurable in the Options dialog, General section.
Mining software
- TeamRedMiner 0.5.1
- WildRig Miner 0.17.5
- T-Rex 0.11.1
Corrections
- Correction to GPU selection for TeamRedMiner
- Correction to the use of screen command on Linux

Quote from: s3c70r on June 11, 2019, 08:24:14 AM

I shouldn't have to set any power usage for my miners. I'm getting power usage from the firmware.

As you can see in the summary, since I'm running asicFW firmware, I have power usage for each board.

As per https://support.awesomeminer.com/support/solutions/articles/35000104685-power-consumption-and-profitability

Quote

Power consumption and profitability

Introduction
Awesome Miner can read and display the current power usage of both nVidia and AMD GPU's, independent of which mining software being used.

ASIC miners in general doesn't have any feature where they can report the power usage and for this reason Awesome Miner cannot display the actual power usage, only manually configured values for power usage together with linear power scaling based on the current hashrate.

It's currently only ASIC miners running the custom firmware AsicFW that can report power usage to Awesome Miner.

It's very nice to have power usage per board.

I'm looking to have an easy way to get the total of all three boards. Though I could do it with a custom progress field.

The actual power usage should be displayed in the Performance column as well, so I think the reason it doesn't show up is that Awesome Miner may not be configured to show the Actual Power usage (instead of the Static values that typically are used for ASIC's).

Please go to the Options dialog, Profitability section, and change the "Power usage mode" to one of the Actual Usage settings.

Quote from: Stryfe on June 11, 2019, 04:16:30 AM

Quote from: patrike on June 07, 2019, 05:46:50 PM

Quote from: Stryfe on June 07, 2019, 11:55:22 AM

Quote from: patrike on June 07, 2019, 11:18:03 AM

Quote from: Stryfe on June 07, 2019, 01:38:26 AM

Quote from: patrike on June 06, 2019, 07:36:30 AM

Quote from: Stryfe on June 06, 2019, 01:10:00 AM

does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.

This miner is supported, at least previous revisions of it.

Even in the past this ASIC has always reported crazy number for the total number or share and total hashrate. What Awesome Miner do is to detect that it's a miner of this kind and then recalculate everything based on each individual ASIC device to get numbers that are accurate.

It might be that more recent revisions of this ASIC is a bit different and Awesome Miner isn't able to detect it correctly. Could you please send me the API report (toolbar: Tools -> API Report) via mail or PM and I will see what changes they might have introduced and how to do another workaround. Thanks!

pm sent with the API log

Perfect - thanks for the log!

I had to make a small adjustment to get Awesome Miner to detect this miner as a BW-L21. Once that detection was updated, it shows up fine.

nice! so in a future update?

Yes, it will be included in the next release.

eta on that update? just so I know when to use AM again for looking at profitability - it currently puts me in the red due to the 3 miners showing as using power but with zero hash rate. it doesnt even show the right pool - maybe thats why the hash rate is zero... hmm, let me try to delete the second pool.

nope that does not work. down in the bottom area where the summary area is, if i click asic it shows them hashing, it just doesnt translate up to the top. the top area seems to want the second pools information. but i cant leave pool one blank .

I will soon make a release with the BW-L21 updates. With the changes I do see hashrate, accepted shares and pools displayed correctly.

Quote from: joseph32 on June 10, 2019, 02:56:26 PM

Quote from: joseph32 on June 01, 2019, 06:53:36 PM

Hey Patrik,

I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.

- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.

Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:

- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.

I think because there is no miner API established because of the crash, even if the mining window is still open?

Hey Patrik,

just got that situation again with the new T-Rex version in one of my single miners. Will send you the API-report by PM.

I think I know why this can happen:

- The profit switcher switched from NBminer to T-Rex, but NBminer wasn't closed for real. It is already running in the background (but depending to the pool with 0 hashrate).
- So there are 2 miners now and AM can't show the numbers for the T-Rex.

Is it somehow possible to double check (and kill) old unneeded tasks? Tried it with a batch command when NBminer stops, but this doesn't work all the time (taskkill /F /IM nbminer.exe).

Hi,
Thanks for sharing the details. I can see from the API Report the T-Rex doesn't return anything and the reason is likely that NBminer uses the API port already, preventing T-Rex from using this port.

Would it be possible for you to also send me the Remote Agent log file for the time where NBMiner was supposed to be closed? You should be able to see log messages like "Closing process" and maybe even "Killing process".

What Awesome Miner do when closing mining software is to first send a friendly request to close down. Awesome Miner will then wait for the process to terminate (a number of seconds, configurable in the Options dialog, Mining Settings section), and if the process is still running, Awesome Miner tells Windows to kill the process.

Quote from: jimlite on June 10, 2019, 02:01:50 AM

Does anyone know which pool in Awesome Miner is most profitable for Nvidia gpus lately?
Thanks

For the predefined pools in Awesome Miner, the recommendation is to run the Benchmark once to make the profit switcher aware of what is most profitable. You can also view the Online Services tab in Awesome Miner at this point if you want to get an overview of the profitability of the predefined pools.

There can of course be other pools with even higher profit than those predefined in Awesome Miner as there are other mining pools for more recent coins on less common algorithms - but it requires a bit more work to keep up with all the latest and smaller coins.

Quote from: toptek12 on June 09, 2019, 06:31:51 AM

Just asking I guess awesome miner doesn't Support AMD Radeon VII ?. I don't expect it to be added right now just want to know.
it only shows the hash rate no fan speed, temps etc.

I will verify the support within the next few days and get back to you.

Quote from: Stryfe on June 08, 2019, 07:02:29 PM

another question, I have asked before but I cannot figure it out --

how do I set different profit profiles for my SHA256 miners? I have tried adding additional ones but whatever I set for one SHA256 miner it sets all of the SHA256 miners to the same one. This does not work for me as some are S9's (all of which do not use the same power) some are T15's and some are T17's --- all of them use different amounts of electricity and I would like to set it for each one separately.

First of all you need more than one profit profile. Please make sure you define for example a S9 and T15 profile in the Options dialog, Profit profile section, where you can add additional profiles. Each profile are configured independently, making it possible for you to specify one hashrate+power for the S9 profile and completely different numbers for the T15 profile.

In the Properties for a miner, you can then select if it should use the S9 profile or the T15 profile as "Profit profile".

Quote from: GKumaran on June 08, 2019, 09:42:22 AM

Awesome miner could add support for device selection in TRM, as currently using the device selection doesnt add the correspondin '-d ' command to the miner. That may solve ur issues.

As for the crashes, I have no clue, mine works fine. Which algo and clocks/timing are you running?

Edit: @Patrik : would be possible to intergrate device selection and builtin watchdog( --watchdog_script=X.bat ) to TRM, the script could be almost same as the SRB one that u have intergrated in AM. Cheesy

I will look into the device selection for TRM.

For watchdog script - I can look into that as well - but do you have any example of what the script would do in the TRM scenario?
For SrbMiner it's needed for terminating the SrbMiner process - in order to let Awesome Miner restart the mining process instead.

Quote from: nordmann666 on June 08, 2019, 09:07:10 AM

Quote from: GKumaran on June 08, 2019, 08:41:56 AM

Quote from: nordmann666 on June 08, 2019, 06:59:57 AM

latest version with a minor and a major problem

1. Awesomeminer shows me wrong GPU if i dont use all GPU´s

for example my 8 card Vega Rig:
TRM 0.5.0(also on 0.5.1)
-d 0 -> it show a not active card but i see shares in "Progress" tab
https://ibb.co/rZBzR4R

-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active
https://ibb.co/bBchQvT

2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore
the same thing with SRBMiner
i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems

is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever?

I use TRM and AM.

1. use TRM with --bus_reorder and then map the GPU in AM in the ascending order of the PCI BUS ID.
This worked for me, cause Default TRM uses Opencl order, --bus_reorder uses BusID order and AM uses the driver order by default.

2. Right click the miner and select view details -> process information. Verfiy that the command line param are correct.
Right click the miner in AM and select diagnostics -> u should be able to see what went wrong. I can personally confirm that TRM and SRB works fine on my remote 6x Vega Rig for months.

i have other rigs that also work...but like you can see at the screenshots (the links) that it dont matter to use or not use bus-reorder...Awesomeminer show me wrong GPU and after 10-30 minutes no shares and TRM and SRB stop working and i cant close or restart or reboot or anything...i have to power off and restart

without using Awesomeminer (and using same parameters in batch, that i use in awesomeminer) it workes for hours now

Hi,
Please us the "Map to system monitoring" dialog to change the order of the cards using the Up and Down arrow. In your first screenshot I think you should put Device#7 on top for example.

For the mining related issues and the command line - is the Diagnostics output (click the Diagnostics button in the toolbar) in Awesome Miner giving the exact same command line arguments as you have in your batch file? The Diagnostics will show exactly how Awesome Miner started the mining software and it will include both the command line arguments generated by Awesome Miner in combination with any manual commands you added.

You could also try to launch the mining software via Awesome Miner - then close down Remote Agent when the mining has started. Do you still get the crashes?

Quote from: Stryfe on June 07, 2019, 05:59:06 PM

Quote from: patrike on June 07, 2019, 05:46:50 PM

Yes, it will be included in the next release.

thank you Patrike

also, I have not read all the back posts - have you managed a way to get ssh into the bitmain miners yet? or have they released a firmware allowing it?

There are no solution to the SSH limitations yet and it looks like Bitmain are continuing to release new firmware with SSH disabled. I've been trying to get Bitmain to implement a setting to enable Privileged API access, but unfortunately no progress on that request either.

A while ago I added the features to set Default Pools and Reboot by connecting to the Antminer web interface instead of SSH - but those where just workarounds for the fact that SSH wasn't available.

Quote from: Stryfe on June 07, 2019, 11:55:22 AM

Quote from: patrike on June 07, 2019, 11:18:03 AM

Quote from: Stryfe on June 07, 2019, 01:38:26 AM

Quote from: patrike on June 06, 2019, 07:36:30 AM

Quote from: Stryfe on June 06, 2019, 01:10:00 AM

pm sent with the API log

Perfect - thanks for the log!

I had to make a small adjustment to get Awesome Miner to detect this miner as a BW-L21. Once that detection was updated, it shows up fine.

nice! so in a future update?

Yes, it will be included in the next release.

Quote from: Stryfe on June 07, 2019, 01:38:26 AM

Quote from: patrike on June 06, 2019, 07:36:30 AM

Quote from: Stryfe on June 06, 2019, 01:10:00 AM

pm sent with the API log

Perfect - thanks for the log!

I had to make a small adjustment to get Awesome Miner to detect this miner as a BW-L21. Once that detection was updated, it shows up fine.

Quote from: patrike on June 03, 2019, 05:43:33 PM

Quote from: Anamorphic on June 03, 2019, 04:24:23 PM

Quote from: patrike on June 02, 2019, 08:47:48 PM

Quote from: Anamorphic on May 31, 2019, 08:23:37 PM

Hey Patrike,
Is there a way to set the Global Electricity Price (per kWh) via HTTP API?
Thank you!

There are no feature to set the value via API today.

You can set the price via the Rules, where you can use the Action called Set Property. You can for example use the rules to define different electricity prices depending on time or day. Rule actions can also be triggered via the API if needed.

I do understand this doesn't give as much flexibility as having an API method for setting an exact price from an external application. Please let me know if you still prefer the API method and I will look into supporting it when possible. Thanks!

Hey Patrike,

If you could add it to your ever expanding "to-do list" that would be awesome! That would help me a lot!

Here in Texas we have the option to go with a variable rate electricity plan that changes the price per kWh every 5 minutes. I'm currently monitoring the real-time price and have different rules and profiles setup in AM for my miners. For example, if the price per kWh goes crazy, up to say $1.00 /kWh, then my mine basically shuts down until the price drops. If the price goes negative (which happens often at night), the miners will overclock and go nuts!

One more thought that might open up a whole new world of possibilities for AM: What if you gave us the option to pass a variable into AM via API that could be used elsewhere in the application? Maybe just a few empty variable slots (Var1, Var2, Var3, etc.) then those variables could be used as "Triggers" inside a rule. Just a thought.

Thanks again!

The API method for electricity price should be possible to include in the near future as it's only a matter of exposing a feature already available.

Thanks for the suggestion about variables, that would make sense as well. Another concept available already today via the triggers are Miner Tags. You can set Tags on miners via the API and you can have trigger looking at certain tags.

A short update about the API method for setting the global electricity price:
POST http://mypc:17790/api/settings/electricity_price?value=0.075
This feature is available in Awesome Miner 6.5.3

Quote from: GKumaran on June 06, 2019, 04:04:46 PM

Quote from: patrike on June 06, 2019, 02:53:30 PM

Awesome Miner version 6.5.3
Features
- Access to formatting of hashrate using MH/s and similar units via the Customize Progress Field feature

Thx again !!
Currently using this:

Code:

"Efficiency : " + Math.Round(status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2) + " H/W"

Couldnt find the documentation for the endpoint for the formating if its mininghelper or status object.
Would like to have a heads up on how it works.

Thanks for all nice feedback.

I've also updated the documentation page and you will find the solution at the bottom of this page:
https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-field

Code:

"Efficiency: " + miningHelper.FormatValue(Math.Round(status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2)) + " H/W"

Awesome Miner version 6.5.3

GPU mining
- Added setting to specify if Ctrl+C should be used to stop a mining process, configurable in the Options dialog, Mining Settings section
- Show GPU vendor name for nVidia devices when running Remote Agent on Linux
Features
- Access to formatting of hashrate using MH/s and similar units via the Customize Progress Field feature
User interface
- Added additional coin icons
- Display number of miners in the Mining History dialog, Mining Performance section
Rules
- Increased the maximum delay allowed to be configured for SSH actions
- Time trigger to display name of day in the trigger summary if only a single day is selected
API
- Added API to set Electricity Price via API
Mining software
- TeamRedMiner 0.5
- WildRig Miner 0.17.4
- CpuMiner-Opt 3.9.2.3

Quote from: trucobit on June 06, 2019, 12:07:38 PM

Quote from: patrike on June 05, 2019, 04:03:27 PM

Quote from: trucobit on June 05, 2019, 03:33:19 PM

https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0

and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ...

Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable.

And having seen that the same thing happens to other people, I insist on the problem.

In addition to my previous response about troubleshooting - I also see that you list quite a number of potential problematic areas.

After you made the troubleshooting I suggested earlier - please also consider to try to eliminate all these factors that could have an impact on the overall system stability. What happens if you modify you overclocking to only be a single percent of overclocking (so the overclocking code is used, but doesn't do much)? What happens if you remove all clocking for one of the miners? What happens if you close down Afterburner?

The OC of winter I have reduced it by 20% for summer, and I have even tried very low OC to see if it happened and if it happens, that was the first thing I did.

What I have not tried has been to remove the Aftherburner until there is a global FAN solution. I can not be defining a curve in each profile when I have 100 or more, and the heat is heat whatever the protocol.

I will try to remove the Aftherburner from 1 machine, the most prone and force several changes. At first you said that it would not affect but it could be.

I ask for a global Fan curve for each rig, regardless of the protocol. That would help me remove Aftherburner.

Perfect that you lowered the OC for the summer - that makes sense. Over the years I've seen the same trend every time it's May or June - I get reports about mining software crashing more frequently with clocking levels that worked fine a few months earlier.

Quote from: trucobit on June 06, 2019, 11:47:22 AM

https://www.dropbox.com/s/zynzi5nd4ywsk9s/5.png?dl=0

Another sample of bugs from the native OC.

If we see the capture, RIG3 would be 6x1080ti, gives the hash of 6, gives the consumption of 6 cards, but then the Profit is 1 card, also only gives the temperature of 1 card.

I have created a rule that counts the cards in case of missing only 1 reboot. But the curious thing that marks me the hash and consumption of 6, temperature and profit of only 1. Something is not right.

He has been like this all night and has not done auto switch because he marked a hash he was not getting. But of course the Switch does it for the hash profile of the currency not for the hash obtained, otherwise X16r would skip all the time.

AM could bring a predefined rule to detect dropped devices.

It is not shown that AM does not get the data right, it can not be working only 1 card and the hash of 6 and the consumption of 6 remain. So I can not make a rule like "if it consumes less than X trigger"

This is more related to what GPU's are being reported as active from the mining software rather than being OC related. When you run into this issue where Awesome Miner only includes one temperature reading - the following would be interesting to know:

1) On the GPU tab for this selected miner, how many GPU's are the mining software reporting. Only one, because the other failed in some way?
2) Next time the mining software report something that looks strange, please generate an API report and sent it to me via PM or mail. I can then review what the mining software is reporting.
3) Did the mining software console window indicating that it was only mining on a single GPU or all 6 GPU's where mining perfectly fine?

It's possible that there is some case where GPU's are being partially reported correctly from the mining software and the display in Awesome Miner gives a temperature and power summary that looks strange - but we need the information above in order to really tell if that's the case.