Phoenix Contact AXC F 1050 User Manual

Download

Page 1

Installing, starting up, and operating the AXC F 1050 controller

User manual

Page 2

User manual

Installing, starting up, and operating the AXC F 1050 controller

UM EN AXC F 1050

This user manual is valid for:

Designation As of HW ver-

As of FW version Order No.

sion

AXC F 1050 05 4.00 2404701

2018-10-30

107709_en_00

PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany

phoenixcontact.com

Page 3

Table of contents

1 For your safety ...........................................................................................................................7

1.1 Identification of warning notes ...............................................................................7

1.2 Qualification of users .............................................................................................7

1.3 Field of application of the product..........................................................................8

1.3.1 Intended use ..........................................................................................8

1.3.2 Modifications ..........................................................................................8

1.4 Safety notes...........................................................................................................8

1.5 Notes on using the AXC F 1050 controller in potentially explosive areas.............11

2 Transport and unpacking .........................................................................................................13

2.1 Transport .............................................................................................................13

2.2 Storage................................................................................................................13

2.3 Checking the delivery ..........................................................................................13

2.4 Unpacking ...........................................................................................................14

3 Description of the AXC F 1050 .................................................................................................15

3.1 Hardware and software requirements.................................................................. 15

3.2 General description of the controller ....................................................................15

3.3 Possible fields of application of the controller ......................................................18

3.3.1 Controller as a decentral controller for an Axioline F station .................18

3.3.2 The AXC F 1050 as a PROFINET controller in a PROFINET

network ................................................................................................19

3.3.3 The AXC F 1050 as a PROFINET device in a PROFINET net-

work .....................................................................................................20

3.3.4 System redundancy with the AXC F 1050 ............................................21

3.4 Connection and operating elements ....................................................................23

3.5 Diagnostics and status indicators ........................................................................24

3.6 Mode selector switch...........................................................................................28

3.7 Reset button (concealed) ....................................................................................29

3.8 Parameterization memory.................................................................................... 30

3.9 Internal basic circuit diagram ...............................................................................31

3.10 Interfaces............................................................................................................. 32

3.10.1 Ethernet ............................................................................................... 33

3.10.2 Service interface (Micro-USB type B) ................................................... 33

3.11 Supply plug.......................................................................................................... 34

3.12 Bus base module.................................................................................................34

107709_en_00 PHOENIX CONTACT 3 / 140

Page 4

AXC F 1050

4 Mounting hardware ..................................................................................................................35

4.1 Safety notes.........................................................................................................35

4.2 Basics..................................................................................................................37

4.3 Structure of an Axioline F station .........................................................................39

4.4 Mounting the controller ........................................................................................40

4.5 Inserting the SD card ...........................................................................................41

5 Connecting and wiring hardware ..............................................................................................42

5.1 Safety notes.........................................................................................................42

5.2 Supply voltage.....................................................................................................44

5.2.1 Sizing of the power supply ...................................................................44

5.2.2 Connecting the power supply ............................................................... 45

5.3 Connecting Ethernet............................................................................................47

6 Starting up with PC Worx Engineer ..........................................................................................48

6.1 Installing PC Worx Engineer ................................................................................48

6.2 PC Worx Engineer licenses .................................................................................48

6.3 User interface ......................................................................................................49

6.4 Creating a new project.........................................................................................51

6.5 Configuring the IP settings...................................................................................52

6.5.1 Setting the IP address range ................................................................52

6.5.2 Setting the IP address ..........................................................................53

6.6 Using the simulation function...............................................................................54

6.7 Connecting to the controller.................................................................................55

6.8 Configuring Axioline F modules ...........................................................................58

6.9 Configuring PROFINET devices ..........................................................................60

6.9.1 Adding PROFINET devices ..................................................................60

6.9.2 Assigning online devices ......................................................................61

6.9.3 Adding I/O modules .............................................................................63

6.10 Programming in accordance with IEC 61131-3....................................................65

6.10.1 Opening and creating the POU, creating variables .............................. 65

6.10.2 Creating a program ..............................................................................67

6.10.3 Creating functions and function blocks ................................................. 68

6.11 Instantiating programs .........................................................................................72

6.12 Assigning process data .......................................................................................73

6.13 Transfer the project to the controller ....................................................................77

6.14 Creating an HMI application ................................................................................77

4 / 140

PHOENIX CONTACT 107709_en_00

Page 5

Table of contents

7 Additional functions in PC Worx Engineer ................................................................................78

7.1 Entering or reading the controller functions and installation location....................79

7.2 Selecting or reading protocols for manual IP assignment ....................................80

7.3 Setting or reading the real-time clock...................................................................81

7.4 Switching the PROFINET controller / PROFINET device function on or

off ........................................................................................................................82

7.5 Using the SD card as the main memory or additional memory.............................83

7.5.1 Main memory .......................................................................................83

7.5.2 Additional memory ...............................................................................85

7.6 Activating or deactivating the MRP client function ...............................................88

7.7 Activating or deactivating the SNMP server function ...........................................89

7.8 Activating or deactivating the FTP server function ...............................................90

7.9 Activating or deactivating the SNTP client function..............................................92

8 System variables and status information ..................................................................................94

8.1 General information .............................................................................................94

8.2 Diagnostic status register ....................................................................................94

8.3 Diagnostic parameter register..............................................................................95

8.4 PROFINET system variables ...............................................................................96

8.5 IEC-61131 runtime system ..................................................................................99

8.6 Control processor ..............................................................................................101

8.7 Ethernet interfaces.............................................................................................101

8.8 SD card..............................................................................................................102

8.9 Energy storage, real-time clock .........................................................................102

8.10 Power supplies ..................................................................................................102

8.11 Mode selector switch.........................................................................................102

8.12 Project-related system variables........................................................................103

9 Web-based management (WBM) ..........................................................................................104

9.1 Establishing a connection to the WBM ..............................................................104

9.2 Changing the language......................................................................................104

9.3 Areas and functions...........................................................................................104

9.3.1 “Information” area ...............................................................................105

9.3.2 “Diagnostics” area ..............................................................................108

9.3.3 “Administration” area ..........................................................................114

107709_en_00 PHOENIX CONTACT 5 / 140

Page 6

AXC F 1050

10 Removing hardware ...............................................................................................................120

10.1 Safety notes.......................................................................................................120

10.2 Removing cables...............................................................................................121

10.3 Removing the plug............................................................................................. 121

10.4 Removing the SD card.......................................................................................122

10.5 Removing the controller.....................................................................................122

11 After use ................................................................................................................................123

11.1 Maintenance and servicing................................................................................123

11.2 Device replacement........................................................................................... 123

11.3 Device failure and repair....................................................................................124

11.4 Disposal.............................................................................................................124

11.5 Return for disposal.............................................................................................124

12 Technical data and ordering data ...........................................................................................125

12.1 Technical data ...................................................................................................125

12.2 Ordering data.....................................................................................................129

A Technical appendix.................................................................................................................130

A 1 Performing updates ...........................................................................................130

B Appendix for document lists....................................................................................................132

B 1 List of figures .....................................................................................................132

B 2 List of tables ......................................................................................................136

B 3 Index..................................................................................................................137

6 / 140

PHOENIX CONTACT 107709_en_00

Page 7

1 For your safety

Read this user manual carefully and keep it for future reference.

1.1 Identification of warning notes

For your safety

This symbol indicates hazards that could lead to personal injury.

There are three signal words indicating the severity of a potential injury.

DANGER

Indicates a hazard with a high risk level. If this hazardous situation is not avoided, it will result in death or serious injury.

WARNING

Indicates a hazard with a medium risk level. If this hazardous situation is not avoided, it could result in death or serious injury.

CAUTION

Indicates a hazard with a low risk level. If this hazardous situation is not avoided, it could result in minor or moderate injury.

This symbol together with the NOTE signal word warns the reader of actions that might cause property damage or a malfunction.

Here you will find additional information or detailed sources of information.

1.2 Qualification of users

The use of products described in this user manual is oriented exclusively to: – Electrically skilled persons or persons instructed by them. The users must be familiar

with the relevant safety concepts of automation technology as well as applicable standards and other regulations.

– Qualified application programmers and software engineers. The users must be familiar

with the relevant safety concepts of automation technology as well as applicable standards and other regulations.

107709_en_00 PHOENIX CONTACT 7 / 140

Page 8

AXC F 1050

1.3 Field of application of the product

1.3.1 Intended use

The AXC F 1050 controller is a modular small-scale controller that can be used for smaller and medium-sized applications. The device has an IP20 protection class and is designed for use in closed control cabinets or control boxes (junction boxes) with IP54 degree of protection or higher.

The device is designed for use in industrial environments.

1.3.2 Modifications

Modifications to hardware and firmware of the device are not permitted.

Incorrect operation or modifications to the device can endanger your safety or damage the device. Do not repair the device yourself. If the device is defective, please contact Phoenix Contact.

1.4 Safety notes

Observe the country-specific installation, safety, and accident prevention regulations.

During startup and maintenance work, proceed in accordance with the five safety rules of DIN EN 50110-1. In general, the rules should be observed in the order indicated below:

– Disconnect safely – Ensure power cannot be switched on again – Verify safe isolation from the supply – Ground and short circuit – Cover or safeguard adjacent live parts

Once the work is complete, perform the above steps again in reverse order.

8 / 140

PHOENIX CONTACT 107709_en_00

Page 9

For your safety

NOTE: Risk of unauthorized network access

Connecting devices to a network via Ethernet always entails the risk of unauthorized access to the network.

Therefore, please check your application for the option of deactivating active communication channels (for instance SNMP, FTP, BootP, DCP, etc.), or setting passwords to prevent third parties from accessing the controller without authorization and modifying the system.

Because of the controller's communication interfaces, we advise against using the controller in safety-critical applications without additional security appliances. Please take additional protective measures in accordance with the IT security requirements and the standards applicable to your application (e.g. virtual networks (VPN) for remote maintenance access, firewalls, etc.) for protection against unauthorized network access.

On first request, you agree to release Phoenix Contact and the companies associated with Phoenix Contact GmbH & Co. KG, Flachsmarktstraße 8, 32825 Blomberg in accordance with §§ 15 ff. AktG or the German Stock Corporation Act (hereinafter collectively referred to as “Phoenix Contact”) from all third-party claims that are made due to improper use.

For the protection of networks for remote maintenance via VPN, Phoenix Contact offers the mGuard product range as security appliances, which you can find described in the latest Phoenix Contact catalog (

phoenixcontact.net/products).

Additional measures for protection against unauthorized network access are listed in the AH EN INDUSTRIAL SECURITY application note. The application note is available for downloading at phoenixcontact.net/products.

NOTE: Electrostatic discharge!

The device contains components that can be damaged or destroyed by electrostatic discharge. When handling the device, observe the necessary safety precautions against electrostatic discharge (ESD) in accordance with EN 61340-5-1 and IEC 61340-5-1.

NOTE: Device failure

The device is designed to be powered by an external 24 V DC voltage supply. The permissible voltage range is from 19.2 V DC to 30 V DC (ripple included). If the voltage exceeds or falls below the permitted voltage range, this may lead to device failure.

• Ensure that the voltage is kept within the permitted range.

NOTE: Electrical damage due to inadequate external protection – No safe fuse tripping in the event of an error

The electronics in the device will be damaged due to inadequate external protection.

• Protect the supply voltage externally in accordance with the connected load (number of Axioline F devices / amount of logic current consumption for each device).

• Ensure the external fuse trips reliably in the event of an error.

NOTE: Device damage due to polarity reversal

Polarity reversal puts a strain on the electronics and can damage the device.

• To protect the device, avoid reversing the poles of the 24 V supply.

107709_en_00 PHOENIX CONTACT 9 / 140

Page 10

AXC F 1050

NOTE: Device failure if operated outside the permitted ambient temperature range

Operating the device in ambient temperatures that are not within the permitted range may lead to malfunctions or even device failure.

• Ensure that the device is being operated within the permitted ambient temperature range, see Section 12.1 for more information.

NOTE: Device failure

The device is designed for mounting on a DIN rail in a control cabinet. If you do not mount the device on a DIN rail in a control cabinet, the device’s degree of protection will not be ensured. This can lead to device failure.

• Mount the device as described in Section 4.2 and Section 4.4 in order to ensure the device’s degree of protection.

NOTE: Device failure due to operation above the permitted specifications for vibrations and shock

If the device is subjected to vibrations and shock levels above the permitted specifications during operation, this may lead to malfunctions or even device failure.

• Ensure that the permitted specifications for vibrations and shocks are adhered to when operating the device, see Section 12.1.

NOTE: Electrical damage

Performing work on the controller during operation can damage the device electronics.

• Before working on the device, disconnect power from the controller.

• Make sure that the supply voltage cannot be switched on again by unauthorized per-

sons.

NOTE: Component breakage and/or short circuit

Inserting the device connectors (RJ45 connectors or USB connectors) into sockets for which they were not designed can lead to components being broken and/or device short circuit.

• Plug each connector only into the socket on the device intended for that connector.

NOTE: Property damage due to impermissible stress

