Characteristics. Schneider Electric Software Communication Application-Specific Functions, Micro/Junior/Pro, 4.5

PDF

Dokument

Annonce

Fipway Communication: General

1.2 Characteristics

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the characteristics and constraints of using Fipway communication.

This section contains the following topics:

Topic

Hardware compatibility

Software compatibility

Performance

Operating mode

Page

35011050 01 July 2006

Fipway Communication: General

Hardware compatibility

General

Availability

Capacity

The binary output of the network is 1 Mbits/s.

The length of a segment depends on the type of branching. The maximum length is

1000 meters without a repeater.

When using repeaters (optic or electric), the maximum length between the two furthest stations depends on the number of repeaters which must be crossed.

The maximum length in km is calculated with the following formula:

L = 22 - (0,5 * R) where R is the number of repeaters crossed by the FIP data between the two stations.

The FIPIO bus is connected to the Hirschmann optic transmitters, with the

TSX FPP 200 PCMCIA card.

This type of communication is available for these PLCs: z

Premium via the intermediary of: z z z the TSX FPP 20 PCMCIA card, the TSX FPP 200 PCMCIA card.

Micro accepts the PCMCIA cards described below (TSX 37-21/22 PLCs).

A FIPWAY network segment is used to connect 36 devices. The devices for a

FIPWAY network can be: z z stations with the constraint of a maximum of 32 stations per segment, repeaters with the constraint of a maximum of 32 repeaters per segment,

On all the segments, a maximum of 64 stations can be connected to the network.

35011050 01 July 2006

Fipway Communication: General

Software compatibility

Message handling

Common words

Shared table

The maximum frame size depends on the type of transaction: z

For a message, the maximum frame is 128 bytes.

For a telegram, the maximum frame is 16 bytes.

Equally, the PCMCIA cards can process: 8 communication functions simultaneously

(8 in receive and 8 in send mode).

z for messages, 8 communication functions simultaneously (8 in send and 8 in receive mode).

z for telegrams, one single communication function (one in send and one in receive mode).

The common words service is supported by the stations at addresses between

0 and 31.

This database is made up of a maximum of 128 words for all the stations.

Each station can produce a maximum of between 0 and 4 common words and consume the other common words on the network.

The shared table service is supported by the stations at addresses between

0 and 31.

This database is made up of a maximum of 128 words for all the stations.

Each station can produce a maximum of between 1 and 32 words (defined in configuration mode) and consume the other words on the network.

35011050 01 July 2006

Fipway Communication: General

Performance

Transaction time The following table gives the transaction time between two stations:

Sending station Cyclic

Periodic 50 ms

Receiving station

Cyclic

50 ms

120 ms

Periodic 50 ms

160 ms

The telegram exchange time between two stations is 21 ms.

35011050 01 July 2006

Fipway Communication: General

Operating mode

Introduction

General chart

The following chart describes the operating modes of the TSX FPP 20 card.

The operating mode is as follows:

Module stopped

Module off

Power up

Operation

Module configured

Reset

Communication function

Module in self-test phase

Module not configured Self-tests OK

Configuration z z z z

After power-up the module self-tests. During this phase the LED indicators flash.

If there is no configuration, the card operates in message handling mode, and it can receive a PL7 configuration.

If there is a PL7 application in the PLC, the configuration of the application is transmitted to the module and the module starts up.

In case of power outage, the PLC processor performs a warm restart. The module then re-launches its self-test procedure.

35011050 01 July 2006

Configuring Fipway communication

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Configuration process during set-up of Fipway communication.

This chapter contains the following topics:

Topic

How to access the FIPWAY configuration screen

FIPWAY configuration screen

FIPWAY parameters linked to the telegrams and to the physical layer

FIPWAY parameters linked to the common data

Example of configuration of shared table service

Page

35011050 01 July 2006

Configuration

How to access the FIPWAY configuration screen

Introduction

