MasterLogic-200 Series

Fast Ethernet I/F Module

Users Manual
2MLL-EFMT
FEB 2006
Release 1.0

 Table of Contents

Chapter 1 Introduction --------------------------------------------------------------- 1-1 ~ 1-6

1.1 How to use the users manual ------------------------------------------------------------------------------ 1-1
1.2 Introduction to FEnet I/F module -------------------------------------------------------------------------- 1-2
1.3 Characteristics of FEnet I/F module ---------------------------------------------------------------------- 1-3
1.4 Product Configuration ---------------------------------------------------------------------------------------- 1-4
1.4.1 Designation ------------------------------------------------------------------------------------------- 1-4
1.4.2 Available units to be installed on each CPU -------------------------------------------------- 1-4
1.5 Software for application of the product ------------------------------------------------------------------- 1-5
1.5.1Checking software ---------------------------------------------------------------------------- 1-5
1.5.2 SoftMaster-PD ---------------------------------------------------------------------------------------- 1-5
1.5.3 Checking version ------------------------------------------------------------------------------------ 1-6

Chapter 2 Product Specifications -------------------------------------------------- 2-1 ~ 2-6

2.1 General Specifications --------------------------------------------------------------------------------------- 2-1
2.2 Performance Specifications --------------------------------------------------------------------------------- 2-2
2.3 Structure and Characteristics ------------------------------------------------------------------------------- 2-3
2.3.1 Structure of FEnet I/F module -------------------------------------------------------------------- 2-3
2.4 Cable Specifications ------------------------------------------------------------------------------------------ 2-4
2.4.1 UTP cable ----------------------------------------------------------------------------------------------- 2-4
2.4.2 Optical cable -------------------------------------------------------------------------------------------- 2-6

Chapter 3 Installation and Operation --------------------------------------------- 3-1 ~ 3-8

3.1 Precautions for Installation ---------------------------------------------------------------------------------- 3-1
3.1.1 How to install ----------------------------------------------------------------------------------------- 3-1
3.1.2 Operation Steps-------------------------------------------------------------------------------------- 3-1

3.2 Installation of the Product ----------------------------------------------------------------------------------- 3-3

3.2.1 Installation of 10/100BASE-TX ------------------------------------------------------------------- 3-3
3.2.2 Installation of 100BASE-FX ----------------------------------------------------------------------- 3-5
3.3 Operation -------------------------------------------------------------------------------------------------------- 3-6
3.3.1 Precautions for system configuration ----------------------------------------------------------- 3-6
3.3.2 Checklist prior to operation ---------------------------------------------------------------------- 3-7
3.3.3 How to install or remove the module ----------------------------------------------------------- 3-8

Chapter 4 System Configuration --------------------------------------------------- 4-1 ~ 4-4

4.1 Configuration of Network System ------------------------------------------------------------------------- 4-1
4.1.1 Public Network composed of MasterLogic PLCs--------------------------------------------- 4-2
4.1.2 Dedicated Network composed of MasterLogic PLCs ----------------------------- 4-2
4.1.3 Dedicated Network composed of Honeywell and Other Companys PLCs ------------------- 4-2
4.1.4 Public Network and Dedicated Network system -------------------------------------------- 4-3
4.1.5 Public Network and Dedicated Network system composed of Honeywell and other
companys PLCs ------------------------------------------------------------------------------------- 4-4

Chapter 5 SoftMaster-PD Program ----------------------------------------------- 5-1 ~ 5-24

5.1 Introduction ----------------------------------------------------------------------------------------------------- 5-1
5.2 Basic Settings--------------------------------------------------------------------------------------------------- 5-2
5.2.1 Register of communication module ------------------------------------------------------------- 5-2
5.2.2 Standard settings (Module)------------------------------------------------------------------------ 5-5
5.3 HS Link Setting ------------------------------------------------------------------------------------------------ 5-8
5.3.1 Setting of HS link parameters -------------------------------------------------------------------- 5-8
5.4 P2P Setting ---------------------------------------------------------------------------------------------------- 5-11
5.4.1 P2P parameters ------------------------------------------------------------------------------------ 5-11
5.5 Communication and Download to Communication Module---------------------------------------- 5-13
5.5.1 Download/Upload -------------------------------------------------------------------------------- 5-13
5.5.2 Link Enable ------------------------------------------------------------------------------------------ 5-16
5.6 System Diagnosis ------------------------------------------------------------------------------------------- 5-18
5.6.1 Execution of the diagnosis function ----------------------------------------------------------- 5-18
5.5.2 Type of diagnosis functions --------------------------------------------------------------------- 5-19

Chapter 6 HS Link Service ---------------------------------------------------------- 6-1 ~ 6-14

6.1 Introduction ----------------------------------------------------------------------------------------------------- 6-1
6.2 HS link Tx/Rx Data Processing -------------------------------------------------------------------------- 6-2
6.3 Operation Sequence through HS link -------------------------------------------------------------------- 6-3
6.4 HS link parameters setting ---------------------------------------------------------------------------------- 6-4
6.4.1 Execution of SoftMaster-PD ---------------------------------------------------------------------- 6-4
6.4.2 Basic settings (Module)----------------------------------------------------------------------------- 6-4
6.4.3 HS Link Parameters (HS Link) ------------------------------------------------------------------- 6-5
6.5 HS Link Information ----------------------------------------------------------------------------------------- 6-10
6.5.1 HS Link Flags --------------------------------------------------------------------------------------- 6-10
6.5.2 Monitor of HS link information ------------------------------------------------------------------ 6-12

Chapter 7 P2P Service --------------------------------------------------------------- 7-1 ~ 7-26

7.1 Introduction ----------------------------------------------------------------------------------------------------- 7-1
7.1.1 Introduction to P2P service ----------------------------------------------------------------------- 7-1
7.1.2 Configuration of P2P parameters ---------------------------------------------------------------- 7-2
7.2 Type of P2P Service ----------------------------------------------------------------------------------------- 7-4
7.2.1 Type of P2P Commands --------------------------------------------------------------------------- 7-4
7.2.2 Type of P2P Service ------------------------------------------------------------------------------- 7-4
7.3 How to Set P2P Service ------------------------------------------------------------------------------------- 7-5
7.3.1 Ethernet (server) driver ---------------------------------------------------------------------------- 7-5
7.3.2 P2P Channel ------------------------------------------------------------------------------------------ 7-6
7.3.3 Define User Frame--------------------------------------------------------------------------------- 7-10
7.3.4 P2P block -------------------------------------------------------------------------------------------- 7-14
7.4 P2P Service Operation ------------------------------------------------------------------------------------- 7-23
7.5 P2P Diagnosis Function ------------------------------------------------------------------------------------ 7-25

Chapter 8 Dedicated Protocol Communication ------------------------------ 8-1 ~ 8-20

8.1 Dedicated Communication ---------------------------------------------------------------------------------- 8-1
8.1.1 Introduction ------------------------------------------------------------------------------------------- 8-1
8.1.2 Frame Structure ------------------------------------------------------------------------------------- 8-2
8.1.3 List of Commands ----------------------------------------------------------------------------------- 8-4
8.1.4 Data Type ---------------------------------------------------------------------------------------------- 8-4
8.2 Execution of Commands ------------------------------------------------------------------------------------ 8-5
8.2.1 Read Separated Direct Variable -------------------------------------------------------------- 8-6
8.2.2 Read Continuous Direct Variable ------------------------------------------------------------ 8-8
8.2.3 Write Separated Direct Variable -------------------------------------------------------------- 8-10
8.2.4 Write Continuous Direct Variable ----------------------------------------------------------- 8-12
8.2.5 Status Read Request (MMI -> PLC) ---------------------------------------------------------- 8-14

8.3 Modbus/TCP Dedicated Server -------------------------------------------------------------------------- 8-19

8.3.1 Driver setting ---------------------------------------------------------------------------------------- 8-19

Chapter 9 Remote Connection Service ------------------------------------------ 9-1 ~ 9-9

9.1 Introduction ----------------------------------------------------------------------------------------------------- 9-1

9.2 Setting and Connection -------------------------------------------------------------------------------------- 9-2
9.2.1 Remote 1 connection (If RS-232C cable used) -------------------------------------- 9-3
9.2.2 Remote 2 connection (RS-232C cable is used for local connection) ------------------ 9-5
9.2.3 Remote 1 connection directly from PC connected with Ethernet --------------- 9-6
9.2.4 Remote 2 connection directly from PC connected with Ethernet --------------- 9-7

Chapter 10 Troubleshooting ---------------------------------------------------- 10-1 ~ 10-13

10.1 Check through communication module LED -------------------------------------------------------- 10-1
10.1.1 Display of Abnormal Operation --------------------------------------------------------------- 10-1
10.2 Module Check through SoftMaster-200 -------------------------------------------------------------- 10-3
10.3 Module Check through Error Codes ------------------------------------------------------------------- 10-4
10.3.1 Abnormal operations ---------------------------------------------------------------------------- 10-4
10.3.2 Troubleshooting ---------------------------------------------------------------------------------- 10-5

Appendix --------------------------------------------------------------------------------- A-1 ~ A-19

A.1 List of Flags ---------------------------------------------------------------------------------------------------- A-1
A.1.1 List of Special Relays (F) ---------------------------------------------------------------------------- A-1
A.1.2 List of Communication Relays (L) ----------------------------------------------------------------- A-9
A.2 ASCII Code Table ------------------------------------------------------------------------------------------- A-15
A.3 Comparison Table of Ethernet Technology ----------------------------------------------------------- A-18
A.4 External Dimensions --------------------------------------------------------------------------------------- A-19

Chapter 1 Introduction

Chapter 1 Introduction
1.1 How to use the users manual

Refer to the manuals below for programming.

MasterLogic-200 PLC Instructions list
MasterLogic-200 PLC SoftMaster-200 users manual
Pay attention to those items below for system configuration of MasterLogic-200 FEnet I/F module.
MasterLogic-200 PLC SoftMaster-200 programming tool: Ver 1.0 or higher
SoftMaster-PD: Ver 1.0 or higher
2MLK CPUH: Ver 1.2
2MLK CPUS: Ver 1.2

1-1

Chapter 1 Introduction

1.2 Introduction to FEnet I/F module

This users manual is prepared to describe Fast Ethernet Interface module of MasterLogic-200 series
PLC (hereinafter referred to as FEnet I/F module, 100Mbps).
Ethernet is a technical standard' established by the international organization of IEEE.
Communication is controlled by CSMA/CD method and network can be established with easy. In
addition, a great amount of data can be transferred with high speed. FEnet I/F module is an interface
module to communicate data between higher level system such as host PC and PLC, or between
PLCs with electric/optical media(10/100BASE-TX, 100BASE-FX).

Ser

100Base-FX (Fiber Optic)

M

H
HMI

100Base-TX

100Base-TX
HMI

[Fig. 1.2.1] Configuration diagram of FEnet system

FEnet I/F module has variety applicable communication systems. Refer to Chapter 4 System
Configuration for detailed system configuration and its description.
1) Communication between PLC and host PC (MMI)
2) Mutual exchange or monitoring data between PLCs /monitoring
3) Data management or system control for field devices.

1-2

Chapter 1 Introduction

1.3 Features of FEnet I/F module

MasterLogic-200 FEnet I/F module supports TCP/IP and UDP/IP protocols and has the features as
specified below;

Fast Ethernet (FEnet I/F module) :

Module exchange on CPU RUN with module exchange switch in the CPU is possible.
Module exchange on CPU RUN with module exchange wizard of SoftMaster-200 is possible.
Conforms to IEEE 802.3 standard (Ethernet standard supported).
HS link service supported for communication between Honeywells PLCs with high speed.
SoftMaster-PD, a communication parameter configuration tool, is provided.
HS link block setting available to link between modules.
(Max. Send Data: 64blocks x 200 words, Max. Receive Data: 128 blocks x 200 words,
Totally 128 blocks can be setup.(Send + Receive)) .
In addition to HS link service, Communication with up to 16 Ethernet devices is available
(dedicated communication + P2P communication).
Loader service (SoftMaster-200 connection) is supported through Ethernet: (dedicated TCP/IP
PORT : 2002 allotted).
It is easy to connect with other companys Ethernet device through P2P communication and
SoftMaster-PD. (Variable READ/WRITE service is available (through Dynamic Connection))
10/100BASE-TX, 100BASE-FX media supported.
Data accessible via the public network.
Honeywell protocol (MasterLogic-200/MasterLogic-100R) and other companys protocol
(MODBUS TCP) supported
(dedicated service)
Convenient client function supported for communication between Honeywells PLCs and
for communication with other companys Ethernet device.
(MasterLogic-200/MasterLogic-100R, Modbus TCP P2P client function)
Dynamic IP supported to make ADSL network available
Access table provided for host PC(MMI) and communication security.
Dynamic Connection/Disconnection supported through P2P service.
Various diagnosis functions and status information of modules and network provided.
-

CPU module status

Communication module status

Communication service (HS link, dedicated service, P2P) status

AutoScan function used to visualize the information of Honeywells
communication modules connected within the network
PING test function provided to check if other modules exist.
Type and average amount of packet received by communication module provided

(network load predictable)

- Diagnosis function provided for communication module through the network.
E-MAIL service (ASCII) provided.
Up to 24 Ethernet communication modules can be installed on basic or extension base.

1-3

Chapter 1 Introduction

1.4 Product Configuration

1.4.1 Designation
Product configuration of MasterLogic-200 FEnet I/F module is as follows;

Designations

Description

Remarks

2MLL-EFMT

10/100BASE-TX

UTP, category 5 or more

2MLL-EFMF

100BASE-FX

Fiber Optic

Notes
1) AUI (10BASE-5) is not supported in MasterLogic-200 series.
2) In the case that UTP cable is used, use the switching hub of 100Mbps, which can be used
together with the 10Mbps Ethernet device (category 3 or less) but its baud rate will be limited to
10Mbps.
Pay attention to installation of the system.

1.4.2 Available units to be installed on each CPU

The maximum installation number of modules based on CPU type of each FEnet I/F module is
described in the table below. After due consideration of the number of communication modules
available, apply such applicable modules to the system configuration.

Classification

Number of communication modules available

2MLK-CPUH

24 modules

2MLK-CPUS

24 modules

Notes
If other kinds of communication are installed, the number of available Ethernet module will be
reduced by the number of other kinds of communication module. In other words, total number of
communication module available on 1 CPU is limited to 24

1-4

Chapter 1 Introduction

1.5 Software for application of the product

The following is for main programming tools and other producing software needed to use FEnet I/F
module. For more precise application of program and communication, please refer to the details below
so to apply to the system.

1.5.1 Checking software

1) Application to MasterLogic-200 series
Classification

2MLL-EFMT

UTP,10/100BASE-TX

2MLL-EFMF

100BASE-FX

Programming tool

Frame Setting

SoftMaster-200

SoftMaster-PD

Notes
1) The software above can be downloaded presently from the web site for its application. If the
Internet is not available, please visit the nearest agent of service center to get the applicable
installation CD-ROM to use.
2) RS-232C and USB port of CPU module is available for downloading the program made by
SoftMaster-200 and communication configuration made by SoftMaster-PD.
Refer to CPU or SoftMaster-200 manual for connection diagram of each cable.

1.5.2 SoftMaster-PD
SoftMaster-PD is exclusive software to setup parameters, edit frames and diagnose
communication modules of MasterLogic-200 series PLC. ule and network necessary for
operation of all the communication modules including FEnet I/F module.
Refer to Chapter 5 SoftMaster-PD for more details.
The figure below shows the initial screen of SoftMaster-PD.

[Fig. 1.5.1] Initial screen of SoftMaster-PD

1-5

Chapter 1 Introduction

1.5.3 Checking version

Prior to use of FEnet I/F module, please check the version of the applicable module.

1) Through SoftMaster-PD
Connect with communication module directly via on-line so to read information of the
communication module.
If interface status with CPU is normal, the information will be acquired as shown below.
1) Execute SoftMaster-PD.
2) Use on-line connection with CPU.
3) If connection between SoftMaster-PD and CPU is established, execute diagnosis of
SoftMaster-PD.
4) On the system diagnosis screen, execute communication module status.
5) Software information will be displayed on the right bottom of the communication module
status screen.

[Fig. 1.5.2] Checking module version through SoftMaster-PD

2) Through the case label of the product

On the external case of each communication module, product information of the module is
printed. The version can be checked module may be removed and then installed if on-line
checking is unavailable due to unavailable external connection device with PC.
The label is adhered to the back of the product where designation and version information of the
product are described.

1-6

Chapter 2 Product Specifications

Chapter 2 Product Specifications

2.1 General Specifications
General specifications of MasterLogic-200 series are as shown in Table 2.1.
No.

Items

Specification

Ambient Temp.

0 ~ 55 C

Reference

Storage Temp.

25 ~ +70 C

Ambient humidity

5 ~ 95%RH (Non-condensing)

Storage humidity

5 ~ 95%RH (Non-condensing)
Occasional vibration

Vibration

Frequency

Acceleration

Pulse width

10 f < 57Hz

0.075mm

Times

57 f 150Hz

9.8m/s2(1G)

10 times

Acceleration

Pulse width

direction (X,Y

10 f < 57Hz

0.035mm

and Z)

57 f 150Hz

4.9m/s2(0.5G)

each

Continuous vibration
Frequency

IEC61131-2

Peak acceleration : 147 m/s (15G)

6

Shocks

Duration : 11ms

IEC61131-2

Pulse wave type : Half-sine (3 times each direction per each axis)
Square wave
Electrostatic

Impulse noise

spec.

Voltage: 4kV (Contact discharge)

discharge
7

Internal test

1,500 V

impulse noise

Radiated
electromagnetic

27 ~ 500 MHz, 10V/m

field noise
Fast transient
/Burst noise
8

Operation
ambience

Classific

Power

Digital/Analog Input/Output,

ation

supply

Communication Interface

Voltage

2kV

1kV

IEC61131-2
IEC61000-4-2
IEC61131-2,
IEC61000-4-3
IEC61131-2
IEC61000-4-4

Free from corrosive gases and excessive dust

Altitude

Less than 2,000m

10

Pollution degree

Less than 2

11

Cooling method

Air-cooling

[Table 2.1] General Specifications

Notes
1) IEC(International Electrotechnical Commission.
: An international nongovernmental organization which promotes internationally cooperated standardization in
electric/electronic fields, publishes international standards and manages applicable estimation system related
with.
2) Pollution level
: An index indicating pollution level of the operating environment which decides insulation performance of the
devices. Generally, Pollution level 2 indicates the state that only non-conductive pollution occurs generally.
However, this state contains temporary conduction due to dew produced.

2-1

Chapter 2 Product Specifications

2.2 Performance Specifications

Specifications for system configuration are as described below according to media of FEnet I/F
module. Refer to the table below for system configuration.
Product Name
Item
Baud rate

2MLL-EFMT
(10/100BASE-TX)

2MLL-EFMF
(100BASE-FX)

10/100Mbps

100Mbps

Transmission Type

Transmission
Specification

Base Band

Max. extended length between

nodes

100m
(Node-Hub)

2km

Max. segment length

Max. number of nodes

Hub connection
(Up to 9 recommended )

30/Segments

Distance between nodes

Integral times of 0.5m

Max. protocol size

1,500 Byte

Access method to service zone

Frame error check
Basic
Specification

Current consumption (5V)

Weight

CSMA/CD
15

CRC 16 = X + X

14

+ X13+ .... + X2 + X + 1

2MLL-EFMT : 410 mA
2MLL-EFMF : 630 mA
2MLL-EFMT : 105 g
2MLL-EFMF : 120 g

[Table 2.2 Performance Specification of FEnet I/F module]

2-2

Chapter 2 Product Specifications

2.3 Structure and Characteristics

2.3.1 Structure of FEnet I/F module
1) 2MLL-EFMT/2MLL-EFMF
W LED display

W Media connector

2MLL-EFMT

2MLL-EFMF

The table 2.3.1 explains the details of LED display. Refer to chapter 10 Troubleshooting of this manual
for judgment and action of trouble based on the status of LEDs.
LED name
RUN
I/F
HS
P2P
PADT
PC
ERR
TX
RX
10/100

LED status
On
OFF
Blinks
Off, On
On

Details
Normal
Serious defect
Normal
Serious defect
During HS link service

Contact A/S center

Off

HS link service being Off

Check SoftMaster-PD
setting

On

During P2P service

Off

P2P service being Off

On

Remote-connected

Off

Remote-disconnected

On
Off
On
Off
On
Off
On
Off
On
Off

During dedicated communication service

Communication service being Off
Serious defect
Normal
Data being transmitted
Serious defect
Data being received
Serious defect
100Mbps
10Mbps
[Table 2.3.1 LEDs of FEnet I/F module]

2-3

Action

Contact A/S center

Check SoftMaster-PD
setting
Check SoftMaster-200
setting
Check MMI(HMI) setting
Contact A/S center
Contact A/S center
Contact A/S center
Media check

Chapter 2 Product Specifications

2.4 Cable Specifications

2.4.1 UTP cable
UTP cable is classified into 2 types based on the following criteria.
Shield: classified into 3 (UTP, FTP, STP)
Frequency band used: classified into 7 (Cat.1~7)

1) Type of cables (shield)

Classification
UTP (or [Link])

FTP (or [Link])

STP (or [Link])

Details

Purpose

Unshielded cable. High speed

data transmission.

Max. 200MHz
Phonetic+Data+Low grade of video signal

Shielded cable core only.

Max.100MHz
Electronic impediment (EMI) and electric stability
considered
Phonetic+Data+Low grade of video sign

Double-shielded cable.
Shielded core and Individually
Pair cable

UTP

Max. 500MHz
Phonetic+Data+Video sign
Substitute for 75 coaxial cable

FTP

STP

Notes
1) UTP : Unshielded

Twisted Paired Copper Cable

FTP : (Overall) Foiled Twisted Paired Copper Cable

STP : (Overall) Shielded(and Shielded Individually Pair)Twisted Paired Copper Cable
2) Patch Cable(or Patch Cord)
Conductor composed of stranded cable instead of solid conductor may be used to increase the
flexibility of UTP 4-pair cable. And surface specification and materials used is Un-coated AWG
24 (7/0203A).
In other words, the diameter of a single cable is 0.203mm, and this cable is of 1+6 structure as
standardized with annealed copper cable.

2-4

Chapter 2 Product Specifications

2) Classification based on frequency used

Classification

Frequency used
(MHz)

Transmission
Speed (Mbps)

Category 1

Phonetic Frequency

Phone network (2-Pair)

Category 2

Multi-Pair communication cable

Category 3

16

16

Phone network + Computer network

Category 4

20

20

1) Computer network transmission

speed Up
2) Low-loss communication cable

Category 5 and
Enhanced
Category 5

100

100

1) Digital Phone network +

Computer network
2) Low-loss, broadband cable

Purpose

Notes
1) Presently classified items are Category 3, 5, En-Cat.5 and Cat.6 inside and outside of the
country, where Category 4 has been replaced by Category 5 and Category 7 is being under
development all over the world as STP structure.

3) Example (CTP-LAN5) of Category 5 twisted-pair cable (UTP)

Item

Unit

Value

Conductor resistance(Max)

/km

93.5

Insulation resistance(Min)

Mkm

2,500

Voltage endurance

V/min

AC 500

Characteristic impedance

(1~100MHz)

100 15

Attenuation

Near-end crosstalk
Attenuation

dB/100m
or less
dB/100m
or less

2-5

10MHz

6.5

16MHz

8.2

20MHz

9.3

10MHz

47

16MHz

44

20MHz

42

Chapter 2 Product Specifications

2.4.2 Optical cable

Item

Value

Cable Type

