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

That doesnt do what i was looking for. It just throttles ur GPU, like, slows it down to keep temperature under that number. And it slows down ur mining or stops it on that GPU if it needs to throttle GPU too much.

love the miner, super solid, very few crashes in the few weeks i have been testing. 

http://imgur.com/a/JfQhj

best miner so far for 1050ti  core+160 mem -300

cant wait for 9.9 with new algos

the problem with turning off your internal GPU is if you have your discrete card go out on you, then you wont have a graphics card to view your system on the monitor until you replace the discrete card. At least this way if your card malfunctions you can still use your system until you get it replaced.

teamviewer is good to remote with, I dont get any dropped rates when using it.

try

--max-temp=70 option

@crysx do you do any maintenance to the pool?

3 times my miner went idle in the last 12 hours  

I use teamviewer when reported drop happens. But when I connect the GPU also has to draw screen before supplying to teamviewer or not? I also notice much more power fluctuation on same GPU when I am connected. But this is not really important because I just connect every other day to check temps a bit or change what is mining on the rig.

I read somewhere that it is better to turn off internal GPU when using PC as mining rig. That apparently frees some channels in MB and helps system work better when using multi GPUs.

Cant application work with temperature values it shows on the screen, like it shows fan %, core clock and such? It needs to take those values from somewhere first and store them in a variable before puting them on screen. And if it reads temp is above 75 or 80 it calls command to close the whole app.

If i am dumb or bother you just say haha. Also dont want to waste ur time. It's just curiosity now as i used to programm on my college and have some okish background. The whole reason why i thought it's simple is coz application allready works with temperatures in some way. I would say it takes that data from somewhere, store then in some string variable, or maybe integer or whatever if it's not stored as character and then put them on the screen.

AND ANYWAY! I like your miner very much. I like it clean and simple as it is. Very nice UI. Also pool is rly cool. Have a lot of details and works well. Keep it up!

1) I use internal gpu as main - so no drop of hashrate. If you don't have one use teamviewer, tightvnc etc. May be rdp to main console will also work - /admin parameter (haven't tried that).
2) Many other pool have the same frontend, e.g. look https://zoi.acc-pool.pw/

I have installed/configured CWI miner on my rig with 4 x 1070. I am only running it for few hours now but it seems i have same results as with other good miners I used - around 30 MH per card. I really like extra effort for nice summary on top and the ability to stop mining if temperature of the card gets to high. I will continue for few more days for sure.

One thing i noticed is that GPU 0 drops hash rate to 25 MH when I connect remotely to my rig. Is this expected? I don't believe other miners had this so pronounced.

Off topic. Your pool has nicest dashboard I saw so far .

Use incognito mode on android if you are on chrome. Dunno about the second pc though

no - not for the foreseeable future ...

its been explained earlier ...

#crysx

having a look now ...

we had no idea - and no alerts came through of any issue ...

will fix now ... we are mining here also ...

#crysx

And about the -api? Is it going to be enabled in the 0.99 version?

we cannot control your system ...

therefore - we cannot write scripts and code specific to your system when issues arise - as your system is NOT like any one elses ... so writing a generic script for a goto loop is not our 'job' per se ... its good to help - but not our position to write anything for anyone regarding their own uses ... we provide the miner for testing and code the miner - provide the simplest of batch files so you have an example of some of the commands CWIgm is capable of - but will not write scripts for you ...

in saying that tho - there are MANY users that have - and will help ...

we use ovh / cryptobates group for two reasons ...

first - they ARE reliable and have been so for the time we have been using them - years now ... the downtime we have had with the servers / vps systems are so minimal - that we have had more issues with australian service providers than ovh or cryptobates group ...

second - when we do have an issue - its resolved in a matter of minutes - not hours ... and at a reasonable price ... we all accept some failure sometime - especially if actual hardware is at fault ... but to have our systems on say AWS for example ( like we did ) - they are not only reliable but VERY expensive ... i dont mean they are a couple of dollars a month more - i mean a LOT more expensive ... they also have the same issues / downtime / uptime as any other large provider we have used and tested ...

now the pool ... the pool is an mpos based pool ... it does what any mpos pool does - like suprnova for example ... the difference being the theme and backend builds ... otherwise - its structurally similar ... so if the stratum goes down - or the miner loses connection - or anything that triggers a reason for a message to be sent - it will send it if you have it activated in your profile ... anything that affects the worker that is setup in your profile - will be notified in as far as the pool is concerned ...

CWIgm-0.9.8 has a a few bugs ... the one you speak of is the termination bug that was found when we first set CWIgm for testing ... we are working on that and in CWIgm-0.9.9 its been rectified ... so if you use external software to shutdown and restart CWIgm - then it should work correctly ... but CWIgm ( as has been explained ) does NOT have that ability internally to shut itself down ...

we appreciate you feedback ...

#crysx

why? ...

no ips are blocked - unless they are the same ips we have been ddos'ed with ...

so there should be no reason as to not being able to login anywhere from any device ...

check username and passwords perhaps - and make sure they are EXACTLY the same as when logging in on the pc ... i know that sounds pretty silly to say - but this needs to be said as devices seems to have a mind of their own with caps and replacing words ...

#crysx

correct ...

CWI have now acquired sweepstakecoin and positioned in the arsenal of projects we currently have along with the other coins ...

no swap or major changes yet ... swap / changes like that will only take place if we do a major change in the code - requiring a hardfork ...

so for the time being - all is well ... a new thread with a basic op will be setup today so strasboug can close his current thread ... we may just even copy the old op just to move things along for the time being - while we setup the changes that are required in such a change ...

we are working on building the pool currently but have a few issues that need to be resolved ... as the daemon is giving us a few issues we did not expect ... a lot has to do with otr / onion integration and we are looking into whether this is something that really should be kept ... but its way too early to say anything until we start to delve into the code - and that will not happen until all the other components are finalized ...

so keep your coins - mine on the other pools if you wish to mine - and expect that when we resolve the daemon issue we currently have - we will reactivate the stratum for sweep so you can mine on our pool also ... we had to disable the stratum last night as someone was mining ( maybe you? hehehe ) - but the hash sent to CWI-Pool SweepStakeCoin will be lost as the daemon / wallet was not registering ANY blocks found during testing ... an error in the wallet itself was preventing ANY blocks from being sent to the blockchain ... so we are working on that issue now ...

rest assured tho - when we get the daemon running properly - we will open the pool for anyone to mine AND CWIgm-0.9.9 will have the algo / coin built in also ...

#crysx

Please add something that bat file can auto restart miner after crash/problem...  All work for stability doesn't make much sense if miner stop working in way like now and we can't auto restarts.

:loop
............
goto loop

This work for ccminer but not in your miner.

I like gui, your project but this should be first thing to make + more stable ded. hosting for pool (ovh is not so good because especially cheap servers = problems (long time) if something goes wrong).

It is also problem with monitoring - pool send emails because of long time from last share... but many times i got email and i saw miner is working.

Much work yet and it looks nice mainly now.... i hope next version will be soon and with solved problem with errors and we can have way to auto restarts after crash.

good advice ...

im going through the posts as i see them - so bear with me ...

#crysx

tanx for that ...

low hashrate in the pool brings low 'luck' in solving blocks ...

but it does work well - and we are working on improving it as best we can ...

a new big server will be commissioned soon - which means ALL mining will stop for the migration when the server is being built ...

a small sacrifice for a much faster bigger better server - and experience ...

you will be notified WELL in advance though ...

#crysx