Name: SIEMENS 6ES7317-2EK14-0AB0
Brand: SIEMENS
SKU: K0252213

Back

Delivery information
Export identifier	AL: N ECCN: EAR99H
Net weight	0.38
Quantity	1 Stück
Packaging quantity	1

Additional product information
Product status	EOP: 2025-10-01
EAN	4025515077794
UPC	040892550337
Static lot number	85371091
List indicator	ST73
Product group	4256
Country of origin	DE
Compliance with the substance restrictions according to RoHS directive	Since: 20091125

Product classifications	Version	Classification
eClass	4	27-24-03-02
eClass	5.1	27-24-22-07
eClass	6.0	27-24-22-07
ETIM	3	/
ETIM	4	EC000236
ETIM	5	EC000236

What is the 6ES7317-2EK14-0AB0 and where is it used

The 6ES7317-2EK14-0AB0 is the SIMATIC S7-300 CPU 317-2 PN/DP from Siemens. It is a central CPU for automation tasks in existing S7-300 systems, where logic processing, communication and the connection of distributed I/O are combined in a single module. The CPU combines an MPI/PROFIBUS DP interface with a PROFINET interface including a 2-port switch and requires a Micro Memory Card as its load memory. It is primarily used in modernised legacy systems, retrofit projects, production lines with distributed I/O structures and wherever an existing S7-300 architecture must remain in operation and rapid replacement in the event of a fault is important.

Overview of the key technical data and what it means

The CPU operates on 24 V DC, provides 1 MB of work memory and uses an MMC as a removable load memory, with support for up to 8 MB according to the product specifications. In practice, this means sufficient memory for typical to more demanding S7-300 applications, but also a clear dependency on a functioning memory card. On the communication side, the CPU provides 1x MPI/PROFIBUS DP up to 12 Mbit/s and 1x PROFINET with 2 RJ45 ports. Supported functions include PROFINET IO Controller, PROFINET IO Device, Open IE Communication, Web Server, up to 128 PROFINET IO devices and up to 124 DP devices. The module measures 40 × 125 × 130 mm and is therefore designed for standard S7-300 racks.

Product status, life-cycle status and obsolescence

For the 6ES7317-2EK14-0AB0, Siemens specifies the status PM410: Product Cancellation, with 01.10.2025 listed as the milestone date. For operators of existing systems, this is a clear indication that spare-part availability, repair strategies and stockholding should be actively planned. An officially confirmed 1:1 successor with the same MLFB could not be verified in the official product data. For modernisation and technology upgrades, Siemens instead refers to migration paths from S7-300/S7-400 to S7-1500 within the TIA Portal environment. A positive aspect for continued operation is that Siemens still documents firmware information; for this CPU, firmware updates up to V3.2.19 are listed. For maintenance and purchasing departments, it is therefore important to manage obsolescence not only technically but also from a procurement perspective.

The available EICHLER services and when they are relevant

For this CPU, EICHLER offers repair, exchange, used and new units. Repair is particularly useful when an existing system must be returned to operation quickly using identical hardware, while keeping the program version, peripheral integration and validation status unchanged. EICHLER states that repairs include technical cleaning, preventive maintenance, comprehensive functional testing and a minimum 24-month warranty. Exchange services are attractive in the event of an unexpected breakdown when time is more critical than retaining the original module. Used units are a practical option where obsolescence and budget constraints are a concern. New units are suitable for planned stockholding and standardised spare-parts strategies. An optional test report is also available.

