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 command line (canopen-lens your.log). 한국어: 창(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 one-line verdict – "Needs attention · unresolved 3 · recovered 2 · warnings 2"
  • A list of problems – messages that belong to one event (fault, EMCY, failed resets …) become one row, e.g. "Node 2 · Stopped: over current → recovered on reset #2"
  • Details on demand – click a row for What happened / Check first / Why it matters

The app and the command line both speak 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 or press Open log. No log yet? Pick one under Examples: 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 summary – the card at the top is the verdict, the table below is the list of problems. Unresolved (red, still wrong at the end of the log) comes first, then Recovered (teal, went wrong but came back). Warnings (amber) are folded away until you open them. Every device's state is listed on the right.
  4. Dig deeper – click a row and the details open on the right: what happened in time order and three things to check first. Show messages at this moment jumps to the Messages page, with every message explained in one line. To attach an EDS or decode a device as a CiA 402 drive, use the ⋯ button next to it in the device list.
  5. Live – the Live page 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. 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; Ctrl+wheel or dragging over a range zooms in on short events.

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

Problem details


Command line

The same summary works over SSH, on a server or on a headless Raspberry Pi. Give it a log file:

canopen-lens examples              # copy the two example logs into this folder
canopen-lens sample_cia402.log     # summary
✖ Needs attention   unresolved 3  recovered 2  warnings 2  OK 1
  sample_cia402.log · 6.0 s · 5,304 messages · 5 nodes

Unresolved
   1  Node 4           No answer — the device seems to be missing                0.27 s
   2  Node 3           Went silent and never came back                           5.41 s
   3  Node 2           A setting was not applied                                 0.26 s

Recovered
   4  Node 5 · axis 2  Stopped: motor blocked → recovered after a reset          1.99 s
   5  Node 2           Stopped: continuous over current → recovered on reset #2  2.99 s

Warnings  Node 3 silent 0.7 s · 1 CAN bus error(s)
OK        Node 1

Details       canopen-lens sample_cia402.log -d 1
Save          canopen-lens sample_cia402.log -s result.csv

The last lines are the next command to type. Pass a number to -d to see that problem in detail:

$ canopen-lens sample_cia402.log -d 4
4  Recovered  Node 5 · axis 2 · Stopped: motor blocked → recovered after a reset
   Cause: Motor blocked (EMCY 0x7121)

   What happened
   1.990 s  Fault — motor torque switched off
   1.990 s  Cause reported: Motor blocked · EMCY 0x7121
   2.490 s  Fault cleared
   2.690 s  Running again

   Check first
   1. Look up 0x7121 in the device manual's error table
   2. Read the drive error code (0x683F) for the exact cause
   3. Remove the cause, then fault reset → 0x06 → 0x07 → 0x0F

   Why it matters  A faulted drive turns motor torque off and ignores motion commands until the fault is reset.
   Messages        #1512 #1515 #1988 #1993 #2179
Command What it does
canopen-lens robot.log summary
canopen-lens robot.log -d 1 problem 1 in detail (-d 1,4 and -d all work too)
canopen-lens robot.log -s result.txt save; the extension picks the format: .txt report · .csv messages (Excel) · .json findings
canopen-lens robot.log --eds 1=drive.eds attach an EDS to node 1 (repeat for more nodes)
canopen-lens robot.log --check exit status 1 if a problem is unresolved (test benches, CI)
canopen-lens live can0 watch a bus live (pip install "canopen-lens[live]"; options: canopen-lens live -h)
canopen-lens open the window

The language follows the computer's setting; use --lang en / --lang ko or the CANOPEN_LENS_LANG environment variable to change it. --no-color (or NO_COLOR=1) turns colours off.


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)

Every problem ends up in one of three states: Unresolved – still wrong at the end of the log (fault, silent device) or a setting was not applied · Recovered – something went wrong but was fine again at the end · Warning – nothing stopped, but it can become a problem if it keeps happening (late heartbeats, CAN bus errors). The verdict follows from them: ✖ Needs attention if anything is unresolved, ▲ Problems occurred, all recovered if every problem recovered, ▲ No real problems if there are only warnings, ✔ No problems found otherwise.

A drive that stops leaves several messages behind: the fault, the EMCY at the same moment, failed resets, the successful reset, running again. These are grouped into one incident (fault and EMCY on the same node within 0.1 s; resets after it are numbered), so one event is not shown as five problems.


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

ov = log.overview("en")                  # the same summary as the app and the command line
print(ov.headline, ov.counts)            # "Needs attention", {"open": 3, "recovered": 2, …}
for inc in ov.incidents:                 # grouped incidents, most important first
    print(inc.number, inc.status, inc.where, inc.title)

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.

Test benches / CI

canopen-lens robot.log --check -s result.json   # exit status 1 if a problem is unresolved, findings as JSON

summary, incidents and devices in result.json hold the same verdict and problem list as the app. The pre-0.5 canopen-lens report … command still works.

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.5.0

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.5.0
File Size Uploaded Provenance Actions
canopen_lens-0.5.0.tar.gz 1.9 MB With provenance Details for canopen_lens-0.5.0.tar.gz

Built distributions (wheels)

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

Total release size: 11.5 MB

Release files / canopen_lens-0.5.0.tar.gz

