Topic: [GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 97. (Read 308626 times)

Thanx for that ... hint, let's see ...

seems like cpuminer uses full power ... to run even if it is only doing scrypt ....

normally I could use 10 miners on a 12v 25a ... power supply but with cpuminer (minerd) I can use only around 5 .... :-(

can someone confirm?

okay folks,
I saw a few bounties and was pm'ed about these problems and after 3 days of research here it is.

Problems:
1 - Apparently windows has problems releasing com ports, as we have all discovered.

2 - For some reason, my mining units don't like any com port above Com9
   (solved see atari's solution above )

3 -If I plug my usb hub into the computer with all my mining units connected to the usb hub all at once I cannot mine.
    (information overload on the usb hub I believe, is my theory)

note:  I am not using the controller because I am having trouble updating it.
My usb hub is connected directly to the pc.

My Solutions:

1.) this little tool resets com ports (made by user Uwe Sieber)
http://www.uwe-sieber.de/files/com_name_arbiter_setter.zip      
thanks to
http://blog.cognitioninfotech.com/2009/01/how-to-clear-or-reset-com-port.html

2.)See atari's solution above, works great

3.) plug your units into the usb hub one at a time.
This allows the usb hub to load the miner properly. The units should pop up in your device manager too. Wait a few seconds between each plug in. (I load the cpuminer for each unit during this time)

4.) use cpuminer-2.3.2-gc335-win32  
http://www.filedropper.com/cpuminer-232-gc3355-win32  

- If this information helps you or you put out a bounty, donations are appreciated
Ltc LKWXz6nGSkQ4Fy6KG2hz6LZ4xGF77CbGaK
Btc 1A7CVDAFC9ZQLBN3LhNPusCAgHU9Sw4YhL


next issues for me:

- Figure out how to verify if btc side is on with cpuminer and control btc on/off functions.

- Figure out how to update my controller firmware. ( I think its just a networking issue )

now its bedtime, while my miners rock it out
live long and prosper

Use

--gc3355=\\.\COM17 instead, that should fix it. you need the direct address for COM10 onwards

Is the performance on the PC better vs using the controller  ? For some reason I feel that might be able to be tweaked a bit more. Receiving my unit on Saturday, just following posts trying to figure out how to get them to reach 400 kh/s - 500 kh/s like others have.

The sequence is out. Move some of the steps around in different combinations until you get the same result every time. Then you've got it.
Remapping played a big part in the resolution of not being able to open comm 2...so now it opens comm 2 but it's really comm11? or remapping then changing the config file to match the same comm port as the remap?
Just thinkin out loud.....
wolfey2014

There is quite a bit of variance in pool-side reported hashrate. I think these are designed to hash at 300 khs, not more. That was the deal when I ordered my unit at least, so I don't expect more.

However, maybe others have secrets to share when it comes to overclocking?

They working but the hashing is 220 to 320 and I change the frequency from 600 to 800, any other secret?

thanks

Try increasing the frequency (--freq) from 600 to 800.

Beware of overheating, though! I left mine hashing at --freq=600 (getting about 300 khs, which is the nominal = announced hashrate)

thanks is working but only 320ks, any idea how to increase the hashes?

thanks again

• Open your device manager,
• Double click the Virtual COM port (your COM17) to open 'Properties' dialog
• Go to the 2nd tab, 'Port Settings'
• Click 'Advanced...'
• Change the COM: port number to the lowest available number (not sure about this)
• Note the new COM: port number
• Change your batch file to the new COM: port number
• Disconnect your miner from USB port
• Reconnect your miner to USB port
• Wait for two minutes
• Try again

It seemed to work for me and for lajz99 too (right?)

If I put the com17 that is the virtual is an error and com1 is working but pool not receiving, any thoughts?

thanks

Yes, replace COM1, COM2 and COM3 in my example with the appropriate virtual COM ports for your machine.

(this example is only useful to those who want to start multiple instances from the same batch file)

Don't we suppose to use the virtual com port?

thanks

You can try forking using the 'start' command of Windows. Can't test myself though, but AFAIK it may work in the batch file:


Up to 3 concurrent processes will be OK, not more, according to Beastlymac.

It doesn't look like you can. The software only supports one device per instance with a maximum of 3 instance. I have a step by step setup in my thread for the silver/gold units if people are looking for one. It is in my signature.

What is the format for entering multiple miners in the .bat file?  Can't figure that part out...got 1 running...

Thanks. Now what is this, I unplug the usb and plug again and I change to com1 that seems available even that is not the virtual one.

