| 44 | |
| 45 | == startservices.sh == |
| 46 | |
| 47 | A very simple shell script can be used to make sure all of the ERSP required services are started. It is already located in the home folder and bin folder of both robots. Its contents are: |
| 48 | |
| 49 | {{{ |
| 50 | !/bin/bash |
| 51 | |
| 52 | /etc/init.d/evolution-drivers-boot start |
| 53 | /etc/init.d/evolution-firewire-boot start |
| 54 | /etc/init.d/evolution-ovt-boot start |
| 55 | /etc/init.d/evolution-peripherals-boot start |
| 56 | /etc/init.d/evolution-pwc-boot start |
| 57 | /etc/init.d/evolution-rcm-boot start |
| 58 | }}} |
| 59 | |
| 60 | All of these services *should* launch on startup, regardless of whether or not the hardware is connected at startup. However, occasionally something may fail, and this script is a quick way of ensuring that everything is running. |
| 61 | |
| 62 | = Python = |
| 63 | |
| 64 | Python scripting is an easy way to control the robots. Most of the work we did in Winlab was in python. There is no explicit documentation of available python commands. An easy way to figure out which commands are available is to browse the directory /opt/evolution_robotics/python/ersp/. Descriptions from the c++ api apply to the python commands with the same name. |
| 65 | |
| 66 | == neldermead.py == |