3Description of the AXC F 2152

3.1General description of the controller

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

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

107708A001.png

 

Figure 3-1 Components of the controller

Axioline F station

An Axioline F station is automatically 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 can be configured and programmed in accordance with IEC 61131 using the PC Worx Engineer automation software.
In addition or as an alternative to the programming languages specified in IEC 61131-3, you can also use the C++ or MATLAB® Simulink® programming languages. The individual programs or program parts can be programmed in any development environment (e.g. Eclipse, Microsoft® Visual Studio®, etc.). These programs or program parts must then be imported into PC Worx Engineer as a library.

Integrated Ethernet interfaces

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

PROFINET controller/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 or PROFINET device, depending on the configuration.

inset_54.png 

 

For additional information on how to integrate the AXC F 2152 as a PROFINET controller or device, please refer to the PC Worx Engineer online help.

Axioline F local bus

There is an interface to the Axioline F local bus 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.

inset_19.png 

 

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 PC Worx Engineer online help 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 are available for downloading at phoenixcontact.net/product/2404267.

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, the controller can be operated using an SD card. The SD card is optional and not required to operate the controller.

inset_20.png 

 

The SD card is not supplied as standard with the controller.

Only use an SD card provided by Phoenix Contact (see Ordering data).

   

inset_14.png 

 

NOTE: Damage to the SD card after formatting

The SD card is already formatted (ext4 format) and is intended for use with Phoenix Contact controllers from the PLCnext Control product range. 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.

Ensure that the SD card is not formatted.

 

Visualization

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

Real-time clock

In the event of a supply voltage failure, the real-time clock integrated into the controller is buffered, see Technical data.

3.2Licensing information on open source software

The AXC F 2152 controller works with a Linux operating system.
License information on the individual Linux packages are to be found in the file system of the AXC F 2152 under the path /usr/share/common-licenses

inset_40.png 

 

Information on the directory structure of the file system is to be found in Section 3.5.

Alternatively, you can also call up the license information via the AXC F 2152 web-based management system, see Section 9.2.

Notes on LGPL software libraries

All open-source software used in the product is subject to the respective license terms that are not affected by the Phoenix Contact Software License Terms (SLT) for the product. In particular, the license holder can change the respective open source software in accordance with the applicable license terms. If the license holder wishes to change an LGPL software library contained in this product, reverse engineering is permitted for debugging such modifications.

Notes on OpenSSL

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

3.3Requesting source code

This AXC F 2152 contains software components that are licensed by the rights holder as free software or open source software under the GNU General Public License.

You can request the source code of these software components in the form of a CD or DVD-ROM for a processing fee of € 50 within three years after delivery of the AXC F 2152.
To do so, contact the Phoenix Contact After Sales Service in writing at the address

PHOENIX CONTACT GmbH & Co. KG
After Sales Service
Flachsmarktstraße 8
32825 Blomberg
GERMANY

Subject: Source code AXC F 2152

3.4Hardware and software requirements

Hardware/software

Description

Controller

AXC F 2152

SD card

For ordering data, see Ordering data

Ethernet cable

Ethernet cable for connecting the controller to a PC

PC Worx Engineer

≥7.2

3.5Directory structure of the file system

The AXC F 2152 controller works with a Linux operating system. You can access the controller via SFTP or via SSH and view the directories and files on the file system (on the internal parameterization memory and on the optional SD card) and modify them as necessary.

Directories and files that are provided by Phoenix Contact (also through firmware updates) are stored on the internal parameterization memory of the AXC F 2152.

If you make changes to the directories or files, the Linux operating system generates an overlay filesystem. The directory structure depends on whether you operate the controller with or without an SD card:

Operation without an SD card

If you make changes to the directories or files on the internal parameterization memory, the Linux operating system generates an overlay filesystem here.

Operation with an SD card

If you operate the controller with an SD card, the overlay filesystem is generated on the SD card.
Settings that you have configured yourself (e.g. network configuration, project bus configuration, PC Worx Engineer project, etc.) are also saved to the SD card.

Table 3-1 Directory structure on the internal parameterization memory and the SD card

Directory

Description

/usr/local/lib

Directory for storing additional open source libraries that are used by customer-specific C++ programs.

Detailed information on programming the AXC F 2152 using C++ is to be found in the PLCnext community at
plcnext-community.net.

/usr/share/common-licenses

License information on the individual Linux packages of the AXC F 2152

/opt/plcnext

Home directory of the Linux user “admin” and working di­rectory of the device firmware

