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

Austpool

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...

Austpool

newbie

Activity: 23

Merit: 0

Quote from: toptek12 on August 20, 2019, 11:01:04 AM

Quote from: patrike on August 20, 2019, 03:29:20 AM

Quote from: toptek12 on August 19, 2019, 05:06:34 PM

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.

toptek12

member

Activity: 126

Merit: 10

Quote from: patrike on August 20, 2019, 03:29:20 AM

Quote from: toptek12 on August 19, 2019, 05:06:34 PM

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.

patrike

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

Siolim

newbie

Activity: 107

Merit: 0

Quote from: patrike on August 20, 2019, 03:25:39 AM

Quote from: Siolim on August 19, 2019, 06:17:26 AM

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

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MoparMiningLLC on August 19, 2019, 07:26:17 PM

Quote from: jstefanop on August 19, 2019, 02:01:58 PM

Quote from: MoparMiningLLC on August 15, 2019, 02:05:02 PM

Quote from: MoparMiningLLC on August 18, 2019, 10:50:13 AM

Quote from: patrike on August 18, 2019, 08:57:26 AM

Quote from: MoparMiningLLC on August 16, 2019, 05:24:13 AM

Quote from: patrike on August 16, 2019, 02:15:16 AM

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.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: toptek12 on August 19, 2019, 05:06:34 PM

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!

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Siolim on August 19, 2019, 06:17:26 AM

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.

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Quote from: jstefanop on August 19, 2019, 02:01:58 PM

Quote from: MoparMiningLLC on August 15, 2019, 02:05:02 PM

Quote from: MoparMiningLLC on August 18, 2019, 10:50:13 AM

Quote from: patrike on August 18, 2019, 08:57:26 AM

Quote from: MoparMiningLLC on August 16, 2019, 05:24:13 AM

Quote from: patrike on August 16, 2019, 02:15:16 AM

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.)

toptek12

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..

Siolim

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?

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Quote from: patrike on August 18, 2019, 08:57:26 AM

Quote from: MoparMiningLLC on August 16, 2019, 05:24:13 AM

Quote from: patrike on August 16, 2019, 02:15:16 AM

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.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MoparMiningLLC on August 16, 2019, 05:24:13 AM

Quote from: patrike on August 16, 2019, 02:15:16 AM

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.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: bensam1231 on August 16, 2019, 03:29:00 AM

Hey Patrike, please add SSL support. Some miners with really weird command line parameters need it entered straight into the command line string, such as with miniz. This is pretty important for a lot of different pools.

Thanks.

Good point. For some mining software Awesome Miner do translate URL's like stratum+ssl://somepool... into parameters required for SSL to work. There are however no general concept for this that works across all mining software and it should preferrably just be a checkbox in the Pool Properties.

joseph32

member

Activity: 418

Merit: 21

Quote from: STSMiner on August 16, 2019, 11:48:05 AM

Quote from: joseph32 on August 16, 2019, 07:14:56 AM

Whats the API identifier code for the new Nicehash Beamv2? Just wanted to add it as userdefined, but cant find that damn code Huh

45

THANKS!

STSMiner

full member

Activity: 270

Merit: 115

Quote from: joseph32 on August 16, 2019, 07:14:56 AM

Whats the API identifier code for the new Nicehash Beamv2? Just wanted to add it as userdefined, but cant find that damn code Huh

45

joseph32

member

Activity: 418

Merit: 21

Whats the API identifier code for the new Nicehash Beamv2? Just wanted to add it as userdefined, but cant find that damn code Huh

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Quote from: patrike on August 16, 2019, 02:15:16 AM

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

bensam1231

legendary

Activity: 1764

Merit: 1024

Hey Patrike, please add SSL support. Some miners with really weird command line parameters need it entered straight into the command line string, such as with miniz. This is pretty important for a lot of different pools.

Thanks.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MoparMiningLLC on August 15, 2019, 07:49:43 PM

@patrike - AM picked up my FutureBit Apollo miner with ease but its reporting the hash wrong - per pool and gui I am hashing right at 105 mh/s in eco mode - AM shows the miner at 2.74 mh/s

my guess is that it is not picking up all the chips?

note: it is identifying it as a FPGA miner not as an ASIC

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.

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