API-README 34 KB

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