The IP20 degree of protection (IEC 60529/EN 60529) requires that the device be used in a clean and dry environment. If you use the device in an environment that is outside of the specified limits, this may cause damage to the device.

• Do not subject the device to mechanical or thermal stress that exceeds the specified thresholds.

Please note:

The service interface is currently without function. The service interface (Micro-USB type B) is intended for connecting a PC. The service in-

terface is not intended for connecting other peripheral devices.

10 / 140

PHOENIX CONTACT 107709_en_00

Page 11

For your safety

1.5 Notes on using the AXC F 1050 controller in potentially explosive areas

Approval in accordance with the 2014/34/EU directive

II 3 G Ex nA IIC T4 Gc X

WARNING: Explosion hazard

Please make sure that the following notes and instructions are observed!

Installation notes

1. The controller is a category 3 device and is suitable for installation in zone 2 potentially

explosive areas. The controller meets the requirements of EN 60079-0:2012+A11:2013 and EN 60079-15:2010.

2. The controller must be installed, started up, operated, and maintained by qualified spe-

cialist personnel only.

3. Follow the installation instructions described in this user manual, in the device-specific

packing slip, and in the UM EN AXL F SYS INST user manual.

4. When installing and operating the device, the applicable safety directives (including na-

tional safety directives), accident prevention regulations, as well as general technical regulations must be observed.

5. For the safety data, please refer to the corresponding documentation (user manual,

packing slip) and the certificates (declaration of conformity and other approvals, if applicable).

6. Do not open up or modify the controller. Do not repair the controller yourself; instead

replace it with an approved controller of the same type. Repairs may only be performed by the manufacturer. The manufacturer is not liable for damage resulting from non-compliance.

7. The IP20 degree of protection (EN 60529) requires that the device be used in a clean

and dry environment.

8. Do not subject the controller to mechanical strain and/or thermal loads that exceed the

limits specified in the product documentation.

9. The controller is not designed for use in potentially dust-explosive atmospheres. If dust

is present, install the device in suitable, approved housing. Please note the surface temperature of the housing.

10. Stop the device and immediately remove it from the potentially explosive area if it is

damaged or was subject to an impermissible load or stored incorrectly or if it malfunctions.

107709_en_00 PHOENIX CONTACT 11 / 140

Page 12

AXC F 1050

Installation in zone 2

1. Observe the specified conditions for use in potentially explosive areas.

2. Install the device in a suitable approved housing (with at least IP54 protection in accor-

dance with EN 60529) that meets the requirements of EN 60079-15:2010. Pay attention to the requirements of EN 60079-14.

3. The following work is only permitted in potentially explosive areas when the power is

disconnected: – Snapping on or disconnecting the bus base modules

– Snapping the devices onto the bus base modules and the DIN rail – Removing the devices from the bus base modules and the DIN rail – Connection and disconnection of cables – Inserting and removing the SD card

4. Connect the DIN rail to protective earth ground.

5. Only devices that are designed for operation in zone 2 Ex areas and for the conditions

at the specific installation location may be connected to the circuits in zone 2.

6. The device may only be operated in potentially explosive areas when all connectors are

fully plugged in.

7. To ensure safe operation, the RJ45 connector must have a fully functioning locking clip.

Repair any damaged connectors immediately.

8. For safe operation with the SD card, it must be completely plugged and snapped in.

9. The service interface may only be used if there is no potentially explosive atmosphere.

Restrictions/limit values

1. Only connect Axioline F modules that have been approved for potentially explo-

sive areas to the controller.

Before using an Axioline F module in a zone 2 potentially explosive area, check that the Axioline F module is approved for installation in this area. For a list of modules that are approved for zone 2 potentially explosive areas, please refer to the AH EN AXC/AXL F EX ZONE 2 application note.

2. Observe the restrictions/limit values specified in the product documentation for the de-

vices.

3. Make sure that the maximum permitted current consumption on the U

is not exceed-

Bus

ed. Refer to the “Power supply to UBus” value applicable to the controller (see section “Ax-

ioline F local bus supply (UBus)” on page 127).

4. The maximum permissible current for each spring-cage contact is 8 A.

12 / 140

PHOENIX CONTACT 107709_en_00

Page 13

2 Transport and unpacking

2.1 Transport

The device is delivered in cardboard packaging.

• Only transport the device to its destination in its original packaging.

• Please note the instructions regarding handling, moisture, shock, tilt, and temperature

indicators on the packaging.

• Observe the humidity specifications and the temperature range specified for transport

(see Section “Technical data” on page 125).

• Protect the surfaces and frame as necessary to prevent damage.

• When transporting the equipment or storing it temporarily, make sure that the surfaces

are protected from the elements and any external influences, and that they are kept dry and clean.

2.2 Storage

The storage location must meet the following requirements: – Dry – Protected from unauthorized access – Protected from harmful environmental influences such as UV light – Temperature range: -40°C ... +85°C – Air pressure: 58 kPa ... 106 kPa (up to 4500 m above sea level) – Permissible humidity: 10% ... 95%, (non-condensing, non-icing)

Transport and unpacking

2.3 Checking the delivery

• Check the delivery for transport damage.

Damaged packaging is an indicator of potential damage to the device that may have occurred during transportation. This could result in a malfunction.

• Submit claims for any transport damage immediately, and inform Phoenix Contact or

your supplier as well as the shipping company without delay.

• Enclose photos which clearly document the damage to the packaging/delivery together

with your claim.

• Immediately after delivery, refer to the delivery note to check that the contents of the

packaging are complete.

• Keep the box and packaging material in case it is necessary to return the product.

• We strongly recommend using the original packaging to return the product.

• If the original packaging is no longer available, observe the following points:

– Observe the humidity specifications and the temperature range specified for trans-

port (see “Ambient conditions” on page 125). – If necessary, use dehumidifying agents. – Use appropriate ESD packaging to protect components that are sensitive to elec-

trostatic discharge. – Make sure that the packaging you select is large enough and sufficiently thick.

107709_en_00 PHOENIX CONTACT 13 / 140

Page 14

AXC F 1050

– Only use plastic bubble wrap sheets as filler material. – Attach warnings to the transport packaging so that they are clearly visible. – Please ensure that the delivery note is placed inside the package in the case of

packages that are to remain within the same country. However, if the package is

being sent to other countries, the delivery note must be placed inside a delivery

note pocket and attached to the outside so that it is clearly visible.

Scope of supply – AXC F 1050 controller

– AXL BS BK bus base module – AXL CN S/UL supply plug

2.4 Unpacking

The AXC F 1050 is supplied in the packaging together with a packing slip with installation instructions.

• Read the complete packing slip carefully before unpacking the controller.

NOTE: Electrostatic discharge!

NOTE: Property damage due to noncompliance with ESD notes

If the ESD notes are not observed during unpacking and packaging, the device may become damaged.

• Observe the ESD notes during unpacking and packaging.

14 / 140

PHOENIX CONTACT 107709_en_00

Page 15

3 Description of the AXC F 1050

3.1 Hardware and software requirements

Hardware/software Description

Controller AXC F 1050 SD card See Section “Ordering data” on page 129 Ethernet cable Ethernet cable for connecting the controller to a PC USB cable USB cable for connecting the controller to a PC, see Sec-

tion “Ordering data” on page 129

PC Worx Engineer ≥ 7.2.2

3.2 General description of the controller

The AXC F 1050 controller is approved for use in Zone 2 potentially explosive areas.

• Observe the notes in Section “Notes on using the AXC F 1050 controller in potentially explosive areas” on page 11.

Description of the AXC F 1050

The AXC F 1050 is a modular small-scale controller with integrated Ethernet and Axioline F local bus connection.

The controller consists of an electronics module (1) and a bus base module (2).

8482B009

Figure 3-1 Components of the controller

Axioline F station An Axioline F station is created by connecting Axioline F modules to the controller side-by-

side. The Axioline F local bus (referred to as local bus in this document) is implemented by arranging bus base modules side-by-side.

Programming The controller is configured and programmed using the PC Worx Engineer automation soft-

ware. The powerful processor can be programmed in all five IEC 61131 programming languages and ensures quick control task processing.

Integrated Ethernet interfaces

The controller features two Ethernet interfaces for TCP/IP/UDP/IP communication within the Ethernet network.

107709_en_00 PHOENIX CONTACT 15 / 140

Page 16

AXC F 1050

PROFINET controller / PROFINET device functions

The PROFINET protocol can be used via the Ethernet interfaces of the controller. In this case, the controller can be used as a PROFINET controller and/or PROFINET device, depending on the configuration. It cannot be used as a PROFINET controller and device concurrently.

For additional information on how to integrate the AXC F 1050 as a PROFINET controller or device, please see Section 7.4.

Axioline F local bus An interface to the Axioline F local bus is provided on the bottom of the controller. Bus base

modules are used to carry the communications power and the bus signals from the controller through the Axioline F station. A bus base module is supplied with the controller.

Up to 63 Axioline F modules can be connected to the controller. The maximum number of modules that can be operated depends on the current consumption of the modules. The total current consumption of all devices connected to the controller must not exceed the maximum current that the controller supplies for the local bus.

NOTE: Electronics may be damaged if overloaded

Observe the current consumption of each device when configuring an Axioline F station. The current consumption is specified in each module-specific data sheet and may vary. The possible number of devices that can be connected depends on the structure of the Axioline F.

Axioline F/ System and firmware

For system-specific information on the Axioline F system, please refer to the online help for the PC Worx Engineer software and the “Axioline F: System and installation” (UM EN AXL F SYS INST) and “Axioline F: Diagnostic registers and error messages” (UM EN AXL F SYS DIAG) user manuals. The user manuals can be downloaded at

phoenixcontact.net/products.

MRP The MRP Media Redundancy Protocol protocol can be used via the Ethernet interfaces of

the controller. The controller supports the MRP client function, which can be enabled or disabled via PC Worx Engineer (see also Section 7.6 for more information). This function is disabled by default. If the function is enabled, it remains enabled after the supply voltage is switched off and on. If the controller has been reset to the default settings, the MRP client function will also be disabled again. In a ring with Media Redundancy Protocol, maximum switch-over times of up to 200 ms can be expected.

Parameterization memory / SD card

The controller has an internal parameterization memory. This memory can be used to store programs and configurations which belong to your project, e.g. the visualization project. If the internal parameterization memory is not large enough for your application program, the controller can be operated using an SD card. The SD card is optional and not required to operate the controller.

The SD card is not included in the scope of delivery of the controller.

• Only use a parameterization memory provided by Phoenix Contact (see Section “Ordering data” on page 129).

NOTE: Damage to the SD card after formatting

The SD card is already formatted and is intended for use with Phoenix Contact devices. If you format the SD card, certain information on the SD card that is required for use with Phoenix Contact devices will be lost. After formatting, you can no longer use the SD card to operate the controller.

• Make sure that the SD card is not reformatted.

16 / 140

PHOENIX CONTACT 107709_en_00

Page 17

Description of the AXC F 1050

Visualization You can create visualizations for the controller using the PC Worx Engineer HMI.

Real-time clock In the event that the supply voltage fails, the real-time clock integrated in the controller is

buffered (see Section “Technical data” on page 125). You can query the status of the realtime clock using system variables (see Section 8.9 for more information).

107709_en_00 PHOENIX CONTACT 17 / 140

Page 18

AXC F 1050

3.3 Possible fields of application of the controller

3.3.1 Controller as a decentral controller for an Axioline F station

The controller can be used as a decentral controller for an Axioline F station that is connected to an Ethernet system. A maximum of 63 devices (Axioline F modules) can be connected to the controller. The maximum number of alignable devices depends on the current consumption of the devices. The total current consumption of all devices aligned on the controller must not exceed the maximum current that the controller supplies for the local bus (2 A).

Ethernet

7572

42 43

02 03

Figure 3-2 Axioline F station with AXC F 1050 controller

02 03

3532

8482B001

18 / 140

PHOENIX CONTACT 107709_en_00

Page 19

Description of the AXC F 1050

3.3.2 The AXC F 1050 as a PROFINET controller in a PROFINET network

Figure 3-3 shows the example of an AXC F 1050 as a PROFINET controller in a PROFINET network.

PROFINET

7572

42 43

02 03

3532

PROFINET

8482A020

Figure 3-3 AXC F 1050 as a PROFINET controller

Key:

A AXC F 1050 PROFINET controller B PROFINET device (in the example: PROFINET bus coupler with connected Axioline F

I/O modules)

For additional information on how to integrate the AXC F 1050 into a PROFINET network as a PROFINET controller, please refer to Section 7.4.

107709_en_00 PHOENIX CONTACT 19 / 140

Page 20

AXC F 1050

3.3.3 The AXC F 1050 as a PROFINET device in a PROFINET network

Figure 3-4 shows the example of an AXC F 1050 as a PROFINET device in a PROFINET network.

PROFINET

RUN/PROG

STP

MRESET

LNK

LAN1.1 LAN1.2

ACT

USB

FL SWITCH SMSC 8GT Ord. No. 2891123

MAC Address

00.A0.45.06.04.02

X10

US1 GND US2 GND

R1 R2

DISPLAY

LNK

ACT

LNK

LAN2

ACT

X11 MEM

RFC 470 PN 3TX Ord.No.2916600