Twin strands of multi-mode fiber optic cable(MMF)

Connector

SC type connector

Diameter of optical fiber

62.5/125m (62.5m fiber optic core and 125m outer cladding)

Wavelength used

1,350 nm

Attenuation

2dB/1,000m or less

Near-end crosstalk Attenuation

11dB or less

Notes
1) Since the type of the connectable cable used for communication module differs from each other
based on the system configuration and its environment, applicable professional advice will be
required prior to installation.
2) The optical cable may have communication errors due to attenuation if any fingerprint or
contamination is stuck on the sectional end of the cable during its treatment.

2-6

Chapter 3 Installation and Test Operation

Chapter 3 Installation and Operation

3.1 Precautions for Installation
3.1.1 How to install
For system configuration through FEnet I/F module, carefully make sure of the following items prior to
installation.
1) Check the basic factors necessary for system configuration so to select an appropriate communication
module.
2) Select the cable to be used for communication module to use. (only one is available between
10/100 BASE-TX and 100BASE-FX).
3) Before installing communication module, check if there is no foreign element on the connector of
base and module, and no damage on the connector pin of the module.
4) All kinds of communication modules can be installed on the extension base fundamentally,
however, it is recommended to install communication modules on the slot as near as possible to
CPU.
5) For installation of the module, exactly insert the protuberant part at the bottom of the module with
the communication cable disconnected into the base groove and then apply enough strength until
its top is locked up with the locking device of the base. If the lock is not applied, it may cause an
error on the interface with CPU.
6) The cable available for the communication module shall be installed with one type only between
10/ 100BASE-TX and 100BASE-FX.
7) Select standard products of switching hub and cable, which are necessary for communication with
FEnet I/F module.

3.1.2 Operation Steps.

The steps for operating FEnet I/F module from installation to operation will be described below. After
the product installation is complete, install and configure the system to be operated as specified in the
following steps.
Operation Steps.
1) Install FEnet I/F module on the base
2) Connect FEnet I/F module with other network.
3) Turn the system power on
4) Run SoftMaster-PD to setup basic parameters.
5) After the basic parameters are downloaded, reset the module.
6) After the module reset, check if RUN and I/F RUN LEDs of the module are normal.
7) If LED and CPU are normal, check the status information of the communication module and CPU
with the diagnosis function of SoftMaster-PD.
8) If the module status is normal, check if response comes in when PING test is executed through a
computer connected to the network if a computer is connected to the network. If computer is not
connected to the network, use the live check item among diagnosis services of SoftMaster-PD to
check the response.

3-1

Chapter 3 Installation and Test Operation

9) Setup the communication services and download the setup items to the PLC with SoftMaster-PD.
10) Enable communication service.
11) After programming with SoftMaster-200, write it on CPU to start the operation.
Notes
1) After station No. and IP address are specified through SoftMaster-PD, surely reset the
applicable
module. The first station No. and IP address (including frames) will keep the value read from
the communication module when initialized. Any changed details during communication will
not
be applied during Run.

3-2

Chapter 3 Installation and Test Operation

3.2 Installation of the Product

3.2.1 Installation of 10/100BASE-TX

[Fig. 3.2.1] Installation of 10/100BASE-TX

The maximum cable length of a segment in 10/100BASE-TX system is 100m (distance between
module and hub). Generally, the hub is of straight cable with TD and RD stranded inside.
If only 2 communication modules are connected 1 to 1, cross-cable form shall be used.

Pin No.

Sign

Straight cable between

hub and module

1 to 1 cross-cable

TD+

11

13

2
3
6
4, 5, 7, 8

TDRD+
RDNot used

22
33
66

26
31
62

3-3

Chapter 3 Installation and Test Operation

Notes
1) Since the structure of 10/100BASE-TX cable is vulnerable to external noise, the cable needs
to be stranded as twisted (two lines twisted with each other) between cables of the pin No.1
and 2 of TD+ and TD- and between cables of the pin No.3 and 6 of RD+ and RD- so to be
strong against noise
2) Hub power shall be separated from PLC power to be used against the noise.
3) Contact professional manufacturers for processing cable terminal, manufacture and
installation.

1) Precautions for UTP installation

(1) In order to transmit reliable 100Mbps sign with UTP cable, use the cable conforming to
the characteristics of Category 5.
(2) Be careful not to exceed the tension strength of the cable intensely during wiring.
(3) When escaping from the coat (sheathed), let it as long as the length only to be wired and
with the insulation kept from damage.
(4) Jumper wire and patch code shall be applied rather loosely. If wired too tight, the
characteristics of Category 5 may be deteriorated.
(5) When UTP cable is installed, a suitable distance shall be maintained between EMI source
and UTP cable.
Min. separation distance
2.0KVA or less
2.5 KVA
5.0KVA or more

Condition
Power line unshielded, or electric facility open or
near to nonmetallic pipe
Power line unshielded, or electric facility near to
metallic pipe buried
Power line inside metallic pipe buried (or equivalently
shielded) near to metallic pipe buried
Transformer, electric motor, fluorescent lamp

127mm

305mm

610mm

64mm

152mm

305mm

76mm

152mm

1,016mm 305mm

Notes
1) If voltage is 480V, rated power is 5KVA or more, separate calculation is needed.

3-4

Chapter 3 Installation and Test Operation

3.2.2 Installation of 100BASE-FX

Optical switch

MULTI MODE

SC

[Fig. 3.2.2] Installation of 100BASE-FX

The maximum cable length of segment in 100BASE-FX system is 2km (distance between
module and optical switch). Let the modules Tx cross-connected with the optical switchs Rx,
and the modules Rx with the optical switchs Tx.
Notes
1) Since the optical cable is vulnerable to impact, pressure, folding and pulling, pay good attention
to its treatment.
The optical contact between the connector and the end of the cable may have communication
errors if contaminated, which may result in unavailable communication.
If the cable is installed outdoors, additional countermeasures are required to protect the cable
suitably for the installation environment.

3-5

Chapter 3 Installation and Test Operation

3.3 Operation

Check status of LEDs of FEnet I/F module when power turned on after communication cable is
connected. If normal, download the applicable program to PLC via SoftMaster-200 so to execute the
program.

3.3.1 Precautions for system configuration

1) IP addresses shall be surely different from each devices in 1 network system including FEnet
I/F module. If there are more than 1 devices of same IP address in 1 network system,
communication error may occur, leading to communication trouble. HS link station No. of all
stations also shall be different from each FEnet I/F module to use HS link service.
2) Use the communication cable as specified only. If not, fatal error may occur to communication.
3)

Check communication cable if opened or shorted prior to installation.

4)

Tighten up communication cable connector until connected firmly. If cable connection is

unstable, fatal error may occur to communication.

5)

If cable is connected long distance, keep the cable far away from power line or inductive noise.

6)

Since the flexibility of coaxial cable is low, it is to be diverged min. 30cm away from the
connector in communication module. If the cable is bent at a right angle or transformed
compulsorily, cable disconnection or connector damage in communication module may be
caused.

7)

If the status of LEDs is abnormal, refer to Chapter 10 Troubleshooting to check for causes and
available actions against the status of LEDs. Contact A/S center if the error is as before

3-6

Chapter 3 Installation and Test Operation

3.3.2 Checklist prior to operation

Check items are described below prior to operation of the FEnet I/F module.

1) Communication module installed on PLC

Check items

Description

Installation and
inspection of Basic S/W

- Is installation and operation of SoftMaster-200 normal?

- Is installation and operation of SoftMaster-PD normal?

Communication cable
connection
(If cable is connected)

- Is connection and tab status of communication cable normal?

- Is the status of LEDs and cable connection normal?

Module Installation

- Is the FEnet I/F module installed correctly on basic base?

2) Steps of operation
The steps will be described below, starting from installation complete on PLC to test operation
Start
Power on:

1) Confirm input power.

2) Check communication cable connection.
3) Power on.
4) Check if power LED of power module is turned on.
5) Check LED status of CPU module.
-> If abnormal, refer to Troubleshooting in user manual of each PLC model.
6) Check if LED status of communication module is normal or not.
-> If abnormal, refer to Chapter 10. Troubleshooting in this user manual.
7) Set system parameters correctly so to download..

Programming : Program execution program with SoftMaster-200 and write to CPU module.

Sequence check :
Confirm the operation of communication module according to program.

Program modification :
If abnormal in sequence program, let it modified.

Program preservation :
1) Save the program onto floppy or hard disk.
2) Print circuit drawings and list.
3) Save the program in the memory module when it is necessary.
End

3-7

Chapter 3 Installation and Test Operation

3.3.3 How to install or remove the module

Follow the steps described below to replace or remove the applicable module due to its
hardware error or system change.

1) To replace the communication module

(1) Power off the base where the communication module is installed on.
(2) Disconnect the network cable.
(3) Install a new module as specified in the steps of 3.3.2 above.

Notes
1) When FEnet I/F module is replaced, reset the opposite side device (MMI or PC). The device
may stop communicating due to the time out of the applicable module

3-8

Chapter 4 System Configuration

Chapter 4 System Configuration

4.1 Configuration of Network System
4.1.1 Public Network composed of Honeywells PLCs

Broadband Monitoring
System 1

Broadband Monitoring
System 2

HMI

Router or
Gateway
Public Network

PLC [D]
IP:[Link]

PLC [F]
IP:[Link]

PLC [E]
IP:[Link]

Router or
Gateway

PLC [A]
IP:[Link]

PLC [C]
IP:[Link]

PLC [B]
IP:[Link]

Ethernet Network (Network 1)

PC
HMI

PC
HMI
Local Monitoring
System 1

Local Monitoring
System 2

[Fig.4.1.1] Ethernet System [Public network with Honeywells PLCs]

4-1

Chapter 4 System Configuration

4.1.2 Dedicated Network composed of Honeywells PLCs

2 34
2 34

CON1
22

COM

17
18
19
04

10BASE5

CON1

21
22
23
COM

25

12
13
14
15
COM

FG

16
17
18
19
04

10BASE5

22
COM

25

08
25
26
27

27
28

10BASE2

29

29
30

30

CON2

CON2

31
COM

10BASE-T

+- DC24V

CON2

31
COM

10BASE-T

+- DC24V

RELAY
AC250V 2A
DC24V 2A

CON1

21
23

08
26
28

10BASE2

29

56

56

11

16

27

31
COM

5 6

2 34

18
04
21

30

78

0: [Link]
1: TEST1
2: TEST2

09
10

12G

15
COM

08

28

78

X1

MODE

08

5 6

5 6

5 6

56
2 34

5 6

5 6
2 34

5 6

5 6

+12V

13

26

10BASE-T

78

X10

COM

90 1

17
19

23

14

FAULT

06

90 1

10

FG

TX/RX

04

GLOFA

GLOFA

GLOFA

16

TOKEN

02
03

78

0: [Link]
1: TEST1
2: TEST2

09

12

LAS

05

[Link]
DC IN

MODE

08

12G

RUN

00
01

11

14
15
COM

STOP

RUN

90 1

+12V

13

10BASE5

PROGRAMMABLE
CONTROLLER

0: [Link]
1: TEST1
2: TEST2

90 1

11

10BASE2

PAU/REM

07

COM

78

0: [Link]
1: TEST1
2: TEST2

09

12

FG

X1

06

DC IN

MODE

08
10

12G

78

78

04

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

MODE

02
03
05

[Link]

90 1

+12V

X10

00
01

G3L-FUEA

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

07

COM

FAULT

90 1

STOP

RUN

RUN
STOP
REMOTE
FAIL
ERROR

PWR

TX/RX

90 1

PROGRAMMABLE
CONTROLLER

0: [Link]
1: TEST1
2: TEST2

07

DC IN

TOKEN

90 1

X1

PAU/REM

G3L-EUEA

GM1-CPUA

GM3-PA1A

RUN
LAS

78
78

78

04
06

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

MODE

02
03
05

[Link]

G3L-FUEA

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

90 1

STOP

X10

00
01

90 1

RUN

90 1

PROGRAMMABLE
CONTROLLER

90 1

78
78

0: [Link]
1: TEST1
2: TEST2

RUN
STOP
REMOTE
FAIL
ERROR

FAULT

MODE

PAU/REM

G3L-EUEA

GM1-CPUA

PWR

TX/RX

5 6

TOKEN

2 34

10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

LAS

2 34

10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

GM3-PA1A

RUN

2 34

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR

2 34

PWR

[Link]

G3L-FUEA

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR

2 34

RUN
STOP
REMOTE
FAIL
ERROR

GLOFAPLC
PLCCC
IP:[Link]
[Link]

2 34

G3L-EUEA

GM1-CPUA

GM3-PA1A

PLC B
GLOFA
PLC B
IP:[Link]

2 34

GLOFAPLC
PLCAA
IP:[Link]
[Link]

+- DC24V

RELAY
AC250V 2A
DC24V 2A

RELAY
AC250V 2A
DC24V 2A

(1)
Ethernet
Network
(Network 1)

56

RUN

STOP

2 34

+12V

10
11

12G

13

GLOFA

2 34

GLOFA

14
15
COM

16
17
18
19
04

CON1

21
22
23
COM

Desktop System

12
13
14

FG

15
COM

16
17
18
19
04

10BASE5

22
COM

25

08
25
26

27

27
28

10BASE2

29

29

30
31
COM

10BASE-T

30

CON2

CON2

31
COM

10BASE-T

+- DC24V

+- DC24V

RELAY
AC250V 2A
DC24V 2A

Host Computer
[Link]
IP:[Link]

CON1

21
23

08
26
28

10BASE2

78

0: [Link]
1: TEST1
2: TEST2

09

11

FG

MODE

08

5 6

5 6

12

10BASE5

78

X1

COM

78

2 34

0: [Link]
1: TEST1
2: TEST2

90 1

09
10

12G

X10

06

DC IN

MODE

08

90 1

+12V

FAULT

04

07

COM

TX/RX

02
03
05

[Link]

07

DC IN

TOKEN

00
01

56

PROGRAMMABLE
CONTROLLER

78

X1

06

901

04

0: [Link]
1: TEST1
2: TEST2

5 67

78

02
03
05

[Link]

RUN
LAS

MODE

PAU/REM

5 6

5 67

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

2 34

5 6

X10

01

G3L-FUEA

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

90 1

00

RUN
STOP
REMOTE
FAIL
ERROR

FAULT

901

HMI

STOP

RUN

90 1

PROGRAMMABLE
CONTROLLER

G3L-EUEA

GM1-CPUA

PWR

TX/RX

90 1

78

0: [Link]
1: TEST1
2: TEST2

TOKEN

90 1

MODE

PAU/REM

GM3-PA1A

RUN
LAS

2 34

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

2 34

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

G3L-FUEA

2 34

RUN
STOP
REMOTE
FAIL
ERROR

PWR

G3Q-RY4A

2 34

G3L-EUEA

GM1-CPUA

GM3-PA1A

RELAY
AC250V 2A
DC24V 2A

GLOFAPLC
PLCDD
[Link]
IP:[Link]

GLOFAPLC
PLCEE
[Link]
IP:[Link]

[Fig.4.1.2] Ethernet System (Dedicated Network with Honeywells PLCs)

4.1.3 Dedicated Network composed of Honeywells and Other Companys PLCs

[Link]

06

2 34

L
+12V

08
09
10

13

04
21

CON1

0: [Link]
1: TEST1
2: TEST2

COM

04

10BASE5

21

CON1

22
23
COM

25

09

16
17
18
19
04

10BASE5

21

CON1

22
23
COM

08

25

08
25
26

27

27

28

28

10BASE2

29
31
COM

10BASE-T

78

13
14
15
COM

FG

29

30

CON2

0: [Link]
1: TEST1
2: TEST2

12

26

10BASE2

29

5 6

5 6

16
17

27

31
COM

08

11

18

08

28

78

X1

MODE

10

12G

19

30

X10

06
COM

+12V

13

26

+- DC24V
RELAY
AC250V 2A
DC24V 2A

FAULT

5 6

2 34

22
23

10BASE-T

TX/RX

02

[Link]

14
15
COM

TOKEN

01

04

12

FG

LAS

03
05

78

GLOFA

18

GLOFA

GLOFA

16
17
19

10BASE5

00

11

12G

14
15
COM

10BASE2

DC IN

MODE
5 6

5 6
2 34

0: [Link]
1: TEST1
2: TEST2

RUN

78
78

901

09
11

0: [Link]
1: TEST1
2: TEST2

STOP

RUN

G3L-FUEA

07

COM

78

12

FG

PAU/REM

PROGRAMMABLE
CONTROLLER

78

X1

901

08
10

12G

MODE

02
04

DC IN

MODE

901

01

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

07

COM

+12V

X10

03
05

07

DC IN

00

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

5 6

0: [Link]
1: TEST1
2: TEST2

5 6

STOP

78

56

5 6
5 6

PAU/REM
RUN

FAULT

90 1

06

PROGRAMMABLE
CONTROLLER

PWR

TX/RX

90 1

90 1

[Link]

78

X1

TOKEN

2 34

56

2 34

02
04

RUN
STOP
REMOTE
FAIL
ERROR

LAS

78

MODE

2 34

01
03
05

G3L-EUEA

GM1-CPUA

GM3-PA1A

RUN

90 1

X10

G3L-FUEA

901

00

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

90 1

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

2 34

RUN
STOP
REMOTE
FAIL
ERROR

FAULT

56

G3L-EUEA

GM1-CPUA

PWR

TX/RX

901

0: [Link]
1: TEST1
2: TEST2

TOKEN

90 1

STOP

GM3-PA1A

RUN
LAS

78
78

901

PAU/REM
RUN

G3L-FUEA

2 34

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

MODE

PROGRAMMABLE
CONTROLLER

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR
10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

2 34

RUN
STOP
REMOTE
FAIL
ERROR

2 34

G3L-EUEA

GM1-CPUA

PWR

GLOFAPLC
PLC CC
IP:[Link]
[Link]

2 34

GM3-PA1A

PLC
B B
GLOFA
PLC
IP:[Link]
[Link]

2 34

GLOFAPLC
PLCA A
IP:[Link]
[Link]

30

CON2

31
COM

10BASE-T

+- DC24V

CON2

+- DC24V

RELAY
AC250V 2A
DC24V 2A

RELAY
AC250V 2A
DC24V 2A

Hub

Hub
G3L-EUEA

G3Q-RY4A

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR

RUN
CPU I/F RUN
FB-SERVECE
HS-SERVICE
GMWIN-SERVICE
GLOFA-SERVICE
FTP-SERVICE
H/W-ERROR

10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

10BASE5 ENABLE
10BASE2 ENABLE
10BASE-T LINK
10BASE-T PLRTY
TX
RX

TOKEN
TX/RX
FAULT

5 6

02

2 34

[Link]

78

X1

06
07
COM

DC IN

MODE

08
09
10

0: [Link]
1: TEST1
2: TEST2

90 1

5 6

05

5 67

5 6

X10

01
03
04

+12V

LAS

2 34

0: [Link]
1: TEST1
2: TEST2

00

90 1

STOP

90 1

PAU/REM

90 1

78

RUN

RUN

78

MODE

PROGRAMMABLE
CONTROLLER

G3L-FUEA

2 34

RUN
STOP
REMOTE
FAIL
ERROR

PWR

2 34

GM1-CPUA

GM3-PA1A

11

GLOFA

Desktop System

12

FG

14

13
15
COM

16
17
18
19
04

10BASE5

21

CON1

22
23
COM

08
25
26
27

HMI

Computer

Host
[Link]
IP:[Link]

12G

28

10BASE2

29
30
31
COM

10BASE-T

CON2

+- DC24V
RELAY
AC250V 2A
DC24V 2A

company
PLC D s
Other
[Link]
PLC D

GLOFAPLC
PLCEE
[Link]
IP:[Link]

[Fig.4.1.3] Ethernet System (Dedicated Network with Honeywells and Other Companys PLCs)

4-2

Chapter 4 System Configuration

4.1.4 Public Network and Dedicated Network system

Broadband
Monitoring System 1

Broadband
Monitoring System 2
HMI

HMI

Router or
Gateway

Public Network

PLC [A]
IP:[Link]

PLC [B]
IP:[Link]

PLC [C]
IP:[Link]

Router
or Gateway

Ethernet Network (Network 1)

HMI

HMI
Local Monitoring
System 1

Local Monitoring
System 2

[Fig.4.1.4] Ethernet System (Public Network + Dedicated Network)

4-3

Chapter 4 System Configuration

4.1.5 Public Network and Dedicated Network system composed of Honeywells

and other companys PLCs

Broadband
Monitoring System 1
HMI
PC

Broadband
Monitoring System 2
HMI
PC
Router
or Gateway

PLC A
IP:[Link]

PLC B
IP:[Link]

Public Network

PLC C
IP:[Link]

Router
or Gateway

Ethernet Network (Network 1)

HMI PC

Local Monitoring
System 1

HMI PC

Local Monitoring
System 2

Other company s PLC D

IP:[Link]

[Fig.4.1.5] Ethernet System (Public Network + Dedicated Network + Other Companys System)

4-4

Chapter 5 SoftMaster-PD Program

Chapter 5 SoftMaster-PD Program

In order to operate FEnet I/F module, SoftMaster-PD, a dedicated S/W for communication modules,
must be used to setup or manage parameters of communication modules including FEnet I/F module.
SoftMaster-PD is dedicated software to setup parameters and of communication modules such as
FEnet, Snet, Devicenet and Profibus-DP communication modules, manage and diagnose
communication modules.

5.1 Introduction
As a basic program tool needed to setup, control and manage the network in Ethernet communication,
SoftMaster-PD is used to setup and manage all of the communication parameters including system
parameters, service parameters, module and network diagnosis, etc.
With regard to Ethernet network, the functions of SoftMaster-PD can be mainly classified as follows;
1) Basic parameters setting of communication system,
2) Parameters setting of communication service (HS link, P2P, dedicated service)
3) Diagnosis service for module and network
Parameters and files the user has specified can be written (downloaded) on and read (uploaded) from
Ethernet communication module through CPU module. Since once downloaded communication system
parameters are managed by CPU, they can be directly used without resetting even if a new
communication module is installed on the initially specified position.
This chapter will focus on the description of settings necessary for the application of Ethernet module

5-1

Chapter 5 SoftMaster-PD Program

5.2 Basic Settings

5.2.1 Register of communication module
PLC type must be selected to establish connection between SoftMaster-PD and PLC.
Execute SoftMaster-PD by selecting [Tool] -> [Network Manager] on the menu of SoftMaster200 and SoftMaster-PD will be displayed with the initial screen shown in [Fig. 5.2.1].

1) Execution of SoftMaster-PD
When SoftMaster-PD is executed for the first time, the menu will be displayed as shown below.
The communication module must be registered on the applicable base and slot positions to
setup basic parameters. The communication module can be registered in online of offline status.

[Fig. 5.2.1] Initial screen of SoftMaster-PD

A) Register in off-line status
In order to register the communication module compulsorily without establishing connection
between SoftMaster-PD and PLC, select the applicable positions of base and slot on the
module settings window of SoftMaster-PD. If FEnet is to be registered on base 0 and slot 2,
select the applicable positions on the module settings window to display the Communication
Module Setting window, and select the communication module type of FEnet and then click
OK on the Communication Module Setting window.

5-2

Chapter 5 SoftMaster-PD Program

[Fig. 5.2.2] Module settings

FEnet module is registered on Slot 2 of Base 0 is as shown below;

[Fig. 5.2.3] Module registered

5-3

Chapter 5 SoftMaster-PD Program

B) Register in Online status
Connect SoftMaster-PD and PLC on which the communication module is installed. After
connection is completed, select [Online] -> [Read IO Information] to search for all the
communication modules installed on the applicable PLC in order to register the modules.

