Skip to main content

CANopen Lens

Give it a candump log and it tells you, in plain words, what happened on your CANopen network and what to check — as a desktop app and as a Python library.

한국어 설명서 (Korean)

pip install "canopen-lens[gui]"    # the desktop app (recommended)
canopen-lens                       # opens the window

pip install canopen-lens on its own installs only the Python library and the canopen-lens report command line. 한국어: 창(GUI)으로 쓰려면 위처럼 pip install "canopen-lens[gui]"로 설치하세요. [gui] 없이 설치하면 라이브러리와 명령줄 기능만 들어갑니다.

Overview screen

Made so that someone new to CANopen can find a root cause from a single log, without knowing CAN IDs or bytes:

  • A verdict – "Problems found – 3 kinds of error, 1 kind of warning"
  • The status of every device – "Node 5 (CiA 402 drive): had problems but recovered · Axis 2: faulted 1 time but recovered to Enabled"
  • What to check first – every problem explained as What happened? / Why does it matter? / How to check

The UI and all explanations are available in English and Korean.


Install

1. Download the app (no Python needed)

Get the file for your computer from Releases, unpack it and run it.

System File Run
Windows 10/11 CANopenLens-…-windows-x64.zip double-click CANopenLens\CANopenLens.exe
Linux (Ubuntu 22.04+ and similar) CANopenLens-…-linux-x86_64.tar.gz CANopenLens/CANopenLens
Raspberry Pi 4/5 (64-bit OS) CANopenLens-…-linux-aarch64.tar.gz CANopenLens/CANopenLens

2. pip (Python 3.9+)

pip install "canopen-lens[gui]"     # app + library
pip install canopen-lens            # library and command line only (servers, headless Pi)

Prebuilt wheels are published for Windows x64, Linux x86_64 and Linux aarch64, so no C++ compiler is needed. Run canopen-lens to open the window.


Five-minute guide

  1. Record a log on the Linux PC or Raspberry Pi attached to the machine: candump -l can0, reproduce the problem, stop with Ctrl+C. (Saved console output such as candump -t a can0 > log.txt works too.)
  2. Open it – drop the file on the window. No log yet? Pick an example under Try the sample log: a mixed network with many problems, or a two-wheel AMR (ros2_canopen master + STM32 two-axis drive) from boot-time PDO configuration to an E-stop and recovery.
  3. Read the overview – the colour at the top is the verdict; below it are the status of each device and the problems to check first, most important first. Repeats of the same problem are shown once with a count.
  4. Dig deeper – Show the messages jumps to the moment of a problem, with every message explained in one line.
  5. Live monitor – the Live monitor tab connects to a USB-CAN adapter or SocketCAN and shows messages and problems as they happen (socketcan, pcan, kvaser, ixxat, vector, slcan, gs_usb). No hardware? Pick Demo to replay the sample log in real time. Everything received is recorded and can be saved as a candump file or opened in log analysis with one click.
  6. State timeline – how each device and motor axis changed state over time. Red is a fault, a gap means the device went silent. Click a bar to jump there.

Unknown words are explained under Glossary. Save results writes a readable report (.txt), JSON or an Excel-friendly CSV.


What it finds

Finding In plain words
SDO failed The device refused a setting; the abort code is explained together with where to look
No SDO answer The device did not reply; check node-ID, power and wiring in that order
Emergency (EMCY) The device reported an error; the code is turned into readable text
Heartbeat gap / stopped The device went quiet for longer than its normal period, or never came back
Unexpected restart The device rebooted without a reset command (power dip, watchdog, …)
Drive fault A motor drive stopped with a fault; the EMCY at the same moment is linked as the likely cause
Enable did not work Enable operation was sent but the drive never turned on (wrong order, motor power, STO)
Fault reset did not work A reset was sent but the fault stayed (its cause is still there)
Quick stop The drive entered quick stop
CAN bus errors Corrupted traffic on the wires (termination, bit rate, cabling)

Verdicts: ✔ OK – nothing went wrong · ▲ recovered – something went wrong but was fine again at the end of the log · ✖ needs attention – still wrong at the end (fault, silent device) or a setting was not applied.


How a log is analysed

