Implemented cip™ objects – Lenze E84DGFCG User Manual

Page 115

Advertising
background image

Implemented CIP™ objects

General CIP objects

115

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Instance attributes for input data of the scanner

The assembly input objects (adapter to scanner) are mapped in the adapter memory starting with

byte 0.
The input objects are transmitted in a "modeless" manner, i.e. a 4-byte header is not included in the

transfer.
So the start address in the assembly memory map is the actual start of the first assembly data

element.
Please observe the actual assembly lengths when mapping the input objects to the controller

memory.
The

Lenze Class (103 / 0x67)

( 141)

provides the image of the input data of the scanner.

Attribute

ID

Service

Name

Data type

Value

3

Get / Set Data

ARRAY of

SINT / INT /

DINT

Max. 20 bytes from the adapter to the

scanner:

• 70 (0x46): Basic Speed Control Input

• 71 (0x47): Extended Speed Control Input

• 72 (0x48): Speed and Torque Control

Input

• 73 (0x49): Extended Speed and Torque

Control Input

• 111 (0x6F): Custom Input

Instance attribute "Data" (attribute 3)

( 116)

In the 111 (0x6F, Custom Input) assembly

object instance, the I/O data are entered in

the last two words.

Configuring I/O data ( 45)

4

Get

Size

UINT

Number of bytes in attribute 3 (Data)

Advertising