MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"gapcontinue": "Wheelphone",
"continue": "gapcontinue||"
},
"warnings": {
"main": {
"*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
},
"revisions": {
"*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
}
},
"query": {
"pages": {
"20": {
"pageid": 20,
"ns": 0,
"title": "Ring",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "=Software=\n* [https://projects.gctronic.com/bracelet/antusb-gethistory-rev350-15.04.13.zip get history] (to be used with ant usb stick); just start the executable named ''antusb-gethistory.exe'' and follows the instructions; the transfer lasts about 90 seconds and produces a csv file ''history.csv''; the zip file contains also the driver needed to install the ant usb stick in Windows (look for ''ANT_USB_Stick_2.inf'').\n** [https://projects.gctronic.com/bracelet/History-format.doc history format]; beware that the current firmware version of the ring save also the data related to the accelerometer, this means that when two hearth rate values are saved in memory, also two values for the movement representation and two values for the energy representation are saved; thus in total 6 values in this sequence: ''HR HR MOVEMENT MOVEMENT ENERGY ENERGY''\n** the file ''history.xls'' can be used to parse the history\n* [https://projects.gctronic.com/bracelet/antusb-realtime-rev355-13.06.13.zip get realtime data] (to be used with ant usb stick); just start the exceutable ''antusb-realtime.exe'' and follows the instructions. The file saves the data every about 60 millisecond into the file ''data.csv''.\nThe ''peak to peak'' indicates whether the signal is good enough for the algorithm, the following image shows an example of a good signal (green):<br/>\n[http://www.gctronic.com/doc/images/antusb-realtime-good.jpg <img size=250>http://www.gctronic.com/doc/images/antusb-realtime-good.jpg</img>] <br/>\nThe following image instead shows a bad signal (red):<br/>\n[http://www.gctronic.com/doc/images/antusb-realtime-bad.jpg <img size=250>http://www.gctronic.com/doc/images/antusb-realtime-bad.jpg</img>]"
}
]
},
"37": {
"pageid": 37,
"ns": 0,
"title": "Ultra Wide Band Extension",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "=Development=\nThe following figure shows the architecture details during the development phase:<br/>\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/architecture-development.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/architecture-development.jpg\">]</span><br/>\n\nOn the nRF52832 the firmware is developed using the C API based on the PANS stack released by Decawave. The communication with the Elisa-3 robot is accomplished through I2C (the robot is the slave). The nRF52 is programmed/debugged through the SWD interface using an external nRF dev kit attached to the computer via USB. An additional UART is attached to the UWB module in order to get logging info.\n\n==Cabling==\nPower taken from the regulated 3V3 digital of Elisa.<br/>\nOn Elisa need to be added 2 simple female connectors, 2 and 3 pins. Painted in white on one side to help not crossing the cabling.<br/>\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/DWM1001cabling_1.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/DWM1001cabling_1.jpg\">]</span><br/>\n\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/ElisaUWB_1.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/ElisaUWB_1.jpg\">]</span><br/>\n\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/ElisaUWB_2.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/ElisaUWB_2.jpg\">]</span><br/>\n\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/ElisaUWBdebugger.jpg <img width=300 src=\"https://projects.gctronic.com/elisa3/uwb/ElisaUWBdebugger.jpg\">]</span>\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/ElisaUwbDevkitUart.jpg <img width=300 src=\"https://projects.gctronic.com/elisa3/uwb/ElisaUwbDevkitUart.jpg\">]</span><br/>\n\n=I2C protocol=\nThe nRF52 (master) writes all the actuators at once and read all the sensors data at once.<br/>\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/protocol-elisa-to-nrf52.jpg <img width=900 src=\"https://projects.gctronic.com/elisa3/uwb/protocol-elisa-to-nrf52.jpg\">]</span><br/>\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/protocol-nrf52-to-elisa.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/protocol-nrf52-to-elisa.jpg\">]</span><br/>\n\n=Implementation=\nAt the moment there are two firmwares for nRF52: one configures the module as a TAG node and the other one as an ANCHOR node.\nOnce the two modules are programmed, the [https://projects.gctronic.com/elisa3/uwb/DRTLS_Manager_R2.apk Android application] is used to put the two nodes in the same network.\nOnce configured, the TAG node will receive distances information and reflects the distance to the RGB led (intensity proportional to distance) while printing also this information to the UART.<br/>\nThe nRF52 poll the Elisa-3 robot at about 20 Hz in a separate thread.\n\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/architecture-implementation.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/architecture-implementation.jpg\">]</span><br/>\n\n=Source code=\nBoth the examples (<code>dwm-simple-anchor</code> and <code>dwm-simple-tag</code>) are based on the <code>dwm-simple</code> example that can be found in the [https://www.decawave.com/wp-content/uploads/2019/03/DWM1001_DWM1001-DEV_MDEK1001_Sources_and_Docs_v9.zip Decawave source code package].\n\nTo build the examples, clone the repo ([https://github.com/gctronic/dwm1001_anchor https://github.com/gctronic/dwm1001_anchor] and [https://github.com/gctronic/dwm1001_tag https://github.com/gctronic/dwm1001_tag]) inside the <code>DWM1001_DWM1001-DEV_MDEK1001_Sources_and_Docs_v9\\DWM1001\\Source_Code\\DWM1001_on_board_package\\dwm\\examples</code> directory. Then use the [https://www.segger.com/downloads/embedded-studio Segger Embedded Studio for ARM] to build the project.\n\nThe Elisa-3 firmware can be cloned from the repo [https://github.com/gctronic/elisa3_firmware_advanced https://github.com/gctronic/elisa3_firmware_advanced], <code>uwb</code> branch. The project can be built with [https://microchipdeveloper.com/atstudio:start Atmel Studio]. The selector must placed in position 15.\n\n=DFU=\nThere is the possibility to update the firmware of the nodes via OTA (Over The Air).<br/>\nFirst the initiator anchor is updated via BLE, then this anchor will automatically update the remaining network nodes via UWB.<br/>\n<span class=\"plainlinks\">[https://projects.gctronic.com/elisa3/uwb/architecture-dfu.jpg <img width=600 src=\"https://projects.gctronic.com/elisa3/uwb/architecture-dfu.jpg\">]</span><br/>\nFor more information refer to <code>DWM1001 Firmware API Guide</code>, chapter 4.3.<br/>\n<b>Not tested yet</b>.\n\n=Documentation=\n# [https://projects.gctronic.com/elisa3/uwb/DWM1001_Datasheet.pdf DWM1001_Datasheet.pdf]\n# [https://projects.gctronic.com/elisa3/uwb/DWM1001_Firmware_User_Guide.pdf DWM1001_Firmware_User_Guide.pdf]\n# [https://projects.gctronic.com/elisa3/uwb/DWM1001_Firmware_API_Guide.pdf DWM1001_Firmware_API_Guide.pdf]\n# [https://projects.gctronic.com/elisa3/uwb/DWM1001_Gateway_Quick_Deployment_Guide.pdf DWM1001_Gateway_Quick_Deployment_Guide.pdf]\n# [https://projects.gctronic.com/elisa3/uwb/System_Overview_and_Performance_for_DWM1001.pdf System_Overview_and_Performance_for_DWM1001.pdf]"
}
]
}
}
}
}