1 / 5

Access from SL-Equip to FESA

Access from SL-Equip to FESA. Kris Kostro SL/CO. Implementation. SL-Equip client. SL-Equip servers running on abcmw1 (Linux) Server to device mapping defined in the configuration DB (for SL-Equip and FESA) Generic Equip to FESA device name mapping (e.g. FAM_MEM or FAM_MEM -> FAMMEM

matt
Télécharger la présentation

Access from SL-Equip to FESA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Access from SL-Equip to FESA Kris Kostro SL/CO

  2. Implementation SL-Equip client • SL-Equip servers running on abcmw1 (Linux) • Server to device mapping defined in the configuration DB (for SL-Equip and FESA) • Generic Equip to FESA device name mapping (e.g. FAM_MEM or FAM_MEM -> FAMMEM • All SL-Equip modes are supported • SL-Equip action is used as FESA property • User options are supported • CMW exceptions returned as SL-Equip error messages R** W** X** SL-Equip Server get() set() CMW Infrastructure Naming Service Oracle DB FESA Server

  3. Implementation Cycle mapping SL-Equip client • In SL-Equip cycles are specified in hex ex: 0x211c0101 • In FESA cycles are specified as [[accelerator.]group.]what ex: SPS.USER.SFTPRO • Current mapping is • no cycle spec->no cycle spec • Any cycle -> SFTPRO • Is this sufficient for TZ? R** W** X** SL-Equip Server get() set() CMW Infrastructure Naming Service Oracle DB FESA Server

  4. Tested for the BOSTEP server (for SSIS) kostro 183% NEquip STEP_MOTOR1_Lgstat_RBR 5 ************************ *********** WELCOME TO NEquip *********** Reference of the equipment: Family [STEP] Member [MOTOR1] Action [Lgstat] Mode [RBR] No user option format double to receive *************** RESULTS **************** EQUIP call worked fine laps [1] min[554]max[554]mean[554] in ms Received 5 doubles : [78.89] [78.8878] [78.89] [0] [36] ************************

  5. Limitations • Family, member, action limited to 6 characters which limits device and property names in FESA • FESA properties must be Uppercase followed by lowercase letters (no backward compatibility for clients) • Accesses serialized in a single server (although more servers could be run for scalability) • Exception messages will be truncated to 80 characters • Cycle description mapping limited

More Related