[GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning

[plzt]

Changed to the new version, running solid for 5+ hours. Autotune already finished, it's a very nice feature, now I can push my rig further!

Thanks for your work, sandor111

Having read on how tight the Blades are on specs - has anyone experienced issues pushing too hard via auto tune yet?

[1714775419]

1714775419

[1714775419]

1714775419

[1714775419]

1714775419

[1714775419]

1714775419

[ManeBjorn]

I have not had any issues with Autotune on the Blade.  If it goes to high and fails it puts it lower and it works great. 
The sweet spot seems to be 850 for me so far on the Blade.  Solid, stable, and next to no errors.

Changed to the new version, running solid for 5+ hours. Autotune already finished, it's a very nice feature, now I can push my rig further!

Thanks for your work, sandor111

Having read on how tight the Blades are on specs - has anyone experienced issues pushing too hard via auto tune yet?

[plzt]

I have not had any issues with Autotune on the Blade.  If it goes to high and fails it puts it lower and it works great. 
The sweet spot seems to be 850 for me so far on the Blade.  Solid, stable, and next to no errors.

Changed to the new version, running solid for 5+ hours. Autotune already finished, it's a very nice feature, now I can push my rig further!

Thanks for your work, sandor111

Having read on how tight the Blades are on specs - has anyone experienced issues pushing too hard via auto tune yet?

OK great, I've been running at freq 838 which seems to then default to 825 - has given me 5.58MH/s so wasn't complaining
Updated binaries, have got debugging and autotune on so will see where the white rabbit takes it

[organofcorti]

Here is an example for PHP:

Code:

<?php
define("API_MINER_START_TIME", "t");
define("API_DEVICES", "d");
define("API_CHIPS", "c");
define("API_LAST_SHARE", "l");
define("API_CHIP_ACCEPTED", "ac");
define("API_CHIP_REJECTED", "re");
define("API_CHIP_HW_ERRORS", "hw");
define("API_CHIP_FREQUENCY", "fr");
define("API_CHIP_HASHRATE", "ha");
define("API_CHIP_SHARES", "sh");
if(!($fp = fsockopen("127.0.0.1", 4028, $errno, $errstr, 0)))
{
    die("Failed to open socket");
}
stream_set_blocking($fp, false);
$out = json_encode(array("get" => "stats"))."\n";
fwrite($fp, $out);
usleep(100000);
$out = "";
while(!feof($fp))
{
    if(!($str = fgets($fp, 2048))) break;
    $out .= $str;
}
fclose($fp);
$arr = json_decode($out);
print_r($arr);

This will print the JSON array.
To get the list of devices you would simply do

Code:

$devs = $arr[API_DEVICES];

Thank you for taking the trouble, but I don't know what to do with that. Is there a non-coder version, for example a http extension?

[csmflynt3]

The only change in autotuning is the time needed to make adjustments, so autotune will take longer to finish.

Maybe that's the issue with my units then.  They are picky enough to want to work faster when they can, but are limited.  I'll recompile and check the results.

-Fuse

The higher the pool difficulty, the longer it will take.
By default, it's 3845 steps (~ 1 hour of hashing time). But with diff 512, it's 512*10 = 5120 steps.

I've set up a separate port on the pool specifically for gridseeds.  It maxes at 256.  Would it be 2560 then?

Is it possible to tune faster, or would that cause more problems?  I'm not saying could you do that, but rather can it be done.  It would be interesting to see what a faster turning time would do.

-Fuse

Sorry, I forgot to mention that the lower bound is 3845. But those values can be adjusted in the source code (gc3355.h).
Look for:

Code:

#define GC3355_OVERCLOCK_MAX_HWE 3
#define GC3355_OVERCLOCK_ADJUST_MIN 10
#define GC3355_OVERCLOCK_ADJUST_STEPS 3845

If you reduce GC3355_OVERCLOCK_ADJUST_MIN and GC3355_OVERCLOCK_ADJUST_STEPS, then it will lower the time needed to adjust. Just don't set it below 2 or diff * 2

Hey! I see lots of progress here since I reverted back to 2.3.2
I do miss the stats at the top though ;(
I think I'll try it out now since most of the issues seem to be handled now.
I know what a hassle updating can be. I just don't have the time or patience to be part of constant debugging. I need stable clean performance w/no issues. Seems it may be there now.
Is the win binary up to date and ready to go now?
Thanks for all your hard work and dedication Sandor111!
Peace
Wolfey2014

Wolfey I would definitely give this latest version a shot seems very stable now and performance is much better than cgminer/bfgminer from all of my testing

[racebyu]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

[Dabs]

I'm using version 0.9d, only two instances instead of 17. (Only because they are on different pools.) But reduced to one worker instead of individual workers.

[wolfey2014]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

[csmflynt3]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

[racebyu]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still is 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

Real random, 1 time was only after about 50 min of use on a pool.
The other time was after 5 hours on a another pool.
I just turned OFF the FIFO buffers on two Com ports, I am running on a Win 7 Acer laptop.
Should the Com ports "Bits per Second" is at 9600, should I turn this up higher on each port.

[wolfey2014]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still is 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

Real random, 1 time was only after about 50 min of use on a pool.
The other time was after 5 hours on a another pool.
I just turned OFF the FIFO buffers on two Com ports, I am running on a Win 7 Acer laptop.
Should the Com ports "Bits per Second" is at 9600, should I turn this up higher on each port.

Reset baud to 115200 - Uncheck 'Use FIFO buffers' = OFF....
'OK' out of it and repeat for each associated comm port.
This may very well solve your intermittent comm problem with the pool servers as csmflynt3 correctly recognizes.

[racebyu]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still is 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

Real random, 1 time was only after about 50 min of use on a pool.
The other time was after 5 hours on a another pool.
I just turned OFF the FIFO buffers on two Com ports, I am running on a Win 7 Acer laptop.
Should the Com ports "Bits per Second" is at 9600, should I turn this up higher on each port.

Reset baud to 115200 - Uncheck 'Use FIFO buffers' = OFF....
'OK' out of it and repeat for each associated comm port.
This may very well solve your intermittent comm problem with the pool servers as csmflynt3 correctly recognizes.

Great, done.
Will see what happens tonight.
Thanks Wolfey2014!

[racebyu]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

I heard the  volt mod on the blade can cause issues with the regs on the board overheating
due to no heat sinks on them like the round miners? Has anyone on here cranked a blade
up to see what the max Mhs is with a 39ohm or higher resistor?

[wolfey2014]

Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

I heard the  volt mod on the blade can cause issues with the regs on the board overheating
due to no heat sinks on them like the round miners? Has anyone on here cranked a blade
up to see what the max Mhs is with a 39ohm or higher resistor?

Ahh! You don't know what you've been missing  
Have a looksee! >>>> https://bitcointalk.org/index.php?topic=576784.0 < edit....DOH!
Enjoy!
Wolfey2014

[simon66]

Can someone compile and post the latest cpuminer from sandor11 for windows?

Thanks!

[jamieb81]

Can someone compile and post the latest cpuminer from sandor11 for windows?

Thanks!

it's already been done

https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip

[wolfey2014]

Can someone compile and post the latest cpuminer from sandor11 for windows?

Thanks!

Yep, you can always find the latest updates via a link in Sandor111's signature, too.....

[RowanX]

I'm getting a lot of rejects with cpuminer 0.9d. Didn't have this problem with 0.9c, I'm certain. Just me?

e.g. with 0.9c I was pleasantly surprised to see the poolside reject rate fall to a new all-time low of 0.38%. After switching to 0.9d, its gone up to 5.27% and climbing, and I can see reports of rejects locally a few times every minute. So I've gone back to 0.9c for now. Rejects such as:

"DEBUG: reject reason: unknown-work"
"DEBUG: reject reason: high hash"

[Kergekoin]

d looks fine to me. pool shows my efficency of 99.8%, while pool average is 98,65%

[racebyu]

I woke up this morning and found the Blade miner had stopped again during the night
using the latest software. I did turn OFF the FIFO buffers and set the baud speed to
115200 for ports 3 & 4 which are being used. Anything else I can check?

Its not the Blade as if I use BFGminer it works for days on end but lower hash power.
The software has stopped working on 3 different pools randomly and the laptop is hard
wired to the network console.
 
Here is a picture of the software as it was this morning on the Mining Pool Co.