Használati útmutató IFM AL4002

IFM nincs kategorizálva AL4002

Olvassa el alább 📖 a magyar nyelvű használati útmutatót IFM AL4002 (68 oldal) a nincs kategorizálva kategóriában. Ezt az útmutatót 2 ember találta hasznosnak és 2 felhasználó értékelte átlagosan 4.5 csillagra

Letöltés PDF
Oldal 1/68
Operating instructions
Remote I/O module 16 DI
PROFINET
IP65 / IP66 / IP67
AL4002
11425600 / 0004 / 2022
GB
AL4002 Remote I/O module 16 DI
2
Contents
1 Preliminary note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Safety instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Cyber security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Intended use................................................................ 7
4 Function ................................................................... 8
4.1 Visual indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3 Inputs ................................................................ 8
4.3.1 Sensor supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4 Digital input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4.1 Debouncing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.4.2 Holding........................................................... 9
4.4.3 Inverting .......................................................... 10
4.4.4 Filter combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5 Counters.............................................................. 10
4.5.1 Counter mode CTU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5.2 Counter mode CTD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.5.3 Counter mode CTUD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.5.4 Counter mode CTDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.6 PROFINET............................................................ 12
5 Installation.................................................................. 14
5.1 Install device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 Electrical connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 Overview.............................................................. 15
6.2 General wiring information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2.1 Connection technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3 Ethernet .............................................................. 15
6.4 Process connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.5 Voltage supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.5.1 Derating behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7 Operating and display elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1 LEDs................................................................. 18
7.1.1 Status............................................................ 18
7.1.2 Ethernet .......................................................... 18
7.1.3 Voltage supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1.4 Process connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8 Set-up..................................................................... 20
9 Settings.................................................................... 21
9.1 Parameter setting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1.1 Supported parameter setting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1.2 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1.2.1 Configure the PROFINET interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1.3 Fieldbus: Read the interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1.4 Fieldbus: Read the connection status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1.5 Ports: Configure input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1.6 Ports: Read digital input data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1.7 Counters: Configure counter modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1.8 Counters: Read counter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1.9 Counters: Control counter modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1.10 Gateway: Read identification information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1.11 Gateway: Read status and diagnostic information. . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9.1.12 Gateway: Set the application tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9.1.13 Firmware: Read firmware version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.1.14 Firmware: Reset the device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.1.15 Firmware: Restart the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.2 ifm IoT Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Remote I/O module 16 DI AL4002
3
9.2.1 ifm IoT Core: General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.2.1.1 Accessing the ifm IoT Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.2.2 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.2.2.1 Notes on configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.2.3 General functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.2.3.1 Example: Outputting the subtree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.2.3.2 Example: Reading several elements sequentially . . . . . . . . . . . . . . . . . . . . . . 31
9.2.3.3 Example: Changing a parameter value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9.2.4 Fieldbus: Read the interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9.2.5 Ports: Configure input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.2.6 Ports: Read digital input data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.2.7 Counters: Configure counter modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.2.8 Counters: Control counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2.9 Counters: Read and write counter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2.9.1 Example: Write counter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9.2.10 Gateway: Read device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9.2.11 Gateway: Read status and diagnostic information. . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9.2.12 Gateway: Set the application tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9.2.13 Gateway: Update firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9.2.14 IoT-Core Visualizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.2.14.1 Start the ifm IoT Core Visualizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.2.14.2 Search for elements in the device description . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.2.14.3 Configure the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.2.14.4 Access process data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.2.14.5 Update firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.3 PROFINET............................................................ 40
9.3.1 Install the GSD file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.3.2 Integrate the device into a PROFINET project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.3.2.1 Use S2 redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.3.2.2 Use Configuration-in-Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.3.2.3 Use Isochronous Realtime (IRT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.3.3 Configure the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.3.3.1 Use Prioritized Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.3.3.2 Use Fast Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.3.4 Configure input filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
9.3.5 Configure counter modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
9.3.6 Read process data of the ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.7 Read counter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.8 Control counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.9 Acyclic access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.3.10 Read counter events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.3.11 Use I&M data records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10 Maintenance, repair and disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.1 Cleaning.............................................................. 47
10.2 Update firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
11 Appendix................................................................... 48
11.1 ifm IoT Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1.1 Profiles........................................................... 48
11.1.2 Types ............................................................ 48
11.1.3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1.3.1 Service: factoryreset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1.3.2 Service: force_counter_values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1.3.3 Service: getblobdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1.3.4 Service: getdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1.3.5 Service: getdatamulti. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1.3.6 Service: getelementinfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.1.3.7 Service: getidentity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.1.3.8 Service: gettree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.1.3.9 Service: install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1.3.10 Service: querytree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1.3.11 Service: reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Remote I/O module 16 DI AL4002
5
1 Preliminary note
You will find instructions, technical data, approvals and further information using the QR code on the
unit / packaging or at .www.ifm.com
AL4002 Remote I/O module 16 DI
6
2 Safety instructions
• The unit described is a subcomponent for integration into a system.
– The system architect is responsible for the safety of the system.
– The system architect undertakes to perform a risk assessment and to create documentation in
accordance with legal and normative requirements to be provided to the operator and user of
the system. This documentation must contain all necessary information and safety instructions
for the operator, the user and, if applicable, for any service personnel authorised by the
architect of the system.
• Read this document before setting up the product and keep it during the entire service life.
• The product must be suitable for the corresponding applications and environmental conditions
without any restrictions.
• Only use the product for its intended purpose ( Intended use).Ò
• If the operating instructions or the technical data are not adhered to, personal injury and/or damage
to property may occur.
• The manufacturer assumes no liability or warranty for any consequences caused by tampering with
the product or incorrect use by the operator.
• Installation, electrical connection, set-up, operation and maintenance of the product must be
carried out by qualified personnel authorised by the machine operator.
• Protect units and cables against damage.
• Replace damaged units, otherwise the technical data and safety will be impaired.
2.1 Cyber security
ATTENTION
Operating the machine in an unprotected network environment
wUnauthorised read or write access to data is possible.
wUnauthorised manipulation of the device function is possible.
uCheck and restrict access options to the device.
Remote I/O module 16 DI AL4002
7
3 Intended use
The unit may only be used for the following purposes:
• Gateway between digital sensors and a higher-level control system
The device is designed for use outside of a control cabinet.
AL4002 Remote I/O module 16 DI
8
4 Function
4.1 Visual indication
The device displays the following indications:
• Status and error indication of the gateway and the system
• Status and activity indication of the Ethernet connection
• Status display of the voltage supply
• Status, error and short circuit/overload indication of the sensor ports
4.2 Parameter setting
The device can be configured using the following options:
• parameter setting software
– ifmmoneo
– ifm moneo|configure SA
• ifm IoT Core
– REST-API
– IoT-Core Visualizer
• PROFINET projection software
4.3 Inputs
The device has 8 ports. Each port has 2 digital inputs.
4.3.1 Sensor supply
The device has a total of 8 sensor supplies (1 sensor supply per port).
4.4 Digital input filters
The device supports preprocessing of the digital input signals. The filter result is forwarded as a
process value. The following filters can be applied to the input signals in the sequence specified.
1. Debouncing
2. Stretching
3. Inverting
Digital input Debouncing Stretching Inverting
Counter input
Process data
Filter module
Each filter can be configured separately.
The device detects signals of a length of min. 0.23 ms. Shorter signals are not detected.
Remote I/O module 16 DI AL4002
9
Periodic signals are only detected reliably if the signal period is at least twice as long as the
cycle time.
4.4.1 Debouncing
The filter suppresses noise signals. The filter provides the input signals at the filter output with a delay
(debounce time). All signals shorter than the set debounce time are ignored by the filter.
Time diagram debounce filter:
2
11 11
0
1
0
1
0
1
t
Process data
Filter output
Filter input
1: debounce time
2: cycle time
4.4.2 Holding
The filter prolongs short input pulses. Level changes that occur during a holding period are ignored.
The filter is configured via the following parameters:
• Hold time: pulse duration to which short pulses are to be prolonged. Pulses that are present for a
longer time than the hold time are not prolonged.
• Hold level: signal level to be prolonged (HIGH or LOW)
Time diagram hold filter (status HIGH):
2
1 1 1
0
1
0
1
0
1
t
Process data
Filter output
Filter input
1: hold time
2: cycle time
Time diagram hold filter (status LOW):
2
1 1 1
0
1
0
1
0
1
t
Filter input
Filter output
Process data
1: hold time
2: cycle time
Remote I/O module 16 DI AL4002
11
• If the counter module detects a positive edge at pin 4 of the port, the value of the main counter is
incremented (m = m+1).
• If the main counter reaches the threshold value CT (m = CT), the counter value is reset (m = 0).
Due to the overflow detection, the value of the batch counter is incremented (b = b+1).
• If the batch counter reaches the threshold value CTb (b = CTb), the counter value is reset (b = 0).
CTb
CT
0
0
t
Main Counter
Batch Counter
4.5.2 Counter mode CTD
In CTD (Count Down) mode, the counter module operates as a down counter with underflow detection
and underflow counting.
Behaviour:
• The initial value of the main counter is m = 0. The initial value of the batch counter is b = 0. The
main counter has a threshold value CT. The batch counter has a threshold value CTb.
• The first time a positive edge is detected at pin 4, the value of the main counter is set to the
threshold value CT-1 (m = CT-1). At the same time, the value of the batch counter is set to the
threshold value CTb-1 (b = CTb-1).
• If the counter module detects a positive edge at pin 4 of the port, the value of the main counter is
decremented (m = m-1).
• If the main counter falls below 0, the counter value is reset to the threshold value (m = CT-1). Due
to the underflow detection, the value of the batch counter is decremented (b = b-1).
• If the batch counter falls below 0, the counter value is reset to the threshold value (b = CTb-1).
CTb
CT
0
0
t
Main Counter
Batch Counter
4.5.3 Counter mode CTUD
In CTUD (Count Up Down) mode, the counter operates as a simultaneous up and down counter with
overflow and underflow detection.
Behaviour:
• The initial value of the main counter is m = 0. The initial value of the batch counter is b = 0. The
main counter has a threshold value CT. The batch counter has a threshold value CTb.
• If the counter module detects a positive edge at pin 4 of the port, the value of the main counter is
incremented (m = m+1).
• If the counter module detects a positive edge at pin 2 of the port, the value of the main counter is
decremented (m = m-1).
AL4002 Remote I/O module 16 DI
12
• If the counter module simultaneously detects a positive edge at pin 4 and pin 2 of the port, the
counter value of the main counter does not change.
• If the main counter reaches the threshold value CT (m = CT), the counter value is reset (m = 0).
Due to the overflow detection, the value of the batch counter is incremented (b = b+1).
• If the main counter falls below 0, the counter value is reset to the threshold value (m = CT-1). Due
to the underflow detection, the value of the batch counter is decremented (b = b-1).
• If the batch counter reaches the threshold value CTb (b = CTb), the counter value is reset (b = 0).
• If the batch counter falls below 0, the counter value is reset to the threshold value (b = CTb-1).
CTb
CT
0
0
t
Main Counter
Batch Counter
4.5.4 Counter mode CTDIR
In CTDIR (Count Direction) mode, the counter module operates either as an up counter with overflow
detection or as a down counter with underflow detection. The counting direction can be set.
Behaviour:
• The initial value of the main counter is m = 0. The initial value of the batch counter is b = 0. The
main counter has a threshold value CT. The batch counter has a threshold value CTb.
• The user can determine the counting direction. The counter module initially operates as an up
counter with overflow detection.
• If the counter module detects a positive edge at pin 4 of the port and the counting direction of the
port is set to “up”, the value of the main counter is incremented (m = m+1).
• If the main counter reaches the threshold value CT (m = CT), the counter value is reset (m = 0).
Due to the overflow detection, the value of the batch counter is incremented (b = b+1).
• If the batch counter reaches the threshold value CTb (b = CTb), the counter value is reset (b = 0).
• If the counter module detects a positive edge at pin 4 of the port and the counting direction at pin 2
of the port is set to “down”, the value of the main counter is decremented (m = m-1).
• If the main counter falls below 0, the counter value is reset to the threshold value (m = CT-1). Due
to the underflow detection, the value of the batch counter is decremented (b = b-1).
• If the batch counter falls below 0, the counter value is reset to the threshold value (b = CTb-1).
CTb
CT
0
0
t
Main Counter
Batch Counter
4.6 PROFINET
Supported PROFINET functions:
Remote I/O module 16 DI AL4002
13
• Device profile: PROFINET IO device
• Fast Startup (FSU)
• Prioritized Startup
• Participation in network with activated IRT protocol
• System redundancy S2
• Dynamic reconfiguration
• Device description: GSD file
AL4002 Remote I/O module 16 DI
14
5 Installation
5.1 Install device
uDisconnect the power of the machine before installation.
uUse a flat mounting surface for installation.
uPlease observe the maximum tightening torque.
uFasten the module onto the mounting surface using M5 screws and washers (tightening torque: 1.8
Nm).
Remote I/O module 16 DI AL4002
15
6 Electrical connection
6.1 Overview
X21: Ethernet 1 (PROFINET)
X22: Ethernet 2 (PROFINET)
X31: power IN
X01: process connection 1 (sensor)
X02: process connection 2 (sensor)
X03: process connection 3 (sensor)
X04: process connection 4 (sensor)
X05: process connection 5 (sensor)
X06: process connection 6 (sensor)
X07: process connection 7 (sensor)
X08: process connection 8 (sensor)
6.2 General wiring information
The unit must be connected by a qualified electrician.
uObserve the national and international regulations for the installation of electrical equipment.
The device is only suitable for operation using SELV/PELV voltages.
This device contains components that may be damaged or destroyed by electrostatic discharge
(ESD).
uPlease observe the required precautions against electrostatic discharge.
The circuits are insulated from each other and from touchable surfaces of the device with basic
insulation according to EN61010-1.
The communication interfaces are insulated from each other and from touchable surfaces of the
device with basic insulation according to EN61010-1.
6.2.1 Connection technology
The threaded connections in the device correspond to the M12 standard. To ensure compliance with
the specified protection rating, only cables that comply with this standard may be used. In the case of
self-assembled cables, the system manufacturer is responsible for the protection rating.
uUse connectors with gold-plated contacts.
uDuring installation, place the connectors vertically so that the coupling nut will not damage the
thread.
uObserve the coding of the connectors during installation.
uCover unused connections with protective covers. Tightening torque: 0.3 ± 0.1Nm
6.3 Ethernet
The device is connected to the PROFINET network via the Ethernet ports X21 / X22 (e.g. PROFINET
control, additional PROFINET device). In addition, the device can be connected to an IT network via
the Ethernet ports. Via the IT network, the user can access functions of the ifm IoT Core (configuration
tools, REST API, IoT Core Visualizer).
AL4002 Remote I/O module 16 DI
16
uConnect the device to the PROFINET network via a free Ethernet port.
uOptional: Connect the device to the IT network via a free Ethernet port.
uFor connection, use an M12 connector (with at least protection rating: IP65 / IP66 / IP67).
uTighten the cable plug using 1.3 ± 0.1Nm.
Wiring:
1 2
34
5
1: TX+
2: RX+
3: TX-
4: RX-
5: not used
6.4 Process connections
The sensors are connected to the device via the process connections.
The total current supply of the ports X01...X08 is limited to 3.6 A.
The ports feature short-circuit/ overload detection.
uConnect the sensors to ports X01...X08.
uFor connection, use M12 connectors (with at least protection rating: IP65 / IP66 / IP67; max. cable
length: 30m).
uTighten the cable plug using 1.3 ± 0.1Nm.
Wiring:
3
1 2
4
5
1: sensor supply L+ (US)
2: digital output 2 (DI2)
3: sensor supply L- (US)
4: digital output 1 (DI1)
5: functional earth (FE)
6.5 Voltage supply
The device is connected to the supply voltage US via the power IN port.
The US supply voltage supplies the device and the sensors connected to the ports X01...X08 with
voltage.
Port X31 has overvoltage protection (US).
Port X31 has reverse polarity protection (US).
Port X31 has an inrush current limitation.
uDisconnect power!
uConnect the device via port X31 to 24VDC (20…30V SELV/PELV).
uFor connection, use an L-coded M12 connector (with at least protection rating: IP65 / IP66 / IP67).
uTighten the cable sockets according to the torque specifications indicated by the cable
manufacturer. Maximum permissible tightening torque: 0.8Nm
u ÒObserve the derating behaviour of the device ( Derating behaviour 17)./
Wiring:
43
2 1
1: +24VDC (US)
2: not used
3: GND (US)
4: not used
Remote I/O module 16 DI AL4002
17
6.5.1 Derating behaviour
The current IUS available at ports X01...X08 depends on the ambient temperature of the device.
-40 -30 -20 -10 0 10 20 30 40 50 60 70
1
2
3
4
2000 m
3000 m
4000 m
Current [A]
Temperature [°C]
0.5
1.5
2.5
3.5
1
1: IUS at ports X01...X08
Remote I/O module 16 DI AL4002
19
LED Description Colour State Description
LNK Status of the con-
nection
Green On Ethernet connection established
ACT Status of the data
transmission
Yellow Off no data transmission
Flashes Data transmission
7.1.3 Voltage supply
LED Description Colour State Description
US Voltage supply sta-
tus
- Off No supply voltage is applied or the applied supply voltage is
too low
Green On Supply voltage applied
Red On Overvoltage, undervoltage, short circuit at sensor supply
7.1.4 Process connections
LED Description Colour State Description
DI1 Digital input signal
level (pin 4)
Yellow Off Digital input - pin 4: LOW
On Digital input - pin 4: HIGH
DI2 Digital input signal
level (pin 2)
Yellow Off Digital input - pin 2: LOW
On Digital input - pin 2: HIGH
AL4002 Remote I/O module 16 DI
20
8 Set-up
uInstall the unit correctly.
uEstablish a correct electrical connection with the device.
wOnce connected to the supply voltage, the unit will start.
wThe LEDs show status and error conditions.
wThe unit is ready for operation.
wThe device can be configured.
AL4002 Remote I/O module 16 DI
22
9.1.3 Fieldbus: Read the interface configuration
uObserve the notes on the configuration of the PROFINET interface: Configure the PROFINET
interface ( 21)Ò/
Available parameters:
Name Description Value range Access
[ipaddress] IP address of the PROFINET inter-
face
e.g. 192.100.0.10
0.0.0.0 (default)
ro 1
[subnetmask] Subnet mask of the network segment e.g. 255.255.255.0
0.0.0.0 (default)
ro 1
[ipdefaultgateway] IP address of the network gateway e.g. 192.100.0.1
0.0.0.0 (default)
ro 1
[macaddress] MAC address of the Ethernet inter-
face
e.g. 00:02:01:0E:10:7F ro
1
[hostname] Name of the device in the PROFINET
network
e.g. al4x0x ro 1
1read only
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the [fieldbussetup] > [network] menu.
wThe menu page displays the current configuration of the PROFINET interface.
9.1.4 Fieldbus: Read the connection status
Available information:
Name Description Value range Access
[connectionstatus] Status of the PROFINET connection • Disconnected: not connected
• Connected: connected
ro 1
[fieldbusfirmware] Firmware version of the PROFINET
stack
e.g. 5.4.0.3 (PROFINET IO Device) ro
1
1read only
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the [fieldbussetup] menu.
wThe menu page displays the status of the PROFINET connection.
9.1.5 Ports: Configure input filters
u ÒObserve the notes on input filters: Digital input filters ( 8)/
Available parameters:
Name Description Value range Access
[pin2]/[debounce_time] Pin 2: debounce time (= value *
0.1ms)
• 0: 0ms (default)
…
• 500: 50ms
rw 1
Remote I/O module 16 DI AL4002
23
Name Description Value range Access
[pin2]/[hold_time] Pin 2: hold time (= value * 0.1ms) • 0: 0ms (default)
…
• 60000: 6000ms
rw 1
[pin2]/[hold_level] Pin 2: hold level • 0: hold LOW
• 1: hold HIGH (default)
rw 1
[pin2]/[invert] Pin 2: inversion • 0: do not invert (default)
• 1: invert
rw 1
[pin4]/[debounce_time] Pin 4: debounce time (= value *
0.1ms)
• 0: 0ms
…
• 500: 50ms
rw 1
[pin4]/[hold_time] Pin 4: hold time (= value * 0.1ms) • 0: 0ms (default)
…
• 60000: 6000ms
rw 1
[pin4]/[hold_level] Pin 4: hold level • 0: hold LOW
• 1: hold HIGH (default)
rw 1
[pin4]/[invert] Pin 4: inversion • 0: do not invert (default)
• 1: invert
rw 1
1read and write; can only be changed if no connection to the fieldbus controller is active
uSelect the menu option [io] > [port[n]] (n: 1…8).
wThe menu page displays the available parameters.
uSet the parameters.
uWrite the changed parameter values to the device.
wThe digital input filters have been configured.
9.1.6 Ports: Read digital input data
Available information:
Name Description Value range Access
[pin2]/[digital] Process value digital input - pin 2 (af-
ter filtering)
• LOW: off
• HIGH: on
ro 1
[pin4]/[digital] Process value digital input - pin 4 (af-
ter filtering)
• LOW: Off
• HIGH: on
ro 1
1read only
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [io] > [port[n]] (n: 1…8).
wThe menu page displays the current process values of the port’s digital inputs.
The displayed process values are the filtered input data.
9.1.7 Counters: Configure counter modules
u ÒObserve the notes on counter modules: Counters ( 10)/
If the operating mode of a counter module is changed, the current counter values will be reset
and any active events will be deleted.
AL4002 Remote I/O module 16 DI
24
For the parameters [pin2_function] and [count_direction_selection] all shown parameter values can be
selected. It is not checked whether these make sense. For each counter operating mode (parameter
[mode]), the table below indicates the valid value ranges ( : valid setting; : invalid setting): 
[mode]
[pin2_function] [count_direction_selection]
N/C
Counter
Edge Input
Pin2
Count Direc-
tion
Reset (Main
& Batch
Counter)
Disable
(Main &
Batch Coun-
ter)
Pin 2 Count
Direction
IoT / PLC
Count Direc-
tion
CTU       
CTD       
CTUD      
CTDIR       
CTDIR       
Available parameters:
Name Description Value range Access
[mode] Operating mode of the counter mod-
ule
• CTU (up counter): up counter (default)
• CTD (down counter): down counter
• CTUD (up counter/ down counter): up
and down counter
• CTDIR (direction counter): up or down
counter
rw 1
[pin2_function] Pin 2 function of the port ( ObserveÒ
note!)
• N/C: no function (default)
• Counter Edge Input 2: counting pulse
(rising edge)
• Count Direction: counting direction
• Reset (Main & Batch Counter): reset
main counter and batch counter
• Disable (Main & Batch Counter): disable
main counter and batch counter
rw 1
[count_direction_selection] Control instance for selecting the
counting direction ( Observe note!)Ò
• Pin 2 Count Direction: pin 2 of the port
(default)
• IoT / PLC Count Direction: Fieldbus PLC
rw 1
[main_threshold] Main counter threshold (CT) • 1
…
• 4294967295 (default)
rw 1
[batch_threshold] Batch counter threshold (CTb) • 1
…
• 65535 (default)
rw 1
1read and write; can only be changed if no connection to the fieldbus controller is active
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [io] > [counter[n]] (n: 1…8).
wThe menu page displays the configuration options of the counter.
uConfigure the counter module.
uOptional: Configure additional counter modules.
uWrite the changed values to the device.
wThe counter modules are configured.
Remote I/O module 16 DI AL4002
25
9.1.8 Counters: Read counter values
Available parameters:
Name Description Value range Access
[maincounter_value] Main counter value 0…4294967294 ro
1
[batchcounter_value] Batch counter value 0…65534 ro
1
1read only
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [io] > [port[n]] (n: 1…8).
wThe menu page displays the current counter values of the main and batch counter.
9.1.9 Counters: Control counter modules
Available parameters:
Name Description Value range Access
[disable] Disable main counter and batch coun-
ter
• 0: counter module is active (default)
• 1: counter module is not active
rw 1
[reset] Reset main counter, batch counter
and CT and CTb thresholds to initial
values
• 0: no action (default)
• 1: reset
rw 1
[direction] 2Set counting direction for main and
batch counter
• 0: up (default)
• 1: down
rw 1
1read and write; can only be changed if no connection to the fieldbus controller is active
2only effective if operating mode of counter module = CTDIR
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [io] > [counter[n]] (n: 1…8).
wThe menu page displays the available parameters.
uOptional: disable counter module.
uOptional: reset counter module.
uOptional: set counting direction of counter module.
uWrite the changed parameter values to the device.
wSelected actions are executed.
9.1.10 Gateway: Read identification information
Available information:
Name Description Value range Access
[productcode] Article number AL4002 ro
1
[devicefamily] Device family Ethernet modules ro
1
[vendor] Manufacturer ifm electronic gmbh ro
1
[swrevision] Firmware revision e.g. AL4x0x_fw_pn_v1.4.0.137 ro
1
[hwrevision] Hardware revision (status) e.g. AA ro
1
AL4002 Remote I/O module 16 DI
26
Name Description Value range Access
[bootloaderrevision] Bootloader version e.g. AL4xxx_bl_v1.2.0.35 ro
1
[serialnumber] Serial number e.g. 0002043100003 ro
1
[fieldbustype] Fieldbus PROFINET ro
1
1read only
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [deviceinfo].
wThe menu page displays the identification information of the device.
9.1.11 Gateway: Read status and diagnostic information
Available information:
Parameter Description Value range Access
[temperature] Temperature of the device (value in
°C)
-30…80 ro 1
[voltage_us] Present voltage value of the device
supply US (value in mV)
0…40000 ro 1
[supervisionstatus_us] Status of the device supply US • 0: no error
• 1: error
ro 1
[current_us] Present current value of the device
supply US (value in mA)
0…40000 ro 1
1read only
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [Processdatamaster].
wThe menu page displays the diagnostic and status information.
9.1.12 Gateway: Set the application tag
Available parameters:
Parameter Description Value range Access
[applicationtag] Application-specific identifier of the de-
vice in moneo
e.g. plant 1 machine 3 rw
1
1read and write
Requirements:
üThe parameter setting software has been started.
üThe detailed view of the device is active.
uSelect the menu option [devicetag].
uEnter the application identifier.
uWrite the changed values to the device.
wThe device can be identified by the selected application tag.
AL4002 Remote I/O module 16 DI
28
9.2 ifm IoT Core
9.2.1 ifm IoT Core: General information
The device has the ifm IoT Core. The ifm IoT Core represents the functionality of a device. Each
device is represented by a number of objects, services and events. The elements of the ifm IoT Core
are arranged in a JSON object in a hierarchical tree structure. The ifm IoT Core makes these elements
available to the outside world via standard interfaces. This allows the user and other devices to access
data (parameters, process data, events) and functions (services) of the ifm IoT Core.
9.2.1.1 Accessing the ifm IoT Core
An element of the ifm IoT Core is accessed via its address (e.g. ). The address isroot/port1/pin2
composed of the path leading to the element ( ) and the identifier of the element ( ).root/port1 pin2
The user can access the ifm IoT Core via HTTP requests. The following methods are supported:
GET method
Access: reading
Syntax of the request:
http://ip/datapoint/service
Parameter Description
ip IP address of the IoT interface
data_point Data point which is to be accessed
service Service
Syntax of the response:
{
"cid":id,
"data":{"value":"resp_data"},
"adr":"data_point/service",
"code":diag_code
}
Field Parameter Description
cid id Correlation ID for the assignment of request and reply
data resp_data Value of the data point; depending on the data type of the data point
adr data_point Data point accessed
service Service that accessed the data point
code diag_code Diagnostic code Diagnostic codes
Example: GET request
• Request:
http://192.168.0.250/devicetag/applicationtag/getdata
• Response:
Remote I/O module 16 DI AL4002
29
{
"cid":-1,
"data":{"value":"factory 2 plant 1"},
"adr":"devicetag/applicationtag/getdata",
"code":200
}
POST method
Access: reading, writing
Syntax of the request:
{
"code":"code_id",
"cid":id,
"adr":"data_point/service",
"data":{req_data},
}
Field Parameter Description
code code_id Service class
• request: Request
• transaction: Transaction
• event: Event
cid id Correlation ID for the assignment in pairs of request and return; identifier freely selectable by the
user
adr data_point Data point which is to be accessed
service Service to access the data point
data 1req_data Data sent to the ifm IoT Core (e.g. new values); syntax depending on the service
1optional; only required for services that send data to the ifm IoT Core (e.g. setdata)
Syntax of the response:
{
"cid":id,
"data":{resp_data},
"adr":"data_point/service",
"code":diag_code
}
Field Parameter Description
cid id Correlation ID for the assignment of request and return ( Request)Ò
data 1resp_data Values returned by the ifm IoT Core; syntax depending on the service
adr data_point Data point accessed
service Service that accessed the data point
code diag_code Diagnostic code
1optional; only available for services that receive data from the ifm IoT Core (e.g. getdata)
Example: POST request
• Request:
AL4002 Remote I/O module 16 DI
32
{
"cid":4711,
"data":{
"processdatamaster/temperature":{"code":200,"data":44},
"deviceinfo/serialnumber":{"code":200,"data":"000174210147"}},
"adr":/getdatamulti",
"code":200
}
9.2.3.3 Example: Changing a parameter value
Task: The Application Tag parameter of the device is to be written with the value “Do not use”. The
new value is only supposed to be valid until the next reboot of the device.
Solution: Write the new value of the element with the /devicetage/applicationtag setdata
service. To keep the new value only until the next restart of the device, pass on the optionduration
with the value.uptime
• Request:
{
"code":"request",
"cid":4711,
"adr":"/devicetag/applicationtag/setdata",
"data":{"duration":"uptime","newvalue":"Do not use"}
}
• Response:
{
"cid":4711,
"adr":"/devicetag/applicationtag/setdata",
"code":200,
}
9.2.4 Fieldbus: Read the interface configuration
Substructure: fieldbussetup
Available data points:
Name Description Values Access
../network/ipaddress IP address of the Ethernet interface: e.g. 192.200.0.100
• 0.0.0.0 (default)
ro 1
../network/subnetmask Subnet mask of the network segment e.g. 255.255.192.0
• 0.0.0.0 (default)
ro 1
../network/ipdefaultgateway IP address of the network gateway e.g. 192.200.63.1
• 0.0.0.0 (default)
ro 1
../network/hostname Name of device in PROFINET project e.g. al4x0x ro
1
../network/macaddress MAC address of the Ethernet interface e.g. 00:02:01:0E:10:7C ro
1
../fieldbusfirmware Version of the PROFINET firmware of the de-
vice
e.g. 5.4.0.3 (PROFINET IO De-
vice)
ro 1
../connectionstatus Status of the connection to the PROFINET
network
• 0: not connected
• 1: connected
ro 1
1read only
Remote I/O module 16 DI AL4002
33
9.2.5 Ports: Configure input filters
u ÒObserve the notes on input filters: Digital input filters ( 8)/
Substructure: (n: 1…8)io/port[n]
Available data points:
Name Description Values Access
../pin2/debounce_time Pin 2: debounce time (= value * 0.1ms) • 0: 0ms (default)
…
• 500: 50ms
rw 1
../pin2/hold_time Pin 2: hold time (= value * 0.1ms) • 0: 0ms (default)
…
• 60000: 6000ms
rw 1
../pin2/hold_level Pin 2: hold level • 0: hold LOW
• 1: hold HIGH (default)
rw 1
../pin2/invert Pin 2: inversion • 0: do not invert (default)
• 1: invert
rw 1
../pin4/debounce_time Pin 4: debounce time (= value * 0.1ms) • 0: 0ms (default)
…
• 500: 50ms
rw 1
../pin4/hold_time Pin 4: hold time (= value * 0.1ms) • 0: 0ms (default)
…
• 60000: 6000ms
rw 1
../pin4/hold_level Pin 4: hold level • 0: hold LOW
• 1: hold HIGH (default)
rw 1
../pin4/invert Pin 4: inversion • 0: do not invert (default)
• 1: invert
rw 1
1read and write; can only be changed if no connection to the fieldbus controller is active
9.2.6 Ports: Read digital input data
Substructure: (n: 1…8)io/port[n]
Available data points:
Name Description Values Access
../pin2/digital Process value digital input - pin 2 (after filter-
ing)
• 0: LOW
• 1: HIGH
ro 1
../pin4/digital Process value digital input - pin 4 (after filter-
ing)
• 0: LOW
• 1: HIGH
ro 1
1read only
9.2.7 Counters: Configure counter modules
u ÒObserve the notes on counter modules: Counters ( 10)/
If the operating mode of a counter module is changed, the current counter values will be reset
and any active events will be deleted.
For the parameters [pin2_function] and [count_direction_selection] all shown parameter values can be
selected. It is not checked whether these make sense. For each counter operating mode (parameter
[mode]), the table below indicates the valid value ranges ( : valid setting; : invalid setting): 
AL4002 Remote I/O module 16 DI
34
[mode]
[pin2_function] [count_direction_selection]
No function Counting
pulse
Counting di-
rection
Reset main
and batch
counter
Disable main
and batch
counter
Pin 2 Fieldbus
PLC
CTU       
CTD       
CTUD      
CTDIR      
CTDIR       
Substructure: (n: 1…8)io/counter[n]
Available data points:
Name Description Values Access
../mode Operating mode of the counter module • 0: CTU – up counter (default)
• 1: CTD – down counter
• 2: CTUD – up and down counter
• 3: CTDIR – up and down counter
with selectable counting direction
rw 1
../pin2_function Pin 2 function of the port ( Observe note!)Ò• 0: no function (default)
• 1: counting pulse (rising edge)
• 2: counting direction
• 3: reset main counter and batch
counter
• 4: disable main counter and batch
counter
rw 1
../count_direction_selection Control instance for selecting the counting
direction ( Observe note!)Ò
• 0: Pin 2 (default)
• 1: Fieldbus PLC
rw 1
../main_threshold Main counter threshold (CT) • 1
…
• 4294967295 (default)
rw 1
../batch_threshold Batch counter threshold (CTb) • 1
…
• 65535 (default)
rw 1
1read and write; can only be changed if no connection to the fieldbus controller is active
9.2.8 Counters: Control counters
Substructure: (n: 1…8)io/counter[n]
Available data points:
Name Description Values Access
../reset Reset counter module (reset counter
and threshold values to default values)
• 0: no action (default)
• 1: reset
rw 1
../disable Disable counter module • 0: enable counter (default)
• 1: disable counter
rw 1
../direction 2Set counting direction for main and
batch counter
• 0: up (default)
• 1: down
rw 1
1read and write; can only be changed if no connection to the fieldbus controller is active
2only effective if operating mode of counter module = CTDIR
9.2.9 Counters: Read and write counter values
Substructure: (n: 1…8)io/counter[n]
Remote I/O module 16 DI AL4002
35
Available data points:
Name Description Values Access
../maincounter_value Current main counter value 0…4294967295 ro
1
../batchcounter_value Current batch counter value 0…65535 ro
1
1read only
Applicable services:
Name Description
../force_counter_value Write counter values of main and batch counter
9.2.9.1 Example: Write counter values
Task: The counter values of the counter module of port 2 are to be changed (main counter = 100,
batch counter = 10).
Solution: Write the new values to the structure with the serviceio/counter[2]
force_counter_value .
• Request:
{
"code":"request",
"cid":4711,
"adr":"io/counter[2]/force_counter_value",
"data": {"maincounter_value":100,"batchcounter_value":10}
}
• Response:
{
"cid":4711,
"adr":"io/counter[2]/force_counter_value",
"code":200
}
9.2.10 Gateway: Read device information
Substructure: deviceinfo
Available data points:
Name Description Values Access
../productcode Article number AL4002 ro
1
../vendor Manufacturer ifm electronic ro
1
../devicefamily Device family Remote IO ro
1
../serialnumber Serial number (12 digits) e.g. 000174210161 ro
1
../hwrevision Hardware revision e.g. AA ro
1
../swrevision Firmware version e.g. AL4x0x_fw_pn_v1.4.0.137 ro
1
../bootloaderrevision Bootloader version e.g. AL4xxx_bl_v1.2.0.35 ro
1
../fieldbustype Fieldbus PROFINET ro
1
1read only
AL4002 Remote I/O module 16 DI
36
9.2.11 Gateway: Read status and diagnostic information
Substructure: processdatamaster
Available data points:
Name Description Values Access
../temperature Temperature of the device (value in °C) e.g. 52 ro
1
../voltage_us Present voltage value of the device sup-
ply US (value in mV)
e.g. 25236 ro 1
../current_us Present current value of the device sup-
ply US (value in mA)
e.g. 82 ro 1
../supervisionstatus_us Status of the device supply US • 0: no error
• 1: Error
ro 1
1read only
9.2.12 Gateway: Set the application tag
Substructure: devicetag
Available data points:
Name Description Values Access
../applicationtag Name of the device in moneo or
LRSMARTOBSERVER
e.g. “factory 2 plant 1” rw
1
1read and write
32 bytes are available on the device for storing the applicationtag parameter. If the memory
range is exceeded, the device will abort the write process (diagnostic code 400).
uWhen writing the applicationtag parameter, note the different memory requirements of the
individual UTF-8 characters (characters 0-127: 1 byte per character; character >127: more
than 1 byte per character).
9.2.13 Gateway: Update firmware
Substructure: firmware
Available data points:
Name Description Values Access
../version Firmware version AL4x0x_fw_pn_1.4.0.137 ro
1
../type Software type Firmware ro 1
../container Structure for firmware (BLOB) - wo
2
../container/maxsize Container size (in bytes) E.g. 4194304 ro
1
../container/chunksize Size of a data segment (in bytes) E.g. 4096 ro
1
../container/size Size of firmware file in container (in
bytes)
E.g. 634523 ro 1
1read only
2write only
Applicable services:
Name Description
../install Install firmware
../container/stream_set Transfer an individual data segment
../container/start_stream_set Start sequential transmission of several data segments
AL4002 Remote I/O module 16 DI
38
wThe ifm IoT Core Visualizer searches the device description for elements with the selected search
criteria.
wThe result list shows all elements found.
9.2.14.3 Configure the device
The [Parameter] menu page allows you to configure the device.
Requirements:
üThe ifm IoT Core Visualizer has been started.
uClick on [Parameter].
wThe menu page displays the available parameters of the device.
wCurrent parameter values are displayed.
uNavigate to the desired parameter.
uChange the parameter value.
uClick on to save the changes.
wThe changed parameter value is written to the device.
wThe changed parameter value is active.
uOptional: Repeat the procedure to change further parameter values.
wThe device has been configured.
9.2.14.4 Access process data
The [Processdata] menu page makes it possible to read and write the process data of the device and
the connected sensors.
Requirements:
üThe ifm IoT Core Visualizer has been started.
uClick on [Processdata].
wMenu page shows the substructures of the device description that contains the process data.
wThe current process values are displayed.
uOptional: Activate the [Polling] option and change the update interval.
wThe process values will be updated with the set interval.
uOptional: Click on next to an element to manually update the process value.
To change the value of a process date:
uNavigate to the required process date.
uChange the process value.
uClick on to save the changes.
wThe changed process value is written to the device.
wThe changed process value is active.
9.2.14.5 Update firmware
The [Update] menu page allows you to update the firmware of the device:
Requirements:
üThe ifm IoT Core Visualizer has been started.
uClick on [Update].
Remote I/O module 16 DI AL4002
39
wThe menu page displays information about the current firmware version.
uClick on [Load software file] and select a new firmware file (*.bin).
uClick on [Update] to start the update process.
wThe firmware of the device is updated.
wThe area shows the progress of the update process.
wAfter successful update: The device reboots automatically.
AL4002 Remote I/O module 16 DI
40
9.3 PROFINET
9.3.1 Install the GSD file
To map the device in a PROFINET projection software, ifm provides an GSD file. The device
description file contains identification information, supported parameters and process data. The user
can download the GSD file via .documentation.ifm.com
To add the device to the hardware catalogue of the PROFINET projection software:
uDownload the GSD file of the device.
uLaunch the PROFINET projection software.
uInstall the GSD file.
wThe device is added to the hardware catalogue of the PROFINET projection software.
wThe PROFINET projection software can access the device functions and data.
9.3.2 Integrate the device into a PROFINET project
Using the installed device description in the hardware catalogue, the device can be added to a
PROFINET project.
Requirements:
üThe GSD file of the device is installed.
uCreate a new project or open an existing one.
uOpen the [Device & networks] view.
uAdd necessary components of the automation network (e.g. PROFINET PLC).
uSelect the device in the hardware catalogue and add it to the network using drag & drop.
uEstablish a logical PROFINET IO connection between the device and the PROFINET PLC.
uSet the IP configuration of the device’s PROFINET interface.
wThe device has been integrated in the PROFINET project.
9.3.2.1 Use S2 redundancy
The device supports the S2 redundancy. S2 redundancy provides a solution to build a redundant
system for implementation of fail-safe systems. The following constraints apply:
• Both Application Relations (SR-AR) use the same configuration (submodule settings, connection
parameters).
• Only one AR can act as a primary SR-AR.
• Diagnostic messages and alarms are only reported to the primary SR-AR.
• Data records can be read via any SR-AR.
• Data records can only be written via the following SR-AR:
– primary SR-AR
– SR-AR that first accesses the device while establishing the connection
9.3.2.2 Use Configuration-in-Run
The device supports the Configuration-in-Run (CiR) function. CiR enables the user to load changes
and extensions of the hardware configuration in the PROFINET configuration software to the PLC
without needing to put the PLC into the “stop” state first.
Remote I/O module 16 DI AL4002
41
9.3.2.3 Use Isochronous Realtime (IRT)
The unit supports participation in a network with activated IRT protocol.
9.3.3 Configure the device
The device is configured via slot 0, subslot X1. The module [PN-IO] is permanently assigned to the
slot. The assignment cannot be changed.
Requirements:
üDevice is integrated in PROFINET project.
uOpen the [Device view].
wThe [Device overview] tab displays the device structure.
uClick on the module [PN_IO] in the slot [0X1].
wThe [Properties] view appears.
wThe [General] tab displays the available configuration options of the device.
uSet the parameters.
wThe device has been configured.
9.3.3.1 Use Prioritized Startup
The device supports the Prioritized Startup function.
To activate the Prioritized Startup function:
Requirements:
üDevice is integrated in PROFINET project.
uOpen the [Device view].
uClick on the module [PN_IO] (slot 1, subslot X1).
wThe [General] tab displays general configuration options.
uSelect [Advanced options] > [Interface options].
uActivate the [Prioritized startup] option.
wThe Fast Startup function has been activated.
9.3.3.2 Use Fast Startup
The device supports the Fast Startup function (FSU).
Achieving the guaranteed fast startup time depends on the complexity and elements used in the
PROFINET network.
To activate the Fast Startup function:
Requirements:
üDevice is integrated in PROFINET project.
üThe Fast Startup function has been activated.
AL4002 Remote I/O module 16 DI
42
uOpen the [Device view].
wThe [Device overview] tab displays the device structure.
uClick on the module [PN_IO] (slot 1, subslot X1).
wThe [General] tab displays general configuration options.
uSelect [Advanced options] > [X21 [X1 P1 R]] > [Port options].
uIn the list [Transmission rate / duplex], select the value [TP 100Mbps full duplex]. The selected
value must match the transmission rate of the network partner.
uDisable the option [Enable autonegotiation].
wThe transmission rate of Ethernet port 1 is permanently set.
uRepeat steps for Ethernet port 2 ([X22 [X1 P2 R]]).
wThe transmission rate of Ethernet port 2 is permanently set.
wThe Fast Startup function is activated for PROFINET IO ports.
9.3.4 Configure input filters
u ÒObserve the notes on input filters: Digital input filters ( 8)/
The input filters are configured via the following module:
• Modules: 8x2DI + Qualifier ( 54)Ò/
The module is permanently assigned to slot 1.
Each digital input on pin 2 and pin 4 of the ports has a filter. Each of these filters can be configured
separately.
Available parameters per input filter:
• debounce time
• hold time
• hold level
• signal inversion
Requirements:
üDevice is integrated in PROFINET project.
uOpen the [Device view].
wThe [Device overview] tab displays the device structure.
uClick on the module [8x2 DI + Qualifier] (slot [1]).
wThe [Properties] view appears.
wThe [General] tab displays the properties of the module.
w[Module parameters] provides access to parameters of the digital inputs.
uSet the parameters of the input filters.
uSave the project.
Remote I/O module 16 DI AL4002
43
wThe filters of the digital inputs are configured.
wThe changed configuration will be activated the next time the application is downloaded to the
device.
9.3.5 Configure counter modules
u ÒObserve the notes on counter modules: Counters ( 10)/
The counter modules are configured via the module [Counter Module] and its submodules:
• Submodule: CTU ( 55)Ò/
• Submodule: CTD ( 56)Ò/
• Submodule: CTUD ( 57)Ò/
• Submodule: CTDIR ( 58)Ò/
The module [Counter Module] needs to be assigned to slot 2 manually. Subsequently, a counter
submodule can be assigned to each port via the respective subslot. The counter submodule
determines the operating mode of the counter.
Each counter module can be configured separately.
Available parameters of the counter submodules:
• event messages of the main counter
• event messages of the batch counter
• threshold CT of the main counter
• threshold CTb of the batch counter
• function of pin 2 of the port
• instance for selecting the counting direction (only with CTDIR operating mode)
Requirements:
üDevice is integrated in PROFINET project.
uOpen the [Device view].
wThe [Device overview] tab displays the device structure.
uIn the hardware catalogue under [Modul] > [Counter], select the module [Counter Module] and
move it to slot 2 using drag& drop.
wThe counter module is assigned to the device.
wThe device overview displays the port designations assigned to the slot.
wThe hardware catalogue displays the available submodules.
uIn the hardware catalogue under [Submodule] > [Counter], select the desired counter submodule
and move it to a free subslot of the port using drag& drop.
AL4002 Remote I/O module 16 DI
44
wThe counter submodule is assigned to the port.
uClick on the subslot with the assigned counter submodule.
wThe [Properties] view appears.
wThe [Properties] tab shows the properties of the counter submodule.
w[Module parameters] provides access to parameters of the counter submodule.
uSet the parameters.
uOptional: Repeat the procedure to assign and configure further counter submodules.
wCounter submodules are assigned to the ports and configured.
9.3.6 Read process data of the ports
The digital input data of the ports and the associated validity indicators are transmitted in the cyclic
process data: Modules: 8x2DI + Qualifier ( 59)Ò/
When the device is integrated into the PROFINET project, IEC addresses are generated automatically
for the digital input data on pin 2 and pin 4 of the ports X01...X08.
Requirements:
üDevice is integrated in PROFINET project.
uConnect the IEC addresses of the subslots with symbols in the global variable list.
wThe user can access the digital input data of the ports via symbol names in the application.
9.3.7 Read counter values
The current counter values are accessed via the cyclical input data:
• Submodule: CTU ( 60)Ò/
• Submodule: CTD ( 61)Ò/
• Submodule: CTUD ( 62)Ò/
• Submodule: CTDIR ( 63)Ò/
When configuring the counter submodules, IEC addresses are generated automatically for the counter
values of the main and batch counter.
Requirements:
üDevice is integrated in PROFINET project.
üThe counter submodules are configured.
uConnect the IEC addresses of the subslots with symbols in the global variable list.
wThe user can access the counter values via symbol names in the application.
9.3.8 Control counters
The counter submodules assigned to the ports can be controlled separately. The following control
signals are available per counter:
• Reset counter module
• Disable counter module
• Set counting direction (only for CTUD counter operating mode)
The control signals are accessed via the cyclical output data:
• Submodule: CTU ( 60)Ò/
• Submodule: CTD ( 61)Ò/
Remote I/O module 16 DI AL4002
45
• Submodule: CTUD ( 62)Ò/
• Submodule: CTDIR ( 63)Ò/
To control the counter modules:
Requirements:
üDevice is integrated in PROFINET project.
üThe counter submodules are configured.
üThe IEC addresses of the cyclic process data are linked to variables.
uSet the control signals in the output data of the counter submodules.
wThe control signals are sent to the counter submodule.
9.3.9 Acyclic access
The user can access configuration and process data acyclically via data records.
The device supports the following data records:
• Data record: Filter configuration ( 64)Ò/
• Data record: Counter configuration ( 65)Ò/
• Data record: Counter values ( 66)Ò/
Note: Read data record
uRead the data record with the function block RDREC.
Specific parameters:
• Input ID: HW_ID of the subslot (project-specific); properties of the
subslot
• Input INDEX: index of the data record
9.3.10 Read counter events
The counter modules generate events when any of the following conditions occur:
• overflow main counter
• underflow main counter
• overflow batch counter
• underflow batch counter
The events triggered by the device are transmitted via the alarm mechanism of PROFINET IO. The
overflow and underflow events of the counter modules are transmitted as process alarms. Process
alarms are stored in an AINFO array. The relevant information is stored in bytes 16...35.
Structure of the AINFO array:
Bytes Content Description
16…19 Module ID Module identification
• 0x40000000: 8x2 DI Module
• 0x41000000: Counter module
20…23 Submodule ID Submodule identification
• 0x41000010: CTU Submodule
• 0x41000011: CTD Submodule
• 0x41000012: CTUD Submodule
• 0x41000013: CTDIR Submodule
AL4002 Remote I/O module 16 DI
46
Bytes Content Description
24…25 Alarm Specifier Alarm
• 0x0000: fixed
26…27 Format Identifier Identification of the format
• 0x8320: user-specific structure
28…29 Channel Number Channel number
• 0x8000: whole device
30…31 reserved Reserved
32…33 Event Info Event
• 0x0100: overflow main counter
• 0x0101: underflow main counter
• 0x0110: overflow batch counter
• 0x0111: underflow batch counter
34…35 reserved Reserved
Requirements:
üThe counter modules are configured.
üEvents for main counter are activated.
üEvents for batch counter are activated.
uProcess the process alarms with OB40.
uUse the RALRM instruction to read the occurred event in the AINFO array.
9.3.11 Use I&M data records
The unit supports the I&M data records I&M0 to I&M3 ( I&M data 67).Ò/
• The data record I&M0 contains ID information. The I&M0 data record is available for each module/
submodule of the device.
• In the data records I&M1...I&M3, the user can store application and device-specific information.
I&M data records can be accessed acyclically. Access to the I&M data records takes place index-
based.
Note: Read data record
uRead the data record with the function block RDREC.
Specific parameters:
• Input ID: HW_ID of the subslot (project-specific); properties of the
subslot
• Input INDEX: index of the data record
Note: Write data record
uWrite the data record with the function block WRREC.
uObserve read and write permissions!
Specific parameters:
• Input ID: HW-ID of the slot (project-specific); properties of the slot
• Input INDEX: index of the data record
Remote I/O module 16 DI AL4002
47
10 Maintenance, repair and disposal
The operation of the unit is maintenance-free.
uDispose of the device in an environmentally friendly way in accordance with the applicable national
regulations when it is no longer used.
10.1 Cleaning
uDisconnect the unit from the voltage supply.
uClean the device from dirt using a soft, chemically untreated and dry cloth.
uIn case of severe soiling, use a damp cloth.
uDo not use any caustic cleaning agents for this!
10.2 Update firmware
The system software of the device can be updated using the following options:
• IoT-Core Visualizer
• IoT-Core REST API
AL4002 Remote I/O module 16 DI
48
11 Appendix
11.1 ifm IoT Core
11.1.1 Profiles
Profile Description
blob Binary Large Object
deviceinfo Identification information of a device
devicetag Device-specific identification
devicereset Restart and reset to factory settings
network Network
parameter Parameter
processdata Process data
service Service
software Software
software/uploadablesoft-
ware
Upgradeable software
11.1.2 Types
Type Description
structure Structural element (e.g. a folder in the file system)
service Service that can be addressed from the network
event An event that can be started by the firmware and sends messages.
data Data point
device Root element a device represents
11.1.3 Services
11.1.3.1 Service: factoryreset
Name: factoryreset
Description: The service sets the parameters of the device to the factory settings.
Request ("data” field): none
Return ("data" field): none
11.1.3.2 Service: force_counter_values
Name: force_counter_values
Description: The service writes the values of the main counter and batch counter. The service can only
be executed if there is no connection to the fieldbus controller.
Request ("data” field):
Parameter Mandatory
field Data type Description
maincounter_value Optional INT Main counter target value
Remote I/O module 16 DI AL4002
49
Parameter Mandatory
field Data type Description
batchcounter_value Optional INT Batch counter target value
Return (“data” field): none
11.1.3.3 Service: getblobdata
Name: getblobdata
Description: The service reads a Binary Large Object (blob).
Request (“data“ field):
Data field Mandatory
field Data type Description
pos mandatory NUMBER Byte position
length mandatory NUMBER Size of the object (number of bytes)
Return ("data" field):
Data field Mandatory
field Data type Description
data mandatory STRING data to be decoded (BASE64 coded)
crc optional HEX STRING CRC of the data after decoding
md5 optional HEX STRING MD5 checksum of the data after decoding
11.1.3.4 Service: getdata
Name: getdata
Description: The service reads the value of a data point and outputs it.
Request ("data” field): none
Return data ("data" field):
Parameter Mandatory
field Data type Description
value mandatory STRING Value of the data point
11.1.3.5 Service: getdatamulti
Name: getdatamulti
Description: The service sequentially reads the values of several data points and provides them. The
value and the diagnostic code are provided for each data point.
Request ("data" field):
Data field Mandatory
field Data type Description
datatosend mandatory ARRAY OF
STRINGS
List of data points to be requested; Data points must support the getda-
ta service ("datatosend":["url1", "url2",..., "urlx"])
Return ("data" field):
Data field Mandatory
field Data type Description
url mandatory STRING Data point request
code mandatory INT Diagnostic code of the request
data mandatory STRING Value of the data point
AL4002 Remote I/O module 16 DI
50
11.1.3.6 Service: getelementinfo
Name: getelementinfo
Description: The service reads the properties of an element of the IoT tree.
Request ("data" field):
Parameter Mandatory
field Data type Description
adr mandatory STRING URL of the element whose proerties are to be changed
Return ("data" field):
Parameter Mandatory
field Data type Description
identifier mandatory STRING Identifier of the element
type mandatory STRING Type of the element
format optional JSON object Format of the data or of the service content
uid optional STRING
profiles optional JSON-AR-
RAY
Element profiles
hash optional STRING
11.1.3.7 Service: getidentity
Name: getidentity
Description: The service reads device information and outputs it.
Request (field „data“): none
Response (field „data“):
Parameter Mandatory
field Data type Description
iot device Device description as JSON object
iot.name mandatory STRING Type of the element
iot.uid optional STRING
iot.version mandatory STRING
iot.catalogue optional ARRAY OF
OBJECTS
iot.deviceclass optional ARRAY OF
STRING
Device class
iot.serverlist optional ARRAY OF
OBJECTS
device optional Article nummer
device.serialnumber optional Serial number
device.hwrevision optional Hardware version
device.swrevision optional Software version
device.custom optional
11.1.3.8 Service: gettree
Name: gettree
Description: The service reads the device description of the IO-Link master and outputs it as a JSON
object. The output can be limited to a subtree of the device description.
Remote I/O module 16 DI AL4002
51
Request (“data” field):
Parameter Mandatory
field Data type Description
adr Optional STRING Root element of the subtree
level Optional STRING Max. level up to which the subtree is output
• no entry: all levels will be displayed
• 0: do not display sub-elements (“subs”)
• 1: display sub-elements
• 2: display sub-elements up to the 2nd level
• 3: display sub-elements up to the 3rd level
...
• 20: display sub-elements up to the 20th level
Return (“data” field)
Parameter Mandatory
field Data type Description
identifier Mandatory STRING Identifier of the root element
type Mandatory STRING Type of the element
format Optional JSON object Format of the data content
uid Optional STRING
profiles Optional JSON array
subs Mandatory JSON array Sub-elements
hash Optional STRING
adr Mandatory STRING Root element of the subtree
11.1.3.9 Service: install
Name: install
Description: The service installs the firmware stored in a memory area of the unit.
Request ("data" field): none
Return ("data" field): none
11.1.3.10 Service: querytree
Name: querytree
Description: The service searches a device tree for the criteria , and andprofile type name
outputs a list with the URLs of the elements found. At least one of the search criteria must be
specified. The service can only be executed on the root node of the machine.
Request ("data" field):
Parameter Mandatory
field Data type Description
profile optional STRING Profile of the searched element
type optional STRING Type of the searched element
name optional STRING Type of the searched element
Return ("data" field):
Parameter Mandatory
field Data type Description
urlList mandatory ARRAY Array with URLs of the found elements; URLs are separated by com-
mas
AL4002 Remote I/O module 16 DI
52
11.1.3.11 Service: reboot
Name: reboot
Description: The service reboots the device.
Request ("data" field): none
Return ("data" field): none
11.1.3.12 Service: setblock
Name: setblock
Description: The service simultaneously sets the values of several data points of a structure.
Request ("data" field):
Parameter Mandatory
field Data type Description
datatoset mandatory ARRAY OF
OBJECTS
List of data points and their new values; Data points must support the
setdata service
consitent optional BOOL IO-Link subindex of the parameter
Return ("data" field): none
11.1.3.13 Service: setdata
Name: setdata
Description: The service sets the value of the data point.
Request ("data" field):
Parameter Mandatory
field Data type Description
newvalue mandatory STRING New value of the data point
duration optional STRING Duration of value storage
• lifetime: Value is saved with IoT Core; Value remains valid even after
restart of the device
• uptime: Value is saved until the next restart of the device
Return ("data" field): none
11.1.3.14 Service: signal
Name: signal
Description: The service triggers the flashing of the status LEDs of the unit.
Request ("data" field): none
Return ("data" field): none
11.1.3.15 Service: start_stream_set
Name: start_stream_set
Description: The service starts the sequential transmission of several data fragments.
Request ("data" field):
Parameter Mandatory
field Data type Description
size mandatory STRING Overal length of the data to be transmitted (number of bytes)
Return ("data" field): none
Remote I/O module 16 DI AL4002
53
11.1.3.16 Service: stream_set
Name: stream_set
Description: The service transfers a data segment.
Request ("data" field):
Parameter Mandatory
field Data type Description
value mandatory BIN
(BASE64)
Segment of the binary data (BASE64-coded)
Return ("data" field): none
AL4002 Remote I/O module 16 DI
54
11.2 PROFINET
11.2.1 Parameters
11.2.1.1 Modules: 8x2DI + Qualifier
Parameter Description Values Access
Debounce Time Debounce time (value * 0.1ms) • 0: 0ms (default)
…
• 500: 50ms
rw 1
Hold time Hold time (value * 0.1ms) • 0: 0ms (default)
…
• 60000: 6000ms
rw 1
Hold level Hold level • 0: Low: hold LOW
• 1: High: hold HIGH (default)
rw 1
Input Inverter signal inversion • 0: Signal not inverted: do not
invert signal (default)
• 1: Signal inverted: invert signal
rw 1
1read and write
Remote I/O module 16 DI AL4002
55
11.2.1.2 Modules: Counter module
Submodule: CTU
Parameter Description Values Access
Enable Main counter
event
Notifications for main counter • : disable
• : enable (default)
rw 1
Enable Main counter
event
Notifications for batch counter • : disable
• : enable (default)
rw 1
Pin 2 function function of pin 2 of the port • Not used: no function (default)
• Reset main & batch counter: Reset
main counter and batch counter
• Disable main & batch counter:
Disable main counter and batch
counter
rw 1
Main Threshold Threshold CT of the main counter • 1
…
• 4294967295 (default)
rw 1
Batch Threshold Threshold CTb of the batch counter • 1
…
• 65535 (default)
rw 1
1read and write
Remote I/O module 16 DI AL4002
57
Submodule: CTUD
Parameter Description Values Access
Enable Main counter
event
Notifications for main counter • : disable
• : enable (default)
rw 1
Enable Main counter
event
Notifications for batch counter • : disable
• : enable (default)
rw 1
Pin 2 function function of pin 2 of the port • Counter edge input 2: counting
input (default)
rw 1
Main Threshold Threshold CT of the main counter • 1
…
• 4294967295 (default)
rw 1
Batch Threshold Threshold CTb of the batch counter • 1
…
• 65535 (default)
rw 1
1read and write
AL4002 Remote I/O module 16 DI
58
Submodule: CTDIR
Parameter Description Values Access
Enable Main counter
event
Notifications for main counter • : disable
• : enable (default)
rw 1
Enable Main counter
event
Notifications for batch counter • : disable
• : enable (default)
rw 1
Pin2 function / Count
direction selection
Pin 2 function of the port and selection of the
control instance for selecting the counting di-
rection
• Pin2 Count direction: signal at pin 2
controls counting direction
• Pin2 Not used & Count Direction by
PLC: pin 2 without function;
selection of counting direction via
PLC
• Pin2 Reset Counter & Count
Direction by PLC: signal at pin 2
resets main counter and batch
counter; selection of counting
direction via PLC
• Pin2 Reset Counter & Count
Direction by PLC: signal at pin 2
deactivates main counter and batch
counter; selection of counting
direction via PLC
rw 1
Main Threshold Threshold CT of the main counter • 1
…
• 4294967295 (default)
rw 1
Batch Threshold Threshold CTb of the batch counter • 1
…
• 65535 (default)
rw 1
1read and write
Remote I/O module 16 DI AL4002
59
11.2.2 Cyclic data
11.2.2.1 Modules: 8x2DI + Qualifier
Input data: 4 bytes
Byte (off-
set)
Bit
7 6 5 4 3 2 1 0
n X4 (pin 2):
DI
X4 (pin 4):
DI
X3 (pin 2):
DI
X3 (pin 4):
DI
X2 (pin 2):
DI
X2 (pin 4):
DI
X1 (pin 2):
DI
X1 (pin 4):
DI
n+1 X8 (pin 2):
DI
X8 (pin 4):
DI
X7 (pin 2):
DI
X7 (pin 4):
DI
X6 (pin 2):
DI
X6 (pin4):
DI
X5 (pin2):
DI
X5 (pin4):
DI
n+2 X4 (pin 2):
QDI
X4 (pin 4):
DQI
X3 (pin 2):
QDI
X3 (pin 4):
DQI
X2 (pin 2):
QDI
X2 (pin 4):
DQI
X1 (pin 2):
QDI
X1 (pin 4):
DQI
n+3 X8 (pin 2):
QDI
X8 (pin4):
DQI
X7 (pin 2):
QDI
X7 (pin 4):
DQI
X6 (pin 2):
QDI
X6 (pin4):
DQI
X5 (pin2):
QDI
X5 (pin4):
DQI
Legend:
• DI Signal level of the digital input 1 bit • 0: LOW
• 1: HIGH
• QDI Validity of the process value of the digital input 1 bit • 0: invalid
• 1: valid
Output data: none
AL4002 Remote I/O module 16 DI
62
11.2.2.4 Submodule: CTUD
Input data: 6 bytes
Byte (off-
set)
Bit
7 6 5 4 3 2 1 0
0…3 Main Counter Value
4…5 Batch Counter Value
Legend:
• Main Counter Value Current main counter value
Main Counter Value = 0x12345678
• Main Counter Value[0] = 0x12
• Main Counter Value[1] = 0x34
• Main Counter Value[2] = 0x56
• Main Counter Value[3] = 0x78
UINT32 • 0x00000000: 0
…
• 0xFFFFFFFE:
4294967294
• Batch Counter Value Current batch counter value
Batch Counter Value = 0x1234
• Batch Counter Value[0] = 0x12
• Batch Counter Value[1] = 0x34
UINT16 • 0x0000: 0
…
• 0xFFFE: 65534
Output data: 1 byte
Byte (off-
set)
Bit
7 6 5 4 3 2 1 0
0 Reserved Disable
Counter
Reset
Counter
Legend:
• Reset Counter Reset main counter and batch counter to initial value 1 bit • 0x0: no action
• 0x1: reset
• Disable Counter Disable main counter and batch counter 1 bit • 0x0: no action
• 0x1: disable

Termékspecifikációk

Márka: IFM
Kategória: nincs kategorizálva
Modell: AL4002

Szüksége van segítségre?

Ha segítségre van szüksége IFM AL4002, tegyen fel kérdést alább, és más felhasználók válaszolnak Önnek


Útmutatók nincs kategorizálva IFM

IFM

IFM PE2599 Útmutató

23 Március 2025
IFM

IFM MK5312 Útmutató

23 Március 2025
IFM

IFM RU6035 Útmutató

18 Március 2025
IFM

IFM SF3210 Útmutató

18 Március 2025
IFM

IFM RU6045 Útmutató

18 Március 2025
IFM

IFM KI0200 Útmutató

18 Március 2025
IFM

IFM PT2400 Útmutató

16 Január 2025
IFM

IFM O2D532 Útmutató

16 Január 2025
IFM

IFM PA3027 Útmutató

16 Január 2025
IFM

IFM TW2001 Útmutató

14 Január 2025

Útmutatók nincs kategorizálva

Legújabb útmutatók nincs kategorizálva

Targus

Targus APK032US Útmutató

2 Április 2025
Beghelli

Beghelli Formula 65 LED HT Útmutató

2 Április 2025
Simrad

Simrad NEP-3 Útmutató

2 Április 2025
Simrad

Simrad S3100H Útmutató

2 Április 2025
Supermicro

Supermicro H14SHM Útmutató

2 Április 2025
Supermicro

Supermicro X14SBI-TF Útmutató

2 Április 2025
Vogel's

Vogel's PFW 6880 Útmutató

2 Április 2025
Hager

Hager ARF560D Útmutató

2 Április 2025
Leba

Leba NoteBox Mobile 32 Útmutató

2 Április 2025
Lowel

Lowel CGA-40B Útmutató

2 Április 2025