How to access the link

This operation describes how to access the configuration parameters of the

FIPWAY link via the intermediary of the PCMCIA cards for Premium PLCs.

The following table shows the procedure for accessing the FIPWAY link:

Step

Action

Access the communication channel configuration screen.

Select the communication channel from the drop-down menu CHANNEL 1

Example

CHANNEL 0

CHANNEL 1

(No PCMCIA submodule)

(Link not configured) MAST

3 Select one of the following PCMCIA cards from the drop-down menu: z TSX FPP 20 FIPWAY PCMCIA CARD z TSX FPP 200 FIPWAY PCMCIA CARD

Example

CHANNEL 1

CHANNEL 1 (No PCMCIA submodule)

(Link not configured)

TSX SCP 114 PCMCIA CARD RS485 MP

TSX FPP 20 PCMCIA FIPWAY CARD

TSX FPP 200 PCMCIA FIPWAY CARD

TSX FPP 10 PCMCIA FIPIO CARD

TSX MBP 100 PCMCIA MODBUS+ CARD

TSX MDM 10 PCMCIA MODEM CARD

35011050 01 July 2006

Configuration

FIPWAY configuration screen

Introduction

Illustration

This screen, split into two zones, is used to declare the communication channel and to configure the necessary parameters for a FIPWAY link.

The screen dedicated to FIPWAY communication looks like this:

TSX 57352 [RACK 0 POSITION 0]

Configuration

Designation: PROCESSOR TSX P 57352

CHANNEL 1

FIPWAY

TSX FPP 20 PCMCIA FIPWAY CARD

MAST

Telegram Management

Event processing 63

Physical layer

FIP

Common Data

None

Common words:

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

Elements and functions

This table describes the different zones that make up the configuration screen:

Address Zone

1 common

2 specific

Function

See (Communication applications Volume 1 - Overwiew of configuration screen).

is used to select or complete the parameters of a FIPWAY link.

It is split into three types of information: z Telegram management parameters, z z the parameters for the physical layer, the parameters for the common data.

35011050 01 July 2006

Configuration

FIPWAY parameters linked to the telegrams and to the physical layer

Introduction

Telegram window

Once the communication channel has been configured, complete the parameters dedicated to the telegrams and to the physical layer.

They are split into two windows: z the Telegram window, z the Physical layer window.

The window looks like this:

Telegram Management

Event processing 63

It is used to complete: z

Telegram management : if the box is checked, the card is used to manage the z telegrams (default setting).

Event processing : this option is accessible only if telegram management has been activated. This option is used to manage the telegrams via an event task. If the box is checked, you must complete the number of the task where the telegrams will be processed.

The possible values are: z z z between 0 and 15 for Micro PLCs, between 0 and 31 for Premium PLCs of type TSX 57-10, between 0 and 63 for Premium PLCs of type TSX 57-20 and higher.

Note: If there is a PCMCIA in the module TSX SCY 21600/21601, telegram management is obligatory.

Physical layer window

The window looks like this:

Physical layer

FIP

It is used to select the physical layer used for the communication.

Note: Only the physical layer specific to FIP is available.

35011050 01 July 2006

Configuration

FIPWAY parameters linked to the common data

Introduction

None

Common words

The window looks like this:

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

It can be used to: z z z activate or deactivatethe exchange management of common data select the type of common data to exchange, complete the parameters necessary for this type of exchange.

Select this button if you wish to disable the management of common data in the application.

Select this button if you wish to have management of common data by common words (%NW).

When selecting this field, you must enter the local Network number to which the database is connected.

Note: The local network number corresponds to the number coded on the PCMCIA card.

Shared table Select this button if you wish to have management of common data by shared table.

When selecting this field, you must complete the following parameters: z

Table start address : this parameter shows the start of the table of internal words reserved in the PLC.

The 128 words following the start of the table will be reserved for the shared table function and are common to all stations.

