I'm not able to reproduce this. Can you please share more details?
If you start and stop a Managed Miner - is it still running? Are you launching the mining software in Admin mode or are there any other non-default settings?

This is the first time I get a request for this miner. What happens if you add it to Awesome Miner, is there something specific that doesn't show up correctly? Is this miner it running with Cgminer API enabled, to make it possible to monitor?

Could you please send me the API Report (toolbar: Tools -> API Report) if possible (by PM or mail). Thanks!

Hi,
Which mining software are you running? There are some command line help for popular mining software on the FAQ page:
https://beam.leafpool.com/getting-started
For Gminer you manually need to add "--ssl 1" for example.

Please share the full Diagnostics output from the mining software if it's still failing. Thanks!

Awesome Miner version 6.9.4

 Configuration
  - Added a new setting to configure how many ASIC miners to connect to at the same time for monitoring information
 Features
  - The Information column can display the miner unique worker name
  - The Information column can display the power efficiency (Hashrate per Watt)
 Mining software
  - GMiner 1.60

Please begin with upgrading to the latest version of Awesome Miner, to get the correct Beam coin statistics.

If you want to mine Beam on a specific pool, the general concept is the following:
1) Add a new pool in Awesome Miner, where you enter the Pool Connection URL and worker name - according to the instructions on the pool web site. Select Beam
2) Add a new miner and select Managed Miner. Select "Equihash 150,5,3 (BeamHashII)" as algorithm, for example GMiner as mining software and select the pool you added in the previous step.

Please let me know if it's a specific Beam mining pool you would like to use, and want assistance in finding out how to fill in the pool details in Awesome Miner.

Awesome Miner version 6.9.3

 ASIC mining
  - Detect incorrect hashrate numbers reported by Antminers and calculate the hashrate in an alternative way
 GPU mining
  - Added a button on the System tab to restart nVidia NVML monitoring - in case the drivers fail to report power usage
 Integration
  - BEAM correctly supported with coin statistics
 Mining software
  - Claymore Ethereum miner 15.0
  - BMiner 15.8.4
  - LolMiner 0.8.8
  - Miniz Miner 1.5q2

Hi,

Thanks for your detailed reply and your honest feedback - it's appreciated.

It may not have been a fully fair evaluation of the firmware performance if there at the same time were attempts made to bypass the DevFee pool mining. It becomes difficult to tell if it's an evaluation of the firmware performance or an evaluation of the firmware tamper protection.

Anyway, I do see the main point you bring up here, related to the mining fee. I will try to give some background information here to at least explain it - also because there were a number of posts about the mining fee earlier in this thread.

First of all, we have not developed this firmware from scratch on our own. We don't have the resources to do that. The firmware is the result of a partnership where we have been working close with a firmware developer to provide better integration between the Antminer firmware and the Awesome Miner application. For this reason, I don't have control over the mining fee level. If we would have the resources to develop our own firmware, it would of course be a completely different case regarding the mining fee.

It all started with a number of existing users contacted us and pointed out that they successfully been testing different custom firmware (all with ~2% mining fee) and wanted to deploy this on a larger scale with better Awesome Miner integration. When running mining operations at this scale, getting performance improvements of >10% results in quite a large amount of extra income - making it easy for them to accept a mining fee. Other users were already running some custom firmware solutions with a 2% mining fee, but also wanted a better integration with Awesome Miner.

By making this firmware partnership that resulted in the Awesome Miner Antminer firmware in combination with better Awesome Miner integration - we could offer a solution to these users that made them super happy. As some already had firmware solutions with a 2% mining fee, the Awesome Miner firmware delivered better integration for the same mining fee.

I do understand that the concept of a mining fee can upset some users. However, the alternatives we had was never about having a mining fee or not having a mining fee - it was about if we would provide this firmware as an option to the users that would find it valuable - or not provide any firmware solution at all.

So the bottom line is that the firmware, with the mining fee, is offered as an option for those that finds it a valuable. Some of our customers are very happy with this solution but I also have full understanding that the firmware may not be for everyone. If someone is looking for an open source solution without a mining fee, BraiinsOS is a great option. I've had a number of discussions with the BraiinsOS developers to make sure Awesome Miner runs fine with their firmware. From an Awesome Miner perspective, you should of course be able to run the firmware solution you want - but I don't see anything wrong in giving our users one more option to choose between. If our reputation is questioned because of this, I might have failed in explaining the idea behind the firmware as it wasn't released with the intent to make anyone upset - just in response to what some of our users were asking for.

Thanks!

Hello,

Thanks for trying out the firmware and for your feedback.

About the number of Accepted share - the difficulty level on the two DevFee pools are very low compared to your main pool. For this reason the DevFee pools will produce many more accepted shares, although they are running on a hashrate no more than 2% of the total available hashrate. For this reason it's not possible to look only on the Accepted value to understand how the hashrate is distributed.

For the hashrate drop at the pool I would need more information in order to investigate. Did you experience this pool hashrate drop shortly after applying the firmware or did it happen all of a sudden? Was it before or after you tried to delay the network trafic to the DevFee pool - which of course would result in connection issues and the reboots?

Typically when you apply this firmware and select a Mining Profile is that the firmware will do auto tuning of the ASIC chips. Depending on if they are in good shape or not, and what Mining Profile you selected, this process can take some time. Everything from 10 minutes to many hours.

We have a number of customers running this firmware on quite large scale mining operations with very good results. It also looks like several users in this thread have successfully deployed the firmware.

Just reach out to me if you want me to investigate your scenario further to find out why it didn't perform as expected. Also let me know if you have any questions. Thanks!

The coins are most likely not on the public blockchain so it isn't possible to monitor the balance unless the pool provides some kind of interface (API) where the balance can be requested. These API's are typically unique per pool so there are unfortunately no universal solution to this.

Thanks for the update. Isn't the main reason why P6 uses less power than P7 because it by default uses a lower GPU clock, lower GPU voltage, lower Memory clock and lower Memory voltage? If you configure P7 with the same parameters as P6, isn't the power usage the same?

The custom HTML tags you can use in the progress field are currently not evaluated in the web because of security reasons. It might be supported in the future, but right now it's limited to the Miners list in the Windows application.

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

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?

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.

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.

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

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

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.

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!

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