Attribute	Value
General information
Product type designation	CPU 317-2 PN/DP
HW functional status	1
Firmware version	V3.2
Product function
● Isochronous mode	Yes; Via PROFIBUS DP or PROFINET interface
Engineering with
● Programming package	STEP 7 V5.5 or higher
Supply voltage
Rated value (DC)	24 V
permissible range, lower limit (DC)	20.4 V
permissible range, upper limit (DC)	28.8 V
external protection for power supply lines (recommendation)	2 A min.
Mains buffering
● Mains/voltage failure stored energy time	5 ms
● Repeat rate, min.	1 s
Input current
Current consumption (rated value)	750 mA
Current consumption (in no-load operation), typ.	150 mA
Inrush current, typ.	4 A
I²t	1 A²·s
Power loss
Power loss, typ.	4.65 W
Memory
Work memory
● integrated	1 024 kbyte
● expandable	No
Load memory
● Plug-in (MMC)	Yes
● Plug-in (MMC), max.	8 Mbyte
● Data management on MMC (after last programming), min.	10 a
Backup
● present	Yes; Guaranteed by MMC (maintenance-free)
● without battery	Yes; Program and data
CPU processing times
for bit operations, typ.	0.025 µs
for word operations, typ.	0.03 µs
for fixed point arithmetic, typ.	0.04 µs
for floating point arithmetic, typ.	0.16 µs
CPU-blocks
Number of blocks (total)	2 048; (DBs, FCs, FBs); the maximum number of loadable blocks can be reduced by the MMC used.
DB
● Number, max.	2 048; Number range: 1 to 16000
● Size, max.	64 kbyte
FB
● Number, max.	2 048; Number range: 0 to 7999
● Size, max.	64 kbyte
FC
● Number, max.	2 048; Number range: 0 to 7999
● Size, max.	64 kbyte
OB
● Size, max.	64 kbyte
● Number of free cycle OBs	1; OB 1
● Number of time alarm OBs	1; OB 10
● Number of delay alarm OBs	2; OB 20, 21
● Number of cyclic interrupt OBs	4; OB 32, 33, 34, 35
● Number of process alarm OBs	1; OB 40
● Number of DPV1 alarm OBs	3; OB 55, 56, 57
● Number of isochronous mode OBs	1; OB 61 - isochronous mode is possible either on DP or PROFINET IO (not simultaneously)
● Number of startup OBs	1; OB 100
● Number of asynchronous error OBs	6; OB 80, 82, 83, 85, 86, 87 (OB83 only for PROFINET IO)
● Number of synchronous error OBs	2; OB 121, 122
Nesting depth
● per priority class	16
● additional within an error OB	4
Counters, timers and their retentivity
S7 counter
● Number	512
Retentivity
— adjustable	Yes
— preset	Z 0 to Z 7
Counting range
— adjustable	Yes
— lower limit	0
— upper limit	999
IEC counter
● present	Yes
● Type	SFB
● Number	Unlimited (limited only by RAM capacity)
S7 times
● Number	512
Retentivity
— adjustable	Yes
— preset	No retentivity
Time range
— lower limit	10 ms
— upper limit	9 990 s
IEC timer
● present	Yes
● Type	SFB
● Number	Unlimited (limited only by RAM capacity)
Data areas and their retentivity
Retentive data area (incl. timers, counters, flags), max.	256 kbyte
Flag
● Size, max.	4 096 byte
● Retentivity available	Yes; From MB 0 to MB 4 095
● Retentivity preset	MB 0 to MB 15
● Number of clock memories	8; 1 memory byte
Data blocks
● Retentivity adjustable	Yes; via non-retain property on DB
● Retentivity preset	Yes
Local data
● per priority class, max.	32 768 byte; Max. 2048 bytes per block
Address area
I/O address area
● Inputs	8 192 byte
● Outputs	8 192 byte
of which distributed
— Inputs	8 192 byte
— Outputs	8 192 byte
Process image
● Inputs	8 192 byte
● Outputs	8 192 byte
● Inputs, adjustable	8 192 byte
● Outputs, adjustable	8 192 byte
● Inputs, default	256 byte
● Outputs, default	256 byte
Subprocess images
● Number of subprocess images, max.	1; With PROFINET IO, the length of the user data is limited to 1600 bytes
Digital channels
● Inputs	65 536
— of which central	1 024
● Outputs	65 536
— of which central	1 024
Analog channels
● Inputs	4 096
— of which central	256
● Outputs	4 096
— of which central	256
Hardware configuration
Number of expansion units, max.	3
Number of DP masters
● integrated	1
● via CP	4
Number of operable FMs and CPs (recommended)
● FM	8
● CP, PtP	8
● CP, LAN	10
Rack
● Racks, max.	4
● Modules per rack, max.	8
Time of day
Clock
● Hardware clock (real-time)	Yes
● retentive and synchronizable	Yes
● Backup time	6 wk; At 40 °C ambient temperature
● Deviation per day, max.	10 s; Typ.: 2 s
● Behavior of the clock following POWER-ON	Clock continues running after POWER OFF
● Behavior of the clock following expiry of backup period	the clock continues at the time of day it had when power was switched off
Operating hours counter
● Number	4
● Number/Number range	0 to 3
● Range of values	0 to 2^31 hours (when using SFC 101)
● Granularity	1 h
● retentive	Yes; Must be restarted at each restart
Clock synchronization
● supported	Yes
● to MPI, master	Yes
● on MPI, device	Yes
● to DP, master	Yes; With DP slave only slave clock
● on DP, device	Yes
● in AS, master	Yes
● in AS, device	Yes
● on Ethernet via NTP	Yes; As client
Digital inputs
Number of digital inputs	0
Digital outputs
Number of digital outputs	0
Analog inputs
Number of analog inputs	0
Interfaces
Number of PROFINET interfaces	1; 2 ports (switch) RJ45
Number of RS 485 interfaces	1; Combined MPI / PROFIBUS DP
Number of RS 422 interfaces	0
1. Interface
Interface type	Integrated RS 485 interface
Isolated	Yes
Interface types
● RS 485	Yes
● Output current of the interface, max.	200 mA
Protocols
● MPI	Yes
● PROFIBUS DP master	Yes
● PROFIBUS DP device	Yes
● Point-to-point connection	No
MPI
● Transmission rate, max.	12 Mbit/s
Services
— PG/OP communication	Yes
— Routing	Yes
— Global data communication	Yes
— S7 basic communication	Yes
— S7 communication	Yes
— S7 communication, as client	No; but via CP and loadable FB
— S7 communication, as server	Yes
PROFIBUS DP master
● Transmission rate, max.	12 Mbit/s
● max. number of DP devices	124
Services
— PG/OP communication	Yes
— Routing	Yes
— Global data communication	No
— S7 basic communication	Yes; I blocks only
— S7 communication	Yes
— S7 communication, as client	No
— S7 communication, as server	Yes
— Equidistance	Yes
— Isochronous mode	Yes; OB 61; isochronous mode can only be used alternatively on PROFIBUS DP or PROFINET IO
— SYNC/FREEZE	Yes
— activation/deactivation of DP devices	Yes
— max. number of DP devices that can be activated/deactivated at the same time	8
— Direct data exchange (slave-to-slave communication)	Yes; as subscriber
— DPV1	Yes
Address area
— Inputs, max.	8 kbyte
— Outputs, max.	8 kbyte
User data per DP device
— Inputs, max.	244 byte
— Outputs, max.	244 byte
PROFIBUS DP device
● Transmission rate, max.	12 Mbit/s
● automatic baud rate search	Yes; only with passive interface
● Address area, max.	32
● User data per address area, max.	32 byte
Services
— PG/OP communication	Yes
— Routing	Yes; Only with active interface
— Global data communication	No
— S7 basic communication	No
— S7 communication	Yes
— S7 communication, as client	No
— S7 communication, as server	Yes; Connection configured on one side only
— Direct data exchange (slave-to-slave communication)	Yes
— DPV1	No
Transfer memory
— Inputs	244 byte
— Outputs	244 byte
2. Interface
Interface type	PROFINET
Isolated	Yes
automatic detection of transmission rate	Yes; 10/100 Mbit/s
Autonegotiation	Yes
Autocrossing	Yes
Change of IP address at runtime, supported	Yes
Interface types
● RJ 45 (Ethernet)	Yes
● Number of ports	2
● integrated switch	Yes
Protocols
● MPI	No
● PROFINET IO Controller	Yes; Also simultaneously with IO-Device functionality
● PROFINET IO Device	Yes; Also simultaneously with IO Controller functionality
● PROFINET CBA	Yes
● PROFIBUS DP master	No
● PROFIBUS DP device	No
● Open IE communication	Yes; Via TCP/IP, ISO on TCP, and UDP
● Web server	Yes
● Media redundancy	Yes
PROFINET IO Controller
● Transmission rate, max.	100 Mbit/s
Services
— PG/OP communication	Yes
— Routing	Yes
— S7 communication	Yes; with loadable FBs, max. configurable connections: 16, max. number of instances: 32
— Isochronous mode	Yes; OB 61; isochronous mode can only be used alternatively on PROFIBUS DP or PROFINET IO
— IRT	Yes
— Shared device	Yes
— Prioritized startup	Yes
— Number of IO devices with prioritized startup, max.	32
— Number of connectable IO Devices, max.	128
— Of which IO devices with IRT, max.	64
— of which in line, max.	64
— Number of IO Devices with IRT and the option "high flexibility"	128
— of which in line, max.	61
— Number of connectable IO Devices for RT, max.	128
— of which in line, max.	128
— Activation/deactivation of IO Devices	Yes
— Number of IO Devices that can be simultaneously activated/deactivated, max.	8
— IO Devices changing during operation (partner ports), supported	Yes
— Number of IO Devices per tool, max.	8
— Device replacement without swap medium	Yes
— Send cycles	250 μs, 500 μs,1 ms; 2 ms, 4 ms (not in the case of IRT with "high flexibility" option)
— Updating time	250 µs to 512 ms (depending on the operating mode, see Manual "S7-300 CPU 31xC and CPU 31x, technical Data" for more details)
Address area
— Inputs, max.	8 kbyte
— Outputs, max.	8 kbyte
— User data consistency, max.	1 024 byte
PROFINET IO Device
Services
— PG/OP communication	Yes
— Routing	Yes
— S7 communication	Yes; with loadable FBs, max. configurable connections: 16, max. number of instances: 32
— Isochronous mode	No
— IRT	Yes
— PROFIenergy	Yes; With SFB 73 / 74 prepared for loadable PROFIenergy standard FB for I-Device
— Shared device	Yes
— Number of IO Controllers with shared device, max.	2
Transfer memory
— Inputs, max.	1 440 byte; Per IO Controller with shared device
— Outputs, max.	1 440 byte; Per IO Controller with shared device
Submodules
— Number, max.	64
— User data per submodule, max.	1 024 byte
PROFINET CBA
● acyclic transmission	Yes
● cyclic transmission	Yes
Open IE communication
● Number of connections, max.	16
● Local port numbers used at the system end	0, 20, 21, 23, 25, 80, 102, 135, 161, 443, 8080, 34962, 34963, 34964, 65532, 65533, 65534, 65535
● Keep-alive function, supported	Yes
Protocols
PROFIsafe	No
Redundancy mode
Media redundancy
— Switchover time on line break, typ.	200 ms; PROFINET MRP
— Number of stations in the ring, max.	50
Open IE communication
● TCP/IP	Yes; via integrated PROFINET interface and loadable FBs
— Number of connections, max.	16
— Data length for connection type 01H, max.	1 460 byte
— Data length for connection type 11H, max.	32 768 byte
— several passive connections per port, supported	Yes
● ISO-on-TCP (RFC1006)	Yes; via integrated PROFINET interface and loadable FBs
— Number of connections, max.	16
— Data length, max.	32 768 byte
● UDP	Yes; via integrated PROFINET interface and loadable FBs
— Number of connections, max.	16
— Data length, max.	1 472 byte
Web server
● supported	Yes
● User-defined websites	Yes
● Number of HTTP clients	5
Communication functions
PG/OP communication	Yes
Data record routing	Yes
Global data communication
● supported	Yes
● Number of GD loops, max.	8
● Number of GD packets, max.	8
● Number of GD packets, transmitter, max.	8
● Number of GD packets, receiver, max.	8
● Size of GD packets, max.	22 byte
● Size of GD packet (of which consistent), max.	22 byte
S7 basic communication
● supported	Yes
● User data per job, max.	76 byte
● User data per job (of which consistent), max.	76 byte; 76 bytes (with X_SEND or X_RCV); 64 bytes (with X_PUT or X_GET as server)
S7 communication
● supported	Yes
● as server	Yes
● as client	Yes; via integrated PROFINET interface and loadable FB or via CP and loadable FB
● User data per job, max.	See online help of STEP 7 (shared parameters of the SFBs/FBs and of the SFCs/FCs of S7 Communication)
S5 compatible communication
● supported	Yes; via CP and loadable FC
PROFINET CBA (at set setpoint communication load)
● Setpoint for the CPU communication load	50 %
● Number of remote interconnection partners	32
● number of master/device functions	30
● total of all master/device connections	1 000
● data length of all incoming master/device connections, max.	4 000 byte
● data length of all outgoing master/device connections, max.	4 000 byte
● Number of device-internal and PROFIBUS interconnections	500
● Data length of device-internal und PROFIBUS interconnections, max.	4 000 byte
● Data length per connection, max.	1 400 byte
Remote interconnections with cyclic transmission
— Transmission frequency: Transmission interval, min.	10 ms
— Number of incoming interconnections	200
— Number of outgoing interconnections	200
— Data length of all incoming interconnections, max.	2 000 byte
— Data length of all outgoing interconnections, max.	2 000 byte
— Data length per connection, max.	450 byte
HMI variables via PROFINET (acyclic)
— Number of stations that can log on for HMI variables (PN OPC/iMap)	3; 2x PN OPC/1x iMap
— HMI variable updating	500 ms
— Number of HMI variables	200
— Data length of all HMI variables, max.	2 000 byte
PROFIBUS proxy functionality
— supported	Yes
— Number of linked PROFIBUS devices	16
— Data length per connection, max.	240 byte; Slave-dependent
Number of connections
● overall	32
● usable for PG communication	31
— reserved for PG communication	1
— adjustable for PG communication, min.	1
— adjustable for PG communication, max.	31
● usable for OP communication	31
— reserved for OP communication	1
— adjustable for OP communication, min.	1
— adjustable for OP communication, max.	31
● usable for S7 basic communication	30
— reserved for S7 basic communication	0
— adjustable for S7 basic communication, min.	0
— adjustable for S7 basic communication, max.	30
● usable for S7 communication	16
— reserved for S7 communication	0
— adjustable for S7 communication, min.	0
— adjustable for S7 communication, max.	16
● total number of instances, max.	32
● usable for routing	X1 as MPI: max. 10; X1 as DP master: max. 24; X1 as DP slave (active): max. 14; X2 as PROFINET: 24 max.
S7 message functions
Number of login stations for message functions, max.	32; Depending on the configured connections for PG/OP and S7 basic communication
Process diagnostic messages	Yes
simultaneously active Alarm_S blocks, max.	300
Test commissioning functions
Status block	Yes; Up to 2 simultaneously
Single step	Yes
Number of breakpoints	4
Status/control
● Status/control variable	Yes
● Variables	Inputs, outputs, memory bits, DB, times, counters
● Number of variables, max.	30
— of which status variables, max.	30
— of which control variables, max.	14
Forcing
● Forcing	Yes
● Forcing, variables	Inputs, outputs
● Number of variables, max.	10
Diagnostic buffer
● present	Yes
● Number of entries, max.	500
— adjustable	No
— of which powerfail-proof	100; Only the last 100 entries are retained
● Number of entries readable in RUN, max.	499
— adjustable	Yes; From 10 to 499
— preset	10
Service data
● can be read out	Yes
Ambient conditions
Ambient temperature during operation
● min.	0 °C
● max.	60 °C
Configuration
Configuration software
● STEP 7	Yes; V5.5 or higher
Programming
● Command set	see instruction list
● Nesting levels	8
● System functions (SFC)	see instruction list
● System function blocks (SFB)	see instruction list
Programming language
— LAD	Yes
— FBD	Yes
— STL	Yes
— SCL	Yes
— CFC	Yes
— GRAPH	Yes
— HiGraph®	Yes
Know-how protection
● User program protection/password protection	Yes
● Block encryption	Yes; With S7 block Privacy
Dimensions
Width	40 mm
Height	125 mm
Depth	130 mm
Weights
Weight, approx.	340 g