REMOTE

MODE

ACT

SPD

US1

I/O

24VDC

LINK

US2

FAIL

678

Mode

X12 V.24

7572

42 43

02 03

3532

8482B002

Figure 3-4 AXC F 1050 as a PROFINET device

20 / 140

Key:

A PROFINET controller (in the example: RFC 470 PN 3TX Remote Field Controller) B Managed Switch (in the example: FL SWITCH SMCS ...) C AXC F 1050 PROFINET device

For additional information on how to integrate the controller into a PROFINET network as a PROFINET device, please refer to Section 7.4.

PHOENIX CONTACT 107709_en_00

Page 21

Description of the AXC F 1050

3.3.4 System redundancy with the AXC F 1050

Figure 3-5 illustrates an application example for system redundancy. In the example, two RFC 460R PN 3TX controllers connected via a fiber optic synchronization connection (SYNC) form the superordinate redundant control system. This superordinate control system controls a subordinate PROFINET ring network that is configured as redundant using the Media Redundancy Protocol (MRP). In the example, the AXC F 1050 controller operates as a PROFINET device with control function and is connected to the PROFINET network via a switch.

Identical application programs run on both superordinate PROFINET controllers. In the example, controller A is the FIRST PROFINET controller and controller B is the SECOND PROFINET controller. Which of the two controllers controls the process depends on the redundancy role (PRIMARY/BACKUP) of the controller, which may change depending on the redundancy status.

For additional information on redundancy, please refer to the UM EN RFC 460R PN 3TX user manual and the AH EN APPLICATIVE SYSTEM REDUNDANCY application note. These documents can be downloaded at

phoenixcontact.net/products.

Redundant control system (with RFC 460R PN 3TX)

Network redundancy with MRP Media Redundancy Protocol

PROFINET device (with Phoenix Redundancy Layer) in the redundancy ring (supports MRP)

RUN/PROG

STP

MRESET

LNK

LAN1.1 LAN1.2

ACT

USB

SYNC

DISPLAY

LNK

RFC 460R PN 3TX Ord.No.2700784

ACT

LNK

LAN2

ACT

24VDC

RUN/PROG

STP

MRESET

LNK

LAN1.1 LAN1.2

ACT

USB

SYNC

DISPLAY

LNK

RFC 460R PN 3TX Ord.No.2700784

ACT

LNK

LAN2

ACT

24VDC

SYNC

MODE

FL SWITCH SMSC 8GT

Ord.No.2891123

SPD

ACT

US2

FAIL

US1

MAC Address

00.A0.45.06.04.02

X10

X11

US1 GND US2 GND

R1 R2

MEM

PROFINET

SYNC

LINK

678

Mode

X12 V.24

PROFINET

7572

42 43

D UI E1 E2

02 03

3532

D UA E1 E2

02 03

FL SWITCH SMSC 8GT Ord.No.2891123

MAC Address

US1 GND US2 GND

MODE

SPD

ACT

LINK

US2

FAIL

US1

678

00.A0.45.06.04.02

Mode

X10

X11

R1 R2

MEM

X12

V.24

8482A003

Figure 3-5 Redundant superordinate control system and subordinate network ring re-

dundancy using MRP

107709_en_00 PHOENIX CONTACT 21 / 140

Page 22

AXC F 1050

Key: A FIRST PROFINET controller (in the example: RFC 460R PN 3TX);

the redundancy role (PRIMARY/BACKUP) may change depending on the redundancy status

B SECOND PROFINET controller (in the example: RFC 460R PN 3TX);

the redundancy role (BACKUP/PRIMARY) may change depending on the redundancy status

C Infrastructure components (in the example: FL SWITCH SMCS ... managed switches) D PROFINET device with control function (in the example: AXC F 1050 with activated

PROFINET device function and Phoenix Redundancy Layer)

22 / 140

PHOENIX CONTACT 107709_en_00

Page 23

Description of the AXC F 1050

3.4 Connection and operating elements

Figure 3-6 Connection and operating elements of the controller

1 Bus base module 2 Reset button 3 Service interface (Micro-USB type B), not currently used 4 Electronics module 5 Ethernet interfaces 6 Function identification 7 Supply socket (socket for connecting the supply voltage (communications power U 8 SD card holder

The SD card is not included in the scope of delivery of the controller.

Please refer to the ordering data in the section “Accessories” on page 129.

))

9 Mode selector switch 10 Diagnostics and status indicators

107709_en_00 PHOENIX CONTACT 23 / 140

Page 24

AXC F 1050

3.5 Diagnostics and status indicators

The diagnostics and status indicators are used for quick local error diagnostics.

ETH

BF-C BF-D

PWR

Figure 3-7 Diagnostics and status indicators

Table 3-1 Controller diagnostics and status indicators

BF-C BF-D

PN/AXC/ PLC

D E

Desig-

Color Meaning Status Description

nation

PN: PROFINET controller/device function

PROFINET con-

BF-C Red

troller:

Communication

error (bus fault)

PROFINET

BF-D Red

device:

Communication

error (bus fault)

SF Red

Group error

(PROFINET)

AXC F 1050 as a PROFINET controller

– The AXC F 1050 has established an active communication

connection to each configured PROFINET device.

Off

Or: – The PROFINET controller function is switched off.

Flashing

(1 Hz)

No link status on the Ethernet interfaces and/or no 100 Mbit transmission and/or no full duplex mode.

Link status present, at least one configured PROFINET device does not have a communication connection.

AXC F 1050 as a PROFINET device

– A PROFINET controller has established an active commu-

nication connection to the AXC F 1050 (PROFINET de-

Off

vice)

Or: – The PROFINET device function is switched off.

Flashing

(1 Hz)

No PROFINET communication (no link status at the Ethernet interfaces).

Link status present, no communication connection to the

PROFINET controller. Off PROFINET diagnostics not present. On PROFINET diagnostics present.

24 / 140

PHOENIX CONTACT 107709_en_00

Page 25

Table 3-1 Controller diagnostics and status indicators

Description of the AXC F 1050

Desig-

Color Meaning Status Description

nation

PLC: Controller diagnostics

RUN Green

Controller RUN

FAIL Red Failure

DBG Yellow

Debug mode

(troubleshooting)

status

Off IEC 61131 runtime system is not operational.

IEC 61131 runtime system successfully initialized and an appli-

cation program is running.

The controller is in RUN mode. IEC 61131 runtime system suc-

Flashing (0.5 Hz)

cessfully initialized.

The controller is in READY/STOP mode, application program is

not being processed.

Flashing

(2 Hz)

Off

Flashing

Controller has been reset to the default status (see Section “Re-

set button (concealed)” on page 29).

No runtime error has occurred in the IEC 61131 runtime system

program.

A runtime error has occurred in the IEC 61131 runtime system

program.

The hardware watchdog of the controller has been triggered.

(0.5 Hz)

The IEC 61131 runtime system / controller is in debug mode,

i.e. debug mode has been activated in PC Worx Engineer On

(breakpoint(s) set and/or variable(s) forced).

The status of the RUN LED is not affected.

Flashing

Controller boot phase, controller is sending Boot_Requests.

(2 Hz)

107709_en_00 PHOENIX CONTACT 25 / 140

Page 26

AXC F 1050

Table 3-1 Controller diagnostics and status indicators

Desig-

Color Meaning Status Description

nation

AXC: Axioline F diagnostics

Off

On green

Flashing

green

Yellow on

Flashing

yellow/red

Axioline F: Diag-

Red/yel-

low/green

nostics for local

bus communica-

tion

Flashing

red

Red on

Yel-

low/red

Error/warning

Yellow on I/O warning at an Axioline F device

Red on Peripheral fault at an Axioline F device

PWR: Supply voltage (communications power UL)

UL Green U

Logic

Off 24 V communications power feed-in not present or too low. On 24 V communications power feed-in present.

Power down:

Device is in (power) reset

Run:

The Axioline F station is ready for operation; communication

within the Axioline F station is OK.

All data is valid. No malfunction is present.

Active:

The Axioline F station is ready for operation; communication

within the Axioline F station is OK. The data is not valid. There

is no valid data available from the controller. No malfunction is

present on the device.

Ready:

The Axioline F station is ready for operation; no data is being

exchanged.

Local bus error during active I/O check

Local bus error during startup

Possible causes:

– Configuration cannot be generated, information is missing

from a device – Chip version of a device is <V 1.1 – Deviation between actual and required configuration – No local bus device connected – The maximum number of local bus devices has been ex-

ceeded Bus error in RUN status

The Axioline F station is ready for operation but has lost connection to at least one device.

Possible causes: – Communication error – A local bus device has been removed or a configured de-

vice is missing – Reset from a local bus device – Serious device error at a local bus device (local bus device

can no longer be reached)

26 / 140

PHOENIX CONTACT 107709_en_00

Page 27

Table 3-1 Controller diagnostics and status indicators

Description of the AXC F 1050

Desig-

Color Meaning Status Description

nation

ETH: Ethernet interfaces

LNK Green Link status

ACT Yellow Activity status

Off Connection not established successfully

Flashing

Connection established successfully (link): the controller is able to contact another network device.

PROFINET device identification “flashing”

(0.5 Hz)

Off Data transmission not active

On/flashing

Data transmission active (activity): The Ethernet interface is sending or receiving data

107709_en_00 PHOENIX CONTACT 27 / 140

Page 28

AXC F 1050

3.6 Mode selector switch

The mode selector switch is used to define the operating state of the controller.

The RUN/PROG and STOP positions have a latching function and the MRESET position has a pushbutton function. After releasing the switch in the MRESET position, it returns to the STOP position.

Table 3-2 Controller operating modes

Operating

Description

mode

RUN/PROG The controller is in the RUN state. The application program is being

processed.

The PC Worx Engineer software can be used for program and configuration modifications and online debugging.

The application program is not processed if a controller error has occurred or if the application program has been stopped by PC Worx Engineer.

STOP The controller is in the STOP state. Application program processing

has been stopped.

MRESET Retain data and the application program are deleted.

Follow these steps to delete the retain data and the application program:

• Hold the mode selector switch in the MRESET position for three seconds.

• Release the mode selector switch for fewer than three seconds.

• Hold the mode selector switch in the MRESET position for three

seconds.

28 / 140

8482B004

Figure 3-8 Mode selector switch

PHOENIX CONTACT 107709_en_00

Page 29

3.7 Reset button (concealed)

-C

-D

107709A001

Figure 3-9 Reset button (1, concealed)

The reset button on the controller can only be operated with a pointed object, such as a pin, and is therefore protected against accidental activation.

Restarting the controller • During operation, briefly press the reset button.

The controller is restarted.

Description of the AXC F 1050

Resetting the controller to the default settings

• Switch off the supply voltage of the controller.

• After the LEDs have gone out, press the reset button.

• Hold the reset button down and switch the supply voltage on. Release the reset button

only after the RUN LED flashes quickly (item 2 in Figure 3-9).

The default settings are restored. The DBG LED flashes. The process has been completed once the RUN LED flashes slowly. The controller has been successfully initialized and reset to its default settings. The control function is in the READY/STOP state; a program is not being processed. This process may take around 90 seconds.

107709_en_00 PHOENIX CONTACT 29 / 140

Page 30

AXC F 1050

3.8 Parameterization memory

The parameterization memory can be used to save programs and configurations (e.g. visualization projects, controller IP address, etc.) that belong to your PC Worx Engineer project. In addition, application-specific data can also be stored in the parameterization memory.

The controller has an integrated parameterization memory. Alternatively, it is possible to use a pluggable parameterization memory in the form of an SD card. The SD card is optional and not required to operate the controller.

NOTE: Potential data loss

Removing the SD card during operation may result in a loss of data.

• Do not remove the SD card during operation.

NOTE: Damage to the SD card after formatting

• Make sure that the SD card is not reformatted.

The SD card is recognized during the initialization phase of the controller.

• Make sure that the SD card has been inserted before switching on the controller so that the controller is able to use it.

• Only insert and remove the SD card when the controller supply voltage is disconnected.

• Only use an SD card provided by Phoenix Contact (for ordering data, see Section “Accessories” on page 129).

30 / 140

PHOENIX CONTACT 107709_en_00

Page 31

3.9 Internal basic circuit diagram

Description of the AXC F 1050

Reset

USB

24 V

Ethernet

RJ45

LNK ACT

RJ45

LNK ACT

3.3 V

24V

Bus

BF-C

BF-D

μC

Figure 3-10 Internal basic circuit diagram

RUN

FAI L

DBG

RTC

Local bus

Bus

Key:

μC

Microprocessor Transmitter

UPS LED

RJ45

LNK ACT

Service interface (Micro-USB type B) Real-time clock

Reset button Power supply unit

RJ45 interface Ethernet switch

RTC

3.3 V

24V

Bus

Functional ground connection Mode selector switch

SD card holder Axioline F local bus

Local bus

Bus

The colored areas in the basic circuit diagram represent electrically isolated areas:

Logic

Ethernet interface

Functional ground

107709_en_00 PHOENIX CONTACT 31 / 140

Page 32

AXC F 1050

3.10 Interfaces

The following interfaces are available on the controller (see Figure 3-11):