[Fig. 5.2.4] Read IO Information

If FEnet is installed on Slot 2 of Base 0, applicable communication module will be
automatically searched for and then registered as shown below;

[Fig. 5.2.5] Standard settings screen

At this time, if not identical to the module information registered in off-line status or in the
previous project, the following message will appear for the user to decide to update or not;

5-4

Chapter 5 SoftMaster-PD Program

[Fig. 5.2.6] Message window of IO changed

5.2.2 Standard settings (Module)

Standard settings is to specify communication system parameters necessary to control and
manage the Ethernet network, which will decide basic items such as FEnet I/F modules IP
address, subnet mask, gateway address, DNS server, reception latency time, number of
dedicated connections, host table setting, etc.
Thus, surely set basic parameters on the standard settings screen of the module window so to
download for the Ethernet communication.

[Fig. 5.2.7] shows specified basic parameters.

[Fig. 5.2.7] Standard settings (details)

5-5

Chapter 5 SoftMaster-PD Program

Details on the screen displayed in [Fig. 5.2.3] are as follows;
Among those details below, IP address, HS link station No. and media shall be reset appropriately
for the application environment.

1) TCP/IP setting
Classification
HS link station
No.

Description
Specify station No. for HS link communication between Honeywell PLCs FEnet
I/F modules, which shall not be duplicated identically to the correspondent
communication module.
Select media to use.
Z AUTO (electric) : automatically detects the module presently installed.
Z 10M/HALF : 10MBps Half Duplex electric

Media

IP address

Z 10M/FULL : 10MBps Full Duplex electric

Z 100M/HALF : 100MBps Half Duplex electric
Z 100M/FULL : 10MBps Full Duplex electric
Z FX/100M/HALF : 100MBps Half Duplex optical
Z FX/100M/FULL : 100MBps Full Duplex optical
Specify the IP Address of the applicable FEnet I/F module.

Subnet mask

Value necessary to check if destination station is on the same network of the

applicable station.

Gateway

IP address of Gateway or Router to transmit/receive data through the public

network or a network different from the network where the applicable FEnet
module is included.

DNS server
DHCP

Specify the IP address of domain name server.

Check DHCP option when not fixed but dynamic IP is to be used (ADSL).
If there is no request during the specified time from the host PC or MMI

Reception
latency time

Number of
dedicated

connected for dedicated communication, it will end the dedicated service

connection regardless of normal ending procedures supposing that the higher
level system is with error. This time is used in dedicated service to reset the
channel when any error occurs on the destination station or the cable is
disconnected.
Max. number of TCP dedicated services (1~16) accessible at a time.

connections

2) Driver (server) setting

Classification
MLDP server
Modbus TCP/IP server

Description
Set when operated as dedicated communication server (slave)
Set when operated as Modbus server driver (slave)

5-6

Chapter 5 SoftMaster-PD Program

3) Host table setting

Classification

Description
Access allowed to applicable module of IP address registered in host

Enable host table

table (unregistered client(IP address) is prohibited from connection

when enabled)

5-7

Chapter 5 SoftMaster-PD Program

5.3 HS Link Setting

5.3.1 Setting of HS link parameters
How to set HS link communication of FEnet I/F module will be described.

1) Initial selection screen

A) Select HS Link window. (click HS link window of SoftMaster-PD)

[Fig. 5.3.1] HS link screen

B) Specify the communication module (double-click HS link 1)

[Fig. 5.3.2] Setting of communication module and communication period

5-8

Chapter 5 SoftMaster-PD Program

Classification

Description

Module type
Communication
module settings
Communication
period settings

Select FEnet.

Base No.

Select Base No. the module is installed on.

Slot No.

Select Slot No. the module is installed on.

Period type

Set the data transmission period.

(available range is 20ms~10sec)

A) Screen after communication module settings

[Fig. 5.3.3] Communication module settings

2) HS link parameters settings (double-click HS link parameters window)

[Fig. 5.3.4] HS link block settings

5-9

Chapter 5 SoftMaster-PD Program

Classification
Station type
Station No.
Block type
Block No.
Read area
Save area

Description

Master
Slave
Native station
No.

Specify Master/Slave of FEnet.

This module to transmit, the correspondent module to receive.

Transmit

Transmits data.

Receive

Receives data.

Block No.

Specify Tx Block and Rx Block.

Address

Memory area of this module

Size (Word)

Specify data size to transmit.

Address
Size (Word)

Area to save data received from the destination station.

Specify data size to receive.

Check applicable HS link on the HS link parameters Write screen and click Confirm.

3) HS link parameters Read

A) Connect with CPU.
B) After connection is established, select Parameters Read in Online menu, check applicable
parameters and then click confirm so to read standard settings and HS link parameters
specified.

5-10

Chapter 5 SoftMaster-PD Program

5.4 P2P Setting

5.4.1 P2P parameters
P2P setting of FEnet I/F module will be described.

1) P2P parameters setting

Select P2P parameters window (click P2P of SoftMaster-PD) to display the menu as shown
below in [Fig.5.4.1]. Up to 8 is available for P2P setting based on the number of FEnet I/F modules
installed.

[Fig. 5.4.1] Screen of initial P2P settings

2) Standard settings of communication module

Click the menu for P2P parameters setting displaying the following menu to select the type of
applicable communication module. In this case, select FEnet. And then specify base No. and
slot No. the applicable module will be installed on.

[Fig. 5.4.2] Selection of communication module

5-11

Chapter 5 SoftMaster-PD Program

[Fig. 5.4.3] P2P setting details

After communication module setting is completed, P2P setting details screen will be displayed
as in [Fig. 5.4.3]. Refer to Chapter 7 P2P Service for detailed setting.

Classification
P2P
channel

Description

User defined frame

Edit the user defined protocol.

MLDP client

Set dedicated service master.

Modbus TCP client

P2P Block
User defined frame
E-mail

Set to Modbus TCP master.

Set each command block based on specified MLDP
client of P2P channel.
Set each command frame for the user defined frame of
P2P channel.
Execute as defined by the user for E-mail service.

5-12

Chapter 5 SoftMaster-PD Program

5.5 Connect and Download to Communication Module

5.5.1 Download/Upload
SoftMaster-PD can be used for downloading (writing) specified parameters or uploading
(reading) the parameters stored in the PLC.

1) PLC Type Settings.

To establish connection between SoftMaster-PD and PLC, PLC type must be selected prior to
connect. Click [Option] [PLC Type Settings] to select the PLC Type.

[Fig. 5.5.1] Option menu of SoftMaster-PD.

There are 4 selections of 2MLK CPUH, 2MLK CPUS.

Confirm the type of PLC CPU to connect with SoftMaster-PD, select the exact type of CPU in
the PLC Type Setting dialog box as depicted in the Fig. 5.5.2.

[Fig. 5.5.2 PLC Type Settings.

5-13

Chapter 5 SoftMaster-PD Program

2) Write (download)
Connect with CPU of the basic base FEnet I/F module installed on whose parameters are
desired to write through [Online] -> [Connect] menu.

[Fig. 5.5.3 Connect Screen

After connection is established, select [Online] -> [Write Parameter (standard settings, HS link,
P2P)] to display [Fig. 5.5.4] screen, where to specify standard settings items of the base and slot
positions FEnet I/F module to write (download) is installed on.
Notes
1) SoftMaster-PD can be programmed through RS-232C port or USB port of CPU module.
Refer to CPU modules connection diagram for detailed cable type.

[Fig. 5.5.4] Parameter Write window

5-14

Chapter 5 SoftMaster-PD Program

[Fig. 5.5.4] Write screen

After all the procedures above completed, it means that Write frame files is normally completed,
however the parameters value present FEnet I/F module operates with is previously
downloaded one, which shall be surely powered again or reset after downloaded for normal
operation. If not, the operation will be kept with the old value.

3) Read (upload)
Connect with CPU of the basic base FEnet I/F module to read is installed on, and register the
communication module to read standard settings.

[Fig. 5.5.5] Read Parameter window

5-15

Chapter 5 SoftMaster-PD Program

After connected, select [Online] -> [Read Parameter (standard settings, HS link, P2P)] to display
[Fig. 5.5.6] screen.

[Fig. 5.5.6] Parameter Read menu

Where, confirm Base No. and Slot No. among the standard settings items, and then select
standard settings of the applicable communication module.
After Read is completed, confirm edit/standard settings of the SoftMaster-PD screen to find the
data read from FEnet module saved.

5.5.2 Link Enable

Link enable procedures are necessary to start the operation of the communication for actual
Tx/Rx of downloaded HS link and P2P data through SoftMaster-PD. Let Link Enable ON to start
Tx/Rx service of the communication module, which will enable or disenable the operation
relationship separately from the specified parameters, where the communication will be kept on
based on the Enable conditions even if CPU stops.

The next is to specify SoftMaster-PD for the Enable conditions. Click the setting menu on [Fig.
5.5.6] to display [Fig. 5.2.8]. Check the items which need the link service.

5-16

Chapter 5 SoftMaster-PD Program

[Fig. 5.5.7] Enable Link setting

[Fig. 5.5.8] Selection of Link Enable

If Link Enable Write is executed, a message will be displayed as in [Fig. 5.5.9], which means that
Link is normally enabled.

[Fig. 5.5.9] Message Screen of Link Enable

5-17

Chapter 5 SoftMaster-PD Program

5.6 System Diagnosis

System Diagnosis function is used to display general service status and information of the
communication module in Online status including link type, link information and O/S version so to
allow the user to precisely diagnose and debug the data Tx/Rx relation of the communication module
presently used.

5.6.1 Execution of the diagnosis function

Run SoftMaster-PD to connect with and then select [Online] -> [System Diagnosis] to display
[Fig. 5.6. 2], which shows base and slot information the present module is installed on and the
operation status.

[Fig. 5.6.1] Selection of system diagnosis function

5-18

Chapter 5 SoftMaster-PD Program

[Fig. 5.6.2] Module information of system diagnosis

5.6.2 Type of diagnosis functions

Through the pop-up menu as in the initial diagnosis screen [Fig. 5.6.2], system status can be
diagnosed for the various communication modules. Main functions for each item are as described
below in [Table 5.6.1].

[Fig. 5.6.3] Diagnosis function pop-up of module

5-19

Chapter 5 SoftMaster-PD Program

Classification
CPU status
Communication
module information
Status by service
Media information
Ping test
Log
Autoscan

Description
Displays presently connected CPUs type, operation status and error/
warning if any.
Displays

communication

modules

basic

information,

H/W

and

communication status.
Displays the status of dedicated communication, P2P, HS link service,
etc.
Provides packet information of Tx/Rx data through media.
Displays port connection status of other station specified on the network.
Saves log value of errors.
Provides active IP information for all the modules specified on the present
network.
[Table 5.6.1] Detailed diagnosis services

1) Information of communication module

Information of communication module shows basic information such as base information, HS
link station No., IP information, etc. in addition to media and start status of the communication
service, through which the user can confirm that the communication module normally transmits
and receives the data.

[Fig. 5.6.4] Information of communication module

5-20

Chapter 5 SoftMaster-PD Program

2) Service status
Service status of the communication module is classified into 3 (dedicated communication, P2P
and HS link), which show detailed information on the respective communication services.
A) Dedicated service
Displays the service status of MMI or HMI dedicated protocol by means of higher client, and
monitors Tx/Rx data and errors of the specified IP.

[Fig. 5.6.5] Dedicated service monitor

B) P2P service
Displays detailed information on the user defined service executed, and checks normal service
to read if P2P parameters are set and enabled, where real time monitoring is available with
Individual Read or Continuous Read specified on the menu.

[Fig. 5.6.6] P2P service monitor

5-21

Chapter 5 SoftMaster-PD Program

C) HS link service
Monitors flags of respective parameters for HS link setting data. Run link, link trouble and
individual information can be all monitored by HS link service.

[Fig. 5.6.7] HS link service monitor

3) Media information
Displays the packet information input through the media.

[Fig. 5.6.8] Media information

5-22

Chapter 5 SoftMaster-PD Program

4) Ping Test

[Fig. 5.6.9] PING test monitor for destination station

5) Log
A) Running Log
Displays the initial operation status of the communication module.

[Fig. 5.6.10] Running log screen

5-23

Chapter 5 SoftMaster-PD Program

B) System Log
Saves and displays service error status during communication service. In case an abnormal
communication error occurs, debugging is available through this log.

[Fig. 5.6.11] System log screen

6) AutoScan
Displays the link interface status of the whole network. The service status of FEnet I/F module
connected with the public network is displayed as simple as shown in the diagram.

[Fig. 5.6.12] Network Autoscan

5-24

Chapter 6 HS Link Service

Chapter 6 HS Link Service

6.1 Introduction
HS link is a communication method between MasterLogic-200 PLC communication modules to send
and receive data with HS link parameters setting, which can also allow the user to use SoftMaster-PD
to exchange data with parameters setting of Send/Receive data size, communication period,
Send/Receive area and area to save through its data transmission service function.
However, since HS link service uses the subnet broad service, it may have an influence on other
communication modules which use the identical network. Thus, setting block size as near to the
maximum Send/Receive size (400 bytes or 200 words) as available per HS link block is recommended
for the user to obtain the greatest communication efficiency with the lowest influence on other modules
so to reduce the sum of blocks. In order to make use of all functions, surely specify the basic
communication parameters in the status of communication available.
HS link functions are specified as below;

1) HS link block setting function

(1) If there are many Send/Receive areas, up to 128 blocks can be setup.
(2) 200 words are available for a block.
2) Communication period setting function
Send/Receive period can be setup per block by user for the areas where especially fast Tx/Rx
is required and not required respectively in a Tx/Rx period of 20ms to 10 sec.
3) Send/Receive area setting function
Send/Receive area can be setup per data block by user according to memory address
specified.
4) Providing function of HS link information
Reliable communication system can be easily configured by providing HS link information for
user via the user keyword.
[Table 6.1.1] shows the data capacity of HS link communication whose basic unit is 1 word.
Classification Max. communication words
2MLL-EFMT

Max. Send words Max. blocks Max. words per block

25,600

12,800

128 (0-127)

[Table 6.1.1] Max. communication data capacity

6-1

200

Chapter 6 HS Link Service

6.2 HS link Send/Receive Data Processing

HS link application will be described below with the example where FEnet I/F modules of the stations
No.0 and No.1 are to send and receive the data between each other.
The station No.0 transmits the data of 10 words from M000 to M009 word with block No.0 and the
received data, transmitted by the station No.1, is saved on M010. The station No.1 receives data of 10
words from the station No.0 to save on M030, and transmits the data of 10 words from M020 to M029
word with block No.1 .
There are 64 blocks for Send data and 128 blocks for Rx data in the HS link parameters. The block
number can be set 0~63 for transmission or 0~127 for receiving. The Send side needs only to decide
which data to read and which block number to send to without setting the destination station No. when
transmitting the data is setup.

Station 0

Station type : Local

Mode: Send/Receive
Block No. : 0, 1
Area to read : M000

Station 1

Block 0

Block 0

Block 1

Block 1

Station type: Local

Mode: Send/Receive
Block No.: 0, 1
Area to read : M020
Area to save : M030
Communication Period:
200ms
Size:10

Area to save : M010

Communication Period:
200ms
Size:10

[Table 6.2.1] Diagram of HS link processing blocks

6-2

Chapter 6 HS Link Service

6.3 Operation Sequence through HS link

Set basic parameters
1

Use SoftMaster-PD
Select HS link

HS link setting window

Select HS link parameters

HS link 1~12
Set communication module

Module type
~ FEnet

Base No.(0~7)

Slot No.(0~11)

Set communication period

7

20ms~10S

Set HS link block (register list)

8
9
10

Station type

Specify and download the basic parameters such

HS link station No., media, IP address, etc. Reset
the PLC to apply downloaded basic parameters.

Open HS link setting window of SoftMaster-PD

Select HS link number.

(1 HS link number is available for 1 communication
module)

Input network type and base and slot No. where

communication module is installed.

Select the networks Send period

(20ms~10sec)

1. Self-station No. for Send blocks (auto

Correspondent station No. for Receive blocks

~ Master
Station No.(0~63)

2. Totally, 128 blocks are available. Send/Receive

Block type

data sorted out by station No. and block No. of

~ Send or ~ Receive

each other.

11

Block No.(0~63)

12

Read area/Save area

13

Size (1~200 words)

3. Self-stations area to read for Send, Selfstations area to save the received data for
Receive

Online (after local-connected )

14

Write
~HS link parameters
Set link enable

HS link1~12

Download HS link parameters from SoftMaster-PD

onto CPU

Set link-enable for the applicable HS link number

to be started the HS link service with SoftMasterPD

Setup the parameters for

correspondent station as in
1~15 above

6-3

Chapter 6 HS Link Service

6.4 HS link parameters setting

HS link parameters shall be setup by the means of setup respective items for HS link after selecting
HS link parameter number on the Hs link screen of SoftMaster-PD. The setting steps and the
functions of respective items are explained below.

6.4.1 Execution of SoftMaster-PD

The initial screen of SoftMaster-PD will be displayed as shown below [Fig. 6.4.1] when
SoftMaster-PD is executed.
Click [Tool] - [Network Manager] on the menu bar of SoftMaster-200 to execute SoftMaster-PD.

[Fig. 6.4.1] Initial screen of SoftMaster-PD

6.4.2 Standard settings (Module)

1) Setting the communication module
Communication module setting can be registered via off-line or Online.
Refer to Chapter 5 SoftMaster-PD program for more details.

2) Downloading standard settings

Select [Online] - [Write Parameter] to open the Write parameter window of [Fig. 6.4.2]. Check
applicable standard settings and click [OK] button.
After standard settings are downloaded, surely let PLC power turn off and on or reset. If the
communication module is not reset, the new communication parameters information will not be
applied.

6-4

Chapter 6 HS Link Service

[Fig. 6.4.2] Write Parameter window

6.4.3 High Speed Link Parameters (HS Link)

1) Initial screen setting of HS link parameters
Select HS Link window of SoftMaster-PD to display the window where HS link parameters can
be setup. 12 HS links are available for MasterLogic-200 series PLC. And parameters setting are
available for the communication modules installed on the basic or extended base.

[Fig. 6.4.3] Initial screen of HS link settings

2) Communication Module Settings and Communication period settings.

Double-click one of the HS links 01~12 on the [Fig.6.4.3] screen to open the Communication
Module setting dialog box depicted in [Fig. 6.4.4] to setup communication module and
communication period.

6-5

Chapter 6 HS Link Service

[Fig. 6.4.4] Communication module setting.

Setup the applicable communication module and communication period on the dialog box.

Item
Communication
module settings

Communication
period settings

Description
Module type

Select the installed communication module type.

Base No.

Select the base number where applicable FEnet module is installed.

Slot No.

Select the slot number where applicable FEnet module is installed.

- HS link service is used to send and receive data by user defined
parameters when the execution of PLC program is ended. Thus, if
the scan time of PLC program is as short as or less, the
communication data will be increased since the communication
module sends data at the end of every scan, which will cause
decreased efficiency of the whole communication system. In

Period type

order to prevent this, the communication is controlled by the

specified communication period whose setting range is 20 ~
10sec, which will be automatically set to default of 200 if not
specified.
- The communication period will be applied for Send blocks.
- The communication period will be applied identically to all the
Send blocks included in the same HS link parameter number.

[Table6.4.2] Setting of communication module and communication period

3) HS link parameters settings

Click [OK] on [Fig.6.4.4] screen to display [Fig.6.4.5] of HS link block registration window.

6-6

Chapter 6 HS Link Service

[Fig. 6.4.5] HS link block selection screen.

4) Setting of HS link blocks

Double-click the left mouse button on the HS link block registration window to open [Fig.6.4.6]
screen to register HS link blocks.

[Fig. 6.4.6] HS link block settings.

6-7

Chapter 6 HS Link Service

Classification
Station type

Master

Native/
Station No.

Destination
Station No.

Description
FEnet I/F module operates as master. Slave function is not supported.
Automatically, The HS link station number of self-station will be setup
for Send blocks. Setup the HS link station number of correspondent
station for Receive blocks. Available station No. for HS link with FEnet
I/F module is 0~63.
Duplicated number is not allowed for station numbers of FEnet I/F
modules included in the identical network since it is a specific number
to discriminate FEnet I/F modules in the network system.
The data memory address where the data to be transmitted is stored.

Read area

Address

(Available memory area: P, M, K, F, T, C, U, Z, L, N, D, R, ZR)

Refer to the list of device in the 2MLK CPU manual for available range
of each memory area.

Size (Word)
Block type
Block No.

The size of data to be transmitted in word unit.

Send

Transmits data.

Receive

Receives data.

Block No.

Used to specify Send/Receive blocks.

The data memory address to save the received data which is
transmitted by the destination station.

Save area

Address

(Available memory area: P, M, K, F, T, C, U, Z, L, N, D, R, ZR)

Refer to the list of device in the 2MLK CPU manual for available range
of each memory area.

Size Word)

The data size of received block in word unit.

[Table 6.4.3] HS link settings

5) Downloading HS link parameters.

After HS link parameters setting is complete, select [Online] - [Write Parameter (standard
settings, HS link, P2P)] on SoftMaster-PD, check applicable HS link and then click [OK].

[Fig. 6.4.7] Write Parameters Screen

6-8

Chapter 6 HS Link Service

6) HS link parameters enable
Select [Online] - [Link Enable] on SoftMaster-PD, check applicable HS link and click [Write]. If
HS link enabled, HS LED will be turned ON on the modules LED display to start HS link.

[Fig. 6.4.8] Link Enable Screen

6-9

Chapter 6 HS Link Service

6.5 HS Link Information

6.5.1 HS Link Flags
When HS link service is used to exchange data between communication modules of two or more
stations, it provides a checking method of HS link service status for the user through HS link
information so to confirm reliability of the data read from the destination station via the HS link. In
other words, the communication module synthesizes the data received up to that time at intervals
of a specific time and lets the user know if HS link is operated as in parameters specified by the
user through HS link information where the whole information of Run-link(_HSxRLINK) and Linktrouble(_HSxLTRBL) to provide the whole information of the communication, and the individual
information of _HSxSTATE, _HSxTRX, _HSxMOD and _HSxERR to provide communication status for
registered items in the parameters are contained. The user can use the information in keyword
format when programming, and also monitor the HS link status using the monitor function of the HS
link information. Prior to its application, the user is requested to check the reliability of the
communication data through HS link information of Run-link and Link-trouble when operating
several PLCs with HS link service. [Table 6.5.1] shows the functions and definition of the HS link
information.

Classification
Information type

Keyword name
(x=HS link No.)
Data type

Run-link

Link-trouble

Whole

Whole

Individual

information

information

information

_HSxRLINK _HSxLTRBL
Bit

Bit

Tx/Rx status Operation Mode

Error

HS link status

Individual

Individual

Individual

information

information

information

_HSxTRX[n] _HSxMOD[n] _HSxERR[n] _HSxSTATE[n]

(n=0~127)

(n=0~127)

(n=0.~127)

(n=0~127)

Bit-Array

Bit-Array

Bit-Array

Bit-Array

Monitor

Available

Available

Available

Available

Available

Available

Program

Available

Available

Available

Available

Available

Available

[Table 6.5.1] The definition of HS link information.

Select [Variable/Comment] on the SoftMaster-200 project window to display [Fig. 6.5.1] as shown
below. From this window drag the device to be monitored on to the variable monitor window.

6-10

Chapter 6 HS Link Service

[Fig. 6.5.1] Variable monitor window

