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

Quote from: sandor111 on May 04, 2014, 06:32:51 AM

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

organofcorti

donator

Activity: 2058

Merit: 1007

Poor impulse control.

Here is an example for PHP:

Code:

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?

plzt

newbie

Activity: 22

Merit: 0

Quote from: ManeBjorn on May 04, 2014, 02:23:51 PM

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.

Quote from: plzt on May 04, 2014, 01:53:30 PM

Quote from: unamis76 on May 04, 2014, 10:59:50 AM

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

ManeBjorn

legendary

Activity: 1288

Merit: 1004

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.

Quote from: plzt on May 04, 2014, 01:53:30 PM

Quote from: unamis76 on May 04, 2014, 10:59:50 AM

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

newbie

Activity: 22

Merit: 0

Quote from: unamis76 on May 04, 2014, 10:59:50 AM

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?

wolfey2014

sr. member

Activity: 378

Merit: 250

Quote from: sandor111 on May 04, 2014, 10:24:50 AM

Quote from: ny2cafuse on May 04, 2014, 10:07:28 AM

Quote from: ny2cafuse on May 04, 2014, 10:07:28 AM

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

unamis76

legendary

Activity: 1512

Merit: 1012

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

sandor111

hero member

Activity: 616

Merit: 500

Quote from: sandor111 on May 04, 2014, 09:52:18 AM

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

racebyu

sr. member

Activity: 346

Merit: 260

Quote from: racebyu on May 04, 2014, 09:49:02 AM

This software works great!!! Thanks Sandor111.
Question, I set the com ports in my file to reflect a one blade miner.

minerd.exe --freq=800 --gc3355=\\.\COM3,\\.\COM4 --gc3355-chips=40 --url=stratum+tcp://usde.poolerino.com:3341 --userpass=username:password

If I have two blades how would I configure for this if on the same computer but each blade on a different pool?
Is this how I would configure or is it not possible?

minerd.exe --freq=800 --gc3355=\\.\COM3,\\.\COM4 --gc3355-chips=40 --url=stratum+tcp://usde.poolerino.com:3341 --userpass=username:password --freq=800 --gc3355=\\.\COM5,\\.\COM6 --gc3355-chips=40 --url=stratum+tcp://de2.miningpool.co:3399 --userpass=username:password

Thanks again for your help, still reading and learning....

If you want to run them on a different pool, you need to run two instances of cpuminer.
So:

Code:

minerd.exe --freq=800 --gc3355=\\.\COM3,\\.\COM4 --gc3355-chips=40 --url=stratum+tcp://usde.poolerino.com:3341 --userpass=username:password
minerd.exe --freq=800 --gc3355=\\.\COM5,\\.\COM6 --gc3355-chips=40 --url=stratum+tcp://de2.miningpool.co:3399 --userpass=username:password

Great, thanks again!!

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

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

sandor111

hero member

Activity: 616

Merit: 500

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.

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.