Fault description	Possible solution
Why does the CPU 317-2 PN/DP immediately switch to STOP after a programming error?	If OB121 is not loaded, the CPU responds to typical programming errors such as invalid block accesses, timer accesses, counter accesses or memory area accesses by switching to STOP. Load OB121, read the diagnostic buffer and then correct the affected block or the incorrect addressing in STEP 7. Siemens documentation explicitly recommends using the STEP 7 test and diagnostic functions for troubleshooting.
Why does the 6ES7317-2EK14-0AB0 switch to STOP when a peripheral fault occurs or an IO device fails?	In the event of peripheral access faults, the CPU calls OB122. If OB122 is not loaded, the CPU switches to STOP. Check the addressing in the hardware configuration and verify whether a module, DP slave or PROFINET IO device has failed. Depending on the fault type, OB82, OB83 or OB86 may also be relevant for handling diagnostic and module-related events.
Why are the BF or SF LEDs illuminated on the CPU 317-2 PN/DP and the PROFINET devices do not start?	Within a PROFINET network, every IO device must have the configured device name assigned to it. In addition, the IP address, subnet and parameterisation must match the hardware configuration. Assign the correct device name to the affected participant, verify the network settings and reload the hardware configuration while the CPU is in STOP. Only then can the controller correctly transfer the parameters to the IO devices.
Why does the CPU request a memory reset after replacing the memory card or when the memory card is defective?	The CPU 317-2 PN/DP requires a Micro Memory Card (MMC) as its load memory. If the MMC is faulty or contains incompatible data, the CPU switches to STOP and requests a memory reset (MRES). Replace or format the card, perform a memory reset if required and then reload the user program and hardware configuration. If the contents of the card are unknown, the card should be erased or formatted before being reused.
Why can't my PG/PC find the CPU online even though the module is powered?	The most common causes are incorrect CPU address settings, an incorrectly selected PG/PC interface or inconsistent Ethernet/MPI parameters. Check the address configured in the hardware configuration, verify the selected PG/PC interface and, for PROFINET connections, also verify the IP address, subnet and device name. Afterwards, establish the online connection again and review the diagnostic buffer for additional information.

