Author

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

legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
Awesome Miner version 6.9.2

 ASIC mining
  - Support for FutureBit Apollo LTC miner
 Integration
  - Dynamic update of coin properties improved to support more API data formats
 Mining software
  - GMiner 1.59
  - TT-Miner 3.0.5
 Corrections
  - Correction to Information column display for Managed Miners

AM is reporting correctly now for the Apollo - thanks!
member
Activity: 204
Merit: 10
Feature Request:
  • Sort Pool list via coins
  • Add external application OC for AMD Vega via OverdrivenTool, pretty simple cli
  • Or, Add support for selecting min fan RPM and P state selection in Vega OC in AM
Thanks for the suggestions.

As Awesome Miner has a Native Overclocking feature - that one will be the main focus for overclocking. It's however fully possible to manually configure any command line to be executed when starting the mining software.

Earlier this year AMD introduced a concept of a Fan Curve in their drivers and Awesome Miner supports this as well via the GPU clocking dialog. It allows to define 5 different fan speed levels depending on the temperature, making it possible to use for both setting the minimum and maximum fan speed.

Awesome Miner is currently setting the GPU Clock/Voltage and Memory Clock/Voltage on the high performance P-state (P7 for the GPU, P2 or P3 for Memory). Is there a scenario where the Vega doesn't go to P7 correctly during mining?

Yes, there are situations where to save power it is preferable to mine using a lower p state either in GPU or memory.

Also, in the dashboard via HTTP API, (used in custom progress field) is not being converted from HTML tags to Text, rather being shown as raw text.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.9.2

 ASIC mining
  - Support for FutureBit Apollo LTC miner
 Integration
  - Dynamic update of coin properties improved to support more API data formats
 Mining software
  - GMiner 1.59
  - TT-Miner 3.0.5
 Corrections
  - Correction to Information column display for Managed Miners
legendary
Activity: 3346
Merit: 1094
Feature Request:
  • Sort Pool list via coins
  • Add external application OC for AMD Vega via OverdrivenTool, pretty simple cli
  • Or, Add support for selecting min fan RPM and P state selection in Vega OC in AM
Thanks for the suggestions.

As Awesome Miner has a Native Overclocking feature - that one will be the main focus for overclocking. It's however fully possible to manually configure any command line to be executed when starting the mining software.

Earlier this year AMD introduced a concept of a Fan Curve in their drivers and Awesome Miner supports this as well via the GPU clocking dialog. It allows to define 5 different fan speed levels depending on the temperature, making it possible to use for both setting the minimum and maximum fan speed.

Awesome Miner is currently setting the GPU Clock/Voltage and Memory Clock/Voltage on the high performance P-state (P7 for the GPU, P2 or P3 for Memory). Is there a scenario where the Vega doesn't go to P7 correctly during mining?
member
Activity: 204
Merit: 10
Feature Request:
  • Sort Pool list via coins
  • Add external application OC for AMD Vega via OverdrivenTool, pretty simple cli
  • Or, Add support for selecting min fan RPM and P state selection in Vega OC in AM
full member
Activity: 195
Merit: 104
@patrike is there any way i can change tags in bulk? When i mark couple miners and choose tag only one miner gets it
When using the panel at the bottom of the screen, it only operates on a single miner. Please select multiple miners and go to the toolbar Find -> Tag Filter -> Edit Tags. The upper part of this dialog has a push-button for each of the available tags. Click on these buttons to assign the tags to all the selected miners.
That worked, thanks
legendary
Activity: 3346
Merit: 1094
@patrike is there any way i can change tags in bulk? When i mark couple miners and choose tag only one miner gets it
When using the panel at the bottom of the screen, it only operates on a single miner. Please select multiple miners and go to the toolbar Find -> Tag Filter -> Edit Tags. The upper part of this dialog has a push-button for each of the available tags. Click on these buttons to assign the tags to all the selected miners.
full member
Activity: 195
Merit: 104
@patrike is there any way i can change tags in bulk? When i mark couple miners and choose tag only one miner gets it
legendary
Activity: 3346
Merit: 1094
Hi,

I have no problem adding custom data sources with block explorer API in AM except with this one.
https://myexplorer.wrkz.work/q/reward
https://myexplorer.wrkz.work/q/hashrate

None of them works, even though it doesn't seems to be different from another API (http://188.165.217.191:3001/api/getdifficulty)
I leave JSON expression empty and it says that it's unable to read value.

Thx
Hi,
It turns out that these two API links returns a newline character before the actual number and Awesome Miner didn't handle this very well. In the web browser it's not possible to see difference, but the actual data is different.

I will correct this in the next release.
newbie
Activity: 21
Merit: 0
Hi,

I have no problem adding custom data sources with block explorer API in AM except with this one.
https://myexplorer.wrkz.work/q/reward
https://myexplorer.wrkz.work/q/hashrate

None of them works, even though it doesn't seems to be different from another API (http://188.165.217.191:3001/api/getdifficulty)
I leave JSON expression empty and it says that it's unable to read value.

