Pages:
Author

Topic: MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform) - page 66. (Read 827336 times)

legendary
Activity: 1288
Merit: 1004
When do you find time?!?!
That looks great.  Will it make it to the android app as well?
Great job as always I look forward to it.

newbie
Activity: 27
Merit: 0
I'm going to look for an API tutorial. Is 192.168.0.0/24 always the address to use Huh My miners are 192.168.1.101/114

Nope - if your miners and network are 192.168.1.101 then you want to use 192.168.1.0/24 in the API allow command. That include the W: as well. That will allow any PCs on your local network to control the miner via RPC API.
Thanks, that's what I did but it doesn't seem to be working.
Code:
     
config cgminer 'default'
        option chip_frequency '282'
        option miner_count '24'
        option api_allow 'W:127.0.0.1,W:192.168.1.0/24'
        option more_options '--quiet'
I had the same issue, you also have to edit the S99cgminer file.
http://pastebin.com/YEiyPjuH This is a handy post on installing nano and which file (and line) you need to edit
https://bitcointalksearch.org/topic/antminer-s1-privileged-api-499837 This one shows exactly what to enter.

Hope it helps, I dunno if you are on Ant or Avalon the process should be the same
newbie
Activity: 27
Merit: 0
member
Activity: 99
Merit: 10
legendary
Activity: 1288
Merit: 1004
For some reason when the O/C for the DualMiners is in there my GPU shows and intensity of 8 instead of 15.  I tried it with and without the comma.
Right now my overclock in out of the loop but I will try it again.  I must be missing something somewhere.
Thanks for the help.

HI Nate
I have a question on how to keep my overclock from my DualMiners from causing havok with my gpu?
Code:
-I 15 -w 512  --thread-concurrency 15232, --set-device gridseed:clock=850
This is what I put in and it works great when for my DualMiners but it makes my GPU run at 18 kh/s.  I have tried both with and without the comma between them as well.
Thanks

There shouldn't be a comma in there and the --set-device argument for the gridseed shouldn't affect your GPU mining at all. You sure that is causing the problem? I use a nearly identical set or arguments. And in fact separate instances of BFGMiner are launched for ASICs and GPUs.
hero member
Activity: 840
Merit: 1002
HI Nate
I have a question on how to keep my overclock from my DualMiners from causing havok with my gpu?
Code:
-I 15 -w 512  --thread-concurrency 15232, --set-device gridseed:clock=850
This is what I put in and it works great when for my DualMiners but it makes my GPU run at 18 kh/s.  I have tried both with and without the comma between them as well.
Thanks

There shouldn't be a comma in there and the --set-device argument for the gridseed shouldn't affect your GPU mining at all. You sure that is causing the problem? I use a nearly identical set or arguments. And in fact separate instances of BFGMiner are launched for ASICs and GPUs.
hero member
Activity: 840
Merit: 1002
I'm a bit of a noob at this, with 7 Antminer U1s and 3 U2s.  I've got a mix where some of these units will run as high as 2.1 while others, only 1.9.  The Java version of Bitminter let's you individually set the clock for each device.  It's a nice feature for those of us starting up with USB miners.

Is there anyway to configure Multiminer to do something similar?  Perhaps group them into pools and set clock speeds by group?

You can but it's tedious. It will be made easier in future versions of MultiMiner. BFGMiner 4.0 will finally make it possible to do per-device settings across the board using --set-device.

As others have mentioned and as you've discovered you use the --set-device argument to overclock the devices. The --set-device argument is pretty cool because it lets you target specific paths and serial numbers, not just all devices for a driver.

So you can double-click the devices in MultiMiner and see the path and serial # on the right. Then you can do something like:

Code:
--set-device antminer@\\.COM15:clock=x0981

Under Settings > Advanced miner settings > SHA2.
sr. member
Activity: 453
Merit: 250
dfgfdgfdg
I'm going to look for an API tutorial. Is 192.168.0.0/24 always the address to use Huh My miners are 192.168.1.101/114

Nope - if your miners and network are 192.168.1.101 then you want to use 192.168.1.0/24 in the API allow command. That include the W: as well. That will allow any PCs on your local network to control the miner via RPC API.
Thanks, that's what I did but it doesn't seem to be working.
Code:
     
config cgminer 'default'
        option chip_frequency '282'
        option miner_count '24'
        option api_allow 'W:127.0.0.1,W:192.168.1.0/24'
        option more_options '--quiet'
hero member
Activity: 840
Merit: 1002
I'm going to look for an API tutorial. Is 192.168.0.0/24 always the address to use Huh My miners are 192.168.1.101/114

Nope - if your miners and network are 192.168.1.101 then you want to use 192.168.1.0/24 in the API allow command. That include the W: as well. That will allow any PCs on your local network to control the miner via RPC API.
hero member
Activity: 840
Merit: 1002
Would this for the Antminer work on my Avalon that has not been reporting current hashrate with this string.
Code:
--api-listen --api-allow W:127.0.0.1,192.168.0.0/24

Try adding --log 5 to the command line for the Avalon.
newbie
Activity: 27
Merit: 0
I've got it such that MultiMiner has API access (control) over all of my standalone units, but the Antminer S1 in particular likes to keep switching back to its default pool (BTC Guild) but with the terrible luck we've been having, I like to have the option to switch if I am so inclined. I have a couple Technobit's routed through an MR-3020 which is a similar, although not the exact same, type of setup. What is the best way to get multiminer's commands to stick so when I tell the S1 to mine elsewhere it will. I'd rather not use MM as a proxy to control the miner, but if thats what I have to do then I will...
legendary
Activity: 1288
Merit: 1004
HI Nate
I have a question on how to keep my overclock from my DualMiners from causing havok with my gpu?
Code:
-I 15 -w 512  --thread-concurrency 15232, --set-device gridseed:clock=850
This is what I put in and it works great when for my DualMiners but it makes my GPU run at 18 kh/s.  I have tried both with and without the comma between them as well.
Thanks
full member
Activity: 210
Merit: 100
Feature request:  I would like a link next to "Time until strategy check" to "Check now" that checks for new coin data on-demand and resets the strategy check timer accordingly.
full member
Activity: 210
Merit: 100
I apologize if this has been answered somewhere.  I've searched about 20 pages, google searched but came up empty.  

