The current version of the repository at the time of writing is 5f55af0d.
Connect the SenTiBoard to a computer running Ubuntu Linux1
Make sure that the SenTiBoard is powered, either by attaching external power, or by adding the jumper USB_PWR
The SenTiBoard should show up as /dev/ttyACMx or /dev/ttyUSBx where x is a number. To see this number, check dmesg | tail
Make sure you have permissions to read from and write to the device. This is done by writing for example ls -la /dev/ttyACMx and verifying that you are a member of the group of the device.
The SenTiBoard should also show up in lsusb with vendor id 6666 and product id 4242.
Install the udev-rule from the sentiboard-utils repository: sudo cp ~/repo/sentiboard-utils/udev/80-sentiboard.rules /etc/udev/rules.d/
Disconnect and reconnect the SenTiBoard (or press the reset button) to trigger the udev-rule
The SenTiBoard should now show up as /dev/ttySentiboard00 (the configuration interface) and /dev/ttySentiboard02 (the data transfer interface).
Now you can use the SenTiBoard and the tools. To configure the SenTiBoard, use the command-line interface. If you have a sensor connected you can try to show the device's rate using testing/sentiboard_rate.py
Although not strictly required, you should create a directory named /opt/sentiboard and copy the loggers/logging-master.service to this directory. This is because the service can be started as a root user automatically at startup.2
Edit the logging-master.service to fit your installation. Especially the User, Group and ExecStart fields. By default, a screen session is started, but this can be altered if needed.
If you are using the default implementation of the logger, you need to make a symbolic link from the ~/repo/sentiboard/loggers to your home directory.
ln -s ~/repo/sentiboard-utils/loggers ~/loggers
If you want to add additional logging scripts, you can add them in log_master.sh. By default, the LOGGER_PROGRAMS variable. These should be scripts with the name somename.sh, and will automatically be started with a command line argument to a suggested logging directory (~/data/flight_XXX/somename)
Finally, enable the logger on boot by registering it with systemd:
sudo systemctl enable logging-master.service
The service can be started, stopped and restarted using sudo systemctl COMMAND logging-master and the default screen session can be attached by running screen -r log-master
If everything works correctly, the data from the SenTiBoard should be stored in the ~/data directory when the system boots.
Other OS-es than Ubuntu Linux will work, but it is more difficult to obtain a fixed name for the device. In Linux you can use an udev-rule to create a symbolic name, while OS X and Windows do not have an easy solution for this ↩
I believe that the service file is copied to a read-only location when it is enabled, but I recommend doing this step as a precaution. ↩