1) Run-link (_HSxRLINK)
As the whole information it shows if HS link is normally executed through the user defined
parameters, whose status will be kept On if once On until Link Enable is Off, and also will be
On under the conditions specified below.
A) If Link Enable is On.
B) If all the register list settings of parameters are specified normally.
C) If all the data applicable to the parameters register list is transmitted and received as
specified in the period.
D) If the status of all the destination stations specified in the parameters is Run and with no
error at the same time.

2) Link-trouble (_HSxLTRBL where x is HS link No.(1~12))

As the whole information it shows if HS link is normally executed through the user defined
parameters, which will be turned On if condition to be turned On the Run-link flag is violated
when Run-link is On, and will be turned Off if the condition is recovered.

3) Tx/Rx status (_HSxTRX[0..127] where x is HS link No.(1~12))

As individual information it shows the operation status of HS link parameters on the register list
up to 128 registered items Tx/Rx information. If the Tx/Rx operation of the registered items is
agreeable to the Tx/Rx period, the applicable bit will be turned On, and if not, it will be turned Off.

6-11

Chapter 6 HS Link Service

4) Operation mode (_HSxMODE[0..127] where x is HS link No.(1~12))

As individual information it shows the operation status of HS link parameters on the register list
up to 128 registered items operation mode information just like the max. register number. If the
station specified in the register item is in Run mode, the applicable bit will be turned On, and if in
Stop/Pause/Debug mode, it will be turned Off.

5) Error (_HSxERR[0..127] where x is HS link No.(1~12))

As individual information it shows the operation status of HS link parameters on the register list
up to 128 registered items error information just like the max. register number. The error
displays the general status of the PLC which fails to execute the user program. If the destination
station PLC is normal, it will be turned Off, and if abnormal, it will be turned On.

6) HS link status (_HSxSTATE[0..127] where x is HS link No.(1~12))

As individual information it shows the operation status of HS link parameters on the register list
up to 127 registered items HS link status just like the max. register number, which synthesizes
the information of the individual items to display the general information of the registered items.
In other words, if the applicable lists Tx/Rx status is normal with the operation mode of Run and
with no error, it will be turned On, and if the conditions above are violated, it will be turned Off.

6.5.2 Monitor of HS link information

HS link information can be checked through the variable monitor on the monitor menu when
SoftMaster-200 is Online state, or through the SoftMaster-PD diagnosis service.

1) Variable monitor
Variable monitor is a function to register the variables to be monitored and monitor the selected
variables. Select [View] - [Variable Monitor Window] to display the variable registration screen
as shown in [Fig. 6.5.1], and there select [Flag] directly to select and register HS link information
flag one by one on the screen of the variable flags list. At this time, since _HSxSTATE[n],
_HSxERR[n], _HSxMOD[n] and _HSxTRX[n] are the flags of array type, the user needs directly
to select the array numbers which stand for the register numbers inside the parameters.

2) HS link monitor from the SoftMaster-PD diagnosis services

A) It will be available through the menu [Connect] -> [Online] -> [System Diagnosis] on
SoftMaster-PD.

6-12

Chapter 6 HS Link Service

[Fig. 6.5.2] System Diagnosis

Item

Description

Link type

Displays communication module type.

Option type

Displays media type of communication module.

H/W status

Displays H/W status.

H/W version

Displays H/W version.

OS version

Displays OS version.

OS date

Displays OS released date.

Remote connection status

Displays remote connection status.

6-13

Chapter 6 HS Link Service

3) With the mouse cursor placed on the applicable module, click the right button of the mouse and
select Status for Respective Services to open [Fig. 6.5.3] screen as shown below.

[Fig. 6.5.3] SoftMaster-PD Diagnosis Services (status for respective services)

6-14

Chapter 7 P2P Service

Chapter 7 P2P Service

7.1 Introduction
7.1.1 Introduction to P2P service
P2P service executes Master operation of the communication module as realized with
parameters setting which was with function blocks (command). 6 P2P commands available in
FEnet I/F module are Read, Write, Send, Receive, ESend and EReceive.
P2P services registration and edit is executed in SoftMaster-PD where up to 8 P2P
parameters can be setup. Respective P2P parameter is composed of up to 64 P2P blocks.
[Fig. 7.1.1] shows an example of P2P parameters setting window in SoftMaster-PD.

[Fig. 7.1.1] Setting window of SoftMaster-PDs P2P parameters

1) P2P parameters registration window
Up to 8 P2P parameters can be setup.

Multiple P2P parameters can be setup for an identical communication module

- However, Enable is available only for 1 parameter among the multiple P2P parameters
for the identical communication module
Respective P2P parameter is composed of P2P channel, P2P block, user defined frame
and e-mail.

2) P2P edit window

Up to 64 P2P blocks can be registered and edited.
Separate frame registration is available for respective drivers.

7-1

Chapter 7 P2P Service

7.1.2 Configuration of P2P parameters

In order to use P2P service the user needs to execute setting for the operation desired on the
P2P parameters window. Specify type, base and slot as desired on the P2P screen to display
P2P parameters setting screen composed of 4 kinds of information as shown in the figure below;

[Fig. 7.1.2] P2P parameters module setting

[Fig. 7.1.3] Setting and registration screen of P2P parameters

7-2

Chapter 7 P2P Service

1) P2P channel
Logical channel of P2P Service (IP, PORT, dedicated driver) to be executed can be setup.
User defined frame, MLDP client and MODBUS TCP client setting available
Communication device setting available which uses other protocol than MLDP/MODBUS TCP
2) P2P block
64 P2P blocks setting separately operated
3) Define user frame
Registration of user defined frames
4) E-mail
Frame registration to transmit and receive e-mail frames

7-3

Chapter 7 P2P Service

7.2 Type of P2P Service

7.2.1 Type of P2P Commands
1) P2P commands.
6 commands are available for programming P2P communication service, and each command
will be used with different purpose according to respective service methods as described in the
table below, for reference.
Classification
MLDP CLIENT

USER DEFINE

Command
Read

Reads the area specified by destination station.

Write

Transmits native stations area data to destination station.

Send

Transmits native stations area data to destination station.

Receive
MODBUS TCP

E-mail

Purpose

Saves the data received from destination station.

Read

Reads the area specified by destination station.

Write

Transmits native stations area data to destination station.

ESend

Transmits a message if an event occurs.

EReceive

Receives a message if an event occurs.

[Table 7.2.1] Type of P2P commands

7.2.2 Type of P2P Service

1) MLDP CLIENT.
MLDP CLIENT service is used to communicate between MasterLogic-200 FEnet I/F modules.
Through its own protocol built-in without additionally defined frame, the user can specify
communication settings simply with basic settings of channel, data type (BIT, BYTE, WORD,
etc.) and memory area. Use port No.2004 for TCP, and port No.2005 for UDP protocol.
2) User Defined Frame.
This service is used to communicate between MasterLogic-200 FEnet I/F module and other
companys Ethernet devices. Since the communication protocol of devices based on Ethernet is
differently defined by different makers, all kinds of communication drivers can not be provided
for respective device. Thus, the user is allowed to edit appropriately to the characteristics of the
applicable communication module, for which the user needs to specify User Defined Frame and
then define the Ethernet users frames with basic structure composed of Header, Body and Tail.
Up to 16 channels can be specified.
3) MODBUS TCP
MasterLogic-200 FEnet supports Modbus protocol widely used as of now as well as User
Defined protocol.

7-4

Chapter 7 P2P Service

7.3 How to Set P2P Service

7.3.1 Ethernet (server) driver
1) Driver setting
Ethernet(server) driver stands for the protocol built-in MasterLogic-200 FEnet module. 2 kinds of
server protocol, MLDP server and MODBUS TCP/IP, are built-in MasterLogic-200 FEnet I/F
module. Ethernet(server) driver can be used to communicate between Ethernet devices with
MLDP or MODBUS TCP/IP protocol. The destination station in Ethernet communication system
is generally MMI (or HMI), where communication is available with the correspondent device only
through parameters setting without additional communication programming by user. [Fig. 7.3.1]
shows the typical example of communication with MMI PC with Ethernet driver used, where
FEnet responds if MMI PC requests to read or write data.
HMI
MasterLogic-200

Data Read/Write Response

(MasterLogic-200/Modbus)

Ethernet
Data Read/Write Response
(MLDP/Modbus)

[Fig. 7.3.1] Example of Ethernet (server) driver application

2) Type of Ethernet (server) drivers

Driver types available are as specified below;
Type

Description

MLDP server

MasterLogic-200 FEnet dedicated protocol by Honeywell

MODBUS TCP/IP server

Open type of protocol by Modicon

[Table 7.3.1] Types of Ethernet (server) drivers

Notes
1) The number of drivers is changeable according to specified Ethernet channel.
Be careful! If Ethernet channel is specified, the number of drivers available will be decreased
as many as specified.
2) Ethernet (server) driver supports 1:N communication, where accordingly, several master
devices can take data through a specified port connected with.

7-5

Chapter 7 P2P Service

7.3.2 P2P Channel
Ethernet P2P channel is used when MasterLogic-200 FEnet I/F module executes the master
function of communication with built-in MLDP protocol or user defined protocol.

Ethernet Device

[Fig. 7.3.2] Application of P2P channel information

1) Setting of P2P channel

FEnet I/F module can send and receive data using up to 16 channels, which is composed of IP
address and port No. for two Ethernet devices. The number of channels available for P2P
service is the maximum number of channels (16) minus the number of dedicated connections in
the basic parameters (The number of P2P channels = 16 the number of dedicated
connections).
P2P communication is available with simple parameters setting to communicate with the device
using MLDP or MODBUS TCP protocol for users convenience. And for the communication with
other devices than described above, user can directly define frames as necessary.
In addition, messages and e-mail addresses can be registered to transmit and receive e-mail
frames (ASCII supports).
However, it is not necessary to set the channel for e-mail communication.
If P2P channel is selected on the P2P setting window, the P2P channel setting window will appear
as follows:

[Fig. 7.3.3] P2P channel settings window.

7-6

Chapter 7 P2P Service

If the desired port is selected, P2P channel settings window will appear for the user to define
P2P driver type applicable for the port.

[Fig. 7.3.4] P2P driver client setting

Drivers and details available in MasterLogic-200 FEnet I/F are as follows;

Drivers

Details

None

P2P service not used

Define user frame

Used to send/receive data with user defined frame.

MLDP client

Used to send/receive data with MasterLogic dedicated protocol.

Modbus TCP client

Used to send/receive data with Modbus/TCP protocol.

[Table 7.3.2] Type of P2P driver clients

If MLDP or Modbus is selected as P2P driver type for the communication port, user defined
frame can not be registered.

7-7

Chapter 7 P2P Service

A) How to use Modbus driver
[Table 7.3.3] displays commands and addresses of Modbus devices.

Code

Function code name

Modicon PLC
data address

Remarks

01

Output Contact Status Read (Read Coil Status)

0XXXX(bit-output)

Bit Read

02

Input Contact Status Read (Read Input Status)

1XXXX(bit-input)

Bit Read

03

Output Register Read (Read Holding Registers)

4XXXX(word-output)

Word Read

04

Input Registers Read (Read Input Registers).

3XXXX(word-input)

Word Read

05

Output Contact 1 Bit Write (Force Single Coil)

0XXXX(bit-output)

Bit Write

06

Output Register 1 Word Write

4XXXX(word-output)

(Preset Single Register)

15

Output Contact Continuous Write (Force Multiple

0XXXX(bit-output)
Coils)

16

Output Register
Multiple Register)

Continuous

Write

(Preset

4XXXX(word-output)

Word Write
Bit Write
Word Write

[Table 7.3.3] Modbus TCP address MAP

2) P2P channel settings

In order to use P2P service, the channel shall be set first and then IP address of the device to
communicate with.
[Fig. 7.3.5] shows the setting menu of the Modbus channel.

[Fig. 7.3.5] Setting example of Modbus TCP channel

7-8

Chapter 7 P2P Service

Details of the driver setting items are as described below.

Item

Description
None

User defined frame

P2P
driver

MLDP client

Modbus TCP
client

Not specified
User defined frame is used as communication protocol.
The MasterLogic dedicated protocol is used as communication
protocol.
Since MLDP is built-in, the user defined frame is needless to be
registered.
The Modbus TCP protocol is used as communication protocol.
Since Modbus TCP protocol is built-in, the user defined frame is
needless to be registered.

TCP/UDP

Select between TCP/UDP. If MODBUS is selected, TCP will be

fixed.

Client/Server

Select between Client/Server. If the protocol is selected between

MLDP/Modbus TCP, Client will be fixed.
(The module is operated as master of communication)

Destination station port

Input the port No. of the destination station.

If the protocol of the user defined frame is to be defined, specify
an optional port No. whose available range is H400~H1024.
However, MLDP client will be fixed to 2004, and Modbus TCP
client to 502.

IP address of counterpart

Input IP address of the correspondent device to communicate

with MasterLogic-200 FEnet through the specified channel.

Notes
1) IP address of the destination station
If MLDP is the client, surely specify IP address of the server equipment. If a dynamic IP address
has been assigned to the server by means of DHCP, the communication will be unavailable due
to different IP from specified. Thus, surely a fixed IP address shall be assigned. If DHCP is used
for server equipment, the communication will be unavailable.

7-9

Chapter 7 P2P Service

7.3.3 Define User Frame

Send/Receive frames must be defined if there are frames to be sent or received whose structure
is different from the structure of MLDP dedicated frame or Modbus TCP frames in the network.
This is available only in P2P service.
All the frames are composed of Header, Data and Tail which can be omitted respectively.
In MLDP, user defined frames are displayed with group name and frame name whose details are
as follows;

1) Group
A) Group of frames with identical header and tail.
B) Group registration surely necessary for the frame registration.

2) Frame
A) Composed of Header, Body and Tail
B) Send/Receive frame shall be defined
C) Fixed and Variable size variables can be added to Body
D) Frame is composed of lots of segments, and up to 4 variable segments can be registered
for a Body.

3) Type of segments
Header, Body and Tail of the frame are composed of lots of segments, which can be registered
on the frame edit window as below.

[Fig. 7.3.6] Register of Segments

Segments used to configure the frame are numerical constant, String Constant, Fixed or
Variable size variables.

7-10

Chapter 7 P2P Service

[Fig. 7.3.7] Add Segment screen

A) Numerical constant
The part to be fixed as Constant shall be defined among frames, with the value of the data item
specified in hexadecimal.

[Fig. 7.3.8] Numeric constant to select and input

B) String Constant
String Constant shall be registered among frames, with the value of the data item specified in
ASCII code.

[Fig. 7.3.9] String Constant to select and register

7-11

Chapter 7 P2P Service

C) Fix sized variable

It is available only in the Body area of the frame, and used to process data whose size is as
long as defined value (size is of Byte). Check Assign Memory to read data from PLC memory
when send frame is registered and save the received data on PLC Memory when receive
frame is registered. Conversion and swap processing are available for the data when FEnet
module read data from PLC memory or save data on PLC memory.

[Fig. 7.3.10] Fix sized Variable to select and register

D) Variable sized variable
(1) Available in the Body area of the frame
(2) Send Frame
Used to change the length of frame.
Check Assign Memory to configure the send frame with the data read from PLC memory.
(3) Receive Frame
a) Used to process the Variable sized data among the received frames.
b) Registration available only in the last segment in the Body area.
Check Assign Memory to save the data for the applicable segment among the
received frames. (Swap and conversion are available)

[Fig. 7.3.11] Variable sized variable to select and register

7-12

Chapter 7 P2P Service

(4) Data Conversion Processing

In order to convert data from Hexadecimal to ASCII code when frames are sent and
received, or execute Byte swap, the applicable setting shall be specified on the frame edit
window.
a) Conversion
Hex To ASCII
Send: converts read data from PLC memory to ASCII code so to configure send frame.
Receive: converts received data to ASCII so to save.
ASCII To Hex
Send: converts read data from PLC memory to Hexadecimal code so to configure
send frame.
Receive: converts received ASCII code data to Hexadecimal code so to save.

[Fig. 7.3.12] Data processing method to select

If 2 Words of PLC memory, MW100/101, are used for Send frame configuration,
and the ASCII code 0x34353637 is saved on MW100/101, the applicable segment
of the send frame will be filled with hexadecimal number 4567, when Hex To
ASCII is selected.
And when some of the received frames are saved as converted to Hex, 0x3435
3637 will be saved on PLC memory, if the value of applicable area is 4567.
b) SWAP
2 Bytes : 2 Bytes swap of applicable part among Send/Receive frames
4 Bytes : 4 Bytes swap of applicable part among Send/Receive frames

8 Bytes : 8 Bytes swap of applicable part among Send/Receive frames

If 0x1234567811223344 is converted by respective methods above, its results are

as follows;
-

2 Bytes swap : 0x3412785622114433

4 Bytes swap : 7856341244332211
8 Bytes swap : 4433221178563412

7-13

Chapter 7 P2P Service

7.3.4 P2P block

If P2P block of applicable parameter is selected on the P2P menu, P2P parameter setting
window will be displayed.

[Fig. 7.3.13] P2P block setting

Up to 64 separate blocks can be set. Select an optional block to specify the applicable block
operation by selection of a function as shown below.

[Fig. 7.3.14] P2P function commands

Setting items and details of respective functions are as follows;

7-14

Chapter 7 P2P Service

1) Read
Used to read the data of Read area in the station assigned in the P2P channel and save the
data in the Save area in the self-station, which is commonly used for MLDP client and Modbus
TCP client drivers. Its basic configuration is as shown below;

[Fig. 7.3.15] Read command setting

It is composed of basic operation setting and memory setting as described below;
A) Basic operation setting
(1) Channel
Select a communication port which will be used by the applicable block.
The communication port for each block is decided when P2P Channel is setup, which can
not be changed during Run.
(2) Condition Flag
Define the condition to operate P2P block. A bit device is available for condition flag and
the P2P block will be operated at the rising edge of the condition flag.
(3) Command Type
Decide details of Read operation. Single and Continuous are available for Command
Type.
Up to 4 memory areas are available for Single Read function, and Continuous Read reads
as many bytes as defined on the Data Size item.
(4) Data Type
Define the format of the data the block will process. Bit, Byte, 2bytes (Word), 4bytes
(Double Word) and 8bytes (Long Word) data can be processed in Single read function
and BYTE only is available for Continuous read function.
(5) Number of Variables.

7-15

Chapter 7 P2P Service

It is activated when Single is selected in the Command field. Decide the number of
areas to read. Up to 4 is available.
(6) Data Size
It is activated when Continuous is selected in the Command field. Since BYTE is fixed in
the Data type when MLDP Client driver is used, Data Size can be assigned in BYTE size.
B) 2MLI and 2MLK setting
Select the CPU type whose selection choices are 2MLK and 2MLI.
C) Memory Settings
(1) Read area
Set the memory area of counterparty station to read.
P, M, K, F, T, C, U, Z, L, N, D, R, ZR areas are available when MLDP client is
selected for Driver which is assigned in the P2P Channel settings.
Refer to the CPU manual for the available ranges of each memory area.
(2) Set as many variables as assigned in the No. of variables for Single Read and the
header address for Continuous Read. The format of address must be different based
on driver types.
(3) MLDP client
Input M100 to read data of counterpartys M100 word address, for example.
(4) Modbus TCP client
Input 30010 to read data of counterpartys AI (Analog Input) 10 address.
(5) Save area
a) Set the area to save the read data on.
b) Set as many variables as assigned in the No. of variables for Single Read and
the header address for Continuous Read.
c) Input P100 to save the read data on P100 word address, for example.
In order to read %MB100s 100 Bytes of the correspondent IP ([Link]) station and
save on my PLC %M0 via the channel 0 when Timer T0000 turns on, its setting shall be as
follows;

7-16

Chapter 7 P2P Service

[Fig. 7.3.16] Read command setting complete

2) Write
Used to write data on optional destination stations area desired, commonly for MLDP client and
Modbus TCP client drivers. It supports Continuous Write and Single Write, where data can be
written on up to 4 individual areas. Its basic configuration is as shown below;

[Fig. 7.3.17] Write command setting

Details of respective input items are as described below;
A) Basic operation setting
(1) Channel
Select a communication port which will be used by the applicable block.
The communication port for each block is decided when setting parameters, which can
not be changed during Run.
(2) Condition Flag
Define the condition to operate P2P block. A bit device is available for condition flag and
the P2P block will be operated at the rising edge of the condition flag.
(3) Command Type
Decide detailed Write operation. Single Write and Continuous Write are available.
Single Write writes up to 4 memory areas and Continuous Write writes as many bytes as
defined on the specified position.
(4)

(5)

(6)

Data Type
Define the format of the data the block will process. Bit, Byte, 2bytes (Word), 4bytes
(Double Word) and 8bytes (Long Word) data can be processed in MasterLogic-200.
Number of Variables
It is activated when Single is selected in the Command field. Decide the number of
areas to write on individually. Up to 4 is available.
Data Size
It is activated when Single is selected in the Command field. Since BYTE is fixed in the

7-17

Chapter 7 P2P Service

Data type when MLDP Client driver is used, Data Size can be assigned in BYTE size.
(7)

Destination station Number: Not used in FEnet I/F module.

B) 2MLI and 2MLK setting

Select the CPU type whose selection choices are 2MLK and 2MLI.
C) Memory Setting
(1) Read area
Set the self-stations memory area where the data to be sent is saved in.
(2) Set as many variables as assigned in the No. of variables for Single Write and
the header address for Continuous Write. The format of address must be different
based on driver types.
(3) MLDP client
Input M100 to read data of correspondent %MW100
(4) Modbus TCP client
Input 30010 to read data of correspondent AI 10 address
(5) Save area
a) Set the area to save the read data on.
b) Set as many as variables with input value which will be different based on driver
types.
c) Input P100 to save the read data on %PW100
In order to write MW0 data of 10 Words of my PLC on the correspondent area A0 via the
channel 1 ([Link], port 502), its edit example will be as follows;

[Fig. 7.3.18] Write command setting complete

7-18

Chapter 7 P2P Service

3) Send
This function is used to send the optional frame to an external device to connect with through not
MLDP client/Modbus TCP client protocol but unspecific communication method.

Only one frame shall be selected to use for one Frame Send function, and memory setting shall be
specified in this function for applicable frames Fix sized /Variable sized variable.
The frame to send should be surely specified before the function is used.

[Fig. 7.3.19] Send command driver setting

7-19

Chapter 7 P2P Service

[Fig. 7.3.20] P2P parameters setting

7-20

Chapter 7 P2P Service

[Fig. 7.3.21] Write command setting complete

Details of respective items above are as described below;
A) Basic setting item
(1) Channel
Select a channel to send the desired frame through (IP:[Link], D_PORT :
3000).
(2) Condition flag
Define when the frame is to be sent.
(3) Frame
Select the name of the user defined frame to be used in applicable P2P block.
Frame shall be defined prior to function registration. Selection available among the
frames registered as frames to send.
B) Variables
(1) Read area
a) Specify the data position to configure the frame as information for the variable
area inside Send frame
b) Input Word address. If the variable area of the frame is configured by reading
data from %DW200, then input D200.
c) Define as many as variables inside the frame.

(2) Size
Set the size of data to be in the variable area inside Send frame selected. It shall be
defined as many as variables.

7-21

Chapter 7 P2P Service

4) Receive
This function is used to receive some frames among those frames the destination station sends.
An identical frame can not be selected for respective P2P Frame Receive function blocks. Only
one Receive function block can be decided for the received frame.

[Fig. 7.3.22] Receive command setting window

[Fig. 7.3.23] P2P block register of Receive command

7-22

Chapter 7 P2P Service

[Fig. 7.3.24] P2P block setting complete of Receive command