Is the 6ES7317-2EK14-0AB0 discontinued?

Yes. Siemens classifies the 6ES7317-2EK14-0AB0 with the lifecycle status PM410: Product Cancellation and specifies 01 October 2025 as the product cancellation date. For operators of existing S7-300 systems, this does not automatically mean the immediate end of operation, but the risk regarding procurement and standardisation increases significantly. A robust spare-parts strategy, documented project backups, secured MMCs and a clear plan for repair, exchange or migration are therefore highly advisable.

Which memory card is required for the 6ES7317-2EK14-0AB0?

The CPU requires a SIMATIC Micro Memory Card (MMC). The load memory is implemented as a removable MMC, and the technical specifications state a maximum supported card size of 8 MB. For reliable operation, it is important that the card not only fits mechanically but also contains valid and compatible data. Memory cards with unknown contents should be erased or formatted before use so that the application program and hardware configuration can be loaded cleanly.

Can I continue using an existing S7-300 project with this CPU in TIA Portal?

Yes. In principle, S7-300 and S7-400 projects can be migrated into a TIA Portal project. Siemens states that the migrated project can continue to be used with the existing S7-300/400 hardware. However, the current engineering environment must be considered: starting with TIA Portal V20, direct migration of *.s7p projects is no longer integrated. Siemens instead provides a dedicated migration tool that generates an *.am20 file. This is particularly relevant for existing installations where the engineering environment is being modernised without immediately replacing the hardware.

