As 121899 DL-PN1 Um 997GB WW GB 2071 2

997GB
PROFINET Communication Unit
DL-PN1 (IX-H/IX)
User's Manual
Read this manual before use.
Keep this manual in a safe place for future reference.
Introduction
This manual describes the basic operations and hardware functions of the DL-PN1.
Read the manual carefully to ensure safe performance and function of the DL-PN1.
Keep this manual in a safe place for future reference.
Ensure that the end user of this product receives this manual.
 Symbols
The following symbols alert you to matters concerning the prevention of injury and
product damage.
It indicates a hazardous situation which, if not avoided, could result in

WARNING
death or serious injury.
It indicates a hazardous situation which, if not avoided, could result in

CAUTION
minor or moderate injury.
It indicates a situation which, if not avoided, could result in product

NOTICE
damage as well as property damage.
Important It indicates cautions and limitations that must be followed during

operation.
Point It indicates additional information on proper operation.
Reference It indicates tips for better understanding or useful information.

Overview of PROFINET
What is PROFINET?
PROFINET is an open industrial networking standard developed and maintained by the
PI (PROFIBUS & PROFINET International).
All supported devices can use the communication network regardless of the vendor.
PROFINET allows easy integration with the currently used field bus (such as
PROFIBUS), enabling you to protect the existing assets without modifying the legacy
system.
The PROFINET communication for the DL-PN1 series supports the PROFINET I/O
communication, which transmits data between I/O controllers (PLC etc.) and I/O
devices, and complies with Conformance Class A.
The PROFINET I/O communication offers the following two types of communication
methods for cyclic data: Real-time communication (RT) and isochronous real-time
communication (IRT).
Real-time communication provides similar communication performance as the existing
field bus, such as the device control in normal factory automation, using Ethernet. The
isochronous real-time communication is capable of meeting stringent real-time
requirements, including synchronized motion control.
The real-time communications offer the following two types of communications: Data I/O
communication for sending and receiving data periodically, and record data
communication for sending and receiving commands/responses at arbitrary timings. In
the data I/O communication, you can set the Update time (Communication cycle) based
on the priority of the data to be sent/received, enabling sending/receiving of data with
adjusted overall communication load. The record data communication is used for
communication applications that require little punctuality (unlike the data I/O
communication).
The DL-PN1 Series supports real-time data I/O communication and record data
communication.
997GB 1
Specifying the IP address using the DCP protocol
In the PROFINET communication, you can specify the IP address of I/O devices using
the DCP protocol (Discovery and Configuration Protocol).
The DCP protocol offers two methods for setting the IP address.
(1) The IP address can be set by the I/O controller based on the device name
information of the I/O device.
(2) The IP address and device name of the I/O device can be set by the I/O supervisor
(PC, etc.).
(1) Check the presence of an I/O device
(2) Response
PROFINET
communication
(3) Set the IP address
I/O Controller
(4) Response
I/O device
Reference If the IP address of the I/O device will be set by the I/O controller, the I/O
device name must match the name in the config of the I/O controller.
2 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Communicating with the IX-H/IX
Types and Number of Connectable Sensor Amplifiers
 Number of connectable sensor amplifiers

Maximum number of
Name Amplifier form Main unit Expansion unit
connectable units
DIN rail mounting 2 (1 main unit,
IX IX-1000 IX-1050
type 1 expansion unit)
The DL-PN1 cannot be used together with sensor amplifiers (main unit/expansion unit)
when the IX is connected.
RST
LINK
/ACT
SF
BF
DL-PN1
IX-1050 IX-1000 DL-PN1
Maximum number of
Name Amplifier form Main unit Expansion unit
connectable units
DIN rail mounting 2 (1 main unit,
IX-H IX-H2000 IX-H2050
type 1 expansion unit)
The DL-PN1 cannot be used together with sensor amplifiers (main unit/expansion unit)
when the IX-H is connected.
RST
LINK
/ACT
SF
BF
DL-PN1
IX-H2050 IX-H2000 DL-PN1
* IX and IX-H amplifiers cannot be connected to the unit at the same time.
The only expansion unit that can be connected to the IX-H2000 is the IX-H2050.
The only expansion unit that can be connected to the IX-1000 is the IX-1050.
- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 3