Produced zone address : this parameter shows the address of the start of the zone of internal words produced by the station.

The address entered must take into account zones of internal words of the other stations. You must avoid an overlap of word zones between two stations.

Length of produced zone : this parameter shows the length (in words) of the table of internal words produced by the PLC (from 1 to 32 words).

35011050 01 July 2006

Configuration

Bridge This button is used to configure the routing function between networks.

See

Multi-network architectures, p. 289

35011050 01 July 2006

Configuration

Example of configuration of shared table service

Introduction The example shows how the stations are configured for using the shared table service.

These configurations use the example described in using shared tables.

Configuration of station 1

The example shows the configuration for station 1.

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

200

Configuration of station 2

The example shows the configuration for station 2.

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

300

310

The zone produced by the station starts at address %MW310.

The corresponding zone of %MW300 to %MW309 is reserved for the words produced by station 1.

35011050 01 July 2006

Configuration

Configuration of station 3

The example shows the configuration for station 3.

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

400

430

The zone produced by the station starts at address %MW430.

The corresponding zone of %MW400 to %MW409 is reserved for the words produced by station 1.

The corresponding zone of %MW410 to %MW429 is reserved for the words produced by station 2.

35011050 01 July 2006

Debugging Fipway communication

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Debugging process during set-up of Fipway communication.

This chapter contains the following topics:

Topic

FIPWAY debugging screen

FIPWAY debugging parameters

Requests available for the communication channel test

How to test a channel with Identification and Mirror requests

How to test a channel with requests

Page

35011050 01 July 2006

Debugging

FIPWAY debugging screen

Introduction

Illustration

This screen, split into two zones, is used to debug a FIPWAY link.

The screen dedicated to FIPWAY communication looks like this:

TSX 57352 [RACK 0 POSITION 1]

Debugging

Designation: TSX P 57352 PROCESSOR Version: 3.3

CHANNEL 1

FIPWAY

TSX FPP 20 PCMCIA FIPWAY CARD

MAST

Channel Information

Network address

Station Address

23 Bus arb.

Bridge

Common data Common Words

Channel Test

Identification

Message Errors

Messages sent and not acknowledged

Message Refused

Receive Response

Reset Counters

Counters

Reset Counters

Enter Request

Mirror

ASCII Hex.

Stations

DIAG...

Elements and functions

This table describes the different zones that make up the debugging screen:

Address Zone

1 common

2 specific

Function

See (Communication applications Volume 1 - Description of communication debugging screens).

is used to access the debugging parameters of a FIPWAY link.

It is split into three windows: z z z information on the channel, information on the message errors, the possibility of testing the communication channel.

35011050 01 July 2006

Debugging

FIPWAY debugging parameters

Introduction

Channel information

Message errors

The specific part is split into three windows: z z z the Channel information window, the Message errors window, the Channel test window.

The window looks like this:

Channel Information

Network address

Station Address

23 Bus arb.

Bridge

Common data Common Words

It shows information concerning the communication channel: z

Network address : this field indicates the network address coded on the PCMCIA card.

z z

Station address : this field indicates the station address coded on the PCMCIA card.

Common data : this field shows the type of common data selected in configuration mode.

z z

B.A.

: this field indicates if the local PCMCIA card is the bus arbiter of the FIPWAY network. In this case, the box is shaded.

Router : this field indicates if the local PCMCIA card is configured as a Bridge

(router). In this case, the box is shaded.

The window looks like this:

Message Errors

Messages sent and not acknowledged

Messages Refused

Reset Counters

This window displays the PCMCIA card error counters: z z

Messages sent and not acknowledged ,

Messages refused .

The button Reset Counters resets these counters.

35011050 01 July 2006

Debugging

Channel test The window looks like this:

Channel Test

Identification

Counters

Reset Counters

Enter Request

Mirror

Stations

Receive Response

...TSX FPP20.../...

