35
edits
Changes
Jump to navigation
Jump to search
mLine 13:
Line 13: + + Line 49:
Line 51: − + Line 82:
Line 84: − + Line 89:
Line 91: − − + Line 110:
Line 111: + Line 115:
Line 117: − + Line 129:
Line 131: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − TBD − TBD+ + + + + + + + + + + + + + Line 141:
Line 184: − + + + + + + + + + + + + + + + − Please also remember GoGo is originally based on Br-GoGo [2] and the intention is to eventually contribute back to that project so please also consider contributing to that project. Line 160:
Line 216: + +
no edit summary
The GoGo Activity is a Python version of the "Monitor" program (MS Windows) and builds upon the Br-GoGo project code [2]. Effort is under way to replicate most of the functionality of the original program and extend/improve certain areas. At the moment this XO version should be considered "Sugar-coated" rather than "Sugar-ized". The integrated nature of the program means breaking it down into distinct activities would detract from fluid navigation. However there are certain elements which could benefit from Sugar's Sharing and Journalling features and these will be addressed in time.
The GoGo Activity is a Python version of the "Monitor" program (MS Windows) and builds upon the Br-GoGo project code [2]. Effort is under way to replicate most of the functionality of the original program and extend/improve certain areas. At the moment this XO version should be considered "Sugar-coated" rather than "Sugar-ized". The integrated nature of the program means breaking it down into distinct activities would detract from fluid navigation. However there are certain elements which could benefit from Sugar's Sharing and Journalling features and these will be addressed in time.
Please see the sites listed under "Further Information" for GoGo-Board help and documentation. The main purpose of this Wiki page is to help you get started, familiarise you with the use of the GoGo-Board on the XO, specifically with the GoGo Activity and any issues you may encounter. Several other websites are listed at the end of this page, such as the SugarLab "Bugs" page which is where problems and feature requests should be submitted.
Please see the sites listed under "Further Information" for GoGo-Board help and documentation. The main purpose of this Wiki page is to help you get started, familiarise you with the use of the GoGo-Board on the XO, specifically with the GoGo Activity and any issues you may encounter. Several other websites are listed at the end of this page, such as the SugarLab "Bugs" page which is where problems and feature requests should be submitted.
Work continues on the GoGo Activity so please check back soon for news of new features.
Work continues on the GoGo Activity so please check back soon for news of new features.
On starting the GoGo activity the Console-Tab is displayed as shown below. In the top of the central region is the name and version of the activity. Please quote the version number if you encounter any problems (on SugarLabs Bugs site [4]). In the center is the image of the GoGo-Board itself, which will be larger is the next version. Below that is the current status "GoGo Connected"/"GoGo Disconnected" followed by "Connect"/"Disconnect" buttons. Also note the status-bar at the bottom of the screen which displays (sometimes transient) messages.
On starting the GoGo activity the Console-Tab is displayed as shown below. In the top of the central region is the name and version of the activity. Please quote the version number if you encounter any problems ([[Activity/Gogo#Suggestions and Bug Reports|Suggestions & Bug Reports]]). In the center is the image of the GoGo-Board itself, which will be larger is the next version. Below that is the current status "GoGo Connected"/"GoGo Disconnected" followed by "Connect"/"Disconnect" buttons. Also note the status-bar at the bottom of the screen which displays (sometimes transient) messages.
The GoGo-Board can store compiled Logo code which can be run by clicking the board's "run" button. Stored code can be run with/ without the board being connected to the XO (batteries or alternative power source are required when the board is untethered). Code is created, edited, saved, loaded and "uploaded" via the Logo Procedures tab shown in the image below. Code is compiled and uploaded (if no errors) in a single step when the "Upload" button is clicked. The "Messages" section will report any errors in the Logo code, in which case nothing should actually be uploaded to the board.
The GoGo-Board can store compiled Logo code which can be run by clicking the board's "run" button. Stored code can be run with/ without the board being connected to the XO (batteries or alternative power source are required when the board is untethered). Code is created, edited, saved, loaded and "downloaded" via the Logo Procedures tab shown in the image below. Code is compiled and uploaded (if no errors) in a single step when the "Download" button is clicked. The "Messages" section will report any errors in the Logo code, in which case nothing will actually be downloaded to the board.
[[File:gg-logo.png]]
[[File:gg-logo.png]]
</center>
</center>
===Data Upload Tab: Capture, Graph & Save===
===Data Upload Tab: Capture, Graph & Save===
Logo procedures can include commands to capture data, storing it on-board until uploaded to the XO. This can be done on the "Data Upload" tab (shown below) by clicking on the "Start" button (top left). The adjacent progress-bar and upload-count will update as data is uploaded. The data will be displayed in the "Recorded Data" section after the upload completes. Data can be displayed in Table or Graph format. In Table format the data can be formatted across a number of columns, which is required when data from more than one sensor/ source is interleaved. A sensor "type" can be selected to display the name & units and to apply calibration to for each column (see next section for how this information is created). Sensor Names & Units are used to display column headers. Name and Unit can be on the same line ("Name (Units)") or split on their own line (a two-line header). Data can be saved in Comma-Separated-Variables (CSV) format along with one/two headers (if selected).
Logo procedures can include commands to capture data and store it on-board until uploaded to the XO. This can be done on the "Data Upload" tab (shown below) by clicking on the "Start" button (top left). The adjacent progress-bar and upload-count will update as data is uploaded. The data will be displayed in the "Recorded Data" section after the upload completes. Data can be displayed in Table or Graph format. In Table format the data can be formatted across a number of columns, which is required when data from more than one sensor/ source is interleaved. A sensor "type" can be selected to display the name & units and to apply calibration to each column (see next section for how this information is created). Sensor Names & Units are used to display column headers. Name and Unit can be on the same line ("Name (Units)") or split on their own line (a two-line header). Data can be saved in Comma-Separated-Variables (CSV) format along with one/two lines of header (if "Headers" check-box is selected).
[[File:gg-upload-2.png]]
[[File:gg-upload-2.png]]
</center>
</center>
Sensor values, even for switches, fall in the range 0..1023. The Sensor-Lab is where particular sensor "types" can be created to calibrate these values, give more meaningful names and specify the units used (eg, Resistance, KOhms). Calibration data is defined by specifying a number of calibration "points" between which the application will interpolate to convert the raw sensor values. In this way a library can be created of commonly encountered sensor types and their calibration data can be assigned when monitoring sensors in the Console tab and when importing captured data in the "Data Upload" tab. In the image below you can see the list of sensors, the calibration points for the selected sensor and a (slightly rough) idea of the shape of the calibration curve in the graph. For easier creation and editing of calibration data the information for each sensor can be exported and imported in both Comma-Separated-Variables (CSV) format or custom "Sensor" format. Like-wise sensor information can imported in either of these formats.
Sensor values, even for switches, fall in the range 0..1023. The Sensor-Lab is where particular sensor "types" can be created to calibrate these values, give more meaningful names and specify the units used (eg, Resistance, KOhms). Calibration data is defined by specifying a number of calibration "points" between which the application will interpolate to convert the raw sensor values. In this way a library can be created of commonly encountered sensor types and their calibration data can be assigned when monitoring sensors in the Console tab and when importing captured data in the "Data Upload" tab. In the image below you can see the list of sensors, the calibration points for the selected sensor and a (slightly rough) idea of the shape of the calibration curve in the graph. For easier creation and editing of calibration data the information for each sensor can be exported and imported in both Comma-Separated-Variables (CSV) format or a custom "Sensor" format.
===Failing To Connect===
===Failing To Connect===
After checking the board is turned on, if connection fails on clicking "Connect" then try it a few more times. For reasons unknown at the moment it may take two or three attempts before connection succeeds. Still no luck? Turn off, turn on, try again. Still no luck? Now we need to identify the problem. The board needs to be recognised by the OS and a Linux device file mounted, the device file must be assigned a group in common with the user named "olpc" and the group must have read-write permissions on the device file. Here is how to check using the Terminal activity:
1. Shortly after plugging the device/ turning it on enter the following command:
[olpc@xo-73-22-91 ~]$ dmesg | tail -n 8
[22543.590117] usb 3-1: new full speed USB device using uhci_hcd and address 4
[22543.755225] usb 3-1: New USB device found, idVendor=0461, idProduct=0033
[22543.755238] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[22543.755249] usb 3-1: Product: SERIAL DEMO
[22543.755257] usb 3-1: Manufacturer: CCS
[22543.755708] usb 3-1: configuration #1 chosen from 1 choice
[22543.757578] cdc_acm 3-1:1.0: This device cannot do calls on its own. It is not a modem.
[22543.757797] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
2. The output above shows the GoGo-Board is assigned the "ttyACM0" device. The permissions of that device can be determined with the following:
[olpc@xo-73-22-91 ~]$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 2011-01-17 18:26 /dev/ttyACM0
3. Above we can see the device is a member of the "dialout" group, which has rw permissions. Now to check what groups user "olpc" is a member of:
[olpc@xo-73-22-91 ~]$ groups
olpc wheel uucp dialout video audio
...yep, user "olpc" is a member of "dialout". So in the above example all is well. If your results differ from these then please post a bug ([[Activity/Gogo#Suggestions and Bug Reports|Suggestions & Bug Reports]]). Note that some older XO/OS's use different device files and/or groups and it may need root access to fix any problem.
==Upcoming Changes==
==Upcoming Changes==
Improving existing features is an ongoing effort. These are new feature are currently being worked on:
* Logo commands reference on-screen
* Logo line numbering
* Logo syntax highlighting
* Strip-chart for sensor monitoring
The GoGo Activity is an open-source project and contributions in terms of code, graphics, testing and feedback are welcome. Bug reports should be submitted on SugarLab's Bug site [4]. Code and graphics should be contributed via the GIT repository [5]. Language translations should be via SugarLab's Pootle port-hole [6].
The GoGo Activity is an open-source project and contributions in terms of code, graphics, testing and feedback are welcome. Bug reports should be submitted on SugarLab's Bug site ([[Activity/Gogo#Suggestions and Bug Reports|Suggestions & Bug Reports]]). Code and graphics should be contributed via the GIT repository [5]. Language translations should be via SugarLab's Pootle port-hole [6].
Please also remember that the GoGo Activity is originally based on Br-GoGo [2] and the intention is to eventually contribute back to that project so please also consider contributing to that project.
==Suggestions and Bug Reports==
When reporting bugs please provide as much information as possible including version numbers for XO hardware, OS and Sugar.
* [https://bugs.sugarlabs.org/newticket?component=GoGo Click here to submit suggestions or report a GoGo bug]
* [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=GoGo Click here to view current GoGo suggestions & bugs]
[6] [http://translate.sugarlabs.org/ translations]
[6] [http://translate.sugarlabs.org/ translations]
[7] [https://www.planetseed.com/node/95150 SEED Community: GoGo Board Basics]