[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 152.

kerney666

member

Activity: 658

Merit: 86

Quote from: patrike on July 05, 2019, 04:15:50 AM

Quote from: kerney666 on July 05, 2019, 12:50:18 AM

Quote from: joseph32 on July 04, 2019, 03:39:05 PM

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
> Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalksearch.org/topic/m.51712911

Hi Patrik! Let me know if you need dev assistance sorting this out, a little surprising, not sure what we’re doing to confuse you when running in normal mode. Would be great to sort it out!

Thanks for your assistance. I think I was able to figure out the scenario here.

If Awesome Miner sends API requests to TeamRedMiner when doing MTP mining, TeamRedMiner will terminate. If I use any other algorithm, it looks fine.

So I think it's something with the API request processing inside TeamRedMiner specifically when doing MTP mining. Please let me know if it's anything else you want me to investigate. Thanks!

Got it, so we have a seg fault for MTP API calls, we’ll address it ASAP.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: kerney666 on July 05, 2019, 12:50:18 AM

Quote from: joseph32 on July 04, 2019, 03:39:05 PM

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
> Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalksearch.org/topic/m.51712911

Hi Patrik! Let me know if you need dev assistance sorting this out, a little surprising, not sure what we’re doing to confuse you when running in normal mode. Would be great to sort it out!

Thanks for your assistance. I think I was able to figure out the scenario here.

If Awesome Miner sends API requests to TeamRedMiner when doing MTP mining, TeamRedMiner will terminate. If I use any other algorithm, it looks fine.

So I think it's something with the API request processing inside TeamRedMiner specifically when doing MTP mining. Please let me know if it's anything else you want me to investigate. Thanks!

kerney666

member

Activity: 658

Merit: 86

Quote from: joseph32 on July 04, 2019, 03:39:05 PM

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
> Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalksearch.org/topic/m.51712911

Hi Patrik! Let me know if you need dev assistance sorting this out, a little surprising, not sure what we’re doing to confuse you when running in normal mode. Would be great to sort it out!

joseph32

member

Activity: 418

Merit: 21

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
> Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0)
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalksearch.org/topic/m.51712911

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Lunga Chung on July 04, 2019, 09:17:35 AM

It looks like on the latest version dashboard isn't updating coin value, I see old prices for coins selected on the bottom of the dashboard

Is the feature to check for software updates working? It's using the same Amazon cloud server for getting the information. In the past it downloaded it via other sources.

If you go to the Menu -> Update mining software definitions you should see GMiner 1.50 for example - unless you upgraded to it earlier today. GMiner 1.50 is not part of the latest release.

If you want you can send me your Awesome Miner log file via PM and I can review the case. Thanks!

Lunga Chung

member

Activity: 277

Merit: 23

It looks like on the latest version dashboard isn't updating coin value, I see old prices for coins selected on the bottom of the dashboard

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: ?? on ??

Hi Patrike,

it's possible to change xmrig cpu miner with xmrigcc miner?

https://github.com/Bendr0id/xmrigCC

It support all cryptonight variant and auto core/thread.

Thanks

Is this a fork of XMrig CPU miner where it also includes a web interface? So from a mining point of view, it's identical to XMrig CPU miner?

If it's fully compatible, you can change the download URL for XMrig CPU miner via the Options dialog, Managed Software section.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: slysir on July 04, 2019, 05:58:13 AM

Download URL changed for Gminer-1.50 and miniZ 1.4o

https://github.com/develsoftware/GMinerRelease/releases/download/1.50/gminer_1_50_windows64.zip

I will add Gminer 1.50 right away. It looks like version 1.48 and 1.49 was removed

For miniZ it looks like their SSL certificate on the website has expired for HTTPS. I will change all download URL's to HTTP instead.

In a few minutes from now you will be able to update the mining software definitions to get these changes.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: buckrogers on July 03, 2019, 11:30:02 PM

Does anyone know if awesome miner can support the futurebit apollo scrypt miner?

I can't seem to gain access to it as Apollos run bfgminer.

thanks!

I don't have any experience with this specific miner. Bfgminer should however be able to provide a monitoring interface where Awesome Miner can connect.

Are there any settings in the web interface called "API" or something with related to Bfgminer?
Is it possible to SSH to this miner?

