Skip to main content

Crate epics_ca_rs

Crate epics_ca_rs 

Source
Expand description

EPICS Channel Access protocol — client and server.

This crate provides the CA wire protocol implementation, separated from the core IOC infrastructure in epics-base-rs.

Modules§

audit
Structured audit log for security-relevant CA server events.
calink
CA links for record INP/OUT fields — resolves CA-modified / ca:// record link fields to a live CA client (monitor-backed cache). Mirrors C dbCa.c / dbCaLink. Always compiled: having epics-ca-rs is enough to resolve CA links, no feature opt-in. calink — Channel Access links for EPICS record INP/OUT fields.
chaos
Optional fault-injection harness for testing.
cli
Helpers shared across the caget / caput / cainfo / camonitor command-line binaries.
client
discovery
Service discovery for CA — mDNS + DNS-SD.
observability
Optional helpers for wiring up tracing + metrics observability.
protocol
repeater
replay
On-disk recording and replay of CA observability events.
runtime
server
CA server components — TCP handler, UDP search, beacon, monitor.
tls
TLS configuration for Channel Access over TCP.

Structs§

PvString
A wire string: a sequence of bytes that is not guaranteed to be valid UTF-8. Backs EpicsValue::String/StringArray and (in epics-pva-rs) ScalarValue::String/TypedScalarArray::String. See the module docs for why this is a byte newtype rather than String.

Enums§

CaError
DbFieldType
EPICS DBR field types (native types only)
EpicsValue
Runtime value from an EPICS PV

Type Aliases§

CaResult