Well I just got my other 2 Furys in the mail today. I never properly setup a config file for the first miner though (I relied on this guy's easy program to help setup the .bat files to run my 1st Fury
https://www.dropbox.com/sh/lwv8p2qj3pepzf0/AABBNg3AfT82KHag3AmF13fYa from a youtube link
https://www.youtube.com/watch?v=QIdLzd-KfOs&feature=youtu.be I found of him unboxing and setting up his miner). So that program worked for my 1st Fury (although I would sometimes see cgminer crash in the first 20 mins or so but it usually didn't crash if it got going past 20-30 mins). After adding two other com ports for the two other miners to the bat file though it runs and then crashes every time after about 5 or so accepts. I can't get it past the first few accepts without it crashing unlike with my first miner which would randomly crash in the first few mins. Perhaps I'm not using the best setup but I'm a total newbie when it comes to all this. One good thing about his program is that it included a link to the drivers that I needed for my computer to recognize the Fury. I was looking at the basic cgminer command in the op post but not sure where to put my com ports or what to do exactly. I also would like to just use my Fury to mine and not my gpu (which I used to mine with back in the day; guys program I used just used my Fury to mine and not gpu which was nice). So if I could get some help setting up the right commands to get cgminer to run my 3 Furys without crashing that would be great. I know this might not be the best thread to post this question in but you guys seem really helpful and I would appreciate any help I get (I would even donate a days worth of dogecoins or so to the person that gets me up and running). Thanks for the help and hopefully when I get off work I can try and get these miners running properly.
I'm not using Windows to control my miners, just a raspberry pi....but the config file/command line options should be quite similar.
For one - I'm not sure what version of cgminer you're using but the best I've found so far is the most recent from Dmaxl.
https://github.com/dmaxl/cgminerLooks like there's a slightly older(maybe one version behind) build here for windows:
http://cryptomining-blog.com/2924-cgminer-4-3-5-with-gridseed-and-zeus-scrypt-asic-supportI've not had a problem with Dmaxl's cgminer closing. Ever. The Zeus devices themselves are the pain in the ass part of the equation. Mine ALWAYS flake out after trying to use bfgminer with them and then try to use cgminer. The only way around the flake out that I've found is to power down everything, simply rebooting the rpi and resetting usb connections doesn't work.
Are you looking to use a config file or a command line? Personally, config is the way to go. Then no matter what, your command line is "cgminer -c miner.conf".
Here's my current (edited) config as an example....it may need some tweaking to work on Windows, may not. Obviously you would replace the /dev/ttyUSBx with whatever com port your miners are on.
{
"pools" : [
{
"url" : "stratum+tcp://US2.coinmine.pw:1111",
"user" : "user",
"pass" : "x"
},
{
"url" : "stratum+tcp://pool.manicminer.in:3333",
"user" : "user",
"pass" : "x"
}
]
,
"api-allow" : "W:127.0.0.1",
"api-description" : "cgminer v3.1.1-zm",
"api-listen" : true,
"api-mcast-addr" : "224.0.0.75",
"api-mcast-code" : "FTW",
"api-mcast-des" : "",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"hotplug" : "5",
"log" : "5",
"queue" : "9999",
"scan-time" : "15",
"scrypt" : true,
"shares" : "0",
"verbose" : true,
"zeus-chips" : "6",
"zeus-clock" : "328",
"zeus-debug" : true,
"zeus-nocheck-golden" : true,
"scan-serial" : [
"/dev/ttyUSB0",
"/dev/ttyUSB1",
"/dev/ttyUSB2",
"/dev/ttyUSB3"
]
}
If you download the windows build of cgminer from that link, and plug in that config file with the changes indicating the comm ports your miners are on...it should get up an running without too much more effort.