(1) 2 x Ethernet X1/X2: 10/100 Base-T(X) (switched internally)

(2) Service inter-

Currently without function face (MicroUSB type B)

8482B007

Figure 3-11 Interfaces: (1) Ethernet, (2) service interface (Micro-USB type B)

32 / 140

PHOENIX CONTACT 107709_en_00

Page 33

Description of the AXC F 1050

3.10.1 Ethernet

The controller is equipped with two Ethernet interfaces (X1/X2).

The Ethernet network is connected via RJ45 sockets.

The contact assignment of the interface is as follows:

Pin Signal Meaning

RJ45

Pin 1

Pin 2

Pin 3

Pin 4

Pin 5

Pin 6

Pin 7

Pin 8

Figure 3-12 Ethernet interface and pin assignment

The Ethernet interfaces are able to switch over the transmitter and receiver automatically (auto crossover).

1 T+ Transmit data + 2 T- Transmit data 3 R+ Receive data + 4– – 5– – 6 R- Receive data 7– – 8– –

3.10.2 Service interface (Micro-USB type B)

The service interface (Micro-USB type B) is currently without function.

107709_en_00 PHOENIX CONTACT 33 / 140

Page 34

AXC F 1050

3.11 Supply plug

Terminal point assignment

a1 a2

Figure 3-13 Terminal points for the supply voltage (communications power UL)

Table 3-3 Terminal point assignment of the supply plug

Key:

U GND Supply voltage reference potential (internally bridged)

a1a2b1

Terminal point Color Assignment

a1, a2 Red 24 V DC (U b1, b2 Blue GND

Communications power feed-in (internally bridged)

)

3.12 Bus base module

Bus base modules carry the communications power and the bus signals from the controller through the Axioline F station (local bus). A bus base module is supplied with the controller.

34 / 140

Figure 3-14 Structure of the controller bus base module

1 Bus base module 2 Connection of the local bus to the controller (socket) 3 Connection to the following bus base module (socket)

PHOENIX CONTACT 107709_en_00

8482A010

Page 35

4 Mounting hardware

4.1 Safety notes

NOTE: Electrostatic discharge!

NOTE: Device failure

• Ensure that the voltage is kept within the permitted range.

NOTE: Electrical damage due to inadequate external protection – No safe fuse tripping in the event of an error

The electronics in the device will be damaged due to inadequate external protection.

• Protect the supply voltage externally in accordance with the connected load (number of Axioline F devices / amount of logic current consumption for each device).

• Ensure the external fuse trips reliably in the event of an error.

Mounting hardware

NOTE: Device damage due to polarity reversal

Polarity reversal puts a strain on the electronics and can damage the device.

• To protect the device, avoid reversing the poles of the 24 V supply.

NOTE: Electrical damage

Performing work on the controller during operation can damage the device electronics.

• Before working on the device, disconnect power from the controller.

• Make sure that the supply voltage cannot be switched on again by unauthorized per-

sons.

NOTE: Device failure if operated outside the permitted ambient temperature range

Operating the device in ambient temperatures that are not within the permitted range may lead to malfunctions or even device failure.

• Ensure that the device is operated within the permitted ambient temperature range, see Section 12.1.

NOTE: Device failure

• Mount the device as described in Section 4.2 and Section 4.4 in order to ensure the device’s degree of protection.

107709_en_00 PHOENIX CONTACT 35 / 140

Page 36

AXC F 1050

NOTE: Device failure due to operation above the permitted specifications for vibrations and shock

If the device is subjected to vibrations and shock levels above the permitted specifications during operation, this may lead to malfunctions or even device failure.

• Ensure that the permitted specifications for vibrations and shocks are adhered to when operating the device, see Section 12.1

NOTE: Property damage due to impermissible stress

• Do not subject the device to mechanical or thermal stress that exceeds the specified thresholds.

NOTE: Component breakage and/or short circuit

Inserting the device connectors (RJ45 connectors or USB connectors) into sockets for which they were not designed can lead to components being broken and/or device short circuit.

• Plug each connector only into the socket on the device intended for that connector.

NOTE: Damage to the contacts when tilting

Tilting the modules can damage the contacts.

• Place the modules onto the DIN rail vertically (see Figure 4-1).

The controller is automatically grounded (FE) when it is snapped onto a grounded DIN rail.

There are two FE springs on the back of the controller that make contact with the DIN rail when the controller is placed on the DIN rail.

Figure 4-1 Placing the module vertically

36 / 140

PHOENIX CONTACT 107709_en_00

Page 37

Mounting hardware

4.2 Basics

For basic information on the Axioline F system and its installation, particularly mounting/removing Axioline F modules, please refer to the UM EN AXL F SYS INST user manual (“Axioline F: System and installation”).

Mounting location The controller meets the requirements for the IP20 degree of protection. The compact de-

sign means that the controller can be installed in standard terminal boxes.

Mounting / DIN rail The controller is mounted on a 35 mm standard DIN rail without any tools using the bus base

module. The controller is mounted perpendicular to the DIN rail. The local bus is created automatically when the bus base modules of the controller and Axioline F devices are installed next to one another.

• Observe the notes on securing the DIN rail and fastening elements as well as the notes on mounting distances in the UM EN AXL F SYS INST user manual.

Supply plug The controller has a supply plug for connecting the power supply. The plug has spring-cage

terminal blocks. With suitable conductors, the conductors can be connected using direct connection technology (Push-In technology).

For additional information, please refer to Section 5.2.2, “Connecting the power supply”.

FE connection There are two FE springs (metal contacts) on the bottom of the controller which establish

the connection to the functional ground when the controller is snapped onto a grounded DIN rail.

End brackets Mount end brackets on both sides of the Axioline F station. The end brackets ensure that

the Axioline F station is correctly mounted. End brackets secure the station on both sides and keep it from moving from side to side on the DIN rail. Phoenix Contact recommends the following end brackets:

Table 4-1 Recommended end brackets

Mounting position Ambient conditions End brackets

Horizontal; A in Figure 4-2 on page 38:

Other; B in Figure 4-2 on page 38

Normal CLIPFIX 35,

CLIPFIX 35-5 High shock and vibration load E/AL-NS 35 Normal E/AL-NS 35 High shock and vibration load

107709_en_00 PHOENIX CONTACT 37 / 140

Page 38

AXC F 1050

Mounting position As standard, mount the controller in a horizontal position on the DIN rail provided for that

purpose (A in Figure 4-2).

A B

02 03

8482B018

7572

42 43

D UI E1 E2

D UA E1 E2

02 03

3532

42 43

Figure 4-2 Horizontal (A) and vertical (B) mounting position

Note the ambient temperatures and any other special features (e.g. derating) specified in the device/module-specific documentation for the Axioline F devices.

38 / 140

PHOENIX CONTACT 107709_en_00

Page 39

4.3 Structure of an Axioline F station

Figure 4-3 shows an example structure of an Axioline F station:

3 4

7572

42 43

Mounting hardware

D UI

E1 E2

02 03

3532

D UA

E1 E2

02 03

Figure 4-3 Structure of an Axioline F station

Key:

1 DIN rail 2 End bracket (e.g. CLIPFIX 35-5; Order No. 3022276) 3 Controller 4 I/O modules (Axioline F devices) corresponding to the application 5 Bus base module

An Axioline F station is set up by mounting the individual components side by side. No tools are required. Mounting the components side by side automatically creates potential and bus signal connections between the individual components of the Axioline F station.

107709_en_00 PHOENIX CONTACT 39 / 140

Page 40

AXC F 1050

4.4 Mounting the controller

• Disconnect the Axioline F station from the power supply.

• Mount the left end bracket on the Axioline F station.

Mounting bus base modules

Snapping the controller into place

• First install the bus base module for the controller and then all bus base modules nec-

essary for the Axioline F station on the DIN rail (A in Figure 4-4).

• Push each subsequent bus base module into the connection of the previous bus base module (B in Figure 4-4).

Figure 4-4 Mounting the bus base modules

• Push the controller vertically on the first bus base module until it snaps into place audibly.

• Make sure that the device plug for the bus base connection is situated above the corresponding socket on the bus base module.

40 / 140

Figure 4-5 Snapping the controller into place

PHOENIX CONTACT 107709_en_00

Page 41

Mounting hardware

4.5 Inserting the SD card

The controller has an SD card holder with push/push technology.

• Gently push the SD card into the SD card holder until it engages with a click in the SD card holder.

>Click<

Figure 4-6 Inserting the SD card

8482A021

107709_en_00 PHOENIX CONTACT 41 / 140

Page 42

AXC F 1050

5 Connecting and wiring hardware

5.1 Safety notes

NOTE: Electrostatic discharge!

NOTE: Device failure

• Ensure that the voltage is kept within the permitted range.

NOTE: Electrical damage due to inadequate external protection – No safe fuse tripping in the event of an error

The electronics in the device will be damaged due to inadequate external protection.

• Protect the supply voltage externally in accordance with the connected load (number of Axioline F devices / amount of logic current consumption for each device).

• Ensure the external fuse trips reliably in the event of an error.

NOTE: Device damage due to polarity reversal

Polarity reversal puts a strain on the electronics and can damage the device.

• To protect the device, avoid reversing the poles of the 24 V supply.

NOTE: Electrical damage

Performing work on the controller during operation can damage the device electronics.

• Before working on the device, disconnect power from the controller.

• Make sure that the supply voltage cannot be switched on again by unauthorized per-

sons.

NOTE: Component breakage and/or short circuit

Inserting the device connectors (RJ45 connectors or USB connectors) into sockets for which they were not designed can lead to components being broken and/or device short circuit.

• Plug each connector only into the socket on the device intended for that connector.

NOTE: Property damage due to impermissible stress

• Do not subject the device to mechanical or thermal stress that exceeds the specified thresholds.

42 / 140

PHOENIX CONTACT 107709_en_00

Page 43

Connecting and wiring hardware

The controller is automatically grounded (FE) when it is snapped onto a grounded DIN rail.

There are two FE springs on the back of the controller that make contact with the DIN rail when the controller is placed on the DIN rail.

Please note:

The service interface is currently without function. The service interface (Micro-USB type B) is intended for connecting a PC. The service in-

terface is not intended for connecting other peripheral devices.

107709_en_00 PHOENIX CONTACT 43 / 140

Page 44

AXC F 1050

5.2 Supply voltage

5.2.1 Sizing of the power supply

• Choose a power supply unit that is suitable for the currents in your application. The se-

lection depends on the bus configuration and the resulting maximum currents.

A power supply without a fall-back characteristic curve must be used for correct operation of the controller (see Figure 5-2). When the controller is switched on, an increased inrush current arises briefly. At the moment it is switched on, the controller behaves as a capacitive load.

WARNING: Loss of electrical safety when using unsuitable power supplies

The controller is designed exclusively for operation with protected extra-low voltage (PELV) in accordance with EN 60204-1. Only PELV in accordance with the listed standard may be used for the supply.

The following applies to the network (PROFINET) and the I/O devices used in it: Only use power supply units that satisfy EN 61204, with safe isolation and PELV in accor-

dance with EN 50178 or EN 61010-2-201. These prevent short circuits between primary and secondary sides.

Some electronically controlled power supplies have a fall-back characteristic curve (see Figure 5-1). They are not suitable for operation with capacitive loads.

Overload range

OUT

[V]

with fall-back

characteristic curve

OUT

 1.1 x I

 2.4 x I

[A]

6219C070

Figure 5-1 Overload range with fall-back characteristic

curve

OUT

[ ]

without fall-back

characteristic curve

OUT

[ ]

Overload range

Figure 5-2 Overload range without fall-back charac-

teristic curve



1.5 x I

6219 071C

44 / 140

PHOENIX CONTACT 107709_en_00

Page 45

Connecting and wiring hardware

5.2.2 Connecting the power supply

Observe the notes in Section 3.11 when assembling the connector for the supply voltage.

• Strip 8 mm off the cable. If necessary, fit a ferrule to the cable.

If you are using ferrules, use them in accordance with the specifications in the UM EN AXL F SYS INST user manual.

• Ensure that the ferrules are correctly crimped.

Solid conductor / ferrule

Stranded conductor • Open the spring by pressing on the spring lever with a screwdriver (A in Figure 5-4).

• Insert the cable into the terminal point. It is clamped into place automatically.

Figure 5-3 Connecting a solid cable

• Insert the conductor into the terminal point (B in Figure 5-4).

