openOBD Client by Jifeline Networks for Python 3
Release notes:
- 1.26.12 : 2026-10
- Feature: Allow enabling GRPC keep alive messages to prevent connections from being dropped
- 1.26.11 : 2026-09
- Feature: Allow hosting functions without using a signature
- 1.26.8 : 2026-07
- Feature: Allow retrieving information on the vehicle and products
- Feature: Support muting and unmuting of locals
- 1.26.7 : 2026-06
- Feature: When serving functions, automatically reconnect when a reconnect request is received
- Fix: Improved stability of passing arguments during function calls
- 1.26.2 : 2026-03
- Feature: Allow calls from active openOBD function to other served openOBD functions
- Fix: Filtering information based on vehicles or products is now properly propagated
- Fix: Recursive folder loading when serving functions to the network
- 1.26.0 : 2025-11
- Feature: New logging service to allow log output to ticket workspace
- 1.25.3 : 2025-11
- Feature: Serve functions and compositions of functions to the ticket dashboard
- 1.25.x-alpha : 2025-09
- Feature: Serve functions and compositions of functions to the ticket dashboard
- 1.25.x : 2025-09
- Feature: Starting functions from the ticket dashboard
- 1.24.x : 2025-08
- Feature: Support for TP2.0 communication
- Feature: Option to link functions to products and vehicles
- 1.23.x : 2025-07
- Feature: Support for DoIP communication
- Feature: Reading the vehicle's voltage
- 1.22.x : 2025-07
- Feature: A list of ECUs detected in the vehicle can now be requested
- 1.20.x : 2025-06
- Feature: Added support for showing images in the user interface
- 1.19.x : 2025-06
- Feature: Added translations to the user interface
- 1.18.x : 2025-06
- Feature: Support for function calls
- Feature: Terminal 15 support
- Feature: Session transfer
- Passing the openOBD session to another function executor
- 1.17.x : 2024-12
Feature: ISO14230 K-line support with Slow/Fast initialization- Supported bitrates are 9600, 10k4 and 15k6
- Supported protocol is KWP2000
- 1.16.x : 2024-09
First production release - 1.11.x :
Beta release
1 maintainer
Metadata
1 maintainer
Release files for openobd 1.26.12
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 | |
|---|---|---|---|---|
| openobd-1.26.12.tar.gz | 45.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openobd-1.26.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.9 kB
Release files / openobd-1.26.12.tar.gz
| Download URL | openobd-1.26.12.tar.gz |
|---|---|
| Size | 45.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8053245a185f2507dd29ff0c1500b7c38a5cfc6424aa7037afed4af0dac0e403
|
|
BLAKE2b-256 checksum How to use checksums |
c59c16bf29b5bc6643cac26bb197b45c4b8b9510cc954e57c8a5eefa06fb8744
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / openobd-1.26.12-py3-none-any.whl
| Download URL | openobd-1.26.12-py3-none-any.whl |
|---|---|
| Size | 63.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
207a804be1e29f05baaf2f1e0dc6a3dbb43dff6a37ea5cb46c78f90091f33dde
|
|
BLAKE2b-256 checksum How to use checksums |
d39ccf28502774bc5a15984b487d563ffdc76320ef6733eaa455e9609c09f24f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for openobd 1.26.12
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.