slysir

newbie

Activity: 52

Merit: 0

Download URL changed for Gminer-1.50 and miniZ 1.4o

https://github.com/develsoftware/GMinerRelease/releases/download/1.50/gminer_1_50_windows64.zip

buckrogers

legendary

Activity: 2746

Merit: 1181

Does anyone know if awesome miner can support the futurebit apollo scrypt miner?

I can't seem to gain access to it as Apollos run bfgminer.

thanks!

NetfetMiningCompany

jr. member

Activity: 315

Merit: 8

Quote from: patrike on July 03, 2019, 04:28:11 AM

Quote from: NetfetMiningCompany on July 02, 2019, 09:57:05 AM

Whats the easiest way to run the nano miner as admin through AM? when i turn the software on, it says i should do it.

im also getting 2 different power output readouts on the graphics card. AM says a card will be 90w, but nanominer says 67w. which would be more accurate?

To run a miner as administrator, please right click on the miner, select Properties and then go to the Environment section where you can enable the Admin setting.

AMD is not reporting as accurate power usage values as nVidia do. For this reason Awesome Miner is by default adding 35% to the power usage to make it a bit more realistic. You can change this in the Options dialog, GPU settings section. If you set it to 0%, Awesome Miner should show the same value as nanominer - but I also think that would be less realistic.

Makes sense. Thank you.

patrike

legendary

Activity: 3346

Merit: 1094

Awesome Miner version 6.6.2

ASIC mining
  - Feature to send custom web commands to an Antminer
Mining software
  - Added mining software: NoncerPro 3.0.2
  - Nanominer 1.4.1
  - Miniz miner 1.4o
  - CpuMiner-Opt 3.9.5.1
  - Lolminer 0.8.3

Please note that we make many of the mining software updates available even before these releases - via the 'Update mining software definitions' feature.

joseph32

member

Activity: 418

Merit: 21

Quote from: patrike on July 03, 2019, 08:34:45 AM

Quote from: joseph32 on July 03, 2019, 08:30:32 AM

Hey Patrik,

sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...

Is it possible to add a trigger like "For X Seconds"?

This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
And it wouldn't have triggered in that case.

For the hashrate, you can actually add multiple "Check statistics" triggers - one that is looking at the current value and one that is looking at the hashrate value 1 or 2 minutes ago. You can then set your rule to only trigger if it matches both these conditions. This makes it possible to not trigger it too frequently.

For Device Count there are no feature like this, but I understand your suggestion for this one as well. Thanks!

Ha, never thought about those tricky hashrate multi-check-rules, but will do now

Thanks!

Sometimes if AM switch from one miner to another, one or some devices are "lost" for a second and all the alarm rules will trigger. Maybe you have a better solution for this scenario, would be great.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: joseph32 on July 03, 2019, 08:30:32 AM

Hey Patrik,

sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...

Is it possible to add a trigger like "For X Seconds"?

This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
And it wouldn't have triggered in that case.

For the hashrate, you can actually add multiple "Check statistics" triggers - one that is looking at the current value and one that is looking at the hashrate value 1 or 2 minutes ago. You can then set your rule to only trigger if it matches both these conditions. This makes it possible to not trigger it too frequently.

For Device Count there are no feature like this, but I understand your suggestion for this one as well. Thanks!

joseph32

member

Activity: 418

Merit: 21

Hey Patrik,

sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...

Is it possible to add a trigger like "For (at least): X Seconds"?

This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
In the case above the rules wouldn't have triggered because they are now in the limit.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on July 02, 2019, 11:00:37 PM

I just tried and it works well. If it is true that controls the core for each card to control the maximum temperature. But it does it in a very abrupt way, it goes from 1600 to 900 suddenly, then it goes up to 1200, then it goes down to 900, and so for a while.

As a result the Rig with so abrupt change of core at the end falls and is interrupted continuously. It stops the miner, then starts (without failing notifications), and of course it is worse. I'm talking about a restart every 4 or 5 minutes on a constant basis.

I think the idea is good but it has to be a bit more refined, to do it in a softer way to avoid so many big core changes continuously, and to be able to find a core value quickly that works to maintain the temperature, could make more changes small of core, not 500 mhz of blow, perhaps 100 in 100 and leaving a few seconds in between.