ASCII Hex.

This window is used to test a communication channel by sending a request to one of the stations on the network.

35011050 01 July 2006

Debugging

Requests available for the communication channel test

Introduction

Test conditions

Available requests

This page describes the different possibilities for testing a communication channel from the debugging screen.

Sending a request to an unconnected station results in an error message.

The Channel Test window allows the following requests: z

Identification : prompts the Identification request to be sent to the designated slave, z z

Counters : prompts the Read error counters request to be sent to the designated station,

Reset Counters : prompts the designated station’s error counters to be reset to zero, z z

Enter request : allows a UNI-TE request, other than those provided by the command buttons, to be sent to the designated station. Selecting this function gives access to a screen that allows you to select the parameters that are specific to the request (request code must be coded in hexadecimal),

Mirror : allows a mirror request to be sent to the designated station. Selecting this function gives access to a screen that allows you to select the length of the character string to be sent (a maximum of 80 characters ). The PLC then sends this character string (ABCD….) to the destination device. The latter automatically sends the character string that was received back to the sender.

35011050 01 July 2006

Debugging

How to test a channel with Identification and Mirror requests

Introduction This page indicates the procedure for testing a communication channel by means of

Identification and Mirror requests.

How to identify a station

The following procedure is used to identify a designated station.

Step

Actions

Select the address of the station to be interrogated using the Station field.

Click on the Identification button.

Result

The response appears in the Receive Response window:

Receive Response

...TSX FPP20.../...

ASCII Hex.

35011050 01 July 2006

Debugging

How to send the

Mirror request

The following procedure is used to send the Mirror request and thus to test the routing of information between two devices.

Step

Action

Select the address of the station to be interrogated using the Station field.

Click on the Mirror button.

Result

The following window appears:

Mirror Request

Length of data to be sent

Send Cancel

Enter the length of data to be sent (maximum 80 characters).

Click on the Send button.

Result

The response appears in the Receive Response window:

Receive Response

ABCDEFGH

ASCII Hex.

The response contains: z the character string ABCDEFGH that corresponds to the length of data sent 8.

35011050 01 July 2006

Debugging

How to test a channel with requests

Introduction

How to send a request

This page indicates the procedure for testing a communication channel from the debugging screen using different requests.

The following procedure is used to send a request, other than those provided by the command buttons, to a designated station.

Step

Action

Select the address of the station to be interrogated using the Station field.

Click on the Enter Request button.

Result

The following window appears:

Enter Request

Request Code (Hexadecimal)

Data (Hexadecimal)

1234db

Send Cancel

The data sent in this example is coded on 3 bytes.

Enter the function code (coded in hexadecimal on one byte), corresponding to the request that you want to send.

Enter the data to be sent by coding all the data in hexadecimal. Enter the data continuously without any intervening spaces.

Click on the Send button.

Result

The response appears in the Receive Response window:

Receive Response

1234DB

ASCII Hex.

the response from the example has data on 3 bytes (12 43 DB).

35011050 01 July 2006

Language objects associated with

FIPWAY communication

Introduction

Aim of this section

What's in this

Chapter?

This chapter introduces the language objects linked to FIPWAY communication.

This chapter contains the following topics:

Topic

Language object for implicit exchange

Language objects in explicit exchange

Explicit exchange management and reports

Language objects associated with the configuration

Page

35011050 01 July 2006

FIPWAY language objects

Language object for implicit exchange

Introduction

Bit objects

This page describes all the language objects for implicit exchange in FIPWAY communication that can be displayed or modified by the application program.

(Communication applications Volume 1 - Default exchanges)

The table below shows the different bit objects for implicit exchange.

Object (1) Function

%Ixy.MOD.ERR Module error bit

%Ixy.i.ERR

Channel error bit

Meaning