• Remove the screwdriver to fasten the cable (recommended: bladed screwdriver, blade

width of 2.5 mm (e.g. SZS 0,4x2,5 VDE, Order No. 1205037)

Figure 5-4 Connecting a stranded conductor

107709_en_00 PHOENIX CONTACT 45 / 140

Page 46

AXC F 1050

Connecting the supply plug

• Place the supply plug vertically into its position and press down firmly. Ensure that the

locking latch snaps into place.

8482B014

Figure 5-5 Connecting the supply plug

Supply the controller via external 24 V DC sources. The permissible voltage range is

19.2 V DC to 30 V DC (ripple included). The power consumption of the controller at 24 V is typically 3 W (no local bus devices connected).

• Only use power supplies that are suitable for operation with capacitive loads (increased inrush current) (see Section 5.2.1).

1. Connect the power supplies to the supply plug as shown above. Note the information in Section 3.11.

2. Switch on the power supplies.

– Behavior of the device LEDs when switching on for the first time (default setting):

– The UL LED lights up. The FAIL LED lights briefly, then the DBG LED flashes for

around 30 seconds. The controller is sending Boot_Requests during these 30 seconds. If a BootP_Server is present in the network, you can assign the controller an IP address via BootP. Once the IP address has successfully been assigned or the 30 seconds have elapsed, the DBG LED goes out. The D LED then remains on permanently (red) and the RUN LED starts flashing.

– Behavior of the device LEDs when an application program is present on the controller

and the IP address settings have been assigned: The FAIL LED lights briefly. When the controller starts up without errors, the RUN and

D LEDs (green) come on and stay on solid.

The controller is now fully initialized.

If the LEDs do not light up or start flashing, there is a serious fault in the controller.

• In this case, please contact Phoenix Contact.

46 / 140

PHOENIX CONTACT 107709_en_00

Page 47

Connecting and wiring hardware

5.3 Connecting Ethernet

• Connect the Ethernet network to the RJ45 sockets.

• Use an Ethernet cable that at least meets the IEEE 802.3 CAT5 requirements.

• Observe the bending radii of the Ethernet cables used.

8482B008

Figure 5-6 Connecting Ethernet

107709_en_00 PHOENIX CONTACT 47 / 140

Page 48

AXC F 1050

6 Starting up with PC Worx Engineer

You must have the PC Worx Engineer software to start up the controller.

6.1 Installing PC Worx Engineer

The software can be downloaded at phoenixcontact.net/product/1046008.

• Download the software onto your PC.

• Double-click on the *.exe file to start installation.

• Follow the instructions of the installation wizard.

6.2 PC Worx Engineer licenses

Once installed, a demo version of PC Worx Engineer is available to you for 30 days. You can use the demo version once on one PC.

You must register PC Worx Engineer within 30 days to continue using the software. To do this, proceed as follows:

• Log in with your access data on the product page at

phoenixcontact.net/product/1046008.

• Select the necessary license(s).

Free licenses and licenses for purchase are available. The licenses are linked to the hardware of a PC.

Once you have sent your order, you will receive an email from Phoenix Contact within 48 hours that contains a ticket ID. You need the ticket ID together with your computer footprint to activate the license.

To register PC Worx Engineer, you must activate the license. The license is activated via the Phoenix Contact Activation Wizard. The Phoenix Contact Activation Wizard is available to download at

phoenixcontact.net/product/1046008 (standalone or as a component of

PC Worx Engineer).

• To activate a license, follow the instructions in the Phoenix Contact Activation Wizard.

48 / 140

PHOENIX CONTACT 107709_en_00

Page 49

Starting up with PC Worx Engineer

6.3 User interface

Figure 6-1 The PC Worx Engineer user interface

1. Menu bar

2. Tool bar

3. “PLANT” area

4. Editors area

5. “COMPONENTS” area

6. Cross-functional area

7. Status bar

“PLANT” area All of the physical and logical components of your application are mapped in the form of a

hierarchical tree structure in the “PLANT” area.

Editors area Double clicking on a node in the “PLANT” area or an element in the “COMPONENTS” area

opens the associated editor group in the Editors area. Editor groups are always displayed in the center of the user interface. The color of the editor group indicates whether it is an instance editor (green; opened from the “PLANT” area) or a type editor (blue; opened from the “COMPONENTS” area). Each editor group contains several editors that can be opened and closed via buttons in the editor group.

107709_en_00 PHOENIX CONTACT 49 / 140

Page 50

AXC F 1050

“COMPONENTS” area The “COMPONENTS” area contains all of the components available for the project. The

components can be divided into the following types based on their function: – Developing program code (“Data Types”, “Programs”, and “Functions & Function

Blocks”)

– Showing all devices available for the “PLANT” area and adding them via GSDML or FD-

CML (“Devices”)

– Editing HMI pages (“HMI”) – Adding libraries such as firmware libraries, International Electrotechnical Commission

(IEC) user libraries or libraries provided by Phoenix Contact (“References”)

Cross-functional area The cross-functional area contains functions that extend across the entire project.

– ERROR LIST:

Shows all errors, warnings and messages of the current project

– GLOBAL FIND AND REPLACE:

Finds and replaces strings in the project

– CROSS REFERENCES:

Displays all cross-references within the project – for example, the use and declaration of all variable types or HMI tags

– WATCH WINDOWS:

Debug tool; shows the current values of the added variables in online mode

– BREAKPOINTS:

Debug tool for setting and resetting breakpoints when debugging within the application

– CALL STACKS:

Debug tool that shows the order for calling up when executing the code and that contains commands for debugging with breakpoints

– LOGIC ANALYZER:

Records and visualizes variable values at runtime

– LOGGING:

Shows all errors, warnings and messages. A distinction is made between “online” (messages regarding the runtime environment and errors and warnings that concern online communication) and “engineering” (messages regarding software events, e.g., GSDML or FDCML files; not project-related).

– RECYCLE BIN:

Elements that have recently been deleted from the “PLANT” or “COMPONENTS” areas are moved to the recycle bin. Deleted elements can be restored from here, if needed.

50 / 140

PHOENIX CONTACT 107709_en_00

Page 51

Starting up with PC Worx Engineer

6.4 Creating a new project

• Open PC Worx Engineer.

• Click on the “Empty AXC F 1050 project” project template on the start page.

The project template for an “Empty AXC F 1050 project” opens.

Figure 6-2 Start page, “Empty AXC F 1050 project” project template

• Open the “File, Save Project as …” menu.

• Enter a unique and meaningful name for the project.

• Click on “Save”.

107709_en_00 PHOENIX CONTACT 51 / 140

Page 52

AXC F 1050

6.5 Configuring the IP settings

6.5.1 Setting the IP address range

• Double-click on the “Project (x)” node in the “PLANT” area.

The “Project” editor group opens.

• Select the “Settings” editor.

• Set the desired IP address range and the subnet mask for the project.

52 / 140

Figure 6-3 Setting the IP address range

PHOENIX CONTACT 107709_en_00

Page 53

Starting up with PC Worx Engineer

6.5.2 Setting the IP address

• Double-click on the controller node in the “PLANT” area.

The “axcf1050-1” editor group opens.

• Select the “Settings” editor.

• Select the “Ethernet” view.

Setting the IP address automatically

Setting the IP address manually

Figure 6-4 Setting the IP address

The IP address of the controller can be set automatically or manually. The IP address is assigned to the controller when you have connected PC Worx Engineer to the controller, see Section 6.7, “Connecting to the controller”.

• Select “automatic” in the “IP address assignment mode” drop-down list.

PC Worx Engineer automatically assigns an IP address to the controller from the set IP address range (see Section 6.5.1, “Setting the IP address range”) as soon as a connection to the controller is established (see Section 6.7, “Connecting to the controller”).

• Select “manual” in the “IP address assignment mode” drop-down list.

• Enter the IP address, subnet mask and gateway in the respective input fields.

PC Worx Engineer assigns the manually set IP address to the controller as soon as a connection to the controller is established (see Section 6.7, “Connecting to the controller”).

107709_en_00 PHOENIX CONTACT 53 / 140

Page 54

AXC F 1050

6.6 Using the simulation function

You can simulate a project if you do not want it to be transferred to a controller. To use the simulation function, proceed as follows:

• Double-click on the controller node in the “PLANT” area.

The “axcf1050-1” editor group opens.

• Select the “Cockpit” editor.

Select “Simulation” from the drop-down list (see Figure 6-5).

54 / 140

Figure 6-5 Setting up a simulation

• Click on the button (“Write project to controller and start execution. (F5)”).

The project is compiled, sent to the simulation and started.

The simulation includes a web server. If the project includes a PC Worx Engineer HMI application (see Section 6.14), the web server provides the PC Worx Engineer HMI application and processes the generated HMI pages.

PHOENIX CONTACT 107709_en_00

Page 55

Starting up with PC Worx Engineer

6.7 Connecting to the controller

To be able to transfer a project to the controller, you must connect PC Worx Engineer to the controller. To do this, proceed as follows:

• Double-click on the controller node in the “PLANT” area.

The “axcf1050-1” editor group opens.

• Select the “Cockpit” editor.

• Select “TCP/IP” from the drop-down list.

Figure 6-6 Setting TCP/IP

• Double-click on the “Project (x)” node in the “PLANT” area.

The “Project” editor group opens.

• Select the “Online Devices” editor.

• Select the desired network card from the drop-down list.

Figure 6-7 Selecting the network card

You can show and hide more detailed information by clicking on the arrows next to “Name of station (Project)” and “Name of station (Online)” (see Figure 6-7).

• Click on the button to search the network for connected devices.

You can see the configured devices under “Name of station (Project)”.

107709_en_00 PHOENIX CONTACT 55 / 140

Page 56

AXC F 1050

You can see the devices that have been found online in the network (Online Devices) under “Name of station (Online)”.

Figure 6-8 Assigning online devices

If you select the device (“Select online device here”) under “Name of station (Online)”, the controller found in the network (the online device) receives the IP settings of the configured controller.

If you select the device (“Select project device here”) under “Name of station (Project)”, the configured controller receives the IP settings of the online device found in the network.

• Select the desired device.

The configured controller has now been assigned to an online device.

If the IP address of an online device found in the network already matches the IP address of the configured controller, the online device is automatically assigned to the configured controller. In this case, you do not need to select the desired device for the assignment.

The icon in the “Status” column indicates the connection was successful.

Figure 6-9 Successful assignment of the configured controller to an online device

56 / 140

PHOENIX CONTACT 107709_en_00

Page 57

Starting up with PC Worx Engineer

Once the configured controller has been assigned to an online device, you can connect PC Worx Engineer to the controller:

• Double-click on the controller node in the “PLANT” area.

The controller editor group opens.

• Select the “Cockpit” editor.

• Click on the button to connect PC Worx Engineer to the controller.

The icon next to the controller node in the “PLANT” area indicates the connection was successful.

Figure 6-10 Connection to the controller was established successfully

107709_en_00 PHOENIX CONTACT 57 / 140

Page 58

AXC F 1050

6.8 Configuring Axioline F modules

All of the physical and logical components of your application are mapped in the form of a hierarchical tree structure in the “PLANT” area. There are two ways to add Axioline F modules to the tree structure. You can add the Axioline F modules manually or have them read in automatically.

Role picker: Adding Axioline F modules manually

To add Axioline F modules manually, proceed as follows:

• Double-click on the “Axioline F (x)” node in the “PLANT” area.

The “/ Axioline F” controller editor group opens.

• Select the “Device List” editor.

• Select “Select type here” in the first row in the “Device List” editor.

The role picker opens. Only the elements from the “COMPONENTS” area that you can actually use are displayed in the role picker.

58 / 140

Figure 6-11 Role picker for selecting the Axioline F modules

• Select the relevant Axioline F module in the role picker.

The Axioline F module is automatically added and shown under the “Axioline F (x)” node in the “PLANT” area (see Figure 6-12 on page 59).

• Proceed as described above to add more Axioline F modules.

PHOENIX CONTACT 107709_en_00

Page 59

Starting up with PC Worx Engineer

Figure 6-12 Axioline F modules in the “PLANT” area and in the Device List

Reading Axioline F modules in automatically

The following preconditions must be satisfied before you can read in Axioline F modules automatically:

– The controller has valid IP settings (see Section 6.5). – PC Worx Engineer is connected to the controller (see Section 6.7).

To read in the Axioline F devices automatically, proceed as follows:

• Right-click the “Axioline F (x)” node in the “PLANT” area.

• Select “Read Axioline F devices” in the context menu.

The Axioline F devices are now read in automatically.

107709_en_00 PHOENIX CONTACT 59 / 140

Page 60

AXC F 1050

6.9 Configuring PROFINET devices

6.9.1 Adding PROFINET devices

• Double-click on the “Profinet (x)” node in the “PLANT” area.

The “/ Profinet” controller editor group opens.

• Select the “Device List” editor.

• Select “Select type here” in the first row in the “Device List” editor.

The role picker opens. Only the elements from the “COMPONENTS” area that you can actually use are displayed in the role picker.

60 / 140

Figure 6-13 Role picker for selecting PROFINET devices

• Select the relevant PROFINET device in the role picker.

The PROFINET device is automatically added and mapped under the “Profinet (x)” node in the “PLANT” area.

• Proceed as described above to add more PROFINET devices.

Figure 6-14 PROFINET devices in the “PLANT” area and in the Device List

PHOENIX CONTACT 107709_en_00

Page 61

Starting up with PC Worx Engineer

6.9.2 Assigning online devices

After you add PROFINET devices to the project, you must assign each configured PROFINET device to the corresponding PROFINET device of your actual bus structure (online device). By making this assignment, you are giving the PROFINET devices their IP settings and their PROFINET device names. To do this, proceed as follows:

• Double-click on the “Profinet (x)” node in the “PLANT” area.

The “/ Profinet” controller editor group opens.

• Select the “Online Devices” editor.

• Select the desired network card from the drop-down list.

Figure 6-15 Selecting the network card

• Click on the button to search the network for connected devices.

You can see the configured devices under “Name of station (Project)”.

You can see the devices that have been found online in the network (Online Devices) under “Name of station (Online)”.

Figure 6-16 Assigning online devices

107709_en_00 PHOENIX CONTACT 61 / 140

Page 62

AXC F 1050

If you select the PROFINET device (“Select online device here”) under “Name of station (Online)”, the PROFINET device found in the network (the online device) receives the IP settings of the configured PROFINET device.

Please note:

The PROFINET device is not supplied with a factory preset IP address.

• When starting up the PROFINET device for the first time, choose the device under “Name of station (Online)”.

The PROFINET device receives the IP settings of the configured PROFINET device.

If you select the device (“Select project device here”) under “Name of station (Project)”, the configured PROFINET device receives the IP settings of the online device found in the network.

• Select the desired device.

The configured PROFINET device has now been assigned to an online device. The icon in the “Status” column indicates that the assignment was successful.

Figure 6-17 Successful assignment of the configured PROFINET device to an online

device

62 / 140

PHOENIX CONTACT 107709_en_00

Page 63

Starting up with PC Worx Engineer

6.9.3 Adding I/O modules

Once you have added all the PROFINET devices from your bus structure to the project, you can add the I/O modules connected to the PROFINET device. You can add I/O modules manually or have them read in automatically.

Adding I/O modules manually

To add I/O modules manually, proceed as follows:

• Double-click in the “PLANT” area on the PROFINET device whose I/O modules you wish to add.

The editor group of the selected PROFINET device opens; “axf-f-bk-pn-1” in the example.

• Select the “Module List” editor.

• Select “Select type here” in the first row in the “Module List” editor.

The role picker opens. Only the elements from the “COMPONENTS” area that you can actually use are displayed in the role picker.

Figure 6-18 Role picker for selecting I/O modules

• Select the relevant I/O module in the role picker.

107709_en_00 PHOENIX CONTACT 63 / 140

Page 64

AXC F 1050

The I/O module is automatically added and shown in the “PLANT” area under the “Profinet” node for the respective PROFINET device (see Figure 6-19).

• Proceed as described above to add more I/O modules.

Figure 6-19 I/O modules of a PROFINET device in the “PLANT” area and in the module

list

Reading in I/O modules automatically

The following preconditions must be satisfied before you can read in the I/O modules of a PROFINET device automatically:

– The controller has valid IP settings (see Section 6.5). – The PROFINET device has valid IP settings and is connected with PC Worx Engineer

(see Section 6.9.2).

To read in the I/O modules of a PROFINET device automatically, proceed as follows:

• Right-click in the “PLANT” area beneath the “Profinet” node on the PROFINET device whose I/O modules you wish to read in.

• Select the “Read Profinet modules” entry in the context menu.

Figure 6-20 Reading in I/O modules of a PROFINET device automatically

64 / 140

The I/O modules connected to the PROFINET device are now read in automatically.

PHOENIX CONTACT 107709_en_00

Page 65

6.10 Programming in accordance with IEC 61131-3

6.10.1 Opening and creating the POU, creating variables

When you create a project, a Program Organization Unit (POU) with the name “Main” is created automatically in the “COMPONENTS” area under “Programs”.

Opening the POU To open a POU, proceed as follows:

• Click on “Programs” in the “COMPONENTS” area and then on “Local”.

• Double-click on the desired POU, for example “Moving_Light_Prog”.

The editor group of the selected POU opens. You are prompted to select the programming language for the first worksheet of the POU.

Starting up with PC Worx Engineer

Figure 6-21 Selecting the programming language for the first worksheet

Creating a new POU To create a new POU, proceed as follows:

• Click on “Programs” in the “COMPONENTS” section.

• Right-click on “Local”.

• In the context menu, select “Add Program”.

107709_en_00 PHOENIX CONTACT 65 / 140

Page 66

AXC F 1050

Figure 6-22 “Add Program” in the context menu

Creating variables Once you have created a POU, the editor group of the POU opens.

• Select the “Variables” editor.

• Create the variables that you need for the selected POU.

66 / 140

Figure 6-23 Creating variables for a POU (“Moving_Light_Prog” in the example

for the POU)

Once you have created all of the necessary variables, create the program for the selected POU, see Section 6.10.2.

PHOENIX CONTACT 107709_en_00

Page 67

6.10.2 Creating a program

Creating a program To create a program, proceed as follows:

• Select the program editor.

By default, the program editor is designated with “Code”. You can change the designation of the program editor as desired.

• Create the program.

Starting up with PC Worx Engineer

Figure 6-24 Example program in FBD

Adding worksheets The program for a POU can consist of several worksheets and of different programming lan-

guages. For each required programming language, add a corresponding worksheet (Code Worksheet) to the POU. Each worksheet is inserted in the editor group of the POU as an additional “code” editor. To add additional worksheets to a POU, proceed as follows:

• Select a worksheet in the program editor (in Figure 6-25: “Code” editor).

• Click on the arrow on the right next to the designation of the program editor.

• From the drop-down list that opens, select the desired code worksheet.

107709_en_00 PHOENIX CONTACT 67 / 140

Page 68

AXC F 1050

Figure 6-25 Adding a code worksheet to a POU

6.10.3 Creating functions and function blocks

Creating a function or function block

To create your own functions and function blocks, proceed as follows:

• Click on “Functions & Function Blocks” in the “COMPONENTS” area.

• Right-click on “Local”.

• In the context menu, select the appropriate entry for the new function or function block

to be created.

Figure 6-26 Context menu for adding a function or a function block

The newly created function or function block is inserted below the “Local” entry in the “COMPONENTS” area.

• Right-click to open the context menu for the newly created function or function block.

• Select “Rename”.

• Enter a unique and meaningful name, “Moving_Light” in the example.

• Press the “Enter” key to apply the entry.

68 / 140

PHOENIX CONTACT 107709_en_00

Page 69

Starting up with PC Worx Engineer

Figure 6-27 Newly created function block in the “COMPONENTS” area

Once you have created a new function or function block, you must program the logic for the function or the function block. To do this, first select the programming language for the first worksheet.

Selecting the programming language for the first worksheet

• Double-click on the function or function block in the “COMPONENTS” area.

The editor group of the function or function block opens. You are prompted to select the programming language for the first worksheet of the function or function block.

Figure 6-28 Selecting the programming language for the first worksheet

• Double-click on the desired programming language.

107709_en_00 PHOENIX CONTACT 69 / 140

Page 70

AXC F 1050

Creating variables Once you have chosen the programming language, create the required variables. To do

this, proceed as follows:

• Select the “Variables” editor.

• Create the variables that you need for programming the function or function block.

Figure 6-29 Creating variables for a function block (“Moving_Light” in the example for

the function block)

Once you have created all of the required variables, program the logic for the function or function block.

70 / 140

PHOENIX CONTACT 107709_en_00

Page 71

Programming logic • Select the “Code” editor.

• Create the program.

Starting up with PC Worx Engineer

Figure 6-30 Example code for a function block

Adding worksheets The program can consist of several worksheets and of different programming languages.

For each required programming language, add a corresponding worksheet (code worksheet) to the function or the function block. Each worksheet is inserted in the editor group of the function or function block as another “Code” editor. To add additional worksheets to a function or function block, proceed as follows:

• Select a worksheet in the program editor.

• Click on the arrow on the right next to the designation of the program editor.

• From the drop-down list that opens, select the desired code worksheet.

107709_en_00 PHOENIX CONTACT 71 / 140

Page 72

AXC F 1050

6.11 Instantiating programs

Instantiate the program in the “Tasks and Events” editor. To instantiate a program, create the required task and assign it to the desired program instance.

Opening the “Tasks and Events” editor

Creating tasks To create a new task, proceed as follows:

Instantiating a program To instantiate a program, proceed as follows:

To open the “Tasks and Events” editor, proceed as follows:

• Double-click on the “PLC” node in the “PLANT” area.

The “/ PLC” controller editor group opens.

• Select the “Tasks and Events” editor.

• In the “Name” column, enter a name for the new task in the “Enter task name here” input

field.

• Click in the input field in the “Task Type” column.

• Select the task type in the “Task type” drop-down list.

• Make all of the required settings for the task in the remaining columns.

• In the “Name” column, enter a name for the program instance below a task in the “Enter

program instance name here” input field (“Moving_Light” in the example in Figure 6-31).

• Click on “Select program type here” in the “Program Type” column.

• Select the program to be instantiated from the drop-down list (“Moving_Light_Prog” in

the example in Figure 6-31).

• The selected program is instantiated and assigned to a task.

72 / 140

Figure 6-31 Tasks and program instances in the “Tasks and Events” editor

PHOENIX CONTACT 107709_en_00

Page 73

6.12 Assigning process data

There are two options for assigning process data: – Assigning a process data item to a variable. – Assigning a variable to a process data item.

Process data is assigned in the “Data List” editor.

Starting up with PC Worx Engineer

Assigning a process data item to a variable

To assign a process data item to a variable, proceed as follows:

• Double-click on the “PLC” node in the “PLANT” area.

The “/ PLC” controller editor group opens.

• Select the “Data List” editor.

You can see an overview of all available variables in the “Data List” editor.

Figure 6-32 Example: List of all available variables

You are also given an overview of all available variables when you double-click on the node for the controller in the “PLANT” area and also open the “Data List” editor there. You can also assign the process data at this point.

107709_en_00 PHOENIX CONTACT 73 / 140

Page 74

AXC F 1050

• In order to assign a process data item to a variable, click on “Select Process Datum

here” in the “Process Datum” column.

The role picker opens. Only the process data that you can actually assign to the respective variable is displayed in the role picker.

74 / 140

Figure 6-33 Role picker for selecting process data

• In the role picker, select the process data item that you want to assign to the respective variable.

The process data item is assigned to the variable.

• Proceed as described for more variables.

PHOENIX CONTACT 107709_en_00

Page 75

Starting up with PC Worx Engineer

Assigning a variable to a process data item

In order to assign a variable to a process data item, proceed as follows:

• Double-click on the “Axioline F” node in the “PLANT” area (for Axioline F modules) or

• Double-click on the “Profinet” node in the “PLANT” area (for PROFINET devices).

The “/ Axioline F” controller editor group (for PROFINET devices: “/ Profinet”) opens.

• Select the “Data List” editor.

• You can see an overview of all available process data in the “Data List” editor.

Figure 6-34 Example: List of all available process data

107709_en_00 PHOENIX CONTACT 75 / 140

Page 76

AXC F 1050

• In order to assign a variable to a process data item, click on “Select Variable (PLC)

here” in the “Variable (PLC)” column.

The role picker opens. Only the variables that you can actually assign to the respective process data item are displayed in the role picker.

Figure 6-35 Role picker for selecting variables

• In the role picker, select the variable that you want to assign to the respective process data item.

The variable is assigned to the process data item.

• Proceed as described above to add more process data.

76 / 140

PHOENIX CONTACT 107709_en_00

Page 77

Starting up with PC Worx Engineer

6.13 Transfer the project to the controller

To transfer a project to the controller, proceed as follows:

• Double-click on the controller node in the “PLANT” area.

The “axcf1050-1” editor group opens.

• Select the “Cockpit” editor.

• Click on the button (“Write project to Controller and start execution. (F5)”).

The project is compiled, transferred to the controller and executed.

Please note:

The project will only be transferred to the controller if you have selected “Cockpit” “TCP/IP” in the editor; see Section “Connecting to the controller” on page 55 for more information. If you selected “Simulation”, the simulation starts.

6.14 Creating an HMI application

In PC Worx Engineer, you can create an HMI application with which you can visualize, monitor and control your application program on your controller.

For more information on creating an HMI application, see “Installing and operating the PC Worx Engineer software” in the quick start guide and in the PC Worx Engineer online help.

107709_en_00 PHOENIX CONTACT 77 / 140

Page 78

AXC F 1050

7 Additional functions in PC Worx Engineer

In the “Online Parameters” editor, you can – Activate or deactivate device-specific controller functions – Make device-specific settings and transfer them to the controller – Read device-specific controller settings

Open the “Online Parameters” editor

• Double-click on the “MONA” node in the “PLANT” area.

The “Online Parameters” editor opens.

78 / 140

Figure 7-1 “Online Parameters” editor

The settings that you can make in the individual views of the “Online Parameters” editor are described in Sections 7.1 to 7.9.

PHOENIX CONTACT 107709_en_00

Page 79

Additional functions in PC Worx Engineer

7.1 Entering or reading the controller functions and

installation location

In the “Identity” view, you can enter the function and installation location for the controller or read the controller's current setting.

• Select the “Identity” view.

Figure 7-2 “Online Parameters” editor, “Identity” view

Entering the function and installation location

Transferring the settings to the controller

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

• Enter the function of the controller in the “Function” input field (max. 32 characters).

• Enter the controller's installation location in the “Location” input field (max. 22 charac-

ters).

You can also make these settings in the “axcf1050-1” editor group in the “Settings” editor.

• To do so, double-click on the node for the controller in the “PLANT” area.

• Select the “Identity” view.

• Click on the button to send the settings to the controller (“Write values to the de-

vice”).

107709_en_00 PHOENIX CONTACT 79 / 140

Page 80

AXC F 1050

7.2 Selecting or reading protocols for manual IP

assignment

The controller IP settings that you have made in the “axcf1050-1” editor group are displayed in the “LAN” view.

Figure 7-3 “Online Parameters” editor, “LAN” view

If you selected “manual” for the IP address assignment mode in the “Settings” editor in the “axcf1050-1” editor group, you can change the IP settings in the “LAN” view. In addition, you can specify which protocol should be used for manually assigning the IP address in the “LAN” view.

• Select the protocol to be used for manually assigning the IP address from the “IP assignment” drop-down list.

Possible settings: – “Static” – “BootP” – “DHCP”

• Enter the IP address, subnet mask and gateway in the respective input fields.

Transferring the settings to the controller

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

• Click on the button to send the settings to the controller (“Write values to the de-

vice”).

The settings will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

80 / 140

PHOENIX CONTACT 107709_en_00

Page 81

Additional functions in PC Worx Engineer

7.3 Setting or reading the real-time clock

In the “RTC” view, you can set the real-time clock and date information for the controller and read the controller's current setting.

If you synchronized the real-time clock and date information to an SNTP server earlier (see Section 7.9) and are now setting the real-time clock manually, the previous time and date information will be overwritten.

• Select the “RTC” view.

Figure 7-4 “Online Parameters” editor, “RTC” view

Setting the date and time • Enter the desired time in the “Time” input field.

• Enter the desired date in the “Date” input field.

• In the field “RTC time offset from UTC”, enter the time offset of your location from UTC

(Coordinated Universal Time).

Transferring the settings to the controller

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

• Click on the button to send the settings to the controller (“Write values to the de-

vice”).

The settings will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

107709_en_00 PHOENIX CONTACT 81 / 140

Page 82

AXC F 1050

7.4 Switching the PROFINET controller / PROFINET

device function on or off

The controller can be used as a PROFINET controller and/or as a PROFINET device.

In the “Profinet” view, you can switch the PROFINET controller / PROFINET device function on or off, or view the controller's current setting.

• Select the “Profinet” view.

Figure 7-5 “Online Parameters” editor, “Profinet” view

Switching the PROFINET controller function on or off

Switching the PROFINET device function on or off

Transferring the settings to the controller

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

• To switch the PROFINET controller function on, select “Activated” in the “Profinet con-

troller status” drop-down list.

• To switch the PROFINET controller function off, select “Deactivated” in the “Profinet controller status” drop-down list.

• To switch the PROFINET device function on, select “Activated” in the “Profinet device status“ drop-down list.

• To switch the PROFINET device function off, select “Deactivated” in the “Profinet device status“ drop-down list.

• Click on the button to send the settings to the controller (“Write values to the de- vice”).

The settings will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

82 / 140

PHOENIX CONTACT 107709_en_00

Page 83

Additional functions in PC Worx Engineer

7.5 Using the SD card as the main memory or

additional memory

The SD card can be used as main or as additional memory.

Figure 7-6 shows how to proceed to use the SD card as the main or additional memory.

Setting in PCWorx Engineer:

Use external SD card as additional memory

Do not remove the SD card during operation

Preferably, use the

external SD card as main memory

SD card inserted before PLC start-up

SD card inserted after PLC start-up

SD card inserted before/after PLC start-up

SD card is main memory

SD card is additional memory

Figure 7-6 Procedure for using the SD card as the main or additional memory

7.5.1 Main memory

If you use the SD card as the main memory, all application-specific data is stored on the SD card.

The SD card is recognized during the initialization phase of the controller.

• Make sure that the SD card is inserted before switching on the controller to enable the controller to use it as the main memory.

If you are using the SD card as the main memory, you may not remove the SD card during operation.

NOTE: Potential data loss

Removing the SD card during operation may result in a loss of data.

• Do not remove the SD card during operation.

107709A003

Should the SD card be accidentally removed during operation, the controller signals an error, stops processing the application program, and switches to the READY state. The FAIL LED indicates an error. If an online connection to PC Worx Engineer is active, a display appears in the cross-functional area indicating that the SD card was unintentionally inserted or removed.

Changing operating modes

If you are operating the controller without an SD card, all application-specific data is stored on the internal parameterization memory of the controller.

When changing operating modes (operating the controller with/without SD card), please note the following:

Change: operation without SD card  operation with SD card

To change the controller mode from “operation without SD card” to “operation with SD card”, proceed as follows:

• Switch off the supply voltage of the controller.

• Insert the SD card, see Section 4.5.

107709_en_00 PHOENIX CONTACT 83 / 140

Page 84

AXC F 1050

• Switch on the supply voltage of the controller.

NOTE: Deletion of all data in the internal parameterization memory

When the controller is switched on with an SD card inserted, all application-specific data except for the IP address is deleted from the internal parameterization memory. Any PC Worx Engineer projects stored there are no longer available. The controller accesses the data stored on the SD card.

Change: operation with SD card  operation without SD card

To change the controller mode from “operation with SD card” to “operation without SD card”, proceed as follows:

• Switch off the supply voltage of the controller.

• Remove the SD card, see Section 10.4.

• Switch on the supply voltage of the controller.

NOTE: No data on the internal parameterization memory

Once the controller has been operated with an SD card, there is no data available on the internal parameterization memory.

PC Worx Engineer setting To use the SD card as the main memory, make the following setting in PC Worx Engineer:

• Double-click on the “MONA” node in the “PLANT” area.

The “Online Parameters” editor opens.

• Select the “External SD card” view.

84 / 140

Figure 7-7 “Online Parameters” editor, “External SD card” view, Preferably, use the SD

card as main memory

• In the “Use of external SD card” drop-down list, select the setting “Preferably, use the SD card as main memory”.

PHOENIX CONTACT 107709_en_00

Page 85

Additional functions in PC Worx Engineer

Transferring the setting to the controller

Reading settings To check whether the SD card is currently being used as the main memory or additional

Default setting The setting “Preferably, use the external SD card as main memory” is activated by default

• Click on the button to send the setting to the controller (“Write values to the de-

vice”).

The setting will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

memory, you can view the current setting on the controller:

• Click on the button to read the controller's settings (“Read values from the device”).

in PC Worx Engineer.

If you do not change this setting, the following is valid: – If the SD card has already been inserted before the controller is started (see also

Figure 7-6 on page 83), the SD card is used as the main memory. All application-specific data is stored on the SD card.

– If the SD card is not inserted until after the controller is started up (see also Figure 7-6

on page 83), the SD card is used as additional memory (see Section 7.5.2). All application-specific data is stored on the internal parameterization memory of the controller.

7.5.2 Additional memory

WARNING: Explosion hazard

In potentially explosive areas, the SD card must not be used as additional memory. Use the SD card as main memory only. Do not insert or remove the SD card during operation.

If the SD card is used as the additional memory, all application-specific data is stored on the internal parameterization memory of the controller.

If you are using an SD card with a license key, the license is still used.

NOTE: Function blocks are no longer executed under certain circumstances

If an SD card with license keys for function block libraries (SD FLASH XXX APPLIC A) is removed from the controller for more than 60 minutes, function blocks that require a license can no longer be executed under certain circumstances. If the SD card is removed and reinserted into the controller within 60 minutes, all function blocks continue to be executed.

• Never remove an SD card with license keys for function block libraries from the controller for more than 60 minutes.

107709_en_00 PHOENIX CONTACT 85 / 140

Page 86

AXC F 1050

Use as additional memory The SD card is used as additional memory (see also Figure 7-6 on page 83) if:

– The SD card is inserted after starting up the controller

– You have selected the “Use SD card as additional memory” setting in

PC Worx Engineer.

Inserting/removing the SD card

If you are using the SD card as additional memory, you can insert or remove the SD card before startup and while the controller is operating.

NOTE: Potential data loss

If you remove the SD card while read and/or write access to the SD card is active, this may result in a loss of data.

• Only remove the SD card when it is not being accessed.

PC Worx setting To use the SD card as additional memory, make the following setting in PC Worx Engineer:

• Double-click on the “MONA” node in the “PLANT” area.

The “Online Parameters” editor opens.

• Select the “External SD card” view.

86 / 140

Figure 7-8 “Online Parameters” editor, “External SD card” view, Use SD card as addi-

tional memory

• In the “Use of external SD card” drop-down list, select the setting “Use SD card as additional memory”.

PHOENIX CONTACT 107709_en_00

Page 87

Additional functions in PC Worx Engineer

Transferring the setting to the controller

• Click on the button to send the setting to the controller (“Write values to the de-

vice”).

The setting will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

Reading settings To check whether the SD card is currently being used as the main memory or additional

memory, you can view the current setting on the controller:

• Click on the button to read the controller's settings (“Read values from the device”).

107709_en_00 PHOENIX CONTACT 87 / 140

Page 88

AXC F 1050

7.6 Activating or deactivating the MRP client function

Contact Phoenix Contact if you would like to use this function.

The controller supports the Media Redundancy Protocol (MRP) and can be used as an MRP client.

In the “MRP” view, you can switch the MRP client function on, off, or read the controller's current setting.

• Select the “MRP” view.

Figure 7-9 “Online Parameters” editor, “MRP” view

Activating or deactivating the MRP client function

Transferring the setting to the controller

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

88 / 140

PHOENIX CONTACT 107709_en_00

• To switch the MRP client function on, select “Activated” in the “MRP function“ drop-

down list.

• To switch the MRP client function off, select “Deactivated” in the “MRP function“ dropdown list (default setting).

• Click on the button to send the setting to the controller (“Write values to the de- vice”).

The setting will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

Page 89

Additional functions in PC Worx Engineer

7.7 Activating or deactivating the SNMP server

function

The controller can be used as an SNMP server.

In the “SNMP server” view, you can switch the SNMP server function on or off, enter the port, or read the controller's current setting.

• Select the “SNMP server” view.

Figure 7-10 “Online Parameters” editor, “SNMP server” view

Activating or deactivating the SNMP server function

Entering the port If you have activated the SNMP server function, you can input the port number you want to

Transferring the setting to the controller

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

107709_en_00 PHOENIX CONTACT 89 / 140

• To switch the SNMP server function on, select “Activated” in the “SNMP server status“

drop-down list.

• To switch the SNMP server function off, select “Deactivated” in the “SNMP server status“ drop-down list (default setting).

use.

• Enter the desired port within the range from 0 ... 65535 in the input field “Port” (default setting: 161).

• Click on the button to send the setting to the controller (“Write values to the de- vice”).

The setting will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

Page 90

AXC F 1050

7.8 Activating or deactivating the FTP server function

The controller can be used as an FTP server.

In the “FTP server” view, you can switch the FTP server function on or off, enter a user name and password for accessing the FTP server, or read the controller's current setting.

• Select the “FTP server” view.

Activating or deactivating the FTP server function

Entering a user name and password

90 / 140

PHOENIX CONTACT 107709_en_00

Figure 7-11 “Online Parameters” editor, “FTP server” view

• To switch the FTP server function on, select “Activated” in the “FTP server status” dropdown list.

• To switch the FTP server function off, select “Deactivated” in the “FTP server status” drop-down list (default setting).

If you have activated the FTP server function, you can enter a user name and password for accessing the FTP server.

• Enter a user name for accessing the FTP server in the “Root user” input field.

• Enter a password for accessing the FTP server in the “Root password” input field.

Page 91

Additional functions in PC Worx Engineer

Transferring the settings to the controller

• Click on the button to send the settings to the controller (“Write values to the de-

vice”).

The settings will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

107709_en_00 PHOENIX CONTACT 91 / 140

Page 92

AXC F 1050

7.9 Activating or deactivating the SNTP client function

You can synchronize the time and date information for the controller's real-time clock to an SNTP server.

If you set the real-time clock time and date information manually earlier (see Section 7.3) and are now activating the SNTP client function, the previous time and date information will be overwritten.

In the “SNTP client” view, you can switch the SNTP client function on or off, enter an update cycle for the synchronization and the SNTP server's IP address, or read the controller's current setting.

• Select the “SNTP client” view.

Activating or deactivating the SNTP client function

92 / 140

PHOENIX CONTACT 107709_en_00

Figure 7-12 “Online Parameters” editor, “SNTP client” view

• To switch the SNTP client function on, select “Activated” in the “SNTP client status“ drop-down list.

• To switch the SNTP client function off, select “Deactivated” in the “SNTP client status“ drop-down list (default setting).

Page 93

Additional functions in PC Worx Engineer

Entering the synchronization cycle and IP address

If you have activated the SNTP client function, you can input a synchronization cycle and the IP address for the SNTP server.

• Enter a length of time (0 s ... 65535 s) in the “Update cycle” input field. Each time this period elapses, the time and date information will be resynchronized with the SNTP server.

• Enter the IP address of the SNTP server in the “Server IP address” input field.

Transferring the settings to the controller

• Click on the button to send the settings to the controller (“Write values to the de-

vice”).

The settings will not take effect until the controller has been rebooted.

• To reboot the controller, click on the button (“Reboot the controller (Ctrl+Alt+F6)”).

Reading settings • Click on the button to read the controller's settings (“Read values from the device”).

107709_en_00 PHOENIX CONTACT 93 / 140

Page 94

AXC F 1050

8 System variables and status information

8.1 General information

This section describes the system variables that are available for the controller.

The controller has a register set that is used for diagnostics and easy control of the controller and the Axioline F local bus.

The diagnostic data is stored in the diagnostic status register and the diagnostic parameter register. These registers are available to the application program as system variables (system flags, global variables).

8.2 Diagnostic status register

Information on the operating state of the Axioline F local bus is stored in the diagnostic status register. A specific Axioline F local bus state is assigned to each bit in the diagnostic status register.

The following system variables can be used to read the diagnostic status register information.

Table 8-1 System variables of the diagnostic status register

System variable Type Description

AXIO_DIAG_STATUS_REG_HI BYTE Diagnostic status register (high byte) AXIO_DIAG_STATUS_REG_LOW BYTE Diagnostic status register (low byte) AXIO_DIAG_STATUS_REG_PF BOOL I/O error AXIO_DIAG_STATUS_REG_PW BOOL I/O warning AXIO_DIAG_STATUS_REG_BUS BOOL Bus error AXIO_DIAG_STATUS_REG_RUN BOOL Data transmission is active AXIO_DIAG_STATUS_REG_ACT BOOL Selected configuration is ready for operation AXIO_DIAG_STATUS_REG_RDY BOOL The Axioline F local bus is ready for operation AXIO_DIAG_STATUS_REG_SYSFAIL BOOL The Axioline F local bus switches to the SYSFAIL state

when the controller is in the STOP state or there is no program present on it.

94 / 140

PHOENIX CONTACT 107709_en_00

Page 95

System variables and status information

8.3 Diagnostic parameter register

The diagnostic parameter register provides additional information on the error indicated in the diagnostic status register. The error code is stored in the diagnostic parameter register and the error location in the extended diagnostic parameter register. The error location is stored as a slot number. This starts at 1 and corresponds to the sequential number of the Axioline F modules that are installed one after another.

Exception: If an interface error cannot be located, the value 128 is displayed in the diagnostic parameter register (bit 7 is set).

The diagnostic parameter register is rewritten whenever a malfunction occurs. If a malfunction has not been detected, the diagnostic parameter register contains the value 0.

Table 8-2 System variables of the diagnostic parameter register

System variable Type Description

AXIO_DIAG_PARAM_REG_HI BYTE Diagnostic parameter register (high byte) AXIO_DIAG_PARAM_REG_LOW BYTE Diagnostic parameter register (low byte) AXIO_DIAG_PARAM_2_REG_HI BYTE Extended diagnostic parameter register (high byte) AXIO_DIAG_PARAM_2_REG_LOW BYTE Extended diagnostic parameter register (low byte)

107709_en_00 PHOENIX CONTACT 95 / 140

Page 96

AXC F 1050

8.4 PROFINET system variables

Table 8-3 lists the PROFINET system variables of the integrated PROFINET controller functions.

Table 8-3 PROFINET system variables (PROFINET controller functions)

System variable Type Description

PNIO_SYSTEM_BF BOOL No connection to a configured PROFINET device

An error has occurred in the PROFINET network, i.e. a connection could not be established to at least one configured PROFINET device. This value is not set if the “Control BF” parameter was set to FALSE for a PROFINET device. The PROFINET device has therefore been excluded from connection monitoring.

PNIO_SYSTEM_SF BOOL Diagnostic alarm on a configured PROFINET device

At least one PROFINET device is indicating a system error (diagnostic alarm or maintenance alarm). The error priority can be taken from the PNIO_DIAG_AVAILABLE, PNIO_MAINTENANCE_DEMANDED, and PNIO_MAINTENANCE_REQUIRED variables.

PNIO_MAINTENANCE_DEMANDED BOOL Maintenance demand

At least one PROFINET device is indicating the “maintenance demand” alarm (high-priority maintenance alarm) with an active connection. The PROFINET device can be identified using the RALRM diagnostic block.

PNIO_MAINTENANCE_REQUIRED BOOL Maintenance required

At least one PROFINET device is indicating the “maintenance required” alarm (low-priority maintenance alarm) with an active connection. The PROFINET device can be identified using the RALRM diagnostic block.

PNIO_FORCE_FAILSAFE BOOL All PROFINET devices are prompted to set their configured

substitute values. PNIO_CONFIG_STATUS WORD Configuration status of the PROFINET controller PNIO_CONFIG_STATUS_READY BOOL This variable is set if the PROFINET controller was able to ini-

tialize correctly. No desired configuration has been loaded by

PC Worx Engineer yet. PNIO_CONFIG_STATUS_ACTIVE BOOL This variable is set if the desired configuration for the

PROFINET controller has been loaded.

In this state, the PROFINET controller attempts to establish a

connection cyclically to all devices in the desired configura-

tion (under the PROFINET icon). PNIO_CONFIG_STATUS_CFG_FAULT BOOL The desired PROFINET controller configuration has not been

applied due to a serious error.

In this case, please contact Phoenix Contact.

96 / 140

PHOENIX CONTACT 107709_en_00

Page 97

System variables and status information

Table 8-4 lists the PROFINET system variables for the integrated PROFINET device functions.

Table 8-4 PROFINET system variables (PROFINET device functions)

System variable Type Description

PND_S1_PLC_RUN BOOL Status of the superordinate PROFINET controller

Information on whether the superordinate PROFINET controller is active. The value is TRUE if the superordinate PROFINET controller is in the RUN state (program is being processed). The display only applies when there is an existing PROFINET connection (PND_S1_VALID_DATA_CYCLE).

PND_S1_VALID_DATA_CYCLE BOOL The superordinate PROFINET controller has established

the connection

Information on whether a connection exists and cyclic data is being exchanged between the PROFINET controller and PROFINET device (AXC F 1050) and whether the last frame received contained valid data.

PND_S1_OUTPUT_STATUS_GOOD BOOL IOP status of the superordinate PROFINET controller

Information on whether the input process data (PND_S1_INPUTS) was received by the PROFINET device with the “valid” status. The value is TRUE if the output data of the superordinate PROFINET controller is valid

(provider status). PND_S1_INPUT_STATUS_GOOD BOOL IOC status of the superordinate PROFINET controller PND_S1_DATA_LENGTH WORD Process data length that was configured for the

PROFINET device PND_S1_OUTPUTS PND_IO_256 Output process data

Memory area for output process data that the PROFINET

device sends to the superordinate PROFINET controller PND_S1_INPUTS PND_IO_256 Input process data

Memory area for input process data that the PROFINET

device receives from the superordinate PROFINET con-

troller PND_IO_DRIVEN_BY_PLC INT Applicative system redundancy

Specifies the superordinate PROFINET controller from

which the data in the PROFINET device originates.

No PROFINET controller

PROFINET controller A

PROFINET controller B

107709_en_00 PHOENIX CONTACT 97 / 140

Page 98

AXC F 1050

Table 8-4 PROFINET system variables (PROFINET device functions)

System variable Type Description

PND_RESET_FACTORY_SETTINGS WORD Reset to factory settings / default

The following bits indicate which data/parameters is/are

reset:

Bit 0: Reserved

Bit 1: Not supported; application data

(Reset_APPLICATION_DATA)

Bit 2: Supported; communication parameter

(RESET_COMMUNICATION_PARAMETER)

Bit 3: Not supported; configuration parameter

(RESET_ENGINEERING_PARAMETER)

Bit 4: Not supported; all saved parameters

(RESET_ALL_PARAMETER)

Bits

Reserved

5 ... 7:

Bit 8: Not supported; all saved parameters in the

PROFINET controller/device (RESET_DEVICE)

Bit 9: Not supported; firmware

(RESET_FIRMWARE)

98 / 140

PHOENIX CONTACT 107709_en_00

Page 99

System variables and status information

8.5 IEC-61131 runtime system

There is a separate group of system variables for the IEC 61131 runtime system.

Table 8-5 System variables for the IEC 61131 runtime system

System variable Type Meaning

PLCMODE_ON BOOL PLC status ON:

The runtime system on the controller is operational.

PLCMODE_LOADING BOOL PLC status LOADING:

The application program is loading.

PLCMODE_RUN BOOL PLC status RUN:

The application program is running.

PLCMODE_STOP BOOL PLC status STOP:

The application program is currently not running.

PLCMODE_HALT BOOL PLC status HALT:

The application program was stopped at an unspecified point.

PLCDEBUG_BPSET BOOL Breakpoint set:

At least one breakpoint has been set in the application program.

PLCDEBUG_FORCE BOOL Variable(s) forced:

At least one variable is being continuously overwritten (forced).

PLCDEBUG_POWERFLOW BOOL In “Powerflow” mode, you can see which parts of your applica-

tion program are being processed.

0: Powerflow disabled/off 1: Powerflow enabled/on

PLC_TICKS_PER_SEC INT System ticks per second:

The number of pulses the system clock of the controller delivers per second.

PLC_SYS_TICK_CNT DINT Number of system ticks:

The total number of pulses delivered by the system clock since

the last startup. PLC_TASK_AVAILABLE INT Number of available PLC tasks PLC_SYSTASK_AVAILABLE INT Number of available system tasks PLC_MAX_ERRORS DINT Maximum number of “errors, warnings, and logging events”.

If the maximum number is reached, the controller is stopped. PLC_ERRORS DINT Number of “errors, warnings, and logging events” currently en-

tered. PLC_TASK_DEFINED INT Number of tasks used PLC_TASK_1 RECORD Information regarding task 1 ::: PLC_TASK_8 RECORD Information regarding task 8 CLOCK_PULSE_1S BOOL 1 s clock pulse CLOCK_PULSE_2S BOOL 2 s clock pulse CLOCK_PULSE_5S BOOL 5 s clock pulse

107709_en_00 PHOENIX CONTACT 99 / 140

Page 100

AXC F 1050

Table 8-5 System variables for the IEC 61131 runtime system

System variable Type Meaning

CLOCK_PULSE_10S BOOL 10 s clock pulse DISABLE_CLOCK_PULSE BOOL Deactivates the refresh function for the clock pulse variables

If this variable is set, the CLOCK_PULSE_xS clock pulse vari-

ables are no longer refreshed. This reduces the processor ca-

pacity of the controller.

FALSE: The CLOCK_PULSE_xS variables are refreshed

(default setting).

TRUE: The CLOCK_PULSE_xS variables are not refreshed. LICENSE DWORD License information

100 / 140

PHOENIX CONTACT 107709_en_00

Phoenix Contact AXC F 1050 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of contents

1 For your safety

1.1 Identification of warning notes

1.2 Qualification of users

1.3 Field of application of the product

1.3.1 Intended use

1.3.2 Modifications

1.4 Safety notes

1.5 Notes on using the AXC F 1050 controller in potentially explosive areas

2 Transport and unpacking

2.1 Transport

2.2 Storage

2.3 Checking the delivery

2.4 Unpacking

3 Description of the AXC F 1050

3.1 Hardware and software requirements

3.2 General description of the controller

3.3 Possible fields of application of the controller

3.3.1 Controller as a decentral controller for an Axioline F station

3.3.2 The AXC F 1050 as a PROFINET controller in a PROFINET network

3.3.4 System redundancy with the AXC F 1050

3.4 Connection and operating elements

3.5 Diagnostics and status indicators

3.6 Mode selector switch

3.7 Reset button (concealed)

3.8 Parameterization memory

3.9 Internal basic circuit diagram

3.10 Interfaces

3.10.1 Ethernet

3.10.2 Service interface (Micro-USB type B)

3.11 Supply plug

3.12 Bus base module

4 Mounting hardware

4.1 Safety notes

4.2 Basics

4.3 Structure of an Axioline F station

4.4 Mounting the controller

4.5 Inserting the SD card

5 Connecting and wiring hardware

5.1 Safety notes

5.2 Supply voltage

5.2.1 Sizing of the power supply

5.2.2 Connecting the power supply

5.3 Connecting Ethernet

6 Starting up with PC Worx Engineer

6.1 Installing PC Worx Engineer

6.2 PC Worx Engineer licenses

6.3 User interface

6.4 Creating a new project

6.5 Configuring the IP settings

6.5.1 Setting the IP address range

6.5.2 Setting the IP address

6.6 Using the simulation function

6.7 Connecting to the controller

6.8 Configuring Axioline F modules

6.9 Configuring PROFINET devices

6.9.1 Adding PROFINET devices

6.9.2 Assigning online devices

6.9.3 Adding I/O modules

6.10 Programming in accordance with IEC 61131-3

6.10.1 Opening and creating the POU, creating variables

6.10.2 Creating a program

6.10.3 Creating functions and function blocks

6.11 Instantiating programs

6.12 Assigning process data

6.13 Transfer the project to the controller

6.14 Creating an HMI application

7 Additional functions in PC Worx Engineer

7.3 Setting or reading the real-time clock

7.5.1 Main memory

7.5.2 Additional memory

7.6 Activating or deactivating the MRP client function

Activating or deactivating the SNMP server function

7.8 Activating or deactivating the FTP server function

7.9 Activating or deactivating the SNTP client function

8 System variables and status information