Are firmware updates still available for the CPU 317-2 PN/DP?

Yes. Siemens continues to document firmware updates for the 6ES7317-2EK14-0AB0. The latest version referenced in Siemens support information is Firmware V3.2.19. Siemens also notes that online firmware updates are possible from STEP 7 V5 onwards. For operators of older systems, this can be important when investigating diagnostic behaviour, stability improvements or known firmware-related issues before deciding to replace a module.

What communication interfaces does the CPU 317-2 PN/DP provide?

The CPU combines an RS485 interface for MPI/PROFIBUS DP with a PROFINET interface featuring two RJ45 ports and an integrated switch. This provides several practical advantages, including integration of existing PROFIBUS networks, simultaneous connection of modern PROFINET devices, PG/OP communication, routing, S7 communication, Open IE communication and an integrated web server. For larger existing systems, it is also important that the CPU supports up to 124 DP devices and up to 128 PROFINET IO devices.

Is there a direct successor to the 6ES7317-2EK14-0AB0?

An officially confirmed 1:1 direct successor for this exact MLFB could not be verified in the available Siemens product information. Instead, Siemens provides extensive guidance for migration from S7-300/S7-400 to S7-1500 platforms. For operators, this means that maintaining the existing architecture typically involves repair, exchange services or qualified replacement procurement. Those planning technological upgrades should view the CPU as part of a broader migration strategy rather than as an isolated replacement project.