Files written by the application program are stored in this directory if the specified file name does not contain a memory path.

/opt/plcnext/logs

Log files of the device firmware

/opt/plcnext/projects/PCWE

Directory for storing PC Worx Engineer projects

All files and subdirectories in this directory are managed exclusively by PC Worx Engineer.

Do not make any changes to this directory.

/opt/plcnext/certificates/https

Directory for storing HTTPS certificates

For detailed information on the exchange of HTTPS certif­icates, please refer to Replacing HTTPS certificate.

3.6Using SFTP to access the file system

The file system (on the internal parameterization memory and on the SD card of the AXC F 2152) is accessed via the SFTP protocol. SFTP client software (e.g. WinSCP) is required for this.

Access to the file system via SFTP requires authentication with a user name and password.

inset_27.png 

 

Please note:

Authentication via a user name and password is always required for SFTP access and cannot be deactivated.

Only users with administrator rights can access the file system.

You can create additional users with administrator rights in the web-based management of the AXC F 2152 via the User Manager, see Section 9.5.2.1.

 

The following access data is set by default with administrator rights:

User name: admin
Password: Printed on the controller (see Figure 3-2).

107708A002.png

 

Figure 3-2Administrator password on the controller

3.7Firewall

inset_22.png 

 

The firewall of the AXC F 2152 is deactivated by default.

Recommended:

Activate the firewall.

Please note:

If you use the AXC F 2152 as a PROFINET controller, you must authorize all incoming connections via all UDP ports if the firewall is activated. Otherwise, establishing a connection to certain PROFINET devices is not possible.

The firewall of the AXC F 2152 is based on internal Linux mechanisms (network filters) and is configured in the shell using nftables. Access is via SSH (Secure Shell).

Access via SSH requires authentication with a user name and password.

inset_52.png 

 

Please note:

Authentication with user name and password is always required for SSH access and cannot be deactivated.

Administrator rights are required for SSH access.

You can create additional users with administrator rights in the web-based management of the AXC F 2152 via the User Manager, see Section 9.5.2.1.

 

The following access data is set by default with administrator rights:

User name: admin
Password: Printed on the controller (see position 1 in the Administrator password on the controller).

You can control the firewall with the following shell commands:

Table 3-2 Shell commands for controlling the firewall

Shell command

Description

sudo /etc/init.d/firewall start

Temporarily activates firewall

This setting is no longer active after a re­start.

sudo /etc/init.d/firewall stop

Temporarily deactivates firewall

This setting is no longer active after a re­start.

sudo /etc/init.d/firewall activate

Permanently activates firewall

The firewall remains activated even after a restart of the AXC F 2152.

sudo /etc/init.d/firewall deactivate

Permanently deactivates firewall

The firewall remains deactivated even after a restart of the AXC F 2152.

The following controller firewall rules are stored in the “plcnext-filter” file in the /etc/nftables upon delivery:

Table 3-3 Controller firewall rules upon delivery

Permitted packets/connections

Blocked packets/connections

Outgoing ICMP echo requests and the cor­responding ICMP echo replies

Ping commands can be issued from the controller.

Incoming ICMP echo requests

The controller cannot be reached via a ping command.

Incoming connections via SSH
(Port 22)
(e.g. for SSH or SFTP connection)

All incoming connections via TCP ports (ex­cept for explicitly approved ports, see left column of table)

Incoming connections via HTTPS
(port 443)

Access to the web server (PC Worx Engineer HMI and WBM)

All incoming connections via UDP ports

Incoming connections via HTTP
(port 80)

The connections are diverted directly to port 443.

 

Incoming connections via TCP port 41100

Common remoting (TLS-encoded), e.g. via PC Worx Engineer

 

Incoming connections via TCP port 17725

The TCP port 17725 is the standard port for the external mode of MATLAB® Simulink®.

 

Incoming connections via TCP port 4840

Standard port for connections to the OPC UA server of the controller

 

Incoming connections via any TCP or UDP port

 

 

3.8Possible fields of application of the controller

3.8.1The AXC F 2152 as a distributed controller of an Axioline F station

The controller can be used as a decentral controller of an Axioline F station which 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 (1 A at an ambient temperature ≤55°C).

86765_1000_int.png

 

Figure 3-3 Axioline F station with AXC F 2152 controller

3.8.2The AXC F 2152 as a PROFINET controller in a PROFINET network

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

86760_1000_int.png

 

Figure 3-4 AXC F 2152 as a PROFINET controller

Key:

A  AXC F 2152 PROFINET controller