Thx
legendary
Activity: 3346
Merit: 1094
also, i have this error coming up when tying to run Bminer.



Initialize diagnostics (40)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.9.1
OS: Microsoft Windows 10 Home 64-bit
nVidia driver version: 431.60
nVidia OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: BMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Set clocking start profile: 25, 1060 core (when stopping, the following will be used: 12, type: Single, Use: True)
Properties: (WindowMode: ConsoleFormat, EngineType: BMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\miner\AppData\Roaming\AwesomeMinerService\bminer-v15.8.3-fc8dae9-amd64_1\bminer-v15.8.3-fc8dae9\bminer.exe  -watchdog=false -uri beamhash2://@beamv2.usa-new.nicehash.com:3378 -api=0.0.0.0:4028
====================================================================================================
Mining Engine Process started, PID: 2568
> [INFO] [2019-08-21T11:25:10+10:00] Bminer: When Crypto-mining Made Fast (v15.8.3-fc8dae9)
> [INFO] [2019-08-21T11:25:10+10:00] Detecting platform                          
> [FATA] [2019-08-21T11:25:17+10:00] CudaError: Unknown error: c:\windows\system32\nvapi64.dll

====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed


i have a fresh install of 431.60 drivers, done as a clean install.
other mining software is working fine, just no OC.


EDIT: after downgrading to 425.31, bminer still crashes for me with another error, so i'm thinking this one is a rig issue. however, the error while on 431.60 didn't go away when going up to 436.02(latest), so it might help with the OC issue...
Hi,

The first issue you reported indicates that it was some nVidia driver issue - as Bminer failed to use one of the main DLL-files for the drivers.
Code:
> [FATA] [2019-08-21T11:25:17+10:00] CudaError: Unknown error: c:\windows\system32\nvapi64.dll
If Bminer fails to initialize the nVidia drivers it may very well cause the overclocking via Awesome Miner to fail for the same reason.

After you downgraded the nVidia driver, you said that you got another error message - what is the error message you get from Bminer in this case? As you pointed out - it sounds like some driver issues specific to this rig.
newbie
Activity: 23
Merit: 0
also, i have this error coming up when tying to run Bminer.



Initialize diagnostics (40)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.9.1
OS: Microsoft Windows 10 Home 64-bit
nVidia driver version: 431.60
nVidia OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: BMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Set clocking start profile: 25, 1060 core (when stopping, the following will be used: 12, type: Single, Use: True)
Properties: (WindowMode: ConsoleFormat, EngineType: BMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\miner\AppData\Roaming\AwesomeMinerService\bminer-v15.8.3-fc8dae9-amd64_1\bminer-v15.8.3-fc8dae9\bminer.exe  -watchdog=false -uri beamhash2://@beamv2.usa-new.nicehash.com:3378 -api=0.0.0.0:4028
====================================================================================================
Mining Engine Process started, PID: 2568
> [INFO] [2019-08-21T11:25:10+10:00] Bminer: When Crypto-mining Made Fast (v15.8.3-fc8dae9)
> [INFO] [2019-08-21T11:25:10+10:00] Detecting platform                           
> [FATA] [2019-08-21T11:25:17+10:00] CudaError: Unknown error: c:\windows\system32\nvapi64.dll

====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed


i have a fresh install of 431.60 drivers, done as a clean install.
other mining software is working fine, just no OC.


EDIT: after downgrading to 425.31, bminer still crashes for me with another error, so i'm thinking this one is a rig issue. however, the error while on 431.60 didn't go away when going up to 436.02(latest), so it might help with the OC issue...
newbie
Activity: 23
Merit: 0
I was hoping someone else would report it .

my
RTX 2060 super
RTX 2070
1660ti

has no fan speed or way to adjust it with the builtin oc..
So it's not only that the Native Overclocking cannot change the fan speed - the current fan speed is not display at all? I've not had any other reports on this issue.

Could you please select a miner and click on the GPU tab, then click "View GPU Details". Please share this information with me via PM or mail. Thanks!


I had to send it back with email the PM on the forums won't allow over 6000 characters.



maybe this will help. I'm getting built in OC fail after updating to 431.60 driver on Nvidia.
worked fine on 425.31.




member
Activity: 126
Merit: 10
I was hoping someone else would report it .

my
RTX 2060 super
RTX 2070
1660ti

has no fan speed or way to adjust it with the builtin oc..
So it's not only that the Native Overclocking cannot change the fan speed - the current fan speed is not display at all? I've not had any other reports on this issue.

Could you please select a miner and click on the GPU tab, then click "View GPU Details". Please share this information with me via PM or mail. Thanks!


I had to send it back with email the PM on the forums won't allow over 6000 characters.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.9.1

 Integration
  - Nicehash BeamV2 pool added (algorithm listed as Equihash 150,5,3)
 User interface
  - Show API identifier in the Pool Properties
  - Show current Mining Profile when opening the dialog to change Mining Profile for the Awesome Miner Antminer firmware
 Mining software
  - XmRig CPU Miner 3.1.0
  - TT-miner 3.0.3
  - GMiner 1.57
  - NbMiner 24.4
  - BMiner 15.8.3
newbie
Activity: 107
Merit: 0
Hi Patrike. I'm trying to add data from the exchange, the data is not readable https://open.citex.co.kr/api/v1/common/snapshot/ETH-BTC. Everything works through postman. The exchange answered me "Please add auth key in your header and the others are unchanged.

For example, headers = {'Authorization': auth key}. Your auth key is '5cc57956cbfb ************3479888143e8982d50c7115fa8d4'.

Do they have any protection?
This API requires a custom HTTP header value for "Authorization" to be set in order to access the API. Awesome Miner is unfortunately not able to set custom HTTP header values for this when making these requests.

Thanks
legendary
Activity: 3346
Merit: 1094

Can you please send me the API report via mail or PM for this miner (toolbar: Tools -> API Report)? With this information I can review what the miner is reporting and maybe adjust Awesome Miner a bit based on this.

Most likely this miner is reporting "FPGA" as device type.

sent via pm
Thanks for sharing the report. This miner is reporting a hashrate of ~2.4MH/s, which of course is incorrect given that it's actually working at a speed of >100MH/s. I wasn't able to find any details reported by the miner that would make it possible for Awesome Miner to display the true hashrate. I think it's some kind of bug in the firmware for this miner where it reports incorrect hashrate.

ok I will try and share it back with Futurebit and see what they say.

@jstefanop - can you see above? I am trying to monitor the Apollo using AM but the API log does not report the correct speed. I can see on the Apollo UI that the speed  matches what the pool reports but its not being reflected in the api data.

Please direct these questions to support thread in the future. Yes the API has some incorrect stats, we only use bits of bfgminer to run the miner, but since its a standalone unit we never fleshed out full support for bfgminer API, as this would have required way more work than needed for what we build out on the UI side.

If Aswsome miner wants to implement support, all they have to do is calculate the hash rate from work utility and difficulty (he should know how to do this but if he needs the formula just tell him to PM me.)
Thanks for sharing the information. It looks like they are aware of the hashrate reporting limitation/issue.

I prefer is the ASIC companies reports the correct information in the first place - otherwise Awesome Miner needs to find some unique detail in the API output from this miner that makes it possible to detect - then recalculate some properties - and finally make sure it doesn't have any side effect on the other 50+ ASIC miners that are supported.

What might be unique in the API output from this miner is that it uses a PGA device name "APL" (as in Apollo), so that could be a way forward.

legendary
Activity: 3346
Merit: 1094
I was hoping someone else would report it .

my
RTX 2060 super
RTX 2070
1660ti

has no fan speed or way to adjust it with the builtin oc..
So it's not only that the Native Overclocking cannot change the fan speed - the current fan speed is not display at all? I've not had any other reports on this issue.

Could you please select a miner and click on the GPU tab, then click "View GPU Details". Please share this information with me via PM or mail. Thanks!
legendary
Activity: 3346
Merit: 1094
Hi Patrike. I'm trying to add data from the exchange, the data is not readable https://open.citex.co.kr/api/v1/common/snapshot/ETH-BTC. Everything works through postman. The exchange answered me "Please add auth key in your header and the others are unchanged.

For example, headers = {'Authorization': auth key}. Your auth key is '5cc57956cbfb ************3479888143e8982d50c7115fa8d4'.

Do they have any protection?
This API requires a custom HTTP header value for "Authorization" to be set in order to access the API. Awesome Miner is unfortunately not able to set custom HTTP header values for this when making these requests.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490

Can you please send me the API report via mail or PM for this miner (toolbar: Tools -> API Report)? With this information I can review what the miner is reporting and maybe adjust Awesome Miner a bit based on this.

Most likely this miner is reporting "FPGA" as device type.

sent via pm
Thanks for sharing the report. This miner is reporting a hashrate of ~2.4MH/s, which of course is incorrect given that it's actually working at a speed of >100MH/s. I wasn't able to find any details reported by the miner that would make it possible for Awesome Miner to display the true hashrate. I think it's some kind of bug in the firmware for this miner where it reports incorrect hashrate.

ok I will try and share it back with Futurebit and see what they say.

@jstefanop - can you see above? I am trying to monitor the Apollo using AM but the API log does not report the correct speed. I can see on the Apollo UI that the speed  matches what the pool reports but its not being reflected in the api data.

Please direct these questions to support thread in the future. Yes the API has some incorrect stats, we only use bits of bfgminer to run the miner, but since its a standalone unit we never fleshed out full support for bfgminer API, as this would have required way more work than needed for what we build out on the UI side.

If Aswsome miner wants to implement support, all they have to do is calculate the hash rate from work utility and difficulty (he should know how to do this but if he needs the formula just tell him to PM me.)
Jump to: