API-README 35 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105
  1. This README contains details about the BFGMiner RPC API
  2. It also includes some detailed information at the end,
  3. about using miner.php
  4. If you start BFGMiner with the "--api-listen" option, it will listen on a
  5. simple TCP/IP socket for single string API requests from the same machine
  6. running BFGMiner and reply with a string and then close the socket each time
  7. If you add the "--api-network" option, it will accept API requests from any
  8. network attached computer.
  9. You can only access the comands that reply with data in this mode.
  10. By default, you cannot access any privileged command that affects the miner -
  11. you will receive an access denied status message see --api-allow below.
  12. You can specify IP addresses/prefixes that are only allowed to access the API
  13. with the "--api-allow" option e.g. --api-allow W:192.168.0.1,10.0.0/24
  14. will allow 192.168.0.1 or any address matching 10.0.0.*, but nothing else
  15. IP addresses are automatically padded with extra '.0's as needed
  16. Without a /prefix is the same as specifying /32
  17. 0/0 means all IP addresses.
  18. The 'W:' on the front gives that address/subnet privileged access to commands
  19. that modify BFGMiner (thus all API commands)
  20. Without it those commands return an access denied status.
  21. See --api-groups below to define other groups like W:
  22. Privileged access is checked in the order the IP addresses were supplied to
  23. "--api-allow"
  24. The first match determines the privilege level.
  25. Using the "--api-allow" option overides the "--api-network" option if they
  26. are both specified
  27. With "--api-allow", 127.0.0.1 is not by default given access unless specified
  28. More groups (like the privileged group W:) can be defined using the
  29. --api-groups command
  30. Valid groups are only the letters A-Z (except R & W are predefined) and are
  31. not case sensitive
  32. The R: group is the same as not privileged access
  33. The W: group is (as stated) privileged access (thus all API commands)
  34. To give an IP address/subnet access to a group you use the group letter
  35. in front of the IP address instead of W: e.g. P:192.168.0/32
  36. An IP address/subnet can only be a member of one group
  37. A sample API group would be:
  38. --api-groups P:switchpool:enablepool:addpool:disablepool:removepool:poolpriority:*
  39. This would create a group 'P' that can do all current pool commands and all
  40. non-priviliged commands - the '*' means all non-priviledged commands
  41. Without the '*' the group would only have access to the pool commands
  42. Defining multiple groups example:
  43. --api-groups Q:quit:restart:*,S:save
  44. This would define 2 groups:
  45. Q: that can 'quit' and 'restart' as well as all non-priviledged commands
  46. S: that can only 'save' and no other commands
  47. The RPC API request can be either simple text or JSON.
  48. If the request is JSON (starts with '{'), it will reply with a JSON formatted
  49. response, otherwise it replies with text formatted as described further below.
  50. The JSON request format required is '{"command":"CMD","parameter":"PARAM"}'
  51. (though of course parameter is not required for all requests)
  52. where "CMD" is from the "Request" column below and "PARAM" would be e.g.
  53. the CPU/GPU number if required.
  54. An example request in both formats to set GPU 0 fan to 80%:
  55. gpufan|0,80
  56. {"command":"gpufan","parameter":"0,80"}
  57. The format of each reply (unless stated otherwise) is a STATUS section
  58. followed by an optional detail section
  59. From API version 1.7 onwards, reply strings in JSON and Text have the
  60. necessary escaping as required to avoid ambiguity - they didn't before 1.7
  61. For JSON the 2 characters '"' and '\' are escaped with a '\' before them
  62. For Text the 4 characters '|' ',' '=' and '\' are escaped the same way
  63. Only user entered information will contain characters that require being
  64. escaped, such as Pool URL, User and Password or the Config save filename,
  65. when they are returned in messages or as their values by the API
  66. For API version 1.4 and later:
  67. The STATUS section is:
  68. STATUS=X,When=NNN,Code=N,Msg=string,Description=string|
  69. STATUS=X Where X is one of:
  70. W - Warning
  71. I - Informational
  72. S - Success
  73. E - Error
  74. F - Fatal (code bug)
  75. When=NNN
  76. Standard long time of request in seconds
  77. Code=N
  78. Each unique reply has a unigue Code (See api.c - #define MSG_NNNNNN)
  79. Msg=string
  80. Message matching the Code value N
  81. Description=string
  82. This defaults to the BFGMiner version but is the value of --api-description
  83. if it was specified at runtime.
  84. For API version 1.10 and later:
  85. The list of requests - a (*) means it requires privileged access - and replies are:
  86. Request Reply Section Details
  87. ------- ------------- -------
  88. version VERSION CGMiner=BFGMiner version
  89. API=API version
  90. config CONFIG Some miner configuration information:
  91. GPU Count=N, <- the number of GPUs
  92. PGA Count=N, <- the number of PGAs
  93. CPU Count=N, <- the number of CPUs
  94. Pool Count=N, <- the number of Pools
  95. ADL=X, <- Y or N if ADL is compiled in the code
  96. ADL in use=X, <- Y or N if any GPU has ADL
  97. Strategy=Name, <- the current pool strategy
  98. Log Interval=N, <- log interval (--log N)
  99. Device Code=GPU ICA , <- spaced list of compiled devices
  100. OS=Linux/Apple/..., <- operating System
  101. Failover-Only=true/false | <- failover-only setting
  102. summary SUMMARY The status summary of the miner
  103. e.g. Elapsed=NNN,Found Blocks=N,Getworks=N,...|
  104. pools POOLS The status of each pool
  105. e.g. Pool=0,URL=http://pool.com:6311,Status=Alive,...|
  106. devs DEVS Each available GPU, PGA and CPU with their status
  107. e.g. GPU=0,Accepted=NN,MHS av=NNN,...,Intensity=D|
  108. Last Share Time=NNN, <- standand long time in seconds
  109. (or 0 if none) of last accepted share
  110. Last Share Pool=N, <- pool number (or -1 if none)
  111. Will not report PGAs if PGA mining is disabled
  112. Will not report CPUs if CPU mining is disabled
  113. devdetail DEVS Each available device with their fixed details
  114. e.g. GPU=0,Driver=opencl,Kernel=diablo,Model=...|
  115. gpu|N GPU The details of a single GPU number N in the same
  116. format and details as for DEVS
  117. pga|N PGA The details of a single PGA number N in the same
  118. format and details as for DEVS
  119. This is only available if PGA mining is enabled
  120. Use 'pgacount' or 'config' first to see if there are any
  121. cpu|N CPU The details of a single CPU number N in the same
  122. format and details as for DEVS
  123. This is only available if CPU mining is enabled
  124. Use 'cpucount' or 'config' first to see if there are any
  125. gpucount GPUS Count=N| <- the number of GPUs
  126. pgacount PGAS Count=N| <- the number of PGAs
  127. Always returns 0 if PGA mining is disabled
  128. cpucount CPUS Count=N| <- the number of CPUs
  129. Always returns 0 if CPU mining is disabled
  130. switchpool|N (*)
  131. none There is no reply section just the STATUS section
  132. stating the results of switching pool N to the
  133. highest priority (the pool is also enabled)
  134. The Msg includes the pool URL
  135. enablepool|N (*)
  136. none There is no reply section just the STATUS section
  137. stating the results of enabling pool N
  138. The Msg includes the pool URL
  139. addpool|URL,USR,PASS (*)
  140. none There is no reply section just the STATUS section
  141. stating the results of attempting to add pool N
  142. The Msg includes the pool URL
  143. Use '\\' to get a '\' and '\,' to include a comma
  144. inside URL, USR or PASS
  145. poolpriority|N,... (*)
  146. none There is no reply section just the STATUS section
  147. stating the results of changing pool priorities
  148. See usage below
  149. disablepool|N (*)
  150. none There is no reply section just the STATUS section
  151. stating the results of disabling pool N
  152. The Msg includes the pool URL
  153. removepool|N (*)
  154. none There is no reply section just the STATUS section
  155. stating the results of removing pool N
  156. The Msg includes the pool URL
  157. N.B. all details for the pool will be lost
  158. gpuenable|N (*)
  159. none There is no reply section just the STATUS section
  160. stating the results of the enable request
  161. gpudisable|N (*)
  162. none There is no reply section just the STATUS section
  163. stating the results of the disable request
  164. gpurestart|N (*)
  165. none There is no reply section just the STATUS section
  166. stating the results of the restart request
  167. gpuintensity|N,I (*)
  168. none There is no reply section just the STATUS section
  169. stating the results of setting GPU N intensity to I
  170. gpumem|N,V (*)
  171. none There is no reply section just the STATUS section
  172. stating the results of setting GPU N memoryclock to V MHz
  173. gpuengine|N,V (*)
  174. none There is no reply section just the STATUS section
  175. stating the results of setting GPU N clock to V MHz
  176. gpufan|N,V (*)
  177. none There is no reply section just the STATUS section
  178. stating the results of setting GPU N fan speed to V%
  179. gpuvddc|N,V (*)
  180. none There is no reply section just the STATUS section
  181. stating the results of setting GPU N vddc to V
  182. save|filename (*)
  183. none There is no reply section just the STATUS section
  184. stating success or failure saving the BFGMiner config
  185. to filename
  186. The filename is optional and will use the BFGMiner
  187. default if not specified
  188. quit (*) none There is no status section but just a single "BYE"
  189. reply before BFGMiner quits
  190. notify NOTIFY The last status and history count of each devices problem
  191. e.g. NOTIFY=0,Name=GPU,ID=0,Last Well=1332432290,...|
  192. privileged (*)
  193. none There is no reply section just the STATUS section
  194. stating an error if you do not have privileged access
  195. to the API and success if you do have privilege
  196. The command doesn't change anything in BFGMiner
  197. pgaenable|N (*)
  198. none There is no reply section just the STATUS section
  199. stating the results of the enable request
  200. You cannot enable a PGA if it's status is not WELL
  201. This is only available if PGA mining is enabled
  202. pgadisable|N (*)
  203. none There is no reply section just the STATUS section
  204. stating the results of the disable request
  205. This is only available if PGA mining is enabled
  206. devdetails DEVDETAILS Each device with a list of their static details
  207. This lists all devices including those not supported
  208. by the 'devs' command
  209. e.g. DEVDETAILS=0,Name=GPU,ID=0,Driver=opencl,...|
  210. restart (*) none There is no status section but just a single "RESTART"
  211. reply before BFGMiner restarts
  212. stats STATS Each device or pool that has 1 or more getworks
  213. with a list of stats regarding getwork times
  214. The values returned by stats may change in future
  215. versions thus would not normally be displayed
  216. Device drivers are also able to add stats to the
  217. end of the details returned
  218. check|cmd COMMAND Exists=Y/N, <- 'cmd' exists in this version
  219. Access=Y/N| <- you have access to use 'cmd'
  220. failover-only|true/false (*)
  221. none There is no reply section just the STATUS section
  222. stating what failover-only was set to
  223. coin COIN Coin mining information:
  224. Hash Method=sha256/scrypt,
  225. Current Block Time=N.N, <- 0 means none
  226. Current Block Hash=XXXX..., <- blank if none
  227. LP=true/false| <- LP is in use on at least 1 pool
  228. When you enable, disable or restart a GPU or PGA, you will also get Thread messages
  229. in the BFGMiner status window
  230. The 'poolpriority' command can be used to reset the priority order of multiple
  231. pools with a single command - 'switchpool' only sets a single pool to first priority
  232. Each pool should be listed by id number in order of preference (first = most
  233. preferred)
  234. Any pools not listed will be prioritised after the ones that are listed, in the
  235. priority order they were originally
  236. If the priority change affects the miner's preference for mining, it may switch
  237. immediately
  238. When you switch to a different pool to the current one (including by priority
  239. change), you will get a 'Switching to URL' message in the BFGMiner status
  240. windows
  241. Obviously, the JSON format is simply just the names as given before the '='
  242. with the values after the '='
  243. If you enable BFGMiner debug (-D or --debug) you will also get messages showing
  244. details of the requests received and the replies
  245. There are included 4 program examples for accessing the API:
  246. api-example.php - a php script to access the API
  247. usAge: php api-example.php command
  248. by default it sends a 'summary' request to the miner at 127.0.0.1:4028
  249. If you specify a command it will send that request instead
  250. You must modify the line "$socket = getsock('127.0.0.1', 4028);" at the
  251. beginning of "function request($cmd)" to change where it looks for BFGMiner
  252. API.java/API.class
  253. a java program to access the API (with source code)
  254. usAge is: java API command address port
  255. Any missing or blank parameters are replaced as if you entered:
  256. java API summary 127.0.0.1 4028
  257. api-example.c - a 'C' program to access the API (with source code)
  258. usAge: api-example [command [ip/host [port]]]
  259. again, as above, missing or blank parameters are replaced as if you entered:
  260. api-example summary 127.0.0.1 4028
  261. miner.php - an example web page to access the API
  262. This includes buttons and inputs to attempt access to the privileged commands
  263. See the end of this API-README for details of how to tune the display
  264. and also to use the option to display a multi-rig summary
  265. ----------
  266. Feature Changelog for external applications using the API:
  267. API V1.17 (BFGMiner v2.6.5)
  268. Added API commands:
  269. 'coin'
  270. ----------
  271. API V1.16 (BFGMiner v2.6.5)
  272. Added API commands:
  273. 'failover-only'
  274. Modified API commands:
  275. 'config' - include failover-only state
  276. ----------
  277. API V1.15 (BFGMiner v2.5.2)
  278. Added API commands:
  279. 'poolpriority'
  280. ----------
  281. API V1.14 (BFGMiner v2.5.0)
  282. Modified API commands:
  283. 'stats' - more icarus timing stats added
  284. 'notify' - include new device comms error counter
  285. The internal code for handling data was rewritten (~25% of the code)
  286. Completely backward compatible
  287. ----------
  288. API V1.13 (BFGMiner v2.4.4)
  289. Added API commands:
  290. 'check'
  291. Support was added to BFGMiner for API access groups with the --api-groups option
  292. It's 100% backward compatible with previous --api-access commands
  293. ----------
  294. API V1.12 (BFGMiner v2.4.3)
  295. Modified API commands:
  296. 'stats' - more pool stats added
  297. Support for the ModMinerQuad FPGA was added
  298. ----------
  299. API V1.11 (BFGMiner v2.4.2)
  300. Modified API commands:
  301. 'save' no longer requires a filename (use default if not specified)
  302. 'save' incorrectly returned status E (error) on success before.
  303. It now correctly returns S (success)
  304. ----------
  305. API V1.10 (BFGMiner v2.4.1)
  306. Added API commands:
  307. 'stats'
  308. N.B. the 'stats' command can change at any time so any specific content
  309. present should not be relied upon.
  310. The data content is mainly used for debugging purposes or hidden options
  311. in BFGMiner and can change as development work requires
  312. Modified API commands:
  313. 'pools' added "Last Share Time"
  314. ----------
  315. API V1.9 (BFGMiner v2.4.0)
  316. Added API commands:
  317. 'restart'
  318. Modified API commands:
  319. 'notify' corrected invalid JSON
  320. ----------
  321. API V1.8 (BFGMiner v2.3.5)
  322. Added API commands:
  323. 'devdetails'
  324. Support for the ZTex FPGA was added
  325. ----------
  326. API V1.8-pre (BFGMiner v2.3.4)
  327. Added API commands:
  328. 'devdetail'
  329. ----------
  330. API V1.7 (BFGMiner v2.3.4)
  331. Added API commands:
  332. 'removepool'
  333. Modified API commands:
  334. 'pools' added "User"
  335. From API version 1.7 onwards, reply strings in JSON and Text have the
  336. necessary escaping as required to avoid ambiguity
  337. For JSON the 2 characters '"' and '\' are escaped with a '\' before them
  338. For Text the 4 characters '|' ',' '=' and '\' are escaped the same way
  339. ----------
  340. API V1.6 (cgminer v2.3.2)
  341. Added API commands:
  342. 'pga'
  343. 'pgaenable'
  344. 'pgadisable'
  345. 'pgacount'
  346. Modified API commands:
  347. 'devs' now includes Icarus and Bitforce FPGA devices
  348. 'notify' added "*" to the front of the name of all numeric error fields
  349. 'config' correct "Log Interval" to use numeric (not text) type for JSON
  350. Support for Icarus and Bitforce FPGAs was added
  351. ----------
  352. API V1.5 was not released
  353. ----------
  354. API V1.4 (Kano's interim release of cgminer v2.3.1)
  355. Added API commands:
  356. 'notify'
  357. Modified API commands:
  358. 'config' added "Device Code" and "OS"
  359. Added "When" to the STATUS reply section of all commands
  360. ----------
  361. API V1.3 (cgminer v2.3.1-2)
  362. Added API commands:
  363. 'addpool'
  364. Modified API commands:
  365. 'devs'/'gpu' added "Total MH" for each device
  366. 'summary' added "Total MH"
  367. ----------
  368. API V1.2 (cgminer v2.3.0)
  369. Added API commands:
  370. 'enablepool'
  371. 'disablepool'
  372. 'privileged'
  373. Modified API commands:
  374. 'config' added "Log Interval"
  375. Starting with API V1.2, any attempt to access a command that requires
  376. privileged security, from an IP address that does not have privileged
  377. security, will return an "Access denied" Error Status
  378. ----------
  379. API V1.1 (cgminer v2.2.4)
  380. There were no changes to the API commands in cgminer v2.2.4,
  381. however support was added to cgminer for IP address restrictions
  382. with the --api-allow option
  383. ----------
  384. API V1.1 (cgminer v2.2.2)
  385. Prior to V1.1, devs/gpu incorrectly reported GPU0 Intensity for all GPUs
  386. Modified API commands:
  387. 'devs'/'gpu' added "Last Share Pool" and "Last Share Time" for each device
  388. ----------
  389. API V1.0 (cgminer v2.2.0)
  390. Remove default CPU support
  391. Added API commands:
  392. 'config'
  393. 'gpucount'
  394. 'cpucount'
  395. 'switchpool'
  396. 'gpuintensity'
  397. 'gpumem'
  398. 'gpuengine'
  399. 'gpufan'
  400. 'gpuvddc'
  401. 'save'
  402. ----------
  403. API V0.7 (cgminer v2.1.0)
  404. Initial release of the API in the main cgminer git
  405. Commands:
  406. 'version'
  407. 'devs'
  408. 'pools'
  409. 'summary'
  410. 'gpuenable'
  411. 'gpudisable'
  412. 'gpurestart'
  413. 'gpu'
  414. 'cpu'
  415. 'gpucount'
  416. 'cpucount'
  417. 'quit'
  418. ----------------------------------------
  419. miner.php
  420. =========
  421. miner.php is a PHP based interface to the BFGMiner RPC API
  422. (referred to simply as the API below)
  423. It can show rig details, summaries and input fields to allow you to change
  424. BFGMiner
  425. You can also create custom summary pages with it
  426. It has two levels to the security:
  427. 1) BFGMiner can be configured to allow or disallow API access and access level
  428. security for miner.php
  429. 2) miner.php can be configured to allow or disallow privileged BFGMiner
  430. access, if BFGMiner is configured to allow privileged access for miner.php
  431. ---------
  432. To use miner.php requires a web server with PHP
  433. Basics: On xubuntu 11.04, to install apache2 and php, the commands are:
  434. sudo apt-get install apache2
  435. sudo apt-get install php5
  436. sudo /etc/init.d/apache2 reload
  437. On Fedora 17:
  438. yum install httpd php
  439. systemctl restart httpd.service
  440. systemctl enable httpd.service --system
  441. On windows there are a few options.
  442. Try one of these (I've never used either one)
  443. http://www.apachefriends.org/en/xampp.html
  444. http://www.wampserver.com/en/
  445. ---------
  446. The basic BFGMiner option to enable the API is:
  447. --api-listen
  448. or in your bfgminer.conf
  449. "api-listen" : true,
  450. (without the ',' on the end if it is the last item)
  451. If the web server is running on the BFGMiner computer, the above
  452. is the only change required to give miner.php basic access to
  453. the BFGMiner API
  454. -
  455. If the web server runs on a different computer to BFGMiner,
  456. you will also need to tell BFGMiner to allow the web server
  457. to access BFGMiner's API and tell miner.php where BFGMiner is
  458. Assuming a.b.c.d is the IP address of the web server, you
  459. would add the following to BFGMiner:
  460. --api-listen --api-allow a.b.c.d
  461. or in your bfgminer.conf
  462. "api-listen" : true,
  463. "api-allow" : "a.b.c.d",
  464. to tell BFGMiner to give the web server read access to the API
  465. You also need to tell miner.php where BFGMiner is.
  466. Assuming BFGMiner is at IP address e.f.g.h, then you would
  467. edit miner.php and change the line
  468. $rigs = array('127.0.0.1:4028');
  469. to
  470. $rigs = array('e.f.g.h:4028');
  471. See --api-network or --api-allow for more access details
  472. and how to give write access
  473. ---------
  474. Once you have a web server with PHP running
  475. copy your miner.php to the main web folder
  476. On Xubuntu 11.04
  477. /var/www/
  478. On Fedora 17
  479. /var/www/html/
  480. On Windows
  481. see your windows Web/PHP documentation
  482. Assuming the IP address of the web server is a.b.c.d
  483. Then in your web browser go to:
  484. http://a.b.c.d/miner.php
  485. Done :)
  486. ---------
  487. The rest of this documentation deals with the more complex
  488. functions of miner.php, using myminer.php, creaing custom
  489. summaries and displaying multiple BFGMiner rigs
  490. ---------
  491. If you create a file called myminer.php in the same web folder
  492. where you put miner.php, miner.php will load it when it runs
  493. This is useful, to put any changes you need to make to miner.php
  494. instead of changing miner.php
  495. Thus if you update/get a new miner.php, you won't lose the changes
  496. you have made if you put all your changes in myminer.php
  497. (and don't change miner.php at all)
  498. A simple example myminer.php that defines 2 rigs
  499. (that I will keep referring to further below) is:
  500. <?php
  501. #
  502. $rigs = array('192.168.0.100:4028:A', '192.168.0.102:4028:B');
  503. #
  504. ?>
  505. Changes in myminer.php superscede what is in miner.php
  506. However, this is only valid for variables in miner.php before the
  507. 2 lines where myminer.php is included by miner.php:
  508. if (file_exists('myminer.php'))
  509. include_once('myminer.php');
  510. Every variable in miner.php above those 2 lines, can be changed by
  511. simply defining them in your myminer.php
  512. So although miner.php originally contains the line
  513. $rigs = array('127.0.0.1:4028');
  514. if you created the example myminer.php given above, it would actually
  515. change the value of $rigs that is used when miner.php is running
  516. i.e. you don't have to remove or comment out the $rigs line in miner.php
  517. It will be superceded by myminer.php
  518. ---------
  519. The example.php above also shows how to define more that one rig to
  520. be shown my miner.php
  521. Each rig string is 2 or 3 values seperated by colons ':'
  522. They are simply an IP address or host name, followed by the
  523. port number (usually 4028) and an optional Name string
  524. miner.php displays rig buttons that will show the defails of a single
  525. rig when you click on it - the button shows either the rig number,
  526. or the 'Name' string if you provide it
  527. PHP arrays contain each string seperated by a comma, but no comma after
  528. the last one
  529. So an example for 3 rigs would be:
  530. $rigs = array('192.168.0.100:4028:A', '192.168.0.102:4028:B', '192.168.0.110:4028:C');
  531. Of course each of the rigs listed would also have to have the API
  532. running and be set to allow the web server to access the API - as
  533. explained before
  534. ---------
  535. So basically, any variable explained below can be put in myminer.php
  536. if you wanted to set it to something different to it's default value
  537. and did not want to change miner.php itself every time you updated it
  538. Below is each variable that can be changed and an explanation of each
  539. ---------
  540. Default:
  541. $dfmt = 'H:i:s j-M-Y \U\T\CP';
  542. Define the date format used to print full length dates
  543. If you get the string 'UTCP' on the end of your dates shown, that
  544. means you are using an older version of PHP and you can instead use:
  545. $dfmt = 'H:i:s j-M-Y \U\T\CO';
  546. The PHP documentation on the date format is here:
  547. http://us.php.net/manual/en/function.date.php
  548. ---------
  549. Default:
  550. $title = 'Mine';
  551. Web page title
  552. If you know PHP you can of course use code to define it e.g.
  553. $title = 'My Rig at: '.date($dfmt);
  554. Which would set the web page title to something like:
  555. My Rig at: 10:34:00 22-Aug-2012 UTC+10:00
  556. ---------
  557. Default:
  558. $readonly = false;
  559. Set $readonly to true to force miner.php to be readonly
  560. This means it won't allow you to change BFGMiner even if the RPC API
  561. options allow it to
  562. If you set $readonly to false then it will check BFGMiner 'privileged'
  563. and will show input fields and buttons on the single rig page
  564. allowing you to change devices, pools and even quit or restart
  565. BFGMiner
  566. However, if the 'privileged' test fails, the code will set $readonly to
  567. true
  568. ---------
  569. Default:
  570. $notify = true;
  571. Set $notify to false to NOT attempt to display the notify command
  572. table of data
  573. Set $notify to true to attempt to display the notify command on
  574. the single rig page
  575. If your older version of BFGMiner returns an 'Invalid command'
  576. coz it doesn't have notify - it just shows the error status table
  577. ---------
  578. Default:
  579. $checklastshare = true;
  580. Set $checklastshare to true to do the following checks:
  581. If a device's last share is 12x expected ago then display as an error
  582. If a device's last share is 8x expected ago then display as a warning
  583. If either of the above is true, also display the whole line highlighted
  584. This assumes shares are 1 difficulty shares
  585. Set $checklastshare to false to not do the above checks
  586. 'expected' is calculated from the device MH/s value
  587. So for example, a device that hashes at 380MH/s should (on average)
  588. find a share every 11.3s
  589. If the last share was found more than 11.3 x 12 seconds (135.6s) ago,
  590. it is considered an error and highlighted
  591. If the last share was found more than 11.3 x 8 seconds (90.4s) ago,
  592. it is considered a warning and highlighted
  593. The default highlighting is very subtle
  594. ---------
  595. Default:
  596. $poolinputs = false;
  597. Set $poolinputs to true to show the input fields for adding a pool
  598. and changing the pool priorities on a single rig page
  599. However, if $readonly is true, it will not display them
  600. ---------
  601. Default:
  602. $rigs = array('127.0.0.1:4028');
  603. Set $rigs to an array of your BFGMiner rigs that are running
  604. format: 'IP:Port' or 'Host:Port' or 'Host:Port:Name'
  605. If you only have one rig, it will just show the detail of that rig
  606. If you have more than one rig it will show a summary of all the rigs
  607. with buttons to show the details of each rig -
  608. the button contents will be 'Name' rather than rig number, if you
  609. specify 'Name'
  610. e.g. $rigs = array('127.0.0.1:4028','myrig.com:4028:Sugoi');
  611. ---------
  612. Default:
  613. $rigtotals = true;
  614. $forcerigtotals = false;
  615. Set $rigtotals to true to display totals on the single rig page
  616. 'false' means no totals (and ignores $forcerigtotals)
  617. If $rigtotals is true, all data is also right aligned
  618. With false, it's as before, left aligned
  619. This option is just here to allow people to set it to false
  620. if they prefer the old non-total display when viewing a single rig
  621. Also, if there is only one line shown in any section, then no
  622. total will be shown (to save screen space)
  623. You can force it to always show rig totals on the single rig page,
  624. even if there is only one line, by setting $forcerigtotals = true;
  625. ---------
  626. Default:
  627. $socksndtimeoutsec = 10;
  628. $sockrcvtimeoutsec = 40;
  629. The numbers are integer seconds
  630. The defaults should be OK for most cases
  631. However, the longer SND is, the longer you have to wait while
  632. php hangs if the target BFGMiner isn't runnning or listening
  633. RCV should only ever be relevant if BFGMiner has hung but the
  634. API thread is still running, RCV would normally be >= SND
  635. Feel free to increase SND if your network is very slow
  636. or decrease RCV if that happens often to you
  637. Also, on some windows PHP, apparently the $usec is ignored
  638. (so usec can't be specified)
  639. ---------
  640. Default:
  641. $hidefields = array();
  642. List of fields NOT to be displayed
  643. You can use this to hide data you don't want to see or don't want
  644. shown on a public web page
  645. The list of sections are:
  646. SUMMARY, POOL, PGA, GPU, NOTIFY, CONFIG, DEVDETAILS, DEVS
  647. See the web page for the list of field names (the table headers)
  648. It is an array of 'SECTION.Field Name' => 1
  649. This example would hide the slightly more sensitive pool information:
  650. Pool URL and pool username:
  651. $hidefields = array('POOL.URL' => 1, 'POOL.User' => 1);
  652. If you just want to hide the pool username:
  653. $hidefields = array('POOL.User' => 1);
  654. ---------
  655. Default:
  656. $ignorerefresh = false;
  657. $changerefresh = true;
  658. $autorefresh = 0;
  659. Auto-refresh of the page (in seconds) - integers only
  660. $ignorerefresh = true/false always ignore refresh parameters
  661. $changerefresh = true/false show buttons to change the value
  662. $autorefresh = default value, 0 means dont auto-refresh
  663. ---------
  664. Default:
  665. $placebuttons = 'top';
  666. Where to place the Refresh, Summary, Custom Pages, Quit, etc. buttons
  667. Valid values are: 'top' 'bot' 'both'
  668. anything else means don't show them - case sensitive
  669. ---------
  670. Default:
  671. $miner_font_family = 'verdana,arial,sans';
  672. $miner_font_size = '13pt';
  673. Change these to set the font and font size used on the web page
  674. ---------
  675. Default:
  676. $colouroverride = array();
  677. Use this to change the web page colour scheme
  678. See $colourtable in miner.php for the list of possible names to change
  679. Simply put in $colouroverride, just the colours you wish to change
  680. e.g. to change the colour of the header font and background
  681. you could do the following:
  682. $colouroverride = array(
  683. 'td.h color' => 'green',
  684. 'td.h background' => 'blue'
  685. );
  686. ---------
  687. Default:
  688. $allowcustompages = true;
  689. Should we allow custom pages?
  690. (or just completely ignore them and don't display the buttons)
  691. ---------
  692. OK this part is more complex: Custom Summary Pages
  693. A custom summary page in an array of 'section' => array('FieldA','FieldB'...)
  694. The section defines what data you want in the summary table and the Fields
  695. define what data you want shown from that section
  696. Standard sections are:
  697. SUMMARY, POOL, PGA, GPU, NOTIFY, CONFIG, DEVDETAILS, DEVS, STATS, COIN
  698. Fields are the names as shown on the headers on the normal pages
  699. Fields can be 'name=new name' to display 'name' with a different heading
  700. 'new name'
  701. There are also now joined sections:
  702. SUMMARY+POOL, SUMMARY+DEVS, SUMMARY+CONFIG, DEVS+NOTIFY, DEVS+DEVDETAILS
  703. SUMMARY+COIN
  704. These sections are an SQL join of the two sections and the fields in them
  705. are named section.field where section. is the section the field comes from
  706. See the example further down
  707. Also note:
  708. - empty tables are not shown
  709. - empty columns (e.g. an unknown field) are not shown
  710. - missing field data shows as blank
  711. - the field name '*' matches all fields except in joined sections
  712. (useful for STATS and COIN)
  713. There are 2 hard coded sections:
  714. DATE - displays a date table like at the start of 'Summary'
  715. RIGS - displays a rig table like at the start of 'Summary'
  716. Each custom summary requires a second array, that can be empty, listing fields
  717. to be totaled for each section
  718. If there is no matching total data, no total will show
  719. ---------
  720. Looking at the Mobile example:
  721. $mobilepage = array(
  722. 'DATE' => null,
  723. 'RIGS' => null,
  724. 'SUMMARY' => array('Elapsed', 'MHS av', 'Found Blocks=Blks',
  725. Accepted', 'Rejected=Rej', 'Utility'),
  726. 'DEVS+NOTIFY' => array('DEVS.Name=Name', 'DEVS.ID=ID', 'DEVS.Status=Status',
  727. 'DEVS.Temperature=Temp', 'DEVS.MHS av=MHS av',
  728. 'DEVS.Accepted=Accept', 'DEVS.Rejected=Rej',
  729. 'DEVS.Utility=Utility', 'NOTIFY.Last Not Well=Not Well'),
  730. 'POOL' => array('POOL', 'Status', 'Accepted', 'Rejected=Rej', 'Last Share Time'));
  731. $mobilesum = array(
  732. 'SUMMARY' => array('MHS av', 'Found Blocks', 'Accepted', 'Rejected', 'Utility'),
  733. 'DEVS+NOTIFY' => array('DEVS.MHS av', 'DEVS.Accepted', 'DEVS.Rejected', 'DEVS.Utility'),
  734. 'POOL' => array('Accepted', 'Rejected'));
  735. $customsummarypages = array('Mobile' => array($mobilepage, $mobilesum));
  736. This will show 5 tables (according to $mobilepage)
  737. Each table will have the chosen details for all the rigs specified in $rigs
  738. DATE
  739. A single box with the web server's current date and time
  740. RIGS
  741. A table of the rigs: description, time, versions etc
  742. SUMMARY
  743. This will use the API 'summary' command and show the selected fields:
  744. Elapsed, MHS av, Found Blocks, Accepted, Rejected and Utility
  745. However, 'Rejected=Rej' means that the header displayed for the 'Rejected'
  746. field will be 'Rej', instead of 'Rejected' (to save space)
  747. Same for 'Found Blocks=Blks' - to save space
  748. DEVS+NOTIFY
  749. This will list each of the devices on each rig and display the list of
  750. fields as shown
  751. It will also include the 'Last Not Well' field from the 'notify' command
  752. so you know when the device was last not well
  753. You will notice that you need to rename each field e.g. 'DEVS.Name=Name'
  754. since each field name in the join between DEVS and NOTIFY is actually
  755. section.fieldname, not just fieldname
  756. The join code automatically adds 2 fields to each GPU device: 'Name' and 'ID'
  757. They don't exist in the API 'devs' output but I can correctly calculate
  758. them from the GPU device data
  759. These two fields are used to join DEVS to NOTIFY i.e. find the NOTIFY
  760. record that has the same Name and ID as the DEVS record and join them
  761. POOL
  762. This will use the API 'pools' command and show the selected fields:
  763. POOL, Status, Accepted, Rejected, Last Share Time
  764. Again, I renamed the 'Rejected' field using 'Rejected=Rej', to save space
  765. $mobilesum lists the sections and fields that should have a total
  766. You can't define them for 'DATE' or 'RIGS' since they are hard coded tables
  767. The example given:
  768. SUMMARY
  769. Show a total at the bottom of the columns for:
  770. MHS av, Found Blocks, Accepted, Rejected, Utility
  771. Firstly note that you use the original name i.e. for 'Rejected=Rej'
  772. you use 'Rejected', not 'Rej' and not 'Rejected=Rej'
  773. Secondly note that it simply adds up the fields
  774. If you ask for a total of a string field you will get the numerical
  775. sum of the string data
  776. DEVS+NOTIFY
  777. Simply note in this join example that you must use the original field
  778. names which are section.fieldname, not just fieldname
  779. POOL
  780. Show a total at the bottom of the columns for:
  781. Accepted and Rejected
  782. Again remember to use the original field name 'Rejected'