B  PROFINET device (in the example: AXC F 2152 with connected Axioline F I/O modules)

inset_21.png 

 

For detailed information on how to integrate the AXC F 2152 as a PROFINET controller in a PROFINET network, please refer to the PC Worx Engineer online help.

3.8.3The AXC F 2152 as a PROFINET device in a PROFINET network

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

86761_1000_int.png

 

Figure 3-5AXC F 2152 as a PROFINET device

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 2152 PROFINET device

inset_17.png 

 

For detailed information on how to integrate the AXC F 2152 as a PROFINET controller in a PROFINET network, please refer to the PC Worx Engineer online help.

3.9Components of the controller

3.9.1Connection and operating elements

86749_1000_int.png

 

Figure 3-6 Connection and operating elements of the controller

The controller comprises the following components:

1Bus base module

2Electronics module

3Reset button

4SD card holder

inset_15.png 

 

The SD card is optional and not supplied as standard with the controller.

Please refer to the ordering data in Ordering data.

5Diagnostics and status indicators

6Ethernet interfaces (X1, X2)

7Supply socket (socket for connecting the supply voltage (communications power UL))

3.9.2Printing

107708A003.png

 

Figure 3-7 Printing

The following information is printed on the controller:

1Order number and order designation

2MAC address

3Administrator password

4QR code

5Link to the PLCnext community

Administrator password

You need the administrator password (in combination with the “admin” user name) for initial access to

The controller file system

Certain functions in PC Worx Engineer

The PC Worx Engineer HMI (in preparation)

The web-based management function (WBM)

The AXC F 2152 OPC UA server

inset_18.png 

 

Recommended:

Only use the administrator password for initial access.

Once you have gained access successfully, change the administrator password to prevent unauthorized administrator access (see Section 9.5.2.1).

 

QR code

You can access the PLCnext community directly via the QR code.
In the PLCnext community, you will find

Information on PLCnext Technology

Information on PC Worx Engineer

Information on programming with AXC F 2152 with C++

Operating instructions

Tutorials

Example projects

FAQs

3.10Diagnostics and status indicators

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

86773_1000_int.png

 

Figure 3-8 Diagnostics and status indicators

Table 3-4 Controller diagnostics and status indicators

Desig­nation

Color

Indicates

Status

Description

PN: PROFINET controller/device function

BF-C

Red

Status of the PROFINET com­munication / com­munication errors

AXC F 2152 as a PROFINET controller

Off

The AXC F 2152 has established an active communication con­nection to each configured PROFINET device.

On

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

Flashing (1 Hz)

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

BF-D

Red

Status of the PROFINET com­munication / com­munication errors

AXC F 2152 as a PROFINET device

Off

A PROFINET controller has established an active communica­tion connection to the AXC F 2152 (PROFINET device).

On

No PROFINET communication (no link status at the Ethernet in­terfaces).

Flashing (1 Hz)

Link status present, no communication connection to the PROFINET controller.

The SF LED is not flashing.

SF

Red

Group error (PROFINET)

Off

PROFINET diagnostics not present.

On

PROFINET diagnostics present.

PLC: Controller diagnostics

RUN

Green

Controller RUN status

Off

PLCnext runtime system is not ready for operation.

Flashing (0.5 Hz)

PLCnext runtime system successfully initialized.
The controller is in the READY/STOP mode, application pro­gram is not being processed.

Flashing (2 Hz)

Controller has been reset to the default status (see Reset button (concealed)).

On

PLCnext runtime system successfully initialized and an appli­cation program is running.
The controller is in the RUN status.

FAIL

Red

Failure

On

A runtime error has occurred in the application program of the PLCnext runtime system.

Off

A runtime error has not occurred in the application program of the PLCnext runtime system.

DBG

Yellow

Debug mode (troubleshooting)

On

The PLCnext runtime system / controller is in debug mode, i.e. debug mode has been activated in PC Worx Engineer (break­point(s) set).

The status of the RUN LED is not affected.

BOOT

Red

Device firmware loading status

On

Device firmware is faulty.

Flashing (2 Hz)

Device firmware is being loaded (boot process).

Off

Device firmware running.

AXC: Axioline F diagnostics

D

Red/yel­low/green

Axioline F: Diag­nostics for local bus communica­tion

Green on

Run:
The Axioline F station is ready for operation; communication within the Axioline F station is OK.
All data is valid. A malfunction is not present.

Flashing green

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. A malfunction is not present on the device.

Yellow on

Ready:
The Axioline F station is ready for operation; no data is being exchanged.