A) Basic setting item
(1) Channel : Select a channel to receive the desired frame through.
(IP:[Link], D_PORT : 3000)
(2) Frame : Select the user defined frame received.
B) Memory setting item
(1) Save area
a) Specify the position to save data for variable-defined segment if registered frame is
received.
b) Define as many as variables inside the received frames.

5) ESend/EReceive
This service is to send/receive e-mails to/from the user for the error value caused by events
while communication operates, which will be provided later.

7-23

Chapter 7 P2P Service

7.4 P2P Service Operation

After P2P parameters are specified, download the parameters onto PLC CPU and start the P2P service.
It is supposed that P2P parameters to download are already prepared and connection is available with
the applicable PLC CPU.

1) P2P parameters downloading

In order to download the prepared P2P parameters, select [Online] [Write] on SoftMaster-PD
menu window to display the parameters downloading window, where registered basic setting,
P2P parameters and HS link parameters can be selected.

[Fig. 7.4.1] P2P parameters downloading

Among P2P 0~7, only the prepared P2P parameters will be displayed after sorted, where P2P
parameters to download will be selected.
Click OK to download the P2P parameters onto CPU.

7-24

Chapter 7 P2P Service

2) P2P service start

Even after P2P parameters are downloaded, P2P shall be started in order to start the P2P
service. Select [Online] -> [Link Enable (HS link, P2P)] on the menu.

[Fig. 7.4.2] Enable setting of P2P service

Select P2P parameters to start on the [Link Enable (HS link, P2P)] window. The P2P parameters
already checked is during run, whose P2P service will stop if cancelled.
In order to confirm normal downloading and normal P2P service operation, select [System
Diagnosis] on the menu.

7-25

Chapter 7 P2P Service

7.5 P2P Diagnosis Function

Diagnosis function of P2P system is used to display the service status and information of the
communication program after the driver of the communication module is specified. The user can
check the normal P2P service through the diagnosis system. Refer to Chapter 5 SoftMaster-PD
Program for more details.

[Fig. 7.5.1] Information of system diagnosis module

1) P2P service
It is used to display detailed information on the user defined service executed, check and read
the service status if P2P parameters are set and enabled, where real-time monitoring is
available with Individual Read or Continuous Read specified on the menu.

7-26

Chapter 7 P2P Service

[Fig. 7.5.2] P2P service monitor

7-27

Chapter 8 Dedicated Communication

Chapter 8 Dedicated Protocol Communication

8.1 Dedicated Communication
8.1.1 Introduction
The dedicated communication service is reading and writing information and data of PLC from/on
PC and associated devices with the protocol built-in FEnet I/F module.
The FEnet I/F module operates as a server in the network and responds to memory Read/Write
request command with MLDP (MasterLogic-200 dedicated protocol) or MODBUS TCP protocol
by Computer or external devices. It uses 2004 and 2005 for TCP and UDP port number of
MasterLogic-200 dedicated driver, respectively and 502 for the port number of MODBUS TCP
driver. This service mainly used to communicate between higher level system (PC program,
MMI) and Honeywell Ethernet module or between Honeywell Ethernet modules.

1) Setting of MLDP driver

[Fig. 8.1.1] Driver setting screen

8-1

Chapter 8 Dedicated Communication

As basic parameters shall be surely specified and downloaded prior to use in the Ethernet
communication, the dedicated communication services shall be also surely specified and
downloaded for its application (MLDP SERVER if not specified).
The number of dedicated connections in the basic parameters is the number of channels (MMI
connections) connected through Honeywell dedicated port (2004). Thus, by changing the
number of dedicated connections on the frame editor, the number of channel connections for
Honeywell dedicated communication can be changed.

8.1.2 Frame Structure

The structure of Honeywell Ethernet modules application frame is as shown below;
Header
IP Header

TCP Header

Application Data Format

Application Header Format

Application Instruction Format

1) Header Structure (Application Header Format)

Item

Size(byte)

Description

Company ID

Honeywell-MasterLogic-200
(ASCII CODE : 4C 53 49 53 2D 58 47 54 00 00)

Reserved

0x00 : Reserved area

* Client(MMI) Server(PLC) : Dont care (0x00)

PLC Info

* Server(PLC) Client(MMI) :
1) If Reserved 1 is 0x00,
Bit00~05 : CPU TYPE
01(2MLK-CPUH), 02(2MLK-CPUS)
Bit06 : 0(Redundancy Master / Single),
1(Redundancy Slave)
Bit07 : 0(CPU normal operation),
1(CPU error)
Bit08~12 : System status
1(RUN),2(STOP), 4(ERROR), 8(DEBUG)
Bit13~15 : Reserved

CPU Info

0xA0 Note1)

Source of Frame

* Client(MMI) Server(PLC) : 0x33

* Server(PLC) Client(MMI) : 0x11

Invoke ID

ID used to discriminate the sequence among frames

(This number is sent as attached to Response frame)

Length

Byte size of application Instructions.

8-2

Chapter 8 Dedicated Communication

Item

Size(byte)

FEnet Position

Reserved 2

Description
Bit 0~3 : FEnet I/F modules Slot No.
Bit 4~7 : FEnet I/F modules Base No.
0x00 : Reserved area

(BCC)

(Application Headers Byte Sum)

Note 1) Regarded as 2MLK/2MLI series through the reserved area.

2) Basic Structure of Frame (Application Instruction Format)

(1) Header
Company ID
(HoneywellMasterLogic
-200)

PLC

Reser

information

ved

area (2)

(1)

H33

Invoke ID

Length

(1)

(2)

(2)

Reserved
area
(1)

BCC
(1)

** Figure in ( ) means the number of bytes.

Company ID: Honeywell-MasterLogic-200 in ASCII text
PLC Info: Information area for PLC
Invoke ID: ID used to discriminate the sequence among frames, which can be set
optionally at request command. And Response frame resends the
received Invoke ID at request command(an area used for checking for
errors in PC or MMI).
Length: Length of the data area at the back of Header in the frame.
(2) Data Request frame (external communication device FEnet I/F module)

Header

Command

Data

Reserved area

Structurized

type

(2 bytes)

data area

(3) ACK Response frame (FEnet module external communication device, if data is received
normally)

Header

Command

Data
type

Reserved
area
(2 bytes)

Error status

Structurized

(2 bytes h0000)

data area

(4) NAK Response frame (FEnet module external communication device, if data is received
abnormally)

Header

Command

Data
type

Reserved

Error status

area

(2 bytes:

(2 bytes)

Not h0000)

8-3

Error code
(1 byte)

Chapter 8 Dedicated Communication

Notes
1) If hexadecimal data is applied, the Hex. type of data is indicated with h or 0x attached in
front of figures inside frame like 01, h12345, h34, 0x12 and 0x89AB.

8.1.3 List of Commands

Commands used in dedicated communication service are as shown below in the table.
Command
code

Command

Read

Request :
h0054
Response :
h0055

Processing Details

Individual

Reads Bit, Byte, Word, Double word and Long word type
of variables data based on each data type.

Continuous

Request :
Write

Data
type

Individual

h0058
Response :
h0059

Continuous

Reads byte type of variables in block unit.

(up to 1,400 bytes).
Writes Bit, Byte, Word, Double word and Long word type
of variables data based on each data type.
Writes byte type of variables in block unit.
(up to 1,400 bytes).

[Table 1.1] List of Commands

8.1.4 Data Type

1) Data type of variables
The Data types of variables in the P, M, L, F, K, C, D, T, N, R, etc device areas are to be included
after the variable indicating letter of %.
Data type
Bit

Example
%PX0,%LX0,%FX0

Byte

%MB0, %PB0, %DB0

Word

%PW0,%LW0,%FW0,%DW0

Double Word
Long Word

%PD0,%LD0,%FD0,%DD0
%PL0,%LL0,%FL0,%DL0
[Table 1.2] List of data types of direct variables

2) Data type
Data type is to be set to Command type when reading or writing direct variables.
Data type

Code

Data type

Code

BIT

h00

DWORD

h03

BYTE

h01

LWORD

h04

WORD

h02

Continuous

h14

[Table 1.3] List of data types of direct variables

8-4

Chapter 8 Dedicated Communication

8.2. Execution of Commands

8.2.1 Read Separated Direct Variable
1) Introduction
This function is used to directly specify the device memory address and the data type to read. Up to
16 separate device memory areas can be read at a time

2) Request format (PC -> PLC)

Read Request of Individual Variable (MMI PLC)
Item

Size(byte)

Description

Command

0x0054 : Read Request

Data type

Refer to Data Type table(X,B,W,D,L)

Reserved area

0x0000 : Dont Care.

Number of blocks

Number of memory address to read; up to 16

The number of characters in the Direct variable; Max. 16

Variable length
Direct Variable
...

Direct Variable

name
Code (Ex.)

Direct variable only available

variable name
...

Variable length

Format

Length of

Header

(Repeatedly as many as the number of blocks /up to 16)

The number of characters in the Direct variable; up to 16

characters.

Length of

Direct variable only available

variable name

Command
H0054

Data

Reserved

Number

Variable

Direct

type

area

of blocks

length

variable

h0002

h0000

h0001

h0006

%MW100

...

1 block (up to 16 blocks setting available repeatedly)

(1) Number of blocks
Used to specify the number of blocks composed of [Variable Length][Variable] in the
request format up to 16 blocks. Accordingly, the value of [Number of Blocks] shall be
h0001 ~ h0010.
(2) Variable length
It means the number of characters of the variable name which is available up to 16
characters, whose range is h01 ~ h10.

8-5

Chapter 8 Dedicated Communication

(3) Variable
Input the address of memory device to be read actually. It shall be ASCII value within 16
characters. Others than figure, capital/small letter, % and . are not allowed.
Based on the PLC type, available types of variables are as described below.
Classification
MasterLogic-200
memory

Bool

Byte

%(P,M,L,K,F,T)X

Word
%(P,M,L,K,F,T
,C,D,S)W

Double Word

Long Word

[Table 2.1] Types of Variables

Notes
1) When the frame is composed with hexadecimal word data to be displayed on the frame
above, h in front of figures shall be taken out with the positions of two bytes exchanged as
below.
Ex.) h0054 5400

3) Response format (For PLCs ACK Response)

Read Response of Individual variable (PLC MMI)
Item

Size(byte)

Command

0x0055 : Read Response

Data type

Refer to Data Type table

Reserved area

0x0000 : Dont Care

Error status

Normal if it is 0, abnormal if not 0.

Error code

If Error State is abnormal, the lower Byte is the error code.

Number of blocks

If Error State is normal, it means the number of blocks to be read.

Data size

Data

Data size

...

...

The size of data in byte unit.

Data

Data size

Header

Code
(Ex.)

...

Comma
nd
h0055

Data read.
(Repeatedly as many as the number of variables /up to 16)

Data size

Format
name

Description

The size of data in byte unit.

Data read.

Data
type
h0002

Reserved
area

Error
status

Number
of
blocks

h0000

h0000

h0001

Data
Size

Data

h0002

h1234

......

1 block (up to 16 blocks)

8-6

Chapter 8 Dedicated Communication

(1) Data Size

It means the number of bytes in Hex. This number is decided based on the memory type
(X,B,W,D,L) included in variable name of the computer request format.
(2) Number of blocks
Used to specify the number of blocks composed of [Number of Data][Data] in the request
format up to 16 blocks. Accordingly, the value of [Number of Blocks] shall be h0001 ~
h0010.
Classification
Bool(X)

Available variables

1
(Lowest bit only effective)

%(P,M,L,K,F,T)X

Word(W)

Number of data (Byte)

%(P,M,L,K,F,T,C,D,S)W

[Table 2.2] Number of data based on variables

Notes
1) Number of data H04 means that 4 bytes of Hex data (Double Word) exists in the data.
2) If data type is Bool, the read data will be displayed in one byte (HEX). In other words, if BIT
value is 0, h00 will be displayed, and if the value is 1, h01 will be displayed.

4) Response format (For NAK Response)

Format
name
Code (Ex.)

Header

Command

...

h0055

Data

Reserved

type

area

h0002

h0000

Notes
1) Error code displays the type of error in 1 byte of Hex
Refer to Error Codes Table for more details.

8-7

Error status
hFFFF
(other than 0)

Error code
(Hex 1 Byte)
h21

Chapter 8 Dedicated Communication

8.2.2 Read Continuous Direct Variable

1) Introduction
This function is used to read the data of directly defined PLC device memory continuously as
many as specified from the address specified.

2) Request format (PC PLC)

Read Request of Continuous Variable (MMI PLC)
Item

Size (byte)

Command

Description
0x0054 : Read Request

Data type

0x0014 : Continuous

Reserved area

0x0000 : Dont Care.

Number of blocks

It is fixed with h0001 for Continuous read.

Variable length

The number of characters in the variable field; Max. 16

Variable name; Byte type of direct variables only available

Length

Variable

(In other words, types of %MB / %PB / %DB/ available:

Variable name

supporting devices: P,N,L,K,T,C,D,N, F )

It displays blocks start address. (Ex. %MB0, %PB0)

Number of Data

Data Size in byte whose Maximum value is 1400.(h0578)

Format
name

Header

Command

Data
type

Reserved
area

Number
of
blocks

Variable
length

Variable

Number
of data

Code
(Ex.)

...

h0054

h0014

h0000

h0001

h0006

%MB000

h0006

Notes
1) Number of data means the number of data in byte unit (up to 1,400 bytes available).
(1) Data type
h0014 only can be used for the data type.
(2) Number of blocks
Definitely h0001 only can be used for the number of blocks.
(3) Variable length
It means the number of characters of the variable name which is available up to 16
characters, whose range is h0001 ~ h0010.
(4) Variable
It stands for variables address to read actually. It shall be ASCII value within 16 characters.
Others than figure, capital/small letter, % and . are not allowed for the variable name.

8-8

Chapter 8 Dedicated Communication

Based on the PLC type, types of variables available to read continuously are as described
below.

3) Response format (For PLCs ACK Response)

Read Response of Continuous Variable (PLC MMI)
Item

Size(byte)

Command

Description
0x0055 : Read Response

Data type

0x0014 : Block Type

Reserved area

0x0000 : Dont Care

Error status

Normal if it is 0, abnormal if not 0.

Error code

If Error State is abnormal, the lower byte is the error code.

Number of blocks

0x0001 : If Error State is normal

Number of data

Data

Data size

Format
name
Code
(Ex.)

Header

Command

...

h0055

The Size of Data in byte.

Data to read; up to 1400 bytes

Data

Reserved

Error

Number

Number

type

area

status

of blocks

of data

h0014

h0000

h0000

h0001

h0006

Data
h012345
6789AB

Number of data means the number of bytes in Hexadecimal number.

4) Response format (For PLCs NAK Response)

Format
name
Code (Ex.)

Header

Command

Data type

...

h0055

h0014

Reserved
area
h0000

Error status
hFFFF

Notes
1) Error code displays the type of error in 1 byte of Hexadecimal number
Refer to Error Codes Table for more details.

8-9

Error code
(Hex 1 Byte)
h21

Chapter 8 Dedicated Communication

8.2.3 Write Separated Direct Variable

1) Introduction
This function is used to directly specify the PLC device memory to write data on applicably to its
memory data type. The data can be written on up to 16 separate device memories at a time.

2) Request format (PC -> PLC)

Write Request of Individual Variable (MMI PLC)
Item

Size(byte)

Description

Command

0x0058 : Write Request

Data type

Refer to Data Type table

Reserved area

0x0000 : Dont Care.

Number of blocks

Number of memory address to write; up to 16.

Variable length

The number of characters in the Direct variable; Max. 16

Direct variable

Variable length

...

...

(Repeatedly as many as the number of blocks /up to 16)

Data size

Data size in byte unit

Data

Data size

...

...

Direct variable only available

Data to write
(Repeatedly as many as the number of blocks /up to 16)

Format
name

Head
er

Comm
and

Data
type

Reserv
ed
area

Number
of
blocks

Variable
length

Direct
variable

Code
(Ex.)

..

h0058

h0002

h0000

h0001

h0006

%MW1
00

..

Number
of data

data

h0002

h12
34

..

1 block (up to 16 blocks setting available repeatedly)

(1) Number of blocks
Used to specify the number of blocks composed of [Variable Length][Variable]and [Data
Length] [Data] in the frame whose Maximum number is 16(h10). Accordingly, the value of
[Number of Blocks] shall be h01~ h10.
(2) Variable length
It means the number of characters of the variable name which is available up to 16
characters, whose range is h01 ~ h10.
(3) Direct variable
Input variables address to read actually. It shall be ASCII value within 16 characters.
Others than figure, capital/small letter, % and . are not allowed for the variable name.

8-10

Chapter 8 Dedicated Communication

Notes
1) Device data type of each block shall be surely identical. If the data type of the first block is
Word, and that of the second is Double Word, an error may occur.
2) If data type is Bool, the data format will be one byte (HEX). In other words, if BIT value is 0, the
data will be h00 and if the value is 1, the data will be h01.
3) When Bit write function is used, the address must be calculated in Bit unit.
For example, to write a data in the hC (12th) bit of M172 word, the Bit address can be
calculated as follow processing.
Wrong Expression: %MX172C
Right Expression: 172(Word number) x 16 + 12(Bit number) = 2764
%MX2764

3) Response format (For PLCs ACK Response)

Format
name
Code (Ex.)

Header

Command

Data type

...

h0059

h0002

Reserved

Error

Number of

area

status

blocks

h0000

h0000

h0001

(1) Number of blocks

It is the number of blocks normally written.

4) Response format (For NAK Response)

Format
name
Code (Ex.)

Header

Command

...

h0059

Data

Reserved

type

area

h0002

h0000

Error status
hFFFF
(other than 0)

Notes
1) Error code is attached the type of error in 1 byte of Hexadecimal code.
Refer to Error Codes Table for more details.

8-11

Error code
(Hex 1 Byte)
h21

Chapter 8 Dedicated Communication

8.2.4 Write Continuous Direct Variable

1) Introduction
This function is used to write the data on the directly defined PLC device memory continuously
as many as specified from the address specified. However, byte type of variables is only available.

2) Request format
Write Request of Continuous Variable (MMI PLC)
Item

Size(byte)

Description

Command

Data type

0x0014 : Block Type

Reserved area

0x0000 : Dont Care.

0x0058 : Write Request

Number of blocks

It is fixed with h0001 for Continuous write.

Variable length

The number of characters in the variable field; Max. 16

Variable

Variable

Variable name; Byte type of direct variables only available.

length

(In other words, types of %MB / %PB / %DB/ available:

supporting devices: P,N,L,K,T,C,D,N )
It displays blocks start address. (Ex. %MB0, %PB0)

Number of data

Data Size in byte whose Maximum value is 1400.(h0578)

Data

Data size

Data to write, up to 1400 bytes

Format
name

Header

Command

Data
type

Reserved
area

Number
of
blocks

Variable
length

Variable

Number
of data

Data

Code
(Ex.)

...

h0058

h0014

h0000

h0001

h0006

%MB1
00

h0002

h1234

(1) Number of data

It means the number of data in byte unit. (up to 1,400(h0578) bytes available).
(2) Number of blocks
h0001 only can be used for Number of blocks field .
(3) Variable length
It is the number of characters of the variable which is available up to 16 characters, whose
range is h01 ~ h10.
(4) Variable
It stands for variables address to write actually. It shall be ASCII value within 16 characters.
Others than figure, capital/small letter, % and . are not allowed for the variable name.
Based on the PLC type, types of variables available to write continuously are described in
[Table 10.3.2].
Notes
1) Refer to applicable technical materials for respective device areas setting of MasterLogic200 series.

8-12

Chapter 8 Dedicated Communication

3) Response format
Read Response of Continuous Variable (PLC MMI)
Item

Size(byte)

Command

0x0059 : Write Response

Data type

0x0014 : Block Type

Reserved area

0x0000 : Dont Care

Error status

Normal if it is 0, abnormal if not 0.

Number of blocks

0x0001 : If Error State normal.

Error code

Description

If Error State abnormal, the lower Byte is error code.

3-1) ACK Response

Format
name

Header

Command

Data type

Reserved
area

Error status

Number of
blocks

Code (Ex.)

...

h0059

h0014

h0000

h0000

h0001

(1) Data type

Available data type is byte (%MB,%IB,%QB).
(2) Number of data
It means the number of bytes (Hex).

3-2) NAK Response)

Format
name
Code
(Ex.)

Header

Command

....

h0059

Data

Reserved

type

area

h0014

h0000

Error status
hFFFF
(other than 0)

(1) Error code

Error code is attached the type of error in 1 byte of Hexadecimal code.
Refer to Error Codes Table for more details.

8-13

Error code
(Hex 1 Byte)
h21

Chapter 8 Dedicated Communication

8.2.5 Status Read Request (MMI -> PLC)

1) Introduction
This service allows the user to use information and status of PLC through communication.

2) Computer Request format

Item

Size(byte)

Command

0x00B0 : Status Request

Description

Data type

0x0000 : Dont Care

Reserved area

0x0000 : Dont Care

3) Response format (ACK Response from PLC)

Item

Size(byte)

Description

Command

0x00B1 : Status Response

Data type

0x0000 : Dont Care

Reserved area

0x0000 : Dont Care

Error status

Normal if it is 0, abnormal if not 0.

Reserved area

0x0000 : Dont Care

Data size

0x0018

data

24

Status Data

4) Data structure of MasterLogic-200 status

Item

Size
(byte)

Byte
position

Description

Slot Info

Slot information
Bit00~Bit03: Locals slot information remotely connected with other station.
Bit04~Bit07: Locals base information remotely connected with other station.
Bit08~Bit11: Other stations slot information remotely connected.
Bit12~Bit15: Other stations base information remotely connected.
Bit16~Bit19: Slot information this module is installed on.
Bit20~Bit23: Base information this module is installed on.
Bit24~Bit31: Reserved

_CPU_TYPE

System type : Flag

_PADT_CNF

SoftMaster-200 connection status : Flag

_SYS_STATE

PLC mode and operation status : Flag

_CNF_ER

12

System error (serious) : Flag

_CNF_WAR

16

System warning : Flag

_VER_NUM

20

OS version No. : Flag

Reserved

22

Reserved area

* Refer to Description of flags below for more details on respective items.

8-14

Chapter 8 Dedicated Communication

5) Description of flags
_CPU_TYPE
15Bit : 2MLK(1)/2MLI(0), 15-Bit : Single, Redundancy master(0)/ Redundancy slave(1)
Single

: 0x8000~0xffff

0xA001 : 2MLK-CPUH
0xA002 : 2MLK-CPUS
_VER_NUM
0xXXYY : [Link]
_SYS_STATE
It displays operation mode and operation status information of the system (DWORD, F00~F01)
Variable

Type

Device

Function

Description

_RUN

Bit

F00000

RUN

CPU modules operation status in RUN

_STOP

Bit

F00001

STOP

CPU modules operation status in STOP

_ERROR

Bit

F00002

ERROR

CPU modules operation status in ERROR

_DEBUG

Bit

F00003

DEBUG

CPU modules operation status in DEBUG

_LOCAL_CON

Bit

F00004

Local control

Operation mode changeable only by mode key

_MODBUS_CON

Bit

F00005

Modbus mode On

During Modbus slave service

_REMOTE_CON

Bit

F00006

Remote mode On

During Run in remote mode

Bit

F00007

_RUN_EDIT_ST

Bit

F00008

Modification in progress
Modified program standing by while modified
during Run (program
during Run
being downloaded)

_RUN_EDIT_CHK

Bit

F00009

_RUN_EDIT_DONE

Bit

F0000A

_RUN_EDIT_END

Bit

F0000B

_CMOD_KEY

Bit

F0000C

_CMOD_LPADT

Bit

F0000D

_CMOD_RPADT

