API tools faq
paste
Advertisement
JMilone

CGWatcher 1.1.4.0 ReadMe

JMilone
May 13th, 2013
211
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 34.02 KB | None | 0 0
raw download clone embed print report
  1. CGWatcher
  2. version 1.1.4.0
  3. © 2013 Justin Milone
  4. Milone99k@gmail.com
  5. http://manotechnology.blogspot.com/p/cgwatcher.html
  6. Donate:
  7. BTC: 19msnBddmcaHnbTTQgFgzPDuy6PqfBgFJh
  8. LTC: LM6Un6hZvPzLBggJWiAVG6E6w2GfaHukXY
  9. NMC: NJjD4rP5xy2mgSK8gXXsZwFkdknbvtvy3q
  10.  
  11. UPDATE:
  12. See the Changelog at the bottom for more information on what has changed in this update.
  13.  
  14.  
  15. PURPOSE:
  16. CGWatcher is a GUI/monitor for CGMiner and BFGMiner, the bitcoin mining program. It provides a graphical user interface, along with
  17.  
  18. control and monitoring options to help ensure mining runs consistently. These miners are capable of detecting and recovering from many
  19.  
  20. problems that can interrupt mining, but there are cases where it is not and having a small utility to keep an eye on it and give it a push
  21.  
  22. when necessary has allowed me to setup 24/7 mining computers without having to constantly monitor them.
  23.  
  24.  
  25. HOW IT WORKS:
  26. CGMiner and BFGMiner have an API allowing other applications to communicate with them for purposes like this. Specifically, it uses RPC to
  27.  
  28. allow communication between the two applications. CGWatcher sends a command to the miner, and the miner returns a reply message. These
  29.  
  30. commands can be simple requests for information (such as asking what the current hash rate is or what devices it is using) along with
  31.  
  32. commands that tell the miner to do something (change pools, disable a device, or restart, etc.) This allows a GUI to be written with a
  33.  
  34. more user-friendly interface without affecting the miner's performance and hash rate. The miner gets to stay lightweight and as fast as
  35.  
  36. possible, and the more resource-intensive GUI program only sends requests when necessary. This communication is not enough to have a
  37.  
  38. noticable effect on the miner's performance.
  39.  
  40.  
  41. REQUIREMENTS:
  42. The .NET Framework 4.0 is required. The latest version of CGMiner or BFGMiner is recommended, although changes to these programs may
  43.  
  44. require updates to CGWatcher, which I will try to do as quickly as possible. These miners must be ran with parameters giving CGWatcher
  45.  
  46. full API privilege for full functionality. You can set these parameters using command-line arguments or in the miner's configuration
  47.  
  48. (*.conf) file.
  49.  
  50. Command-line arguments:
  51. --api-listen --api-allow W: 127.0.0.1
  52.  
  53. Configuration file entries (separate entries with commas):
  54. "api-listen" : true
  55. "api-allow" : "W: 127.0.0.1"
  56.  
  57.  
  58. USING CGWATCHER:
  59.  
  60. PROFILES
  61.  
  62. Version 1.1.4 introduces mining profiles that allow you to easily switch between crypto-currencies. Upon starting version 1.1.4, a default
  63.  
  64. profile will be created for you. If you've used previous versions of CGWatcher, your previous miner and arguments will be used for this
  65.  
  66. profile. If you haven't used CGWatcher before but have a miner running when you first start it, it will load that miner to the default
  67.  
  68. profile. If none of these are met, it will check for a miner (cgminer.exe or bfgminer.exe) in the same directory or subdirectories
  69.  
  70. (miner,cgminer,bfgminer). If it cannot find a miner, you will just have to edit the profile and point to the miner's executable (or a
  71.  
  72. batch or command file you use to launch the miner.) You can add, edit, or delete profiles by clicking 'Manage Profiles...' in the Settings
  73.  
  74. tab.
  75.  
  76. (Note: CGWatcher will only create a profile for a running miner if no profiles exist. Once at least a default profile exists, any other
  77.  
  78. miners that are running will be considered an "unknown" profile.)
  79.  
  80. To add, edit, or create profiles, use the 'Manage Profiles...' button on the Settings tab. Although the Settings tab displays the active
  81.  
  82. profile's settings, you cannot edit them here. Also, the small buttons with the yellow folder icons are to open that file's directory, not
  83.  
  84. to browse your computer to select a new profile. I apologize for the confusion, and may modify or remove these buttons in the future. If
  85.  
  86. you want to edit these profile settings, click the 'Manage Profiles...' button and you can do so in the Mining Profiles window.
  87.  
  88. For each profile, you can specify the following:
  89.  
  90. -Profile name (required) - a unique name (e.g. "Bitcoin", "Litecoin")
  91.  
  92. -Miner Path (required) - path to the miner's .exe (or .bat/.cmd file used to launch the miner). Each profile can have its own miner,
  93.  
  94. they can all use the same one, or a mix of both.
  95.  
  96. -Config File (optional) - a config file to use with the miner (does not have to be in the same directory as the miner). If the config
  97.  
  98. file path contains spaces, CGWatcher will automatically put quotes around it to prevent an error in the miner. You can specify the
  99.  
  100. complete file path, or just the filename for config files in the same directory as the miner and CGWatcher will convert it to the complete
  101.  
  102. path for you. If you've named config files in Config File Editor (see below), they will appear in a drop-down list in the Config File
  103.  
  104. textbox allowing you to select a config file by name it it will be automatically converted to its file path.
  105.  
  106. -Miner Arguments (optional) - arguments used when launching the miner. Note: if you set a .bat or .cmd file as the Miner Path, the
  107.  
  108. arguments WILL BE saved inside the .bat or .cmd file. Changing the profile arguments in CGWatcher will not affect other lines in the .bat
  109.  
  110. or .cmd file, so if you're setting GPU_MAX_ALLOC_PERCENT or GPU_USE_SYNC_OBJECTS in your batch/command file before launching the miner,
  111.  
  112. these lines will remain unaffected.
  113.  
  114. If you've set a config file in the Miner Arguments using --config, CGWatcher will automatically extract it from the arguments and set it
  115.  
  116. as the Config File. So if you see the --config option disappear from the Miner Arguments textbox, it is because it is now specified in the
  117.  
  118. Config File textbox... and if it is in the Config File textbox, it will be used when launching the miner.
  119.  
  120. There are two profiles you should be aware of in CGWatcher - the active profile and the current mining profile. The active profile is the
  121.  
  122. one you want to use for mining and you can change this any time in the Settings tab by selecting a profile from the drop-down list and
  123.  
  124. clicking 'Save Settings'. However, if the miner was running while you switched to a new profile, you will need to restart it for it to use
  125.  
  126. the new profile. CGWatcher will prompt you to restart the miner when you change the active profile while mining, but if you choose not you
  127.  
  128. will not be actually using the new profile until you restart the miner. The Status tab, as well as the bottom right corner of the window
  129.  
  130. when the miner is running, display the current mining profile - the profile the miner is currently using. The Settings tab will show you
  131.  
  132. the active profile. If the miner is not using the active profile you've selected, it will after you restart it. This active profile is
  133.  
  134. what is saved and loaded the next time CGWatcher opens.
  135.  
  136. - The only time you need to worry about the current mining profile is if you change profiles while a miner is running and choose not to
  137.  
  138. restart the miner when CGWatcher asks you. -
  139.  
  140. Example: You are mining with a profile called "Bitcoin". While the miner is still running, you go to the Settings tab and change the
  141.  
  142. active profile to "Litecoin" and click 'Save Settings'. You will be asked if you want to switch to the "Litecoin" profile now, and
  143.  
  144. declining means the miner will keep running under the "Bitcoin" profile until the next time it is restarted or stopped and started.
  145.  
  146.  
  147. INTERFACE
  148.  
  149. To keep the interface as small as possible, features are separated into tabs. Upon starting for the first time, you should go to the
  150.  
  151. Settings tab and click 'Manage Profiles...' to setup your mining profiles. The Settings tab also allows for changing the miner RPC
  152.  
  153. server's IP address and port, but this will start out set default to the miner's defaults and should not need changed for most people.
  154.  
  155. you should go to the Settings tab and specify the path to CGMiner's executable (cgminer.exe), CGMiner arguments, and the IP Address:Port
  156.  
  157. for CGMiner's RPC server. Below is a list of the tabs and information on the features each tab contains:
  158.  
  159.  
  160. STATUS
  161.  
  162. The Status tab provides general information such as hash rate (current and average), accepted and rejected shares, etc. Moving the
  163.  
  164. mouse over a text box will provide you with more information about the data being shown in it. This tab also features a line graph showing
  165.  
  166. the current hash rate and GPU temperatures for the last ten times information was polled from the miner.
  167.  
  168. At any time, you can refresh the information in CGWatcher by clicking the Refresh button. If monitoring is enabled, this will be
  169.  
  170. done automatically at the interval you specify. However, if you wish to update it instantly without changing the interval, you can use
  171.  
  172. this button at any time.
  173.  
  174. The Status tab also includes a large Pause/Un-Pause button. If a miner is currently running, the button will be labeled "Pause
  175.  
  176. Mining". Clicking it will shutdown the miner. Once the miner is not running, the button turns into a "Start Mining" button. Clicking it
  177.  
  178. will launch the miner using the active profile and begin mining. The idea behind this button is to have a very easy way to "pause" mining
  179.  
  180. if you wish to do something on the computer (like watch a video, for example) where you will need more performance from your GPU than you
  181.  
  182. can get while mining, since mining usually maxes out your GPU. Depending on your GPU(s) and intensity settings, you may not need to pause
  183.  
  184. the miner to do something like watch a video, but the option is there nonetheless.
  185.  
  186. On the bottom of the window underneath all of the tabs, you will see a status display on the left (which only appears when
  187.  
  188. CGWatcher is doing something.)
  189. On the right is a miner status display that says whether a miner is running or not. Monitoring has to be turned on for this to
  190.  
  191. work, as it will not get updated if monitoring is turned off. Even if you open or close CGMiner outside of CGWatcher, it will still detect
  192.  
  193. that CGMiner is running and update the display accordingly.
  194.  
  195.  
  196. MONITOR
  197.  
  198. The Monitor tab provides options for monitoring CGMiner and watching for problems and correcting them. Changes to the settings on
  199.  
  200. this tab are applied instantly and do not need to be "Saved."
  201.  
  202. "Enable monitoring, get miner status every: <seconds>" - This turns on the monitoring feature which will request mining
  203.  
  204. information from the miner at the interval you set. This option has to be turned on in order to enable the other monitoring and recovery
  205.  
  206. options below it, because with it disabled it will not continuously watch the miner. The default value of 10 seconds means every 10
  207.  
  208. seconds CGWatcher will request data from the miner, update the display, and perform the checks that you've enabled. When this option is
  209.  
  210. turned on, you will see "[Monitoring]" added to the text in the CGWatcher title bar.
  211.  
  212. "Restart if total hashrate falls below: <hashrate> <Kh/s;Mh/s;Gh/s> - On occasion I have seen the hashrate fall to virtually
  213.  
  214. nothing for some unknown reason. To correct this, you can enable this option and set it to a low value such as 10% of your current
  215.  
  216. hashrate. For example, if your current hashrate is 500 Mh/s, you may want to set this at 50 Mh/s (or below). A number this low will avoid
  217.  
  218. restarting due to small fluctuations in hashrates that can occur. If the total hashrate is below this cutoff for 3 consecutive checks, the
  219.  
  220. miner will be restarted.
  221. (Note: You can change the number of consecutive checks by editing the HashRateCounter value in CGWatcher.exe.ini)
  222.  
  223. "Restart miner every: (hours of continuous mining): <hours>" - As a sort of last resort, you can specify a number of hours of
  224.  
  225. continuous mining before the miner is restarted. For example, the default value of 24 means the miner will be restarted after it runs for
  226.  
  227. 24 continuous hours (without stopping). Whenever the miner is stopped or restarted, this timer resets. As an example, if you set this to 2
  228.  
  229. hours and a temporary problem disrupted mining, it should ensure that at most you will have 2 hours of downtime.
  230.  
  231. "Restart miner if accepted shares stop increasing for: <minutes>" - If your accepted share count stops increasing for an unusually
  232.  
  233. long amount of time, this likely indicates a problem with your pool or network. Setting this to 10, for example, means that if your
  234.  
  235. accepted share count doesn't increase for 10 minutes, the miner gets restarted.
  236.  
  237. "Restart miner when sick or dead GPUs are detected" - More often than not, the miner will detect sick or dead GPUs but is unable
  238.  
  239. to restart them and continue mining. When CGWatcher detects these sick or dead GPUs, it restarts the miner. (Note: This option no longer
  240.  
  241. attempts to restart the sick or dead GPU only, as that often fails. Instead it now completely restarts the miner.)
  242.  
  243. "Restart miner if full API access becomes read-only or if API access is lost compeltely" - If CGWatcher had API access to the
  244.  
  245. currently running miner process but then lost it, it indicates a problem with the miner and it will restart it by killing the process and
  246.  
  247. restarting. Likewise, if CGWatcher had full API access and this became read-only or lost completely, it also performs the kill and
  248.  
  249. restart. If it has read-only access and never had full access, it will not restart the miner. Nor will it restart any miner that it never
  250.  
  251. had API access to.
  252.  
  253. "Ensure miner stays running unless paused or stopped in CGWatcher" - means what it says. If you enable this option and you or some
  254.  
  255. unknown force closes the miner outside of CGWatcher, CGWatcher will start it up again. And it will continue to do this until you enable
  256.  
  257. this option. Stopping the miner by using the Pause Mining or Stop buttons will prevent the miner from being restarted. If starting the
  258.  
  259. miner fails 3 consecutive times, CGWatcher will give up and notify you of a problem.
  260.  
  261. SCHEDULE
  262.  
  263. "Start mining on selected days at this time: (if not already running) <time><days>" - Specify a time to start mining on the days
  264.  
  265. you select. If mining is already running, CGMiner will be restarted to correct any problems that may not have been corrected by other
  266.  
  267. checks. The actual time mining is started may vary up to the monitoring interval you've set. For example, if you've set the monitoring
  268.  
  269. interval to 10 seconds and the schedule start time to 5:00:00, the actual start time may be anywhere between 5:00:00 and 5:00:10.
  270.  
  271. "Stop mining after: <hours>" - When you use the scheduling option, you can specify a number of hours for it to stop mining after.
  272.  
  273. This would allow you to, for example, run CGMiner while you sleep by setting it to start at night and stop after 8 hours. CGMiner will
  274.  
  275. only be stopped if it was started by the scheduler. If you use the Start, Stop, or Restart buttons on the Settings tab, the scheduled stop
  276.  
  277. will be aborted. You can, however, use the Pause Mining/Start Mining button on the Status tab to pause or un-pause scheduled mining
  278.  
  279. without aborting the scheduled stop time.
  280.  
  281.  
  282. DEVICES
  283.  
  284. This tab shows mining device information, and is broken down into more tabs - one for each type of device. Currently it only
  285.  
  286. supports GPUs. At the top is the number of GPUs found and a drop-down box for selecting a GPU. Once you select one, you can see
  287.  
  288. information specific to that GPU (hashrate, clock, temperature, etc.) Some of these text boxes are read-only (gray text) and some are
  289.  
  290. editable (black text), meaning you can change values and click 'Apply Changes' to change those settings on the GPU even while mining. This
  291.  
  292. makes it easier to test and adjust different settings without having to edit the CGMiner config file and restart the miner, or use the
  293.  
  294. miner's command-driven interface.
  295. Towards the bottom is a large text box containing more information for the selected GPU. Underneath is the selected GPU's status
  296.  
  297. (ACTIVE, DISABLED, etc.) and buttons to enable/disable or restart the GPU. (Note that enable/disable and restart are just in terms of
  298.  
  299. mining and will not affect other programs.)
  300.  
  301. If you have a low monitor interval you may not have time to change settings in between refreshes. If you are just changing one
  302.  
  303. setting, you may have enough time to change it and click Apply Changes because CGWatcher will not update a textbox that you are changing.
  304.  
  305. If you find that you need more time, you can click the 'Freeze' button next to the GPU list to stop updates on all editable fields. This
  306.  
  307. will allow you to edit the settings uninterrupted, click 'Apply Changes', then click the same 'Un-freeze' button to resume updates in
  308.  
  309. these fields. Even while frozen, all other fields will continue to update as usual.
  310.  
  311. Changing GPU settings to values outside of their operating ranges can cause system crashes and possibly damage components! Please
  312.  
  313. make sure you know what you are doing before you change these. These settings can all be changed in the miner arguments and config file as
  314.  
  315. well, but neither program is responsible should you push your hardware outside of its operating range and break something.
  316.  
  317. CPU, FPGA, and ASIC support - I don't mine with my CPU, and don't yet have FPGAs or ASICs. If you would like to help get these
  318.  
  319. devices supported, go to the Tests tab and click the appropriate Device Tests button. Each one will request appropriate information from
  320.  
  321. the miner and display the results in the large textbox. You can then send these results to me at Milone99k@gmail.com so I can see what
  322.  
  323. kind of data is available and implement support for it. I realize I could get the CPU data myself, but I figured asking for it and seeing
  324.  
  325. how many people mine with CPUs would help determine the demand and whether or not it is worth the effort adding.
  326.  
  327.  
  328. POOLS
  329.  
  330. This tab is similar to the devices tab, except that it shows pool information. You can select a pool from the drop-down list at
  331.  
  332. the top to see information specific to that pool. You can enable/disable a pool, change the pool's priority (which will adjust other
  333.  
  334. pools' priorities accordingly), and switch to a specific pool (which will enable the pool (if it is disabled) and set its priority to 0).
  335.  
  336. The large text box shows more information specific to the selected pool.
  337.  
  338. Clicking the 'Manage Pools' button will open the current mining profile's config file in Config File Editor. You can change any
  339.  
  340. config settings, including adding, editing, or removing pools. Once changes to the config file are saved, the miner will need to be
  341.  
  342. restarted to load the updated configuration.
  343.  
  344.  
  345. REPORT
  346.  
  347. This tab's purpose is for all of the data I couldn't fit anywhere else. It shows information regarding CGWatcher and its monitor
  348.  
  349. (if enabled), the current miner, and the active profile. At the bottom is debug information that may be helpful when troubleshooting
  350.  
  351. problems or bugs. If you are having a problem with CGWatcher, submitting the text in this tab along with a description of what is
  352.  
  353. happening should be enough to troubleshoot in most cases.
  354.  
  355. Similar to the GPU tab, you can freeze the report by clicking the 'Freeze Report' button. This prevents any updates to the report
  356.  
  357. data so you can read it without interruption. When you want to resume updates, click the same 'Un-freeze Report' button.
  358.  
  359.  
  360. REMOTE
  361. The Remote tab is for future configuration and use with CGRemote, which will allow you to monitor and control your miners
  362.  
  363. remotely. More information will be given when it is released.
  364.  
  365.  
  366. SETTINGS
  367.  
  368. This tab is for CGWatcher settings. Remember to click 'Save Settings' to save any changes to the fields on this tab. If you later
  369.  
  370. change a setting without saving and want to go back to the last saved settings, click the 'Cancel' button. The settings include:
  371.  
  372. Active Profile
  373. Here you can set the active profile you want to use. If the miner is running while you change profiles, you will need to restart
  374.  
  375. it for it to use the new profile. The profile's settings are displayed below, but are read-only. If you want to change profile settings,
  376.  
  377. click the 'Manage Profiles...' button. Next to the Miner and Config File paths, you will see buttons that either open the corresponding
  378.  
  379. file's directory, open the config file in Config File Editor, or open the file in Notepad.
  380.  
  381. - "Check mining profitability" opens http://dustcoin.com/mining which displays estimated earnings for mining different crypto-
  382.  
  383. currencies with a given hashrate.
  384.  
  385. Miner Settings
  386. - 'Start', 'Stop', 'Restart' buttons - Start, stop, and restart the miner. Note that if you are using the scheduled mining option
  387.  
  388. in the Monitor tab, using these buttons during a scheduled mining time will cancel the 'Stop mining after <hours>' option if you've
  389.  
  390. enabled it. If you would like to stay on the scheduled mining, use the Pause Mining/Start Mining button on the Status tab.
  391.  
  392. - "Miner Address (IP:port)"" - This is the IP Address and port of the miner's RPC server. This is required for CGWatcher to work,
  393.  
  394. because it communicates with the miner via RPC. The default values are 127.0.0.1:4028.
  395.  
  396. - "Miner window mode" - For those who don't like seeing the miner, you can select to have it ran hidden or minimized. Minimized
  397.  
  398. will still show its icon in the taskbar, which you can click on to restore the miner's window. Hidden will cause the miner to not appear
  399.  
  400. on the screen or in the taskbar. The only way you can tell it is working is by checking CGWatcher. You will need to use the buttons in
  401.  
  402. CGWatcher to start/stop/restart the miner. Alternatively, you could kill the cgminer.exe or bfgminer.exe process in Task Manager.
  403.  
  404. - 'Config File Editor' opens a blank/default config file in Config File Editor. You will also see smaller Config File Editor
  405.  
  406. buttons next to textboxes that contain config file paths, allowing you to quickly open those files in the editor.
  407.  
  408.  
  409. CGWatcher Settings
  410. - "Run when Windows starts" adds a startup entry for CGWatcher. This means it will launch automatically when Windows starts. This
  411.  
  412. is useful in the case of system restarts to ensure mining resumes automatically (after a system crash, for example). However, if your
  413.  
  414. computer requires you to login to Windows, you would obviously have to login first before mining could be resumed after a system crash and
  415.  
  416. automatic restart.
  417.  
  418. - "Start Minimized" starts CGWatcher minimized. If the "Minimize to system tray" option is also enabled, CGWatcher will start
  419.  
  420. minimized to the system tray.
  421.  
  422. - "Minimize to system tray" - minimizes CGWatcher to the system tray. This means it will not appear in the taskbar. Instead, its
  423.  
  424. icon will be in the system tray above (or near) the clock. Double-click the CGWatcher icon to restore its window.
  425.  
  426. - "Run miner when started" - will launch the active profile's miner and start mining when you run open CGWatcher (if the miner is
  427.  
  428. not already running). For continuous mining after a system crash in the above example, you would also want to enable this feature.
  429.  
  430. The idea is, in case of a system crash (BSOD, "Blue screen of death"), the computer is automatically restarted. The order to
  431.  
  432. resume mining would be:
  433.  
  434. Computer restarts -> [Windows login?] -> Launch CGWatcher automatically -> Launch CGMiner automatically = mining resumed
  435.  
  436. - "Don't prompt on exit" - By default, CGWatcher will ask you if you're sure you want to exit if: the miner is running, monitoring
  437.  
  438. is enabled, and the reason for exit is the user is closing the window. Enable this option to prevent any prompts upon exiting.
  439.  
  440.  
  441. LOG
  442.  
  443. This displays the CGWatcher log for the current session (since CGWatcher was started).
  444. - 'Clear Log Text' - clears only the textbox without deleting any log entries.
  445. - 'Clear Entire Log' - completely deletes all data from the log file.
  446. - 'Open in Notepad' - if you need to view older log events, this button opens the cgwatcher.log file located in the same directory
  447.  
  448. as CGWatcher. This will display the entire log history, either from the last time you cleared it or the first time you ran CGWatcher.
  449. - 'Show Debug Log Entries' - the log typically keeps you updated on what CGWatcher is doing or has done. There are also debug log
  450.  
  451. entries that provide error and troubleshooting information. Checking this box shows those entries as well.
  452.  
  453.  
  454. TESTS
  455.  
  456. This tab allows you to send commands to CGMiner and see what kind of reply messages it sends back. This can be useful for
  457.  
  458. requesting information that I haven't yet implemented into the program. The reply messages are comma-delimited, but checking the "Convert
  459.  
  460. comma-separated results into line-separated results" will do what it says, making the results easier to read. Unchecking it reverts back
  461.  
  462. to the comma-delimited message.
  463.  
  464. If you wish to send multiple commands in one click, enter the commands in the Diagnostic text box (separate them by commas). Then
  465.  
  466. click Run. The reply messages for all of the commands will be displayed in the large Result message text box.
  467. For information on Device Tests (CPU, FPGA, and ASIC), see the Devices section above.
  468.  
  469.  
  470. ABOUT
  471.  
  472. Displays information about CGWatcher. The link will direct you to the official CGWatcher page. The 'Check for Update' button will
  473.  
  474. check for program updates and if available, will provide a download link.
  475.  
  476.  
  477. SOURCE
  478.  
  479. I am working on releasing the source. I've been rewriting a lot (most) of the code as I have time getting closer to having something
  480.  
  481. presentable, only to get a ton of feature requests and turn to trying to add as much stuff as quickly as possible. I am trying to find a
  482.  
  483. balance between the two, and I will be open-sourcing it on GitHub. I honestly look forward to having others contribute and I've received a
  484.  
  485. lot of good ideas from users that indicate there is still a lot that could be done. I've created the repositories but still no ETA, sorry.
  486.  
  487. Future CGWatcher Repository: https://github.com/justinmilone/CGWatcher
  488. Future CGRemote Repository: https://github.com/justinmilone/CGRemote
  489.  
  490.  
  491. UPDATES
  492.  
  493. Starting with version 1.1.4, I've switched to the four-part version number, so actually 1.1.4.0. The last part (minor revision) will
  494.  
  495. be used to fix bugs quickly as I become aware of them. The CGWatcher download page will contain a link to the last major release (1.1.4)
  496.  
  497. and the last bugfix release (1.1.4.x) so anyone having a problem can check for an updated release that fixes it. Only major releases will
  498.  
  499. return that an update is available when you click the 'Check for Update' button. For bugfix releases, you'll have to check the download
  500.  
  501. page to see the latest version number.
  502.  
  503.  
  504. CONFIG FILE EDITOR [BETA]
  505.  
  506. The Config File Editor attempts to make editing your miner's configuration easier. To start, it displays the config file in a grid
  507.  
  508. allowing you to see all available settings and a description of each. Settings that can only be enabled or disabled will have a true or
  509.  
  510. false option. Settings that allow numbers only (not including lists of numbers) will only allow numbers. The 'Validate' button attempts to
  511.  
  512. check your settings for errors that may prevent the miner from starting or working correctly.
  513.  
  514. * The Config File Editor is in beta and is not yet perfect. It has undergone quite a bit of testing but with so many possible
  515.  
  516. configurations, it will take some user testing to get bugs worked out.
  517.  
  518. * Settings set to default values are not written to the config file when saving. They are also not converted to arguments, because
  519.  
  520. they are set to default values and don't need to be explicitly set as arguments.
  521.  
  522. * To add, edit, or remove pools, locate Pools in the config file grid. (There may be a Pools category hearing as well in Category view
  523.  
  524. mode), but you want the Pools that says '(Collection)' in the cell next to it. Click on the word '(Collection)' and a small '...' button
  525.  
  526. will appear in the cell. Click on this '...' button to open the pool window.
  527.  
  528. When editing pools, you can create names for them as well so they are more easily identifiable when editing them later on. Pool names
  529.  
  530. are saved inside the config file, but will not cause a problem with the miner. To change pool priorities, use the up and down arrows in
  531.  
  532. the pools window to move pools up and down the list. The top of the list is the first priority, the bottom of the list is last priority.
  533.  
  534. 'Name #' - You can name your config files so when you're using them in profiles they will be easier to access. Enter a name for the
  535.  
  536. config file in the Name textbox. Then when managing your profiles, you can select a Named config file from the Config File textbox drop-
  537.  
  538. down instead of needing to browse your computer for it. After clicking out of the Config File textbox, it will be converted to the config
  539.  
  540. file path automatically.
  541.  
  542. 'Ensure API is enabled upon saving' : If enabled, the API access needed by CGWatcher will always be enabled when saving the config
  543.  
  544. file, regardless if these settings were enabled in the grid. It will not affect other groups/IP address in the api-allow setting, it only
  545.  
  546. makes sure api-listen is enabled and that 127.0.0.1 is included in the W: group of api-allow.
  547.  
  548. The Config File Editor Menu
  549.  
  550. - File -> New : Create a new config file.
  551. - File -> Open : Open an existing config file.
  552. - File -> Save (As) : Save the current config file.
  553. - File -> Close : Close the Config File Editor.
  554. - Tools -> Import Settings -> From Config File... : select an existing config file to import settings from. The current settings will
  555.  
  556. be overwritten, but will not be permanent until you save the config file.
  557. -Tools -> Import Settings -> From Named Config File -> <select> : if you've set names for config files using the Name textbox in
  558.  
  559. Config File Editor, these config files can be loaded quickly by just this name, both in Config File Editor and in the Mining Profiles
  560.  
  561. window. This is the same as the previous menu item, but quicker and easier.
  562. - Tools -> Import Settings -> From Arguments : enter or paste miner arguments to have them converted to a config file. If you have a
  563.  
  564. config file open, you will be asked if you want to overwrite only the settings listed in the arguments, or if you want to create a new
  565.  
  566. config file using only the settings listed in the arguments.
  567. - Tools -> Export Settings -> To Arguments : converts the current config file to miner arguments.
  568. - Tools -> Open this Config File in Notepad : opens config file in Notepad. There is also a button next to the config file's Path to
  569.  
  570. open in Notepad.
  571. - Tools -> Validate this Config File : checks the config file for errors in the settings' formats or values.
  572.  
  573.  
  574.  
  575. CHANGELOG:
  576.  
  577. version 1.1.4 (5/12/2013)
  578. - Config File Editor added.
  579. - Mining profiles added.
  580. - Improved monitor and restarting ability.
  581. - Notify user of (3) consecutive failed miner starts.
  582. - Scheduled Mining bug fix.
  583. - Hashrate/temperature chart displays temps for up to 8 GPUs.
  584. - Restart if API access becomes read-only or is lost option.
  585. - Check total share count option now only checks accepted share count.
  586. - Some data added/removed from Status tab to keep up with mining changes. Discarded work now only shown on Report tab.
  587. - Created tabs for other devices, Device Tests on Tests tab to allow help in implementing support for these devices.
  588. - Fixed bug with window position saving on multiple monitors that caused CGWatcher to open in wrong monitor.
  589. - Introduces several smaller features and improvements, maybe some new bugs.
  590. - I'm so tired.
  591.  
  592. version 1.1.3
  593. - Scrypt mining detected automatically and hashrates are corrected accordingly.
  594. - Culture problems fixed where using a decimal instead of a comma produced incorrect hashrates.
  595. - Miner is restarted when sick or dead GPUs are detected, as restarting the GPU often fails.
  596. - Increased API buffer size to prevent chinese characters from appearing when miner returned a lot of data.
  597. - Ability to switch miners (CGMiner to BFGMiner or vice versa) handled in case that should ever happen.
  598. - Share percentages displayed and include stale and discarded in total to give more accurate percentages.
  599. - Check for Update button in the About tab added.
  600. - Restart when hashrate below X now fixed to require the hashrate to be below the value for three consecutive CGWatcher refreshes.
  601.  
  602. This number can be changed by changing the HashRateCounter value in CGWatcher.exe.ini. You can also now select whether this value is in
  603.  
  604. Kh/s, Mh/s, or Gh/s.
  605. - Miner restarts are improved. If CGWatcher lost full API access or the miner closes unexpectedly on the "restart" command, it is
  606.  
  607. correctly handled by CGWatcher.
  608. - Miner is given a startup grace period where it will not be restarted during in order to give it time to start mining. The default is
  609.  
  610. 180 seconds. This can be changed by changing RestartGracePeriod value in CGWatcher.exe.ini.
  611. - CGWatcher remembers window position including multi-monitor setups and monitor changes.
  612.  
  613. version 1.1.2
  614. - Form size increased to make room for more options.
  615. - Simple scheduling option added.
  616. - Minimize to system tray option added.
  617. - Select CGMiner window mode (normal, minimized, hidden) option added.
  618. - Editable options now marked in black text, read-only in gray text (in most cases).
  619. - Closing CGWatcher while CGMiner is running will prompt the user to confirm closing.
  620. - Added support for BFGMiner.
  621.  
  622.  
  623. THINGS TO DO:
  624. - Better support for pool problems
  625. - More statistics, information, and reports.
  626. - Remote monitoring and control using CGRemote. (in development)
  627. - FPGA and ASIC support. (working on it)
  628. - Setting Text Size in Windows to Medium (125%) or Large (150%) causes problems with interface (makes text labels too large).
  629. - Feature suggestions can be sent to Milone99k@gmail.com
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!