as integer), with data 1234. Ethernet/IP SAS C:65
H
/I:A408
H
/A:01
H
= 1234 will be translated into rincmd:
2017A408:1234;.
Note
This method of accessing the Rincmd protocol relies on the PLC supporting 16bit
instances. These are widely supported. If your device does not support them, it is
recommended you use the Rincmd initiate and result instances within the Assembly
object (Section 20.3.3).
20.3.5 TCP Object (Class F5
H
)
The following table describes the attribute, status, and common services information for the TCP Object.
Instance Attribute
ID
Name Object Value Access
0 (Class) 1 Revision UINT 4 Get
1 1 Status UDINT See ODVA Vol 2: TCP/IP Object Status Get
1 2 Configuration
capability
UDINT See ODVA Vol 2: TCP/IP Object Configura-
tion Capability
Get
1 3 Configuration
control
UDINT See ODVA Vol 2: TCP/IP Object Configura-
tion Control
Get/Set
1 4 Physical
link object
Bytes Type Description Value
0-1 UINT Path Size 2 words
2-n
UINT
Array
Path
20
H
F6
H
24
H
01
H
Class: Ethernet Link F6
H
Instance: 1
Get
1 5 Interface
configura-
tion
Bytes Type Description Value
0-3 UDINT IP address From C500
4-7 UDINT Network mask From C500
8-11 UDINT Gateway address From C500
12-15 UDINT Name server 1 From C500
16-19 UDINT Name server 2 From C500
20-21 UINT Domain name size From C500
22-n STRING Domain name From C500
Get/Set
1 6 Hostname
Bytes Type Description Value
0-1 UINT Host name size From C500
2-n STRING Host name From C500
Get/Set
The services provided by the TCP object are as follows:
Service Code Service Name Class Level Instance Level
0E
H
GAS Yes Yes
01
H
GAA No Yes
10
H
SAS No Yes
20.3.6 Ethernet Link Object (Class F6
H
)
The following table contains the attribute and common services information for the Ethernet Link Object.
113 C500-600-2.0.3