 Show Posts
|
|
Pages: [1] 2 »
|
I went ahead last night and sorted through the code with a few references for your example. This configuration included all pools with all coins, uses the official sgminer 5.0 from nice/westhash, and successfully pulls all information as well as launches appropriate versions of each miner. Configuration for Radeon r9 280x X2. Make sure if you use this to change the directory structure to point to your associated miner's for each coin- Besides that just punch in your BTC address and your account name/api key where necessary and you're up and running. {
"general": {
"power": 0.15,
"exchange": 500,
"mintime": 4,
"maxtime": 180,
"switchtime": 3,
"deadtime": 10
},
"algorithms": [
{ "name": "x11", "hashrate": 6400, "power": 49 },
{ "name": "x13", "hashrate": 4400, "power": 49 },
{ "name": "x15", "hashrate": 4000, "power": 52 },
{ "name": "nist5", "hashrate": 24600, "power": 54 },
{ "name": "scrypt", "hashrate": 1200, "power": 60 },
{ "name": "scryptn", "hashrate": 480, "power": 60 },
{ "name": "keccak", "hashrate": 630, "power": 50 },
{ "name": "sha256", "hashrate": 0, "power": 50 }
],
"westhash": {
"account": "1Pe5huNgu8TfNgjiXVKuSja6VNw5wTB7KM",
"worker": "1",
"param1": "stratum+tcp://stratum.westhash.com",
"weight": 0.90,
"algos": [
{ "algo": "x11", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x11", "command": "sgminer.exe", "arguments": "--kernel darkcoin-mod -o _PARAM1_:3336 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x13", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x13", "command": "sgminer.exe", "arguments": "--kernel marucoin-mod -o _PARAM1_:3337 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scrypt", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt", "command": "sgminer.exe", "arguments": "--kernel ckolivas -o _PARAM1_:3333 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scryptn", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt_n", "command": "sgminer.exe", "arguments": "--kernel psw -o _PARAM1_:3335 -u _ACCOUNT_._WORKER_ -p x --nfactor 11 -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "keccak", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\keccak", "command": "sgminer.exe", "arguments": "--kernel keccak -o _PARAM1_:3338 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x15", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x15", "command": "sgminer.exe", "arguments": "--kernel x15 -o _PARAM1_:3339 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "nist5", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\nist5", "command": "sgminer.exe", "arguments": "--kernel nist5 -o _PARAM1_:3340 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 18 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "sha256", "folder": "", "command": "cmd.exe", "arguments": "--kernel KERNELNAME -o _PARAM1_:3334 -u _ACCOUNT_._WORKER_ -p x" }
]
},
"nicehash": {
"account": "1Pe5huNgu8TfNgjiXVKuSja6VNw5wTB7KM",
"worker": "1",
"param1": "stratum+tcp://stratum.nicehash.com",
"algos": [
{ "algo": "x11", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x11", "command": "sgminer.exe", "arguments": "--kernel darkcoin-mod -o _PARAM1_:3336 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x13", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x13", "command": "sgminer.exe", "arguments": "--kernel marucoin-mod -o _PARAM1_:3337 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scrypt", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt", "command": "sgminer.exe", "arguments": "--kernel ckolivas -o _PARAM1_:3333 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scryptn", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt_n", "command": "sgminer.exe", "arguments": "--kernel psw -o _PARAM1_:3335 -u _ACCOUNT_._WORKER_ -p x --nfactor 11 -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "keccak", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\keccak", "command": "sgminer.exe", "arguments": "--kernel keccak -o _PARAM1_:3338 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x15", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x15", "command": "sgminer.exe", "arguments": "--kernel x15 -o _PARAM1_:3339 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "nist5", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\nist5", "command": "sgminer.exe", "arguments": "--kernel nist5 -o _PARAM1_:3340 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 18 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "sha256", "folder": "", "command": "cmd.exe", "arguments": "--kernel KERNELNAME -o _PARAM1_:3334 -u _ACCOUNT_._WORKER_ -p x" }
]
},
"trademybit": {
"apikey": "APIKEYGOESHERE",
"account": "USERNAME",
"worker": "1",
"param1": "stratum+tcp://west01.us.trademybit.com",
"algos": [
{ "algo": "x11", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x11", "command": "sgminer.exe", "arguments": "--kernel darkcoin-mod -o _PARAM1_:4440 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x13", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x13", "command": "sgminer.exe", "arguments": "--kernel marucoin-mod -o _PARAM1_:5550 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x15", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x15", "command": "sgminer.exe", "arguments": "--kernel x15 -o _PARAM1_:6660 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "nist5", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\nist5", "command": "sgminer.exe", "arguments": "--kernel nist5 -o _PARAM1_:7770 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 18 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scrypt", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt", "command": "sgminer.exe", "arguments": "--kernel ckolivas -o _PARAM1_:3330 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scryptn", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt_n", "command": "sgminer.exe", "arguments": "--kernel psw -o _PARAM1_:2220 -u _ACCOUNT_._WORKER_ -p x --nfactor 11 -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" }
]
},
"yaamp": {
"account": "1Pe5huNgu8TfNgjiXVKuSja6VNw5wTB7KM",
"worker": "1",
"param1": "stratum+tcp://yaamp.com",
"algos": [
{ "algo": "x11", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x11", "command": "sgminer.exe", "arguments": "--kernel darkcoin-mod -o _PARAM1_:3533 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x13", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x13", "command": "sgminer.exe", "arguments": "--kernel marucoin-mod -o _PARAM1_:3633 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "x15", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\x15", "command": "sgminer.exe", "arguments": "--kernel x15 -o _PARAM1_:3733 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "nist5", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\nist5", "command": "sgminer.exe", "arguments": "--kernel nist5 -o _PARAM1_:3833 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 18 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" },
{ "algo": "scrypt", "folder": "C:\\Users\\MFCEOSean\\Desktop\\MinerControl_Complete\\miners\\sph_sgminer\\scrypt", "command": "sgminer.exe", "arguments": "--kernel ckolivas -o _PARAM1_:3433 -u _ACCOUNT_._WORKER_ -p x -w 256 --thread-concurrency 8192 --shaders 2048 -I 13 -g 2 --lookup-gap 2 --gpu-memclock 1500 --gpu-engine 1033 --expiry 1 --scan-time 1 --queue 0 -d 0,1" }
]
}
}
|
|
|
|
|
Does anyone have the necessary .conf settings for a Radeon 280x? I've been through pages upon pages of the old NiceHash Control Tool as well as throughout this posting but don't seem to be able to find a .conf setup that works. Everything pulls prices, but when attempting to start SGMiner nothing happens - even with the correct directory structures set using \\ to separate heirarchy.
If someone would be willing to post which miner they are using for AMD, and their appropriate .conf files that would be absolutely amazing!
|
|
|
|
Did they pack up and run?
Just started using the site today, so hopefully this isn't the case. Although I have to admit this error specifically is somewhat discerning as most sites have some sort of notification for maintenance or DDOS or the like. Would be a shame, as the site has a nice layout and is quite easy to use. If it comes up I'll probably pull my balance manually to my wallet just in case it is maintenance related I'll still be able to access my funds during the downtime. Update: Posted on twitter asking about the downtime, still awaiting a response. Will check back if/when I receive a response. Update 2: Can't find an official update anywhere. The iRC channel #bytecoin-dev on Freenode has 5 people in it, none of which seem to be officials from HitBTC, and none of which will respond. The twitter post still has no response. These forums have no response. Starting to get worried. I guess it's a good thing I always do micro-transactions for the first few trades on new exchanges, I could have just saved myself a huge loss. |
|
|
|
502 Bad Gateway
Same here. |
|
|
|
|
I seem to have discovered the issue, and it seems it could be a possible bug.
What seems to have happened: I changed my minimum payout threshold to 0.015 BTC, after the balance had already reached a point higher than that. As such, it didn't seem to "trigger' the payout as the threshold had been bumped lower than the current BTC balance. Once I changed the threshold to something higher than the BTC balance on eligius, once it reached that amount it successfully "triggered" the payout into the queue system.
So, it would appear changing the minumun threshold for payout "jumped" over the trigger, and resetting to an amount yet to be attained it successfully triggered when hitting that point.
|
|
|
|
|
I've been over the confirmed BTC payout threshold for over a day and a half now, the "timer" has said 0 seconds to enter payout queue for several days now, and my balance still shows a full wallet on eligigius - with no mention of my address whatsoever in the payout queue of my BTC wallet address. Any idea's what's going on? I only started mining with eligius 5 days ago or so now, so i'd wondering if this extended delay normal? Do payouts generally run several days behind?
I suppose it's not that big of a deal as my balance continues to grow, so I'm getting credit for my hashrate, it just worries me because there is no manual withdraw method and as I have been over the payout queue threshold for some time now I'm beginning to wonder if/when it will properly trigger the payout.
Thanks in advance, and hopefully someone familiar with eligius can shed some light on this.
|
|
|
|
best place to start I guess would be their api part. http://www.mobileminerapp.com/#apiI've got it combined with mutilminer and it seems that all I can do is detect the antminers on the network but can't do much more than the basic hash rate, pool, whether active or not and a temperature as multiminer is accesing them through the "standard" no changes allowed cgminer API ah no to get remoting you have to turn on perks and give the writer of mutiminer 1% of your hashrate (in multiminer anyway) That's correct, some features require donation to unlock. However, even without the full features the app implementation of real time monitoring and hash rates, as well as temperatures for your miners, is incredibly useful. Also, the push notifications that pop up when a miner goes down or offline is extremely useful for quick notification of miner statuses. I guess what I'm saying is even if you choose not to unlock the extra features, which is completely at the miner operators whim, the implementation of passive features to an already existing API would offer a lot of people an extremely convenient solution for remote monitoring, as well as bring more attention to M's awesome program! Also, if you don't mind my asking, how did you get M's and MM to play nicely together? Did you use the CGMiner API plugin they offer? And if so, how did you use/apply it as that was one of the places I got stuck myself when trying to combine the two in my tests. |
|
|
|
|
Any chance of seeing MobileMiner integration? Currently I have to use MultiMiner to be able to remotely monitor the status of my Antminers, and with this being specifically tailored for the Antminer - and Multiminers remote control/status checking abilities - It seems like the next logical step!
|
|
|
|
Do any of you here know why the queue on the config is set so high? Is there a big gain from setting it to a lower number or why did they program 4096 as the queue. The discarded amounts are so high...
Any idea? Not sure, but what I can say is outside adjusting the freq and timings for overclocking, there's really nothing else you need to adjust or change. That being said, if your discarded shares are quite high it might be worth resetting your Antminer via the reset switch inside, and then checking your network for stability and throughput. |
|
|
|
Do you guys feel it is good to instantly remove the heatsinks and apply new thermal paste to the chips?
I am unsure of the quality paste used from manufacturer but I highly doubt it is premium due to production costs.
I have been running both of my Ant's OC'd to 500 GH/s and 490 GH/s and both temperatures are well within normal ranges and all chips are stable and hashing with no X's. One of them has been running a few hours as if you look up a post or two you'll see where we came up with the newer smaller incremental frequency steps, and that is the one running at 490 GH/s up from the 237.5 clock which was in the 470-480 GH/s range, while the other has been running for 72 hours at 500 GH/s. Highest temperature reached by any miner is 44C, while averaging 40-43 C in use, so I would say replacing the thermal compound is unnecessary. That being said, if you do decide to go ahead and upgrade/replace the thermal compound, do not use any compound with Silver in it as it is conductive, and make absolutely sure that whatever brand you decide to go with DOES NOT CONDUCT ELECTRICITY - YOU WILL FRY YOUR ANTMINER!!!!! I see  Yes my current have same temperature, from some pictures I have seen of heatsinks removed I noticed very bad application of the paste. I don't expect too much from the assembly line. Silly question but I must ask, outside of trial and error how are you coming up with the newer reg codes you posted above? Should I completely ignore the first page and use the recent posting? I separated out the operating speed's into incremental steps and JakeTri calculated the appropriate Freq values and Timings. |
|
|
|
Do you guys feel it is good to instantly remove the heatsinks and apply new thermal paste to the chips?
I am unsure of the quality paste used from manufacturer but I highly doubt it is premium due to production costs.
I have been running both of my Ant's OC'd to 500 GH/s and 490 GH/s and both temperatures are well within normal ranges and all chips are stable and hashing with no X's. One of them has been running a few hours as if you look up a post or two you'll see where we came up with the newer smaller incremental frequency steps, and that is the one running at 490 GH/s up from the 237.5 clock which was in the 470-480 GH/s range, while the other has been running for 72 hours at 500 GH/s. Highest temperature reached by any miner is 44C, while averaging 40-43 C in use, so I would say replacing the thermal compound is unnecessary. That being said, if you do decide to go ahead and upgrade/replace the thermal compound, do not use any compound with Silver in it as it is conductive, and make absolutely sure that whatever brand you decide to go with DOES NOT CONDUCT ELECTRICITY - YOU WILL FRY YOUR ANTMINER!!!!! |
|
|
|
I was able to seperate the above frequencies into smaller incremental steps, but I have no idea how to calculate the "reg. value" or the "ideal delay" for them. Anyone with a little more know-how than myself willing to help out? I know a few other people in this thread were looking for something like this as well, and any help at all would be appreciated. Thanks!
Adjusting the S1 formula based on S3 ASIC spec I was able to get following register values (and timeout). Use the settings below at your own risk! | Clock_Freq | Register value | Timeout | | (chip_freq) | (freq_value) | (timeout) | | 100 | 0783 | 40 | | 103.125 | 1007 | 39 | | 106.25 | 0803 | 38 | | 109.375 | 1107 | 37 | | 112.5 | 0883 | 36 | | 115.625 | 1207 | 35 | | 118.75 | 0903 | 34 | | 121.875 | 1307 | 33 | | 125 | 0983 | 32 | | 128.125 | 1407 | 31 | | 131.25 | 0A03 | 30 | | 134.375 | 1507 | 30 | | 137.5 | 0A83 | 29 | | 140.625 | 1607 | 28 | | 143.75 | 0B03 | 28 | | 146.875 | 1707 | 27 | | 150 | 0B83 | 27 | | 153.125 | 1807 | 26 | | 156.25 | 0C03 | 26 | | 159.375 | 1907 | 25 | | 162.5 | 0C83 | 25 | | 165.625 | 1A07 | 24 | | 168.75 | 0D03 | 24 | | 171.875 | 1B07 | 23 | | 175 | 0D83 | 23 | | 178.125 | 1C07 | 22 | | 181.25 | 0E03 | 22 | | 184.375 | 1D07 | 22 | | 187.5 | 0E83 | 21 | | 190.625 | 1E07 | 21 | | 193.75 | 0F03 | 21 | | 196.875 | 1F07 | 20 | | 200 | 0782 | 20 | | 206.25 | 1006 | 19 | | 212.5 | 0802 | 19 | | 218.75 | 1106 | 18 | | 225 | 0882 | 18 | | 231.25 | 1206 | 17 | | 237.5 | 0902 | 17 | | 243.75 | 1306 | 16 | | 250 | 0982 | 16 | | 256.25 | 1406 | 16 | | 262.5 | 0A02 | 15 | | 268.75 | 1506 | 15 | | 275 | 0A82 | 15 | | 281.25 | 1606 | 14 | | 287.5 | 0B02 | 14 | | 293.75 | 1706 | 14 | | 300 | 0B82 | 13 | | 306.25 | 1806 | 13 | | 312.5 | 0C02 | 13 | | 318.75 | 1906 | 13 | | 325 | 0C82 | 12 | | 331.25 | 1A06 | 12 | | 337.5 | 0D02 | 12 | | 343.75 | 1B06 | 12 | | 350 | 0D82 | 11 | | 356.25 | 1C06 | 11 | | 362.5 | 0E02 | 11 | | 368.75 | 1D06 | 11 | | 375 | 0E82 | 11 | | 381.25 | 1E06 | 10 | | 387.5 | 0F02 | 10 | | 393.75 | 1F06 | 10 | | 400 | 0F82 | 10 |
Awesome! I'm testing the following now: option 'freq_value' '1306' option 'chip_freq' '243.75' option 'timeout' '16' One of my Ant's works fine at 250, however the other does not and had to be bumped down to the 237.5 to refrain from attaining X's. This seems to be stable so far, but only time will tell as it took about an hour/2 for it to show X's the first time around. Currently averaging 485-490 GH/s. |
|
|
|
|
Clock Freq.(M) Hash rate(G) Reg.value Ideal delay(ms) Recommenddelay(ms)
100 6.30 0783 42.6 38
-106.25
-112.5
-118.75
125 7.88 0983 34.0 31
-131.25
-137.5
-143.75
150 9.45 0b83 28.4 26
-156.25
-162.5
-168.75
175 11.03 0d83 24.3 22
-181.25
-187.5
-193.75
200 12.60 0782 21.3 19
-206.25
-212.5
-218.75
225 14.18 0882 18.9 17
-231.25
-237.5
-243.75
250 15.75 0982 17.0 15
-256.25
-262.5
-268.75
275 17.33 0a82 15.5 14
-281.25
-287.5
-293.75
300 18.90 0b82 14.2 13
-306.25
-312.5
-318.75
325 20.48 0c82 13.1 12
-331.25
-337.5
-343.75
350 22.05 0d82 12.2 11
-356.25
-362.5
-368.75
375 23.63 0e82 11.3 10
-381.25
-387.5
-393.75
400 25.20 08f2 10.6 10
I was able to seperate the above frequencies into smaller incremental steps, but I have no idea how to calculate the "reg. value" or the "ideal delay" for them. Anyone with a little more know-how than myself willing to help out? I know a few other people in this thread were looking for something like this as well, and any help at all would be appreciated. Thanks!
|
|
|
|
|
Work Input timing
Clock Freq.(M) Hash rate(G) Reg.value Ideal delay(ms) Recommenddelay(ms)
100 6.30 0783 42.6 38
125 7.88 0983 34.0 31
150 9.45 0b83 28.4 26
175 11.03 0d83 24.3 22
200 12.60 0782 21.3 19
225 14.18 0882 18.9 17
250 15.75 0982 17.0 15
275 17.33 0a82 15.5 14
300 18.90 0b82 14.2 13
325 20.48 0c82 13.1 12
350 22.05 0d82 12.2 11
375 23.63 0e82 11.3 10
400 25.20 08f2 10.6 10
Has anyone successfully broken the above down into smaller incremental steps? Preferably 1/4 of their current spacing? Or even 1/6th? Thanks!
|
|
|
|
PD: Is posible to enable that we can change the pool through the mobileminer app in the future?
This is supported by the MobileMiner API but Michele would need to add support in Minera. I'm happy to help with it. It may be worth adding your request here: https://github.com/michelem09/minera/issuesAs that is where the author has directed previous MobileMiner requests. Curious if there has been any luck getting a fully functional binary under MinerA for the RockMiner RocketBox's? Or if there are currently no problems if you have any pointers in getting it working as I have so far been unable to replicate even 60% of the hashrate of the RockMiner official controller in BFGMiner and have had no success whatsoever under the current CGMiner =/ Hoping anyone can help! |
|
|
|
Hi is there a way to login to minera GUI as a read only user, so that I can share the GUI without the possibility of the viewer to mess things up. I know there was a post before about this some 30+ pages back. would be great if there was a possibility of declaring parts of the GUI to be shown. have a nice day to all of you  No, but that's a feature I'd like to add in next releases. --------- If you wanna know how much people are using Minera, here are the first stats I got: active systems: 152 active devices: 992 last total hashrate: 91.04GH/s miners: cgdmaxlzeus: 17 cpuminer: 112 bfgminer: 14 unknown: 6 cgminer: 3 Soon you will be able to see them at http://getminera.comI'd love to crank up the numbers and get my RK-BOX farm successfully running under MinerA, but so far I seem to be unable to get CGMiner to function or BFGMiner to the correct hashrate, only pulling about 50% of the 120+ GH/s per blade =/ |
|
|
|
So here's a weird one relating to a non-supported feature. Running the r-boxes with the rockminer-cgminer under minera works great and everything, but it does something I've never seen before.
Maybe I just have an old binary of their CGminer under Minepeon - but under minera it ignores my set frequency of 290 and instead the cgminer terminal screen says "Autofreq:350mhz"
The result is 10-15 extra GHS (cool!) but 25-35 more watts drawn from the wall (oh, less cool!). I'm not sure the extra GH are worth the extra watts.
Anyone have thoughts?
i wonder if you have received a response about this issue? im debating purchasing a few and want to run them on minera. Does anyone have a functional binary of either BFGMiner or CGMiner for the RockMiner RK-Box? All the one's I've tried seem to only get the blade's hashing at R-BOX speed's (1/4 their potential), and BFGMiner only get's up to about 50% but has a 90% error/reject rate under the included binary. Hoping someone has either a command line code I'm missing or a functional binary for this miner. Thanks in advance! |
|
|
|
@silverthornne thank you very much! I like so much feedbacks like yours, each of your requests is possible and I'm just working on them. but there is one I can't understand when you speak about the autorestart method. Let me explain what it does and then tell me if you need more.
Autorestart if enabled looks at the share time of your devices. If X devices arent' hashing (sending shares) for Y seconds Minera try to restart completely the miner (not reboot, restart the miner process). So, if you want to restart it as soon as 3 or more devices goes down, just put 3 as device number and 75 as seconds to wait before declaring them dead. If this is not your case, please explain me what you like to have and I'll do my best.
@la7eralus that's definitely a API/RPC problem, it seems the API doens't send the same data the original cgminer sends. I need to know that to fix it (if it's fixable). Please do this:
* start cgminer for rockminer
* don't bother the dashboard
* look at the terminal (use the web one or ssh into it)
* run this: echo '{"command":"summary+devs+pools"}' | nc 127.0.0.1 4028
* give me the output please
Thanks
So I'm a noob and apparently had my hubs mixed up. The modified cgminer binary does indeed not work, however the included BFGMiner binary does detect all the blades and display their information accordingly. However, bfgminer is incapable of gettings each blade of the RKBOX up to its full potential, capping out in the 200 GH/s range out of 480+. Custom string used for BFGMiner: -S rockminer:all --set rockminer:clock=320 Im assuming BFGMiner is not paying attention to the frequency setting of 320 I am setting and that this is the culprit. However, bfgminer does pull full API access and MinerA displays everything perfectly, it just isn't capable of currently getting up to speed. Maybe a special BFGMiner binary specifically for the RKBOX? Or possible the CGMiner binary that comes with the default RockWeb Raspberry Pi controller would serve as a solid base, as I have already tried directly swapping the binaries with this one and it seemed to not function properly. |
|
|
|
|
