1. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 ODVA Object & Device Profile Definition (Process & Recommendations) System SIG 1998 Annual Meeting

2. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Core System SIG Members Allen-Bradley Control Technology Cutler-Hammer National Instruments OMRON Turck

3. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

4. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 1: Create a SIG If an appropriate Special Interest Group does not exist, contact the Chief Technical Officer of Technical Review Board Submit a SIG Charter to TRB A call for participants will be distributed to all ODVA members SIG Creation

5. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 2: First Meeting Determine voting rules Clarify scope of SIG Submit final charter to TRB for approval SIG Creation

6. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

7. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 3: Begin Profile(s) Initially focus on sensor/actuator Define minimal device functionality first EXAMPLE: Throttling Valve Identifying Objects

8. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 4: Identify Preliminary Object(s) Use physical view as first guess Position Identify inputs Identifying Objects

9. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

10. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 5: Create Instance Attribute Table Since all instances have a state transition diagram, recommend State as attribute identifier #1 (Assumes Invalid State for Service error response is supported.) Place input(s) as next attribute(s) Control Attributes NOTE: Object definition INDEPENDENT OF SUBNET

11. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 6: Define Semantics of Position Range of Position from zero (0) to one hundred (100) percent (or full range based on data type?) Zero (0) percent is closed One hundred (100) percent is fully open Control Attributes

12. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 7: Determine Data Type of Position Should Position have 100 increments, 1000 increments, or 10000 increments? (See Appendix J, Volume I for data types) Control Attributes

13. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 8: Create Attribute Descriptions Further clarify any value restrictions or support requirements in attribute descriptions following Instance Attributes table. Position Value determines desired valve position in hundredths of a percent, where zero (0) is fully closed, 10000 is fully open. Some valves may not support the full resolution, but shall accept full range of values. Values greater than 10000 shall be interpreted as fully open. Control Attributes

14. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 9: Identify object Outputs Setpoint Actual To avoid confusion, input name changed to Setpoint Control Attributes

15. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Start Simple Review existing objects for possible reuse Add functionality maintaining technology independence (positioner may be pneumatic, stepping motor, etc.) Step 10: Inheritance Basic Throttling Valve State Setpoint Throttling Valve + Actual Throttling Valve + Zero + Span NOTE: When making decisions THINK OF THE CUSTOMER!

16. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 11: Add Attribute Description Actual Value identifies actual valve position in hundredths of a percent, where zero (0) is fully closed, 10000 is fully open. Some valves may not support the full resolution, thus providing actual indications in greater increments, like; 0, 100, 200 and so forth. This attribute is optional. Control Attributes

17. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

18. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 12: Define Behavior Use template NON-EXISTENT IDLE RUNNING Create or Power Up/ Delete or Power Down/ Set or Get Attribute/ Apply/ Reset/ NON-EXISTENT IDLE RUNNING IDLE Behavior Get Attribute/ RUNNING

19. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

20. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 13: Identify Configuration Attributes Relative to IDLE state, are there any configuration attributes? Configuration Attributes NOTE: Send Member to System SIG and Conformance SIG EARLY in definition process.

21. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 14: Attribute Relationships Does a common calibration behavior exist? Does Zero adjust affect Span? Device Calibration To calibrate, place valve in IDLE state via an explicit Reset service. ZERO ADJUST: While in IDLE state, perform a Set Attribute on Setpoint with a value of zero (0) to the instance. Visually check valve. If partially open, perform a Get Attribute of Zero, decrement value by desired amount, then perform a Set Attribute to Zero attribute. Continue until valve is fully closed. SPAN ADJUST: While in IDLE state, perform a Set Attribute on Setpoint with a value of 10000. Visually check valve. Depending upon position, perform a Get Attribute of Span and increment/decrement value by desired amount, then perform a Set Attribute to Span attribute. Increment or decrement value until valve is fully open. Configuration Attributes

22. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 15: Complete Attribute Definition Zero If optional attribute supported, it shall be maintained in Non Volatile memory. Value may be factory set, therefore, a default value does not exist. Value may only be set while in IDLE state. Span If optional attribute supported, it shall be maintained in Non Volatile memory. Value may be factory set, therefore, a default value does not exist. Value may only be set while in IDLE state. NOTE: Signed 16 Bit integers used here. Configuration Attributes When is value saved to non volatile memory? Prior to a Set Attribute Response? Only upon receipt of a Save or Apply request to the Throttling Valve object? (For consistency with other objects, specify in Device Profile, not in Throttling Object profile.)

23. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 16: Define Unique Dialogs Define dialogs when an unsupported value is set within node. Client Configuration Tool Throttling Valve Node Set_Attribute_Req, Throttling_Valve, 1, Setpoint, 870 Node accepts 800 or 900, not 870 Set_Attribute_Resp, 800 Success response contains actual value accepted.

24. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 17: Revise Object Profile Setpoint Value determines desired valve position in hundredths of a percent, where zero (0) is fully closed, 10000 is fully open. Values greater than 10000 shall be interpreted as fully open. Some valves may not support the full resolution, but shall accept the full range of values. For this attribute, the successful response to a Set Attribute Single shall always contain the value accepted, which shall be rounded down when full range not supported. EXAMPLE: Set_Attribute_Req, Throttling_Valve, 1, Setpoint, 870 Set_Attribute_Resp, 800

25. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 18: Class Attributes All objects in Volume II have been updated to reference a common set of class attributes shared by all classes. Specify in Device Profile if any class attributes are required. Only specify additional class attributes, when necessary. Configuration Attributes

26. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

27. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 19: Define IO Assemblies Input Assembly Instance 2Output Assembly Instance 1 IO Assemblies Size (length) of Assemblies are currently fixed, since IO Messages of lengths other than that specified by the consumed connection size may result in an error at the consuming node. This may be due to invalid configurations between two nodes. (Deviations SHALL be specified in Device Profile.)

28. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 20: IO Assemblies Selection Device Net Connection (Polled IO) Assembly [7] Assembly [6] Assembly [5] Assembly [4] Assembly [3] Assembly [2] Assembly [1] produced_connection_path consumed_connection_path Generic Tools prefer Assembly instance specified using Appendix I, Logical Encoding. ( EXAMPLE: Class8, Assembly, Instance8, 1, Attribute8, Data ) ( Required support & encoding defined in Device Profile ) IO Assemblies Client tools shall set; consumed size, consumed_connection_path, produced size, produced_connection_path, consistent with length of produced and consumed assemblies.

29. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 21: Dynamic Assemblies (Create service conditional on Dynamic Assembly support.) Device Net Connection Polled Assembly [0] ACTIVE RUNNING ESTABLISHED CreateResp, 100 Explicit Response External Events SetAttribSingle, Assembly, 100, MemberList,..Actual.. SetAttrib, MemberList,..Actual.. Explicit Request SetAttrResp Explicit Response ApplyResp Explicit Response Apply, Assembly, 100 Apply Explicit Request ACTIVE Explicit Request Create, Assembly, 0 Assembly [100] NON EXISTENT INACTIVE Create Does transition of Assembly [100] from INACTIVE to ACTIVE guarantee that all informationin the Member List attribute is valid? (Define meaning of ApplyResp in Device Profile.)

30. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 22: IO Assemblies Selection Device Net Connection (Polled IO) Assembly [100] {Member List::= Class8,Valve, Instance8, 1 Attrib8, Actual Class8,Identity, Instance8, 1 Attrib8,Status} IO Assemblies Throttling Valve State, Actual, Setpoint Identity Status, Member List of Dynamic Assembly instance specified using Appendix I, Logical Encoding. If desired, rules on layout order defined. (Required encoding defined in Device Profile)

31. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

32. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 23: Create Device Profile Identify required & optional objects (DeviceNet, Connection, Identity, Message Router) Identify object relationships and dialogs Device Model Message Router Device Net Connection (Polled IO) Assembly [2] (Produced Input) Assembly [1] (Consumed Output) Throttling Valve Connection (Explicit) Identity Connection (Cyclic/COS IO) Ack Handler

33. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

34. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 24: Identify External Events Receive Idle (Zero length IO Message) Receive Data (Normal IO Message) Receive Data (Invalid length IO Message) Receive Data (Invalid local configuration) Local Power Applied (Subnet power applied before local) Local Power Removed (while Subnet power applied) Object Faults Device Modes (Manual, Auto, Program, Calibrate) External Events

35. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 25: Identify Master Sequence of Events NON-EXISTENT IDLE INACTIVE Create or Power Up/ Delete or Power Down/ Set or Get Attribute/ Scanner Started/ Allocate & Send Idle Messages Scanner Reset/ Stop Sending IO Messages NON-EXISTENT IDLE INACTIVE ACTIVE Application Started/ Send IO Messages ACTIVE Application Stopped/ Send Idle Messages INACTIVEIDLE External Events Vendor Specific behavior INACTIVE

36. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 26: Define Normal Behavior (Assume all objects in operational state) Message Router Device Net Connection (Polled IO) Assembly [2] (Produced Input) Assembly [1] (Consumed Output) Throttling Valve Connection (Explicit) Identity Connection (Cyclic/COS IO) Receive Data Device Net Connection (Polled IO) Received Data Setpoint Assembly [1] (Consumed Output) Actual Throttling Valve Assembly [2] (Produced Input) Actual Poll Response Connection (Polled IO) Device Net Poll Response External Events Ack Handler

37. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 27: Message Sequence Chart (First Receive Data Event) Device Net Connection Polled Assembly [1] Assembly [2] Throttling Valve INACTIVE IDLE RUNNING ESTABLISHED Poll Request INACTIVE Receive Data ACTIVE Setpoint RUNNING Actual Poll Response Actual ACTIVE Is receipt of Setpointan implied Apply OR ignored if not RUNNING? (Clarify in Device Profile) External Events

38. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 28:Message Sequence Chart ( Receive Idle Event while RUNNING) Device Net Connection Polled Assembly [1] Assembly [2] Throttling Valve ACTIVE RUNNING ESTABLISHED Poll Request ACTIVE Receive Idle RUNNING Actual Poll Response Actual? DoesAssembly detect zero length message and Reset valve OR does Assembly pass Position = 0 to valve? (Clarify in Device Profile) ? IDLE? Is there a response to a Receive Idle? (Clarify in Device Profile) External Events

39. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 29:Message Sequence Chart ( Connection Timeout Event while RUNNING) Device Net Connection Polled Assembly [1] Assembly [2] Throttling Valve ACTIVE RUNNING ESTABLISHED ACTIVE End of Consumption INACTIVE RUNNING (Define inter object dialogs within Device Profile.) IDLE ResetEnd of Production INACTIVE TIMED OUT External Events

40. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 30: Update Behavior (if required) NON-EXISTENT IDLE RUNNING Create or Power Up/ Delete or Power Down/ Set or Get Attribute/ Apply/ Reset/ External Events Get Attribute/ If setting of some or all attributes allowed in this state, clearly specify in object profile. ODVA RULING: If a Set Attribute is allowed on Setpoint while in RUNNING state, it shall be overwritten by the next consumed IO Message. If only Explicit Messages are used for control (no IO Message allocated), connection timeout faults may not be detected unless specified otherwise in Device Profile!

41. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 31: Update Behavior If COS, is an Actual IO Messages sent upon receipt of Setpoint, then at interval equal to production inhibit time? Is an error generated if Actual <> Setpoint after a period of time? 100 90 80 70 60 50 Setpoint = 90 @ t4 010203040 Time Actual External Events If Actual attribute wanders, does valve continually produce IO Messages at interval equal to production inhibit time or is adead band attribute required? (Specify desired behavior in Device Profile.)

42. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 32: External Events A good Device Profile has evidence that the various event scenarios were discussed, resolved and SIG decisions documented. (DSE-68-59) External Events DO NOT place communications specific signals in Application Objects. The RELATIONSHIPS shall be placed in the Device Profile.

43. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

44. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 33: Device Fault Indications Assume previous Fault Events occurred in device. How does a controller or tool know what happened? TODAY: Generally Vendor Specific behavior, with few profiles specifying how specific faults are determined. (Indication in Heartbeat or Bit in Produced IO Message) Fault Behaviors

45. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 34: Existing Profiles Fault Behaviors

46. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 35: Determining Fault Details Device Profile should specify a common interface to read faults, even when they are vendor specific. Common interface simplifies user programming. Common interface allows support by general tools. Fault Behaviors

47. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 36: Queue for Faults System SIG defining a common object where all faults may be retrieved via Explicit Message requests. Prefer faults be encoded using Appendix I/J for interpretation by common client dialog. Fault Behaviors

48. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 37: Sample Dialog Device Net Connection Polled Throttling Valve Queue RUNNING ESTABLISHED Insert Member, Valve, 1, Position Timeout RUNNING Connection Explicit ESTABLISHED FAULTED Assembly [2] ACTIVE Explicit Request Remove Member, Queue, 1, List, 1 1,C8,Valve,I8, 1,UINT, Position Timeout Explicit Response Poll Response IO Message Await client diagnostic application delay Poll Request Fault Behaviors Error Flag (bit 7 = FALSE) Await next scan delay Error Flag (bit 7 = TRUE)

49. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

50. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 38: Test Plans SIG submitting the Device Profile to the TRB shall provide Test Plan to the Conformance SIG Test Plan shall ONLY test items specified in Device Profile Test Plan shall test items specified in related Application Objects Test Plans

51. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Device Profiles SIG Creation Identifying Objects Control Attributes Behavior Configuration Attributes IO Assemblies Device Model External Events Fault Behaviors Test Plans Electronic Data Sheets

52. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Step 39: Electronic Data Sheets SIG submitting the Device Profile to the TRB shall provide an EDS to the Conformance SIG EDS shall ONLY contain items specified in Device Profile EDS shall contain items specified in related Application Objects EDS

53. ODVA System Architecture SIG ©1998 ODVA DeviceNet \slides\ODVA 98 Prior to submittal of DSE to TRB; DSE shall have signatures of SIG members Updated specification sections Test Plan Prototype EDS Step 40: SIG Deliverables