LouCOMAX_Controllers
Controllers for hardware in the LouCOMAX Project.
Overview
LouCOMAX_Controllers is a collection of software modules designed to interface with and control various hardware components used in the LouCOMAX Project. The controllers provide reliable communication, automation, and monitoring for supported devices.
The following hardware devices are interfaced within this package :
- Amptek DP5, PX5, DP5X, DP5G, MCA8000D, Mini-X2 and products derived from these (X123, X55, Gamma-Rad5, TB-5).
- iMOXS/2® Control Service Unit for X-Ray Source
- Specific setup of Arduino with telemetry laser : HG-C1100-P
- Thorlabs' BCS203 with NanoMax300 micropositioning stages
- Zaber multi stage daisy chain (contains 3 stages XYZ)
Note : The modules were initialy developped for specific hardware setup on LouCOMAX project. It may not be usable as is for some setup too different. Please feel free to contribute to the github or ask questions to developper.
Features
- Modular controller architecture for easy extension
- Support for multiple hardware interfaces (e.g., serial, USB, Ethernet)
- Logging and error handling
- Example scripts for common hardware tasks
Getting Started
-
Clone the repository:
git clone https://github.com/abpydev/LouCOMAX_Controllers.git -
Install dependencies:
Refer to therequirements.txtor relevant setup instructions for your platform. -
Run an example controller:
python controllers/example_controller.py
Directory Structure
LouCOMAX_Controllers/
├── controllers/ # Main controller modules
├── examples/ # Example usage scripts
├── tests/ # Unit tests
├── README.md # Project documentation
└── requirements.txt # Python dependencies
Initial developpers
Developped by :
- Antoine BLASIAK : antoine.blasiak66@gmail.com
Other contributors :
- Laurent PICHON : laurent.pichon@culture.gouv.fr
Contributing
Contributions are welcome! Please open an issue or submit a pull request.
License
This project is licensed under the MIT License.
Metadata
Release files for loucomax-controllers 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| loucomax_controllers-1.0.3.tar.gz | 88.1 MB | Without provenance | Details for loucomax_controllers-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| loucomax_controllers-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for loucomax_controllers-1.0.3-py3-none-any.whl |
Total release size: 176.3 MB
Release files / loucomax_controllers-1.0.3.tar.gz
| Download URL | loucomax_controllers-1.0.3.tar.gz |
|---|---|
| Size | 88.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af215b69711f142a501131e17c429a577d87e09f5d3a2fb03aa56ac96bf1d61e
|
|
BLAKE2b-256 checksum How to use checksums |
9bc215125a40cbd6fac237c01f383bc40025b1adc7c40f7baf59aa0850be8e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Release files / loucomax_controllers-1.0.3-py3-none-any.whl
| Download URL | loucomax_controllers-1.0.3-py3-none-any.whl |
|---|---|
| Size | 88.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db692b1a57a7059721ca289a421ee9b1dcea63ba7c88371e85c9573593728e71
|
|
BLAKE2b-256 checksum How to use checksums |
0cf8a4efc62b916a87ccc690b72cb85950522590d23c1cb3b1388c99028cacc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Security for loucomax-controllers 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.