Flashing yellow

Access from Startup+ in the I/O check mode

Flashing yellow/red

Local bus error during active I/O check

Flashing red

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

Local bus device not connected

The maximum number of local bus devices has been exceeded

Red on

Bus error in RUN status

The Axioline F station is ready for operation but has lost con­nection to at least one local bus device.

Possible causes:

Communication error

Local bus device has been removed or configured local bus device is missing

Reset at a local bus device

Serious device error at a local bus device (local bus device can no longer be reached)

Off

Power down:
Local bus device is in (power) reset

E

Yel­low/red

Error/warning

Yellow on

I/O warning at a local bus device

Red on

I/O error at a local bus device

EXT

Yellow

 

 

Currently without function

PWR: Supply voltage (communications power UL)

UL

Green

ULogic

Off

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

On

24 V communications power feed-in present.

ETH: Ethernet interfaces

 

Green

Link status

Off

Connection not established successfully

On

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

 

Yellow

Activity status

Off

Data transmission not active

On/flashing

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

inset_25.png 

 

Special case: Firmware update

During a firmware update, the RUN LED first flashes, and then stops. Upon a successful controller restart, the RUN LED lights up again permanently.

Information on firmware updates is to be found in Updating the firmware.

  

inset_55.png 

 

Special case: Unauthorized removal of the SD card during operation

If the SD card is removed during operation, all LEDs except the D and E LEDs begin to flash (1 Hz).

Information on operating the controller with an SD card is to be found in SD card (optional).

3.11Reset button (concealed)

86768_1000_int.png

 

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.

If the reset button is actuated during operation for ≥ 2 s, the controller is restarted.

The reset button can also be used to reset the controller to the default settings. Here, a distinction is made between two types of default settings:

Type 1:
All user-specific data is deleted.

Type 2:
The controller is restored to the delivery state.

Default setting type 1

When resetting the controller to factory default setting 1, all settings that you have configured are deleted. These include, for example:

The PC Worx Engineer project including all applications that have been programmed in accordance with IEC 61131-3

All applications that were programmed using high-level languages

The project bus configuration

The network configuration of the controller

Changes and extensions that you have made to the operating system or to the firmware

To restore the controller to default setting type 1, proceed as follows:

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.

The RUN and FAIL LEDs light up.

Release the reset button.

The controller is reset to default setting 1.

107708A004.png

 

Figure 3-10 Timing when resetting to default setting type 1 and LED indicators

Default setting type 2

When restoring to default setting type 2, the controller is reset to the delivery state. In doing so, all settings that you have configured are deleted.

inset_26.png 

 

Please note:

The operating system and all firmware components of the controller are reset to the delivery state.

To restore the controller to default setting type 2, proceed as follows:

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.

The RUN and FAIL LEDs light up.

Press and hold the Reset button until (approx. 30 s) until all LEDs (except LEDs E and D) light up.

Release the reset button.

The controller is reset to default setting 2.

107708A005.png

 

Figure 3-11 Timing when resetting to default setting type 2 and LED indicators

3.12Parameterization memory

The controller has an internal parameterization memory. Alternatively, a plug-in parameterization memory in the form of an SD card can be used, see Section 3.13.

The programs and configurations (e.g. controller IP address) belonging to your PC Worx Engineer project are stored in the parameterization memory. In addition, application-specific data can also be stored in the parameterization memory.

If you make changes to Linux operating system files on the internal parameterization memory, the Linux operating system generates an overlay filesystem from the changed files and directories.
If you operate the controller with an SD card, the overlay filesystem is generated on the SD card.

3.13SD card (optional)

If the internal parameterization memory is not large enough for your application, the controller can be operated using an SD card. The SD card is optional and not required to operate the controller.

If you operate the controller with an SD card, all application-specific data (e.g. the PC Worx Engineer project) is stored there. 

inset_28.png 

 

The SD card is recognized during the initialization phase of the controller. If you insert the SD card during operation, the SD card will not be recognized.

Ensure that the SD card has been inserted before switching the controller on, in order that the controller can use it.

Only insert and remove the SD card when the controller supply voltage is disconnected.
Refer to Diagnostics and status indicators for the LED blink codes in the event of unauthorized removal of the SD card during operation.

Only use an SD card provided by Phoenix Contact, see Ordering data.

  

Change: Operation without SD card  Operation with SD card

When changing from operation without SD card to operation with SD card, note the following:

If there is already an overlay filesystem on the internal parameterization memory, this will be copied to the SD card.
If there is already an overlay file system on the SD card, the controller will access this. The overlay filesystem on the internal parameterization memory will be deleted.

