Topic: ### A ChainWorks Industries (CWI) Project - CWIgm | Simple Powerful Stable - page 49. (Read 67732 times)

Mine always connect to port 6000 , too.

https://vgy.me/KR1fPo.jpg

thats strange ...

the reason i say that is simply because we did not activate the autosense feature in the miner ...

or should i say - we were NOT SUPPOSED to activate it ... not yet anyway ...

is everyone having this same issue? ... if so - then we must have set it active last codebase ... it shouldnt have been active until the next revision - as its currently experimental ...

with this next version - the autosense ( CWISense ) module will still be active - BUT you will be able to manually the port ... this will be released very soon ... though like i mentioned earlier - all those that have a miner currently will need to upgrade - and the system ( or lack thereof ) we currently have will take a while before we get everyone with the new miner ...

bear with us as we figure out how to get all those in our beta test the new miner ...

possibly an email address? ... will be checking if mega has this option ...

#crysx

Mine always connect to 6000:

hi all ...

we have been surprised and absolutely ecstatic about the response for the beta test from this awesome community of miners ...

we appreciate it very very much ...

we are working diligently to rectify a few issues that have risen - as we were not expecting an influx of testers land interest as you have shown ...

there will be a small update to the miner that will be released in the coming hours - which will focus on improving the usability and functionality of the miner ... stability is still the biggest factor here and as such - default intensities and a couple of other tweaks have been made to the miner ...

we will also release a specific compute50 version of the miner - to test those older maxwell cards ... we had huge numbers of the gigabyte 750ti oc lp in our theFARM before it got blown to bits - so these compute50 cards are an interesting test in itself ...

we are pleasantly surprised at some of the results and stability that you are getting from the results and settings you have posted - and are equally intrigued by the crashes and lockups that seems to occur with the few ... please keep posting these figures - as these stats are VERY important for the growth of CWIgm ...

the amount of pm we have had to join the beta test is massive ... and again - we are humbled by the interest you have all shown ... which is also the reason we have been holding back a little with posting the link to the current miner ...

CWIgm-0.9.7.1 will be released with some of the changes ive mentioned in the coming hours ... but we really do need a different way of pushing this miner out to the current and future beta testers ...

till then - we will continue to go through each and every pm we ( i ) get ...

tanx ...

#crysx

if you are using the current CWIgm-0.9.7 - this is not possible ...

the current miner is locked to lodiff port 2000 ...

this will change as we will add a port parameter for you to choose in the next small update ...

the diff was a little too high a target for the lodiff stratum port - thats changed now - and will not hit higher than 2.5diff ...

port 6000 however - starts at that diff ... and can handle all the hash you can throw at it ...

#crysx

hi wolf0 ...

well - sp is sp ... and does what he does for his own greedy benefit ... we all know that ...

much respect to you mate - after all you have for the community AND us ... if you decide you wish to come on board and help with an amd miner - we would luv to do it ... just like old times ...

we could always cut a deal for a bin that is tied to this test ( and pool ) if it can be done mate ... but as always - a faster sgminer bin is always welcome anyway - even though we dont really focus on amd much anymore - we would luv to help the community in that way also ... maybe bring some amd miners to the pool also ...

let me know mate ...

#crysx

CWGIgm-0.9.7 wont mate ...

compute50 devices will not be supported in this version ...

which is why in the next small update - a separate miner will be released specifically for compute50 devices - like the 750ti ...

#crysx

our entire network was disconnected for most of the night ...

tanx to the dumbass isp we have ( which 'should' be changing to a better one in two days time ) - our networks ( yes - ALL of them ) continuously disconnect due to dynamic ip changes ... imbeciles set us up on this type of internet connections even AFTER we specifically asked for a set of points to be strictly adhered to on our connection ... seriously deficient these blasted telcos ...

ok - bitch is over ... we are back ...

changed the stratum diff for the lodiff port 2000 - to max out target at 2.5 - it should go no higher than that ... the hidiff port 6000 is actually not in use with this current version CWI-gm-0.9.7 due to its locking on port 2000 ... sending the stratum into a seesaw rollercoast in diff ...

some issues should be fixed on that end the scale ...

hope you will come back soon - as we have a few changes in the next version ( for port adjustment and a couple of other parameters - to name a few ) ...

#crysx

how to set port to lowdiff? 

Your miner is clearly bit better (2-4%) than the one im using at the moment (ccminer1.0-skunk) but im bit annoyed by the pool restriction. Could you just add the current pool fee .7% to the miner and lose the pool restriction?

back onto other pools, will comeback again when pool diff is fixed including miners coming & going hope new version miner is more stable with the flexibility of options to choose diff levels.

