Damnsammit (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 13, 2013, 09:45:25 PM |
|
10 PRINT "Hello World!"
New here. I got cgminer working well with my pool at Triple Mining. It's my first "rig" and it's just a bunch of old parts I threw together. Got it up to almost 800MHash/s, but it seems that my 5850 that I put in there is stalling out every 24-36 hours causing it to go "DEAD" and then not running until I get a chance to restart cgminer.
Saw a cool program in cgwatcher, downloaded it, linked it to my batch file (below) and am getting an error that I can't figure out.
When I click "Start Mining" it opens up CGminer with my batch file and starts mining. Then it sits in "waiting for CGminer API to start" mode for 15 seconds until giving me the following error:
"I was unable to start and establish communication with CGMiner. Check that the path, arguments, and config file (if any) are correct and try again."
This is my batch file for cgminer, i added the API stuff because when I was troubleshooting that seemed to be the problem that everyone was linking to, but I have never used anything with API before and am not entirely sure what it means.
cgminer -o stratum.triplemining.com:3334 -u xxx -p xxx --intensity 13 --gpu-engine 850 --thread-concurrency 7200 --shaders 2880 --worksize 128 --api-allow --api-listen --api-network
Thanks in advance. Any help much appreciated!
|
|
|
|
milone
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 14, 2013, 07:35:55 AM |
|
The newer versions should take care of enabling the API for you, but maybe there is still an issue I need to work out. Try changing --api-allow --api-listen --api-network to --api-listen --api-allow W:127.0.0.1 And let me know if that helps. I'll go over the API enabling code when I wake up.
|
|
|
|
Damnsammit (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 14, 2013, 12:17:05 PM |
|
That worked! Thank you so much! Love the program and appreciate all of the hardwork ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
Damnsammit (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 14, 2013, 08:00:41 PM |
|
That worked! Thank you so much! Love the program and appreciate all of the hardwork ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Good luck with solving further problems if they arise. Another problem has arisen. It keeps turning off my cards at temperature intervals that it is not hitting. The temp never breeches 91C but it keeps shutting off causing my hashrate to go from 700MH to an average of about 400MH because of the cards turning on and off... When I look in the log of cgwatcher it says
"[6/14/2013 2:58:23 PM] GPU0 intensity changed from 10 to 9 due to temperature of 90°C exceeding the set temp-overheat of 85°C"How can I change this to where it will not change the intensity of the GPU? I only want it to restart cgminer if a card goes "DEAD" not change with the settings that I have optimized for my rig in cgminer. I don't want cgwatcher to interfere with any settings, but to simply restart cgminer when and *IF* a card goes "DEAD". Help please! I'll give you a 0.01 BTC donation if you can help me resolve this ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
milone
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 14, 2013, 08:46:28 PM Last edit: June 14, 2013, 11:45:53 PM by milone |
|
Set the temp-target, temp-overheat, and temp-cutoff settings to values you prefer. The default values (given by the miner, not CGWatcher) are 75°C, 85°C, and 95°C respectively. You can set these settings in the config file or in the arguments.
Alternatively, you could disable overheat protection in CGWatcher's Monitor tab (make sure you're using 1.1.6.0a, otherwise you have to disable it in the INI file.)
Overheat protection is enabled by default and will do this to GPUs that the miner is not providing overheat protection for. The reason the miner would not be providing protection for a GPU is a) the miner is unable to get a temperature for the card (specifically, Nvidia GPUs), or b) the auto-gpu option is disabled which has to be enabled for the miner to really care about temperatures (although auto-fan may make it adjust fan speeds to keep in target range, its clock speeds will not be adjusted and it will not be disabled if it gets too hot.)
So your GPU meets one of these criteria. The temperature is exceeding the temp-overheat of 85°C (as it says it is 90°C), so it is attempting to reduce intensity to get the temperature back into the temp-target range.
Edit: Also, the reason you initially had API problems was because you used --api-allow without setting a value for it (e.g. W:127.0.0.1). This was unexpected on my part, so the next update will handle this.
Edit #2: I had found a bug that caused the overheat protection checkbox to not be checked on startup if overheat protection was enabled. So even if it was unchecked, it still may have been enabled unless you checked and unchecked the box yourself. Downloading again (1.1.6.0a) will give you the fixed version.
|
|
|
|
Damnsammit (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 17, 2013, 11:24:32 PM |
|
I think all I needed was the new version. However, just a note: When setting up my profiles (one for BTC, LTC, and FTC) it edited my batch files to include the directory and the batch file name, causing cgminer to try to open a batch that opened a batch, that opened a batch, etc... Not sure if anyone else has noted this, but the only way I found around it was to just cross my fingers and hope that it started up. I tried manually editing the batch files, but it seemed like it kept adding it back in there. I suppose I could just not use batch files and put all of those settings into the config. Anyways, thank you so much for this program and your help. I will be sending you a donation later this evening ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
Damnsammit (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 01:16:12 PM |
|
Donation sent! Thanks for all of the help and this very useful program ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Set the temp-target, temp-overheat, and temp-cutoff settings to values you prefer. The default values (given by the miner, not CGWatcher) are 75°C, 85°C, and 95°C respectively. You can set these settings in the config file or in the arguments.
Alternatively, you could disable overheat protection in CGWatcher's Monitor tab (make sure you're using 1.1.6.0a, otherwise you have to disable it in the INI file.)
Overheat protection is enabled by default and will do this to GPUs that the miner is not providing overheat protection for. The reason the miner would not be providing protection for a GPU is a) the miner is unable to get a temperature for the card (specifically, Nvidia GPUs), or b) the auto-gpu option is disabled which has to be enabled for the miner to really care about temperatures (although auto-fan may make it adjust fan speeds to keep in target range, its clock speeds will not be adjusted and it will not be disabled if it gets too hot.)
So your GPU meets one of these criteria. The temperature is exceeding the temp-overheat of 85°C (as it says it is 90°C), so it is attempting to reduce intensity to get the temperature back into the temp-target range.
Edit: Also, the reason you initially had API problems was because you used --api-allow without setting a value for it (e.g. W:127.0.0.1). This was unexpected on my part, so the next update will handle this.
Edit #2: I had found a bug that caused the overheat protection checkbox to not be checked on startup if overheat protection was enabled. So even if it was unchecked, it still may have been enabled unless you checked and unchecked the box yourself. Downloading again (1.1.6.0a) will give you the fixed version.
|
|
|
|
|
Rabinovitch
Legendary
Offline
Activity: 2030
Merit: 1076
BTCLife.global participant
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 07, 2014, 04:50:29 PM |
|
Hello! Nice thread to post my problem. ) On my laptop BFGminer 5.0.0 seems working normally itself, but when I try to make it work with cgwatcher 1.4.1 I see this: ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fsnag.gy%2FVGFgB.jpg&t=665&c=9AMKDZVc4_7giA) . I do use options "--api-listen --api-allow W:127.0.0.1" in my .bat file. Maybe I should also specify a port number there too?
|
|
|
|
|