(1760500002.000250) can0 185#3702180220030000
 └ time               └ port └ ID └ data bytes
  1. Who sent what. CANopen IDs are "message type + node-ID": 0x185 = 0x180 (TPDO1, real-time data from a device) + node 5.
  2. Where the values are. Which values sit where inside a PDO (the PDO mapping) is taken from, in this order: SDO configuration found earlier in the log → the EDS you attach → the CiA 402 default (assumed, axis 1 only).
  3. Values into words. Here: axis 1 statusword + axis 2 statusword + axis 1 actual velocity → TPDO1: Axis 1 state: Enabled (SW 0x0237), Axis 2 state: Fault (SW 0x0218), Axis 1 Velocity actual value=800.
  4. Following the story. SDO questions are paired with answers; each node's heartbeat period is learned and late heartbeats are flagged; every CiA 402 axis gets its own state machine, commands are checked against the state that follows, and EMCY messages around a fault are linked to it.
  5. Grouping. Identical findings are collapsed and sorted by importance.

Clicking a message shows a byte-by-byte breakdown. For 582#4300100092010200: 43 = command byte (binary 010 0 00 1 1: read reply, value inside the frame, 4 bytes), 00 10 = index 0x1000 read back to front (CANopen sends the least significant byte first), 00 = sub-index, 92 01 02 00 = 0x00020192: profile 0x0192 = 402 (drive), additional info 0x0002 = servo drive.

Not CANopen? candump records every frame regardless of protocol. If a log has no heartbeat/NMT/SDO/EMCY/SYNC at all, or mostly 29-bit IDs (J1939, vendor protocols), the overview says so instead of pretending, and shows a protocol-independent traffic by ID table (count, period, largest gap, DLC).

Decoding runs in C++; a two-million-frame log opens in one to two seconds on an ordinary PC, and only the rows on screen are turned into text, so large logs stay responsive.


Using it from Python

from canopen_lens import open_log, Kind

log = open_log("robot.log", eds={1: "drive.eds"})   # EDS optional

print(log.report("en"))                  # the whole readable report

h = log.health("en")                     # verdict, per-node status, grouped findings
for group in log.grouped_issues():
    ex = log.explain(group.first, "en")
    print(ex.title, group.count, ex.steps)

df = log.to_dataframe("en")              # pandas (pip install pandas)
log.to_csv("frames.csv")                 # UTF-8 with BOM, opens cleanly in Excel
log.to_json("result.json")

for row in log.trace.filter(kinds=[Kind.EMCY], node=2):
    print(log.summary(int(row), "en"))
for p in log.trace.axis_timeline(5, axis=1):  # node 5, axis 2
    print(p.t, p.state)

Live bus (python-can)

import can
from canopen_lens import LiveDecoder

dec = LiveDecoder(eds={1: "drive.eds"})
with can.Bus(interface="socketcan", channel="can0") as bus:
    dec.run(bus, lang="en")              # prints findings the moment they happen

Or push frames yourself with dec.feed(t, can_id, data). Only the newest frame is kept, so memory stays flat however long it runs.

Command line / CI

canopen-lens report robot.log                          # readable report
canopen-lens report robot.log --brief --fail-on-error  # exit code 1 on errors
canopen-lens report robot.log --format json -o result.json
canopen-lens report robot.log --format csv -o frames.csv
canopen-lens live --channel can0 -v                    # pip install "canopen-lens[live]"

Type hints are included for IDE completion.


Limitations

  • Log files must be in candump format; PCAN .trc is next (the live monitor can use PCAN adapters directly).
  • PDOs are assumed to use the default COB-IDs (0x180 + node, …); COB-IDs changed through 0x1400/0x1800 are not followed yet.
  • Axes 2–8 of multi-axis drives are decoded when the EDS or the log provides their PDO mapping.
  • Findings are guidance based on what the log shows; the device manual has the final word.
  • The Python API may still change before 1.0.

Development

git clone https://github.com/lch-98/canopen-lens
cd canopen-lens
pip install -e ".[gui,test,pandas,live]"
pytest
python tests/make_sample.py      # regenerate the mixed-network example
python tests/make_amr_sample.py  # regenerate the two-wheel AMR example

Releases: see RELEASING.md.

License

MIT

Metadata