Bit

F0000E

_CMOD_RLINK

Bit

F0000F

_FORCE_IN

Bit

F00010

Compulsory input

_FORCE_OUT

Bit

F00011

Compulsory output

Modification in
progress during Run
(internally processed)
Modification complete
during run
Internal flag known
when modification
complete during run
Operation mode change
cause
Operation mode change
cause
Operation mode change
cause
Operation mode
change cause

8-15

Modification during Run being processed

internally
Modification normally complete during run.
Modification normally complete during run.
Operation mode changed by key
Operation mode changed by local PADT
Operation mode changed by remote PADT
Operation mode changed by remote
communication module
Compulsory On/Off being executed for input
contact
Compulsory On/Off being executed for output
contact

Chapter 8 Dedicated Communication

Variable

Type

Device

_SKIP_ON

Bit

F00012

_EMASK_ON

Bit

F00013

_MON_ON

Bit

F00014

_USTOP_ON

Bit

F00015

_ESTOP_ON

Function

Description

I/O skip being

Specified I/O module existent to stop error

executed

check and data refresh.

Error mask being

Specified I/O module existent to speedily carry

executed

out the operation even if a defect occurred.

External monitor in progress for programs and

Being monitored

variables

Stop by stop

Stopped by stop function after scan closed

function

during RUN mode operation

Stop by ESTOP

Immediately stopped by ESTOP function during

function

RUN mode operation.

Bit

F00016

Bit

F00017

Compiling

Compile being performed.

_INIT_RUN

Bit

F00018

Initializing

Initialization task being performed.

Bit

F00019

Bit

F0001A

_CONPILE_MOD
E

Bit

F0001B

_PB1

Bit

F0001C

Program code 1

No.1 program code being executed

_PB2

Bit

F0001D

Program code 2

No.2 program code being executed

_CB1

Bit

F0001E

Compile code 1

No.1 compile code being executed

_CB2

Bit

F0001F

Compile code 2

No.2 compile code being executed

_CNF_ER
It displays all the error flags related with operation failure.
Variable

Type

Device

_CPU_ER

Bit

F00020

_IO_TYER

_IO_DEER

Bit

Bit

F00021

F00022

_FUSE_ER

Bit

F00023

_IO_RWER

Bit

F00024

Function

Description

CPU configuration

Normal operation unavailable due to CPU

Error

module error found by self-diagnosis.

Module type
discordant Error
Module installation
error

Different configuration between each slots I/O

configuration parameters and actually installed
module
If each slots module configuration changes
during Run, it will be detected and displayed.

Fuse blown error

If fuse is blown on the module among each

slots modules, it will be detected and displayed.

I/O module Read/

Displayed if normal Read/write of I/O module

Write error

among each slots modules is not available

Special/communicati Displayed if normal interface is unavailable due

_IP_IFER

_ANNUM_ER

Bit

Bit

F00025

F00026

on module

to abnormal special or communication module

interface error

among each slots modules

Serious error

Displayed if serious error detected in external

detected in external

device by user program and recorded on

equipment

ANC_ERR[n].

8-16

Chapter 8 Dedicated Communication

Variable

Type

Device

function

Bit

F00027

_BPRM_ER

Bit

F00028

_IOPRM_ER

Bit

F00029

_SPPRM_ER

Bit

F0002A

_CPPRM_ER

Bit

F0002B

_PGM_ER

Bit

_CODE_ER
_SWDT_ER

Description
-

Basic parameters
error

Displayed if basic parameters abnormal

IO configuration

Displayed if I/O configuration parameters

parameters error

abnormal.

Special module

Displayed if special module parameter

parameters error

abnormal.

Communication module

Displayed if communication module

parameters error

parameter abnormal.

F0002C

Program error

Displayed if user program abnormal.

Bit

F0002D

Program code error

Bit

F0002E

Bit

F0002F

_BASE_POWER_
ER

System watch-dog
error
Power error

Displayed if an indecipherable command

is met while uses program executed.
Displayed if System watch-dog exceeded.
Displayed if base power abnormal
Displayed if program scan time exceeds

_WDT_ER

Bit

F00030

Scan watch-dog

scan watch-dog time specified with

parameters

F00031

F0003F

_CNF_WAR
It displays all the warning flags related with continuation of the operation (DWORD,
F004~F005)
Variable

Type

Device

_RTC_ER

Bit

F00040

Function
RTC data error

Description
Displayed if RTC data abnormal
Displays that normal (hot or) warm restart
program unavailable due to damaged data

_DBCK_ER

Bit

F00041

Data back-up error

memory, thus clod-restart executed, which will

be available in initialization program. If the
initialization program complete, it will be reset
automatically.

_HBCK_ER

Bit

F00042

Hot restart unavailable

Displays that continuous operation not allowed
with the synchronized data kept in scan unit
when program stopped in the middle due to

_ABSD_ER

Bit

F00043

Abnormal operation stopped

power-cut while program executed and then

powered back, which is available in
initialization program. If the initialization
program complete, it will be reset
automatically.

8-17

Chapter 8 Dedicated Communication

Variable

Type

Device

Function

_TASK_ER

Bit

F00044

Task impact

_BAT_ER

Bit

F00045

Battery error

Description
Displayed if identical tasks requested as
duplicated when user program executed.
Displayed if battery voltage for back-up of
user program and data memory is less than
specified.

_ANNUM_ER

Bit

F00046

Slight error detected in

external equipment.

_LOG_FULL

Bit

F00047

Log memory full warning

_HS_WAR1

Bit

F00048

HS parameter 1 error

_HS_WAR2

Bit

F00049

HS parameter 2 error

_HS_WAR3

Bit

F0004A

HS parameter 3 error

Displayed if slight error detected in external

equipment by user program and recorded
on ANC_WB[n]
Displays PLCs log memory full.

_HS_WAR4

Bit

F0004B

HS parameter 4 error

_HS_WAR5

Bit

F0004C

HS parameter 5 error

Representative flag used to display HS link

_HS_WAR6

Bit

F0004D

HS parameter 6 error

unavailable by checking parameters of HS

_HS_WAR7

Bit

F0004E

HS parameter 7 error

link if enabled, which shall be reset if HS

_HS_WAR8

Bit

F0004F

HS parameter 8 error

link disenabled.

_HS_WAR9

Bit

F00050

HS parameter 9 error

_HS_WAR10

Bit

F00051

HS parameter 10 error

_HS_WAR11

Bit

F00052

HS parameter 11 error

_HS_WAR12

Bit

F00053

HS parameter 12 error

_P2P_WAR1

Bit

F00054

P2P parameter 1 error

_P2P_WAR2

Bit

F00055

P2P parameter 2 error

_P2P_WAR3

Bit

F00056

P2P parameter 3 error

Representative flag used to display P2P

_P2P_WAR4

Bit

F00057

P2P parameter 4 error

unavailable by checking parameters of

_P2P_WAR5

Bit

F00058

P2P parameter 5 error

each P2P if enabled, which shall be reset

_P2P_WAR6

Bit

F00059

P2P parameter 6 error

if P2P disenabled.

_P2P_WAR7

F0005A

P2P parameter 7 error

_P2P_WAR8

F0005B

P2P parameter 8 error

_Constant_ER

F0005C

Fixed cycle error

F0005D
~F0005F

It will ON if the scan time is greater than

Fixed Cycle specified.
-

8-18

Chapter 8 Dedicated Communication

8.3 Modbus/TCP Dedicated Server

This is used when it operates as the master of other device or higher PC (MMI) Modbus.

8.3.1 Driver setting

[Fig. 8.3.1] Modbus TCP driver setting

[Fig. 8.3.2] Modbus TCP address

8-19

Chapter 8 Dedicated Communication

Modbus function and the maximum number of response data that Modbus TCP driver supports
are described in the table below. The correspondent master device shall make a request within
the range specified in the table. For example, Bit Read Request is available up to 2000 bits,
and Bit Write Request is up to 1600 bits.

Code

Description

Address

Response Size

01

Read Coil Status

0XXXX

2000 Coils

02

Read Input Status

1XXXX

2000 Coils

03

Read Holding Registers

4XXXX

125 Registers

04

Read Input Registers

3XXXX

125 Registers

05

Force Single Coil

0XXXX

1 Coil

06

Preset Single Register

4XXXX

1 Register

15

Force Multiple Coils

0XXXX

1600 Coils

16

Preset Multiple Registers

4XXXX

100 Registers

Mapping of MasterLogic-200 PLC memory is required for each function codes request.
Respective setting details are as follows;

Item

Description

Remarks

DI area address

MasterLogic-200 address applicable to digital input area

Bit address

DO area address

MasterLogic-200 address applicable to digital output

Bit address

area
AI area address

MasterLogic-200 address applicable to analog input area

Word address

AO area address

MasterLogic-200 address applicable to digital output

Word address

area

The address value specified in each item is the base address of the applicable area.
Fig 8.3.1 shows that DI area is assigned starting from PX0000 and that AO area is assigned
starting from PW300.
The input value of the base address shall be within the effective areas of %M, P, etc. Since
Modbus address is 1 ~ 9999 (decimal), the size of the bit I/O area will be 9999/8 = 1249.875
bytes. In addition, the size of the word I/O area will be 9999*2 = 19998 bytes.
If the user sets the base address of the bit output (0XXXX) area to 0, Modbus bit area 00001
will be correspondent to 0th byte, 0th bit, and 00002 to 0th byte, 1st bit.

8-20

Chapter 9 Remote Connection Service

Chapter 9 Remote Connection Service

9.1 Introduction
This function is used for programming, downloading of user program, program debugging, monitoring,
etc in network system where PLCs are connected with each other via Ethernet by remote control
without moving the physical connection status of SoftMaster-200 or SoftMaster-PD. It is especially
convenient for easy access to each device from a place without repositioning when networkconnected devices are separated far. SoftMaster-200 or SoftMaster-PD remote connection service is
available under the following Logical Path to attain its purpose.

PC

PLC [1]
IP: [Link]

PLC [2]
IP: [Link]

PLC [n]
IP: [Link]

SoftMaster-200
SoftMaster-PD
USB or RS-232C

Local connection

Logical connection via Ethernet communication module (remote)

[Fig. 9.1.1] Ethernet network

A network is supposed where RS-232C cable is connected between PC in which SoftMaster-200 and
SoftMaster-PD is installed and PLC #1 station, and PLC #1, PLC #2 and PLC #n are connected with
each other via Ethernet in SoftMaster-PD of [Fig.9.1.1]. To access the contents of PLC #1 station in the
figure above, Local connection is needed in SoftMaster-PDs on-line menu. After finishing accessing the
contents of PLC #1, disconnect the Local connection with Disconnect menu. To access the PLC #n
station, select PLC #n by setting the IP address of PLC #n and Base and Slot No. where FEnet module
is installed in the PLC #1 station in the remote connection dialog box and connect. Then logical
connection between SoftMaster-PD and PLC #n will be established via RS-232C and Ethernet. This
status is identical to the status that RS-232C cable is connected between PC and PLC #n station and it
is available to execute all functions of programming, downloading, debugging and monitoring as in PLC
#1.
Also, if Ethernet module (LAN Card) is installed on PC where SoftMaster-PD is installed and connected
to the identical network to PLC, remote stage 1 connection with PLC is available via Ethernet without
local connection via RS-232C.
With the remote connection service of SoftMaster-200 and SoftMaster-PD, easy access to PLC is
possible even if the PLC is located at a far place. And re-programming without repositioning the PLC is
possible when PLC is located at a place hard to reach.

9-1

Chapter 9 Remote Connection Service

9.2 Setting and Connection

All PLCs connected via MasterLogic-200 network are available to connect with each other by remote
connection service. SoftMaster-PD remote connection is composed of stage 1 and stage 2 connections
as described below.
The followings explains remote 1 and remote 2 connections.

PC

SoftMaster-200
SoftMaster-PD

PLC [1]
IP: [Link]

PLC [2]
IP: [Link]
FDEnet #1

PLC [n]
IP: [Link]

Network 1: FEnet

USB or RS-232C

Local connection

Logical connection via Ethernet module (remote 1)

Logical connection via Ethernet module (remote 2)
Network 2: FDEnet
PLC [A]
FDEnet #2

PLC [B]
FDEnet #3

[Fig. 9.2.1] Remote connection

[Fig. 9.2.1] shows an example of network system composed of two networks.

9-2

Chapter 9 Remote Connection Service

9.2.1 Remote 1 connection (If RS-232C cable used)

For remote stage 1 connection, SoftMaster-PD shall be in off-line state.
When Connection Settings item is selected on the Online menu [Fig. 9.2.2], Online Settings
dialog box will be displayed. [Fig. 9.2.3]

[Fig. 9.2.2] SoftMaster-PD remote connection option to select

[Fig. 9.2.3] SoftMaster-PD remote stage 1 connection

9-3

Chapter 9 Remote Connection Service

1) Connection type
It designates the connecting method for local connection. Local connection is applied with
RS-232C used as in [Fig. 9.2.1]. Select the port used in PC for a communication port. The
case that Ethernet is used for local connection will be described in the next section. Refer to
users manual of each communication module for the case with other connection types.
2) Connection depth
Decide a PLC connection stage of local, remote stage 1 or 2. Select remote stage 1 here.
3) Network type
Select a network type for stage 1 connection among Rnet, Fdnet, Snet, FEnet and FDEnet.
Ethernet is to be selected because stage 1 connection is applied through FEnet in [Fig.
9.2.1].
4) Base No.
Specify the base No. where FEnet I/F module for remote connection is installed.
5) Slot
It indicates the slot number where FEnet module is installed in locally connected PLC via
RS-232C. Select No.0 in [Fig. 9.2.3] since FEnet installed on PLC 1 is on slot No.0.
6) IP address
Specify the IP address of FEnet I/F module installed in the PLC which will be connected with
SoftMaster-PD in the network 1. Use the IP address of FEnet module installed in PLC #2
station, [Link] in [Fig. 9.2.3].

Now click [OK] and then select [Connect] on the Online menu.
Since stage 1 connection-completed status is the logical connection status identical to the
local connection with RS-232C cable is connected to the PLC, where all of the on-line menus
are available. (Except that CPU type between PLC and presently open project is
disagreeable)

Notes
1) Precautions for remote connection
Prepare a program suitable for the correspondent CPU type to connect with remotely. If the
CPU type is disagreeable between the two, limited functions only will be allowed, where
program uploading/downloading and monitoring are not available.

9-4

Chapter 9 Remote Connection Service

9.2.2 Remote 2 connection (RS-232C cable is used for local connection)

Select Connection Settings on the Online menu and setup each items of Local, Remote1 and
Remote 2 settings. [Fig. 9.2.4] shows a connection setting example to connect PLC [B] with
remote 2 stage where remote 1 is FEnet and remote 2 is FDEnet.
Click Settings... button on the Online Settings dialog box after selecting RS-232C for Type and
Remote 2 for Depth.

[Fig. 9.2.4] SoftMaster-PD remote stage 2 connection

Remote 2 only will be described below since the others are the same in the dialog box above.
1) Setting of network type
Select a network type for remote stage 2 connection among MasterLogic-200 Rnet, Fdnet,
Snet, FEnet and FDEnet. Network types of stage 1 and stage 2 connections bear no relation
to each other. 2MLL-FDEnet is to be selected since stage 2 connection is with FDEnet in
[Fig. 9.2.4].

9-5

Chapter 9 Remote Connection Service

2) Station No. of Remote 2 communication module

Use the station No. of the module installed in PLC which will be connected with stage 2 in
the network 2 for remote stage 2. In the case of [Fig. 9.2.4], use 3 for station number of
remote 2 communication module, since the connection will be established between PC and
PLC [B] whose station No. of FDEnet module is 3.

3) Base and slot No. of Remote 1 communication module

Set the Base and Slot No. where FDEnet module is installed in the PLC[2] which will be
connected with stage 1 in the network 1.
Stage 2 connection-completed status as above is the logical connection status identical to the
connection with RS-232C cable is connected to PLC [B], where all of the on-line menus are
available.

9.2.3 Remote 1 connection directly from PC connected with Ethernet

Remote stage 1 connection via Ethernet without connecting RS-232C is available if a PC where
SoftMaster-200 and SoftMaster-PD is operating is included in PLC Ethernet network.
PC
IP: [Link]

PLC [1]
IP: [Link]

PLC [2]
IP: [Link]

PLC [n]
IP: [Link]

SoftMaster-200
SoftMaster-PD

Logical connection via Ethernet communication module (remote)

[Fig. 9.2.5] Remote stage 1 connection system through PC

[Fig. 9.2.5] shows the connection between PC and PLC via Ethernet, where connection
to all PLCs on the network is available without RS-232C used in SoftMaster-200 or
SoftMaster-PD. In this case local connection is omissible and remote 1 connection is
available with all PLCs.
Select Connection settings on the Online menu and change the setting in the dialog box as
specified below to establish remote stage 1 connection directly via Ethernet.

9-6

Chapter 9 Remote Connection Service

[Fig. 9.2.6] Remote 1 connection directly via Ethernet

1) Connection type
Select an applicable type for connection. In the case of [Fig. 9.2.6], select Ethernet because
the connection is established directly via Ethernet without application of RS-232C.
2) Connection depth
Decide a PLC connection stage of remote stage 1 or 2. Select remote 1 here.
3) IP address
Set the IP address of FEnet I/F module to connect to. Use IP address, [Link] to
connect to PLC [n] in [Fig. 9.2.5].
The rest procedures are the same as with RS-232C used. Now click [OK] and then select
[Connect] on the Online menu.

9.2.4 Remote 2 connection directly from PC connected with Ethernet

Remote stage 2 connection is available via Ethernet if a PC where SoftMaster-PD is operating is
included in PLC Ethernet network as in [Fig. 9.2.7]. The procedures are the same as in remote 1
connection and a setting example of Connection Setting is as [Fig. 9.2.7].

9-7

Chapter 9 Remote Connection Service

PC
IP: [Link]

PLC [1]
IP: [Link]

PLC [2]
IP: [Link]
FDEnet #1

PLC [n]
IP: [Link]

SoftMaster-200
SoftMaster-PD
Network 1: FEnet

Logical connection via Ethernet module (remote 1)

Logical connection via Ethernet module (remote 2)
Network 2: FDEnet
PLC [A]
FDEnet #2

PLC [B]
FDEnet #3

[Fig. 9.2.7] Remote stage 2 network system

[Fig. 9.2.8] Remote 2 connection directly via Ethernet

9-8

Chapter 9 Remote Connection Service

Notes
1) Precautions for operation with remote stage 1 & 2 connection
(1) The following menus are not available if the types between the project presently open in
SoftMaster-PD and the CPU connected with stage 1 or 2 are not identical.
A) Write program and each parameter
B) Read program and each parameter
C) Monitor
D) Flash memory
E) Set Link Enable
F) I/O information
G) Compulsory I/O information
I) I/O SKIP
(2) Execute the remote connection with applicable project open of the station to connect
to for SoftMaster-PD programming through remote stage 1 & 2 connection.
(3) Up to 2 stages only are available for the remote connection. More than that is not available
for the remote connection.

9-9

Chapter 10 Troubleshooting

Chapter 10 Troubleshooting
This chapter is to describe various errors that may occur in system operation, their causes and
actions to take against. Follow the procedures below to check for errors and error details in
MasterLogic-200 FEnet I/F module. And take suitable actions against the abnormal module states
surely through the troubleshooting in proper procedures. Discretionary repair or disassembly is not
allowed.

10.1 Check through communication module LED

The status of the communication module can be checked through LED display.

10.1.1 Display of Abnormal Operation

The operation status can be checked through LED in front of Ethernet module.

2MLL-EFMT
HS
P2P
PADT

PC

ERR

RUN
I/F
TX
RX
PHY

< LED of 2MLL-EFMT >

[Fig.10.1.1] LED structure of FEnet I/F module
LED

RUN

Error

Turned off after

FEnet powered
on

Action
1) Ethernet communication module incorrectly installed
- check DC 5V power supply of power module.
- check the communication module if correctly installed on
the base.
2) Check if communication module is correctly perceived with
SoftMaster-PD.
1) Check the operation state of CPU module.

I/F

LED on or off
during normal
communication

2) Check the communication module if correctly installed on the

base.
3) Check if module information is correctly perceived with
SoftMaster-200 software.

10-1

Chapter 10 Troubleshooting

LED

Error
Turned off during

P2P

HS

PADT

PC

P2P command
service
Turned off during
HS link service

Action
1) Check if the basic parameter is downloaded correctly.
2) Check if the function block/command is edited correctly.
3) Check if the media is connected correctly.
4) Check if Link Enable is enabled.
1) Check if the basic parameter is downloaded correctly.
2) Check HS link setting if correct.
3) Check if Link Enable is enabled.

Turned off during

1) Check if IP address for remote (PADT) connection is normal.
remote connection
2) Check if remote connection of PADT is disconnected
service

Turned off during

dedicated service

1) Check if IP address for dedicated connection is correct.

2) Check if Host table is enabled.
If Host table is enabled, check if the IP address of HMI(PC) is
registered in the host table.
3) Check if connection is requested from MMI (PC) device.

Turned on during
ERR

TX

RX

PHY

normal
communication
Turned on during
transmitting data
Turned on during
receiving data
Turned off during
normal
communication

1) Check if the basic parameter is downloaded correctly.

2) Check for any error in interface with CPU.

1) Check if request frame is received normally from the client.

1) Check for any error in receiving program.
2) Check for any error in frame edit.
3) Check if the media is connected correctly.
1) Check if the media is composed of 100Mbps.
(Auto-Negotiation)

10-2

Chapter 10 Troubleshooting

10.2 Module Check with SoftMaster-200

SoftMaster-200 program can be used to monitor the communication module simply. Establish
connection between PLC and a PC in which SoftMaster-200 is installed, and then select [Online] ->
[PLC History], [PLC Error/Warning] in SoftMaster-200.

[Fig.10.2.1] PLC history

If a hardware error or a CPU interface error occurs on the module, LED of the communication module
itself operates abnormally in general, whose status can be monitored simply through its dedicated
program.
[Fig.10.2.1] shows error/warning information through PLC History on the SoftMaster-200 [Online]
menu, which can be settled by referring to [Details and Actions].

10-3

Chapter 10 Troubleshooting

10.3 Module Check through Error Codes

Identify the error codes of abnormal operations described in 10.3.1 for troubleshooting. 10.3.2
Troubleshooting will show error details and actions to take against.

10.3.1 Abnormal operations

Error code

Error display

Description

E00-01

ECM_12 ~ ECM_15

H/W self-diagnosis error

E00-02

ECM_13, ECM_18

Interfacing error with CPU

[Table 10.3.1] H/W related error of communication module

Error code

Error display

Description

E02-01

ECM_18

Interface abnormal between FEnet I/F module and

CPU

[Table 10.3.2] Interface operation abnormal with CPU of the communication module

Error code

Description

Cause

E03-01

HS link parameter setting

error

After Online link enabled, HS link parameters

specified incorrectly, or not specified, or cracked.

E03-02

HS link not executable

After link enabled with HS link parameters normal,

communication is not available as desired.

E03-03

_HSxRLNK and _HSxTRX

contacts not On when HS
link executed

After link enabled with HS link parameters normal,

_HSxRLNK is not On.

E03-04

_HSxLTBL contact On
when
HS link executed

After link enabled with HS links _HSxRLNK On,

_HSxLTBL is On due to PLC or communication
error.

[Table 10.3.3] Abnormal operation of HS link function

Error code

Error display

Description

E04-01

[No response] message

displayed when remote
connection requested

RS-232C cable not connected between MasterLogic200 and PLC, or PLC is powered Off

E04-02

[Other error message]

