pyixblue
Python parser for the iXblue stdbin output protocol (versions 2 through 5).
stdbin is the binary navigation output of iXblue inertial systems. This package reassembles and decodes those frames. It does not open a socket or a serial port; pass in the bytes you receive over UDP, TCP, or serial.
The block layout and checksum follow the MIT-licensed ixblue_stdbin_decoder.
Install
From PyPI:
pip install pyixblue
For development, from a checkout (installs the package in editable mode along with the test dependencies):
uv sync
Usage
from pyixblue import StdBinDecoder
decoder = StdBinDecoder()
decoder.add_new_data(chunk) # bytes-like; a chunk may be a partial frame
while decoder.parse_next_frame(): # False when more bytes are needed
header = decoder.last_header
if header.message_type == "nav":
nav = decoder.last_nav # missing blocks are None
if nav.position is not None:
print(nav.position.latitude_deg, nav.position.longitude_deg)
else:
payload = decoder.last_answer
parse_next_frame raises StdBinError when a frame is recognized but its
protocol version or checksum is invalid. The decoder drops the bad version
byte, or the whole frame after a bad checksum, so the next call can resync.
Navigation, extended-navigation, and external-sensor blocks are present only
when their mask bit is set. INS algorithm and system status words are IntFlag
values (1 << bit), so they compare equal to the raw integer:
from pyixblue.models import InsAlgorithmStatus1
if nav.ins_algorithm_status is not None:
status = nav.ins_algorithm_status.status1
if InsAlgorithmStatus1.NAVIGATION in status:
print(hex(status))
Protocol
Supported output frames:
| Kind | Magic | Versions |
|---|---|---|
| Navigation | IX |
2, 3, 4, 5 |
| Answer | AN |
3, 4, 5 |
Multi-byte fields are big-endian. The checksum is the low 32 bits of the sum of
every preceding byte, stored as a big-endian uint32.
Version 3 adds the extended-navigation mask. Versions 4 and 5 add the
navigation-data size. The header also keeps the frame counter, which the
reference C++ header discards.
License
MIT. Sample frames under tests/fixtures/ were converted from the
ixblue_stdbin_decoder test logs (MIT, Copyright (c) 2019 iXblue SAS).
Metadata
Release files for pyixblue 0.9.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyixblue-0.9.2.tar.gz | 26.4 kB | With provenance | Details for pyixblue-0.9.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyixblue-0.9.2-py3-none-any.whl | Python 3 | none | any | Details for pyixblue-0.9.2-py3-none-any.whl |
Total release size: 39.4 kB
Release files / pyixblue-0.9.2.tar.gz
| Download URL | pyixblue-0.9.2.tar.gz |
|---|---|
| Size | 26.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c610a1a2060398e437861110d79be5009b164fb25eba1b34dd6f1b6a08f969e
|
|
BLAKE2b-256 checksum How to use checksums |
ebb6299967a58869029363d318f6d080b1cf0c703499375491f42baac5313ebb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / pyixblue-0.9.2-py3-none-any.whl
| Download URL | pyixblue-0.9.2-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaab2ee7f18883d2b6e7c92bbff83b13be358a8167dfa2bf3b2305824d7945d4
|
|
BLAKE2b-256 checksum How to use checksums |
8b288fd41c4e6a724b4ea8fd935059783038a036d244aa06cca5b9f5dbeb397b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for pyixblue 0.9.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pyixblue-0.9.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.