Translate PLC register maps into EPICS Modbus IOC configurations.
npx skills add https://github.com/BCDA-APS/opencode-skills --skill modbus
Please help me install this Agent Skill. Skill: modbus Source: https://github.com/BCDA-APS/opencode-skills/tree/main/modbus Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill modbus
Modbus register maps often take significant effort to convert into working EPICS IOCs, because you must correctly wire communication ports, protocol interposing, Modbus port drivers, and matching database records.
Configure an EPICS Modbus IOC by choosing the correct connection type (TCP/UDP/RTU/ASCII), creating modbus ports for each contiguous address range and function code, and then generating a substitution file that instantiates the appropriate database templates using the provided register offsets and data types.
High-intent search queries and answers about installing and using this skill.
Configuring an EPICS Modbus IOC involves translating PLC register maps into asyn port setup, modbus interpose framing, port drivers, and matching database templates. This process generates the required st.cmd logic and substitution files for PLC communication over TCP, UDP, RTU, or ASCII.
Mapping Modbus function codes to EPICS database templates requires selecting the correct function code (FC1/2/3/4/5/6/15/16/23) for your discrete I/O or holding/input registers. You then choose matching record templates like bit, word, analog, string, or arrays to handle the data types.
Writing multiple registers atomically in an EPICS Modbus IOC is supported using specific Modbus function codes. The configuration handles multi-register atomic writes by ensuring consistent data type byte and word order alongside precise OFFSET semantics for accurate record linking.
Incorrect float values during EPICS Modbus reads usually stem from inconsistent data type byte or word order configurations. Ensuring precise OFFSET semantics and consistent byte order matching between the PLC register map and the EPICS database templates corrects the read and write behavior.
The EPICS Modbus driver supports TCP, UDP, RTU, and ASCII connection types. You configure the appropriate asyn IP or serial port setup and modbus interpose framing to establish communication with your specific PLC and device communication scenario.
The correct OFFSET semantic for configuring EPICS Modbus port drivers can be either relative or absolute. Precise OFFSET configuration is required alongside accurate function-code selection to ensure that database template substitution entries read and write registers correctly.
rnbenFind nearby places using OpenStreetMap data by coordinates, addresses, city names, or zip codes.
BCDA-APSConfigure EPICS areaDetector IOCs with plugin chains and HDF5 file writers.
BCDA-APSConfigure EPICS motor IOCs for model-3 asyn motor deployments.
JNZader-VaultImplement Modbus protocol in Rust, Go, and Python for PLC data exchange.