displayed when remote
connection requested

Service not executed normally due to unsuitable

request

[Table 10.3.4] Operation error of PADT communication service function

10-4

Chapter 10 Troubleshooting

10.3.2 Troubleshooting
1) Error code E00-01 : H/W error

H/W error

Powered
normally?

No

Check power/voltage

Yes

Installed
as specified?

No

Let the conditions as

specified

No

Install communication
module correctly

Yes

Communication
module installed
correctly?
Yes

Restart the power

Same error?

No

Operation normal?

Yes

No

Communication module
H/W error. Contact A/S
center

Shoot the trouble of the

applicable error

10-5

Yes

Run

Chapter 10 Troubleshooting

2) Error code E00-02 : Interface error

Interface error

Powered
normally?

No

Check power/voltage

Yes

Installed
as specified?

Let the conditions

modified or complemented
as specified

No

Yes

Communication
Module installed correctly
on basic base?

Install communication
module correctly on the
basic base

No

Yes

Any error on
connector pin of
communication
module?

Yes

Correct connector pin

No
Communication module or
CPU H/W error. Contact A/S
center

End

10-6

Chapter 10 Troubleshooting

3) Error code E02-01 : Interface error with CPU during run

Interface error during run

CPU error
of communication module
interface?

CPU error of
I/O and special module
interface?

No

Yes
Let error module installed
correctly.

Yes
Communication
module installed firmly on
basic base?

No

No

Shoot the trouble in

CPU

Let communication module

installed. correctly

Yes

Powered normally?

No
Check power/voltage

Yes

Installed as specified?

No

Let the conditions

modified as specified

Yes
Communication module H/W
error. Contact A/S center.

End

10-7

Chapter 10 Troubleshooting

4) Error code E03-01 : HS link parameter error

HS link parameter error

CPU back-up
battery normal?

Replace the battery and download

program and parameters.

No

Yes

Network type, slot

and self-station No. set
correct in link setting?

No

Modify link setting as agreeable to

network type and station/slot No.
of the applicable slot.

Yes

Station No. set correct in

registration items?

No

See 6.1.4 to modify station No.

Yes
Any duplicated
block No. for the same
station in registration
items?

Yes

Modify the duplicated block No.

No

Number of Tx items
in registration items more
than 32?

Yes

Reduce the number of Tx

items to below 32.

No

See CPU type and basic

parameters to adjust Tx/Rx area
range.

No

Tx/Rx area suitable in

registration items?
Yes
Download parameters again

Let link enable On.

End

10-8

Chapter 10 Troubleshooting

5) Error code E03-02 : HS link operation error

HS link operation error

Link Enable On?

Let applicable link enable ON in

link enable setting.

No

Yes
Network type,
self-station/slot No. set
correct in link setting?

Set network type and

self-station/slot No.
correct in link setting

No

Yes

Station No. set correct

in registration items

No

See 6.1.4 to set station No.

correct.

No

See CPU type and 6.1.4 to modify

Tx/Rx area range.

No

Configure network correctly as

shown in the flow chart of
E01-01.

Yes

Tx/Rx area correct?

Yes

Network configured
correctly?
Yes
Any error
on the correspondent
station registered?

Yes

Shoot the trouble in the

correspondent station.

No
Download parameters again

Let link enable On.

End

10-9

Chapter 10 Troubleshooting

6) Error code E03-03 : HS links Run link contact On unavailable

HS Run link not On

HS link of each
station normal?

No

Troubleshoot E03-02 of each

station.

No

Set applicable link enable On in

link enable setting of each station.

No

Set the mode of each station to

Run.

No

See 6.1.4 to set station No.

correct.

No

Configure network correctly as

shown in the flow chart of
E01-01.

Yes

Link enable On
of each station?

Yes
Is CPU operation
Of each station in Run
mode?
Yes

Station [Link]
correct as desired?

Yes

Network configured
correctly?

Yes
Any error
on the correspondent
station registered?

Yes

No
Download parameters again

Let link enable On.

End

10-10

Shoot the trouble in the

correspondent station.

Chapter 10 Troubleshooting

7) Error code E03-04 : HS link trouble contact On

Link trouble contact On.

Power of each
station normal?

Yes

Let powered back after actions as

necessary.

No

Set applicable link enable On in

link enable setting of each station.

No

Set the mode of each station to

Run.

No

Configure network correctly as

shown in the flow chart of
E01-01.

Yes

Shoot the trouble in the

correspondent station.

No
Link enable On
of each station?
Yes

Is CPU operation of
each station in Run
mode?
Yes
Network
configured correctly?

Yes
Any error
on any correspondent
station?
No
Check details using HS link
information monitor.

Download parameters and then let link

enable On.

End

10-11

Chapter 10 Troubleshooting

8) Error code E04-01 : MasterLogic-200 communication time-out

ti

MasterLogic-200 communication
t

RS-232C cable
connection error?

Yes

Check the cable connection

status.

No

Communication port
set correct?

No

Reset the port used for

MasterLogic-200
i ti

Yes

Detail specified for the

connection type on
Connection Option
correct?

No

Correct the detail specified

for the connection type

Yes

CPU operation normal?

No

Yes
End

10-12

Shoot the CPU trouble.

Chapter 10 Troubleshooting

9) Error code E04-02 : MasterLogic-200 internal communication error

MasterLogic-200 internal
communication error

RS-232C cable
connection error?

Yes

Check the cable connection

status.

No

Communication port
set correct?

No

Reset the port used for

MasterLogic-200

Yes

Refer to CPU manual to

shoot the CPU error.

Yes

Serious error on
CPU?

No
After disconnected, close
SoftMaster-PD and then let it

End

10-13

Appendix

Appendix
A.1 List of Flags
A.1.1 List of Special Relays (F)
Device 1

Device 2

F0000

Variable

Function

DWORD _SYS_STATE

Type

Mode & Status

PLC mode & run status displayed.

Description

F00000

BIT

_RUN

RUN

RUN status.

F00001

BIT

_STOP

STOP

STOP status.

F00002

BIT

_ERROR

ERROR

ERROR status.

F00003

BIT

_DEBUG

DEBUG

DEBUG status.

F00004

BIT

_LOCAL_CON

Local control

Local control mode.

F00005

BIT

_MODBUS_CON

Modbus mode

Modbus control mode.

F00006

BIT

_REMOTE_CON

Remote mode

Remote control mode.

F00008

BIT

_RUN_EDIT_ST

F00009

BIT

_RUN_EDIT_CHK

F0000A

BIT

_RUN_EDIT_DON
E

F0000B

BIT

_RUN_EDIT_END

Modification during
run
Modification during
run
Modification
complete during run
Modification
complete during run

F0000C

BIT

_CMOD_KEY

Run Mode

Run Mode changed by key.

F0000D

BIT

_CMOD_LPADT

Run Mode

Run Mode changed by local PADT.

F0000E

BIT

_CMOD_RPADT

Run Mode

Run Mode changed by remote PADT.

F0000F

BIT

_CMOD_RLINK

Run Mode

Run Mode changed by remote

communication module.

F00010

BIT

_FORCE_IN

Compulsory input

Compulsory input status.

F00011

BIT

_FORCE_OUT

Compulsory output

Compulsory output status.

F00012

BIT

_SKIP_ON

I/O SKIP

I/O SKIP being executed.

F00013

BIT

_EMASK_ON

Error mask

Error mask being executed.

F00014

BIT

_MON_ON

Monitor

Monitor being executed.

F00015

BIT

_USTOP_ON

STOP

Stopped by STOP function

F00016

BIT

_ESTOP_ON

ESTOP

Stopped by ESTOP function.

F00017

BIT

_CONPILE_MODE Compiling

F00018

BIT

_INIT_RUN

Initializing

Initialization task being performed.

F0001C

BIT

_PB1

Program code 1

Program code 1 selected.

F0001D

BIT

_PB2

Program code 2

Program code 2 selected.

A-1

Program being downloaded during run.

Modification in progress during run.
Modification complete during run.
Modification complete during run.

Compile being performed.

Appendix

Device 1

Device 2

Type

Variable

Function

Description

F0001E

BIT

_CB1

Compile code 1

F0001F

BIT

_CB2

Compile code 2

Compile code 2 selected.

System error

Serious error in system reported.

F0002

DWORD _CNF_ER

Compile code 1 selected.

F00020

BIT

_CPU_ER

CPU error

CPU configuration error found.

F00021

BIT

_IO_TYER

Module type error

Module type not identical.

Module displaced.

F00022

BIT

_IO_DEER

Module installation
error

F00023

BIT

_FUSE_ER

Fuse error

Fuse blown.

F00024

BIT

_IO_RWER

Module I/O error

Module I/O error found.

Error found in Special/communication
module interface.
Serious error detected in external
equipment.

F00025

BIT

_IP_IFER

F00026

BIT

_ANNUM_ER

Module interface
error
External equipment
Error

F00028

BIT

_BPRM_ER

Basic parameter

Basic parameter abnormal.

F00029

BIT

_IOPRM_ER

IO parameter

IO configuration parameter abnormal.

F0002A

BIT

_SPPRM_ER

F0002B

BIT

_CPPRM_ER

Special module
parameter
Communication
module parameter

F0002C

BIT

_PGM_ER

Program error

Program error found.

F0002D

BIT

_CODE_ER

Code error

Program code error found.

F0002E

BIT

_SWDT_ER

System watch-dog

System watch-dog active.

F0002F

BIT

_BASE_POWER_
ER

Power error

Base power abnormal.

F00030

BIT

_WDT_ER

Scan watch-dog

Scan watch-dog active.

System warning

Slight error in system reported.

F0004

DWORD _CNF_WAR

Special module parameter abnormal.

Communication module parameter
abnormal.

F00040

BIT

_RTC_ER

RTC error

RTC data abnormal.

F00041

BIT

_DBCK_ER

Back-up error

Data back-up error found.

F00042

BIT

_HBCK_ER

Restart error

Hot restart unavailable.

F00043

BIT

_ABSD_ER

Run error stop

Stopped due to abnormal run.

F00044

BIT

_TASK_ER

Task impact

Task being impacted.

F00045

BIT

_BAT_ER

Battery error

Battery status abnormal.

F00046

BIT

_ANNUM_WAR

External equipment Slight error detected in external

error
equipment.

F00047

BIT

_LOG_FULL

Memory full

Log memory full

F00048

BIT

_HS_WAR1

HS link 1

HS link parameter 1 error

F00049

BIT

_HS_WAR2

HS link 2

HS link parameter 2 error

F0004A

BIT

_HS_WAR3

HS link 3

HS link parameter 3 error

F0004B

BIT

_HS_WAR4

HS link 4

HS link parameter 4 error

A-2

Appendix

Device 1

Device 2

Type

F0004C

BIT

_HS_WAR5

HS link 5

HS link parameter 5 error

F0004D

BIT

_HS_WAR6

HS link 6

HS link parameter 6 error

F0004E

BIT

_HS_WAR7

HS link 7

HS link parameter 7 error

F0004F

BIT

_HS_WAR8

HS link 8

HS link parameter 8 error

F00050

BIT

_HS_WAR9

HS link 9

HS link parameter 9 error

F00051

BIT

_HS_WAR10

HS link 10

HS link parameter 10 error

F00052

BIT

_HS_WAR11

HS link 11

HS link - parameter11 error

F00053

BIT

_HS_WAR12

HS link 12

HS link - parameter12 error

F00054

BIT

_P2P_WAR1

P2P parameter 1

P2P - parameter1 error

F00055

BIT

_P2P_WAR2

P2P parameter 2

P2P parameter2 error

F00056

BIT

_P2P_WAR3

P2P parameter 3

P2P parameter3 error

F00057

BIT

_P2P_WAR4

P2P parameter 4

P2P parameter4 error

F00058

BIT

_P2P_WAR5

P2P parameter 5

P2P parameter5 error

F00059

BIT

_P2P_WAR6

P2P parameter 6

P2P parameter6 error

F0005A

BIT

_P2P_WAR7

P2P parameter 7

P2P parameter7 error

F0005B

BIT

_P2P_WAR8

P2P parameter 8

P2P parameter8 error

F0005C

BIT

_CONSTANT_ER Fixed cycle error

F0009

WORD

Variable

Function

Description

Fixed cycle error

_USER_F

User contact point

Timer available for user.

F00090

BIT

_T20MS

20ms

CLOCK of 20ms cycle.

F00091

BIT

_T100MS

100ms

CLOCK of 100ms cycle.

F00092

BIT

_T200MS

200ms

CLOCK of 200ms cycle.

F00093

BIT

_T1S

1s

CLOCK of 1s cycle.

F00094

BIT

_T2S

2s

CLOCK of 2s cycle.

F00095

BIT

_T10S

10s

CLOCK of 10s cycle.

F00096

BIT

_T20S

20s

CLOCK of 20s cycle.

F00097

BIT

_T60S

60s

CLOCK of 60s cycle.

F00099

BIT

_ON

Always ON

Bit always ON.

F0009A

BIT

_OFF

Always OFF

Bit always OFF

F0009B

BIT

_1ON

1 scan ON

Bit only ON for the first scan.

F0009C

BIT

_1OFF

1 scan OFF

Bit only OFF for the first scan.

F0009D

BIT

_STOG

Reverse

Every scan reversed.

WORD

_USER_CLK

User CLOCK

CLOCK available to set by user.

F00100

BIT

_USR_CLK0

F00101

BIT

_USR_CLK1

F0010

Repeat specific
scan
Repeat specific
scan

A-3

ON/OFF CLOCK 0 for specific scan

ON/OFF CLOCK 1 for specific scan

Appendix

Device 1

Device 2

Type

Variable

Function

Description

F00102

BIT

_USR_CLK2

Repeat specific scan ON/OFF CLOCK 2 for specific scan

F00103

BIT

_USR_CLK3

Repeat specific scan ON/OFF CLOCK 3 for specific scan

F00104

BIT

_USR_CLK4

Repeat specific scan ON/OFF CLOCK 4 for specific scan

F00105

BIT

_USR_CLK5

Repeat specific scan ON/OFF CLOCK 5 for specific scan

F00106

BIT

_USR_CLK6

Repeat specific scan ON/OFF CLOCK 6 for specific scan

F00107

BIT

_USR_CLK7

Repeat specific scan ON/OFF CLOCK 7 for specific scan

F0011

WORD

_LOGIC_RESULT Logic result

Logic result displayed.

F00110

BIT

_LER

Calculation error

ON for 1 scan if calculation in error.

F00111

BIT

_ZERO

Zero flag

ON if calculation result is 0.

F00112

BIT

_CARRY

Carry flag

ON if Carry found during calculation.

F00113

BIT

_ALL_OFF

Whole output OFF

ON if all output OFF

F00115

BIT

_LER_LATCH

Calculation error
latch

ON kept if calculation in error.

_CMP_RESULT

Compared result

Compared result displayed.

F0012

WORD
F00120

BIT

_LT

LT flag

ON if less than

F00121

BIT

_LTE

LTE flag

ON if less than or equal

F00122

BIT

_EQU

EQU flag

ON if equal

F00123

BIT

_GT

GT flag

ON if greater than

F00124

BIT

_GTE

GTE flag

ON if greater than or equal

F00125

BIT

_NEQ

NEQ flag

ON if not equal

F0013

WORD

_AC_F_CNT

Inspected power cut

Number of inspected power-cuts

displayed.

F0014

WORD

_FALS_NUM

FALS No.

FALS No. displayed.

F0015

WORD

_PUTGET_ERR0 PUT/GET error 0

Main base PUT / GET error

F0016

WORD

_PUTGET_ERR1 PUT/GET error 1

Added base step 1 PUT / GET error

F0017

WORD

_PUTGET_ERR2 PUT/GET error 2

Added base step 2 PUT / GET error

F0018

WORD

_PUTGET_ERR3 PUT/GET error 3

Added base step 3 PUT / GET error

F0019

WORD

_PUTGET_ERR4 PUT/GET error 4

Added base step 4 PUT / GET error

F0020

WORD

_PUTGET_ERR5 PUT/GET error 5

Added base step 5 PUT / GET error

F0021

WORD

_PUTGET_ERR6 PUT/GET error 6

Added base step 6 PUT / GET error

F0022

WORD

_PUTGET_ERR7 PUT/GET error 7

Added base step 7 PUT / GET error

F0023

WORD

_PUTGET_NDR0 PUT/GET complete 0 Main base PUT / GET complete

F0024

WORD

_PUTGET_NDR1 PUT/GET complete 1 Added base step 1 PUT / GET complete

F0025

WORD

_PUTGET_NDR2 PUT/GET complete 2 Added base step 2 PUT / GET complete

F0026

WORD

_PUTGET_NDR3 PUT/GET complete 3 Added base step 3 PUT / GET complete

F0027

WORD

_PUTGET_NDR4 PUT/GET complete 4 Added base step 4 PUT / GET complete

F0028

WORD

_PUTGET_NDR5 PUT/GET complete 5 Added base step 5 PUT / GET complete

A-4

Appendix

Device 1

Device 2

Type

Variable

Function

Description

F0029

WORD

_PUTGET_NDR6 PUT/GET complete 6 Added base step 6 PUT / GET complete

F0030

WORD

_PUTGET_NDR7 PUT/GET complete 7 Added base step 7 PUT / GET complete

F0044

WORD

_CPU_TYPE

CPU type

Information on CPU type displayed.

F0045

WORD

_CPU_VER

CPU version

CPU version displayed.

F0046

DWORD _OS_VER

OS version

OS version displayed.

F0048

DWORD _OS_DATE

OS date

OS released date displayed.

F0050

WORD

_SCAN_MAX

Max. scan time

Max. scan time displayed

F0051

WORD

_SCAN_MIN

Min. scan time

Min. scan time displayed

F0052

WORD

_SCAN_CUR

Present scan time

Present scan time displayed.

F0053

WORD

_MON_YEAR

Month / Year

PLCs time information (Month/Year)

F0054

WORD

_TIME_DAY

Hour / Date

PLCs time information (Hour/Date)

F0055

WORD

_SEC_MIN

Second / Minute

PLCs time information (Second/Minute)

F0056

WORD

_HUND_WK

100 years / Day

PLCs time information (100 years/Day)

Floating decimal calculation result
displayed.
Latched if in incorrect error.

F00570

BIT

_FPU_LFLAG_I

FPU calculation
result
Incorrect error latch

F00571

BIT

_FPU_LFLAG_U

Underflow latch

Latched if underflow found.

F00572

BIT

_FPU_LFLAG_O

Overflow latch

Latched if overflow found.

F00573

BIT

_FPU_LFLAG_Z

Latch divided by 0

Latched if divided by 0.
Latched if invalid calculation.
Reported if incorrect error found.

F0057

F0058

WORD

_FPU_INFO

F00574

BIT

_FPU_LFLAG_V

F0057A

BIT

_FPU_FLAG_I

Invalid calculation
latch
Incorrect error

F0057B

BIT

_FPU_FLAG_U

Underflow

Reported if underflow found.

F0057C

BIT

_FPU_FLAG_O

Overflow

Reported if overflow found.

F0057D

BIT

_FPU_FLAG_Z

Division by 0

Reported if divided by 0.

F0057E

BIT

_FPU_FLAG_V

Invalid calculation

Reported if calculation invalid.

F0057F

BIT

_FPU_FLAG_E

Irregular value input

Reported if irregular value input.

DWORD _ERR_STEP

Error step

Error step saved.

Increased when module refresh
executed.
Increased if module refresh normal

F0060

DWORD _REF_COUNT

Refresh

F0062

DWORD _REF_OK_CNT

Refresh OK

F0064

DWORD _REF_NG_CNT

Refresh NG

F0066

DWORD _REF_LIM_CNT

Refresh LIMIT

F0068

DWORD _REF_ERR_CNT Refresh ERROR

F0070

DWORD

F0072

_MOD_RD_ERR
_CNT
_MOD_WR_ERR
DWORD
_CNT

Increased if module refresh abnormal.

Increased if module refresh abnormal
(TIME OUT).
Increased if module refresh abnormal.

Module READ
ERROR

Increased if module reads 1 word

abnormally.

Module WRITE
ERROR

Increased if module writes 1 word

abnormally.

A-5

Appendix

Device 1

Device 2

Type

Variable

Function

Description

F0074

DWORD _CA_CNT

Block service

F0076

DWORD _CA_LIM_CNT

Block service LIMIT

F0078

DWORD _CA_ERR_CNT

Block service
ERROR

Increased if modules block data service

abnormal.
Increased if modules block data service
abnormal.

F0080

DWORD

Buffer FULL

Increased if CPUs internal buffer is

FULL.

F0082

DWORD _PUT_CNT

PUT count

Increased if PUT executed.

F0084

DWORD _GET_CNT

GET count

Increased if GET executed.

F0086

DWORD _KEY

Present key

Local keys present status displayed.

F0088

DWORD _KEY_PREV

Previous key

Local keys previous status displayed.

_BUF_FULL_CN
T

Increased if modules block data serviced

F0090

WORD

_IO_TYER_N

Discordant slot

F0091

WORD

_IO_DEER_N

Displaced slot

Slot number with discordant module type

displayed.
Slot number with displaced module
displayed.

F0092

WORD

_FUSE_ER_N

Fuse blown slot

Slot number with fuse blown displayed.

F0093

WORD

_IO_RWER_N

RW error slot

F0094

WORD

_IP_IFER_N

IF error slot

F0096

WORD

_IO_TYER0

Module type 0 error

Main base module type error.

F0097

WORD

_IO_TYER1

Module type 1 error

Added base step 1 module type error.

F0098

WORD

_IO_TYER2

Module type 2 error

Added base step 2 module type error.

F0099

WORD

_IO_TYER3

Module type 3 error

Added base step 3 module type error.

F0100

WORD

_IO_TYER4

Module type 4 error

Added base step 4 module type error.

F0101

WORD

_IO_TYER5

Module type 5 error

Added base step 5 module type error

F0102

WORD

_IO_TYER6

Module type 6 error

Added base step 6 module type error

F0103

WORD

_IO_TYER7

Module type 7 error

Added base step 7 module type error

F0104

WORD

_IO_DEER0

Main base module installation error

F0105

WORD

_IO_DEER1

F0106

WORD

_IO_DEER2

F0107

WORD

_IO_DEER3

F0108

WORD

_IO_DEER4

F0109

WORD

_IO_DEER5

F0110

WORD

_IO_DEER6

F0111

WORD

_IO_DEER7

Module installation 0
error
Module installation 1
error
Module installation 2
error
Module installation 3
error
Module installation 4
error
Module installation 5
error
Module installation 6
error
Module installation 7
error

F0112

WORD

_FUSE_ER0

Fuse blown 0 error

Main base Fuse blown error

F0113

WORD

_FUSE_ER1

Fuse blown 1 error

Added base step 1 Fuse blown error

F0114

WORD

_FUSE_ER2

Fuse blown 2 error

Added base step 2 Fuse blown error

F0115

WORD

_FUSE_ER3

Fuse blown 3 error

Added base step 3 Fuse blown error

A-6

Slot number with module Read/Write

error displayed.
Slot number with module interface error
displayed.

Added base step 1 module installation

error
Added base step 2 module installation
error
Added base step 3 module installation
error
Added base step 4 module installation
error
Added base step 5 module installation
error
Added base step 6 module installation
error
Added base step 7 module installation
error

Appendix

Device 1

Device 2

Type

Variable

Function

Description

F0116

WORD

_FUSE_ER4

Fuse blown 4 error

Added base step 4 Fuse blown error

F0117

WORD

_FUSE_ER5

Fuse blown 5 error

Added base step 5 Fuse blown error

F0118

WORD

_FUSE_ER6

Fuse blown 6 error

