Write EPICS Channel Access client programs for PV reads, writes, and monitors.
npx skills add https://github.com/BCDA-APS/opencode-skills --skill epics-ca-client
Please help me install this Agent Skill. Skill: epics-ca-client Source: https://github.com/BCDA-APS/opencode-skills/tree/main/epics-ca-client Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill epics-ca-client
This Skill helps you write reliable EPICS Channel Access (CA) client programs that can connect to PVs, read and write values, and receive monitor updates with correct callback and error handling.
ca_get/ca_array_get and ca_put/ca_array_put, including completion callbacks for async operations.ca_create_subscription with appropriate DBE event masks for value/alarm/property changes.ca_pend_io() completes.Ask the AI to generate a C example that connects to a given PV, performs a synchronous DBR_DOUBLE read safely using ca_pend_io(), then installs a subscription that prints new values on change.
High-intent search queries and answers about installing and using this skill.
To write an EPICS Channel Access client in C, you create a CA context, establish channel connections, and use ca_create_subscription with appropriate DBE event masks to monitor Process Variables and trigger callbacks on value, alarm, or property changes.
Handling ca_get and ca_put callbacks in EPICS C programming requires using ca_array_get and ca_array_array_put with completion callbacks, then flushing the buffer with ca_flush_io and processing events via ca_pend_event or ca_pend_io to ensure data validity.
EPICS CA client data is only valid after ca_pend_io completes because the Channel Access protocol buffers I/O operations; reading DBR structures before pending I/O finishes returns uninitialized or stale values, violating core CA data validity rules.
You need specific DBR types for EPICS Channel Access monitoring when applications require value-only data, status, time stamps, graphic limits, or control properties; selecting the correct DBR code ensures the subscription callback receives the proper structure.
Yes, EPICS Channel Access supports both synchronous PV workflows using blocking ca_get and ca_put operations with ca_pend_io, and asynchronous workflows using completion callbacks and event-driven subscriptions with ca_pend_event in C client programs.
Managing CA context lifecycle in an EPICS C client involves creating the context, safely handling channel connect and disconnect transitions with connection callbacks, querying channel state, and properly destroying the context to avoid resource leaks.
BCDA-APSImplements EPICS PV Access client and server operations in C++.
urjitbhatiaMonitor, search, and manage terminal processes via the Brainlog MCP server.
BCDA-APSCreate custom EPICS areaDetector NDPluginDriver and NDPluginFile plugins.
BCDA-APSImplement EPICS PV Access clients in C++ using pvxs for typed operations.