HAICU Control Script (haicu-ctl)
Overview
Package and command line utility for controlling and sequencing the MLD1200
Installation
The recommended installation method is via pip
To install/upgrade:
pip install -U haicu
To run it locally from the source (from the scripts/haicu directory):
python -m haicu
Usage
Command:
haicu-ctl [-h] [--version] [-v] [-l file] [-s SERIAL] [-j] {list,info,set,upload,program,convert,compare}
Purpose: Connects to an MLD1200 device and reads/writes registers, statuses, and memory. Also contains utility functions to create .RLE files for consumption by device.
Options:
-h or --help
Print out help for general usage or subcommand. Ie: haicu-ctl -h or haicu-ctl set -h
--version
Print out current version
-v or --verbose
Increase logging level, can be used multiple times
-l LOG_FILE or --log LOG_FILE
Specify log file name, instead of standard naming scheme
-s SERIAL or --serial SERIAL
Specify serial number of MLD1200 to connect to
-j or --json
For reads, format output in JSON. Only affects set (with no value), info, status, control, memory, and bread
The available subcommands are:
list- List of available MLD1200 devicesinfo- Get full report on MLD1200, all registers and status bitsset <regname> [data]- Allows human-readable setting of register values. If data is omitted, returns current value in registerupload <file> <section>- Upload a new sequence into MLD1200 from file. Choose section to load ('left','right','extension'). Does not start sequence.program [config_file] [--auto/-a]- Upload and start sequence. Can be passed a path to an INI file, otherwise tries to use 'haicu.ini' in current directory. The '--auto' option auto-reload the sequencer when it finishes, it will then start again on next trigger.convert <infile> <outfile>- Convert a derived format file 'infile' into RLE formatted file 'outfile'compare <derived_file> <rle_file>- Compare a derived file to an RLE file
Diagnostic subcommands:
memtest- Test the selected MLD by writing and reading random values to DDR memorystatus <addr>- Low level readback of status register at given addresscontrol <addr> [data]- Low level read/write of control registers. Omit 'data' to return current value at given addressmemory <addr> [data]- Low level read/write of DDR memory. Omit 'data' to return current value at given addressbread <addr> <count>- Low level block read of DDR memory section. Reads 'count' words out of DDR started at given address
Metadata
Release files for haicu 0.9.7
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 |
|---|---|---|---|---|
| haicu-0.9.7.tar.gz | 19.1 kB | Without provenance | Details for haicu-0.9.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| haicu-0.9.7-py3-none-any.whl | Python 3 | none | any | Details for haicu-0.9.7-py3-none-any.whl |
Total release size: 37.9 kB
Release files / haicu-0.9.7.tar.gz
| Download URL | haicu-0.9.7.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe3cda8b8ccd89adab690fd40b0b80c3ccb6c5cfd94615b4860209c38f9fe81c
|
|
BLAKE2b-256 checksum How to use checksums |
dca91261e96363fd4bde82a33d378d0219ddf65c565de8a11ce1e41a1cac73c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / haicu-0.9.7-py3-none-any.whl
| Download URL | haicu-0.9.7-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f789e69deb8d49fbbdf83a723b409a2fae604c32cf6d78d38bb66f03ebc91b7
|
|
BLAKE2b-256 checksum How to use checksums |
341c7d3fb859ec6681b8b3561b3c3f5df538173ff1b038efd0a2d3d67e10f2b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for haicu 0.9.7
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.