Topic: NPlusMiner - |MultiRig remote management|AI|Autoupdate|Pool/Algo switching - page 35. (Read 37563 times)

thanks buddy

Also I moved from alexisPHI to SPmodPHI and I got some gain --> 24.7 MH/s on 1070Ti

https://github.com/MrPlusGH/NPlusMiner/issues/5

Unzip and move to miners folder.

it will download directly from Justaminer github.

link?

here I still see the PalginHSR https://github.com/MrPlusGH/NPlusMiner-1.3/tree/master/Miners

Nemo already replaced Palgin with Justaminer HP version due to full api support + no fee with equal or better performance.

I opened a issue in your github with the miner file, or you can just pulled from Nemos repository.

yes sorry.

I tested with one GTX 1070 Ti. Just for testing I used only one GPU.

Ccminer KlausT gives me 1174/1185 KH/s
HSR Miner Justaminer HP version gives me 1230/1243 KH/s

Numbers and hardware details might help a decision

May you replace the PalginHSR with the Justaminer HP version? The HP version gives me way more hashrate compared to the Palgin and to the "normal" jsutaminer one

thanks!

I used my skills and fixed it

What does Trust level actually do?

Removed PalginHSR or proposed work around other than removing neo from that bat?

Do you have any experience running ccminer or other mining software by itself? If not, then I strongly suggest you not use this miner manager until all the kinks and bugs are worked out because it is not really geared towards newbies and may not ever be suitable for such, given that it is a collection of PowerShell scripts and batch files.

NiceHash is an excellent alternative, and no shame in using it - I do myself sometimes.

I get an error when Is tart ccminer alexis.

I have 12 cards. When I select  -SelGPUDSTM '0 1 2 3 4 5 6 7 8 9 10 11' -SelGPUCC '0,1,2,3,4,5,6,7,8,9,10,11
I get an error from ccmimer alexis 1.0 as CUDA 11 gpu not existing.


Is it a known problem?

Suggestions:

1. StartEarningsTracker.bat should get its parameters from the Start[pool].bat file, and not have to be separately specified. This makes it easier to switch between pools.

2. Use a fixed name for the main NPlusMiner PS1 script rather than one that changes with each version so that the same Start[pool.bat files can be used from version to version without modification. If parameter and/or miner selection changes in a version then simply warn us about it in the readme or let us suffer the consequences.

3. v1.3 failed sometime last night because of a missing dll, no doubt as a result of me simply copying the bin directory over from one version to the next, and the NPlusMiner script basically sat there doing nothing for several hours once again (this never seems to happen while I am awake, I notice...). There really needs to be some monitoring of the miners and a way to mark miners/algos/ports as inoperative and skip over them rather than get stuck.

Otherwise, I still like the progress being made and that is why I have spent many hours installing and testing each version as it is released.

Thanks for testing and reporting.
Was this using ahashpoolplus?

From ahashpool

Announcement: [2018-02-23 07:22 UTC] Cryptopia is having serious issues not seeing deposits for many coins. This has been on going for 24 hours + already. This seriously affects pool operations. We have no choice but to disable mining for these coins, setting API estimates and actuals values to zero. Please make sure you are using profit switching script, and not only mining 1 algo because if you mine an algo that is disabled, you will receive nothing.

Properly handeld by ahashpoolplus
No worries

Fixed in 1.3.1
https://github.com/MrPlusGH/NPlusMiner/releases

GitHub switched to TSL v1.2 Only on Feb 22 which breaks miners downloads
https://githubengineering.com/crypto-removal-notice/

which pool are you using now ? zergpool ?

In an attempt to see if I could match earnings estimates, I decided to hop onto ahashpool for 24hrs. I had spent 72hrs on AHP before, and the results were less than satisfactory. That test is documented in my older posts if anyone's interested.

Equipment:

- 3 1080Tis @ 200w
- 1 1070Ti @ 150w

I downloaded the release of NPlusMiner 1.3 and I was on my way. I selected xevan, hsr, phi, tribus, x17, Nist5, Lyra2RE2, blake2s, and neoscrypt as my algos. I also selected skein, but again, it never stopped benchmarking so I just ditched it because I'm impatient. The benchmarking process yielded me 0.000061901 BTC; this amount will be subtracted from my first 24hrs later.

- My switching gain was 4%
- I suffered about 30 minutes of downtime
- The test started (benchmarking finished) on Feb 21 9:35pm. I stopped it at 10:35pm of the following day to account for the downtime.

I waited another 30 mins for any stray earnings to register. My total earned was 0.00118892 BTC. After subtracting the earnings from the benchmarking section, I'm left with 0.001127019 BTC. Let's break this down to what each card amounted to approximately:

- 1080Ti: 0.3 mBTC*3 cards = 0.9 mBTC
- 1070Ti: 0.22 mBTC*1 card = 0.22 mBTC

I haven't dabbled with any other Yiimp-based pools except for Zergpool briefly; most of my mining is from NH. In the same time frame, I've earned about 0.34-0.37 mBTC for each 1080Ti and about 0.23-0.26 mBTC for each 1070Ti. My actual earnings are usually within very close proximity to estimates. The greatest outlier I've seen was less than 5%. This leads me to my conclusion.

The good: After reaching 100% trust level in NPlus, the "average BTC/D" reading is extremely accurate. I still enjoy the UI, there's something classic about it.

The bugs: Skein benchmark never stops for me, this has happened to me twice in isolated situations.

The switching behaviour is also very strange. The first time I boot after finishing benchmarks, my sleep time is 30 secs. X17 is the most profitable at this time. As X17 warms up during this minute, the program sees that X17 is the most profitable algo, yet, it'll restart X17 and I gotta warm up again. Talking about warming up, without changing the default intensity, I warm up starting from around 53mh all the way to 70mh. Once in a while, I'll warm up from 64mh to 70mh. Not sure what's causing the latter, but I wish I could reproduce it. Takes about 10 mins to warm this damn thing up if I have to start from 53mh.

After my first round with 30 sec sleep time, it turns to 180 secs. I didn't touch the "-interval" option at all. It's not even in my batch file. HSR is now the most profitable algo. I think to myself "alright, the program probably just thinks it's temporary, so it hasn't switched algos". I wait for 20 minutes. The switcher hasn't refreshed once ever since sleep time turned to 180 secs. The computer isn't frozen and neither is the miner. I think to myself again "ah fuck it, X17 will probably be on top soon enough anyways, I'll just leave it and let's see how long it takes". Almost 2 hours pass and I can safely conclude it's probably a glitch at this point. I manually restart. After the reboot, we're back to 180 sec sleep time; the miner refreshes and switches properly now.

The ugly: Outside of the BTC/D from reaching 100% trust, the earnings estimates are still wildly inaccurate from my experience. I'm not sure why this is, but fuck AHP is all I'm saying.

Thanks for reading.

Same error here. https://imgur.com/a/RBW6E

Still an issue with Nemos 2.5, does the current NPlus have this issue as well? Any workaround to be able to run Neo?