Baltech SDK
Installation
pip install baltech-sdk
Usage
from baltech_sdk import Brp, UsbHid
# Sample code for GetInfo
with Brp(UsbHid()) as brp:
print(brp.Sys_GetInfo())
# This is a shortcut for:
io = UsbHid()
brp = Brp(io, open=False)
brp.open()
print(brp.Sys_GetInfo())
brp.close()
A complete reference of the supported commands can be found here.
Supported IO protocols
from baltech_sdk import Brp, UsbHid, RS232
# USB HID autodetect connected reader
brp = Brp(UsbHid())
# USB HID by serialnumber
brp = Brp(UsbHid(serialnumber=99999999))
# Serial with (optional) custom settings
brp = Brp(RS232("COM1", baudrate=115200, parity=b"N"))
Reader Update
from baltech_sdk import Brp, UsbHid, ReaderUpdater
with Brp(UsbHid(), open=True) as brp:
updater = ReaderUpdater.from_path("firmware.bf3")
# simple upload
updater.run(brp)
# upload with progress
for progress in updater.iter(brp):
print(f"{progress.progress:.0%} ({progress.transferred_bytes} bytes)")
Access Reader Configuration
from baltech_sdk import Config
cfg_src = {(0x0201, 0x02): b'\x01'} # instead of a confDict also a brp object
# can be passed to modify reader's
# configuration directly
cfg = Config(cfg_src)
# set value
cfg.Device_Boot_StartAutoreadAtPowerup("EnableOnce")
# get value
print(cfg.Device_Boot_StartAutoreadAtPowerup.get())
# delete value
cfg.Device_Boot_StartAutoreadAtPowerup.delete()
Templates and BaltechScripts
from baltech_sdk import Config, Template, BaltechScript, TemplateFilter
confdict = {}
cfg = Config(confdict)
cfg.Scripts_Events_OnAccepted(
BaltechScript()
.ToggleInverted("RedLed", RepeatCount=3, Delay=20)
.Toggle("GreenLed", RepeatCount=1, Delay=20)
.DefaultAction()
)
cfg.Autoread_Rule_Template(
0,
Template()
.Static(b"SNR:")
.Serialnr(TemplateFilter(BinToAscii=True, Unpack=True, BinToBcd=True))
)
print(confdict)
Linux or macOS
To use baltech-sdk under Linux or macOS you need to build your own binary of the BaltechSDK and manually set the path to your binary.
from pathlib import Path
from baltech_sdk import set_brp_lib_path
set_brp_lib_path(Path("path/to/brp_lib"))
Custom protocols
Implement your own protocol in Python by subclassing CustomProtocol. Override
only the methods you need; not overriding a method makes it a transparent
passthrough to the layer below. Add the role marker (IoProtocol /
CryptoProtocol) matching where the protocol is meant to be mounted.
A byte-stream I/O transport (here over a TCP socket) overrides send_frame
and recv_frame. recv_frame drives the framing loop: missing_bytes_cb(chunk)
appends chunk and returns how many bytes are still missing (0 = frame complete):
import socket
from baltech_sdk import Brp, CustomProtocol, IoProtocol
from brp_lib.err import BrpTimeoutError
class TcpIo(CustomProtocol, IoProtocol):
INTERFACE_NAME = "IP" # log filename "{interface}-{instance}.html"
def __init__(self, host, port):
super().__init__()
self.host, self.port = host, port
@property
def instance_id(self): # the "{instance}" half (e.g. "IP-192.168.0.42.html")
return self.host
def open(self):
super().open()
self.sock = socket.create_connection((self.host, self.port), timeout=5)
def close(self):
self.sock.close()
super().close()
def send_frame(self, data):
self.sock.sendall(data)
def recv_frame(self, timeout, missing_bytes_cb):
self.sock.settimeout(None if timeout is None else timeout / 1000)
chunk = b""
while True:
n = missing_bytes_cb(chunk) # bytes still missing (0 = complete)
if n == 0:
break
try:
chunk = self.sock.recv(n)
except (socket.timeout, TimeoutError):
raise BrpTimeoutError()
if not chunk:
raise BrpTimeoutError()
with Brp(TcpIo("192.168.0.42", 9999)) as brp:
print(brp.Sys_GetInfo())
(A message/datagram transport that reads whole frames overrides
recv_any_frame(timeout) instead of recv_frame.)
A middle layer transforms whole frames and forwards them to the layer below
via self.base (here a toy obfuscation in the crypto slot). It can also run a
handshake when the stack is opened by extending open: super().open()
brings up the layer below, then exchange frames over it; raise a BrpError
to abort (the stack stays closed):
from baltech_sdk import Brp, UsbHid, CustomProtocol, CryptoProtocol, Layer
from brp_lib.err import OpenIOError
class XorLayer(CustomProtocol, CryptoProtocol):
def open(self):
super().open() # opens the layer below first
self.base.send_frame(b"AUTH-REQ") # negotiated in clear (no XOR)
if self.base.recv_any_frame(2000) != b"AUTH-OK":
raise OpenIOError("handshake rejected")
def send_frame(self, data):
self.base.send_frame(bytes(b ^ 0x5A for b in data))
def recv_any_frame(self, timeout=None):
return bytes(b ^ 0x5A for b in self.base.recv_any_frame(timeout))
brp = Brp(UsbHid())
brp.set_layer(Layer.CRYPTO, XorLayer())
brp.open() # runs XorLayer.open()
For open/close, extend with super() as usual — like every implementor of
an open callback (in C too), an override is responsible for bringing up the
layer below itself, and super().open() does exactly that (forget it and the
handshake send_frame fails on the still-closed base). For data methods,
forward through self.base, never super() — their base implementations are
"not implemented" markers, the layer below is reached via base.
self.base.send_frame / self.base.recv_any_frame exchange raw frames with
the layer directly below. For high-level command negotiation (e.g.
brp.Sys_GetInfo()), run it after brp.open() — those calls need the BRP
framing layer above this one.
Further parameters on connections fors sensible data
Additional Options:
- AES based Encryption can be activated
- Enabled monitoring can be suppressed or extended to plaintext
from baltech_sdk import Brp, UsbHid, SecureChannel
KEY = b'abcdefghijklmnuk'
brp = Brp(UsbHid(),
crypto=SecureChannel(security_level=1, key=KEY), # encrypt communication
monitor="plaintext" # log unencrypted data (if activated by user)
)
Metadata
Release files for baltech-sdk 5.2026.11
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 |
|---|---|---|---|---|
| baltech_sdk-5.2026.11.tar.gz | 302.3 kB | Without provenance | Details for baltech_sdk-5.2026.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| baltech_sdk-5.2026.11-py3-none-any.whl | Python 3 | none | any | Details for baltech_sdk-5.2026.11-py3-none-any.whl |
Total release size: 609.3 kB
Release files / baltech_sdk-5.2026.11.tar.gz
| Download URL | baltech_sdk-5.2026.11.tar.gz |
|---|---|
| Size | 302.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
326fe5319d228c5eb4e45580a16974200357b5184bfd9738ad94ea6bd382073b
|
|
BLAKE2b-256 checksum How to use checksums |
ecb0627b49b10f6f4d9553b0b3b2811bdb2d068b5332daabcfc5a7c57695bc53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / baltech_sdk-5.2026.11-py3-none-any.whl
| Download URL | baltech_sdk-5.2026.11-py3-none-any.whl |
|---|---|
| Size | 306.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5031637763adb388f2cad7651ad7524225930df4451f33f013182b536b36a65f
|
|
BLAKE2b-256 checksum How to use checksums |
08eeb1a43f5f62c5e5492d5c3f11d4d93f5e5d0f888521978dd5bc708eef6aea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for baltech-sdk 5.2026.11
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.