Furthermore, all application-specific data will be deleted from the parameterization memory. Any PC Worx Engineer projects and IP configurations stored there will no longer be available. The controller access the data that is stored on the SD card. 

inset_16.png 

 

NOTE: Data loss due to removing the SD card

If you remove the SD card during operation, data will be lost.

Do not remove the SD card during operation.

  

inset_24.png 

 

NOTE: Damage to the SD card after formatting

The SD card is already formatted (ext4 format) and is intended for use with Phoenix Contact controllers from the PLCnext Control product range. 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.

Ensure that the SD card is not formatted.

If you would like to delete the overlay filesystem from the SD card:
Ensure that you only delete the "upperdir" and "work" directories, and do not format the SD card.

 

inset_41.png 

 

The SD card is recognized during the initialization phase of the controller. If you insert the SD card during operation, the SD card will not be recognized.

Ensure that the SD card has been inserted before switching the controller on, in order that the controller can use it.

Only insert and remove the SD card when the controller supply voltage is disconnected.
Refer to Diagnostics and status indicators for the LED blink codes in the event of unauthorized removal of the SD card during operation.

Only use an SD card provided by Phoenix Contact, see Ordering data.

   

inset_53.png 

 

Please note:

The SD card can be read with a conventional SD card reader at any time. Sensitive data on the SD card can be read if you do not physically protect the SD card against unauthorized access.

Ensure that unauthorized persons do not have access to the SD card.

    

Change: Operation with SD card  Operation without SD card

If you want to switch from operation with SD card to operation without SD card, please note the following:

If there is an overlay filesystem on the SD card, there will be an empty overlay filesystem on the internal parameterization memory after removing the SD card and rebooting the controller. The content of the overlay filesystem on the SD card will not be transferred over to the internal parameterization memory of the controller.

The application data on the SD card will not be transferred over to the internal parameterization memory of the controller either.

3.14Internal basic circuit diagram

86770_1000_int.png

 

Figure 3-12 Internal basic circuit diagram

Key:

Mikroprozessor.png 

Microprocessor

 

Uebertrager.png 

Transmitter

USB_Schnittstelle.png 

Service interface (USB type C)

 

LED.png 

LED

Reset_Taster.png 

Reset button

 

RTC.png 

Real-time clock

RJ45_Buchse_inkl_LED.png 

RJ45 interface

 

Netzteil.png 

Power supply unit

FE_Funktionserdungsanschluss.png 

Functional ground connection

 

ETH_Switch.png 

Ethernet switch

SD_Kartenhalter.png 

SD card holder

 

Axioline_F_Lokalbus.png 

Axioline F local bus

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

Farben_Logik.png 

Logic

 

 

 

Farben_ETH.png 

Ethernet interface

 

 

 

Farben_FE.png 

Functional ground

 

 

 

3.15Communication paths

The following communication paths are available on the controller (see Figure 3-13):

(1)

2 x Ethernet

X1/X2: 10/100 BASE-T(X) (switched internally)

 

 

 

(2)

Service interface (USB type C)

Currently without function

  

86767_1000_int.png

 

Figure 3-13 Communication paths: (1) Ethernet, (2) service interface (USB type C)

3.15.1Ethernet

Two Ethernet interfaces (X1/X2) are available on the controller for connecting the Ethernet network.

The Ethernet network is connected via RJ45 sockets.

inset_56.png 

 

Use an Ethernet cable that at least complies with CAT5 of IEEE 802.3.

Observe the bending radii of the Ethernet cables used.

The contact assignment of the interface is as follows:

42679_1000_int.png

 

 

Pin

Signal

Indicates

 

1

T+

Transmit data +

 

2

T-

Transmit data -

 

3

R+

Receive data +

 

4

 

5

 

6

R-

Receive data -

 

7

 

8

Figure 3-14 Ethernet interface and pin assignment

inset_23.png 

 

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

3.16Supply plug

54891_1000_int.png

 

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

Terminal point assignment

Table 3-5Terminal point assignment of the supply plug

Terminal point

Color

Assignment

a1, a2

Red

24 V DC (UL)

b1, b2

Blue

GND

Key:

UL

Communications power feed-in (internally bridged)

GND

Supply voltage reference potential (internally bridged)

3.17Bus 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.

8482A010.png

 

Figure 3-16 Structure of the controller bus base module

1Bus base module

2Connection of the local bus to the controller (socket)

3Connection to the following bus base module (socket)