The speed on zeusminers needs to be alot lower ,the ones i own at between 220 and 248, at 328 they not even start
They instant crash at 300+
Then you would own zuesminers Thunder X6. I have 9 of them. Ive been trying like hell to get these working on latest bfgminer. Olatest bfgminer will not detect mine. Can you please post you .bat file? Is there anything special you needed to do so bfgminer can see them? Did you recomiple the source and add zeus support?
Thanks in advance
Vegas
Would love it if someone could verify this is the case. Is the initial clock speed too high for newer devices?
I was only able to test up to the 256-chip devices some months ago.
I have both Zeus miner X6 and Zeus miner X3. Multiminer DOES work with Zeusminer X3 as its native speed is 328mhz, however even the latest Multiminer binary (released 4 days ago) does not work with thunder X6. Both the zeusminer thunder X3 and X6 are pretty much identical. They both have 128 chips, they even use the same FTDI driver, the only difference is clock speed. Thunder X3: 328mhz, Thunder X6: 248mhz. I quoted factory clock speeds. Yes, my thunder X6 do crash running latest multiminer, zeus thunder X3 works fine.
CONFIRMED!Have you tried specifying the clock speed with the BFGMiner arguments?
You can specify that in MultiMiner in the settings
here.
Edit: more info from README.ASIC (thanks to a recent contribution):
Zeusminers do not support autodetection, so you will need to use --scan to probe
for them:
-S zeusminer:\\.\COM3
You should also configure the driver for your specific device:
--set zeusminer:clock=N Clock frequency (default: 328)
--set zeusminer:chips=N Number of chips per device
Blizzard : 6 Cyclone : 96
Hurricane X2: 48 (2*24) Hurricane X3: 64 (2*32)
Thunder X2: 96 (4*24) Thunder X3: 128 (4*32)
Note: if you set this option incorrectly, the device may underperform and/or
misreport hashrate.
For example:
bfgminer --scrypt -o stratum+tcp://pool:port -u user -p pass -S zeusminer:\\.\COM3 --set zeusminer:clock=328 --set zeusminer:chips=128