Download URL canopen_lens-0.5.0.tar.gz
Size 1.9 MB
Tags Source
SHA-256 checksum
How to use checksums
25368dc079e31116dc53300d828ffc9ba99c2d821b2dbc73f8e3add186e2a765
BLAKE2b-256 checksum
How to use checksums
dabf14aeca2220c662cb0a15d8b91a4a45eaa516b2ca8912b2e9ba920fb109d2
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp314-cp314-win_amd64.whl
Size 637.6 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
05dcd608d224053d4e388d5ace1bb5a95b8b9da53c8ca8f61a95d56447154b6b
BLAKE2b-256 checksum
How to use checksums
11933f59ebb933bcf09a976df7cb7e44f6a7a3e0fe7355d59af4a6367177c8ec
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 509.1 kB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
7833c9434f7741abecb39262eb5e6df7d4a322b90647d2646e7407827eb93fc8
BLAKE2b-256 checksum
How to use checksums
9be6e977a2797a7b2786f3d5bcab4540ca26ee5c097c8e178ddc5f7396d3c7fe
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 481.0 kB
Tags CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
aeffc8c46ea47f1fe09d90dc5109d41d8ebb4d3a230ffa08076b14480b8d6aaa
BLAKE2b-256 checksum
How to use checksums
24c7ab05c133505efc56d14e4b4f5ff0fbb06459119722683fbb677b20f844c1
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp313-cp313-win_amd64.whl
Size 620.9 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
4403ec36637bf395dd0b6f177bf9dae3314081993aa77deef65652f0409afc44
BLAKE2b-256 checksum
How to use checksums
c1cc9bcedb61d8b4fef2269934b8c95d0dbb9e18e8566340e9198dacced5303c
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 509.4 kB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
9acf227dd6603d201b11031e44380123c41ea16d50a7628e41139c5f21d74f04
BLAKE2b-256 checksum
How to use checksums
9e8922ae726ed2f71844617289218051c5d41c42b9dd93658f6bc90538a1d08f
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 480.4 kB
Tags CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
be8c8eb4f81b47531e2fa02d8a7f88e3d91f30f363e531e5dff38933f9c02d68
BLAKE2b-256 checksum
How to use checksums
c50053e9692c3cb0f7944a9779b5a7e36b51da69ab94d2bb7108915b006b65ca
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp312-cp312-win_amd64.whl
Size 620.9 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
7cc62fb262106b7cb649490fae2504a94906e3643bf62163cc72938acd2fc70d
BLAKE2b-256 checksum
How to use checksums
56de1b4eb9a392b7f55757432f22aada88fcedd1091c80f87cd3d350a42a6faf
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 509.3 kB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
44b9964dc318c1e0c0dc0952d822a9eccc4ef45326f5145dafa59062beb6b2b4
BLAKE2b-256 checksum
How to use checksums
cf62ff5f0eed7a3c035cc90da6dd342ba53eac83add5971f0e7e213ff6d5ae7c
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 480.4 kB
Tags CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
ac7febc8968478a86b441582717ff075660e4b8938744ceab37d26b5d537b90d
BLAKE2b-256 checksum
How to use checksums
e402f8411d0c1918d73d558c65f526bbdad4595a28b7e2bc7e9b83caaf58e05c
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp311-cp311-win_amd64.whl
Size 618.8 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
7eae3b33210cac0216c982a390014e0533444c47766122030abbe9fc4fe2d894
BLAKE2b-256 checksum
How to use checksums
7f23f144b9e2b79af2b9fda2dfbd0e6aa33c96caed16221bfe76a4a741c7ce74
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 507.8 kB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
fce5c95163d915805ea883dc8ae71fcf1974f802688509e3c511c67e6d419253
BLAKE2b-256 checksum
How to use checksums
abf806d4542903b358e3ba8b69d0c7856d29abe6e78ec89b50fff47527557e86
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 478.9 kB
Tags CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
df2b68d468b37d5cdc1442cd69598cacd49e82bda79e30fb33fd00fd0a734d81
BLAKE2b-256 checksum
How to use checksums
04274fcd00088cfdd15141954e81c06c0382fc3ce2f6b199d54d9743aa4d91f0
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp310-cp310-win_amd64.whl
Size 617.3 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
3d08a20b586be58865beeb0ae5da1898960e6a0d135c6f3a0966b71e6dca70c3
BLAKE2b-256 checksum
How to use checksums
a2e5269c8ed85d2ced0902c135f123a9e416412f125ea77b45bc4b868dc8f25d
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 506.3 kB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
6d45c1c32c3a1d321057873bca2ed81512357a66eefc3e1c047d5232fcd0ae4e
BLAKE2b-256 checksum
How to use checksums
1455004201e20cbdd8369fc4eb92ec3b71247d5ce0ca5fad27e756085875ee40
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 477.6 kB
Tags CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
c3198afb86aed5f510de4a97aab0f4a4939ad9b19141705df215f7407dbe7cc8
BLAKE2b-256 checksum
How to use checksums
910be39781dbd12579e61a615e08a8499db0fece9b0ab0f8967b15557ef62c88
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp39-cp39-win_amd64.whl
Size 618.1 kB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
ce1507beef2ef7b649dac77767c3fae101d5b42dac5577207ef1a3c0c9d89189
BLAKE2b-256 checksum
How to use checksums
840ce719dc7598e4db57d528805efb7c358f62a0ef867792136b82b597b4dc86
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 506.7 kB
Tags CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
314c6135f82604c0ef9fea9667708b16d0e8ab1a4de8115943d03b2cd709ed46
BLAKE2b-256 checksum
How to use checksums
959735abb85b1e8819937afd59831296986881719cccb8a726264fa2fff8a537
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 22, 2026.

Transparency log

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

Download URL canopen_lens-0.5.0-cp39-cp39-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 477.8 kB
Tags CPython 3.9 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
78d2654b417fd8fd4702d6d68d1b98306908c940783a1e2d354dcedd0a4a5c6d
BLAKE2b-256 checksum
How to use checksums
ceb9c01327726a1e25537b1fe09a622df2744b5656d758fe9529817e2ec93ba8
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 22, 2026.

Transparency log

Security for canopen-lens 0.5.0

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.5.0.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 22, 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