Communication Data Allocation Setting and Measurement Value Number
With the DL-PN1, the tool result allocated with the [Output Assignment] setting of the
IX-H/IX is output as [measurement value n (n: 1 to 15)].
(For details on the [Output Assignment setting], see the IX-H User's Manual or the IX
Series User's Manual.)
Important With an expansion unit connected, it is necessary to select [Main/

Expansion] for [Apply to:] in order to use the I/O functions of the
expansion unit. (When only using a main unit, use the [Main unit only]
setting.)
The [Output Assignment] setting assigns the "measurement value" of
each tool. To use the I/O functions, it is not necessary to separately set
the [Output Assignment].
The IX [Output Assignment] setting screen is shown below.
The following tools can be allocated to numbers 1 to 15.

Main unit tool Expansion unit tool
OFF (default value) -
Main unit: Tool 01 Exp. unit: Tool 01
: :
Main unit: Pos. adjust Exp. unit: Pos. adjust
Main unit: Tilt adj (Scan) Exp. unit: Tilt adj (Scan)
Main unit: Tilt adj (Line) Exp. unit: Tilt adj (Line)

For example, if the communication data has been allocated as shown in the following figure,
the measurement values are assigned to measurement values 1 to 15 as shown below.
Measurement Value 1: Main unit: Tool 01 Measurement Value 9: Exp. unit: Tool 01
Measurement Value 7: Main unit: Tool 07 Measurement Value 15: Exp. unit: Pos. adjust
Measurement Value 8: Main unit: Pos. adjust
Invalid (----) is the result of measurement values for which "OFF" is selected.

 Byte Swapping (used when changing the FTP transmission file name)
To enable data area byte swapping, select
[Enable].
Point You can change the order in which data is stored in memory. The
storage order can be changed in units of two bytes.
• Disable: Low to high (example: ABCDEF)
• Enable: High to low (example: BADCFE)
Set byte swapping to match the specifications of the PLC. For details,
see the user's manual of the PLC.
 Pin Height Tool Output (IX-H only)

Set the output method of the pin height
tool.
Select from Separate, MAX/MIN, and
Worst Value.
For details on the setting method, refer to
the IX-H User's Manual.

DL-PN1 PROFINET Communication Overview
The DL-PN1 enables you to check various settings and conditions of the sensor
amplifier via PROFINET.
Examples are shown below.
Data I/O Record Data Reference
Item
Communication Communication page
Reading the sensor amplifier control output   19
Executing the external input to the sensor amplifier   19
Reading the sensor amplifier measurement value   22
Changing the sensor amplifier program   23
DL-PN1 PROFINET functions are specified in a GSDML file.
You can download the GSDML file from the KEYENCE website:
http://www.keyence.com
Data I/O Communication

 What is data I/O communication?
This function enables cyclic (i.e. in fixed intervals) data communications with the
PROFINET devices. This function provides high-speed control with several to several
tens of milliseconds.
The communication can be controlled by referencing and updating the variables in the
PLC, making it easy to control the programs on the PLC side.
PROFINET
communication
I/O Controller
Input Area Output Area
∙ Status result ∙ Status result

∙ Control/status/error result ∙ Control/status/error result
∙ Read measurement value Update time ∙ Read measurement value
(Communication
Output Area cycle) Input Area
∙ Execute external input ∙ Execute external input
Point • Communication settings for the data I/O communication, such as

Update time (communication cycle) and the data size, will be
configured on the PLC side.
• In a network with many connected devices (including the PROFINET
devices), a network delay and/or packet loss may occur when there
is a heavy load on the network. Conduct a thorough verification
before the operation.

Precautions When Using TIA Portal Made by Siemens
When selecting IX-H/IX slave modules from the [Hardware catalog] and registering
these modules to the [Device overview], the number of IX-H/IX slave modules that can
be registered varies depending on:
• Whether the IX-H/IX is used as a main unit or expansion unit.
• The [Output Assignment] setting on the [Communication unit (DL) settings] screen.
(a) When using the unit only as a main unit

When using the unit only as a main unit, it is necessary to register three or more IX-H/IX
slave modules.
Important When using the unit only as a main unit, communication will not be
performed correctly if the number of IX-H/IX slave modules is two or
less.
If [Output Assignment] on the [Communication unit (DL) settings] screen is set to the
range of 1 to 3, the number of slave modules to register is 3.
Example: If 1 and 2 are selected for [Output Assignment], register three slave modules.

When 4 or a higher number is selected with [Output Assignment] on the
[Communication unit (DL) settings] screen, the number of slave modules to register is
equivalent to the largest number among the numbers assigned with [Output
Assignment].
Example: If 1, 2, and 5 are selected for [Output Assignment], register five slave modules.
(b) When using the unit as a main unit/expansion unit

When using the unit as a main unit/expansion unit, it is necessary to register six or more
IX-H/IX slave modules.
Important When using the unit as an expansion unit, communication will not be
performed correctly if the number of IX-H/IX slave modules is five or
less.

If [Output Assignment] on the [Communication unit (DL) settings] screen is set to the
range of 1 to 6, the number of slave modules to register is 6.
Example: If 1 to 4 are selected for [Output Assignment], register six slave modules.
When 7 or a higher number is selected with [Output Assignment] on the

[Communication unit (DL) settings] screen, the number of slave modules to register is
equivalent to the largest number among the numbers assigned with [Output
Assignment].
Example: If 1 to 8 are selected for [Output Assignment], register eight slave modules.

 Data I/O communication device map (DL-PN1  PROFINET I/O controller)
 DL-PN1 (Slot 0)
 Input
Address Bit Function name Description Value
0 to 6 Reserved for system - -
Stores the error status of the sensor
0 amplifiers. 0: No error occurred.
7 Error status
"Types of error and error code" 1: Error occurred.
(page 61)
1 to 15 0 to 7 Reserved for system - -

 Sensor amplifier (Slot 1 to 15)
 Input
Slot 1
Stores the response to a program
Program change response 0: No input
0 change input applied to the sensor
(main unit) 1: Input reception
amplifier.
Stores the response to a trigger/
Trigger/timing response 0: No input
1 timing input applied to the sensor
amplifier.
Zero/offset response Stores the response to a zero/offset 0: No input
16 2
(main unit) input applied to the sensor amplifier. 1: Input reception
Reverses the ON/OFF state when the 0 1:
Measurement value result
3 measurement value is updated Switched when the comparison
update complete (main unit)
(toggle operation). result is updated.
Emission stop status 0: No input
4 Stores the emission stop status.
0 Reserved for system - -
Stores the measurement value 1 0: Normal
1 Measurement value 1 invalid
invalid ("----") status. 1: Measurement value invalid "----"
0: Normal
Measurement value 1 under Stores the measurement value 1
2 1: Measurement value under range
range under range status ("−FFFF").
"−FFFF"
17
0: Normal
Measurement value 1 over Stores the measurement value 1 over
3 1: Measurement value over range
range range status ("FFFF").
"FFFF"
0: No error occurred.
7 Error status (main unit) -
1: Error occurred.
18 0 to 7 Reserved for system - -
Used when reading measurement
19 to 22 0 to 7 Measurement value 1*3 INT32(LITTLE)
value 1.

Slot 2
Stores external output 1 of the main 0: OFF
0 External output 1 (main unit)
unit.*1 1: ON
unit.*1 1: ON
23 unit.*1 1: ON
unit.*1 1: ON
unit.*1 1: ON
0: Normal
24 range under range status ("−FFFF").
"−FFFF"
0: Normal
"FFFF"
value 2.
Slot 3
unit.*1 1: ON
unit.*1 1: ON
30 unit.*1 1: ON
unit.*1 1: ON
External output 10 Stores external output 10 of the main 0: OFF
4
(main unit) unit.*1 1: ON
0: Normal
"−FFFF"
0: Normal
"FFFF"
value 3.

Slot 4

Stores the response to a program
Program change response 0: No input
0 change input applied to the sensor
(expansion unit) 1: Input reception
amplifier.
Stores the response to a trigger/
Trigger/timing response 0: No input
1 timing input applied to the sensor
amplifier.
Zero/offset response Stores the response to a zero/offset 0: No input
37 2
(expansion unit) input applied to the sensor amplifier. 1: Input reception
Measurement value result Reverses the ON/OFF state when the 0 1:
3 update complete measurement value is updated Switched when the comparison
(expansion unit) (toggle operation). result is updated.
Emission stop status 0: No input
4 Stores the emission stop status.
0: Normal
range under range status ("−FFFF").
"−FFFF"
38
0: Normal
"FFFF"
1: Error occurred.
value 4.

Slot 5
External output 1 Stores external output 1 of the 0: OFF
0
(expansion unit) expansion unit.*1 1: ON
1
2
44 (expansion unit) expansion unit.*1 1: ON
3
4
0: Normal
"−FFFF"
0: Normal
"FFFF"
value 5.
Slot 6

0
1
2
51 (expansion unit) expansion unit.*1 1: ON
3
4
0: Normal
"−FFFF"
0: Normal
"FFFF"
value 6.

Slot 7 to 15

16+7(n-1) 0 to 7 Reserved for system - -
Stores the measurement value n 0: Normal
1 Measurement value n invalid
invalid ("----") status.*2 1: Measurement value invalid "----"
0: Normal
Measurement value n under Stores the measurement value n
range under range status ("−FFFF").*2
"−FFFF"
17+7(n-1)
0: Normal
Measurement value n over Stores the measurement value n over
range range status ("FFFF").*2
"FFFF"
1: Error occurred.
18+7(n-1) 0 to 7 Reserved for system - -
19+7(n-1)
to 0 to 7 Measurement value n *3 INT32(LITTLE)
value n.*2
22+7(n-1)
*1 The output type of external outputs 1 to 10 depends on the IX-H/IX "4. Output
assignment" setting. For details, see the IX-H User's Manual or the IX Series User's
Manual.
*2 "n" indicates the slot number. For example, with slot 7, octets 61 to 64 become
measurement value 7.
*3 Measurement values indicate the measurement values assigned with the [Output
Assignment] setting of the IX-H/IX.
For details, see "Communication Data Allocation Setting and Measurement
Value Number" (page 4).
 Data I/O communication device map (PROFINET I/O controller  DL-PN1)
 DL-PN1 (Slot 0)
 Output

 Sensor amplifier (Slot 1 to 15)
 Output
Slot 1
Trigger/timing request Sends a request for trigger/timing 0: OFF
0
(main unit) input to the sensor amplifier. 1: ON
Zero/offset request (main Sends a request for zero/offset input 0: OFF
1
unit) to the sensor amplifier. 1: ON
1 0: OFF
2 Reset request (main unit) Request the reset input.
1: ON
Emission stop request (main Sends a request for emission stop 0: OFF
3
unit) input. 1: ON
Slot 2

Program change request Sends a request for a program 0: OFF
0
(main unit) change to the sensor amplifier. 1: ON
Change program number bit Requests bit 0 of the change program
1
0 (main unit) number.
2
2 1 (main unit) number. 0: OFF
Change program number bit Requests bit 2 of the change program 1: ON
3
4
Slot 3

Slot 4

Trigger/timing request Sends a request for trigger/timing 0: OFF
0
(expansion unit) input to the sensor amplifier. 1: ON
Zero/offset request Sends a request for zero/offset input 0: OFF
1
(expansion unit) to the sensor amplifier. 1: ON
4 Reset request (expansion 0: OFF
2 Request the reset input.
unit) 1: ON
Emission stop request Sends a request for emission stop 0: OFF
3
(expansion unit) input. 1: ON

Slot 5

Program change request Sends a request for program change 0: OFF
0
(expansion unit) input to the sensor amplifier. 1: ON
1
0 (expansion unit) number.
2
5 1 (expansion unit) number. 0: OFF
Change program number bit Requests bit 2 of the change program 1: ON
3
4
Slot 6 to 15

6 to 15 0 to 7 Reserved for system - -
 Communication Methods
The following describes how the I/O controller communicates with the DL-PN1 (data I/O
communication).
• "Reading an output from a sensor amplifier" (page 19)
• "Applying an external input to a sensor amplifier (other than emission stop input)"
(page 19)
• "Reading measurement values from sensor amplifiers" (page 22)

Reading an output from a sensor amplifier
Available outputs: External outputs 1 to 10
This example illustrates how to read external output 1 of the main unit.
PLC
1
Bit 0 of input address 23 of
0
slot 2
Sensor amplifier (1)

ON
Output
OFF
External output 1 of the main unit
This example illustrates how to read external output 1 of the main unit.
(1) The output from the sensor amplifier entered into Bit 0 of the input address 23 via
data I/O communication.
Applying an external input to a sensor amplifier (other than

emission stop input)
Available external inputs: Trigger/timing request, zero/offset request, reset request
This example illustrates how to apply trigger/timing input to a main unit.
PLC (1)
1
Trigger/timing input request
0
Bit 0 of output address 1 of slot 1
(2)
1
Trigger/timing input response
0
Bit 1 of input address 16 of slot 1
Sensor amplifier
ON
External input
OFF
TIMING input of ID01
(1) The output address value to which a trigger/timing input (main unit) was assigned is
linked via data I/O communication and the trigger/timing input (main unit) of the
sensor amplifier is turned on or off.
(2) The input status of the sensor amplifier can be checked with the trigger/timing input
response.
Point • The corresponding input response signal is not contained in the

[reset request]. Use the timing with which the [measurement value
result update complete] bits are reversed as a reference.
• [Zero/offset request] must maintain the ON state (1) until [zero/offset
response] changes from 0 to 1.
• When the [main-unit-synchronized input] function is enabled, the
main unit and expansion unit are linked so that the external input
applied to the main unit is also applied to the expansion unit.
• The operation when an external input request from the amplifier and
an external input request through the main unit are applied with the
same timing is shown below.

- [Trigger/timing request] and [emission stop request]
The ON state of the input request through the external input of the
amplifier or the input request through the main unit is maintained.
If the other input turns ON, it is not executed. The input request
that is already ON stays ON, enabling this request.
- [Zero/offset request] and [reset request]
The ON state of the input request through the external input of the
amplifier or the input request through the main unit is maintained.
If the other input turns ON, it is executed. The input request is
executed on the rising edge (OFF ON) of the external input from
the amplifier or the external input through the main unit.
• The trigger/timing function cannot be executed when:
- The conditions are such that a trigger error occurs when the
trigger function is used.
When a trigger error occurs with trigger errors set to [enabled],
the [error status] changes from 0 to 1 and the error code of the
trigger error is stored in the [error code].
- Trigger/timing is applied to the expansion unit with [main-unit-
synchronized input] set to [enabled].
Even if trigger/timing cannot be executed, the trigger/timing
response turns ON.
• The zero offset function cannot be executed when:
- The conditions are such that a zero offset error occurs.
[Zero/offset response] changes from 0 to 1.
When a zero offset error occurs with zero offset errors set to
[enabled], the [error status] changes from 0 to 1 and the error
code of the zero offset error is stored in the [error code].
- The sensor is in setting mode.
- Zero offset is applied to the expansion unit with [main-unit-
synchronized input] set to [enabled].
In this situation, the [zero offset response] does not turn ON.

Applying an External Input to a Sensor Amplifier (Emission Stop Input)
Available external input: Emission stop
PLC (1)
Emission stop input request 1

Bit 3 of output address 1 0
of slot 1
(4)
Emission stop status 1
Bit 4 of input address 16 0
of slot 1
Sensor amplifier
Emission stop/release
processing
1 (2) (3)
Emission permitted Emission stopped Emission permitted
Emission stop status 0
This example illustrates how to apply an emission stop request to the main unit.
(1) When the [emission stop input request] changes from OFF (0) to ON (1), the
sensor's emission stop input changes from OFF to ON.*
(2) Emission is stopped while the emission stop input request is held as ON (1).
(3) The laser is emitted depending on the operating status while the emission stop input
request is held as OFF (0).
(4) The sensor's emission status can be checked with the [emission stop status].
* When the emission stop input function is assigned to the input (IN2 to IN8) of the
external I/O terminals of the sensor amplifier and the sensor amplifier is used at the
same time as the DL-PN1, the OR calculation will be performed on these inputs for
the emission stop input.
Point When the [main-unit-synchronized input] function is enabled, the main

unit and expansion unit are linked so that the external input applied to
the main unit is also applied to the expansion unit.

Reading measurement values from sensor amplifiers
PLC
(3)
Measurement value invalid
Each bit 1 of input address 17/24/31
of slot 1/2/3
(4)
Measurement value over range
of slot 1/2/3
(5)
Measurement value under range
of slot 1/2/3
Measurement value 1 1234 4567 7890

Input addresses 19 to 22 of slot 1


Measurement value result update 1 (2)

complete (main unit)
0
Bit 3 of input address 16 of slot 1
Measurement value result update 1

complete (expansion unit)
Bit 3 of input address 37 of slot 4 0
Sensor amplifier
Measurement value 1 (1)
(when a main unit tool has been 1234 4567 7890
allocated)
Measurement value 2
(when an expansion unit tool has 2345 5678 8901
been allocated)
Measurement value 3
(when a main unit tool has been 3456 6789 9012
allocated)
This example illustrates how to read measurement values 1 to 3 when main unit tools
have been assigned to measurement values 1 and 3 and an expansion unit tool has
been assigned to measurement value 2.
(1) When the measurement value of a sensor amplifier is updated, it is entered by cyclic
transfer.
If the value is normal, the parameter range is −999.97 to +999.98.
If the measurement value is over range, under range, or invalid, the previous value is
retained without updating the measurement value. Use the value with the
measurement value "invalid," "over," or "under."
(2) The bits of [measurement value result update complete] are switched when the
sensor amplifier measurement values are updated.
Bits are switched from 0 to 1 and from 1 to 0 after the previous measurement value
is updated.
(3) If the measurement value of a sensor amplifier is invalid, the bit corresponding to the
measurement value number of that sensor amplifier flips to 1.

(4) If the measurement value of a sensor amplifier is over range, the bit corresponding
to the measurement value number of that sensor amplifier flips to 1.
(5) If the measurement value of a sensor amplifier is under range, the bit corresponding
to the measurement value number of that sensor amplifier flips to 1.
Point When sample hold (level) is being used, the bits of [measurement
value result update complete] are switched when the sample hold is
applied or cleared. While the hold is being released, [measurement
value result update complete] is not switched.
Changing the program number of sensor amplifiers
PLC
(1)
Program number to change to bits 0 to 3 1 Program number C
Program number B
Bits 1 to 4 of output address 2 of slot 2 0
1 (2)
Program change request
Bit 0 of output address 2 of slot 2 0
1 (3)
Program change response
Bit 0 of input address 16 of slot 1 0
Sensor amplifier
Program change processing Change processing Change processing
Program number Program number A Program number B Program number C
This example illustrates how to change the program number of the main unit.
(1) Set the program number to change to with bits 0 to 3 of the "program number to
change to."
(2) When the "program change request" is executed (changed from 0 to 1), the program
change processing of the sensor is executed.
(3) When the program change processing on the sensor finishes, the "program change
response" changes from 0 to 1.
Point • The maximum number of programs that can be changed with cyclic
transfer is 16, ranging from programs 0 to 15. To change to program
17 or later, use the procedure under "Changing programs" (page
39).
• When changing the program from a PLC, you have to set the program
change method of the IX-H or the IX to "monitor/PC/communication."
• N, the number of the program to change to, must be maintained from
the execution of the "program change request" (changing from 0 to
1) to the "program change response" turning ON (changing from 0
to 1).

If this value is changed before the response turns ON (changes from
0 to 1), it may not be possible to change the program correctly.
• [Program change request] must maintain the ON state (1) until
[program change response] changes from 0 to 1.
• When the [main unit/expansion unit synchronized input] function is
enabled, the main unit and expansion unit are linked so that the
external input applied to the main unit is also applied to the
expansion unit.
• When the [main unit/expansion unit synchronized input] function is
enabled, the [program change response] only turns ON when the
main unit is successful.
Even if the expansion unit fails to change the program, this
response will still turn ON if the change is successful on the main
unit.
Also, if the main unit fails to change the program, the program will
not be changed on the expansion unit.
• The program cannot be changed when:
- [Program change method] is set to [external input].
- The sensor is in setting mode.
- A program change is executed on the expansion unit with [main
unit/expansion unit synchronized input] set to [enabled].
When the program change cannot be executed, the [program
change response] does not turn ON.

Record Data Communication
 What is record data communication?

Record data communication is a function that performs communication by issuing
commands when desired. It is used for applications that do not require the punctuality of
data I/O communication, such as checking I/O device settings.
I/O controller DL-PN1 Sensor amplifier
(1) Record data

communication command
Send Receive
(2) Interpret and

execute command
Receive Send
(3) Record data
communication response
 Basic Format and Flow of Record Data Communication

Record data communication uses function block, which blocks circuits being used in a
program. For Siemens SIMATEC Manager / TIA Portal, use SFB52"RD REC" and
SFB53"WR REC".
SFB52"RD REC" SFB53"WR REC"
Reads data. Writes data.
6)% 6)%
5HDGD3URFHVV'DWD5HFRUG :ULWHD3URFHVV'DWD5HFRUG
(1 5'5(& (1 (1 :55(& (1
5(4 9$/,' 5(4 9$/,'
,' %86< ,' %86<
,1'(; (5525 ,1'(; (5525
0/(1 67$786 0/(1 67$786
5(&25' /(1 5(&25'

Parameter name Description
EN Enables.
EN0 Shows that EN is enabled.
REQ Enables when making a request.
ID Enters 00 for the DL-PN1, 01 for the main unit, and 04 for the expansion unit.
INDEX Enters the Access Address Index number.
MLEN Set to 4.
RECORD A value is input when reading. Inputs a value when writing.
VALID Replies as to whether the action was valid.
BUSY Replies as to whether the unit is busy.
ERROR Replies as to whether there is an error.
STATUS Replies with status information (including error information).
LEN Replies the length of the reply data.
Point To input the device number for the DL-PN1 into ID, refer to the
instruction manual for each PLC. When inputting the device number of
the sensor amplifier connected to the DL-PN1 into ID, input the smaller
of the Slot I Address and Q Address. If Q Address will be input, add
32768(0x8000).
 Access Address (Slot 0)

Index Data
Function name Description Attribute Value
(DEC) type
0 to 31 Reserved for system
Stores the DL-PN1 error
status. 2byte
32 DL-PN1 error status R
"Types of error and error WORD
code" (page 61)
33 to 63 Reserved for system
When the sensor amplifier is
Bit1: Main unit
in the error state, the
2byte Bit4: Expansion unit
64 Sensor error status corresponding bit is set. R
WORD Bits other than those listed
"Types of error and error
above: Reserved for system
code" (page 61)
65 to
Reserved for system
194

 Access Address (Slot 1 to 15)
The slot numbers used when the IX-H or the IX is connected are shown below.
Slot 1: main unit
Slot 4: expansion unit
Slots 2 to 3 and slots 5 to 15: Not used
Index Data Default
(DEC) type value
000 Reserved
*1
Zero offset execution *2
001 DINT C 1
request *3
*4
*5
Zero offset clear execution *2
002 DINT C 1
request *6
*4
*7
003 Reset execution request DINT C 1
*4
4 to 32 Reserved
Bit 0: Internal communication error
Bit 1: Program corruption error
Bit 2: Nonvolatile memory error
Bit 3: Non-connected sensor head error
033 Sensor amplifier error status *8 DWORD R 0
Bit 10: System error
Bit 13: FTP error
Bit 14: Zero shift error
Bit 15: Trigger error
34 to 35 Reserved
Store the control output status.
bit0: OUT1
bit1: OUT2
bit2: OUT3
bit3: OUT4
036 Outputs 1 to 10 *9 DWORD R 0 bit4: OUT5
bit5: OUT6
bit6: OUT7
bit7: OUT8
bit8: OUT9
bit9: OUT10
37 to 42 Reserved
0: Program 0
1: Program 1
043 Current program number DINT R 0
:
31: Program 31
44 to 53 Reserved
0: Execution in progress
054 Zero offset execution result *10 DINT R 1 1: Normal termination
2: Abnormal termination
055 Reset execution result *11 DINT R 1 1: Normal termination
56 to 58 Reserved
Zero offset clear execution
059 *11 DINT R 1 1: Normal termination
result

Index Data Default
(DEC) type value
60 to
Reserved
128
Bits 0 to 3: Writing execution target
specification
Bit 0 ON: Transmission condition 1
*30
FTP file name writing
129 *31 DWORD R/W 0
execution request Bits 4 to 7: Reserved for system
*35
Bit 8: Writing to nonvolatile memory

ON: Write
OFF: Do not write
Bits 9 to 15: Reserved for system

FTP file name writing
130 *35 DWORD R 1 1: Normal termination
execution result
Bits 0 to 3: Reading execution target
specification
FTP file name reading *32 Bits 4 to 7: Reserved for system

131 DWORD R/W 0
execution request *35
Bit 8: Reading execution request
classification specification
ON: Read the file name saved to the
nonvolatile memory.
OFF: Read the current file name.
Bits 9 to 15: Reserved for system

FTP file name reading
132 *35 DWORD R 1 1: Normal termination
execution result
54 characters in ASCII format
*33 Acquires the file name (text input area) during
133 to FTP file names 1 to 27
*34 DWORD R/W 0 transmission with the FTP client function.
159 (for reading/writing)
*35 Alternatively, changes the file name (text input
area) during transmission.
160 Reserved
0: Trigger/timing input OFF
161 Trigger/timing input *12 DINT R/W 0
1: Trigger/timing input ON
0: Emission stop input OFF
162 Emission stop input *12 DINT R/W 0
1: Emission stop input ON
*13
Program change execution
163 *14 DINT R/W 0 0 to 31
request
*4
Program change execution
result

Index Data Default
(DEC) type value
Specify the number of the threshold to read.
Range: 0 to 32
0: Tool 1 lower limit threshold
1: Tool 1 upper limit threshold
Threshold reading execution *16 3: Tool 2 upper limit threshold
165 DINT R/W 0
request *17 4: Tool 3 lower limit threshold
:
32: Position adjustment lower limit threshold
Threshold reading execution *18
166 DINT R 1 1: Normal termination
result *17
*19
167 Threshold (for reading) DINT R 0 Parameter range: -999.99 to +999.99
*17
168 Threshold (for writing) *20 DINT R/W Parameter range: -999.99 to +999.99
Specify the number of the threshold to write.
Range: 0 to 32
Threshold writing execution *21 3: Tool 2 upper limit threshold
169 DINT R/W 0
request *20 4: Tool 3 lower limit threshold
:
32: Position adjustment lower limit threshold
*22 0: Execution in progress
Threshold writing execution
result
*20 2: Abnormal termination
Specify the number of the measurement
value to read (reading range: 0 to 18).
0: Tool 1
1: Tool 2
*24
Measurement value reading 2: Tool 3
171 *25 DINT R/W 0
execution request :
*26
15: Tool 16
16: Position adjustment
17: Tilt adjustment (scan)
18: Tilt adjustment (line)
*24 0: Execution in progress
Measurement value reading
execution result
*26 2: Abnormal termination
*24
Measurement value (for
173 *28 DINT R 0 Parameter range: -999.99 to +999.99
reading)
*26
174 to
Reserved
192
193 Product code DINT R 4026 4026
200 Product name 1 *29 STRING R "IX"
201 Product name 2 STRING R ""

Index Data Default
(DEC) type value
204 to
Reserved
255
*1 To check whether the zero offset has completed normally or not, read the "zero
offset execution result."
When performing the same execution request in succession, check that the
previous execution request is complete before performing the next execution
request. If the next request is executed while the previous request is being
executed, this next request will not be processed.
Also, when using an execution request with a different type of execution request,
execute the request after first checking that the other request is not being executed.
If a different execution request is performed while an execution request is being
performed, the execution result of this different request will be abnormal
termination.
*2 To record the zero offset status in nonvolatile memory, it is necessary to set the
zero/offset recording to [Use] by accessing [Sensor Expansion Settings] [Input
Settings] [Input Functions] [Zero/offset Recording].
*3 Zero/offset is not executed for tools that are not set as zero/offset targets in [Output
Assignment] [Expansion Functions] [Zero/offset Target Tools].
*4 When the main unit/expansion unit synchronized input function is enabled,
functions are executed on the expansion unit just by performing function execution
requests on the main unit. The execution result indicates only that of the main unit
(even if the expansion unit's execution fails, if the main unit succeeds, the result will
be normal termination).
*5 To check whether the zero offset clear has completed normally or not, read the
"zero offset clear execution result."
termination.
*6 Zero/offset clear is not executed for tools that are not set as zero/offset targets in
[Output Assignment] [Expansion Functions] [Zero/offset Target Tools].
*7 To check whether resetting has completed normally or not, read the "reset
execution result."

termination.
*8 Stores the error status.
When an error has occurred, the corresponding bit is ON.
(For details on the error bits, see the error list sheet.)
*9 Details of the output status can be checked by noting the ON/OFF state of each bit.
Regardless of the output mode, with the NO setting, bits that correspond to ON
output are 1, and bits that correspond to OFF output are 0.
*10 Abnormal termination occurs in the following situations.
(1) During execution of the function execution request from the DL, a different type
of function execution is requested.
Example: If zero offset execution is requested during reset execution request
processing
(2) The sensor amplifier is not in run mode.
(3) Among all the tools that can be executed (height, height difference, MAX/MIN,
calculation, area height, pin height, edge position, and width/diameter), it was
not possible for even one tool to perform the zero offset (zero offset execution
when measurement values are disabled).
(Tool measurement values are disabled in the following situations.
• The latest measurement value does not exist. [Immediately after operation,
after resetting, and when not even one comparison has been performed]
• There are no measurement values due to measurement not being possible.)
(4) An execution request targeted at the expansion unit was performed with no
expansion unit connected.
(5) An execution request targeted at the expansion unit was performed when the
main unit/expansion unit synchronized input function was enabled.
Example: If zero offset clear execution is requested during reset execution
request processing
*12 This turns OFF when the following three conditions are all met: (1) data "0" is
written, (2) the amplifier's external input is OFF, and (3) input has been turned OFF
with DL-PN1 cyclic communication.

*13 To check whether the program change has completed normally or not, read the
"program change execution result."
When performing requests in succession, check that the previous processing is not
being executed before performing an execution request. If the next request is
executed while the previous request is being executed, this next request will not be
processed.
*14 When executing a program change from the DL, it is necessary to set [Sensor
Expansion Settings] [Program Change Method] to [Monitor/PC/Communication
(DL)] on the IX-H or the IX.
Example: If program change execution is requested during reset execution
request processing
(5) [Program change method] is set to [external input].
*16 To check whether threshold reading has completed normally or not, read the
"threshold reading execution result."
processed.
*17 To read a threshold, perform the following three steps in order.
(1) Specify the threshold number with the [threshold reading execution request].
(2) Check the [threshold reading execution result].
(3) Read the [threshold (for reading)].
For details, see "Communication Examples With Message Communication"
(page 37).
Example: If threshold reading execution is requested during reset execution
request processing
(3) The tool of the specified threshold number does not exist. (Example: An
attempt was made to read the lower limit threshold of tool 2 regardless of tool 2
not being set.)

*19 Read the threshold after first checking that the [threshold reading execution result]
command has ended normally.
If the threshold (for reading) is read while the [threshold reading execution result]
command is being executed or has terminated abnormally, the threshold (for
reading) is set to the last threshold that was read with normal termination.
*20 To change a threshold, perform the following three steps in order.
(1) Write the threshold with the [threshold (for writing)].
(2) Specify the threshold number with the [threshold writing execution request].
(3) Check the [threshold writing execution result].
(page 37).
*21 To check whether the threshold writing execution request has completed normally
or not, read the "threshold writing execution result."
processed.
Example: If threshold writing execution is requested during reset execution
request processing
(3) An invalid threshold or threshold number is written.
*23 The following cases correspond to "An invalid threshold or threshold number is
written." listed above.
(1) The tool or the threshold of the specified threshold number does not exist.
Example: An attempt was made to write the lower limit threshold of tool 1
regardless of tool 1 not being set.
Example: An attempt was made to write the upper limit threshold of tool 2
regardless of tool 2 being a monochrome area tool and the upper
limit threshold being invalid.
(2) A value outside the range specified by the tool's upper and lower limits is set.
Example: An attempt was made to write "500" for the upper limit threshold of
tool 2 regardless of tool 1 being a monochrome area tool and the
upper limit threshold being valid with a setting scale of 0 to 200.
(3) An attempt was made to set the tool's lower limit threshold to a value greater
than the tool's upper limit threshold.
Example: An attempt was made to write +2.00 for the lower limit threshold of
tool 1 with the upper limit threshold of tool 1 set to +1.00.
(4) An attempt was made to set the tool's upper limit threshold to a value smaller
than the tool's lower limit threshold.

Example: An attempt was made to write +1.00 for the upper limit threshold of
tool 1 with the lower limit threshold of tool 1 set to +2.00.
*24 Measurement values indicate the measurement values assigned with the [Output
Assignment] setting of the IX-H or the IX.
For details, see "Communication Data Allocation Setting and Measurement
Value Number" (page 4).
*25 To check whether measurement value reading has completed normally or not, read
the "measurement value reading execution result."
processed.
*26 To read a measurement value, perform the following three steps in order.
(1) Specify the measurement value number with the [measurement value reading
execution request].
(2) Check the [measurement value reading execution result].
(3) Check the [measurement value (for reading)] result.
(page 37).
Example: If measurement value reading execution is requested during reset
execution request processing
(3) The tool of the specified measurement value number does not exist. (Example:
Regardless of tool 2 not being set, an attempt was made to read tool 2.)
*28 If the value is normal, the parameter range is −999.97 to +999.98.
When the measurement value is over range, "+999.99" is stored.
When the measurement value is under range, "−999.99" is stored.
When the measurement value is invalid, "−999.98" is stored.
*29 The read character string is stored as ASCII code.
*30 You can specify multiple transmission conditions.
Turning ON all the bits specifies transmission conditions 1 to 4.
Also, turning OFF bits 0 to 3 specifies transmission condition 1.
*31 The nonvolatile memory can be written to approximately 100,000 times.
When not writing to the nonvolatile memory, nothing is recorded when the sensor
turns OFF.
*32 You cannot specify multiple transmission conditions.
Also, turning OFF bits 0 to 3 specifies transmission condition 1.

*33 • Add a NULL (0x00) character after the character string that you want to change
to.
• The file name cannot be changed to the correct value if the NULL (0x00)
character is not added.
• If all 54 characters are rewritten, it is not necessary to add a NULL (0x00)
character.
• Example of changing the file name
DP-V1_Slot1/Slot4
File name
133 134 135 136 137 138 to 159
0x4142 0x4344 0x4546 0x0000 Writing not Writing not
ABCDEF
(AB) (CD) (EF) ([NUL][NUL]) required required
0x3132 0x3334 0x3536 0x3738 0x3900 Writing not
1234567
(12) (34) (56) (78) (9[NUL]) required
*34 • The data is all NULL (0x00) characters when no characters to read exist.
• The characters to read are output as ASCII code. Set byte swapping correctly to
match the specifications of the PLC.
• Example of reading the file name
DP-V1_Slot1/Slot4
File name
133 134 135 136 137 138 to 159
0x4142 0x4344 0x4546 0x0000 0x0000 0x0000
ABCDEF
(AB) (CD) (EF) ([NUL][NUL]) ([NUL][NUL]) ([NUL][NUL])
0x3132 0x3334 0x3536 0x3738 0x3900 0x0000
1234567
(12) (34) (56) (78) (9[NUL]) ([NUL][NUL])
*35 This can only be used by the IX-H2000, IX-H2050, IX-1000 (R2.00 and later
versions), and IX-1050 (R2.00 and later versions).

* Notices regarding function execution requests
When performing the applicable execution requests shown below, check that
execution is complete before performing the next function execution request.
• When performing the same execution request in succession, check that execution
is not in progress for the previous execution request before performing the next
execution request. Requests received during execution will be ignored.
• When performing different types of execution requests together, execute the
request after first checking that the other request is not being executed. The
execution result of requests received during execution of other requests will be
abnormal termination.
[Applicable execution requests]
• Zero offset execution request
• Zero offset clear execution request
• Reset execution request
• Program change execution request
• Threshold reading execution request
• Threshold writing execution request
• Measurement value reading execution request
• FTP file name writing execution request
• FTP file name reading execution request

Communication Examples With Message Communication
This section explains message communication examples of executing the following operations.
• Requesting zero offset execution
• Changing programs
• Reading comparison thresholds
• Changing comparison thresholds
• Reading measurement values
• Reading the FTP file name (text input area)
• Changing the FTP file name (text input area)
 Executing zero offset requests

Execute a zero offset request on the main unit.
(1) Write data to the [zero offset execution request].
(2) Read the [zero offset execution result].
(3) If the response is [0: Execution in progress], the processing is not yet complete, so
repeatedly read the result until a response of [1: Normal termination] is returned.
PLC side DL side

(1)
[Zero offset execution

request]
Command
ID (Slot number): 01
Index: 001
Response
(2)
[Zero offset execution

result]
Command
ID (slot number): 01
Index: 054
Response
NO
[0: Execution in
progress]*1
(3)
Is the response
[1: Normal termination]?
YES
Stop

*1 Possible causes for the [zero offset execution result] being [2: Abnormal
termination] are shown below.
• During execution of the function execution request from the DL, a different type
(Example: If zero offset execution is requested during reset execution request
processing)
• The sensor amplifier is not in run mode.
• Among all the tools that can be executed (height, height difference, MAX/MIN,
calculation, area height, pin height, edge position, and width/diameter), it was
not possible for even one tool to perform the zero offset.
The zero offset will not be executed normally when the measurement value is
invalid. Tool measurement values are disabled in the following situations.
- The latest measurement value does not exist. (Immediately after operation,
after resetting, and when not even one comparison has been performed)
- There are no measurement values due to measurement not being possible.
• An execution request targeted at the expansion unit was performed with no
• An execution request targeted at the expansion unit was performed when the

 Changing programs
This example illustrates how to change the program number of the main unit to 3.
(1) Use the [program change execution request] to write the number of the program to
change to.
(2) Read the [program change execution result]. Check that the result is [1: Normal
termination] and that the program change is complete.
If the result is [0: Execution in progress], the program change is not yet complete, so
(1) PLC side DL side
[Program change execution

request]
Command
Index: 163
Data to write: 00000003h
Response
(2)
[Program change execution

result]
Command
Index: 164
Response
NO
[0: Execution in
progress]*1
(3)
Is the response
YES
Stop
*1 Possible causes for the [program change execution result] being [2: Abnormal
Example: If program change execution is requested during reset execution
request processing

• An execution request targeted at the expansion unit was performed when the
• [Program change method] is set to [external input].

 Reading comparison thresholds
This example illustrates how to read the comparison threshold, 12.34, set to the "tool 3
upper limit threshold" of the expansion unit.
(1) Write the number corresponding to the threshold that you want to read in the
[threshold reading execution request].
(2) Read the [threshold reading execution result].
(4) After checking that you have received a response of [1: Normal termination], read
the [threshold reading execution result].
[Threshold reading execution request]
ID (Slot number): 04 Command

Index: 165
Response
(2)
[Threshold reading execution result]

Index: 166
Response
NO
[0: Execution in
progress]*1
(3)
Is the response
YES
(4)
[Threshold (for reading)]

Index: 167
Response
Example: 1234
Stop

*1 Possible causes for the [threshold reading execution result] being [2: Abnormal
(Example: If threshold reading execution is requested during reset execution
request processing)
• The tool of the specified threshold number does not exist.
(Example: An attempt was made to read the lower limit threshold of tool 2
regardless of tool 2 not being set.)

 Changing comparison thresholds
This example illustrates how to change "Tool 3 upper limit threshold" on the expansion
unit to 12.34.
(1) Write the threshold to change to in the [threshold (for writing)].
(2) Use the [threshold writing execution request] to write the threshold number (upper
limit or lower limit) of the number of the tool that you want to change.
(3) Read the [threshold writing execution result].
[Threshold (for writing)]

Command
ID (Slot number): 04 Example: 1234
Index: 168
Response
(2)
[Threshold writing execution

request]
Command
Index: 169
Response
(3)
[Threshold writing execution

result]
Command
Index: 170
Response
NO
[0: Execution in
progress]*1
(4)
Is the response
YES
Stop

*1 Possible causes for the [threshold writing execution result] being [2: Abnormal
Example: If threshold writing execution is requested during reset execution
request processing
• An invalid threshold or threshold number is written.
The following cases correspond to "• An invalid threshold or threshold number is

written." listed above.
(1) The tool or the threshold of the specified threshold number does not exist.
Example: An attempt was made to write the lower limit threshold of tool 1
regardless of tool 1 not being set.
Example: An attempt was made to write the upper limit threshold of tool 2
regardless of tool 2 being a monochrome area tool and the upper
limit threshold being invalid.
(2) A value outside the range specified by the tool's upper and lower limits is set.
Example: An attempt was made to write "500" for the upper limit threshold of
tool 2 regardless of tool 1 being a monochrome area tool and the
upper limit threshold being valid with a setting scale of 0 to 200.
(3) An attempt was made to set the tool's lower limit threshold to a value greater
than the tool's upper limit threshold.
Example: An attempt was made to write +2.00 for the lower limit threshold of
tool 1 with the upper limit threshold of tool 1 set to +1.00.
(4) An attempt was made to set the tool's upper limit threshold to a value smaller
than the tool's lower limit threshold.
Example: An attempt was made to write +1.00 for the upper limit threshold of
tool 1 with the lower limit threshold of tool 1 set to +2.00.

 Reading measurement values
This example illustrates how to read the measurement value, 12.34, set to "tool 2" on
the main unit.
(1) Write the number of the measurement value that you want to read in the
[measurement value reading execution request].
(2) Read the [measurement value reading execution result].
the [measurement value reading execution result].
[Measurement values reading

execution request]
Command
Index: 171
Response
(2)
[Measurement values reading

execution result]
Command
Index: 172
NO Response
[0: Execution in
progress] *1
(3)
Is the response
YES
(4)
[Measurement values (for

reading)]
Command
Index: 173
Response
Example: 1234
Stop

*1 Possible causes for the [measurement value reading execution result] being [2:
Abnormal termination] are shown below.
(Example: If measurement value reading execution is requested during reset
execution request processing)
• The tool of the specified measurement value number does not exist.
(Example: An attempt was made to read the lower limit threshold of tool 2
regardless of tool 2 not being set.)

 Reading the FTP file name (text input area)
This example illustrates how to read "ABCDE," which is currently set for the
"transmission condition 2 file name (text input area)" of the expansion unit.
(1) Write the number corresponding to the information that you want to read in the [FTP
file name reading execution request].
(2) Read the [FTP file name reading execution result].
[FTP file name 1] to [FTP file name 3] in order.

PLC side DL side
(1)
[FTP file name reading execution

request] Command
Index: 131
Response
(2)
[FTP file name reading execution

result]
Command
Index: 132
Response
NO
[0: Execution in
progress] *1
(3)
Is the response
YES
(4)-1
[FTP file name 1]

Index: 133
Response
Example: AB
(4)-2
[FTP file name 2]
Index: 134
Response
Example: CD
(4)-3
[FTP file name 3]
Index: 135
Response
Example: E (NULL)
Stop

*1 Possible causes for the [FTP file name reading execution result] being [2: abnormal
• During execution of the processing for the function execution request from the
DL, a different type of function execution is requested.
Example: If reset execution is requested during FTP file name reading execution
request processing
• An execution request targeted at the IX-1050 was performed with the IX-1050
(R1.00) connected to the IX-1000 (R2.00 and later versions).

 Changing the FTP file name (text input area)
This example illustrates how to change the "transmission condition 2 file name (text
input area)" on the expansion unit to "ABCDEF." Nothing is written to the nonvolatile
memory.
(1) Write the (ASCII) text to change to in [FTP file name 1] to [FTP file name 4].
(2) Use the [FTP file name writing execution request] to write the transmission condition
number and save condition that you want to change.
(3) Read the [FTP file name writing execution result].

PLC side DL side
(1)-1 Command
[FTP file 1] Example: AB
Example: AB
Index: 133
Response
(1)-2 [FTP file 2] Example: CD Command

ID (Slot number): 04 Example: CD
Index: 134
Response
(1)-3
[FTP file 3] Example: EF Command
Example: EF
Index: 135
Response
(1)-4
[FTP file 4] Example: [NULL][NULL] Command
ID (Slot number): 04 Example: [NULL][NULL]
Index: 136
Response
(2) [FTP file name writing execution

request] Command
Index: 129
Response
(3) [FTP file name writing execution

result]
Command
Index: 130
NO Response
[0: Execution in
progress] *1
(4) Is the response
YES
Stop

*1 Possible causes for the [FTP file name writing execution result] being [2: abnormal
• During execution of the processing for the function execution request from the
DL, a different type of function execution is requested.
Example: If reset execution is requested during FTP file name writing execution
request processing
• A value that is not valid has been entered for the text.
• An execution request targeted at the IX-1050 was performed with the IX-1050
(R1.00) connected to the IX-1000 (R2.00 and later versions).

Appendix
Specifications
The specifications of the DL-PN1 are as follows:
Product name PROFINET I/O Communication Unit
Model DL-PN1
Suitable network PROFINET I/O communication
Compliant standards IEEE 802.3u (100BASE-TX)
Ethernet Transmission rate 100 Mbps (100BASE-TX)
Transmission medium STP cable or Category 5e or higher UTP cable (100BASE-TX)
Maximum cable length 100 m
Data I/O communication
Compatible functions
Record data communication
No. of connectable
1
PROFINET I/O controllers
PROFINET Update Time 2 - 512 ms
GSDML version V2.3
Conformance class Conforms with Conformance Class A
Conformance test version Conforms with V2.2.4
Suitable protocols LLDP, DCP
Connectable sensors Sensor amplifiers with D-bus support
Sensor connection
Number of connectable
specifications 15 units max.*1
sensor units
Link/activity indicator (LINK/ACT): Green LED
System failure indicator (SF): 2-color (orange/red) LED
Indicator lamps
Bus failure indicator (BF): Red LED
Sensor communication indicator (D-bus): 2-color (green/red) LED
20 to 30 V DC, including ripple (p-p)10%
Power voltage
supplied from the connected sensor amplifiers
Power consumption 1500 mW or less (at 30 V 50 mA max.)
Operating ambient air
-20 to +55°C (no freezing)
temperature
Operating ambient air
Environmental 35 to 85% RH (no condensation)
humidity
resistance
10 to 55 Hz compound amplitude 1.5 mm, 2 hours each in X, Y, Z
Vibration resistance
directions
Pollution degree 2
Materials Main unit: Polycarbonate
Weight Approx. 70 g
*1 This varies depending on the connected sensor amplifiers. (Up to two IX-H/IX
sensor units can be connected.)
For details, see "Types and Number of Connectable Sensor Amplifiers" (page 3).

Dimensions
(Unit : mm)
25.6
29.4
(42.5)
38.1
43.5 35.4
94.5

Data Processing Time
The data update time for data I/O communication is shown below.
master DL Sensor amplifier
RST
LINK
/ACT
SF
BF
(1) (2) (3) (4)
DL-PN1
Maximum data processing time = (1) + (2) + (3) + (4)
(1) I/O controller data update time

(2) Network data update time
(3) DL-PN1 data communication time
The lengths of time taken for the output and measurement value data to be sent from
a sensor amplifier to the DL-PN1 are summarized below.
Number of communication data

Output/measurement value [ms]*1
allocations*2
1 -
2 -
3 18
4 20
5 24
6 26
7 30
8 32
9 36
10 38
11 42
12 44
13 48
14 50
15 54
*1 For the data processing time of the expansion unit, add 4 ms to the above values.
For information on (1), (2), and (4), refer to the manual of each device.
*2 The number of communication data allocations is determined according to
"Allocation rules for the number of communication data allocations" (page 56)."

 Allocation rules for the number of communication data allocations
This section explains how to select the number of communication data allocations.
For an explanation of the "Output Assignment" setting of the IX-H or the IX, see
"Communication Data Allocation Setting and Measurement Value Number" (page 4).
The number of communication data allocations is determined according to conditions

(a) or (b) shown below.
(a) [Apply to:] setting: "Main unit only" or "Main/Expansion"
The number of communication data allocations varies as shown below depending on
whether [Main unit only] or [Main/Expansion] is selected.
• When [Main unit only] is selected: The minimum number of communication data
allocations is three.
• When [Main/Expansion] is selected: The minimum number of communication data
allocations is six.
(b) [Output Assignment] settings
The number of communication data allocations (b) is the largest number among the
numbers for which communication data allocation was performed.
Example: When numbers 1 to 5 are selected under [Output Assignment], the
number of communication data allocations is five.
Example: When numbers 1, 5, 8, and 13 are selected under [Output Assignment],
the number of communication data allocations is 13, which is the largest
number among those selected.
Finally, the DL-PN1 data communication time is set to the "Output/measurement value"
number corresponding to the number of communication data allocations of (a) or (b),
whichever is larger.
Example 1: [Apply to:] set to [Main unit only] and 1 and 2 selected under [Output
Assignment]
Because [Main unit only] is selected, the number of communication data
allocations for (a) is three.
Because 1 and 2 are selected under [Output Assignment], the number of
communication data allocations for (b) is two.
Hence, the number of communication data allocations is three (a), the
larger value.

Example 2: [Apply to:] set to [Main unit only] and 1, 2, and 5 selected under [Output
Assignment]
Because 1, 2, and 5 are selected under [Output Assignment], the num-
ber of communication data allocations for (b) is five.
Hence, the number of communication data allocations is five (b), the
larger value.
Example 3: [Apply to:] set to [Main/Expansion] and 1 to 4 selected under [Output

Assignment]
Because [Main/Expansion] is selected, the number of communication
data allocations for (a) is six.
Because 1 to 4 are selected under [Output Assignment], the number of
communication data allocations for (b) is four.
Hence, the number of communication data allocations is six (a), the
larger value.

Example 4: [Apply to:] set to [Main unit only] and 1 to 15 selected under [Output
Assignment]
Because 1 to 15 are selected under [Output Assignment], the number of
communication data allocations for (b) is 15.
Hence, the number of communication data allocations is 15 (b), the
larger value.
(4) Sensor amplifier response time
For (1) and (2), see manuals for each model.

For (4), refer to the User's Manual of each sensor amplifier connected to the DL-PN1.

Troubleshooting
The indicator LEDs on the DL-PN1 can be used to determine the causes of errors.
Link/activity indicator (Green)
System Failure indicator (Orange, Red)
Bus Failure indicator (Red)
Sensor communication indicator (Green, Red)
 Link/activity indicator (LINK/ACT)

This indicator indicates whether the DL-PN1 is communicating correctly.
LED Status Condition Corrective Action
Solid The DL-PN1 is normally linked. -
Green The DL-PN1 is normally linked and is
Flashing -
now exchanging data.
• Check if the power supply is correctly connected.
• Check if the DL-PN1 is correctly connected to the
sensor amplifier.
Power is not supplied to the DL-PN1.
Not lit • Check if the IP address is correct.
The DL-PN1 is not linked.
• Check if the power supply of the connected device
or Ethernet switch is correctly connected.
• Check if the cable is correctly connected.
 System Failure indicator (SF)

This indicator indicates whether the DL-PN1 is operating normally.
• Check the D-bus LED status.
• Check if the number of connected sensor
amplifiers exceeds the maximum number of
connectable units.
There may be a system error on the • Check if the IP address is correct.
Solid red
DL-PN1 or a connected sensor. • Check if the slot number is correct.
sensor amplifier.
• Check if there is an electrical noise source near the
DL-PN1.
Flash LED was requested on the I/O
controller.
Flashing orange -
Flashes approximately 4 times per
second.
Not lit The DL-PN1 is normally operating. -

 Bus Failure indicator (BF)
This indicator indicates whether the DL-PN1 is communicating correctly with PROFINET.
• Check if the number of connected sensor
connectable units.
Data exchange via data I/O • Check if the IP address is correct.
Solid red communication is not being carried out • Check if the slot number is correct.
normally. • Check if the DL-PN1 is correctly connected to the
sensor amplifier.
• Check if there is an electrical noise source near the
DL-PN1.
Not lit The DL-PN1 is normally operating. -
 Sensor communication indicator (D-bus)

This indicator indicates whether the DL-PN1 is communicating correctly with the sensor
amplifier.
If an error occurs, you can identify the cause of the error by reading the error code via
cyclic communication or message communication.
"Error code list" (page 61)
The DL-PN1 is communicating correctly with
Solid green -
the sensor amplifier.
Flashing After it has started up, the DL-PN1 automatically shifts
After power-on, the DL-PN1 is now starting up.
green to the normal status.
The DL-PN1 could not communicate with the
sensor amplifier during its start-up.
sensor amplifier and turn on the power again.
(Error code: 00H/52 or 00H/55)
• Check if an unsupported sensor amplifier is
An attempt to assign an ID number has failed. connected to the DL-PN1 and turn on the power
(Error code: 00H/51) again.
Solid red The DL-PN1 could not communicate • Check if the number of connected sensor amplifiers
continuously with the sensor amplifier for one exceeds the maximum number of connectable units.
second or longer. • Check if there is an electrical noise source around
(Error code: 00H/57) the DL-PN1.
• If the error cannot be recovered after checking the
A system error may have occurred in the DL-
above, contact your nearest Keyence office.
PN1.
A current limitation error occurred.
(Error code: 00H/56)
Flashing red
An unsupported sensor amplifier was
(Repetition of
connected. Check the sensor amplifier configuration.
4 consecutive
(Error code: 00H/53)
flashes)
Unconnectable models are mixed. (Error code:
00H/54)
Flashing red
Sometimes the DL-PN1 cannot temporarily Check if there is an electrical noise source around the
(Flashing at
communicate with the sensor amplifier. DL-PN1. (The error is automatically reset if the cause is
fixed
(Error code: 00H/57) removed.)
intervals)
Not lit Power is not supplied to the DL-PN1. sensor amplifier.
• Check if the power supply is correctly connected.

Types of error and error code
 Error code list
The following error codes may occur in the DL-PN1.
 DL-PN1
Error
Description Cause Actions
code
0 No error - -
Check if the number of connected sensor
sensor amplifiers that can be connected to
the main unit.
The main unit assigned no
"Types and Number of Connectable
51 Unassigned error connection within 10 seconds
Sensor Amplifiers" (page 3)
after the DL-PN1 started.
Check the connection with the sensor
amplifiers and then turn the power on again.
If this error cannot be recovered, contact
your nearest KEYENCE office.
Start-time Communication between sensor amplifiers and then turn the power on again.
52
communication error amplifiers ended abnormally. If this error cannot be recovered, contact
Unsupported sensor Check the model of the connected sensor
A sensor amplifier not supported
53 amplifier connection amplifier and remove the sensor amplifier if it
by the DL-PN1 is connected.
error is not supported by the DL-PN1.
Sensor amplifiers outside the
54 Mixed model error specifications have a mixed Check if the models are mixable.
connection.
Start-time Communication failed during the amplifiers and then turn the power on again.
55
communication error initial communication. If this error cannot be recovered, contact
The number of connected
Current limitation Use sensor amplifiers within the allowable
56 sensor amplifiers exceeds the
error range.
allowable range.
Check if there is a noise source around the
Communication error An error occurred during
DL-PN1.
57 between sensor communication between sensor
If the sensor communication indicator is solid
amplifiers amplifiers.
red, turn the power on again.
100 System error The IP address is incorrect.
A default gateway setting error
101 System error
occurred.
An attempt to read data in
102 System error EEPROM such as the MAC
address has failed.
An attempt to start the protocol
103 System error
stack has failed. Contact your nearest KEYENCE office.
An attempt to access FlashROM
104 System error
has failed.
The number of held IDs is
150 System error
incorrect.
The number of sensors is
151 System error
incorrect.
152 System error An initial read error occurred.

Revision History
Print date Edition Description

April, 2020 Official release

WARRANTIES AND DISCLAIMERS
(1) KEYENCE warrants the Products to be free of defects in materials and workmanship for a period of one (1)
year from the date of shipment. If any models or samples were shown to Buyer, such models or samples
were used merely to illustrate the general type and quality of the Products and not to represent that the
Products would necessarily conform to said models or samples. Any Products found to be defective must
be shipped to KEYENCE with all shipping costs paid by Buyer or offered to KEYENCE for inspection and
examination. Upon examination by KEYENCE, KEYENCE, at its sole option, will refund the purchase price
of, or repair or replace at no charge any Products found to be defective. This warranty does not apply to any
defects resulting from any action of Buyer, including but not limited to improper installation, improper
interfacing, improper repair, unauthorized modification, misapplication and mishandling, such as exposure
to excessive current, heat, coldness, moisture, vibration or outdoors air. Components which wear are not
warranted.
(2) KEYENCE is pleased to offer suggestions on the use of its various Products. They are only suggestions,
and it is Buyer's responsibility to ascertain the fitness of the Products for Buyer’s intended use. KEYENCE
will not be responsible for any damages that may result from the use of the Products.
(3) The Products and any samples ("Products/Samples") supplied to Buyer are not to be used internally in
humans, for human transportation, as safety devices or fail-safe systems, unless their written specifications
state otherwise. Should any Products/Samples be used in such a manner or misused in any way,
KEYENCE assumes no responsibility, and additionally Buyer will indemnify KEYENCE and hold KEYENCE
harmless from any liability or damage whatsoever arising out of any misuse of the Products/Samples.
(4) OTHER THAN AS STATED HEREIN, THE PRODUCTS/SAMPLES ARE PROVIDED WITH NO OTHER
WARRANTIES WHATSOEVER. ALL EXPRESS, IMPLIED, AND STATUTORY WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, AND NON-INFRINGEMENT OF PROPRIETARY RIGHTS, ARE EXPRESSLY
DISCLAIMED. IN NO EVENT SHALL KEYENCE AND ITS AFFILIATED ENTITIES BE LIABLE TO ANY
PERSON OR ENTITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, SPECIAL OR
CONSEQUENTIAL DAMAGES (INCLUDING, WITHOUT LIMITATION, ANY DAMAGES RESULTING
FROM LOSS OF USE, BUSINESS INTERRUPTION, LOSS OF INFORMATION, LOSS OR
INACCURACY OF DATA, LOSS OF PROFITS, LOSS OF SAVINGS, THE COST OF PROCUREMENT OF
SUBSTITUTED GOODS, SERVICES OR TECHNOLOGIES, OR FOR ANY MATTER ARISING OUT OF
OR IN CONNECTION WITH THE USE OR INABILITY TO USE THE PRODUCTS, EVEN IF KEYENCE
OR ONE OF ITS AFFILIATED ENTITIES WAS ADVISED OF A POSSIBLE THIRD PARTY’S CLAIM FOR
DAMAGES OR ANY OTHER CLAIM AGAINST BUYER. In some jurisdictions, some of the foregoing
warranty disclaimers or damage limitations may not apply.
BUYER'S TRANSFER OBLIGATIONS:

If the Products/Samples purchased by Buyer are to be resold or delivered to a third party, Buyer must
provide such third party with a copy of this document, all specifications, manuals, catalogs, leaflets and
written information provided to Buyer pertaining to the Products/Samples.
E 1101-3
Specifications are subject to change without notice.
KEYENCE CORPORATION www.keyence.com/glb

1-3-14, Higashi-Nakajima, Higashi-Yodogawa-ku, Osaka, 533-8555, Japan PHONE: +81-6-6379-2211
AUSTRIA HONG KONG NETHERLANDS TAIWAN
Phone: +43 (0)2236 378266 0 Phone: +852-3104-1010 Phone: +31 (0)40 206 6100 Phone: +886-2-2721-8080
BELGIUM HUNGARY PHILIPPINES THAILAND
Phone: +32 (0)15 281 222 Phone: +36 1 802 7360 Phone: +63-(0)2-8981-5000 Phone: +66-2-369-2777
BRAZIL INDIA POLAND UK & IRELAND
Phone: +55-11-3045-4011 Phone: +91-44-4963-0900 Phone: +48 71 368 61 60 Phone: +44 (0)1908-696-900
CANADA INDONESIA ROMANIA USA
Phone: +1-905-366-7655 Phone: +62-21-2966-0120 Phone: +40 (0)269 232 808 Phone: +1-201-930-0100
CHINA ITALY SINGAPORE VIETNAM
Phone: +86-21-3357-1001 Phone: +39-02-6688220 Phone: +65-6392-1011 Phone: +84-24-3772-5555
CZECH REPUBLIC KOREA SLOVAKIA
Phone: +420 220 184 700 Phone: +82-31-789-4300 Phone: +421 (0)2 5939 6461
FRANCE MALAYSIA SLOVENIA
Phone: +33 1 56 37 78 00 Phone: +60-3-7883-2211 Phone: +386 (0)1 4701 666
GERMANY MEXICO SWITZERLAND
Phone: +49-6102-3689-0 Phone: +52-55-8850-0100 Phone: +41 (0)43 455 77 30
A5WW1-MAN-2090
*997GB-2*
Copyright (c) 2020 KEYENCE CORPORATION. All rights reserved.
195084GB 2071-2 997GB Printed in Japan

As 121899 DL-PN1 Um 997GB WW GB 2071 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

As 121899 DL-PN1 Um 997GB WW GB 2071 2

Uploaded by

Copyright:

Available Formats

997GB

PROFINET Communication Unit

It indicates a hazardous situation which, if not avoided, could result in

It indicates a hazardous situation which, if not avoided, could result in

It indicates a situation which, if not avoided, could result in product

Important It indicates cautions and limitations that must be followed during

Point It indicates additional information on proper operation.

Reference It indicates tips for better understanding or useful information.

(1) Check the presence of an I/O device

2 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Types and Number of Connectable Sensor Amplifiers

 Number of connectable sensor amplifiers

IX-1050 IX-1000 DL-PN1

IX-H2050 IX-H2000 DL-PN1

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 3

Important With an expansion unit connected, it is necessary to select [Main/

The IX [Output Assignment] setting screen is shown below.

The following tools can be allocated to numbers 1 to 15.

4 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 5

 Pin Height Tool Output (IX-H only)

6 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Data I/O Communication

Input Area Output Area

∙ Status result ∙ Status result

∙ Execute external input ∙ Execute external input

Point • Communication settings for the data I/O communication, such as

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 7

(a) When using the unit only as a main unit

8 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

(b) When using the unit as a main unit/expansion unit

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 9

When 7 or a higher number is selected with [Output Assignment] on the

10 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 11

12 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 13

Address Bit Function name Description Value

14 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Address Bit Function name Description Value

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 15

Address Bit Function name Description Value

 Data I/O communication device map (PROFINET I/O controller  DL-PN1)

16 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Address Bit Function name Description Value

Address Bit Function name Description Value

Address Bit Function name Description Value

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 17

Address Bit Function name Description Value

Address Bit Function name Description Value

18 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Sensor amplifier (1)

Applying an external input to a sensor amplifier (other than

Point • The corresponding input response signal is not contained in the

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 19

20 - PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) -

Available external input: Emission stop

Emission stop input request 1

Point When the [main-unit-synchronized input] function is enabled, the main

- PROFINET Communication Unit DL-PN1 User’s Manual (IX-H/IX) - 21

Measurement value 1 1234 4567 7890

Measurement value 2 2345 5678 8901

Measurement value 3 3456 6789 9012