so far i think for a start the pool & miner is doing very well. i have set donation of 0.7% & stayed for a little over 24hrs & the pool did hit couple of nice blocks & got a few nice shares due to a small pool so miners gets a bigger piece of the cake.

pool is very responsive & payout is quick too.

looking forward to further improvements, GL to all miners & OP.

much thx for the community support & i will be back when there are further improvements.

just my 2 sats, i hope OP will be a little more active with updates.

My rig has 6 pcs of 1080 , hash rate about 221 MH/s.

It alway connect to port 6000, that is for hi-diff.

Do I need to change to port 2000 , lo-diff? and How?

Rig Detail
OS      : Windows 10 X64
CPU    : Intel G4400
MB      : Biosstar TB250-BTC
RAM     : 4GB DDR4
GPU's  : 6 x GTX 1080
Driver  : 382.53


Palgin ccminer
i -20 : total 208 MH/s


CWI x32
i -24 : stop ming after a while
i -23 : stop ming after a while
i -22 : total 218 MH/s
i -21 : total 219 MH/s
i -20 : total 221 MH/s


CWI x64
i -24 : stop ming after a while
i -23 : stop ming after a while
i -22 : total 218 MH/s
i -21 : total 214 MH/s
i -20 : total 215 MH/s

I'd like to be a tester too. Having 6x1060 & 2xRX580 running

How can I get the miner to try?

tested on 750Ti and K2200
it doesnt work, there are some unsupported instructions because it complains about "Ilegal instruction"

so far most of my rigs are stable on the x64 for abt last 24 hrs or so.

testing x86 now & it seems a little faster to me on 2 x msi gaming x 1080 ti getting abt 51.05 - 51.4 Mh/s on both of them: *edited, sorry i was still running x64, now on x86*

PL 80 - Core 110/120 - Mem 0 - Temps 63C/60C - W - DO NOT show W anymore on x86

regarding the pool, my worker suddenly goes & comes, imo the default diff is a little too high ? i could be wrong but maybe a little lower diff & maybe next version would allow the miner to pick the diff & report back results.

we hit some blocks at the pool & yes sometimes it comes to the "luck" factor but always remember if something that's new, faster, bigger or more expensive may not be always good.

pool & miner is still new but so far imo it is doing quite well & there's definitely much room for improvements. i know how it is as i have ran both p2pool, mpos pools before, it's not as easy job.

i hope more can join us. op i have posted link of this thread on the official SIGT telegram group & few have pm'ed you, hurry with the "approval" rate, we need more onboard

cryptophilanthropist & chrysophylax are missing, come back ! hahaha

Rig Detail
OS      : Windows 10 X64
GPU's  : 3 x GTX 1070
Driver  : 382.05

Afterburner Settings
Core clock      :  +120
Memory clock :  -140
Power            :   85%

Performance
Intensity      : 25
Hashrate      : 26 mh/s to 27 mh/s  (per card)
Power Draw  : 115 W to 130 W   (per card)


I was getting the same hashrates and power draw with spmod's ccminer.

Reporting in after ~18 hours, and things are really good

This miner is better than all the others ones I've tried for SIGT...It's fast, very stable, and no dropped shares etc.
I've only tried the default intensity, and I've found the X64 miner was faster for my setup.

Now we just need a bit more pool hashrate to find more blocks please

Rig Detail
OS      : Windows 10 X64
CPU    : Intel G4400
MB      : Asus Prime Z270A
RAM     : 4GB DDR4
GPU's  : 5 x GTX 1080 ti Founders Edition
Driver  : 384.94
Case    : Rosewill 4U - closed

AfterBurner settings
PL       : 81%
Core    : +200
Mem   : 0
Fan     : 71%

GPU0: 64.0 C (180W / 71%)
GPU1: 58.0 C (190W / 71%)
GPU2: 55.0 C (191W / 71%)
GPU3: 56.0 C (188W / 71%)
GPU4: 59.0 C (189W / 71%)

Rig Detail
OS      : Windows 10
CPU    : Intel Core [email protected] GHz
VGAs  : 6 x ASUS Dual GTX 1060 3gb
Driver : 382.53

AfterBurner settings
PL       : 80%
Core    : +125
Mem   : -500

With x86 and -i 24, CWIgm gives me 102.43MH/s (avg 17.07MH/s per card)
With x64 and -i 24, CWIgm gives me 102.59MH/s (avg 17.09MH/s per card)

For me, there is no significant difference between x86 and x64.
I tried -i 25 and it crashed, just like sp-version

PS. skunksp-mod3 and -i 24 gave me 104MH/s for the same rig (17.33MH/s per card)