Specification and Bindings for Swift Binary Protocol
- Installing sbp2json, json2sbp, json2json and related tools
- Building / installing
- SBP Development Procedures
- SBP Protocol Specification
- JSON Schema Definitions
The Swift Navigation Binary Protocol (SBP) is a fast, simple, and minimal binary protocol for communicating with Swift devices. It is the native binary protocol used by the Piksi GPS receiver to transmit solutions, observations, status and debugging messages, as well as receive messages from the host operating system, such as differential corrections and the almanac.
This project provides language-agnostic specification and documentation for messages used with SBP, a compiler for generating message bindings, and client libraries in a variety of languages. This repository is organized into the following directory structure:
docs: Protocol documentation and message definitions.
spec: Machine readable protocol specification in YAML.
generator: Simple, template-based generator for different languages.
python: Python client and examples.
c: C client library and examples.
haskell: Haskell client and examples.
java: Java client library and examples.
rust: Rust client library and examples.
sbpjson: Tools for parsing SBP-JSON.
Except for the
generator, all of the above are generated and should not be modified directly.
Installing sbp2json, json2sbp, json2json and related tools
This repository also provides the following utilities for comprehending and inspecting SBP data:
sbp2json: converts SBP binary into a JSON representation, in which field names and values are expanded into JSON objects, common fields such as "message type" and "payload" are included as well.
json2sbp: uses the "message type", "payload" and related fields from an SBP JSON stream to reconstruct the binary representation.
json2json: some tools (notably the Swift GUI Console) produce abbreviated JSON logs with only common fields such as "message type" and "payload", the
json2jsontool expands these JSON objects to include fields specific the individual message.
To install a released version of these tools, visit the releases page and download an archive for your platform.
To install from source, you can use Rust's cargo tool (first install Rust), then run:
cargo install --git https://github.com/swift-nav/libsbp.git --bins
There's also a Haskell version available which can be installed by
stack install in the ./haskell directory of a checkout
of this repo (after installing
stack) or by visiting the
releases by and downloading an
sbp_tools_haskell archive. This variant of
the tools predate the Rust and Python versions, and also includes an
tool as well as a
Finally, a Python version of the
sbp2json tool exists, which is installable
on any platform that supports Python via pip, e.g.:
pip3 install sbp
The tool can then be invoked as follows:
python3 -m sbp2json <sbp.bin
The performance of the Python version is significantly slower than Rust and Haskell, but works on all platforms that Python itself supports.
Building / installing
Fetching the prebuilt image from DockerHub
The quickest method to get going is to just pull a prebuilt copy from DockerHub (no guarantees on freshness) by running the following on your command line:
docker run --rm -v $PWD:/mnt/workspace -i -t swiftnav/libsbp-build:2021-07-16 /bin/bash
This will mount your local copy of the libsbp repository onto the image.
Check this link for newer tags. Alternatively, you could run
docker run --rm -v $PWD:/mnt/workspace -i -t swiftnav/libsbp-build:latest-master /bin/bash
if you are facing issues with compilation and the tags are out of date as well.
Creating your own image
Dockerfile will create a docker image that contains all the
necessary dependencies to build libsbp. You can make a local image fresh from
this file by running
docker build as such:
docker build -t libsbp-build - <Dockerfile
Reading the Dockerfile from STDIN prevents docker from pulling in the whole
repostory into the build context (which is then immediately discarded anyway).
You can customize the UID of the user that's created with the docker image
by passing the desired
UID value to the build:
docker build -t libsbp-build --build-arg UID=1234 - <Dockerfile
You can then make this image operate on your local workspace like this:
docker run --rm -v $PWD:/mnt/workspace -i -t libsbp-build:latest /bin/bash
Using the docker image
Once in the image, simply type
make all to generate all the libsbp bindings.
This could take several hours to run. Alternately, the docker image will run
make all command by default, so you can kick off the
make all process
by simply running the following command:
docker run --rm -v $PWD:/mnt/workspace -i -t libsbp-build:2021-07-16
When you are finished, quit Docker so that it would not unnecessarily use up resources on your machine.
If you run into issues during the generation process, try running
Alternatively, you could recompile from a clean, newly-cloned libsbp repository
on your machine, which would minimize the chance of running into compilation
issues from an old build.
Installing from package managers
Some bindings are available on package managers:
Installing development Python versions
To install the Python binding from source (using pip) run the following command:
pip install 'file:///path/to/libsbp#subdirectory=python'
Or via setuptools directly:
cd /path/to/libsbp cd python python setup.py
Adding development version as a pip dependency
Run the following command:
pip install git+https://github.com/swift-nav/libsbp@<GIT_REVISION>#egg=sbp&subdirectory=python
Or add this to
Installing from source
You can build one binding at a time or update all at once:
are both valid. To see a list of all valid targets, run
Python version notes:
- by default the Python targets
make test-python(as well as
make all) run tests on all Python versions officially supported by the libsbp Python bindings, currently 2.7, 3.5, and 3.7, skipping any versions not installed. To run tests on just specific Python version(s), specify the
TOXENVenvironment variable, e.g.,
TOXENV=py27,py35 make python. Travis runs Python tests on all supported versions.
- by default the code generators are run on the system's (or virtual env's)
default Python interpreter. Currently Python versions 2.7, 3.5, and 3.7
are officially supported, other versions may or may not work. The generated
libsbp bindings should be the same on all supported Python versions. To use
a different version than your default Python interpreter, specify the
GENENVenvironment variable, e.g.,
GENENV=py27 make all(you must have that version of Python installed beforehand).
- to run both the generator and the Python tests on specific Python versions,
specify both envs, e.g.,
GENENV=py37 TOXENV=py27,py37 make python
SBP Development Procedures
SBP Protocol Specification
SBP consists of two pieces: (i) an over-the-wire message framing format and (ii) structured payload definitions. As of Version 1.0, the packet consists of a 6-byte binary header section, a variable-sized payload field, and a 16-bit CRC value. SBP uses the CCITT CRC16 (XMODEM implementation) for error detection.
Please see the docs for a full description of the packet structure and the message types. Developer documentatation for the language-specific sbp libraries is here. Please refer to the changelog for more information about the evolution of the library and its messages.
JSON Schema Definitions
Copyright © 2021 Swift Navigation
Distributed under MIT.