10. Appendix D: DeviceNet Objects
10.3. Graphical Representation of the Gateway’s DeviceNet Objects
LUFP9 gateway memory
|
|
|
|
|
|
|
|
|
|
|
|
16#0000 |
| 16#01FF | 16#0200 |
| 16#03FF | 16#0400 | 16#07FF | ||||
| Input data (1) |
|
|
| Output data (1) | General data area | |||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Applicative |
|
| |
|
|
|
|
|
|
|
|
| Objets |
|
|
|
|
|
|
|
|
| I/O Data Output |
| Diagnostic | ||
|
|
|
|
|
|
| Mapping Object |
| Object | ||
|
|
|
| I/O Data Input |
|
|
|
|
| ||
|
|
|
| Mapping Object |
|
|
|
|
| ||
|
|
|
|
|
|
|
|
|
| Identity | |
|
|
| Acknowledge |
|
|
| Object | ||||
|
|
| Handler Object |
|
|
|
|
| |||
| Assembly |
|
|
|
|
| Message | Objets Reserved | |||
| Objects |
| I/O |
|
| Explicit |
| Router | for Communications | ||
|
|
|
|
|
|
|
| DeviceNet | |||
|
|
| Connections |
|
| Messages |
|
|
| Object | |
| The classes which | Connection Object |
|
|
|
|
| ||||
| correspond to the |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |||
| grey objects are |
|
|
|
|
|
|
|
|
| |
| required |
|
|
|
|
| DeviceNet network |
|
| ||
|
|
|
|
|
|
|
|
|
|
|
|
(1)The input and output data areas can be read or written either using “I/O connections” or using “explicit messages”.
10.4. Identity Object (class 16#01)
The “Identity” object only has a single instance (Instance ID = 16#01). This object contains general information allowing you to identify the gateway and diagnose its status. This object is described in chapter
Attributes of class 16#01
ID | Access | Name | Need | Type | Value | Description |
16#01 | Get | Revision | Required | UINT | 1 | Major and minor indices for the revision of the “Identity |
|
|
|
|
|
| Object”. |
Services in class 16#01
Service code | Name of the service | Need | Description |
16#0E | Get_Attribute_Single | Required | This service allows the value of one of the attributes of the class to be |
|
|
| read. |
95