The 1080ti are problematic and very delicate. For example in MTP I invest in 85 90 500, now I am with 70 50 300 and limitation to 76 degrees, but the core of the hot cards changes so much and so fast that it produces multiple falls of the mine, it recovers at the moment, but not It can be like this.

@patrike you could debug this maximum temperature function. The idea is very good but I think the changes are very big and frequent, it could be softer, but little by little. I hope you consider it.

regards

The Temperature Limit you can define is a way to tell the nVidia drivers that they should enforce the limit. Awesome Miner has no control of how this limit is enforced. It's also the same as if you use other overclocking tools, they can also only set the limit but it's up to the nVidia drivers to do the actual work.

Like you point out it might be that the clock speed is lowered significantly. I suppose this is a balance between setting a low clock for a shorter period of time vs setting just a little lower clock for a longer period of time. I don't know if there even is a manual way to configure this behavior for nVidia.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on July 02, 2019, 01:25:46 PM

Hello Patrike, I have a doubt in the auto profit mode with the OC.

I have rigs that are multi-brand, each card is a different brand but they are all 1080ti, but there are some brands that go with too much factory OC.

So the problem that I have that only one OC for all the cards is not valid for me. While some are at 65 degrees another one reaches 84 and stops. They are the MSI ARMOR with a special Artic ventilation kit, and I can not use them. They have a very high CORE. If under the core so that only that card is not hot, in the end the rig produces me less, I have a card at 77-78 degrees and the others at 65 or less.

I do not see that there is a way to save OC profiles, in which each card can have its own core, memory, power, limitation. I think in managed if you can, but in Auto profit no.

I think this is a situation that can be given to many people, that one card gets hotter than the rest and you have to lower the general OC, instead of defining for example a profile for "Rig5 MTP" "RIG5 X16R" with which could reduce the core of MSI armor but leave the others with more power because they do not heat up as much.

It would be a perfect scenario to make totally personalized profiles, and it is as easy as making a general one and when you have it, you modify it card by card, going to the one that gets hotter and only that lowering the core enough so that it does not overheat. And the average hash of the Rig would be greater than if under the OC to all the cards.

I have changed the thermal paste, the thermal pads, I have put the best air cooling kits that is Artic Cooler IV with huge rear heat sink. But seeing Clocking in AM, I see that these cards are 100mhz higher in the core than the other models. This is a huge difference.

It is a lot of work to make fully customized profiles to several RIGS for each al-go, but the work does not scare me, so there is no possibility of doing what I ask. It would be the perfect option to finish the OC, even forgetting about the double OC that I asked, because this is a much more serious problem for me. In winter there are no problems with this because the air of the street is very cold, but in summer you can notice that difference of OC in a single card.

You should be able to use Clocking Profile Groups (Options dialog, GPU Clocking Profiles section) to define for which GPU to apply a certain Clocking Profile.

In the past you could only specify by GPU ID or GPU Name (like 1080), but in recent version you can also specify by vendor (ASUS, MSI, ...) which might be of help here. You can for example have one overclocking profile set for all ASUS cards and another one for the MSI cards. If you have multiple types of MSI cards (Armor and Gaming) there are however no solution except using GPU ID's.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Siolim on July 02, 2019, 11:47:10 AM

Hello

How to get the complexity and the current nethash from the Explorer https://explorer.web.sero.cash via a get request?

Unfortunately I don't have an answer to this - but there might be someone else in the community that are more experienced with extracting data from block explorers.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: NetfetMiningCompany on July 02, 2019, 09:57:05 AM

Whats the easiest way to run the nano miner as admin through AM? when i turn the software on, it says i should do it.

im also getting 2 different power output readouts on the graphics card. AM says a card will be 90w, but nanominer says 67w. which would be more accurate?

To run a miner as administrator, please right click on the miner, select Properties and then go to the Environment section where you can enable the Admin setting.

AMD is not reporting as accurate power usage values as nVidia do. For this reason Awesome Miner is by default adding 35% to the power usage to make it a bit more realistic. You can change this in the Options dialog, GPU settings section. If you set it to 0%, Awesome Miner should show the same value as nanominer - but I also think that would be less realistic.

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