I'll have to try again tomorrow, but I now suspect it's the dual mining implementation with NBMiner, my scenario is when mining ckb+eth, where I needed to specify dual intensity for Ethereum not to lose hashrate and nbminer treated eth as the secondary algo instead of primary. So I input for a 2 gpu rig under eaglesong algo instead of eth algo, then I don't see the argument gets parsed to the rig.

Thank you Patrike, dual mining with NBMiner now works in profit switcher, one bug though:

The per-algo commandline argument in profit profile does not get parsed to NBMiner during normal mining, it does get parsed during benchmarking however.

Best Regards,

1. you would need to add a pool, follow the documentation

https://support.awesomeminer.com/support/solutions/articles/35000086010-mining-pools


2. Easiest is to use the Zergpool's Miner Command Line Generator (select radio button that says Party) located on their home page and fill in the relevant information, just copy paste in the generated command and paste them into the Pool Properties

Server URL: {generated}
Worker Name: {generated}
Worker password: {generated}

you sure you're not Claymore or Wolf?

Official EWBF_ thread is this way

---->

https://bitcointalk.org/index.php?topic=4466962.0

Thanks Patrike, have been able to get NBMiner to bench ckb+ethash, with a few issues though.

1.
The dual hashrate been recorded by default has been inversed, say, I have 85 MH/s for Eth and 1.2GH/s for Eaglesong, the benchmark will read and record

I'm not sure if that's due to NBminer, when dual mining, it uses eaglesong as primary and ethash as secondary and made the metrics mixed up but I do suspect it to be the culprit.

2.
The dual hashrate and revenue from Eaglesong does not get taken into consideration in profit switching calculation, somehow even when populated with non "0" benchmarks into keccak, lbry, ckb 's dual mining hashrate in profit profiles, the Profit Switching tab for the miner still only lists 2 2ndary algos in my case:


and thus, it won't start dual mining ckb+eth as it isn't in the profitability list.
I have even just enabled only the eth and ckb pool in the profit profile to confirm the behaviour.

Hi all,

I've not dual mined eth + whatever for a whole year at least. Has anyone gotten Gminer / NBMiner to dual mine with "Managed Profit Miner" in AM?

I somehow couldn't get it working automatically and wonder if I missed anything.

Thanks Patrike!

regarding the VPN now that I think about it again, maybe I can just invest in a pair of VPN routers, that'd probably make it less complicated.

Cheers!

Hi Patrike,

First of all happy holidays to you and all the Awesomers!

been awhile since I last posted, some suggestions/queries from the past few months of mining (which for me is relatively boring, broken down hardware, stagnant BTC price...hence the inactivity )

Anyhow, back to topic:

1. Is it possible to collect accumulated power usage data in the mining history of the managed (profit) miners? That would be helpful for me to gauge efficiency and negotiate hosting costs with off-site provider, and something like a hashrate graph but in power consumption would be a great bonus so I can visually present the case of no mining, no charge for unused electricity