Added base step 6 Fuse blown error

F0119

WORD

_FUSE_ER7

Fuse blown 7 error

Added base step 7 Fuse blown error

F0120

WORD

_IO_RWER0

Module RW 0 error

Main base module Read/Write error

F0121

WORD

_IO_RWER1

Module RW 1 error

F0122

WORD

_IO_RWER2

Module RW 2 error

F0123

WORD

_IO_RWER3

Module RW 3 error

F0124

WORD

_IO_RWER4

Module RW 4 error

F0125

WORD

_IO_RWER5

Module RW 5 error

F0126

WORD

_IO_RWER6

Module RW 6 error

F0127

WORD

_IO_RWER7

Module RW 7 error

Added base step 1 module Read/Write

error
Added base step 2 module Read/Write
error
Added base step 3 module Read/Write
error
Added base step 4 module Read/Write
error
Added base step 5 module Read/Write
error
Added base step 6 module Read/Write
error
Added base step 7 module Read/Write
error

F0128

WORD

_IO_IFER_0

Module IF 0 error

Main base module interface error

F0129

WORD

_IO_IFER_1

Module IF 1 error

Added base step 1 module interface error

F0130

WORD

_IO_IFER_2

Module IF 2 error

Added base step 2 module interface error

F0131

WORD

_IO_IFER_3

Module IF 3 error

Added base step 3 module interface error

F0132

WORD

_IO_IFER_4

Module IF 4 error

Added base step 4 module interface error

F0133

WORD

_IO_IFER_5

Module IF 5 error

Added base step 5 module interface error

F0134

WORD

_IO_IFER_6

Module IF 6 error

Added base step 6 module interface error

F0135

WORD

_IO_IFER_7

Module IF 7 error

Added base step 7 module interface error

F0136

WORD

_RTC_DATE

RTC date

RTCs present date

F0137

WORD

_RTC_WEEK

RTC day

RTCs present day of the week

F0138

DWORD _RTC_TOD

RTC time

RTCs present time (ms unit)

F0140

DWORD _AC_FAIL_CNT

Power-cut times

Power-cut times saved.

F0142

DWORD _ERR_HIS_CNT

Errors found

Number of found errors saved.

F0144

DWORD _MOD_HIS_CNT

F0146

DWORD _SYS_HIS_CNT

Mode conversion
times
History updated
times

A-7

Mode conversion times saved.

Systems history updated times saved.

Appendix

Device 1

Device 2

F0148

Type

Variable

DWORD _LOG_ROTATE

Function

Description

Log rotate

Log rotate information saved.

F0150

WORD

_BASE_INFO0

Slot information 0

Main base slot information

F0151

WORD

_BASE_INFO1

Slot information 1

Added base step 1 slot information

F0152

WORD

_BASE_INFO2

Slot information 2

Added base step 2 slot information

F0153

WORD

_BASE_INFO3

Slot information 3

Added base step 3 slot information

F0154

WORD

_BASE_INFO4

Slot information 4

Added base step 4 slot information

F0155

WORD

_BASE_INFO5

Slot information 5

Added base step 5 slot information

F0156

WORD

_BASE_INFO6

Slot information 6

Added base step 6 slot information

F0157

WORD

_BASE_INFO7

Slot information 7

Added base step 7 slot information

F0158

WORD

Used block number

Presently used block number

Flash status

Flash block status

Flash Read

ON when reading Flash N block data.

Flash Write

ON when writing Flash N block data.

Flash error

Error found during Flash N block service.

Available contact

Contact point available in program

_RBANK_NUM
_RBLOCK_STAT
WORD
E
_RBLOCK_RD_F
DWORD LAG
_RBLOCK_WR_
DWORD FLAG
DWORD _RBLOCK_ER_F
LAG
WORD _USER_WRITE_
F

F0159
F0160
F0162
F0164
F1024
F10240

BIT

_RTC_WR

RTC RW

Data Write & Read in RTC

F10241

BIT

_SCAN_WR

Scan WR

Scan value initialization

F10242

BIT

F10243

BIT

F1025

WORD
F10250

BIT

Detect external
_CHK_ANC_ERR serious error
_CHK_ANC_WA Detect external
R
slight error
_USER_STAUS_ User contact point
F
Initialization
_INIT_DONE
complete
External serious
_ANC_ERR
error information
External slight error
_ANC_WAR
information

Detection of serious error in external

equipment requested.
Detection of slight error in external
equipment requested.
User contact point
Initialization complete displayed.
Serious error information in external
equipment displayed.
Slight error information in external
equipment displayed.

F1026

WORD

F1027

WORD

F1034

WORD

_MON_YEAR_D
T

Month / Year

Time information data (Month/Year)

F1035

WORD

_TIME_DAY_DT

Hour / Date

Time information data (Hour/Date)

F1036

WORD

_SEC_MIN_DT

Second / Minute

Time information data (Second/Minute)

F1037

WORD

_HUND_WK_DT

100 years / Day

Time information data (100 years/Day)

A-8

Appendix

A.1.2 List of Communication Relays (L)

1) Special register for data link
HS link No. 1 ~ 12
No.

L000000

L000001

Keyword

_HS1_RLIN
K

_HS1_LTRB
L

Type

Bit

Bit

Detail

HS link parameter
No.1s all stations
normally operated

After _HS1RLINK
is ON, abnormal
status displayed

HS link parameter
No.1, Block [Link]
general status
displayed

Description
Displays all stations normally operated as specified
in HS link parameter, which will be On if
[Link] is no error with all stations specified in
parameter in RUN mode
2. All data block is in normal communication as
specified in parameter.
3. The parameter specified in each station itself is
in normal communication. Run_link will be kept
On if once On until stopped by link disenable.
This flag will be On if the station specified in
parameter and the data blocks communication
status are as described below with _HSmRLINK
flag On,.
1. when the station specified in parameter is not
in RUN mode,
2. when the station specified in parameter is in
error,
3. when data blocks communication status
specified in parameter is unstable,
The link trouble will be On if one of those
conditions 1,2 and 3 above occurs. And if such a
condition is back to normal, it will be Off.
Displays the general status of the communication
information for the specified parameters
respective data blocks.

L000020
~
L00009F

_HS1_STAT
E[k]
(k=000~127)

Bit
Array

L000100
~
L00017F

_HS1_MOD[
k]
(k=000~127)

Bit
Array

HS link parameter
No.1, Block No.k
stations Run
operation mode

Displays the operation mode of the station

specified in parameters data block k.

Displays
the
communication
status
of
parameters data block k to check if normal as
specified.

Displays
the
communication
status
of
parameters data block k to check for any error.

HS1STATE[k]=HS1MOD[k]&_HS1TRX[k]&(~_HS
mERR[k])

L000180
~
L00025F

_HS1_TRX[k
]
(k=000~127)

Bit
Array

Normal
communication
displayed with HS
link parameter
No.1, Block No.k
station

L000260
~
L00033F

_HS1_ERR[k
]
(k=000~127)

Bit
Array

HS link parameter
No.1, Block No.k
stations Run error
mode

L000340
~
L00041F

HS link parameter
_HS1_SETB
Displays the setting status of parameters data
Bit
No.1, Block No.k
LOCK
block k.
Array
setting displayed
[k=000~127]
[Table A.1] List of communication flags based on HS link number

A-9

Appendix

HS link No.

L area address

L000500~L00099F

L001000~L00149F

Remarks
Compared with HS link of 1 in [Table 1], other HS link station
numbers flag address will be simply calculated as follows;

4
5

L001500~L00199F
L002000~L00249F

Calculation formula: L area address = L000000 + 500 x (HS link

No. 1)

L002500~L00299F

7
8

L003000~L00349F
L003500~L00399F

L004000~L00449F

10

L004500~L00499F

11

L005000~L00549F

In order to use HS link flag for program and monitoring, use the flag
map registered in SoftMaster-200 for convenient application.

K as a block number is displayed through 8 words by 16 for 1 word for the information of 128 blocks
from 000 to 127.
For example, block information of 16~31, 32~47, 48~63, 64~79, 80~95, 96~111, 112~127 will be
displayed in L00011, L00012, L00013, L00014, L00015, L00016, L00017 from block 0 to block 15
for mode information (_HS1MOD).

A-10

Appendix

P2P parameters : 1~8, P2P block : 0~63

No.

Keyword

Type

Detail

Description

L006250

_P2P1_NDR00

Bit

P2P parameter No.1, block

No.00 service complete
normally

P2P parameter No.1, block No.0 service

complete normally

L006251

_P2P1_ERR00

Bit

P2P parameter No.1, block

No.00 service complete
abnormally

P2P parameter No.1, block No.0 service

complete abnormally

L00626

_P2P1_STATUS0
0

Word

Error code if P2P parameter

No.1, block No.00 service
complete abnormally

Error code displayed if P2P parameter

No.1, block No.0 service complete
abnormally

L00627

_P2P1_SVCCNT0
0

DWord

P2P parameter No.1, block

No.00 service normal
execution times

P2P parameter No.1, block No.0 service

normal execution times displayed

L00629

_P2P1_ERRCNT0
0

DWord

P2P parameter No.1, block

No.00 service abnormal
execution times

P2P parameter No.1, block No.0 service

abnormal execution times displayed

L006310

_P2P1_NDR01

Bit

P2P parameter No.1, block

No.01 service complete
normally

P2P parameter No.1, block No.1 service

complete normally
P2P parameter No.1, block No.1 service
complete abnormally

L006311

_P2P1_ERR01

Bit

P2P parameter No.1, block

No.01 service complete
abnormally

L00632

_P2P1_STATUS0
1

Word

Error code if P2P parameter

No.1, block No.01 service
complete abnormally

Error code displayed if P2P parameter

No.1, block No.1 service complete
abnormally

L00633

_P2P1_SVCCNT0
1

DWord

P2P parameter No.1, block

No.01 service normal
execution times

P2P parameter No.1, block No.1 service

normal execution times displayed

L00635

_P2P1_ERRCNT0
1

DWord

P2P parameter No.1, block

No.01 service abnormal
execution times

P2P parameter No.1, block No.1 service

abnormal execution times displayed

[Table 2] List of communication flags based on P2P service setting

A-11

Appendix

2) List of link devices (N)

P2P No. : 1 ~ 8, P2P block: 0 ~ 63
No.

Keyword

Type

N00000

_P1B00SN

Word

N00001
~
N00004

_P1B00RD
1

Device
structure

N00005

_P1B00RS
1

Word

N00006
~
N00009

_P1B00RD
2

Device
structure

N00010

_P1B00RS
2

Word

N00011
~
N00014

_P1B00RD
3

Device
structure

N00015

_P1B00RS
3

Word

N00016
~
N00019

_P1B00RD
4

Device
structure

N00020

_P1B00RS
4

Word

N00021
~
N00024

_P1B00W
D1

Device
structure

N00025

_P1B00W
S1

Word

N00026
~
N00029

_P1B00W
D2

Device
structure

N00030

_P1B00W
S2

Word

N00031
~
N00034

_P1B00W
D3

Device
structure

N00035

_P1B00W
S3

Word

Detail

Description

P2P parameter No.1,

block No.00s
correspondent station
No.
P2P parameter No.1,
block No.00 area
device 1 to read
P2P parameter No.1,
block No.00 area size
1 to read
P2P parameter No.1,
block No.00 area
device 2 to read
P2P parameter No.1,
block No.00 area size
2 to read
P2P parameter No.1,
block No.00 area
device 3 to read
P2P parameter No.1,
block No.00 area size
3 to read
P2P parameter No.1,
block No.00 area
device 4 to read
P2P parameter No.1,
block No.00 area size
4 to read
P2P parameter No.1,
block No.00 saved
area device 1
P2P parameter No.1,
block No.00 saved
area size 1
P2P parameter No.1,
block No.00 saved
area device 2
P2P parameter No.1,
block No.00 saved
area size 2
P2P parameter No.1,
block No.00 saved
area device 3
P2P parameter No.1,
block No.00 saved
area size 3

P2P parameter No.1, block No.00s correspondent

station No. saved
Use P2PSN instruction to modify during Run if
correspondent station number is used in SoftMaster-PD.

A-12

P2P parameter No.1, block No.00 area device 1 to read

saved
P2P parameter No.1, block No.00 area size 1 to read
saved
P2P parameter No.1, block No.00 area device 2 to read
saved
P2P parameter No.1, block No.00 area size 2 to read
saved
P2P parameter No.1, block No.00 area device 3 to read
saved
P2P parameter No.1, block No.00 area size 3 to read
saved
P2P parameter No.1, block No.00 area device 4 to read
saved
P2P parameter No.1, block No.00 area size 4 to read
saved
P2P parameter No.1, block No.00 saved area device 1
saved
P2P parameter No.1, block No.00 saved area size 1
saved
P2P parameter No.1, block No.00 saved area device 2
saved
P2P parameter No.1, block No.00 saved area size 2
saved
P2P parameter No.1, block No.00 saved area device 3
saved
P2P parameter No.1, block No.00 saved area size 3
saved

Appendix

No.

Keyword

Type

N00036
~
N00039

_P1B00W
D4

Device
structure

N00040

_P1B00W
S4

Word

N00041

_P1B01SN

Word

N00042
~
N00045

_P1B01RD
1

Device
structure

N00046

_P1B01RS
1

Word

N00047
~
N00050

_P1B01RD
2

Device
structure

N00051

_P1B01R
S2

Word

N00052
~
N00055

_P1B01R
D3

Device
structure

N00056

_P1B01R
S3

Word

N00057
~
N00060

_P1B01R
D4

Device
structure

N00061

_P1B01R
S4

Word

N00062
~
N00065

_P1B01W
D1

Device
structure

N00066

_P1B01W
S1

Word

N00067
~
N00070

_P1B01W
D2

Device
structure

N00071

_P1B01W
S2

Word

N00072
~
N00075

_P1B01W
D3

Device
structure

Detail

Description

P2P parameter No.1,

block No.00 saved
area device 4
P2P parameter No.1,
block No.00 saved
area size 4
P2P parameter No.1,
block No.01
correspondent station
No.
P2P parameter No.1,
block No.01 area
device 1 to read
P2P parameter No.1,
block No.01 area size
1 to read
P2P parameter No.1,
block No.01 area
device 2 to read
P2P parameter No.1,
block No.01 area size
2 to read
P2P parameter No.1,
block No.01 area
device 3 to read
P2P parameter No.1,
block No.01 area size
3 to read
P2P parameter No.1,
block No.01 area
device 4 to read
P2P parameter No.1,
block No.01 area size
4 to read
P2P parameter No.1,
block No.01 saved
area device 1
P2P parameter No.1,
block No.01 saved
area size 1
P2P parameter No.1,
block No.01 saved
area device 2
P2P parameter No.1,
block No.01 saved
area size 2
P2P parameter No.1,
block No.01 saved
area device 3

A-13

P2P parameter No.1, block No.00 saved area device 4

saved
P2P parameter No.1, block No.00 saved area size4
saved
P2P parameter No.1, block No.01s correspondent
station No. saved
Use P2PSN instruction to modify during Run if
correspondent station number is used in SoftMaster-PD.
P2P parameter No.1, block No.01 device area 1 to read
saved
P2P parameter No.1, block No.01 area size 1 to read
saved
P2P parameter No.1, block No.01 area device 1 to read
saved
P2P parameter No.1, block No.01 area size 2 to read
saved
P2P parameter No.1, block No.01 area device 3 to read
saved
P2P parameter No.1, block No.01 area size 3 to read
saved
P2P parameter No.1, block No.01 area device 4 to read
saved
P2P parameter No.1, block No.01 area size 4 to read
saved
P2P parameter No.1, block No.01 saved area device 1
saved
P2P parameter No.1, block No.01 saved area size 1
saved
P2P parameter No.1, block No.01 saved area device 2
saved
P2P parameter No.1, block No.01 saved area size 2
saved
P2P parameter No.1, block No.01 saved area device 3
saved

Appendix

No.

Keyword

Type

N00076

_P1B01W
S3

Word

N00077
~
N00080

_P1B01W
D4

Device
structure

N00081

_P1B01W
S4

Word

Detail

Description

P2P parameter No.1,

block No.01 saved
area size 3
P2P parameter No.1,
block No.01 saved
area device 4
P2P parameter No.1,
block No.01 saved
area size 4

P2P parameter No.1, block No.01 saved area size 3

saved
P2P parameter No.1, block No.01 saved area device 4
saved
P2P parameter No.1, block No.01 saved area size 4
saved

Notes
1) If P2P parameters are to be specified with SoftMaster-PD used for N area, the setting will be
performed automatically. And its modification during Run is also available by P2P dedicated
instruction.
2) Since the addresses of N area available are classified according to P2P parameter setting No.
and block index No., the area not used for P2P service can be used as an internal device.

A-14

Appendix

A.2 ASCII Code Table

American National Standard Code for Information Interchange
ASCII
Hex

Dec

00

000

01

Value

ASCII
Hex

Dec

NULL

40

064

001

SOH

41

02

002

STX

03

003

04

Value

ASCII
Hex

Dec

80

128

065

81

129

42

066

82

130

ETX

43

067

83

004

EQT

44

068

05

005

ENQ

45

069

06

006

ACK

46

07

007

BEL

08

008

09

Value

ASCII

Value

Hex

Dec

C0

192

C1

193

C2

194

131

C3

195

84

132

C4

196

85

133

C5

197

070

86

134

C6

198

47

071

87

135

C7

199

BS

48

072

88

136

C8

200

009

HT

49

073

89

137

C9

201

0A

010

LF

4A

074

8A

138

CA

202

0B

011

VT

4B

075

8B

139

CB

203

0C

012

FF

4C

076

8C

140

CC

204

0D

013

CR

4D

077

8D

141

CD

205

0E

014

SO

4E

078

8E

142

CE

206

0F

015

SI

4F

079

8F

143

CF

207

10

016

DLE

50

080

90

144

D0

208

11

017

DC1

51

081

91

145

D1

209

12

018

DC2

52

082

92

146

D2

210

13

019

DC3

53

083

93

147

D3

211

14

020

DC4

54

084

94

148

D4

212

15

021

NAK

55

085

95

149

D5

213

16

022

SYN

56

086

96

150

D6

214

17

023

ETB

57

087

97

151

D7

215

18

024

CAN

58

088

98

152

D8

216

19

025

EM

59

089

99

153

D9

217

1A

026

SUB

5A

090

9A

154

DA

218

1B

027

ESC

5B

091

9B

155

DB

219

A-15

Appendix

ASCII
Hex

Dec

1C

028

1D

Value

ASCII
Hex

Dec

FS

5C

092

029

GS

5D

1E

030

RS

1F

031

20

Value

ASCII
Hex

Dec

9C

156

093

9D

157

5E

094

9E

158

US

5F

095

9F

159

032

(space)

60

096

A0

160

21

033

61

097

A1

161

22

034

"

62

098

A2

23

035

63

099

24

036

64

100

25

037

65

26

038

&

27

039

28

Value

ASCII

Value

Hex

Dec

DC

220

DD

221

DE

222

DF

223

E0

224

E1

225

162

E2

226

A3

163

E3

227

A4

164

E4

228

101

A5

165

E5

229

66

102

A6

166

E9

230

'

67

103

A7

167

EA

231

040

68

104

A8

168

EB

232

29

041

69

105

A9

169

EC

233

2A

042

6A

106

AA

170

ED

234

2B

043

6B

107

AB

171

EE

235

2C

044

6C

108

AC

172

EF

236

2D

045

6D

109

AD

173

F0

237

2E

046

6E

110

AE

174

F1

238

2F

047

6F

111

AF

175

F2

239

30

048

70

112

B0

176

F3

240

31

049

71

113

B1

177

F4

241

32

050

72

114

B2

178

F5

242

33

051

73

115

B3

179

F6

243

34

052

74

116

B4

180

F7

244

35

053

75

117

B5

181

F8

245

36

054

76

118

B6

182

F9

246

37

055

77

119

B7

183

FA

247

38

056

78

120

B8

184

FB

248

39

057

79

121

B9

185

FC

249

3A

058

7A

122

BA

186

FD

250

A-16

Appendix

ASCII
Hex

Dec

3B

059

3C

Value

ASCII
Hex

Dec

7B

123

060

<

7C

3D

061

3E

062

3F

063

Value

ASCII
Hex

Dec

BB

187

124

BC

7D

125

>

7E

126

7F

127

Value

ASCII

Value

Hex

Dec

FE

251

188

FF

252

BD

189

EF

253

BE

190

EF

254

BF

191

EF

255

A-17

Appendix

A.3 Comparison Table of Ethernet Technology

Ethernet

Fast
Ethernet

Gigabit
Ethernet

Technology

Speed
(Mbps)

Transmission
Media

Max. Distance

Token Ring

4,16

UTP

100m

10BASE-T

10

UTP

100m

10BASE-F(Multi Mode)

10

Optical Cable

Max. 2km

10BASE-F(Single Mode)

10

Optical Cable

Max.2.5km

10BASE-5

10

Coaxial Cable

500m

10BASE-2

10

Coaxial Cable

185m

100BASE-T4

100

UTP

100m

100BASE-TX

100

UTP

100m

100BASE-FX(Multi Mode)

100

Optical Cable

412m(Half Duplex)
2km(Full Duplex)

100BASE-FX(Single Mode)

100

Optical Cable

20km

1000BASE-T

1000

UTP

100m

100BASE-FX(Single Mode)

1000

Optical Cable

3km

100BASE-FX(Multi Mode)

1000

Optical Cable

500m

100BASE-T

1000

Coaxial Cable

25m

100VG-AnyLAN

100

UTP

ATM

155-622

UTP, Optical Cable

FDDI(Single Mode)

100

Optical Cable

40-60km

FDDI(Multi-Mode)

100

Optical Cable

2km

A-18

Appendix

A.4 External Dimensions

Unit : mm

A-19

Australia
Honeywell Ltd.
Phone : (61) 2-9353-4500
Fax : (61) 2-9353-7677

Japan
Honeywell Inc.
Phone: (81)3-5440-1395
Fax: (81)3-5440-1368

Singapore
Honeywell Pte Ltd.
Phone: (65) 6355-2828
Fax: (65) 6445-3033

China
Honeywell (Tianjin) Ltd. Beijing
Phone: (86-10) 8458-3280
Fax: (86-10) 8458-3102

South Korea
Honeywell Co., Ltd.
Phone : (82) 2-799-6114
Fax : (82) 2-792-9015

Thailand
Honeywell Systems Ltd.
Phone: (662) 693-3099
Fax: (662) 693-3085

Honeywell (Tianjin) Ltd. Shanghai

Phone: (86-21) 6237-0237
Fax : (86-21) 6237-3102

Malaysia
Honeywell Engineering Sdn Bhd.
Phone: (603) 7958-4988
Fax: (603) 7958-8922

Taiwan
Honeywell Taiwan Ltd.
Phone: (886) 2-2245-1000
Fax: (886) 2-2245-3241

New Zealand
Honeywell Ltd.
Phone: (64-9) 623-5050
Fax: (64-9) 623-5060

For Countries (SE Asia) Listed

below, call Honeywell Singapore
Office
Pakistan, Cambodia, Laos,
Myanmar, Vietnam and East Timor

Indonesia
PT Honeywell Indonesia
Phone : (62) 21-535-8833
Fax : (62) 21-5367-1008
India
Honeywell Automation India Ltd.
Phone: (91) 20-5603-9400
Fax: (91) 20-5603-9800

Philippines
Honeywell Systems Inc.
Phone: (63-2) 633-2830
Fax: (63-2) 638-4013

email : MasterLogic@[Link]

For Countries Listed below,

call Honeywell India Office
Bangladesh, Nepal, and Sri Lanka