Skip to main content

RfSoC Interaction Handler

Generic interface for interacting with the RfSoC.

API Calls

InteractionHandler(ip_address)

Creates an instance of the handler. Needs the IP address of the RfSoC to connect.

SerialInteractionHandler(port, bautrate, timeout)

Creates an instance of the handler but for serial communication via pyserial. The port name is needed, everything is initialized with the values from the RfSoC and shouldn't be changed unless you changed settings on the RfSoC.

Parameters:

  • ip_address (str) — IP address of the RfSoC.

send_message(instruction, par)

Sends a command message with the given instruction and parameter.

Parameters:

  • instruction (str) — The instruction to be sent.
  • par (int) — The parameter to send with the instruction.

send_start()

Starts the streaming engines of the RfSoC.
Depending on the trigger setting it either:

  • starts sending and generates a trigger, or
  • waits for an incoming trigger.

send_stop()

Stops the streaming engines and the DACs.


send_set_trigger_in()

Configures the RfSoC to receive a trigger.


send_set_trigger_out()

Configures the RfSoC to send out a trigger.


send_data(filepath)

Sends a signal file to the board and stores it in the database.
The filename will be used for saving the file on the RfSoC.

Parameters:

  • filepath (str) — Path to the file that should be sent.

select_signal(channel_id, filename)

Selects the signal for a given channel from a filename.
The file must be uploaded to the RfSoC first. Otherwise, this will throw an error.

Parameters:

  • channel_id (int) — Channel ID to use (0–7).
  • filename (str) — Name of the signal file to be loaded.

list_files()

Prints a list with all files that are uploaded. The location on the RfSoC and the creation time is given.


delete_signal(filename)

Deletes the file from the database and from the drive.

Parameters:

  • filename (str) — Name of the signal file to be deleted.

set_freq(frequency)

Sets the sampling frequency of the DACs. Due to clock divider issues some frequencies are not allowed but currently there is no sanity check (will be added in the future). The maximum frequency is 168.75hz (for now).

Parameters:

  • frequency (int) — The target frequency in Hz

set_sending_mode(mode)

Sets the sending mode of the RfSoC. Currently it can be toggled between sending a single transmission and stream out periodically.

Parameters:

  • mode (int) — Allows changing between two modes for now: 0 -- Stream Mode 1 -- Single Transmission mode

set_scaling(scaling)

Sets the scaling of the signal. The scaling can be an arbitrary value between 0 and 1 with two digits maximum precision.

Parameters:

  • scaling (float) — The scaling factor of the signal between 0 and 1 (two digits max)

Metadata

Release files for rpc_rfsoc_handler 1.1.6

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

Source distribution (sdist)

Source distribution for rpc_rfsoc_handler 1.1.6
File Size Uploaded Provenance
rpc_rfsoc_handler-1.1.6.tar.gz 5.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for rpc_rfsoc_handler 1.1.6
File Interpreter ABI Platform
rpc_rfsoc_handler-1.1.6-py3-none-any.whl Python 3 none any Details

Total release size: 13.4 kB

Release files / rpc_rfsoc_handler-1.1.6.tar.gz

Download URL rpc_rfsoc_handler-1.1.6.tar.gz
Size 5.7 kB
Tags Source
SHA-256 checksum
How to use checksums
deee149b20a5f7d971126259170ff348baec8c3ce74ea243aacafbcddfe1b49f
BLAKE2b-256 checksum
How to use checksums
31b2598587fb9650cb6486f50bfb203ba44ef4be2099dde571eda77a7d88c152
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / rpc_rfsoc_handler-1.1.6-py3-none-any.whl

Download URL rpc_rfsoc_handler-1.1.6-py3-none-any.whl
Size 7.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7ba2e45b4aec2aa18332570d226dadf4832cd19b1ab01e913cd60f51cdf06288
BLAKE2b-256 checksum
How to use checksums
c7e8e49122d73fdefde6b9e9ca200479b2905543244bf0beff554ef45368eee4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for rpc_rfsoc_handler 1.1.6

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.

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