2. Since ZergPool was able to implement several CryptoNight variants into Yiimp mining, I find myself using XMRig at times to be included in profit switching (Btw, using Nvidia, I know, they are crappy for CN but doesn't hurt to have them in profit switcher), is it possible for you to add support for the JSON config section in the Profit Profile's software section like Claymore/SRBMiner, I hope you know what I was referring to, Right Click Miner -> Edit Profit Profile -> Mining Software Priority List -> Select Software in question -> Configure... where you got the override config.txt content if say you select SRBMiner.

3. Can it be corrected that when NanoMiner (mining RandomX) via CPU to show actual CPU power usage rather than the idle GPU stats?

4. To your knowledge, do you know that if AM supports profit switching for the BlackMiner Mini(+) series? like if I get a few of them and if I can use the custom defined pool groups on them as I do with Managed Profit Miner GPU rigs? (I know the website states AM do support the F1 but was unsure about the other models).

5. If 4 is doable, another non-essential question would be if there are any method to add them (obviously in reasonable numbers) to AM if I was to host them behind a NAT, currently using NeoRouter for the VPN for remote miners, not sure what's the most efficient and uncomplicated way to add these standalone FPGA/ASIC in similar fashion.

Best Regards and Merry Xmas to you!

Try Options -> Statistic Providers -> Override coin algorithms: (Configure) -> Add

Coin Short Name: ZEL
Map to algorithm: Equihash 125,4

if you want quick fix straight away.

***
it really is probably duplicate entries from before and after fork that got things mixed up, if you look at Options -> Coins

Both in Visible and Hidden column, it's likely you have more than 1 ZEL added all up from those 2 columns if you have "Keep coins even when no longer listed by provider" checked in the Options -> Statistic Providers page

Personally I have 3 since ZEL forked to 144 then 125 from original Equihash whichever parameter that was I don't remember.

Hi Patrike,

Also, Feature Request related to Coin Dynamic Update:

As a reasonable number of coins utilise multi-algo PoW, is there any robust way in your opinion, to duplicate/clone those dynamic properties within AM?

I was thinking about some sort of template feature in Coin Properties -> Dynamic Update -> Provider (consider adding default lists, either from history via other custom coin properties, or standard common ones, especially from more common exchanges fetching prices)

(e.g, if I'm to fetch prices from an exchange say, crex24, I can select it from Provider List and AM will populate the URL (except the Ticker Pair), HTTP method, JSON property expression to (subjective, but as far as concerned, bidding price seems more popular to use than asking).

**

And for other properties such as Difficulty, Network Hash (running a local node), it'll be nice to have a history to pull as they all ended up having the same URL, POST body, and slightly different JSON property expression.


Not an urgently needed feature but would be handy (currently in process of adding GlobalToken and it's kinda pita with 60 odd supported algos less the ASIC ones, granted it's likely not profitable to mine it, rather it's able to be merge mined, but would like to keep it as option as well as other coins that uses mult-algos)

Best Regards,

Hi Patrike,

I have noticed that lately AM does not use the correct pool when "View Details" shows all profits < 0 for a Managed Profit Miner for my rigs, it has occurred on 6.7.x and since upgrade to 6.8.1, remains the issue.

(i.e, instead of mining at pool x at next least loss level of -$0.01 per day, it go with something at pool y at a loss of -$0.30 per day)

Best Regards,

Edit:
Actually, I think it is still doing the switching correctly but under certain circumstances, it might play up from time to time. I am not sure, but hypothesising on some conflict between rules and Profit Switching Options. Or it might be that the profit switching threshold didn't apply properly when profits are negative.

I noticed I have
Minimum Time to stay on a pool (minutes) option set

+

a Rule that restarts the mining process if Rejected % is above certain threshold in a given period of time.

and according to the above condition

the Minimum time to stay on a pool seems to override Switching Interval on the same Options page (on top), that is, if Min time on pool > Switching interval, then Switching interval = Min time on pool.

then this in conjunction with the reject/restart rule, that say triggered b4 the Min Time on pool is reached, seems to reset the Min Time on Pool and consequently, the Profit Switching interval for a said Managed Profit Miner. so if the reject/restart rule keep triggering due to say, the pool or miner for some reasons throws a lot of rejects, then the profit switching interval can stay indefinitely not triggered (or for hours) until manual intervention or the situation corrects itself whichever comes first (usually the former)

I almost always have some (but not all) rigs failed to update Remote Agent each time there's an update till 6.x.x the issue are less. However, usually due to slow network, CPU too slow to respond (shitty celerons....) and installer timeout. when this happens, my solution is remote into the rig, exit Remote Agent process or reboot if it won't terminate for some reason. go to your %appdata% /Roaming/AwesomeMinerService/ folder and manually run the downloaded installer from there, it almost always downloaded the installer fine, but just msiexec process either occupied by another process (including windows update) or timed out and need manual intervention, not sure if this will help with the remote not updating on your rigs.

As for other issues, I can't comment as I haven't had much Windows 10 rigs where OC was causing issues, then again, I only have 2 rigs that runs windows 10 and they are not full mining rigs, though they do run the 1903 build

Hi Patrik & Fellow Awesome Miners,

A few ideas (some might not necessarily be practical / useful)

• Ability to Bulk Edit Pool Properties - Especially Worker name, Worker password, Wallet Address, Profit Factor field
• Ability to clone Pool Groups
• In conjuction to above, ability to have the Pool Groups the ability to override the fields in point #1 (which can make the first 1 points obsolete and completelly replaced by this one IMHO), This is particularly useful for pools like Zergpool where one want's to switch between coin addresses/payout coin type/coin targeting/solo or shared mode switching
• Ability to fetch Auto-Exchange Status via pool API and consequently include/exclude from a Pool Group (mining a coin when AE is disabled generally means no reward when payout coin needed to be exchanged)
• Ability to parse Online Services' Actual payout % to individual pools according to their algorithm (Yiimp pools somehow seems to have poor luck, or at least I find mining on Zergpool generally have efforts way > 100% across all algos, shared or solo mining
• Ability to detect and compare coin price delta (daily, 7day, 30day ... etc) and set it as a rule trigger, basically interested in the pairs (BTC/USD, XXX/BTC where XXX is an Alt pair of choice) due to the delaying nature of auto-exchange and correlation between major coins espeically BTC leading entire crypto up and down, sometimes this can automate a more optimal exchange option rather than manual (i.e, sometime it's better to mine and AE to BTC, other times it is better perhaps to be paid in say, LTC for example)

Best Regards,

Yes Patrike, the effective value is what I meant (couldn't word it better) that's all needed.


Thanks to you and your excellent Awesome Miner to make it possible!

Hi Patrike,

Is it by any chance the HTTP API for


can also include "Exponential Factor" (Default and Override where applicable) as part of the JSON response?

I've done some work on my Excel sheet to display TTF based on profile hashrate, but right now, using a lot of "if else if" for different algo/coins (since PowerBi don't support switch like statements), it'll be handy to just refer them as cell variables if it's included in the JSON.

Best Regards,

P.S. It's coming along nicely though.
https://imgur.com/a/oXL96B5

Supposedly this is normal behavior with GPUBoost, not sure what settings you are running under afterburner to see clocks all the same @trucobit? The fan curves, OC settings, algorithms and miner programs you're running.

If you Google, many ppl will tell you that these acute thermal throttling happen at roughly 50 something degrees Celsius or higher from their experience. Factors at every moment that causes fluctuation from highest probably goes like this:

Temperature > load | voltage

To mitigate, easiest is to first run efficient cooling (or turn the fan up high, which generally kills the fan quicker especially with the low quality fans gigabyte uses)

Quality PSU, Risers, power cables that used with the risers

Remove power saving features in Windows.

Choose "prefer maximum performance" in global profile under nvidia control panel's 3D setting section. Sometimes you might have to use nvidia profile inspector to find and change hidden settings.

Use EVGA's KBoost to keep the cards running at max boost clock indefinitely (need some hack for non evga cards) at your own risk, normally not recommended.


Running random hash algos will always cause fluctuations, and mining software complicate it further since they assign loads differently on top of the shuffling algo orders.

Hi Patrike,

in addition to several GPU miners are available for Argon2D + variants, is there any way to map multi algo coins such as XMY more effectively since they all share the same ticker (short name)?

eg. Myriad_Argon2d from Coincalculators is determined by AM as Argon2d-DYN, but the coin itself is actually using Argon2d4096

Just mapping XMY to the right algo results in AM mapping the yescrypt variant instead of the Argon2D.

Thanks in advance!

Best Regards,

and according to discord, removed algorithms are as follows for quick reference:

Try

https://explorer.jemcash.info/insight-api-jemcash/status

JSON Expression:
info.difficulty

Wow thanks heaps patrike! That was fast!!!

A little problem though, if you recall I had issues with updating block rewards from wallet JSON-RPC about 2 weeks ago, I'm having these issues still, and this time with network hashrate as well (block rewards was not resolved either). (ref: https://bitcointalk.org/index.php?topic=676942.msg50374809;topicseen#msg50374809)

In AM log, I'm getting these:


I can however, get updates from MPOS based pools with their public API provided if I found one, though since I'm running the wallet node already, I prefer to have it read from local node.
I'm wondering if that's due to some sort of type parsing causing error in AM for those values other than difficulty?

sample output from wallet node JSON response as below (getnetworkhashps):


again, the test button shows correct result from the response, but the properties kept failing the update.