1 / 13

Property interfacing to Hardware: DevIO

This document covers the problem statement, DevIO concept, implementations, and how to connect properties with physical devices like sensors and motors. It delves into the DevIO architecture, including the Property Servant Implementation Class Diagram. The DevIO interface class template is explained, showcasing how properties can be linked to different DevIO implementations. It also discusses the drawbacks and proposes solutions for future DevIO developments.

arnoldd
Download Presentation

Property interfacing to Hardware: DevIO

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. Property interfacing to Hardware: DevIO ACS Development Team

  2. Contents • problem • DevIO concept • implementations • implementing new DevIO DevIO

  3. Problem Statement • Connecting properties with (physical) devices (sensors, motors, controllable units) in a generic way • This implies: • Communication with hardware device (points) • Data conversion (i.e. from raw data (binary, hex, …) into engineer units (ampers, …)) DevIO

  4. ACS Architecture DevIO

  5. Property Servant Implementation Class Diagram See p. 24, ACS Architecture DevIO

  6. Bridge pattern and DevIO • bridge design pattern is used: DevIO

  7. Implementation (C++) • DevIO: C++ abstract template class • DevIOMem: Default implementation provided by ACS • HW specific access provided by specific DevIOXXX implementation • one method for read and one for write data • example: • ROdouble/RWdouble uses read/write methods from DevIOXXX<double> DevIO

  8. DevIO Implementations • Current implementations: • Memory:DevIOMem • TICS: CAN bus:devIOCAN • APEX: Socket: DevIOSock, DevIOUDPSock • HPT: Shack-Hartmann sensor unit, Heidenhains encoder board, … • DevIOMem default implementation used by properties DevIO

  9. DevIO interface class Template <class T> class DevIO { public: virtual ~DevIO(){}; virtual bool initializeValue()=0; virtual T read(int& errcode, unsigned long long& timestamp); virtual void write(const T& value, int& errcode, unsigned long long& timestamp); };//class DevIO DevIO

  10. Usage • creating a property that uses the default DevIO (DevIOMem):p = new ROdouble(…, …); • createing a property that uses another DevIO (DevIOXXX) implementation: m = new devIOXXX<double>(…);p = new ROdouble(…, …, m); • accessing a DevIO DevIO *dev = p->getDevIO(); DevIO

  11. Drawbacks • It may need different implementation for different conversions • Split: • Conversion • communication (read & write) DevIO

  12. New DevIO implementation • Inherit DevIO template class • Implement: • read • write (if needed) DevIO

  13. References • ALMA Common Software Architecture, ALMA-SW-0016 • ALMA Common Software Release Notes • ACS web site DevIO

More Related