Release files for canopen-lens 0.4.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for canopen-lens 0.4.2
File Size Uploaded Provenance Actions
canopen_lens-0.4.2.tar.gz 1.8 MB With provenance Details for canopen_lens-0.4.2.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for canopen-lens 0.4.2
File Actions
canopen_lens-0.4.2-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for canopen_lens-0.4.2-cp314-cp314-win_amd64.whl
canopen_lens-0.4.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for canopen_lens-0.4.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
canopen_lens-0.4.2-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for canopen_lens-0.4.2-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
canopen_lens-0.4.2-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for canopen_lens-0.4.2-cp313-cp313-win_amd64.whl
canopen_lens-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for canopen_lens-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
canopen_lens-0.4.2-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for canopen_lens-0.4.2-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
canopen_lens-0.4.2-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for canopen_lens-0.4.2-cp312-cp312-win_amd64.whl
canopen_lens-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for canopen_lens-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
canopen_lens-0.4.2-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for canopen_lens-0.4.2-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
canopen_lens-0.4.2-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for canopen_lens-0.4.2-cp311-cp311-win_amd64.whl
canopen_lens-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for canopen_lens-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
canopen_lens-0.4.2-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for canopen_lens-0.4.2-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
canopen_lens-0.4.2-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for canopen_lens-0.4.2-cp310-cp310-win_amd64.whl
canopen_lens-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for canopen_lens-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
canopen_lens-0.4.2-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for canopen_lens-0.4.2-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
canopen_lens-0.4.2-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details for canopen_lens-0.4.2-cp39-cp39-win_amd64.whl
canopen_lens-0.4.2-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for canopen_lens-0.4.2-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
canopen_lens-0.4.2-cp39-cp39-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for canopen_lens-0.4.2-cp39-cp39-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Total release size: 11.1 MB

Release files / canopen_lens-0.4.2.tar.gz

Download URL canopen_lens-0.4.2.tar.gz
Size 1.8 MB
Tags Source
SHA-256 checksum
How to use checksums
f7443d412a6cb5f80158ac7adcde43f7d43fbf220de4677ff687f9dfcd677096
BLAKE2b-256 checksum
How to use checksums
989c2dd707ce5260b2efb4d2e42582cf7473ba7936c94bcc574928ea3d45207e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp314-cp314-win_amd64.whl

Download URL canopen_lens-0.4.2-cp314-cp314-win_amd64.whl
Size 616.0 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
99323d5a70bb3ee35309566e75e8d50d83f3455c88eea962c4136aa7da2b8234
BLAKE2b-256 checksum
How to use checksums
7bf33bba30cb0cae02b56913ea3c2b3500bb2eafcc0e9c722cf3d9903b7dd3c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL canopen_lens-0.4.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 487.8 kB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
f077e784684076bffd09fa95a05d5493e2d284e8228a3c254c4a1b0d2fed463b
BLAKE2b-256 checksum
How to use checksums
6a15d1e252dea067db459082c746e8b565886ef507270ce9eb8c57d3db4d26b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL canopen_lens-0.4.2-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 459.7 kB
Tags CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
026503df438e1dd3b9b9259151b1a92f1b8a552e9ff470eb6cbb300fbad2ec48
BLAKE2b-256 checksum
How to use checksums
0816ac874dc593cbe0031f00387e6a55c1d73b476c7f466de75da2272812c6c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp313-cp313-win_amd64.whl

Download URL canopen_lens-0.4.2-cp313-cp313-win_amd64.whl
Size 599.5 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
8e55c51e6f01e6e95d23b6a712155127767d8da389637b0cb32374b3c3b02f2a
BLAKE2b-256 checksum
How to use checksums
04808283a5c7fec13bed77ae80bee9f9d83fbc0798182630618a57fe464f636b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL canopen_lens-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 488.1 kB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
166274521b9d2bcde957ff192679db701f25f4fcf50b4112c9c29eb62f4f057a
BLAKE2b-256 checksum
How to use checksums
46930959172846ee16d0c003bfd94fa0fbd090851fc15e752f3856e9ae83a117
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL canopen_lens-0.4.2-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 459.1 kB
Tags CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
8ea6ea8b8e50dcbf41c812fa5eb57d1d1d8b99d66c90fcc63d0337443034a4f3
BLAKE2b-256 checksum
How to use checksums
41ad403d563209f0c2699588bd7b5259cd993ba143e10ae9d6bb7c9524610106
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp312-cp312-win_amd64.whl

