asyn-port-config

Configure asyn IP and serial ports in EPICS IOC startup scripts.

1|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BCDA-APS/opencode-skills --skill asyn-port-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asyn-port-config
Source: https://github.com/BCDA-APS/opencode-skills/tree/main/asyn-port-config
Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill asyn-port-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of configuring EPICS asyn communication ports correctly in st.cmd so instruments and clients reliably connect, exchange data with the right EOS handling, and can be debugged when things go wrong.

Core Features & Use Cases

  • IP port setup for clients and servers: Configure asyn IP ports for TCP/UDP/HTTP and TCP servers with appropriate connection behavior.
  • Serial port setup with operational parameters: Create serial ports on Linux/Windows device names and apply baud/bits/parity/stop and flow-control options via asynSetOption.
  • EOS, tracing, and connection diagnostics: Set input/output EOS for text protocols, enable targeted asyn trace masks and I/O formatting, redirect trace output, and validate connectivity using asynRecord-style commands.

Quick Start

Use the asyn-port-config skill to generate a complete st.cmd snippet that configures a TCP instrument port with correct EOS, enables useful trace output, and positions the dbLoadRecords calls after the port configuration.

Frequently Asked Questions about asyn-port-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure asyn ports for TCP and serial communication in an EPICS IOC?

To configure asyn ports in EPICS, you define TCP, UDP, or serial connections in the st.cmd startup script using appropriate hostInfo, serverInfo formatting, and serial options like baud and parity via asynSetOption.

What is the correct way to set EOS for octet I/O in EPICS asyn ports?

Setting EOS for octet I/O in EPICS asyn ports involves defining specific input and output end-of-string characters within your st.cmd configuration to ensure text protocols exchange data reliably without truncation.

How do I enable asyn trace masks for debugging EPICS IOC connections?

Enabling asyn trace for EPICS IOC debugging requires applying targeted trace masks and I/O formatting commands in the startup script to redirect diagnostic output and validate instrument connectivity.

When should I load database records relative to asyn port configuration in st.cmd?

Database records must be loaded after completing the asyn port configuration and connection management ordering in st.cmd to ensure the EPICS IOC initializes the underlying communication channels successfully.

Can I use asynSetOption to configure flow control for serial ports on Linux?

Yes, you can use asynSetOption in the st.cmd script to apply operational parameters like baud, bits, parity, stop bits, and flow-control options for serial ports using Linux or Windows device names.

What is the best way to set up an asyn TCP server port in an EPICS IOC?

Setting up an asyn TCP server port in EPICS requires using the correct serverInfo formatting in the st.cmd script to establish appropriate server-side connection behavior for incoming client requests.