• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Anatomy Of A Cdp Application
 

Anatomy Of A Cdp Application

on

  • 1,199 views

Presentation of the main components to any CDP application, the control system design platform. ...

Presentation of the main components to any CDP application, the control system design platform.
With CDP you can easily create safe and advanced, redundant and fast control system that run on COTS.
CDP is a middleware for making safety critical control systems

Statistics

Views

Total Views
1,199
Views on SlideShare
1,199
Embed Views
0

Actions

Likes
1
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Hello and welcome to thesecond episode of CDP introductory videos.

Anatomy Of A Cdp Application Anatomy Of A Cdp Application Presentation Transcript

  • CDP basic, episode 2 Anatomy of a CDP application A CDP application consists of Components and their XML files Objects Signals Parameters Alarms State machine Subcomponents Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture CDP Components  The component assembles functionality in one logical unit, making it easier to get an overview of the control system.  All CDP-components have a unique name:  ‘AHCRemotePanel’  ‘AHCRemotePanel.WebServer’  ‘AHCRemotePanel.AHCPanel.Setup.DrumHelp’ Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture CDP Components Contents:  Signals  Parameters  Messages  Alarms  State machine  Subcomponents  Component connectors  Optionally additional execution threads  Configuration in .xml file Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture Component .xml files  A component has a model .xml and an instance .xml.  The model .xml file defines properties common to all components of a specific type. The model .xml files are located in the folder ‘ApplicationModels’.  The component .xml file specifies properties for one specific component, such as parameter values and signal routing. The component files are located in ‘ApplicationComponents’ and sub- folders.  See Appendix A for example model/component files. Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture CDPObject  The CDPObject is the base class for all addressable objects in CDP. It provides objects with a human readable name/address, which gives the object the possibility to receive messages. CDPObjects are registered hierarchically in the CDP system, allowing management in an object- oriented way.  Has a system-wide unique Name (Maximum 256 characters long, of which the 'short name' or component-relative name is maximum 32 characters).  All names map to auto-generated 'handles' (32-bit integers) in the CDP system, but this is invisible to the end-user. All object access is done by using names. Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture Signals  Signals are dynamic values which change over time.  Can be input or output.  Signals can be routed so that the value is retrieved from another signal, this is done by specifiyingRouting=‘SomeComponent.SignalName’ for the signal in the component .xml.  Signals can be monitored in the CDPBrowser or Internet Explorer Signal .xml example, excerpt from component .xml: <Signals> <SignalName=quot;Inputquot;Type=quot;doublequot;Input=quot;1quot;Value=quot;0quot;Routing=quot;MyApp.Outputquot;></Signal> <SignalName=quot;Outputquot;Type=quot;doublequot;Input=quot;0quot;Value=quot;0quot;Routing=quot;No routingquot;></Signal> </Signals> Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture Parameters  Parameters are persistent values, they are stored to disk so that the value is retained when the controller is switched off.  The value seldom changes.  Only available inside owner component, no routing.  When a parameter is changed the new value is written to a storage unit, such as a flash-disk.  Parameters can be set from the CDPBrowser or Internet Explorer.  Parameters are named ‘Parma’ in the .xml. Parameter .xml example, excerpt from component .xml: <Parameters> <ParmaName=quot;Offsetquot;Value=quot;0.0quot;TimeLastChanged=quot;Tue Dec 14 16:42:17 2004quot;Description=quot;quot;></Parma> <ParmaName=quot;Amplitudequot;Value=quot;1.2quot;TimeLastChanged=quot;Tue Dec 12 12:42:19 2004quot;Description=quot;quot;></Parma> <ParmaName=quot;Frequencyquot;Value=quot;5quot;TimeLastChanged=quot;Tue Dec 14 16:42:10 2004quot;Description=quot;quot;></Parma> </Parameters> Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture Alarms  Alarms notifies when something is wrong  Can be displayed on screens (CDPUI) and CDP tools  Can be set-up to trig on signals (filtered, value, mask).  Can be activated or disabled by component state  Can set signals or send message to a component  Can block component states  Can have time delay before it is set to avoid faulty triggering due to noise  Components monitor all its alarms and sets ’Status’ according to worst alarm status  Multiple levels: Notify, Warning and Error, and Low and High for signal levels Alarm .xml example, excerpt from component .xml: <Alarms> <AlarmName=quot;Loadcellcablebreakquot;Level=quot;Warningquot;Enabled=quot;1quot;Trig=quot;0quot;Signal=quot;.Loadcellquot;Mask=quot;0x0002quot; EnabledState=quot;Onlinequot;Text=quot;Cablebreak detected on signal from loadcell 1 of AHC winch.quot;> </Alarm> </Alarms> Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture State machine  A CDP component has a state machine:  Functionality implemented in the code for existing state is run periodically  States and state transitions are always determined, it is impossible to enter an invalid state  The start-up state is always ‘Null’ if the component .xml does not specify a different <InitialState>.  The state machine runs at periodic interval <fs>, specified in component .xml (Model .xml defines default values for <fs> for all components of a given type). Industrial Control Design AS www.icd.no +47 93 07 32 30
  • Architecture Subcomponents  A component can have subcomponents, or, it can be a subcomponent.  Subcomponents are owned by another component  When a subcomponent is specified inside a component, it is automatically created when the controller starts .xml example, excerpt from component file: <Subcomponents> <SubcomponentName=quot;Spoolingquot;Type=quot;SpoolingDevicequot;src=quot;ComponentsSpooling.xmlquot;></Subcomponent> </Subcomponents> Industrial Control Design AS www.icd.no +47 93 07 32 30