Generate EPICS StreamDevice .proto and .db definitions for byte-stream devices.
npx skills add https://github.com/BCDA-APS/opencode-skills --skill streamdevice
Please help me install this Agent Skill. Skill: streamdevice Source: https://github.com/BCDA-APS/opencode-skills/tree/main/streamdevice Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill streamdevice
Writing EPICS StreamDevice support often requires careful, error-prone formatting of byte-stream commands and record link strings, especially when devices use serial/TCP/GPIB protocols and non-trivial reply parsing.
Use the streamdevice skill to draft a StreamDevice .proto protocol and matching EPICS .db records for a device command/response pair over your configured bus (serial, TCP/IP, or GPIB).
High-intent search queries and answers about installing and using this skill.
To generate StreamDevice protocol files, define linear request/reply sequences for byte-stream devices using .proto syntax, including timeouts, terminators, and error handlers for serial, TCP/IP, or GPIB buses.
EPICS database records use DTYP = "stream" and reference protocol blocks via INP/OUT link formats. The generated .db files bind record fields to byte-stream command sequences and format converter parsing rules.
StreamDevice format converters support numeric, string, raw binary, regex-based extraction, checksums, and timestamp handling. They manage record field redirection, array parsing, and %r precision versus width specifications.
StreamDevice protocol arguments use $1-$9 syntax for variable substitution within command sequences. Exception handlers are defined within protocol blocks to manage error conditions, ensuring robust byte-stream communication parsing.
StreamDevice supports byte-stream devices across serial, TCP/IP, and GPIB buses. Protocol definitions and record links are generated to handle command/response pairs over any configured bus interface.
StreamDevice handles array elements and checksums using pseudo-converters within format converter rules. These parse multi-value replies and validate data integrity across byte-stream device responses.
BCDA-APSConfigure asyn IP and serial ports in EPICS IOC startup scripts.
BCDA-APSImplement asynPortDriver-based EPICS device drivers with parameter interfaces and callbacks.
BCDA-APSCreates and configures IOC apps and modules with Bazel build system and runtime startup behavior.
ovachieverControl laboratory liquid handlers and devices through a unified Python interface.
