Currently I don't think cgminer is able to set different frequencies for sticks in the same cgminer instance. Since hotswap support became the standard and the -S flag disappeared I'm not sure what's required to specify devices in separate instances anymore.
i think it can, but you have to know which stick is in which port, and you have to number them correctly, its an augment set at run, i'll read the documents later and see how wrong i am.
Well, i think i might be wrong? there is a Advance USB options that lets you tell cgminer whats connected:
Advanced USB options:
The --usb option can restrict how many USB devices are found:
--usb 1:2,1:3,1:4,1:*
or
--usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0
or
--usb :10
You can only use one of the above 3
The first version
--usb 1:2,1:3,1:4,1:*
allows you to select which devices to mine on with a list of USB
bus_number:device_address
All other USB devices will be ignored
Hotplug will also only look at the devices matching the list specified and
find nothing new if they are all in use
You can specify just the USB bus_number to find all devices like 1:*
which means any devices on USB bus_number 1
This is useful if you unplug a device then plug it back in the same port,
it usually reappears with the same bus_number but a different device_address
You can see the list of all USB devices on linux with 'sudo lsusb'
Cgminer will list the recognised USB devices
with the '-n' option or the
'--usb-dump 0' option
The '--usb-dump N' option with a value of N greater than 0 will dump a lot
of details about each recognised USB device
If you wish to see all USB devices, include the --usb-list-all option
The second version
--usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0
allows you to specify how many devices to choose based on each device
driver cgminer has - the current USB drivers are:
AVA, BAS, BFL, BF1, DRB, HFA, ICA, KLN and MMQ.
N.B. you can only specify which device driver to limit, not the type of
each device, e.g. with BAS:n you can limit how many BFL ASIC devices will
be checked, but you cannot limit the number of each type of BFL ASIC
Also note that the MMQ count is the number of MMQ backplanes you have
not the number of MMQ FPGAs
The third version
--usb :10
means only use a maximum of 10 devices of any supported USB devices
Once cgminer has 10 devices it will not configure any more and hotplug will
not scan for any more
If one of the 10 devices stops working, hotplug - if enabled, as is default
- will scan normally again until it has 10 devices
--usb :0 will disable all USB I/O other than to initialise libusb
which I'm sure you could use this to tell cgminer what speed to run each device at..
Maybe get ck- to pop in and tell me what I'm thinking wrong?
Alas, this is the Sales thread, not the discussion thread, if it wasn't for the price of milk here in aussieland, I'd have another BTC in sides wallet for 10 more of these sticks :< maybe i should stop milking up my coffees..
I'm not afraid of some soldering, or using a meter. But I'm not sure how you did this.
Does anyone have a guide?
While waiting for AJRGale's guide - the short of it is that instead of using the USB host for power, you use an external (5V!) power supply.
That can be as simple as severing Vbus (V+ / the red wire), connecting the positive of your power supply where Vbus used to connect (or connecting it closer to the actual ports on the hub (in case the traces are pretty narrow and you're not too sure the traces will handle the current), connecting your power supply's negative where USB GND (V- / the black wire) connects, and off you go.
You can add some capacitors for stability or make the circuit a bit more intelligent (google 'USB power injector'), but it pretty much comes down to that first sentence.
I picked a USB hub that basically has that intelligent bit and whatnot already built-in so I can just plug external power in with a barrel jack, but it is a bit power limited, so I also have a small board where I've only done the 'sever the red wire' approach that's been running my engineering sample Compac for some higher speed tests, but efficiency goes down the gutter at those higher rates
working on it, I'm pulling up some old threads that people have discussed and done this said build too, just for extra clarity. i might even go as far as to show you how NOT to do it!