This bit set to 1, indicates a module error (at least one of the channels has an error, for instance.

This bit set to 1, indicates a line fault.

Key

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

35011050 01 July 2006

Word objects

FIPWAY language objects

The table below shows the different word objects for implicit exchange.

Object (1)

%IWxy.i.0

%IWxy.i.1

...

%IWxy.i.5

Function

Network status

Common data refresh flags

...

Common data refresh flags z z z z z z z z

Meaning z x0 = 1: if at least one of the stations is present z z x0 = 1: the common words or the words from the shared table from station 0 are refreshed.

...

x7 = 1: the common words or the words from the shared table from station 7 are refreshed.

x8 = 1: the common words or the words from the shared table from station 0 are refreshed.

...

x15 = 1: the common words or the words from the shared table from station 7 are refreshed.

...

z z x0 = 1: the common words or the words from the shared table from station 48 are refreshed.

...

x7 = 1: the common words or the words from the shared table from station 55 are refreshed.

x8 = 1: the common words or the words from the shared table from station 56 are refreshed.

...

x15 = 1: the common words or the words from the shared table from station 63 are refreshed.

Key

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

Common words The following table describes the words of the input channels:

Object

%NW{n.s}0 to

%NW{n.s}3

Function

Common words

Meaning corresponds to the exchanged common data

35011050 01 July 2006

FIPWAY language objects

Language objects in explicit exchange

Introduction This page describes all the language objects for explicit exchange in FIPWAY communication that can be displayed or modified by the application program.

(Communication applications Volume 1 - Specified exchanges: General points)

35011050 01 July 2006

Word objects

FIPWAY language objects

The table below shows the different word objects for explicit exchange.

Object (1) Function

%MWxy.MOD.2

Module status

%MWxy.i.2

%MWxy.i.3

%MWxy.i.4

%MWxy.i.5

%MWxy.i.6

Standard channel status

Specific channel status

Error counters

Network/station address z z z z z z z z

Meaning x0 = 1: defective module x1 = 1: functional error (error between the processor and the module, adjustment or configuration error, etc.) x2 = 1: terminal block fault (not connected) x3 = 1: self-tests running x4 = 1: reserved x5 = 1: error in hardware or software configuration (the module present is not that declared in the configuration, the sub-modules are not compatible) x6 = 1: missing module x7 = 1: error in one of the sub-modules z z z z z z z x0 = 1: only station on the network x1 = 1: not used x2 = 1: transmission line error x3 = 1: not used x4 = 1: internal software fault x5 = 1: hard- or software error or absence of configuration x6 = 1: communication problem with the processor x7 = 1: application fault (double address station) z

Byte 0: z x0 = 0: if bridge (0 if not router)

Byte 1: z z z

= 16#00: unsupported bus arbiter function

= 16#03: active bus arbiter function

= 16#20: bus arbiter function in standby

Unacknowledged messages

Refused messages

Byte 0: station number

Byte 1: network number

35011050 01 July 2006

FIPWAY language objects

Object (1)

%MWxy.i.7

%MWxy.i.8

...

%MWxy.i.11

Function

Common words or shared table information

Status of stations from 0 to 15

...

Status of stations from 48 to 63 z z z z z z z z z z z z z z z z z z z z z z

...

Meaning

Byte 0: z z

= 16#00: inactive service

= 16#01: read/write of common words z z

= 16#02: reading of common words

= 16#03: participation in the exchange of a shared table (operation without error)

= 16#04: overlap of the exchange zone of a z z shared table

= 16#05: exchange error of a shared table

Byte 1: size x0 = 1: station 0 present (= 0 absent) x1 = 1: station 1 present (= 0 absent) x2 = 1: station 2 present (= 0 absent) x3 = 1: station 3 present (= 0 absent) x4 = 1: station 4 present (= 0 absent) x5 = 1: station 5 present (= 0 absent) x6 = 1: station 6 present (= 0 absent) x7 = 1: station 7 present (= 0 absent) x8 = 1: station 8 present (= 0 absent) x9 = 1: station 9 present (= 0 absent) x10 = 1: station 10 present (= 0 absent) x11 = 1: station 11 present (= 0 absent) x12 = 1: station 12 present (= 0 absent) x13 = 1: station 13 present (= 0 absent) x14 = 1: station 14 present (= 0 absent) x15 = 1: station 15 present (= 0 absent) x0 = 1: station 48 present (= 0 absent)

...

x7 = 1: station 55 present (= 0 absent) x8 = 1: station 56 present (= 0 absent)

...

x15 = 1: station 63 present (= 0 absent)

Key

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

35011050 01 July 2006

FIPWAY language objects

Explicit exchange management and reports

Introduction

Word objects

This page describes all the language objects that manage explicit exchanges.

(Communication applications Volume 1 - Exchange and report management)

The table below shows the different word objects for the management of explicit exchanges.

Object (1) Function

%MWxy.MOD.0 Module exchanges in progress

%MWxy.MOD.1 Module report

%MWxy.i.0

%MWxy.i.1

Channel exchanges in progress

Channel report z z z z

Meaning z z z x0 = 1: status reading in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module z z z x0 = 1: status reading in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel x1 = 0: command parameters received and accepted by the communication channel x2 = 0: adjustment parameters received and accepted by the communication channel

Key

(1) Address xy.i

z z z x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number

35011050 01 July 2006

FIPWAY language objects

Language objects associated with the configuration

Introduction

Internal constants

This page describes all the configuration language objects for FIPWAY communication that can be displayed by the application program.

The following table describes the internal constants:

Object Function

%KWxy.i.0

Type

%KWxy.i.1

Physical layer

%KWxy.i.2

Supported services

Meaning

Byte 0 = 4 for FIPWAY communication

Byte 0: station address z z

= 0: FIP physical layer

= 1: WORLD FIP physical layer byte 1: reserved

Byte 0: common data z = 16#00: none z = 16#01: common words z = 16#02: shared table

Byte 1: telegrams z z

= 16#00: unsupported services

= 16#01: supported

Address of the beginning of the shared table %KWxy.i.3

Shared table information

%KWxy.i.4

Common words and shared table

Byte 0: the number of common words or size of production zone of the shared table

Byte 1: Address (in bytes) of the beginning of the production zone of the shared table

35011050 01 July 2006

Communication via ETHERNET network

Introduction

Subject of this part

What's in this

Part?

This part introduces the Communication function on the Micro/Premium PLCand describes its implementation with PL7 software.

This part contains the following chapters:

Chapter Chapter Name

5 Communication via Ethernet network

Facilities

Configuration parameters

TSX ETY 110 Module

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100 modules

Page

133

171

219

35011050 01 July 2006

ETHERNET communication

35011050 01 July 2006

Communication via Ethernet network

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter introduces communication via Ethernet network and its facilities.

This chapter contains the following topics:

Topic

About ETHERNET

General Information about the TSX ETY Modules

Details of Available Functions

Page

35011050 01 July 2006

General points

About ETHERNET

Introduction

Associated manuals

ETHERNET communication is essentially used for the following applications: z co-ordination between PLCs, z z z local or centralized monitoring, communication with production management data processing, communication with remote inputs/outputs.

Two communication profiles are supported by the ETHERNET network modules: z the ETHWAY profile, which restarts all the devices of the X-WAY communication architecture: z

X-WAY addressing system, z z z z

UNI-TE messaging, distributed databases (common words).

TCP/IP profile on ETHERNET allowing communication in: z

UNI-TE messaging with all of the X-WAY architecture,

Modbus messaging.

The ETHERNET network modules also support the SNMP standard network management protocol as an agent.

If you require fuller information you should consult the following manuals:

Title

ETHERNET network - Reference manual

Premium TSX PL7s - Set up manual

Momentum Bases - Set up manual

Description

Detailed description of the ETHERNET network

Hardware set up

Hardware and software set up of the

Momentum TSX

35011050 01 July 2006

General points

General Information about the TSX ETY Modules

At a Glance ETHERNET network communication is available for Premium PLCs using: z

TSX ETY 110 and TSX ETY 110 WS modules, z z

TSX ETY 410•, TSX ETY PORT and TSX ETY 510• modules, the TSX ETY 210 module.

They have several types of interface.

The TSX ETY 110 module

Connection can be made: z to an ETHWAY profile network supporting the following utilities: z common words, z z

UNI-TE messaging, to a TCP/IP profile network supporting the following utilities: z z

UNI-TE and Modbus messaging,

SNMP management.

For the

TSX ETY 110 WS module

Connection can be made: z to an ETHWAY profile network supporting the following utilities: z common words, z z

UNI-TE messaging, to a TCP/IP profile network supporting the following utilities: z z

UNI-TE and Modbus messaging,

SNMP management.

z z

TCP direct access, access to the Web-user pages HTTP server.

TSX ETY 410• and

TSX ETY PORT modules

Connection can be made: z to a TCP/IP profile network supporting the following utilities: z

UNI-TE and Modbus messaging, z z z z z z

SNMP management, input/output management (I/O Scanner),

IP address management (BOOTP/DHCP), access to the embedded Web server, common data exchange between stations (Global Data), diagnostics from Web pages.

35011050 01 July 2006

General points

The

TSX ETY 510• module

Connection can be made: z to a TCP/IP profile network, which is necessary when using FactoryCast and which supports the following utilities: z

UNI-TE and Modbus messaging, z

SNMP management, z z z z z z z z time synchronization (NTP), input/output management (I/O Scanner),

IP address management (BOOTP/DHCP), access to the embedded Web server, common data exchange between stations (Global Data), diagnostics from Web pages, access to the Web-user pages HTTP server, with direct TCP access.

The TSX ETY 210 module

Connection can be made: z to an ETHWAY profile network supporting the following utilities: z z common words,

UNI-TE messaging.

z to a TCP/IP profile network supporting the following utilities: z

UNI-TE and Modbus messaging, z z

SNMP management, specific to redundancy.

35011050 01 July 2006

General points

Details of Available Functions

At a Glance Depending on the type of ETHERNET module selected, certain functions will or will not be accessible.

Selection Guide The summary table below shows the various selections possible:

Function TSX ETY 110 TSX ETY 110 WS TSX ETY 410• /

TSX ETY PORT

Connection at 10 Mbits/s in Half/Full

Duplex in Half/Full Duplex in Half/Full

Duplex

Connection at 100 Mbits/s -

TCP/IP utility

SNMP utility:

Standard MIB

MIB Ethernet Transparent

Factory

IO Scanner Utility

Address Server utility

(BOOT/DHCP)

X in Half Duplex

UNI-TE messaging

Modbus messaging

ETHWAY profile

Software loading via FTP

(firmware)

TSX ETY 510• TSX ETY 210

X in Half/Full

Duplex in Half Duplex

in Half/Full

Duplex

Embedded HTTP server -

Global Data -

Diagnostics from Web pages

User WEB pages HTTP server

Redundancy

TCP direct access

Time synchronization utility

Legend

Available

Not available

35011050 01 July 2006

General points

35011050 01 July 2006

Facilities

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter introduces the main points of the different facilities used by the modules.

This chapter contains the following sections:

Section

6.1

6.2

6.3

6.4

6.5

6.6

6.7

6.8

6.9

6.10

Topic

TCP/IP Messaging

IO Scanning Facility

BOOTP/DHCP Address Server Utility

SNMP Facility

Global Data Utility

Managing Faulty Devices

Time Synchronization Service

HTTP on-board server

Bandwidth Monitoring

ETHWAY Facility

Page

35011050 01 July 2006

Annonce

1.2