Ficheiros necessários:
http://www.diffpair.com/lightningasic/Tutoriais:
https://bitcointalk.org/index.php?topic=482352.140https://bitcointalksearch.org/topic/gridseed-5-chip-cells-466230Dual minning com Gridseed em windows:
https://www.youtube.com/watch?v=vjXu5BYjEHo&list=UUcqRbsp96-Z3BAu_oSG-TCAFor those of you running Windows and CGminer for Gridseed ASICsLong time lurker, but new member here. I usually just sit back and read to solve my problems. I registered here today just to make this post.
I noticed when using Gridseed 5 chip miners with Windows/CGminer that miners would randomly drop off. When you close CGminer or reboot, this was especially true. The fix? Unplug the USB cable to your miner or hub and set hotplug to a higher number than 0 (most seem to like 5).
Great, but I have a job/life/kids/wife/car/hobbies/etc and can't always be next to the computer waiting to unplug/plug a USB connector.
I did a little experimenting and found out that disabling/enabling them in device manager brought them back without having to physically unplug them. This got me thinking...
I was able to use devcon.exe (from Microsoft) and write a quick batch file that enables/disables the miners. Then I scheduled the batch file to run ever 60 seconds (maybe overkill). The good part is that devcon.exe does not disable devices if they are in use, it waits for a reboot. So, your active miners never go down they just get "flagged" to be disabled on next boot and your inactive miners get disabled/enabled and start working again. This also requires hotplug to be greater than 0 (I used --hotplug=10)
It's quick and dirty and by no means a great solution. But it works. If someone wants to take this and expand on it, be my guest.
To make sure its working:
Run CGMiner, make sure it works and miners start.
Close CGMiner.
Run CGMiner, no miners (or less miners) are found.
Close CGMiner.
Run batch found below.
Run CGMiner, all miners working again.
You may need to edit the batch file to include match your miners hardware ID (*5740* is wildcard-part_of_hardware_ID-wildcard). I'm not sure if all hardware IDs are all the same, but all mine are. I just shoved it in the root of my C:\ drive. It's very basic and self explanatory.
Zip contains:
devcon.exe
resetusb.bat
https://www.dropbox.com/s/ih0eszwbf6bucl4/resetusb.zipVou actualizando este post