C:\Users\mining\Desktop\cpuminer\cpuminer-2.3.2-GC3355-win32>minerd  --freq=600
--gc3355=com1 --url=stratum+tcp://litecoinpool.org:3333 --userpass=XXXXXXXX.XX:X
[2014-02-26 18:34:29] Starting Stratum on stratum+tcp://litecoinpool.org:3333
[2014-02-26 18:34:29] GC3355 chip mining thread started, in SINGLE mode
[2014-02-26 18:34:29] open UART device com1
>>> LTC : 55aac000c0c0c0c00500000001000000
>>> LTC : 55aaef020000000000000000000000000000000000000000
>>> LTC : 55aaef3020000000
>>> LTC : 55aa1f2810000000
>>> LTC : 55aa1f2813000000
>>> LTC : 55aaef000500e082
[2014-02-26 18:34:29] set GC3355 core frequency to 600Mhz
>>> LTC : 55aaef02ffff000000000000000000000000000000000000
>>> LTC : 55aaef02ffffffff00000000000000000000000000000000
>>> LTC : 55aaef02ffffffffffff0000000000000000000000000000
>>> LTC : 55aaef02ffffffffffffffff000000000000000000000000
>>> LTC : 55aaef02ffffffffffffffffffff00000000000000000000
>>> LTC : 55aaef02ffffffffffffffffffffffff0000000000000000
>>> LTC : 55aaef02ffffffffffffffffffffffffffff000000000000
>>> LTC : 55aaef02ffffffffffffffffffffffffffffffff00000000
>>> LTC : 55aaef02ffffffffffffffffffffffffffffffffffff0000
>>> LTC : 55aaef02ffffffffffffffffffffffffffffffffffffffff
[2014-02-26 18:34:31] dispatching new work to GC3355 LTC core
>>> LTC : 55aa1f2810000000
>>> LTC : 55aa1f2813000000
>>> LTC : 55aa1f00000000000000000000000000000000000000000000000000000000fcff0300
004869f45e1f88826a483f5ceb83414773ed46563087d024373df8e7ff16f7c78b00000002a223b 8
19881506baf9c056fb774f5c006ad5d79feeccaf1ad42daec3c5e3fe06e3cd6f4ce305bf391b80c 0
8229d58fab9393dce981b584822a6bac38e052f0ad530ea4551b13b9a000000000ffffffff12345 6
78
[2014-02-26 18:34:50] dispatching new work to GC3355 LTC core
>>> LTC : 55aa1f2810000000
>>> LTC : 55aa1f2813000000
>>> LTC : 55aa1f00000000000000000000000000000000000000000000000000000000fcff0300
00b080dce6668f5fe08324c8eb8c5697e8a206991582fb2ad94eab51bf3a9e57f900000002a223b 8
19881506baf9c056fb774f5c006ad5d79feeccaf1ad42daec3c5e3fe06239736e8e2f93441694ae 4
9d641e3007cfae5836a8df937a991752a62343b5fe530ea4821b13b9a000000000ffffffff12345 6
78
[2014-02-26 18:35:35] dispatching new work to GC3355 LTC core
>>> LTC : 55aa1f2810000000
>>> LTC : 55aa1f2813000000
>>> LTC : 55aa1f00000000000000000000000000000000000000000000000000000000fcff0300
0028b4cdc30f65d35e5f493d86f530a03a56acc127ed5122fb1be3ae1d806a93a500000002a223b 8
19881506baf9c056fb774f5c006ad5d79feeccaf1ad42daec3c5e3fe061ed645fd9a18eec102bd0 9
07f50f09023043ab69b4aac7e445fd0fc7bc315bb0530ea4af1b13b9a000000000ffffffff12345 6
78
[2014-02-26 18:36:59] dispatching new work to GC3355 LTC core
>>> LTC : 55aa1f2810000000
>>> LTC : 55aa1f2813000000
>>> LTC : 55aa1f00000000000000000000000000000000000000000000000000000000fcff0300
003443936de6f6b47397ba9a69c45bae255ad7b66ec57d8a7e67d092d9b9767f5300000002a223b 8
19881506baf9c056fb774f5c006ad5d79feeccaf1ad42daec3c5e3fe062c2b6d037f3f53e6cbc5e 4
8d77044dfebfb882d0ac2c1b5cb96bae72caa3f23a530ea4dc1b13b9a000000000ffffffff12345 6
78
4-02-26 18:37:09] Stratum detected new block
[2014-02-26 18:37:12] dispatching new work to GC3355 LTC core
>>> LTC : 55aa1f2810000000
>>> LTC : 55aa1f2813000000
>>> LTC : 55aa1f00000000000000000000000000000000000000000000000000000000f0ff0f00
00cecb41fd9d055f2da2930768259ae560e27b9fe16545cf4bb74ea80820ce5c07000000026e45e 3
073436ed5b78d2734e34f9993397f18d824622383167e874af7ccd6e9e7198b6c4b7905204c3392 b
6a9a478e9c109438c822099d778213d8ff581e2dc4530ea50e1b13b9a000000000ffffffff12345 6
78

This is the key!!!
[/list]

This is the same issue I reported above.  At this point nobody knows what the issue is it sounds like...