Configure EPICS motor IOCs for model-3 asyn motor deployments.
npx skills add https://github.com/BCDA-APS/opencode-skills --skill motor-ioc
Please help me install this Agent Skill. Skill: motor-ioc Source: https://github.com/BCDA-APS/opencode-skills/tree/main/motor-ioc Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill motor-ioc
This Skill helps you configure and deploy EPICS motor IOCs correctly by providing reliable patterns for templates, substitution files, record semantics, and st.cmd startup ordering.
Configure an EPICS motor IOC for 4 model-3 asyn motor axes with an asyn IP port by using the provided st.cmd ordering, loading the motor record templates via substitution files, and initializing motorUtil after iocInit.
High-intent search queries and answers about installing and using this skill.
Configure a multi-axis EPICS motor IOC by generating correct database templates, substitution patterns, and st.cmd startup sequences for model-3 asyn motor deployments. This includes setting up asyn IP/serial communication, controller creation, and loading motor record fields with proper DTYP=asynMotor settings.
Correct st.cmd ordering for asyn motor IOC startup requires support registration, asyn port setup, controller creation, template loading via dbLoadTemplate, and motorUtilInit execution after iocInit to ensure proper initialization timing.
Incorrect engineering unit conversions in EPICS motor records usually stem from wrong MRES-based step/EGU conversions or improper @asyn(PORT,ADDR) OUT formatting. Apply correct motor record field mappings for resolution, direction, and offset to resolve the issue.
Yes, you should avoid problematic PINI settings when configuring EPICS motor IOCs. Proper configuration applies safe field semantics and correct motorUtilInit timing after iocInit while preventing settings that disrupt expected initialization behavior.
Yes, you can use dbLoadTemplate with substitution files to instantiate multi-axis motor record graphs in EPICS. This approach uses model-3 asyn motor template structures to define correct motor record fields, limits, and motion-control semantics.
The best way to set up asyn IP port communication for an EPICS motor controller is to follow safe st.cmd ordering for asyn port configuration, apply correct @asyn(PORT,ADDR) OUT formatting, and enable optional features like auto power and profile moves.
BCDA-APSConfigure asyn IP and serial ports in EPICS IOC startup scripts.
BCDA-APSImplement EPICS model-3 asyn motor drivers with controller and axis subclasses.
BCDA-APSGenerate EPICS StreamDevice .proto and .db definitions for byte-stream devices.
Sun-Lab-NBBImplement Zaber motor interfaces with zaber-motion for hardware discovery and axis binding.