I'm a bit of a noob at this, with 7 Antminer U1s and 3 U2s.  I've got a mix where some of these units will run as high as 2.1 while others, only 1.9.  The Java version of Bitminter let's you individually set the clock for each device.  It's a nice feature for those of us starting up with USB miners.

Is there anyway to configure Multiminer to do something similar?  Perhaps group them into pools and set clock speeds by group?

I launched it without any overclock commands and somehow multiminer tried pushing all 10 to 2.0+ but a couple of the units were having quite a few hardware errors.  It looked as if Multiminer was trying to max everything out, maybe even self-tune to max stable clock rate but it never got over 16 ghash where it should have been 20+.

Can't find any documentation on this subject.  Can anyone help a noob out?

Thx

You can't do it - technically, however, you can work around it.

Firstly, Antminer U1s should be able to reach 2Gh/s with a low error rate as long as you're pointing a fan at them for cooling.  Antminer U2s should be able to do that at base.  Just make sure you're using the settings below.
Code:
-S antminer:all --set-device antminer:clock=x0981

If that does not work, you can do a workaround configuration that will allow you to accomplish what you're wanting.
  • Set up a Stratum server in MuM
  • Disconnect all of your U2s
  • Set up the U1s using a recent version of CGminer and Zadig.
  • Point CGminer at MuM's Stratum server and start it.
  • Reconnect your U2s
  • Fire up MuM.
  • Make certain that CGminer is loaded, and have MuM detect your remaining miners (the U2s).
You should now have all of your U1s on CGminer pointed at your MuM server and can configure them independently.   
newbie
Activity: 1
Merit: 0
I apologize if this has been answered somewhere.  I've searched about 20 pages, google searched but came up empty.  

I'm a bit of a noob at this, with 7 Antminer U1s and 3 U2s.  I've got a mix where some of these units will run as high as 2.1 while others, only 1.9.  The Java version of Bitminter let's you individually set the clock for each device.  It's a nice feature for those of us starting up with USB miners.

Is there anyway to configure Multiminer to do something similar?  Perhaps group them into pools and set clock speeds by group?

I launched it without any overclock commands and somehow multiminer tried pushing all 10 to 2.0+ but a couple of the units were having quite a few hardware errors.  It looked as if Multiminer was trying to max everything out, maybe even self-tune to max stable clock rate but it never got over 16 ghash where it should have been 20+.

Can't find any documentation on this subject.  Can anyone help a noob out?

Thx
sr. member
Activity: 453
Merit: 250
dfgfdgfdg
I just tried again and it didn't work. I right-clicked an AntMiner S1 in MuM 2.8.1 and chose the 2nd pool. Logged into the pool account and no hashing has appeared in the last 10 minutes. All hashing is still going to pool 1.
Make sure that your configuration for your AntMiner has a W: prefix for api-allow, e.g.:
Code:
option api_allow 'W:127.0.0.1,W:192.168.0.0/24'
Otherwise the API access is read-only.

I have my S1 set up this way:
Pool 1 is MultiMiner
Pool 2 is Multipool
Pool 3 is GHash
This way MuM still controls all of the mining, but if it crashes for some reason, it will failover to one of two other good pools.

How do you set up Pool 1 as MultiMiner Huh

I PuTTYed into an S1 and edited /etc/config/cgminer changing:
Code:
option api_allow 'W:127.0.0.1'
to
Code:
option api_allow 'W:127.0.0.1,W:192.168.0.0/24'
But it's still not working. Is this the right file that I need to edit Huh

I'm going to look for an API tutorial. Is 192.168.0.0/24 always the address to use Huh My miners are 192.168.1.101/114
legendary
Activity: 1288
Merit: 1004
Would this for the Antminer work on my Avalon that has not been reporting current hashrate with this string.
Code:
--api-listen --api-allow W:127.0.0.1,192.168.0.0/24

I just tried again and it didn't work. I right-clicked an AntMiner S1 in MuM 2.8.1 and chose the 2nd pool. Logged into the pool account and no hashing has appeared in the last 10 minutes. All hashing is still going to pool 1.

Make sure that your configuration for your AntMiner has a W: prefix for api-allow, e.g.:

Code:
option api_allow 'W:127.0.0.1,W:192.168.0.0/24'

Otherwise the API access is read-only.

If BitMain loaded bfgminer in its firmware would that give you full control Huh

Nope.
full member
Activity: 210
Merit: 100
I just tried again and it didn't work. I right-clicked an AntMiner S1 in MuM 2.8.1 and chose the 2nd pool. Logged into the pool account and no hashing has appeared in the last 10 minutes. All hashing is still going to pool 1.

Make sure that your configuration for your AntMiner has a W: prefix for api-allow, e.g.:

Code:
option api_allow 'W:127.0.0.1,W:192.168.0.0/24'

Otherwise the API access is read-only.

If BitMain loaded bfgminer in its firmware would that give you full control Huh

Nope.

I have my S1 set up this way:
Pool 1 is MultiMiner
Pool 2 is Multipool
Pool 3 is GHash

This way MuM still controls all of the mining, but if it crashes for some reason, it will failover to one of two other good pools.
hero member
Activity: 840
Merit: 1002
Pages:
Jump to: