canopen-bench 1.0.170__tar.gz

canopen_bench-1.0.170/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 NobseVomBerg
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

canopen_bench-1.0.170/PKG-INFO

@@ -0,0 +1,243 @@
+Metadata-Version: 2.4
+Name: canopen-bench
+Version: 1.0.170
+Summary: CANopen Bench — web-based test bench and machine control for CANopen devices: scan, SDO access from EDS files, YAML test cases, firmware download, live CAN trace (IXXAT, PCAN, Vector, demo mode without hardware; vendor devices via plugins)
+Author: NobseVomBerg
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/NobseVomBerg/CANopen-Bench
+Project-URL: Issues, https://github.com/NobseVomBerg/CANopen-Bench/issues
+Project-URL: Changelog, https://github.com/NobseVomBerg/CANopen-Bench/blob/main/CHANGELOG.md
+Project-URL: Author, https://unsix.de/projekte.html
+Keywords: canopen,can,can-bus,cia301,eds,test-bench,test-automation,machine-control,sdo,pdo,nmt,lss,firmware-update,python-can,ixxat,pcan,vector
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Web Environment
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Manufacturing
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Embedded Systems
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: System :: Hardware
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: THIRD-PARTY-NOTICES.md
+Requires-Dist: starlette>=0.37
+Requires-Dist: uvicorn>=0.29
+Requires-Dist: websockets>=12
+Requires-Dist: python-can>=4.4
+Requires-Dist: canopen>=2.3
+Requires-Dist: packaging>=23
+Requires-Dist: pyyaml>=6
+Provides-Extra: serial
+Requires-Dist: pyserial>=3.5; extra == "serial"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-cov>=5; extra == "dev"
+Requires-Dist: httpx>=0.27; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Dynamic: license-file
+
+# CANopen Bench
+
+Web tool to test and control CANopen devices on a hardware bench — scan,
+object access, system tests, firmware download and a live CAN trace,
+driven by the devices' EDS files. Python backend (Starlette +
+canopen/python-can), no-build frontend (Preact/HTM), one self-contained
+workspace folder per bench.
+
+![Live CAN trace (dark mode): SDO transfers decoded against the EDS, heartbeats, state log](https://raw.githubusercontent.com/NobseVomBerg/CANopen-Bench/main/docs/img/trace.png)
+
+## Try it — no hardware needed
+
+```bash
+pip install canopen-bench
+canopen-bench                  # → http://127.0.0.1:8000
+```
+
+No virtualenv needed to just run it. From a clone, `pip install .`
+installs the same thing from the checkout — without `-e`, which installs
+the package for editing, and that is what `## Development` below is for.
+
+`canopen-bench` is a shortcut the install writes; the module runs just as
+well by itself, and from a clone's root it runs that checkout:
+
+```bash
+python -m canopen_bench                       # same thing, same options
+python -m canopen_bench --port 8001 --host 0.0.0.0
+```
+
+Two reasons to prefer it. It runs *this* directory rather than whatever
+`canopen-bench` happens to point at, which matters as soon as a second
+copy or a second virtualenv is around. And it needs only the
+dependencies, not the package itself: `pip install starlette uvicorn
+websockets canopen python-can pyyaml` (the `dependencies` list in
+`pyproject.toml`) and a clone is enough — worth knowing on a bench
+machine where you would rather not install anything.
+
+Note the underscore: the distribution is `canopen-bench`, the module is
+`canopen_bench`. `python -m canopen-bench` cannot work — a hyphen is not
+valid in a Python module name.
+
+Pick **Demo mode** on the Setup page, **Connect**, **Scan**: virtual
+devices are generated from the bundled `canopen_bench/seed/DemoDevice.eds`
+(installed into
+the workspace on first run). SDO reads/writes are answered from the EDS
+object dictionary — including realistic aborts on out-of-range writes —
+and every access shows up in the Trace like real bus traffic.
+
+![Setup page: bus interface, EDS registry with identity matching, machine control](https://raw.githubusercontent.com/NobseVomBerg/CANopen-Bench/main/docs/img/setup.png)
+
+## Features
+
+- **Setup** — adapter/bitrate/scan-range, EDS registry with identity
+  matching (0x1018), machine control: adopt the bench's expected state,
+  scan & verify against it, re-address via exchangeable flow files.
+- **Production view**: a switch to a reduced bench for the end of a line,
+  showing the procedures a vendor package ships (flows marked
+  `grade: production`, e.g. flash a board) with their firmware choices,
+  a Start button, instructions and progress.
+- **Objects** — EDS object browser with read/write, favorites
+  (auto-saved), typed RAW rows (SDO / PDO / NMT with per-row node-id),
+  last-known values per device serial number.
+- **Tests** — declarative YAML test cases
+  (`docs/ablaeufe/testfall-format.md`, examples in
+  `examples/testcases/`) executed for real against the selected device.
+  A run leaves HTML behind: one file per case, one summary, and a JSON
+  sibling. From those, "Overview by variant" folds the last so many days
+  into one collapsible section per hardware variant — runs, successes
+  and last verdict per case — which is how you tell one broken variant
+  from a broken device family.
+- **Bench instruments** — a remote-controllable lab power supply is set
+  from the Setup page and from a test case (`psu` step), which is what
+  keeps an under-voltage case automated instead of asking an operator to
+  turn a knob. Serial port, `pip install ".[serial]"`; drivers in
+  `canopen_bench/instruments/`.
+- **SWDL** — firmware download; the files come from a folder you point at
+  (often the firmware project's build output, drag & drop works too), and
+  what each one is comes from the extension that knows the format.
+  Download protocols are manufacturer-specific and ship as vendor
+  extension packages (see the note on the page).
+- **Trace** — live monitor, newest frame at the top, scrollable back
+  through the whole 200k-frame ring buffer or an opened capture rather
+  than a screenful. Class + device filters, ms/µs timestamps, capture
+  save/load, and autosave — every recorded frame written to a capture
+  file as it arrives, kept for two weeks, for the endurance runs that are
+  longer than the ring is deep.
+
+## Hardware
+
+Which adapters the tool talks to, via python-can. Names are the
+manufacturers' — see the trademark note in `THIRD-PARTY-NOTICES.md`;
+this project is not affiliated with any of them, and the table says what
+has been exercised, not what is warranted.
+
+| Adapter | Driver | State |
+|---|---|---|
+| IXXAT USB-to-CAN | VCI4 (Windows) | in regular use on the author's bench |
+| PCAN-USB | PCANBasic | wired up, never run — no such adapter here |
+| Vector VN1600 (VN1610/VN1630) | XL driver (Windows) | run against a VN1630 |
+| Demo mode | — | no hardware, EDS-driven simulation |
+| other adapters (e.g. CPC-USB) | via plugin packages | separate install |
+
+Everything above demo mode goes through python-can's own backends, so
+adapter support tracks python-can. The Vector entry exists because plain
+CAN on a VN1600 needs only Vector's freely downloadable XL driver — the
+CANoe/CANalyzer licences are for their applications, not for talking to
+the hardware — and a lot of that hardware outlives the software budget
+it was bought with. Bring-up checklists live in
+`docs/ablaeufe/A-01-verbinden.md` and `A-02-scan.md`.
+
+## Workspaces
+
+Every subfolder of the data folder is one workspace: its own sqlite db,
+EDS files, trace captures and flow files. Create and switch workspaces on
+the Setup page; copy a folder to clone or back up a bench. The data folder
+is chosen under Setup > Folders and kept per user (`%APPDATA%\CANopen-Bench`,
+`~/.config/canopen-bench`), so the bench finds it wherever it is started
+from; on the first start it is `./data` where there is one, else
+`~/CANopen-Bench`. `--data <folder>` names it for one start (a second bench
+beside the everyday one, a mounted Docker volume). `--db <path>` remains as an expert override for a
+single explicit database file.
+
+Flows and EDS files a package ships are written over in the workspace on
+every start, like its test cases: an update arrives without anybody
+looking for the old copy. A file of one's own goes in under another name.
+
+## Docker
+
+```bash
+docker build -t canopen-bench .
+docker run -p 8000:8000 -v canopen-bench:/data canopen-bench
+```
+
+All workspaces live on the `/data` volume. Demo mode works out of the
+box; USB CAN adapters need the device passed through
+(`--device=/dev/bus/usb`). The tool has no authentication — keep the
+port on a trusted network (see `SECURITY.md`).
+
+## Extending
+
+Vendor- and device-specific functionality (adapter cards, EDS seeds,
+firmware catalogs, addressing procedures with session identities, demo
+protocol simulations, trace decoders, EMCY code tables, custom
+test-step primitives, SWDL strategies) lives in separate pip packages
+registered under the
+`canopen_bench.plugins` entry-point group — installing one activates it.
+In multi-workspace mode this needs no shell at all: Setup > Extensions
+installs a plugin package (`.whl`) straight from the browser, active
+immediately — its own dependencies are not installed with it, and the
+state log names any this Python lacks, with the pip command that adds
+them. Guide with hook table and a minimal example:
+`docs/extending.md`; API: `canopen_bench/plugin.py`. A complete worked
+example ships in this repo under
+[`plugins/cob-cpcusb/`](https://github.com/NobseVomBerg/CANopen-Bench/tree/main/plugins/cob-cpcusb) — python-can driver plus
+adapter card, its own tests, MIT. It is a separate distribution, not part
+of the `canopen-bench` package: install it only if you have that
+adapter.
+
+## Documentation
+
+- `IMPLEMENTATION.md` — architecture and design decisions
+- `CONTRIBUTING.md` — dev setup, test conventions, what goes where
+- `docs/extending.md` — plugin guide
+- `docs/ablaeufe/` — operational sequence specs (German)
+- `docs/ablaeufe/testfall-format.md` — YAML test-case format
+
+## Development
+
+```bash
+python -m venv .venv && . .venv/bin/activate
+pip install -e ".[dev]"         # editable + pytest/ruff
+pytest                          # core suite
+```
+
+`CONTRIBUTING.md` has the rest: what CI checks, where things belong, the
+versioning rule.
+
+Behind a TLS-inspecting corporate proxy, pip fails with
+`CERTIFICATE_VERIFY_FAILED` on pypi.org: the proxy's CA is trusted by the
+operating system but not by the certificate bundle Python ships. On
+pip 23.2+, `--use-feature=truststore` makes pip use the OS store
+instead. On older pip that route is closed — it needs the `truststore`
+package, which also comes from pypi.org — so export the OS root
+certificates to a PEM and point pip at it with `--cert`, or set it once
+with `pip config set global.cert <file>`. Either way certificate
+verification stays on.
+
+## License & author
+
+Core application: MIT (`LICENSE`). Plugin packages are licensed
+independently — vendor plugins proprietary, `cob-cpcusb` MIT.
+Bundled and depended-on third-party components, and the trademark note
+(CANopen® and CiA® belong to CAN in Automation e.V.; this is not a
+CiA-certified or CiA-affiliated tool), are listed in
+[`THIRD-PARTY-NOTICES.md`](https://github.com/NobseVomBerg/CANopen-Bench/blob/main/THIRD-PARTY-NOTICES.md).
+
+Created by NobseVomBerg · [unsix.de](https://unsix.de) ·
+[GitHub](https://github.com/NobseVomBerg/CANopen-Bench)

canopen_bench-1.0.170/README.md

@@ -0,0 +1,198 @@
+# CANopen Bench
+
+Web tool to test and control CANopen devices on a hardware bench — scan,
+object access, system tests, firmware download and a live CAN trace,
+driven by the devices' EDS files. Python backend (Starlette +
+canopen/python-can), no-build frontend (Preact/HTM), one self-contained
+workspace folder per bench.
+
+![Live CAN trace (dark mode): SDO transfers decoded against the EDS, heartbeats, state log](https://raw.githubusercontent.com/NobseVomBerg/CANopen-Bench/main/docs/img/trace.png)
+
+## Try it — no hardware needed
+
+```bash
+pip install canopen-bench
+canopen-bench                  # → http://127.0.0.1:8000
+```
+
+No virtualenv needed to just run it. From a clone, `pip install .`
+installs the same thing from the checkout — without `-e`, which installs
+the package for editing, and that is what `## Development` below is for.
+
+`canopen-bench` is a shortcut the install writes; the module runs just as
+well by itself, and from a clone's root it runs that checkout:
+
+```bash
+python -m canopen_bench                       # same thing, same options
+python -m canopen_bench --port 8001 --host 0.0.0.0
+```
+
+Two reasons to prefer it. It runs *this* directory rather than whatever
+`canopen-bench` happens to point at, which matters as soon as a second
+copy or a second virtualenv is around. And it needs only the
+dependencies, not the package itself: `pip install starlette uvicorn
+websockets canopen python-can pyyaml` (the `dependencies` list in
+`pyproject.toml`) and a clone is enough — worth knowing on a bench
+machine where you would rather not install anything.
+
+Note the underscore: the distribution is `canopen-bench`, the module is
+`canopen_bench`. `python -m canopen-bench` cannot work — a hyphen is not
+valid in a Python module name.
+
+Pick **Demo mode** on the Setup page, **Connect**, **Scan**: virtual
+devices are generated from the bundled `canopen_bench/seed/DemoDevice.eds`
+(installed into
+the workspace on first run). SDO reads/writes are answered from the EDS
+object dictionary — including realistic aborts on out-of-range writes —
+and every access shows up in the Trace like real bus traffic.
+
+![Setup page: bus interface, EDS registry with identity matching, machine control](https://raw.githubusercontent.com/NobseVomBerg/CANopen-Bench/main/docs/img/setup.png)
+
+## Features
+
+- **Setup** — adapter/bitrate/scan-range, EDS registry with identity
+  matching (0x1018), machine control: adopt the bench's expected state,
+  scan & verify against it, re-address via exchangeable flow files.
+- **Production view**: a switch to a reduced bench for the end of a line,
+  showing the procedures a vendor package ships (flows marked
+  `grade: production`, e.g. flash a board) with their firmware choices,
+  a Start button, instructions and progress.
+- **Objects** — EDS object browser with read/write, favorites
+  (auto-saved), typed RAW rows (SDO / PDO / NMT with per-row node-id),
+  last-known values per device serial number.
+- **Tests** — declarative YAML test cases
+  (`docs/ablaeufe/testfall-format.md`, examples in
+  `examples/testcases/`) executed for real against the selected device.
+  A run leaves HTML behind: one file per case, one summary, and a JSON
+  sibling. From those, "Overview by variant" folds the last so many days
+  into one collapsible section per hardware variant — runs, successes
+  and last verdict per case — which is how you tell one broken variant
+  from a broken device family.
+- **Bench instruments** — a remote-controllable lab power supply is set
+  from the Setup page and from a test case (`psu` step), which is what
+  keeps an under-voltage case automated instead of asking an operator to
+  turn a knob. Serial port, `pip install ".[serial]"`; drivers in
+  `canopen_bench/instruments/`.
+- **SWDL** — firmware download; the files come from a folder you point at
+  (often the firmware project's build output, drag & drop works too), and
+  what each one is comes from the extension that knows the format.
+  Download protocols are manufacturer-specific and ship as vendor
+  extension packages (see the note on the page).
+- **Trace** — live monitor, newest frame at the top, scrollable back
+  through the whole 200k-frame ring buffer or an opened capture rather
+  than a screenful. Class + device filters, ms/µs timestamps, capture
+  save/load, and autosave — every recorded frame written to a capture
+  file as it arrives, kept for two weeks, for the endurance runs that are
+  longer than the ring is deep.
+
+## Hardware
+
+Which adapters the tool talks to, via python-can. Names are the
+manufacturers' — see the trademark note in `THIRD-PARTY-NOTICES.md`;
+this project is not affiliated with any of them, and the table says what
+has been exercised, not what is warranted.
+
+| Adapter | Driver | State |
+|---|---|---|
+| IXXAT USB-to-CAN | VCI4 (Windows) | in regular use on the author's bench |
+| PCAN-USB | PCANBasic | wired up, never run — no such adapter here |
+| Vector VN1600 (VN1610/VN1630) | XL driver (Windows) | run against a VN1630 |
+| Demo mode | — | no hardware, EDS-driven simulation |
+| other adapters (e.g. CPC-USB) | via plugin packages | separate install |
+
+Everything above demo mode goes through python-can's own backends, so
+adapter support tracks python-can. The Vector entry exists because plain
+CAN on a VN1600 needs only Vector's freely downloadable XL driver — the
+CANoe/CANalyzer licences are for their applications, not for talking to
+the hardware — and a lot of that hardware outlives the software budget
+it was bought with. Bring-up checklists live in
+`docs/ablaeufe/A-01-verbinden.md` and `A-02-scan.md`.
+
+## Workspaces
+
+Every subfolder of the data folder is one workspace: its own sqlite db,
+EDS files, trace captures and flow files. Create and switch workspaces on
+the Setup page; copy a folder to clone or back up a bench. The data folder
+is chosen under Setup > Folders and kept per user (`%APPDATA%\CANopen-Bench`,
+`~/.config/canopen-bench`), so the bench finds it wherever it is started
+from; on the first start it is `./data` where there is one, else
+`~/CANopen-Bench`. `--data <folder>` names it for one start (a second bench
+beside the everyday one, a mounted Docker volume). `--db <path>` remains as an expert override for a
+single explicit database file.
+
+Flows and EDS files a package ships are written over in the workspace on
+every start, like its test cases: an update arrives without anybody
+looking for the old copy. A file of one's own goes in under another name.
+
+## Docker
+
+```bash
+docker build -t canopen-bench .
+docker run -p 8000:8000 -v canopen-bench:/data canopen-bench
+```
+
+All workspaces live on the `/data` volume. Demo mode works out of the
+box; USB CAN adapters need the device passed through
+(`--device=/dev/bus/usb`). The tool has no authentication — keep the
+port on a trusted network (see `SECURITY.md`).
+
+## Extending
+
+Vendor- and device-specific functionality (adapter cards, EDS seeds,
+firmware catalogs, addressing procedures with session identities, demo
+protocol simulations, trace decoders, EMCY code tables, custom
+test-step primitives, SWDL strategies) lives in separate pip packages
+registered under the
+`canopen_bench.plugins` entry-point group — installing one activates it.
+In multi-workspace mode this needs no shell at all: Setup > Extensions
+installs a plugin package (`.whl`) straight from the browser, active
+immediately — its own dependencies are not installed with it, and the
+state log names any this Python lacks, with the pip command that adds
+them. Guide with hook table and a minimal example:
+`docs/extending.md`; API: `canopen_bench/plugin.py`. A complete worked
+example ships in this repo under
+[`plugins/cob-cpcusb/`](https://github.com/NobseVomBerg/CANopen-Bench/tree/main/plugins/cob-cpcusb) — python-can driver plus
+adapter card, its own tests, MIT. It is a separate distribution, not part
+of the `canopen-bench` package: install it only if you have that
+adapter.
+
+## Documentation
+
+- `IMPLEMENTATION.md` — architecture and design decisions
+- `CONTRIBUTING.md` — dev setup, test conventions, what goes where
+- `docs/extending.md` — plugin guide
+- `docs/ablaeufe/` — operational sequence specs (German)
+- `docs/ablaeufe/testfall-format.md` — YAML test-case format
+
+## Development
+
+```bash
+python -m venv .venv && . .venv/bin/activate
+pip install -e ".[dev]"         # editable + pytest/ruff
+pytest                          # core suite
+```
+
+`CONTRIBUTING.md` has the rest: what CI checks, where things belong, the
+versioning rule.
+
+Behind a TLS-inspecting corporate proxy, pip fails with
+`CERTIFICATE_VERIFY_FAILED` on pypi.org: the proxy's CA is trusted by the
+operating system but not by the certificate bundle Python ships. On
+pip 23.2+, `--use-feature=truststore` makes pip use the OS store
+instead. On older pip that route is closed — it needs the `truststore`
+package, which also comes from pypi.org — so export the OS root
+certificates to a PEM and point pip at it with `--cert`, or set it once
+with `pip config set global.cert <file>`. Either way certificate
+verification stays on.
+
+## License & author
+
+Core application: MIT (`LICENSE`). Plugin packages are licensed
+independently — vendor plugins proprietary, `cob-cpcusb` MIT.
+Bundled and depended-on third-party components, and the trademark note
+(CANopen® and CiA® belong to CAN in Automation e.V.; this is not a
+CiA-certified or CiA-affiliated tool), are listed in
+[`THIRD-PARTY-NOTICES.md`](https://github.com/NobseVomBerg/CANopen-Bench/blob/main/THIRD-PARTY-NOTICES.md).
+
+Created by NobseVomBerg · [unsix.de](https://unsix.de) ·
+[GitHub](https://github.com/NobseVomBerg/CANopen-Bench)

canopen_bench-1.0.170/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,117 @@
+# Third-party notices
+
+CANopen Bench itself is MIT-licensed (see `LICENSE`). It bundles and
+depends on the components below, which keep their own licenses. This
+file is the attribution required by those licenses; it travels with the
+wheel, the sdist and the Docker image.
+
+## Bundled in this repository
+
+Shipped as source inside the package (`canopen_bench/static/vendor/`),
+so these notices apply to every copy of CANopen Bench:
+
+| Component | License | Copyright |
+|---|---|---|
+| [Preact](https://preactjs.com) | MIT | © 2015-present Jason Miller |
+| [htm](https://github.com/developit/htm) | Apache-2.0 | © 2018 Jason Miller |
+| [IBM Plex](https://github.com/IBM/plex) | OFL-1.1 | © 2017 IBM Corp. |
+
+Preact and htm are combined into the single bundle
+`canopen_bench/static/vendor/preact-htm.module.js`, which carries the
+same notices in its file header. The bundle is unmodified upstream
+output — CANopen Bench adds no code to it.
+
+### OFL-1.1 (IBM Plex)
+
+`canopen_bench/static/fonts/` holds seven woff2 files, IBM's own
+unmodified builds taken from the `@ibm/plex-sans` (1.1.0) and
+`@ibm/plex-mono` (2.5.0) packages. The full license text ships beside
+them as `fonts/LICENSE.txt`, as the OFL requires.
+
+The copyright line reserves the font name: *"Copyright © 2017 IBM Corp.
+with Reserved Font Name 'Plex'"*. Bundling the fonts with software of any
+license is explicitly allowed, so shipping them inside this MIT package
+is fine and does not affect its license. What the reserved name does
+forbid is calling a **modified** version Plex — which is why these files
+are shipped whole rather than subsetted to save bandwidth. Anyone
+subsetting or otherwise rebuilding them has to rename the result.
+
+### MIT (Preact)
+
+> Permission is hereby granted, free of charge, to any person obtaining a
+> copy of this software and associated documentation files (the
+> "Software"), to deal in the Software without restriction, including
+> without limitation the rights to use, copy, modify, merge, publish,
+> distribute, sublicense, and/or sell copies of the Software, and to
+> permit persons to whom the Software is furnished to do so, subject to
+> the following conditions:
+>
+> The above copyright notice and this permission notice shall be included
+> in all copies or substantial portions of the Software.
+>
+> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+> OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+> MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+> IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+> CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+> TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+> SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+### Apache-2.0 (htm)
+
+Licensed under the Apache License, Version 2.0. You may obtain a copy of
+the License at <http://www.apache.org/licenses/LICENSE-2.0>. Unless
+required by applicable law or agreed to in writing, software distributed
+under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
+OR CONDITIONS OF ANY KIND, either express or implied. See the License for
+the specific language governing permissions and limitations under it.
+
+## Runtime dependencies
+
+Installed by pip, not vendored — but a Docker image built from this
+repository contains them, and distributing that image distributes them:
+
+| Package | License |
+|---|---|
+| [python-can](https://github.com/hardbyte/python-can) | **LGPL-3.0-only** |
+| [canopen](https://github.com/christiansandberg/canopen) | MIT |
+| [Starlette](https://github.com/encode/starlette) | BSD-3-Clause |
+| [Uvicorn](https://github.com/encode/uvicorn) | BSD-3-Clause |
+| [websockets](https://github.com/python-websockets/websockets) | BSD-3-Clause |
+| [PyYAML](https://github.com/yaml/pyyaml) | MIT |
+| [packaging](https://github.com/pypa/packaging) | Apache-2.0 OR BSD-2-Clause |
+
+**python-can is LGPL-3.0.** CANopen Bench imports it as an unmodified
+library and neither copies nor modifies its source, so the LGPL's
+obligations attach to python-can alone, not to CANopen Bench. If you
+redistribute a Docker image or any other bundle built from this
+repository, you are conveying python-can and must pass on its license
+text and let recipients replace it with a modified version — with a
+pip-installed package that is already the case, since it can simply be
+reinstalled.
+
+## Plugin packages
+
+Plugins are separate distributions with their own licensing; installing
+one does not change the license of this package. The public
+[`cob-cpcusb`](plugins/cob-cpcusb/)
+is MIT. Check each plugin's own `LICENSE` before redistributing an
+environment that contains it — a copyleft or proprietary plugin puts its
+own obligations on that environment.
+
+## Trademarks
+
+CANopen® and CiA® are registered trademarks of
+[CAN in Automation e.V.](https://www.can-cia.org/) CANopen Bench is an
+independent project and is neither affiliated with, endorsed by, nor
+certified by CAN in Automation. References to CiA specifications
+(CiA 301, CiA 305, CiA 402, …) describe which published behaviour this
+tool implements; they are not a claim of conformance, and this tool is
+not a CiA conformance test tool.
+
+IXXAT® is a trademark of HMS Networks. PCAN® is a trademark of
+PEAK-System Technik GmbH. CPC-USB is a product of EMS Dr. Thomas Wünsche.
+All other product names are the property of their respective owners and
+are used here solely to state which hardware this software interoperates
+with. Their use implies no affiliation with or endorsement by those
+companies.

canopen_bench-1.0.170/canopen_bench/__init__.py

@@ -0,0 +1,43 @@
+"""CANopen Bench — web tool to test and control CANopen devices."""
+import re
+from importlib.metadata import PackageNotFoundError
+from importlib.metadata import version as _pkg_version
+from pathlib import Path
+
+
+def _read_version() -> str:
+    """The one place the version is read from.
+
+    pyproject.toml first: this project bumps the version on every commit
+    and does not tag releases, so a source checkout is the normal way to
+    run it — and the installed metadata of an editable install goes stale
+    until the next `pip install -e`, happily reporting an old number.
+    Wheel installs have no pyproject next to the package and fall through
+    to the (then correct) metadata.
+
+    The file is scanned for the version line rather than parsed as TOML:
+    ``tomllib`` only exists from Python 3.11, and on 3.10 falling back to
+    the metadata would quietly reintroduce exactly the staleness this
+    function exists to avoid. Adding a ``tomli`` dependency to read one
+    line is not worth it.
+
+    Kept in this module rather than in ``core`` so that reading the
+    version costs no imports beyond the standard library.
+    """
+    try:
+        pp = Path(__file__).resolve().parent.parent / "pyproject.toml"
+        for line in pp.read_text(encoding="utf-8").splitlines():
+            # first `version = "..."` in the file; [project] declares it
+            # before any other table can (build-system has no version key)
+            match = re.match(r'\s*version\s*=\s*["\'](?P<v>[^"\']+)["\']', line)
+            if match:
+                return match.group("v")
+    except OSError:
+        pass
+    try:
+        return _pkg_version("canopen-bench")
+    except PackageNotFoundError:  # bare checkout without install
+        return "dev"
+
+
+__version__ = _read_version()