Download URL canopen_lens-0.4.2-cp312-cp312-win_amd64.whl
Size 599.5 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
fb859d5ae23e4da5448b2f4216decdc145bd68536c99e6a00200106aa6d17de0
BLAKE2b-256 checksum
How to use checksums
2dfc9589c67477e6bd2a95a541d8321554b6caefc97a8eecf1225022543bed86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL canopen_lens-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 488.0 kB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
5a04f8a85920f1041109667be9ae42ad464a36544856761eef3d0333ae391af3
BLAKE2b-256 checksum
How to use checksums
2de3815366d708ad23ac24e452fff04c3bd3338049881f35ba0c295218930ccf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL canopen_lens-0.4.2-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 459.1 kB
Tags CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
cb5eb1d588b8ed013c922485513cb6d47103245f654a2b512bca3c80dab55f43
BLAKE2b-256 checksum
How to use checksums
ec2579f4255529199f68e8758ea4f8bee6f152900ad36be5796bfb1c1bf14302
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp311-cp311-win_amd64.whl

Download URL canopen_lens-0.4.2-cp311-cp311-win_amd64.whl
Size 597.4 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
c066c2570f951db8234cecb86e7e82c8f5d2c7d8d3ee1e48cac53734e58d4c5c
BLAKE2b-256 checksum
How to use checksums
ee42c17a3d87b44791154b97fc2f98db0b1b52d2ab73cc75ea7e6ef9425cebd3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL canopen_lens-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 486.5 kB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
075ba913a676e6db78960e47b86b364a7b7f95e1de5aaa2cca5a3cf0720abd0a
BLAKE2b-256 checksum
How to use checksums
5679af3bad20966987996b0f46dec7afaec0bcb59e8ea9e47505e40878112d60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL canopen_lens-0.4.2-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 457.6 kB
Tags CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
579119b199cb5cd1e9248d67b1f5bfa7f62c81dedff817e153fc538dd9600c55
BLAKE2b-256 checksum
How to use checksums
916865bbb47613db79c30595096b0cfae6bdaa335937e73d7079036c69b2701a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp310-cp310-win_amd64.whl

Download URL canopen_lens-0.4.2-cp310-cp310-win_amd64.whl
Size 595.9 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
2b742a96086e52647c66fb7e2c05bbffd7342d55df87bf8117b2f0f47113c6f3
BLAKE2b-256 checksum
How to use checksums
8b3c4cf1510bab30c36935245ce7f68434b13aa2f583ad997374e5348f6cc279
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL canopen_lens-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 485.0 kB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8fe3e315f0e9c2bb1a5ffac864114d90a24d469c8f33b70c3aa5ee029d86ebb1
BLAKE2b-256 checksum
How to use checksums
13195f2ce3c199e33805bd6a2825553dc168d17a5f57734abce93c608d949c93
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL canopen_lens-0.4.2-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 456.3 kB
Tags CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
71ecf7bc3a93694f8d4c0fc447e1fcbd9f3b6ebe174c43be579a01efa1e1b07b
BLAKE2b-256 checksum
How to use checksums
e12060662c1b6c12f20a603cfd9407dc8dfb4bb3c1ead39c7836740c475bf46f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp39-cp39-win_amd64.whl

Download URL canopen_lens-0.4.2-cp39-cp39-win_amd64.whl
Size 596.7 kB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
c7713125b166113adef780115a07c0988d1c98089247b7935ec86486b385df88
BLAKE2b-256 checksum
How to use checksums
2e1275cb925f8e0775bd767910f14e9214e228fce94ba5ad405b718be3d71a57
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL canopen_lens-0.4.2-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 485.4 kB
Tags CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
cbdd4a63a3c6ebad977c147da980925fd86e9f089199c939e1334d3591cac541
BLAKE2b-256 checksum
How to use checksums
7e6e30cccfe1c2055ca36d53890b8d6a28e2fce8f099b779b1b7ff176dec1bd4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Release files / canopen_lens-0.4.2-cp39-cp39-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL canopen_lens-0.4.2-cp39-cp39-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 456.5 kB
Tags CPython 3.9 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
14881c911de68005082db40484c56b07db5c7cad0c9f5acfab70438c7db218e4
BLAKE2b-256 checksum
How to use checksums
f8275d18bc94dc6d81413f94c3bb0939c4c4515fb2e9d5f62035acd401108cc0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 21, 2026.

Transparency log

Security for canopen-lens 0.4.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

All 19 files in this release have been uploaded with provenance metadata.

Select from 19 files

Attestation for canopen_lens-0.4.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 Oct 21, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page