Ge Appliances Gefanuc Automation Programmable Control Products Tcp Ip Ethernet Communications For The Series 90T 70 Plc Gfk TCP/IP 90 User's Manual, 1004B

GFK-1004B to the manual c4c82325-fadd-4d5d-a796-7286bc638d35

2015-01-23

: Ge-Appliances Ge-Appliances-Gefanuc-Automation-Programmable-Control-Products-Tcp-Ip-Ethernet-Communications-For-The-Series-90T-70-Plc-Gfk-1004 ge-appliances-gefanuc-automation-programmable-control-products-tcp-ip-ethernet-communications-for-the-series-90t-70-plc-gfk-1004b-users-manual-256144 ge-appliances pdf

Open the PDF directly: View PDF PDF.
Page Count: 268 [warning: Documents this large are best viewed by clicking the View PDF Link!]

GE Fanuc Automation
Programmable Control Products
TCP/IP Ethernet Communications
for the Series 90 -70 PLC
User’s Manual
GFK-1004B January 1996
GFL–002
Warnings, Cautions, and Notes
as Used in this Publication
Warning
Warning notices are used in this publication to emphasize that
hazardous voltages, currents, temperatures, or other conditions that
could cause personal injury exist in this equipment or may be
associated with its use.
In situations where inattention could cause either personal injury or
damage to equipment, a Warning notice is used.
Caution
Caution notices are used where equipment might be damaged if care is
not taken.
Note
Notes merely call attention to information that is especially significant to
understanding and operating the equipment.
This document is based on information available at the time of its publication. While
efforts have been made to be accurate, the information contained herein does not
purport to cover all details or variations in hardware or software, nor to provide for
every possible contingency in connection with installation, operation, or maintenance.
Features may be described herein which are not present in all hardware and software
systems. GE Fanuc Automation assumes no obligation of notice to holders of this
document with respect to changes subsequently made.
GE Fanuc Automation makes no representation or warranty, expressed, implied, or
statutory with respect to, and assumes no responsibility for the accuracy, completeness,
sufficiency, or usefulness of the information contained herein. No warranties of
merchantability or fitness for purpose shall apply.
The following are trademarks of GE Fanuc Automation North America, Inc.
Alarm Master
CIMPLICITY
CIMPLICITY PowerTRAC
CIMPLICITY 90–ADS
CIMSTAR
Field Control
GEnet
Genius
Genius PowerTRAC
Helpmate
Logicmaster
Modelmaster
ProLoop
PROMACRO
Series Five
Series 90
Series One
Series Six
Series Three
VuMaster
Workmaster
Copyright 1994-1996 GE Fanuc Automation North America, Inc.
All Rights Reserved
TCP/IP Ethernet Communications User’s Manual – January 1996 iii
GFK-1004B
Preface
Content of this Manual
Chapter 1. Introduction: Discusses the TCP/IP Ethernet Interface, the communica-
tions software, and the GEnet System Manager.
Chapter 2. Installing the TCP/IP Ethernet Interface: Describes the basic features of
the TCP/IP Ethernet Interface, the installation and power-up of the Inter-
face, and a procedure for the initial checkout of the Interface on your Ether-
net cable.
Chapter 3. The GEnet System Manager-Station Configuration: Describes the instal-
lation and operation of the GEnet System Manager and how to configure a
Series 90-70 PLC Ethernet Station.
Chapter 4. Programming Communications Requests: Describes the ladder program-
ming necessary for communications between PLCs.
Chapter 5. The Station Manager: Describes how to use the Station Manager to pro-
vide on-line supervisory access to the TCP/IP Ethernet Interface.
Chapter 6. Troubleshooting: Describes troubleshooting and problem isolation for the
TCP/IP Ethernet Interface.
Appendix A. Glossary of Terms
Appendix B. Communications Port Characteristics
Appendix C. Soft Switch Parameters
Appendix D. DOS System Files
Appendix E. Data Link Error Codes
Appendix F. Forms
Appendix G. Assigning IP and MAC Addresses
Appendix H Sample Ladder Program
Preface
TCP/IP Ethernet Communications User’s Manual – January 1996
iv GFK-1004B
Related Publications
GFK-0262 Series 90 -70 Programmable Controller Installation and Operation
GFK-0263 Logicmaster 90 Programming Software User’s Manual
GFK-0265 Logicmaster 90 Programming Software Reference Manual
GFK-1029 Logicmaster 90 -70-Ethernet TCP/IP User’s Manual
GFK-0870 Host Communications Toolkit for C/C++ Applications User’s Manual
GFK-1026 Host Communications Drivers for Microsoft Windows User’s Manual
GFK-1063 Host Communications Toolkit for Visual Basic Applications User’s Manual
GFK-1186 TCP/IP Ethernet Communications for the Series 90 -30 PLC Station Manager
Manual
GFK-1084 TCP/IP Ethernet Communications for the Series 90 -30 PLC User’s Manual
We Welcome Your Comments and Suggestions
At GE Fanuc automation, we strive to produce quality technical documentation. After
you have used this manual, please take a few moments to complete and return the
Reader’s Comment Card located on the next page.
Contents
v
GFK-1004B TCP/IP Ethernet Communications User’s Manual – January 1996
Chapter 1 Introduction 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Ethernet Communications System 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Ethernet Interface 1-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The GEnet System Manager (GSM) 1-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Make it Work 1-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quick Guide to the Manual 1-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Installing the Ethernet Interface 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Interface Hardware Overview 2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Board Indicators 2-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restart Button 2-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Battery 2-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port 2-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AUI (Transceiver) Port 2-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Default Station Address Label 2-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Number Label 2-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 1: Installing the Ethernet Controller Board in the PLC 2-5
Equipment Required to Perform the Installation Procedures 2-5 . . . . . . . . . . . .
Ethernet Controller Board Installation 2-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 2: Verifying Proper Power-Up of the Ethernet Interface 2-7
Using the GSM “Access Station Manager” Function 2-7 . . . . . . . . . . . . . . . . . . . .
States of the Ethernet Interface 2-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Powering-Up the Ethernet Interface 2-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems During Power-Up 2-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 3: Configuring the Ethernet Interface with
Logicmaster 90-70 (PLC Module Configuration) 2-11 . . . . . . . . .
PLC Systems with CPU Firmware Version 5.03 or Later 2-12 . . . . . . . . . . . . .
PLC Systems with CPU Firmware Versions Prior to 5.03 2-16 . . . . . . . . . . . . .
Procedure 4: Configuring and Downloading a Station 2-20 . . . . . . . . .
Configuring a Station 2-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading a Station 2-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initiating the Download 2-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems During the Download 2-23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Issue the LOAD Command from the Station Manager 2-23 . . . . . . .
Procedure 5: Testing the Ethernet Interfaces on the Network 2-24 . . .
Field Network Test Utility 2-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Invoking the Field Network Test Utility 2-25 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running Field Network Test 2-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
vi TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Procedure 6: Pinging the TCP/IP Interfaces on the Network 2-30 . . . .
Chapter 3 The GEnet System Manager–Station Configuration 3-1 . . . . . . . . . . . . .
What is the GSM? 3-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why Does a Station Have to be Configured and Downloaded? 3-2 . . . . . . . . . .
Connecting the GSM to the LAN Interface 3-3 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 1: Installing and Starting-Up the GSM 3-4 . . . . . . . . . . . . . . . .
Hardware Requirements 3-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the PC Network Card (for Network GSM Operation) 3-5 . . . . . . . . .
Installing the GEnet System Manager (GSM) Software 3-6 . . . . . . . . . . . . . . . . .
Setting-Up DOS System Files 3-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local GSM Operation (Exclusively) 3-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network GSM Operation (or Both Local and Network) 3-8 . . . . . . . . . . . . .
Unusual Procedures 3-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating or Adding to Existing GSM Software 3-12 . . . . . . . . . . . . . . . . . . . . .
Changing the PC Network Card 3-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting-Up the GSM 3-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working Your Way through the GSM Menus 3-14 . . . . . . . . . . . . . . . . . . . . . .
GSM Keyboard Functions 3-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM Menu Structure 3-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 2: Configuring a Station 3-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information Needed to Configure a TCP/IP Ethernet Interface Station 3-17 . . .
Configure a Station Screen 3-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Station Configuration File 3-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting a Station Configuration File 3-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Station Configuration File 3-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the MAC Address 3-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Editor Menu for Series 90-70 PLCs 3-21 . . . . . . . . . . . . . . . . . . . . .
Saving Changes Before Exiting the Configuration Editor Main Menu 3-21 . .
TCP/IP Parameters Screen 3-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced Parameters Menu 3-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Link Parameters Screen 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Parameters Screen 3-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 3: Downloading a Station 3-29 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download Station Screen 3-29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Locally (Over the Serial Port) 3-29 . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Over the Network 3-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
vii
GFK-1004B TCP/IP Ethernet Communications User’s Manual – January 1996
Section 4: Accessing the Station Manager 3-32 . . . . . . . . . . . . . . . . . . . .
Access Station Manager Screen 3-32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 5: Using the GSM Support Functions 3-33 . . . . . . . . . . . . . . . . .
List All Stations Screen 3-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setup GSM Menu 3-35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the GSM Password Screen 3-35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Download Mode Screen 3-36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Station Manager Mode Screen 3-36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit to DOS 3-36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4 Programming Communications Requests 4-1 . . . . . . . . . . . . . . . . . . . . . .
Section 1: The Communications Request 4-2 . . . . . . . . . . . . . . . . . . . . .
Structure of the Communications Request 4-2 . . . . . . . . . . . . . . . . . . . . . . . . . . .
COMMREQ Function Block 4-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COMMREQ Command Block 4-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channel Commands 4-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Data 4-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Logic Program Controlling Execution of the
COMMREQ Function Block 4-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operation of the Communications Request 4-5 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 2: The COMMREQ Function Block and Command Block 4-6
The COMMREQ Function Block 4-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The COMMREQ Command Block 4-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 3: Channel Commands 4-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establishing a Channel 4-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aborting and Re-tasking a Channel 4-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retrieving Detailed Status on the Channel 4-10 . . . . . . . . . . . . . . . . . . . . . . . .
Specifying the Location of the Channel Status 4-10 . . . . . . . . . . . . . . . . . . . . .
Establish Read Channel (2003) 4-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establish Write Channel (2004) 4-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Send Information Report (2010) 4-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abort Channel (2001) 4-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retrieve Detailed Channel Status (2002) 4-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assign Channel Status Vector (2000) 4-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 4: Status Data 4-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Status Data 4-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of the Status Data 4-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OK Output of the COMMREQ Function Block 4-26 . . . . . . . . . . . . . . . . . . . . .
FT Output of the COMMREQ Function Block 4-26 . . . . . . . . . . . . . . . . . . . . . .
Status Bits 4-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Status Words 4-29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Minor Error Codes 4-31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
viii TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 5: Controlling Communications in the Ladder Program 4-34 .
Essential Elements of the Ladder Program 4-34 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Your Ladder Program 4-37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring the Communications Channel 4-38 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sequencing Communications Requests 4-39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Transfers with One Repetition 4-39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5 The Station Manager 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Station Manager Services 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 1: Accessing the Station Manager 5-2 . . . . . . . . . . . . . . . . . . . .
Accessing the Station Manager Using the GSM 5-3 . . . . . . . . . . . . . . . . . . . . . . . .
Accessing the Station Manager Using an ASCII Terminal 5-4 . . . . . . . . . . . . . . .
Remote Operation of the Station Manager 5-4 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 2: Using the Station Manager 5-5 . . . . . . . . . . . . . . . . . . . . . . . .
Using the Monitor Commands 5-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Modify Commands 5-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Station Manager Command Syntax 5-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Task Identification 5-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Data Representation 5-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numeric Values 5-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Byte String Values 5-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Address 5-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Station Manager in Utility Programs 5-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Soft Switch Entry Utility 5-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field Network Test Utility 5-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
ix
GFK-1004B TCP/IP Ethernet Communications User’s Manual – January 1996
Section 3: Command Descriptions 5-15 . . . . . . . . . . . . . . . . . . . . . . . . . .
CHANNEL Command 5-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BPS Command 5-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHBPS Command 5-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHDATE Command 5-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHLTIME Command 5-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHSOSW Command 5-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHTIME Command 5-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLEAR Command 5-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLSOSW Command 5-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DATE Command 5-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXS Command 5-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HELP Command 5-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOAD Command 5-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOG Command 5-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOGIN Command 5-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOGOUT Command 5-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LTIME Command 5-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NET Command 5-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NODE Command 5-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OK Command 5-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PING Command 5-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROG Command 5-28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REM Command 5-28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REPORT Command 5-29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REPP Command 5-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESTART Command 5-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW Command 5-31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SOSW Command 5-34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STAT Command 5-34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPP Command 5-35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPT Command 5-35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TALLY Command 5-36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TEST Command 5-42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIME Command 5-43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRACE Command 5-43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
xTCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Chapter 6 Troubleshooting 6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview 6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using this Chapter 6-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What to do if you Cannot Solve the Problem 6-4 . . . . . . . . . . . . . . . . . . . . . . . . .
The Power-Up State 6-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Soft Switch Entry State 6-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Field Network Test State 6-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Loader State 6-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Operational State 6-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting When STATUS OK LED is OFF 6-8 . . . . . . . . . . . . . . . . . . . .
Troubleshooting When the STATUS OK LED is ON 6-9 . . . . . . . . . . . . . . . . .
Exception Log Event Error Codes 6-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A Glossary A-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Commonly Used Acronyms and Abbreviations A-1 . . . . . . . . . . . . . . . . . . . . . . .
Glossary of Terms A-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix B Communications Ports Characteristics B-1 . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port for Local GSM Communications B-1 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port Settings B-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port Pinouts B-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Cable B-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Terminal Settings B-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The AUI Port for the Ethernet Interface B-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet AUI Port Pinouts B-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AUI (Transceiver Cable) B-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transceiver Description B-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix C Soft Switch Parameters C-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Config Mode C-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Station Address C-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Source C-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Online C-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backplane Online C-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Load Address C-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify Soft Switch Settings C-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Soft Switch Parameters C-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Soft Switch Parameters Using the GSM C-5 . . . . . . . . . . . . . . . .
Correct Results of Soft Switch Configuration C-7 . . . . . . . . . . . . . . . . . . . . . . .
Contents
xi
GFK-1004B TCP/IP Ethernet Communications User’s Manual – January 1996
Appendix D Sample DOS System Files D-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3Com Etherlink II D-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3Com Etherlink 3 D-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3Com Etherlink 16 D-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3Com Etherlink /MC D-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Western Digital EtherCard PLUS, EtherCard PLUS Elite 16,
EtherCard PLUS/A D-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intel 82593 D-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Xircom Pocket Adapter (PE2) D-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Xircom Pocket Adapter (PE3) D-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMC EtherCard PLUS, EtherCard PLUS Elite 16, EtherCard PLUS/A D-10 . . .
IBM PCMCIA D-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimizing the GSM for Network Operation D-12 . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix E GEnet System Manager Data Link Error Codes E-1 . . . . . . . . . . . . . . . . .
Appendix F Network Test Form F-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Form F-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix G Advanced Information About IP and MAC Addresses G-1 . . . . . . . . . . .
IP Addresses G-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateways G-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subnets G-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC Addresses G-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix H Sample Ladder Program H-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
xii TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Figure 1-1. Major Components of the TCP/IP LAN 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1-2. The Main Tasks for Installing the TCP/IP Ethernet Communications System 1-6 . . . . . . . . . .
Figure 2-1. Ethernet Controller Board 2-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-2. Ethernet Controller Installation in the Series 90-70 PLC 2-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-3. States of the Ethernet Interface 2-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-1. GEnet System Manager (GSM) on 802.3 LAN 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-2. GSM Main Menu 3-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-3. GSM Menu Structure 3-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-4. Configure a Station Screen 3-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-5. Configuration Editor Menu 3-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-6. TCP/IP Parameters Screen 3-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-7. Advanced Parameters Menu 3-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-8. Data Link Parameters Screen 3-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-9. System Parameters Screen 3-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-10. Download Station Screen 3-29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-11. Access Station Manager Screen 3-32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-12. List All Stations Screen 3-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-13. Setup GSM Menu 3-35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-1. Elements of the Communications Request 4-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-2. Operation of the Communications Request for an Establish Read ChannelCommand 4-5 . .
Figure 4-3. Format of the COMMREQ Status Word (CRS Word) 4-29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-4. Format of the Detailed Channel Status Words (DCS Words) 4-29 . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-1. Station Manager Accessed Locally through the 9–pin Serial Port by a GSM in
Local Station Manager Mode (or an ASCII Terminal) 5-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-2. Station Manager Accessed Directly over the Network by a GSM in Network
Station Manager Mode 5-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-3. Station Manager Accessed Remotely over the Network by a GSM in Local
Station Manager Mode using the REM (Remote) Command 5-3 . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-1. Determining the State of the Ethernet Interface 6-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure B-1. Serial Cable to Connect GSM (25–Pin Connector) to Ethernet Interface B-2 . . . . . . . . . . . . . .
Figure B-2. Serial Cable to Connect GSM (9–Pin Connector) to Ethernet Interface B-2 . . . . . . . . . . . . . . .
Figure B-3. Transceiver Cable Connection B-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure B-4. 10Base2 Transceiver Configuration B-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure G-1. IP Address Format for Network Classes A, B, C G-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure G-2. Connecting Two Networks with a Gateway G-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure G-3. Network Configuration Using a Subnet Mask G-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
xiii
GFK-1004B TCP/IP Ethernet Communications User’s Manual – January 1996
Table 2-1. Ethernet Controller Board Indicators 2-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-1. 802.3/Ethernet Cards for the PC 3-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-2. Default PC Hardware Settings for 802.3/Ethernet Cards 3-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-3. GSM Keyboard Functions (Alt-K) 3-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-1. Time Unit Values for Read/Write Repetition Period 4-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-2. Series 90-70 PLC Memory Types 4-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-3. Status Bits (LIS Bits and Channel Status Bits) 4-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-4. Major Error Codes 4-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-5. Minor Error Codes for Major Error Codes 05H (at Remote Server PLC) and
85H (at Client PLC) 4-31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-5. Minor Error Codes for Major Error Codes 5H and 85H (Continued) 4-32 . . . . . . . . . . . . . . . . . .
Table 4-6. Minor Error Codes for Major Error Code 11H (at Remote Server PLC) 4-32 . . . . . . . . . . . . . . . .
Table 4-7. Minor Error Codes for Major Error Code 90H (at Client PLC) 4-33 . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-1. Monitor Commands 5-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-2. Modify Commands 5-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-3. Task Identifiers 5-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-4. Soft Switch Entry Utility Commands 5-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-5. Field Network Test Utility Commands 5-14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-6. Control Characters 5-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-7. Load Source Parameters 5-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-8. Soft Switch Default Values for the Ethernet Interface 5-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-9. Log Event Definitions 5-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-10. Configuration Parameters 5-32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-11. PLC Driver Tallies (Tally c) 5-36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-12. Address Resolution Protocol (ARP) Driver Tallies (Tally f) 5-37 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-13. Channel API Tallies (Tally h) 5-37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-14. Internet Protocol (IP) Tallies (Tally i) 5-38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-15. Internet Control Message Protocol (ICMP) Tallies (Tally j) 5-39 . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-16. Data Link Tallies (part of Tally l) 5-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-17. MAC Layer Tallies (part of Tally l) 5-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-18. Service Request Transfer Protocol (SRTP) Server Tallies (Tally v) 5-41 . . . . . . . . . . . . . . . . . . . . .
Table 5-19. Transmission Control Protocol (TCP) Tallies (Tally w) 5-41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-1. Ethernet Interface Diagnostic Tools 6-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-2. Power-Up State 6-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-3. Soft Switch Entry State 6-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-4. Field Network Test State 6-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-5. Loader State 6-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-6. Operational State 6-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
xiv TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Table 6-7. Troubleshooting with ONLINE LED OFF 6-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-8. Troubleshooting with ONLINE LED ON 6-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-9. Exception Log Event Definitions 6-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6-10. Exception Log Event Codes 6-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table B-1. Pinouts of the Serial Port B-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table B-2. Pinouts of the AUI Port B-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table B-3. 10Base5 Transceiver Configuration B-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table C-1. Soft Switch Settings C-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table E-1. GEnet System Manager Data Link Error Codes E-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table E-2. NDIS Error Codes E-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1section level 1
figure bi level 1
table_big level 1
Restarts for autonumbers that do not restart in each
chapter.
figure bi level 1, reset
table_big level 1, reset
chap_big level 1, reset1
app_big level 1, resetA
figure_ap level 1, reset
table_ap level 1, reset
figure level 1, reset
table level 1, reset Table 1.
these restarts must be in the header frame of chapter 1.
a:ebx, l 1 resetA
a:obx:l 1, resetA
a:bigbx level 1 resetA
a:ftr level 1 resetA
c:ebx, l 1 reset1
c:obx:l 1, reset1
c:bigbx level 1 reset1
c:ftr level 1 reset1
Reminders for autonumbers that need to be restarted
manually (first instance will always be 4)
let_in level 1: A. B. C.
letter level 1:A.B.C.
num level 1: 1. 2. 3.
num_in level 1: 1. 2. 3.
rom_in level 1: I. II. III.
roman level 1: I. II. III.
steps level 1: 1. 2. 3.
1-1
GFK-1004B
Chapter 1Introduction
This manual describes the Series 90-70 Ethernet Interface and the GEnet System Manager
Software (GSM).
The Series 90-70 Ethernet Interface and the GSM, together with applications running on
other Series 90-70 or 90-30 PLCs and host computers, form a complete TCP/IP Commu-
nications System for the Series 90-70 PLC. The host application can be Logicmaster
90-70-TCP/IP Software or an application developed using the Host Communications
Toolkit (HCT). GE Fanuc offers the Logicmaster 90-70-TCP/IP software product and the
Host Communications Toolkit product separate from the Ethernet Interface and GSM.
This chapter provides an overview of the product and covers the following topics.
The Ethernet Communications System,
How to Make the System Work,
Quick Guide to the Manual.
The Ethernet Communications System
The Figure 1-1 shows the major components of the Ethernet Communications System,
along with a third- party compatible device, together on one Ethernet cable. Note espe-
cially the two main parts of the Ethernet Communications system, the Ethernet Interface
and the GEnet System Manager Software, and the separation of functions between them.
TransceiverTransceiver TransceiverTransceiverTransceiver
Ethernet
Interface
Series 90–30
PLC
Series 90–70
PLC
a45401
Network
Connection
Local RS–232 Connection
Ethernet
Cable
Host Computer or
Control Device
IBM PC
Compatible
Series 90–70
PLC
GEnet SYSTEM MANAGER Software
Other Ethernet DevicesTCP/IP Ethernet InterfaceGEnet SYSTEM MANAGER (GSM)
– User Applications
– Logicmaster 90
Programming Software
– Direct Network Attachment
of PLC
– On–board Diagnostics and
Communication Software
Downloaded from GSM
– Creates Configuration Files
for Stations on the Network
– Downloads Configuration
Files and Executive Software
to the TCP/IP Ethernet Interface
– Accesses Station Manager
Software on Interface
– Network and Local Connections
TCP/IP
Ethernet
Interface
TCP/IP
Ethernet
Interface
Figure 1-1. Major Components of the TCP/IP LAN
1
1-2 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
The Ethernet Interface allows you to directly attach the Series 90-70 PLC to an Ethernet
LAN via a user-supplied transceiver and AUI cable, and to communicate with other
PLCs, hosts, and other control devices on the network.
The Ethernet Interface for the Series 90-70 PLC has “client/server” capability. As a “cli-
ent” it can initiate communications with other Series 90 PLCs containing Ethernet Inter-
faces. This is done from the PLC ladder program using the COMMREQ function. As a
“server” it responds to requests from other devices such as Logicmaster 90-70 TCP/IP
Ethernet, a Host computer running a Host Communications Toolkit application, or
another Series 90 PLC acting as a “client”. No PLC programming is required for server
operation.
The Ethernet Interface
An operational Ethernet Interface consists of the Ethernet controller board with resident
firmware and the Ethernet Interface software downloaded from the GEnet System Manager.
(It is the TCP/IP-Ethernet software that distinguishes this product from the similar MMS-
Ethernet product.) The Ethernet controller board provides a physical connection from
the PLC to the Ethernet LAN. It also is shipped with on–board diagnostics, a download
program to complement the downloader on the GEnet System Manager, and a utility pro-
gram that permits testing the cable plant. The controller board becomes a fully function-
al communications interface only after downloading additional software from the GEnet
System Manager.
Capabilities of the Ethernet Interface
The Ethernet Interface brings to your PLC a great deal of capability. It will allow you to:
Directly attach your PLC to an Ethernet network. The Ethernet Interface allows
you to directly attach the Series 90-70 PLC to an Ethernet LAN via a user-supplied
transceiver and AUI cable, and to communicate with host computers and other
Series 90 PLCs on the local network.
Transfer data between PLCs. The Ethernet Interface provides client capability, the
capability to initiate communications to other Series 90 Ethernet Interfaces, using
COMMREQ functions in the ladder program.
Access data using a Host Computer. Computer applications which use the GE
Fanuc Host Communications Toolkit can access data within the Series 90-70 PLC
through the server capability of the Ethernet Interface. Supported computer
operating systems include Windows for Workgroups, Windows NT , HP-UX
9000, DEC VAX/VMS , and DEC Alpha AXP/VMS .
Communicate simultaneously to multiple devices. The multiplexing capabilities of
the Ethernet Interface, along with Ethernet network’s high capacity, allow the PLC
to communicate with several other devices at the same time.
Windows, and Windows NT are trademarks of Microsoft Corporation.
DEC, VAX, Alpha AXP, and VMS are trademarks of Digital Equipment Corporation.
1
1-3
GFK-1004B Chapter 1 Introduction
Maintain Compatibility with other GE Fanuc devices, as well as with devices from
other vendors. The GE Fanuc Series 90–70 PLC with TCP/IP Ethernet Interface is
compatible with the Series 90-30 PLC with TCP/IP Ethernet Interface.
It is also compatible with GE Fanuc Logicmaster 90-70 TCP/IP Ethernet and GE
Fanuc HCT Ethernet products available on DEC, HP, IBM, and other computer
platforms running TCP/IP.
Diagnose and maintain your system, using diagnostic and station management
tools. You can find problems before they become serious. In the event that
communications software upgrades are needed, you can use the network or the
built-in serial port to download the software to the interface.
Indirectly attach to other Local Area Networks and/or wide area networks via third
party IP routers. When configured to use an IP gateway (router), the Ethernet
Interface can communicate with remote PLCs and other nodes reachable through
the router.
Communicate with remote computers via Serial Line Internet Protocol (SLIP)
using modems and/or serial lines. Using third party SLIP software, a remote host
computer can be attached to a TCP/IP network thus allowing it to communicate to
the Series 90 PLC via the Ethernet Interface.
Attachment of the Ethernet Interface to the LAN
The AUI port provides the electrical and mechanical interface to the user-provided
Ethernet transceiver cable, which connects the AUI port to an external user-provided
transceiver. The external transceiver is directly connected to the Ethernet cable.
Various Ethernet baseband media (10Base...) can be interconnected by appropriate re-
peaters. Capabilities and limitations are defined in IEEE 802.3 Chapter 13, “System Con-
siderations for Multi-Segment Networks”.
The Ethernet Controller can operate on any of the following media with the appropriate
user-supplied transceiver cable and transceiver. IEEE 802.3 specifies the definitive re-
quirements of each medium.
10Base5 Coax: 10Base5 uses a 0.4 inch diameter 50–ohm coaxial cable. The maximum
length of a cable segment is 500 meters. The distance between any two stations must be
a multiple of 2.5 meters. A maximum of 100 stations is allowed on a thickwire Ethernet
segment.
10Base2 Coax: 10Base2 uses a 0.2 inch diameter 50–ohm coaxial cable. The maximum
length of a cable segment is 185 meters. A maximum of 30 stations is allowed on a thin-
wire Ethernet segment.
10BaseT: 10BaseT uses a twisted pair cable of up to 100 meters in length between each
node and a hub or repeater. Typical hubs or repeaters support 6 to 12 nodes connected
in a star wiring topology.
10BaseF: 10BaseF has two variations that both use the same type of fiberoptic cable:
10BaseFP can support up to 33 nodes at distances of up to 500 meters from a passive
star; 10BaseFL supports up to 2000 meters between a node and a repeater (a multi-port
repeater would thus constitute a star). Additionally, 10BaseFB provides a means of inter-
connecting (only) repeaters by up to 2000 meters of (the same) fiber optic cable.
1
1-4 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
10Broad36: 10Broad36 uses 75-ohm coaxial cable and CATV-like media components
(taps, amplifiers, headend translators, etc.) to support hundreds of nodes at distances of
up to 2800 meters. Broadband cannot be connected to baseband via repeaters. Broad-
band cable plant design and installation must be in accordance with IEEE 802.7 and re-
quires special expertise. GE Fanuc recommends you contract professional specialists for
these services. Consult your GE Fanuc sales representative or field service office for help
in identifying local specialists.
The Ethernet Software
As stated above, the Ethernet Interface becomes fully functional only after additional software
is downloaded from the GEnet System Manager. The downloaded software consists of:
The Station Manager. The Station Manager provides On–Line supervisory access to the
Ethernet Interface, through either the serial port on the controller board or over the
Ethernet cable. These Station Manager services on the Ethernet Interface include:
An interactive set of commands for interrogating and controlling the station.
Unrestricted access to observe internal statistics, an exception log, and configuration
parameters.
Password security for commands that change station parameters or operation.
Note
The Ethernet Interface firmware provides some Station Manager
functions. Downloaded software adds commands to provide more
functionality.
Communications Software. This software consists of the TCP/IP protocol stack and in-
terface software interfacing the protocol stack with the PLC.
Configuration File. This configuration data consists of an IP address for the Interface, a
subnet mask, and the IP address of a gateway. This data is overridden by any TCP mode
configuration configured for the Ethernet Interface in the LM90 configurator.
The GEnet System Manager (GSM)
The GEnet System Manager is a menu–driven software package that runs on a user–pro-
vided Workmaster or IBM PC. The GSM provides various management and configura-
tion tools. The GSM can be connected to the Ethernet Interface either with a serial RS–232
cable, or over the Ethernet cable. When used over Ethernet, one GSM can conveniently
access any of the Ethernet Interfaces on that cable.
The most essential GSM tools are:
The Configuration Editor
The Downloader
Access to the Station Manager on the Ethernet Interface
In addition, the GSM has the following functions:
Examine the list of configured Ethernet Interfaces.
Examine and modify network–wide configuration parameters.
1
1-5
GFK-1004B Chapter 1 Introduction
Note
Typically, there will be only one GSM on the network. It will contain
configuration information and communications software for all the
GEnet stations on the network.
The Configuration Editor
The Configuration Editor is a menu–driven software package that is part of the GSM.
It is used offline to examine and modify configuration parameters for the GE Fanuc Series
90-70 Ethernet Interfaces on your network. These configuration parameters are stored in files
on the PC hard disk and subsequently downloaded to the interface using the GSM
Downloader.
The Downloader
The Downloader is a utility which transfers the Communications Software and the Configu-
ration File to the Ethernet Interface. The Downloader operates in two modes, local (RS232)
and network. The Downloader and the download mode are selected in the main screen of
the GSM.
Access to the Station Manager on the Ethernet Interface
The Ethernet Interface provides an interactive maintenance interface called the Station Man-
ager (described in Chapter 5). The Station Manager allows you to view current and histori-
cal information about the operation of the Ethernet Interface. The GSM provides access to
the Ethernet Interface and Station Manager in both local and network modes. Access to the
Station Manager and the access mode are selected in the main screen of the GSM.
1
1-6 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
How to Make it Work
There are a number of tasks required to get your Ethernet Communications System
working. These tasks involve not only the Ethernet Interface and the GEnet System Manag-
er Software, but also Logicmaster Configuration and Programming Software. The figure below
illustrates what the tasks are for each part of the system.
a45402
User supplied
IBM PC
compatible
GSM software
Use Configuration
Editor to create
configuration
files for stations
Access
Station Manager
to run
Field Network Test
Use Downloader
to download
configuration
files and
executive software
to Interface
Install Logicmaster software
Fully
Operational
Interface
Use Logicmaster
configuration
package to
configure
Interface
Install Interface in PLC
Power–up PLC
Logicmaster software
Ethernet Interface
Series 90–70
PLC
Power–up PLC again
or restart Interface
Install GSM software
Use Logicmaster 90
programmer package to
program COMMREQs to
initiate communications from
your Series 90–70 PLC *
Access Station Manager on
Interface to monitor
and manage network
*Optional if client capability is needed
Figure 1-2. The Main Tasks for Installing the TCP/IP Ethernet Communications System
1
1-7
GFK-1004B Chapter 1 Introduction
Quick Guide to the Manual
As you can see from Figure 1–2, the tasks to install the TCP/IP Communications System
fall into three categories:
1. GEnet System Manager (GSM) Tasks
2. Ethernet Interface Tasks
3. Logicmaster Configuration and possibly Programming Tasks
The table below breaks down these tasks and identifies where in the manual they are
described.
Tasks Where to go in the Manual
GEnet System Manager (GSM)
Installing, Starting Up, and
Using the GSM
Chapter 3. The GEnet System Manager
Section 1. Installing and
Starting–Up the GSM
Configuring Stations Chapter 3. The GEnet System Manager
Section 2. Configuring Stations
Downloading a Station Chapter 3. The GEnet System Manager
Section 3. Downloading a Station
Accessing the Station Manager
(Terminal Emulation Mode)
Chapter 3. The GEnet System Manager
Section 4. Accessing the Station Manager
Chapter 5. The Station Manager
Ethernet Interface
Installing the Interface Chapter 2. Installing the Ethernet Interface
Procedure 1. Installing the Interface
Powering–Up the Interface Procedure 2. Verifying Proper Power–
Up of the Interface
Configuring the Module
(Setting Soft Switch Configuration)
Procedure 3. Configuring the Interface
with the Logicmaster 90-70
Configurator
Field Network Tests Procedure 5. Testing the TCP/IP Interfaces on
the Network
PING Application Connection Tests Procedure 6. Pinging the TCP/IP Interfaces on
the Network
Monitoring the Station and
Managing the Network
Chapter 5. The Station Manager
Troubleshooting the Interface on
the Network
Chapter 6. Troubleshooting
Logicmaster Configuration/Programming
Configuring the Module
PLC Ladder Programming (COMMREQ)
Chapter 2. Procedure 3. Configuring the Interface
with the Logicmaster 90-70
Configurator
Chapter 4. Programming Communications Requests
2section level 1
figure bi level 1
table_big level 1
2-1
GFK-1004B
Chapter 2Installing the Ethernet Interface
This chapter describes the basic features of the Ethernet Interface, its installation, and a
procedure for its initial checkout on your Ethernet cable. The chapter first provides an
overview of the Ethernet Controller Board, which is the hardware component of the
Ethernet Interface. It is then divided into six sequential Installation Procedures, each
providing an overview of the procedure, explaining the steps to be performed, and de-
scribing the expected results.
As you work through a procedure you may encounter references to the appendices and
other chapters in this manual. These references provide more detailed information
about the subject under discussion.
The installation procedures described in this chapter are listed below:
Procedure 1: Installing the TCP/IP Ethernet Controller Board in the PLC Rack -
Required
Procedure 2: Verifying Proper Power-Up of the Ethernet Interface - Required
Procedure 3: Configuring the Ethernet Interface with the Logicmaster 90-70
Configurator - Required
Procedure 4: Configuring and Downloading a Station - Required
Procedure 5: Testing the Ethernet Interfaces on the Network - Optional
Procedure 6: Pinging the Ethernet Interfaces on the Network - Optional
Some of the procedures require prior cable plant design and installation.
After completing the Installation Procedures you will gain an understanding of the parts
of the network and how they fit together. You will also have confidence that your equip-
ment is working properly.
Ethernet Interface Hardware Overview
The Ethernet Controller board is mounted in the Series 90-70 PLC rack. It is connected to
an external transceiver via a user-provided transceiver cable. The external transceiver is
then connected to the Ethernet cable. The figure below shows the layout of the Ethernet
Controller board.
2
2-2 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
PUSH
SLIDE FROM
FRONT TO
LOCK: FROM
BACK TO
RELEASE
15–PIN
ETHERNET
CONNECTOR
MODEL 70
CMM 741
MODULE OK
ONLINE
STATUS OK
BATTERY
CONNECTIONS
INSTALL NEW
BATTERY BEFORE
UNPLUGGING OLD
BATTERY. USE
IC697ACC701
ON OR BLINK= OK
MODULE
IC697CCM741
LABEL
44A726758–117R01
Y
R
E
B
A
T
T
OPEN
REPLACEMENT
BATTERY
CONNECTOR
CURRENTLY
INSTALLED
BATTERY
CONNECTOR
RESTART
PUSHBUTTON
9–PIN
SERIAL
PORT
LEDS
GROUND
WIRE
DEFAULT
STATION
ADDRESS
LABEL
a44663
SERIAL
NUMBER
LABEL
SERIAL
PORT
RS–232
DTE
2 TX (OUT)
3 RX (IN)
7 GND
TRANSCEIVER
CABLE
WHEN RUNNING
DIAGNOSTICS
PUSH TO RESTART
LAN INTERFACE.
PUSH AND HOLD
TO REQUEST
LAN INTERFACE
DOWNLOAD. INOP
Figure 2-1. Ethernet Controller Board
The Ethernet Controller board has several user-accessible elements.
Three LEDs are located at the top of the board. The Restart pushbutton is located im-
mediately below the LEDs. The battery and battery holder is located to the right of the
LEDs. The battery connectors are located on the controller board between the Restart
button and the 9-pin connector to the serial port. The 15-pin connector, located beneath
the serial port and facing downward, is the transceiver port. The Default Station Ad-
dress label is affixed on the outside of the plastic housing.
2
2-3
GFK-1004B Chapter 2 Installing the Ethernet Interface
Board Indicators
There are three LEDs on the Ethernet Controller board. The table below describes the
meaning of the LED patterns for all possible states.
Table 2-1. Ethernet Controller Board Indicators
Indicator Status Description
MODULE OK ON MODULE OK is ON if the Ethernet Interface has passed
diagnostics and its hardware is operating properly.
OFF It is OFF if the module fails a diagnostic test or if a fatal
failure is detected while the board is running.
BLINKING This LED is blinking if the module is running
diagnostics or is in Soft Switch Entry state.
If this LED and the STATUS OK LED are blinking
together, diagnostics have completed and the operator
is being given a chance to enter Field Network Test.
ONLINE ON ONLINE is ON when the Ethernet Interface is
connected to and ready to communicate on the network.
OFF This LED is OFF when:
the station is not communicating on the network
due to disconnection or a disruption of the cable.
the local station has malfunctioned, or the
Ethernet Interface has been commanded not to enter
the network, or is in a state where network operation
is inappropriate, such as Soft Switch Entry state or
local loading.
BLINKING It is BLINKING when the module is transferring data
on the network or loading over the network.
STATUS OK ON STATUS OK is ON if the module is running without
exception conditions.
OFF This LED is OFF if the module is running and detects an
event that calls for supervisory attention. In this case
you should connect the GSM and follow the instructions
in Chapter 5 to obtain further information.
BLINKING This LED is BLINKING if the module is loading or look-
ing for a load source for the Ethernet Interface software.
Restart Button
The Restart button serves two functions: Restart, and Restart and Reload. The Restart
button is inaccessible when the door to the Ethernet Controller board is closed.
Restart: Pressing the Restart button (for fewer than 5 seconds) forces a restart of the
Ethernet Interface. The power-up diagnostics run and the software on the module is
restarted when the pushbutton is released.
Restart and Reload: Pressing and holding the Restart button for 5 seconds or more
forces a restart and requests a reload of the Ethernet Interface. When the Restart button
is pressed, all LEDs go out. After 5 seconds have elapsed, the STATUS OK LED comes
ON, to indicate that the Ethernet Interface will request a reload. After the Restart push-
button is released, the power-up diagnostics run and the Ethernet Interface requests to
be loaded.
2
2-4 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Notes
In either case, any data being transferred by the Ethernet Interface at
the time of the Restart will be lost.
The Restart Pushbutton will not be operable during the Ethernet
Controller board diagnostic phase. The Ethernet Controller board is in
diagnostic phase when the BOARD OK LED is BLINKING and the
ONLINE and STATUS OK LEDs are off.
Battery
When connected, the battery preserves the contents of RAM when there is no power to
the board. The battery will maintain RAM contents for a minimum of six months.
Warning
The lithium battery presents a fire, explosion, or severe burn risk. Do
NOT: recharge it, remove its polarized connector, disassemble it, heat
it above 100C (212F), incinerate it, or expose its cell contents to water.
Dispose of the battery as required by applicable ordinances or
regulations. When replacing the battery, use only Catalog No.
IC697ACC701. Use of another battery could result in ignition or
explosion of the battery. Replacement batteries can be ordered from
GE Fanuc Automation - NA or any GE Fanuc Authorized Distributor.
Serial Port
The 9-pin serial port (RS-232 interface) is used to connect to the GEnet System Manager
(GSM). The communication software on the distribution diskette may be loaded
through this port. A cable is needed to connect the GSM to the Ethernet Interface (see
Appendix B, Communications Ports Characteristics). The faceplate of the Ethernet Inter-
face must be open to connect the cable. The serial port may also be used with a serial
terminal for local Station Management.
AUI (Transceiver) Port
The 15-pin AUI port provides the electrical and mechanical interface to the user-pro-
vided IEEE 802.3 transceiver cable, which connects the AUI Port to an external Ethernet-
compatible transceiver (see Appendix B for the characteristics of the AUI Port). The ex-
ternal transceiver is directly connected to the Ethernet cable.
Default Station Address Label
The Default Station Address label lists the station address to be used by this module, un-
less changed by the user via soft switches.
Serial Number Label
The Serial Number Label indicates the serial number of this controller board.
2
2-5
GFK-1004B Chapter 2 Installing the Ethernet Interface
Procedure 1: Installing the Ethernet Controller Board in the PLC
This section describes the physical installation of the Ethernet Controller board into the
Series 90-70 PLC rack. For information on the installation procedures for the rack, 90-70
CPU, Power Supply, and other Series 90-70 modules, refer to GFK-0262, Series 90-70 Pro-
grammable Controller Installation and Operation User’s Manual.
Equipment Required to Perform the Installation Procedures
In addition to the Ethernet Controller board, make sure you have the items listed below
before you begin.
A Series 90-70 PLC rack.
A Series 90-70 power supply.
Note
The Ethernet Interface requires a power supply that can provide +5
Vdc and +12 Vdc. Use one of the following power supplies:
IC697PWR711 IC697PWR724
IC697PWR721 IC697PWR748
IC697PWR731
A Series 90-70 CPU.
An operating Logicmaster 90-70 system (serial, parallel, or network version).
A Workmaster, or IBM-compatible personal computer.
The Ethernet Interface software diskette.
A copy of the data sheet applicable to your Ethernet Controller board and cable plant.
A certified Ethernet-compatible transceiver and Ethernet cables.
A serial cable for the RS-232 connector on the Ethernet Controller board (see
Appendix B).
Ethernet Controller Board Installation
The Ethernet Controller board installation is summarized here.
1. Read and record the 12-digit default station address (MAC address) from the printed
label on the Ethernet Controller board. A Station Configuration Data Form is
provided in Appendix F for your convenience in recording the station configuration
information.
2. Be sure the Series 90-70 PLC rack power is OFF.
3. Connect the battery to either of the battery connectors on the controller board.
4. Slide the Ethernet Controller into the Series 90-70 PLC slot for which it was
configured in the system - normally the first available slot to the right of the CPU.
The controller must be placed in the main rack.
2
2-6 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Press firmly to lock the board in place, but do not force the board.
Note
The Ethernet Controller board will not operate properly if there are
empty slots to the left of the slot you select.
5. Connect the free end of the safety wire (18 inch long green wire attached to the
Ethernet Controller board) to the ground lug at the side of the Series 90-70 PLC rack.
(See Figure 2-2).
Warning
The ground wire must be securely fastened to the chassis of the Series
90-70 PLC rack and the rack must be properly grounded. Failure to do
so may cause personal injury and/or improper operation of the LAN.
6. Connect the transceiver cable into the 15-pin AUI Port of the Ethernet Controller
board. Secure the cable with the slide latch mechanism. The other end of the
transceiver cable should be connected to an external IEEE 802.3 compatible
transceiver which is attached to the Ethernet network. SQE must be enabled on the
transceiver.
7. Set the CPU Run/Stop switch to STOP.
8. Continue with Procedure 2: Verifying Ethernet Interface Power-Up.
Ethernet Controller Board Installed in Series 90-70 PLC Rack
P
SU
C
P
a45349
GROUND
WIRE
TRANSCEIVER
CABLE TO
802.3
TRANSCEIVER
B
T
M
E
T
H
E
R
N
E
T
Figure 2-2. Ethernet Controller Installation in the Series 90-70 PLC
Note
The Ethernet Controller board must be installed in the main rack;
installation in an expansion rack is not supported.
2
2-7
GFK-1004B Chapter 2 Installing the Ethernet Interface
Procedure 2: Verifying Proper Power-Up of the Ethernet Interface
Before powering–up the Ethernet Interface, you may wish to connect the GEnet System
Manager (GSM) locally to the Ethernet Interface, and select the “Station Manager” func-
tion from the GSM Main menu. This allows you to observe the progress of the power–
up diagnostics via the Station Manager software on the Ethernet Interface. The GSM is
also used to perform other operations in subsequent Installation Procedures.
Refer to Chapter 3, “The GEnet System Manager”, for instructions on installing the GSM
software on a user-supplied PC-compatible computer.
Note
Alternately, you can use a dumb terminal, or another terminal
emulation product on a PC. However, you will probably find it most
convenient to use the GSM since you will be using the GSM for other
configuration purposes in subsequent steps.
If you do not use the GSM, configure the terminal for 9600 bps, 8 bits, no
parity, and 1 stop bit. See Appendix B, for instructions on making the
serial cable.
Using the GSM “Access Station Manager” Function
The Station Manager software on the Ethernet Interface is accessed by connecting the
Ethernet Interface to a Workmaster or other computer running the GSM software and
selecting the “Station Manager” function from the GSM main menu.
1. There are two ways the GSM can be physically connected to an Ethernet Interface:
Local Connection and Network Connection.
Note
To observe the progress of Power–Up Diagnostics described in this
procedure and to invoke the Field Network Test Utility described in
Installation Procedure 5, the GSM must be connected locally and put in
the Local Station Manager Mode.
A. GSM Using Local Connection. Connect the COM1 RS–232 serial port on the
device running the GSM to the 9–pin connector on the Ethernet Interface. Refer
to Appendix B, for instructions on how to make the RS–232 cable.
B. GSM Using Network Connection. Connect the Ethernet card on the device
running the GSM to the Ethernet Network.
C. For now, use the Local connection.
2. Power–up the computer (on which you have previously installed the GSM software)
into DOS. Refer to Chapter 3 for the GSM installation procedure.
2
2-8 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
3. Set the PC default directory to the GSM directory, by typing:
C:\> cd \gsm
4. Start–up the GSM by typing:
C:\GSM> gsm
5. At the password screen, type in the password. The default password is “gsm”.
6. Once the GSM Main Menu appears, go into the Setup GSM functions to set the
Station Manager communications mode to Local, exiting with <ALT-U>.
7. From the GSM Main Menu, cursor to the “Station Manager” function and press
Enter to select.
If you selected Local Mode in step 6, the GSM will automatically access the Station
Manager of the locally connected Ethernet Interface. If you are prompted for
“Station Name”, you did not select Local Station Manager mode. Repeat step 6.
States of the Ethernet Interface
The figure below shows the 5 possible states of the Ethernet Interface. The states are
distinguished by LED patterns and by unique Station Manager NODE command and
prompt outputs.
Soft Switch
Entry Utility
Power Up/
Restart Certain
Exceptions
Detected
a45163
Soft
Switches
OK?
Pass
Issue ”@”
Station Manager Prompt
<Done>
<Restart>
Yes
Receive
”F”
Response?
Field Network
Test Utility
No
<Restart>
No
RAM
Software
Loaded/Checksum
Correct?
Yes
Loader
Utility
Operational
The operations above the
line are executed from PROM
N
o
The operations below the
line are executed from the
Configuration and
Communications Software
downloaded by the user.
Yes
Figure 2-3. States of the Ethernet Interface
2
2-9
GFK-1004B Chapter 2 Installing the Ethernet Interface
The Ethernet Interface will normally transition from the Power–Up State to the Opera-
tional State without entering any other state.
If there is a problem with the Soft Switch data, however, the Ethernet Interface will tran-
sition automatically to the Soft Switch Entry utility (see Appendix C for instructions).
And if you have not previously downloaded a station configuration to the Ethernet In-
terface, the Ethernet Interface will transition automatically to the Loader utility (see Pro-
cedure 4 for instructions). Also, the operator may manually cause the Ethernet Interface
to enter the Field Network Test utility.
Powering-Up the Ethernet Interface
Follow the procedure below to verify that the Ethernet Interface is operating correctly.
1. Power–up the PLC. This will initiate a series of diagnostic tests.
Upon power–up the Module OK LED blinks, On Line and Status OK LEDs are OFF.
2. Observe the local Station Manager screen if connected. If power–up is successful,
then a Station Manager message similar to the following will be displayed, normally
within 15 seconds
IC697 PLC Factory LAN Interface
Copyright (c) 1990-1995. All rights reserved.
PROM version 2.00 (XXAx),Software version (xxAx)
TCP/IP Ethernet
IP address = 3.0.0.1
MAC address = <<080019010177>> MAC default = <<080019010177>>
EM7A2
3. Also, the LEDs will have the following pattern upon successful power up. At this
time the Ethernet Interface is in the Operational State and Online with no exception
conditions
LED Ethernet Interface Online
Module OK ON
On Line ON/Traffic Blink
Status OK ON
2
2-10 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Problems During Power-Up
The Ethernet Interface may not transition directly to the Operational State upon power–
up or restart. It may stop in another state or a fault may have been detected. Refer to
the table below for possible states your Ethernet Interface can assume after completion
of power-up diagnostics.
LED Pattern Where Stopped Possible Cause Corrective Actions
MODULE OK On
STATUS OK Blinking Loader utility Interface requires a (re)load
of communications software. Load the Communication Soft-
ware. See Procedure 4.
MODULE OK On
ONLINE Off Operational Transceiver or transceiver
cable not (properly) con-
nected.
SQE not enabled on trans-
ceiver.
LAN Online Soft Switch* set
to NO.
Connect cable & transceiver.
Set SQE ON on transceiver in ac-
cord with manufacturer ’s
instructions.
Use LM90 configurator to set
LAN Online Soft Switch* to
“YES”. See Procedure 3.
MODULE OK On
ONLINE On
STATUS OK Off
Operational Exception condition oc-
curred. Use the Station Manager LOG
command as explained in
Chapter 6 under the section,
“Troubleshooting When
STATUS OK LED is OFF”.
MODULE OK Blink-
ing Slowly Soft Switch Entry utility Invalid Soft Switch Data.
Soft Switch Data checksum
invalid. System Software
detected incompatible MAC
address assignments. Cer-
tain system errors.
IP address = 0.0.0.0
Correct Soft Switch Data and
Restart or Reload Ethernet Inter-
face. See Procedures 3
and/or 4.
MODULE OK Off Power-Up/Restart Fatal Error. Inspect the Interface for loose
components, reseat the Inter-
face, and Restart. Recheck
Logicmaster 90 Configuration.
Examine PLC Fault Table for
clues. If the problem persists,
replace the Interface.
* MMS-ETHERNET configuration mode only
2
2-11
GFK-1004B Chapter 2 Installing the Ethernet Interface
Procedure 3: Configuring the Ethernet Interface with
Logicmaster 90-70 (PLC Module Configuration)
Before you can use the Ethernet Interface with the Series 90-70 PLC, you must define
the Ethernet Interface to the PLC. This is called module configuration. This is done
through the Logicmaster 90-70 configuration software. The Logicmaster 90-70 config-
uration software allows you to specify the modules and I/O that will reside in your Se-
ries 90-70 PLC rack(s).
As of Logicmaster 90-70 release 6, you may define either a TCP/IP configuration mode or
an MMS-ETHERNET configuration mode for the Series 90-70 Ethernet Interface. All Lo-
gicmaster 90-70 configuration software earlier than release 6 provided only MMS-
ETHERNET configuration mode.
MMS-ETHERNET configuration mode is primarily used for configuring the Ethernet In-
terface for running the MMS-Ethernet software (refer to GFK-0868, MMS-Ethernet Commu-
nications for the Series 90-70 PLC User’s Manual). The MMS-Ethernet software cannot oper-
ate with a TCP/IP configuration mode. The TCP/IP Ethernet software can run with either
MMS-ETHERNET configuration mode or TCP/IP configuration mode, but certain new
features are supported differently. For example, the location of the sixty-four (64) Channel
Status bits is configured by Logicmaster 90-70 in TCP/IP configuration mode, but must be
specified in an Assign Channel Status Vector COMMREQ in MMS-ETHERNET configura-
tion mode. See Chapter 4, Programming Communications Requests, for more details.
Note
GE Fanuc LAN Interfaces are assigned a unique location for LAN Interface
Status (LIS) in the Logicmaster 90-70 Configurator Package. The location
of the LIS is set when configuring the slot for the Ethernet Interface.
Note
The Logicmaster 90-70 Configurator is distinct from the GEnet System
Manager (GSM) Configuration Editor. The Logicmaster 90-70
Configurator defines a module in the Series 90-70 PLC to the PLC CPU.
The GSM Configuration Editor defines the Ethernet Interface relative to
other nodes in the network.
For the Ethernet Interface specifically, the configuration software allows you to:
Define the configuration mode for the Ethernet Interface (TCP/IP or
MMS-ETHERNET).
Define the status address of the Ethernet Interface.
Assign the IP Address for the Ethernet Interface, and optionally the Subnet Mask
and the Gateway Address (TCP mode only).
Configure the GSM parameters (optional).
2
2-12 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
To configure the Ethernet Interface:
Go to the I/O Configuration rack screen in the Logicmaster 90-70 Configuration Package,
and follow the steps listed in the appropriate section below: PLC Systems with CPU
Firmware Version 5.03 or later, or PLC Systems with CPU Firmware Version prior to 5.03.
PLC Systems with CPU Firmware Version 5.03 or Later
1. Move the cursor to the desired rack and slot location. The slot may be either
unconfigured or previously configured.
2. Press the Communications softkey, i.e., Comm (F6). Your screen display will change
to the one shown on the following page.
2
2-13
GFK-1004B Chapter 2 Installing the Ethernet Interface
3. Press ethnet (F2). Your screen display will change to the one shown below.
4. Make sure Ethernet Interface IC697CMM741 is selected and press Enter. The
configuration screen for the Ethernet Interface will appear.
2
2-14 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Configuration Mode: This currently defaults to TCP/IP. If your Ethernet Interface PROM
version is 1.15 or earlier, or if its TCP/IP software is version 1.28 or earlier, you must use
MMS-ETHERNET configuration mode.
Status Address: The Status Address is the location of the LAN Interface Status (LIS) bits
(16 bits) and the Channel Status bits (64 bits). The Channel Status bits are always located
immediately following the LAN Interface Status bits.
Note
Do not use the 80 bits assigned to the LIS bits and Channel Status bits
for other purposes or your data will be overwritten.
Status Length: For TCP/TP configuration mode, this is fixed at 80 bits (the sum of the LIS
bits and the Channel Status bits).
IP Address, Subnet Mask, Gateway Address, and Name Server IP Address: The values for
the IP Address, Subnet Mask, and Gateway Address should be assigned by the person in
charge of your network (the network administrator). TCP/IP network administrators are
familiar with these parameters. It is important that these parameters are correct, other-
wise the Ethernet Interface may be unable to communicate on the network and/or net-
work operation may be corrupted. It is especially important that each node on the net-
work is assigned a unique IP address.
However, if you have no network administrator and a simple isolated network with no
gateways, you can use the following range of values for the assignment of local IP ad-
dresses:
3.0.0.1 First PLC
3.0.0.2 Second PLC
3.0.0.3 Third PLC
..
..
..
3.0.0.255 Logicmaster TCP or host
Also, on an isolated network, the Subnet Mask, Gateway IP address, and Name Server IP
address can all be 0.0.0.0. (The Name Server IP address is not currently used and is
reserved for future use.)
Note
If the isolated network is ever connected to another network, the IP
addresses 3.0.0.1 through 3.0.0.255 must not be used and the Subnet Mask
and Gateway IP address must be assigned by the Network Administrator.
The IP addresses must be assigned so that they are compatible with the
connected network. Refer to Appendix C for more information on
addressing.
See also the section “Determining If an IP Address Has Already Been
Used” in Procedure 4.
2
2-15
GFK-1004B Chapter 2 Installing the Ethernet Interface
5. Optionally, after you have assigned the IP address, etc., press Page Down to display
the following screen.
The Logicmaster 90-70 Configurator also allows you to optionally configure the MAC
(Station) Address and Network Load Address in TCP/IP configuration mode.
6. Press the Escape key to return to the rack display. Press Escape again to save the
configuration to disk.
7. Power up the PLC. (See Procedure 3 to verify proper power-up of the Ethernet
Interface.)
8. Store the configuration to the PLC.
Refer to GFK-0263, Logicmaster 90 Series 90-70 Programming Software User’s Manual for
more information on configuring the Ethernet Interface using Logicmaster 90-70 soft-
ware.
2
2-16 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
PLC Systems with CPU Firmware Versions Prior to 5.03
In order to support TCP/IP configuration mode, you must have Logicmaster 90-70
release 6 and PLC CPU firmware version 5.03 or later. Certain CPU models (CPU 780,
788, and 789) cannot support firmware version 5.03 or later. To allow support of TCP/IP
Client features (COMMREQs) in pre-5.03 CPUs that cannot support TCP/IP
configuration mode. We support reduced functionality Client support through
MMS-Ethernet configuration mode.
To compensate for the lack of TCP/IP configuration mode, the pre-5.03 CPU user must
take two additional steps that the users of TCP/IP configuration mode do not:
(1) configure TCP/IP parameters (including the IP address of the Ethernet Interface) in
the GSM, and (2) use the Assign Channel Status Vector COMMREQ to specify the
location of the sixty-four (64) Channel Status bits.
1. Move the cursor to the desired rack and slot location. The slot may be either
unconfigured or previously configured.
2. Press the Communications softkey, i.e., Comm (F6). Your screen display will change
to the one shown on the following page.
2
2-17
GFK-1004B Chapter 2 Installing the Ethernet Interface
3. Press Ethernet (F2). Your screen display will change to the one shown below.
2
2-18 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
4. Make sure Ethernet Interface IC697CMM741 is selected and press Enter. You will
then see the screen shown below.
5. Move the cursor to the Config Mode field showing TCP/IP and press Tab. This
changes the field to MMS-ETHERNET. Press Enter to accept the change. The fields
in the screen will change as shown below.
2
2-19
GFK-1004B Chapter 2 Installing the Ethernet Interface
Configuration Mode: This defines the Logicmaster configuration mode. MMS-Ethernet
mode is required for Ethernet Interface firmware 1.15 or earlier.
Status Address: This is the location in PLC CPU memory of the sixteen (16) LAN
Interface Status (LIS) bits. To specify the location of the Channel Status bits, use the
Assign Channel Status Vector COMMREQ.
Note
Do not use the 16 bits assigned to the LIS bits for other purposes or your
data will be overwritten.
Status Length: For MMS-Ethernet configuration mode, this is fixed at 16 bits.
Station Address: The Station address is the MAC address of the Ethernet Interface. If
this field is left as all zeroes, the factory-assigned default MAC address (see the label on
the Ethernet Interface’s faceplate).
LAN Controller Load Source: This identifies where the Ethernet Interface should look for
a GSM download. The choices are:
SERIAL PORT - Only look for a download through the 9-pin serial port on the front
of the Ethernet Interface.
NETWORK - Only look for a download through the Ethernet network.
POLL ALL SOURCES - Alternate looking for a download from the serial port and
from the Ethernet network.
LAN Online: This parameter allows the Ethernet Interface to access the Ethernet
network (YES) or not (NO) after completing its power-up diagnostics. A setting of NO
will prevent any network activity until a configuration with a YES setting is received by
the Ethernet Interface.
Backplane Online: This parameter allows (YES) or disallows (NO) data transfer across
the PLC VME backplane. A setting of NO will prevent any COMMREQs and prevent
any host-requested data transfers from occurring until a configuration with a YES setting
is received by the Ethernet Interface.
Network Load Address: This specifies the GSM “group” to which this Ethernet Interface
belongs. If there is only one GSM on the network, or if this Ethernet Interface will only
be loaded serially, then this parameter should be left at the default value of all zeroes.
2
2-20 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Procedure 4: Configuring and Downloading a Station
For the Ethernet Interface to become a fully Operational station, you must perform two
GSM operations.
Create a station configuration file for the Ethernet Interface.
Download the configuration file and communications software to the Ethernet
Interface.
Each Ethernet Interface requires configuration information and communications soft-
ware in order to operate. The configuration information must be created and stored in a
file using the GSM Configuration Editor for that type of Ethernet Interface. This config-
uration file is downloaded to the Ethernet Interface along with the communications soft-
ware. The file is retained on the PC hard disk for a permanent record of the configura-
tion for each Ethernet Interface in the network.
The configuration information consists of an IP address, a subnet mask, and an IP ad-
dress of a gateway. Configuring a station also associates particular communications soft-
ware with the MAC address of the station for subsequent downloading (communica-
tions software for GE Fanuc CNC Ethernet Interfaces and for GE Fanuc Series 90-70 PLC
Ethernet Interfaces is different). Therefore, a unique configuration file must be created
for each Ethernet Interface.
Configuring a Station
The configuration procedure is performed offline on a personal computer. It is not ex-
plained here, but is found in Chapter 3, “The GEnet System Manager” as described be-
low.
To install the GSM software on a user–supplied Workmaster or PC Compatible, refer to
Chapter 3, Section 1, “Installing and Starting–Up the GSM”.
To configure a station refer to Chapter 3, Section 2, “Configuring a Station”.
The type of parameters you may need to configure include:
Station Name, Type, and MAC Address (always required)
TCP/IP Parameters (IP address, subnet mask, and IP address of a gateway)
2
2-21
GFK-1004B Chapter 2 Installing the Ethernet Interface
Downloading a Station
The software that handles the Ethernet Interface communication services must be
loaded into each Ethernet Interface on the network. This software is loaded together
with the configuration file for each station. The software can be loaded into the Ethernet
Interface through the serial port (locally) or across the network.
When Must a Station Be Downloaded?
When the Ethernet Interface is initially configured.
When you wish to reload the Ethernet Interface with new parameters (i.e.,
configuration was modified).
When you wish to reload the Ethernet Interface with a different software version.
When an Ethernet Interface is replaced for any reason.
Note
An Ethernet Interface must be configured on the GSM before it can be
downloaded by the GSM. See instructions immediately preceding.
Setting-Up the GSM and the Ethernet Interface for the Download
Start by deciding whether you will load locally or over the network. Downloading re-
quires a physical connection (communication cable) between the Ethernet Interface and
the GSM. This may be either the local RS-232 cable (described in Appendix B) or an
Ethernet network connection.
The Network Download Mode is recommended (if you have an Ethernet Interface
installed in the device running the GSM) because the time to download is less than 30
seconds. A download in Local Download Mode takes about 2 minutes due to the lower
data rate of the RS–232 link.
Downloading requires cooperation between the Ethernet Interface and the GSM. Both
must be in appropriate states, and both must be using the same download communica-
tion facility, i.e., local or network.
Before attempting the download make sure you have fulfilled the conditions in the follow-
ing table.
Note
The MAC Address and Load Source Soft Switch of the Ethernet
Interface are normally determined by the Logicmaster configuration, as
set in “Procedure 3: Configuring the Ethernet Interface with
Logicmaster 90-70 (PLC Module Configuration)”.
2
2-22 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
GSM Ethernet Interface
MAC Address You must configure a station
with the MAC Address of the
Ethernet Interface you are go-
ing to download.
The MAC Address of the station must match the
MAC Address of the configuration to be down-
loaded from the GSM
Download Mode/
Load Source Download Mode
The Download Mode must be set
so that it is compatible with the
physical connection to be used.
Set the Download Mode to local
or network as appropriate us-
ing the “Setup GSM” function
in the GSM Main Menu.
Load Source
The Load Source Soft Switch parameter* must be
compatible with the physical connection used to
connect to the GSM. The Load Source options are:
ALT - Accepts either a local or a network down-
load, wherever it finds the Download Server.
Factory Default.
LOC - Accepts only a local download.
NET - Accepts only a network download.
Loader State After putting the Ethernet In-
terface into the Loader State
(right column), see instructions
immediately below, “Initiating
the Download”.
The Ethernet Interface must be in the Loader State
to receive a download.
a. If the Ethernet Interface is new from the fac-
tory, it will automatically enter the Loader State
when powered up. Also, unless overridden
by the PLC CPU configuration (set in Proce-
dure 3), the MAC Address will be the default
address (shown on a label on the board, see
Figure 2-1), and the Load Source will be ALT.
b. For a previously installed Ethernet Interface, if
you are physically close to it, press and hold
the Restart/Load Button on the front of the
Ethernet Interface until the STATUS OK LED
comes ON (about 5 seconds).
If you are not physically close to the Ethernet
Interface and it is not in the Loader State, you
can issue the Station Manager LOAD com-
mand to the Ethernet Interface. See the sec-
tion below entitled “How to Issue the LOAD
Command from the Station Manager.”
* MMS-ETHERNET configuration mode only
Initiating the Download
When the conditions above have been satisfied, initiate the download by selecting the
Download Station function from the GSM Main Menu.
Local Downloading
If the GSM was in the Local Download mode when you initiated the download, you will
be prompted for the STATION_NAME of the station to be downloaded. Type in the
name and press Enter. (The STATION_NAME parameter is the name that you assigned
to the station when it was initially configured.) Then the download will proceed.
When the local download is complete, the GSM changes automatically to Local Station
Manager access. At this time the Ethernet Interface MODULE OK LED should remain
ON, and the STATUS OK LED should stop blinking and remain ON. The ONLINE LED
should be ON if the station is connected to the Ethernet network. A sign-on message
(NODE command output) should appear on the Station Manager screen of the GSM.
2
2-23
GFK-1004B Chapter 2 Installing the Ethernet Interface
Network Downloading
If the GSM was in the Network Download mode when you selected Download Station,
the download will proceed automatically, assuming the Ethernet Interface is connected
to the Ethernet network and is Online.
When the network download is complete, the GSM remains in the Download Server
mode waiting for a download request (from any other stations requesting to be down-
loaded). At this time the Ethernet Interface MODULE OK LED should remain ON, and
the STATUS OK LED should stop BLINKING and remain ON, and the ONLINE LED
should be ON.
Problems During the Download
After the download, the Ethernet Interface should transition to the Operational State.
This is indicated by the MODULE OK and the STATUS OK LEDs remaining ON. If this
is not the case, refer to “Problems During Power-Up” in Procedure 2.
How to Issue the LOAD Command from the Station Manager
If the Ethernet Interface is not already in the Loader State, you must place it in the Loader
State before attempting a download to it. You can press and hold the Restart/Load push-
button until the STATUS OK LED comes on, or you can issue the LOAD command to the
Ethernet Interface from the Station Manager as explained below.
1. Go to the Setup GSM functions from the GSM Main Menu and set the Station
Manager Mode to “Local” or “Network” depending on how the GSM is connected to
the Ethernet Interface.
2. Select the Access Station Manager function from the GSM Main Menu.
3. If you selected the Local Station Manager mode, skip to step 4.
If you selected the Network Station Manager mode the Station Name window will
appear. Enter the STATION_NAME of the station you wish to access and press Enter.
(The STATION_NAME parameter is the name that was assigned to the station when
it was initially configured.) NOTE: If the station cannot access the network, you will
not receive any response to this command. You will need to correct that problem
before proceeding further.
4. Log on to the station. Type “login system” and press Enter. If you are prompted to
enter a password, type “system” (“system” is the default station password) and
press Enter again. NOTE: If the station cannot communicate over the link you’re
using, you will not receive any response to this command. You will need to correct
that problem before proceeding further.
5. Type “load” and press Enter. This causes the station to request a load.
6. Press Esc to exit the Station Manager and return to the GSM Main Menu. Continue
at the preceding section, “Initiating the Download”.
2
2-24 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Procedure 5: Testing the Ethernet Interfaces on the Network
This procedure shows you how to verify operation of the physical network to provide
the necessary foundation for reliable communications.
This procedure will ensure that:
The cable plant is functional,
The physical connection of each node is functional,
All transmission paths meet or exceed the expected low bit error rate.
When you are testing the network, be sure there is an adequate explanation for any-
thing unusual. Logging of exceptions should be the exception, not the rule. Properly
setup nodes and networks can run for long periods (weeks or months) without logging
exceptions.
Field Network Test Utility
This section describes the use of the Field Network Test Utility that is built into the
Ethernet Interface.
All software and configuration needed to perform these tests is contained in the Ether-
net Interface as it is shipped from the factory. You do not need to download the commu-
nications software from the GSM for these tests, however, you may optionally change
Soft Switch parameters as described previously. (However, if you have loaded commu-
nications software, the Field Network Test Utility will still operate properly, and the soft-
ware you loaded will be preserved.) The default parameters provided will work on any
network with up to 50 nodes. For larger networks, consult GE Fanuc Automation – NA if
you need assistance to determine how to test your network.
Note
After you have established confidence in your particular application and
configuration parameters, you can periodically re–test your physical
network while the applications are running. This is done by using the TEST
Station Manager command, but without invoking the Field Network
Test Utility. All the Station Manager commands available in Field
Network Test Utility are also available when the Ethernet Interface is
fully operational.
2
2-25
GFK-1004B Chapter 2 Installing the Ethernet Interface
Invoking the Field Network Test Utility
To invoke the Field Network Test Utility you need to connect the GSM locally to one of
the Ethernet Interfaces on the network.
Refer to Chapter 3, “The GEnet System Manager”, for instructions on installing the
GSM software on a user supplied Workmaster or IBM–PC Compatible computer.
See Installation Procedure 2 in this chapter for instructions on using the terminal
emulation feature of the GSM.
Note
Alternately, you can use a dumb terminal, or another terminal
emulation product on a PC. However, you will probably find it most
convenient to use the GSM terminal emulation feature since you will be
using the GSM for other configuration purposes. Configure the terminal
for 9600 bps, 8 bits, no parity, and 1 stop bit.
Perform the following steps to invoke the Field Network Test Utility.
1. Connect the GSM locally to one of the Ethernet Interfaces on the Network you are
testing.
2. Power up the PLC (if power is already on, you need to cycle power or press the
Restart push–button on the Ethernet Interface ).
3. After step 7 of the power–up diagnostic is complete, the “@” symbol will appear on
the terminal device. After the “@” symbol appears, you have 3 seconds to enter the
single character (“F” or “f”) to invoke the Field Network Test Utility. The “F” will not
be echoed back. Any characters other than “f” or “F” are ignored. If you do not see
a startup message displayed like the one shown below, press the Restart button on
the Ethernet Interface (or cycle power on the station) and repeat this step.
The expected startup message upon entering the Field Network Test Utility is similar
to the one shown here:
@
IC697 PLC Factory LAN Interface
Copyright (c) 1990-1995. All rights reserved.
PROM Version 2.00 (xxAn)
MAC address = <<08001901001f>>, MAC default = <<08001901001f>>
EM7A2
<<< Field Network Test Utility >>>
$
4. Repeat steps 1 through 3 for each Ethernet Interface to be tested.
2
2-26 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Running Field Network Test
Once all stations are running the Field Network Test Utility, you will use the Station
Manager to run tests to verify that the cable plant is operating correctly and to examine
statistics about network performance.
The procedure below describes the steps to be performed for the Field Network Test.
1. Select a station to be the test initiator and connect the GSM to this station. This may
be any Ethernet Interface. If your application uses a particular node to communicate
with most others, we suggest you designate this node as the test initiator.
Note
All commands described in this procedure are issued from your test initiator.
2. Enter the command:
$ test all : Lists all nodes on operating network.
or
$ test 010000000000 : Lists all GE Fanuc nodes on operating network.
The response to “test all” will return a list of the MAC addresses of all nodes attached
to the network and presently operating. (This list may include other vendor’s nodes
since the standard IEEE 802.2 test response mechanism is used. Testing other
vendor’s nodes is, however, beyond the scope of this procedure. Ignore responses
from these nodes.)
Caution
Using either of the addresses “all” or “01000000000” to access stations
on the network is recommended only under controlled test conditions.
Execution of Station Manager commands on an operational network
using these addresses may generate a great deal of traffic and might
degrade network or node performance temporarily.
Compare this list with the nodes in the network. If all expected nodes are not listed,
double-check that each node is powered up, is running the Field Network Test
Utility, and has its drop cable or transceiver cable connected.
Correct any deficiencies and repeat steps 1 and 2 until all nodes to be tested are in
the response list.
This procedure assumes that all stations attached to the network remain either
powered or not powered continuously from step 2 through step 6. Turning any
node(s) ON or OFF or Restarting any node during this test will artificially inflate the
error count.
2
2-27
GFK-1004B Chapter 2 Installing the Ethernet Interface
3. Clear the error log and LLC and MAC tallies in all GE Fanuc test responders in the test.
This step cannot be performed for non–GE Fanuc devices using the Station
Manager.
This step can be done for all Ethernet Interfaces at one time by executing the
following REMote commands:
$ rem 010000000000 login system : Logon to all GE Fanuc stations
$ rem 010000000000 clear log : Clear logs of all GE Fanuc stations
$ rem 010000000000 clear tally : Clear tallies of all GE Fanuc stations
Note
Pressing Ctrl–R will display the last command executed. This is
especially helpful when you are repeating similar commands. Simply
display the previous command, change the desired part of the
command, and press Enter.
This step can be done for individual Ethernet Interfaces by executing the following set of
REMote commands for each Ethernet Interface to be tested.
$ rem <node> login system
$ rem <node> clear log
$ rem <node> clear tally
where <node> is the 12–digit MAC address of the target node.
4. To clear the error log and LLC and MAC tallies in the test initiator Ethernet Interface,
issue the following commands:
$ clear log
$ clear tally
5. Issue the desired TEST command to initiate the network test.
$ test 010000000000 1000 50 256 :Tests all GE Fanuc stations on the
network
or
$ test all 1000 50 256 :Tests all stations on the network
The TEST command causes the test initiator to broadcast 1000 test command frames
of varying lengths and data patterns to all GE Fanuc nodes or all nodes of all types
on the network. All nodes receiving these commands are expected to send a similar
test response back to the initiating node. The initiating node counts all responses
from each responding node.
This command will take about 10 minutes to complete. When the command is com-
plete, a report like the following should be displayed.
<<< Test Results >>> Page 1 of 1
Command: test <<ffffffffffff>> 3e8H 32H 100H ALT
Init Node: <<08001901001f>> Frames sent: 3e8H Nodes responding: 4H
Responding nodes Response recd Response w/err No Response
<<08001901027d>> 3e8H 0H 0H
<<080019010163>> 3e8H 0H 0H
<<080019010043>> 3e8H 0H 0H
<<08001901012c>> 3e8H 0H 0H
2
2-28 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
This TEST ALL command and report shows performance over the network between the
initiating node and each responding node, at a rate comparable to what an application
might experience. For further information, see the descriptions of the TEST and REPORT
commands in Chapter 4.
Verify that all GEnet stations under test are included in the list, either as the initiating node
or as a responding node. Also, all GEnet stations should report,
3e8H Responses received,
0H Responses with error, and
0H No Responses. (A No Response will occur occasionally. But, on average, a
No Response should occur no more than once with the TEST command above
executed with 40,000 frames instead of 1,000 frames.)
Transcribe this report onto a clean copy of the Ethernet Network Test Data Sheet
found in Appendix F, Forms. If you are testing a network with many nodes, you
may need more than one data sheet.
6. When the TEST ALL command has completed and its results have been transcribed,
gather the accumulated error log and LLC and MAC tallies from all GEnet stations
by sending the following commands to each station. Transcribe all non–zero results
to the Data Sheet.
$ rem <node> log
$ rem <node> tally l
7. Get the exception log and LLC and MAC tallies from the initiator by issuing the
following commands:
$ log
$ tally l
Transcribe all non–zero results to the Data Sheet.
The LOG response from each node, including the initiator, should appear as follows:
REM$ <<<Exception Log>>>
REM$ Exception log empty
Make a notation on the Network Test Data Sheet that the log is empty, or record the values,
if any, reported in the log response message.
The TALLY L response from each station should appear as follows:
REM> <<< Data Link Tallies >>>
REM> Unreg = 0000H Lsap0 = 0000H LsapOfl = 0000H EthUnreg = 0000H
REM> MacErr = 0000H BufProb = 0000H UnrecPdu = 0000H TstRcvd = 0000H
REM> TstResp = 0000H
REM>
REM> <<< MAC Tallies >>>
REM> SQEErr = 0000H MisdPack = 0000H FrameErr = 0000H SuccOne = 0000H
REM> CrcErr = 0000H RbufErr = 0000H LateCol = 0000H LostCarr = 0000H
REM> BsyCar = 0000H NoRtry = 0647H SuccMore = 0000H FRtry = 0000H
2
2-29
GFK-1004B Chapter 2 Installing the Ethernet Interface
The TALLY L report provides more detailed information about faults than the TEST ALL
command. Acceptable tally rates are indicated on the Network Test Data Sheet. Note that
certain tallies should always be 0, while other tallies are acceptable if their average rate is
not excessive.
Record the LOG and TALLY L results for each Interface under test.
8. At this point, you have completed your initial checkout of the Ethernet Interface and
its operation on the network. If the acceptance criteria is met, your Interface and
network meets requirements and no further testing is necessary. If the criteria is not
met, refer to Chapter 6, “Troubleshooting”, for the meaning of the log data and refer
to Chapter 5, “The Station Manager”, for meaning of the tally data.
2
2-30 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Procedure 6: Pinging the TCP/IP Interfaces on the Network
PING (Packet InterNet Grouper) is the name of a program used in the Internet to test
reachability of destinations by sending them an ICMP echo request and waiting for a
reply. Most hosts, as nodes on the Internet are called, including the Ethernet Interface,
implement a PING command.
The user should ping each installed Ethernet Interface. When the Ethernet Interface re-
sponds to the ping, it verifies that the interface is operational and configured properly.
Specifically it verifies that acceptable configuration information and communications
software have been downloaded to the interface.
The ping can be executed from a UNIX host or PC (most TCP/IP communications soft-
ware provides a PING command) or from an Ethernet Interface. When using a PC, the
user can refer to the documentation for the PING command, but in general all that is re-
quired is the IP address of the remote host as a parameter to the PING command. For
example, “ping 3.0.0.1”.
Perform the following steps to ping from an Ethernet Interface.
1. Connect the GSM locally to one of the Ethernet Interfaces. Refer to Using the GSM
“Access Station Manager” Function in Procedure 2.
2. Enter the NODE command to verify that the local interface has the correct IP
address.
> node
IC697 PLC Factory LAN Interface
Copyright (c) 1990-1995. All rights reserved.
PROM version 2.00 (xxAx), Software version 2.00 (xxAx)
IP address = 3.0.0.1
MAC address = <<080019010688>>, MAC default = <<080019010688>>
EM7A2
3. Login to be able to use the PING command. (The LOGIN command is described in
Chapter 4).
> login
Password : (The default password is “system”.)
Logged in
=
4. Enter the PING command supplying in turn the IP address for each remote Ethernet
Interface to be tested.
= ping 3.0.0.2
<<<Ping Initiated>>>
<<< Ping Results >>>
Command: ping 3.0.0.2 1 100 64
Sent = 1, Received = 1, No Timely Response = 0
Late/Stray Response = 0
Round-trip (ms) min/avg/max 0/1/10
2
2-31
GFK-1004B Chapter 2 Installing the Ethernet Interface
5. The most recent PING results (and the parameters used to obtain them) can be
viewed using the REPP command. Both commands, as well as the STOPP command
are described in detail in Chapter 5.
Alternately, remote Station Manager connection may be used. Again, refer to the
section “Using the GSM ‘Access Station Manager’ Function” in Procedure 2.
REM>
REM> > login system
REM>
REM= Logged in
REM= =
REM= ping 3.0.0.2
<<<Ping Initiated>>>
REM= <<< Ping Results >>>
REM= Command: ping 3.0.0.2 1 100 64
Sent = 1, Received = 1, No Timely Response = 0
Late/Stray Response = 0
Round-trip (ms) min/avg/max 10/10/10
REM=
REM= =
3section level 1
figure bi level 1
table_big level 1
3-1
GFK-1004B
Chapter 3The GEnet System Manager–Station
Configuration
This chapter describes how to install the GEnet System Manager (GSM), and how to use
it to configure your Ethernet Interface. The chapter includes an overview of the GSM
and a detailed guide to the basic menus that are used in configuring and managing your
Ethernet Interface.
The chapter is divided into 5 sections.
Section 1. Installing and Starting-Up the GSM
Section 2. Configuring a Station for a Basic Network
Section 3. Downloading a Station via the GSM
Section 4. Accessing the Station Manager
Section 5. GSM Support Functions
Note
The GSM is used to maintain a variety of LAN Interfaces. Parts of this
chapter are written so as to reflect this generality. Thus, you may see
occasional references to LAN Interfaces other than the type(s) you use.
a45341
802.3 LAN TRANSCEIVER
GSM
(LOCAL)
TRANSCEIVER
GSM
(NETWORK)
RS–232 LINK
TRANSCEIVER
SERIES 90–70 PLC WITH
ETHERNET INTERFACE
TRANSCEIVER
SERIES 90–30 PLC WITH
ETHERNET INTERFACE
Figure 3-1. GEnet System Manager (GSM) on 802.3 LAN
3
3-2 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
What is the GSM?
The GEnet System Manager (GSM) is a menu-driven software package that runs on a
user-provided personal computer (PC). The GSM is used to perform management func-
tions for LAN Interfaces. The GSM software operates under the MS-DOS environment.
The primary GSM functions are:
Configure Station Parameters
Access is provided to one or more LAN Interface Configuration Editors. The
Configuration Editor is used to examine and modify the configuration
information for each LAN Interface on the network. There is a unique
Configuration Editor for each type of LAN Interface. The Configuration Editor
is supplied with your LAN Interface Software, and is integrated with the GSM
during installation. Station configuration is performed off-line on the PC and
results in a configuration file on the hard disk unique to each station.
Download the Configuration and Communications Software to a LAN Interface
This function is used to download initial or revised configuration parameters or
LAN Interface software. The download can occur either over a local serial cable
or over the network.
Access the Station Manager software on a LAN Interface
For this function, the GSM becomes a simple terminal emulator that connects to
the LAN Interface Station Manager either over a local serial cable or over the
network.
The GSM also provides the following support functions.
List All Configured Stations
Change GSM Password
Set Download and Station Manager Communication Modes (Local or Network)
Why Does a Station Have to be Configured and Downloaded?
LAN Interfaces consist of a circuit board with processor and Ethernet circuitry, loaded
with configuration information and communications software.
The power-up diagnostics and loader software reside in Programmable Read Only Memory
(PROM) on the board, and cannot be changed without physically disassembling the
LAN Interface.
Some very basic parameters, known as Soft Switch Parameters, are stored in another kind of
memory, Electronically Erasable PROM (EEPROM). In the future, other configuration
parameters may be stored here.
3
3-3
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
These Soft Switches are set to default values during manufacture of the LAN Interface
and are retained indefinitely until changed by the user, normally via the Logicmaster 90
Configurator. For a LAN Interface, the Logicmaster 90 Configurator has access only to
these Soft Switch parameters. All other parameters of the LAN Interface are set using
the GSM.
The communications software, along with all other configuration information, is set and main-
tained on the GSM, and must be downloaded to the LAN Interface when a software or
configuration change is required. This information is stored on the LAN Interface in ei-
ther battery-backed RAM . This memory technology permits ready change of the
memory content (via downloading from the GSM).
Connecting the GSM to the LAN Interface
The GSM may be carried to the station and connected to the LAN Interface with an
RS-232 cable. We refer to this method of connection as local communications mode or
local GSM operation.
Alternatively, the GSM can reside at a central location on the network and “logically”
connect to any station over the Ethernet network. We refer to this method of connection
as network communications mode or network GSM operation.
You must choose which mode of operation you desire.
When using RS-232, the serial cable is connected between the LAN Interface 9-pin con-
nector and the personal computer COM1 port. See Appendix B for serial port character-
istics.
To connect to the LAN over the network, you must have an appropriate network card or
PCMCIA adapter for your PC-Compatible computer. See Table 3-1 for a list of sup-
ported interfaces.
Figure 3-1 illustrates these alternative connection means of the GSM. The GSM may use
either an internal or external transceiver; or none if used exclusively for local operation.
Note
We recommend there be only one GSM on the network. It will contain
configuration information and communications software for all the
GEnet stations on the network.
3
3-4 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 1: Installing and Starting-Up the GSM
This section describes the hardware requirements for running the GEnet System Manag-
er (GSM) software, and tells you how to install the GSM on the hard disk of your per-
sonal computer.
Topics covered are:
Hardware Requirements
Installing the PC Network Interface Card (for Network GSM Operation)
Installing the GEnet System Manager Software
Setting-Up the DOS System Files
For Local GSM Operation (Exclusively)
For Network GSM Operation (or both Local and Network)
Unusual Procedures
Starting Up the GSM
LAN Interface Software is licensed separately from your LAN Interface hardware. For
PLC LAN Interfaces, this software is provided in 3 1/2-inch double-density format; for
CNC, 3 1/2-inch high-density diskette format only. The GSM software is part of this
LAN Interface Software.
These diskettes do not contain the MS-DOS operating system. You must boot your com-
puter from your hard drive or another diskette containing this operating system soft-
ware.
Hardware Requirements
The following hardware is required in order to support the GSM software on the PC:
PC Compatible, DOS Version 5.0 or later.
RAM: Minimum of 525,000 bytes free (“largest executable program size” on DOS
MEM command).
2 MBytes of free hard disk space.
3 1/2 inch double-density diskette drive (for CNC, 3 1/2-inch high-density also
supported).
Color or monochrome monitor.
For network GSM operation, an NDIS-compliant, 802.3/Ethernet card installed in the
PC. A list of supported cards is shown in the next section.
3
3-5
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Installing the PC Network Card (for Network GSM Operation)
The table below lists the 802.3/Ethernet cards that GE Fanuc has tested for proper net-
work GSM operation. If you wish to access stations from the GSM across the network,
you must have a network card or PCMCIA adapter in your PC. The PC network card
must support NDIS (Network Driver Interface Specification). If you use a PC network
card not in the list below, GE Fanuc cannot guarantee proper operation of the GSM.
Table 3-1. 802.3/Ethernet Cards for the PC
Vendor Model Size PC Bus Width
3Com Etherlink II (3C503) Half slot XT, AT 8-bit
3Com Etherlink 16 (3C507) 1 slot XT, AT 8-bit
3Com Etherlink/MC (3C523) 1 slot Micro Channel 8-bit
SMC/Western Digital EtherCard PLUS Half slot XT, AT 8-bit
SMC/Western Digital EtherCard PLUS Elite 16 1 slot AT 16-bit
SMC/Western Digital EtherCard PLUS/A 1 slot Micro Channel 16-bit
Intel Intel 82593 Interface is built-in to Zenith Z-note PC
Xircom Xircomϖ Pocket Adapter External Enhanced
Printer Port N/A
NDIS supporting
network card Vendor-dependent
Etherlink II, Etherlink 16, and Etherlink M/C are trademarks of 3Com Corporation.
EtherCard PLUS, EtherCard PLUS Elite16, and EtherCard PLUS/A are trademarks of Western Digital Corp.
Z-Note is a trademark of Zenith Data Systems.
Intel is a Registered Trademark of Intel Corporation.
Xircom is a Registered Trademark of Xircom Incorporated.
SMC is a Registered Trademark of Standard Microsystems Corporation.
Note
The PC can lock-up if you make setup errors when installing PC
network cards and device drivers in a PC. Be sure you have a system
boot diskette to recover from possible setup errors.
When installing the network card in your PC, be sure to do the following.
1. Install the network card into the computer according to the manufacturer’s
instructions. Setup the hardware as described in the table below; these are the
default settings of the card. If you do not use the default settings, you will need to
record your settings for later use in the section, “Setting-Up DOS System Files”.
3
3-6 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Table 3-2. Default PC Hardware Settings for 802.3/Ethernet Cards
Vendor Vendor Model [Restrictions] Default Hardware Settings
3Com Etherlink II (3C503) I/O base address = 0x0300, IRQ3
3Com Etherlink 16 (3C507) I/O base address = 0x0300, IRQ3
3Com Etherlink/MC
[ELNKMC.SYS v 2.0 min] N/A
SMC/Western Digital EtherCard PLUS I/O base address = 0x0280, IRQ3,
Memory Address = 0D00H
SMC/Western Digital EtherCard PLUS Elite 16 I/O base address = 0x0280, IRQ3,
Memory Address = 0D00H
SMC/Western Digital EtherCard PLUS/A I/O base address = 0x0280, IRQ3,
Memory Address = 0D00H
Intel Intel 82593 I/O base address = 0x0300, IRQ15,
Xircom Xircom Pocket Adapter
[PE2NDIS.EXE v 1.44 min] None
NDIS supporting net-
work card Vendor-dependent
2. Install the device driver software provided with your network card.
3. Run any diagnostic software provided by the manufacturer of the network card to
ensure that the card is working properly.
Installing the GEnet System Manager (GSM) Software
To become fully operational, your GEnet LAN Interface hardware requires correspond-
ing GEnet LAN Interface Software. This software is provided on floppy diskettes.
For PLC LAN Interfaces, each diskette contains the GSM software as well as the Commu-
nications Software and Configuration Editor for your LAN Interface. Select the size of dis-
kette you wish to use.
For CNC LAN Interfaces, each diskette contains the GSM software as well as the Com-
munications Software and Configuration Editor for one Station Type/Load Type (e.g.,
Series 15MA, Series 15TT, Series 16MA, etc.). Select the diskette that is compatible with
your Station Type/Load Type.
Caution
Preserve the original software diskette as a master. Set the diskette
write protection to avoid damage to the diskette, copy the diskette, and
retain the original as master software. Only working copies should be
used for running the software.
During the installation of the GSM and LAN Interface software, sample DOS system files will
be created in the C:\GSM directory. When the software installation is complete, you will need
to modify your DOS system files based on the sample files. Refer to the sections on setting-up
the DOS system files after you have completed the GSM software installation.
Perform the steps described below to install the GSM software onto your hard disk.
1. Power-up the PC into DOS.
2. Go to the root directory (\) of the drive on which you want to install the GSM. We
recommend that you install the GSM on C: because the sample DOS System Files for
your PC Interface card are created using C: (see Appendix D).
3
3-7
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
3. Create a directory for the GSM by typing:
C:\> mkdir gsm
4. Change the default directory to the GSM directory by typing:
C:\> cd gsm
Note
Do not simply copy all of the files from the GSM diskette. Follow the
installation procedure.
5. With the GSM directory as the default; place the LAN Interface software diskette
into drive A or drive B. If you use drive A, type the instruction below.
C:\GSM> a:install
If you use drive B, type the instruction below.
C:\GSM> b:install
The files that make up the Configuration Editor, the Communications Software, and
the GSM executable software are now installed in the GSM directory.
6. After the GSM files are installed, the following message will be displayed.
Current GSMCFG pathname is : C:\GSM\CFILES
Specify GSMCFG pathname : _
Where GSMCFG is the GSM environment variable which specifies the location of
the station configuration files you will later create with the GSM.
The environment variable must be specified in your AUTOEXEC.BAT to take effect.
The current step, however, defines it only in the AUTOEXEC.GSM sample file in the
GSM directory.
It is recommended that you use the default pathname which is C:\GSM\CFILES
(when installing on drive C).
To accept the default pathname, press Enter.
Note
If you ever move your GSM station configuration files, you must
redefine the GSMCFG variable in AUTOEXEC.BAT to specify the new
location.
7. Next, you will be prompted to specify the type of network card installed in your PC.
A. If you are going to use the GSM for local operation only, enter “0” (for no LAN
interface installed).
B. If you are going to use the GSM for network operation only or for both network
and local operation, specify the type of PC network card installed in your PC.
Selections in the menu include the PC network card types listed in Table 3-1.
Enter the number for the desired PC Network card type and press Enter.
This completes the installation of the software for Network GSM operation. You must
now set up the various DOS system files as explained below before the GSM will run
properly.
3
3-8 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Setting-Up DOS System Files
After you have completed the GSM software installation procedure, you will need to
modify your DOS system files for proper operation of the GSM. Refer to the appropriate
section below for setting-up your DOS system files.
Local GSM Operation (Exclusively)
During the GSM installation for local operation, two sample files were created in the
C:\GSM directory. These files are,
CONFIG.GSM
AUTOEXEC.GSM
These sample files contain the requirements for the files, CONFIG.SYS and AUTOEX-
EC.BAT, located in the root directory.
1. To set up your PC so the GSM software will run, you must ensure that your
CONFIG.SYS file and AUTOEXEC.BAT file contain certain commands. The
commands needed have been included in the sample files. You may enter these
commands individually into your existing CONFIG.SYS and AUTOEXEC.BAT files
using an editor, or you may use DOS commands to copy the .GSM files.
CONFIG.GSM
FILES = 20
BUFFERS = 48
AUTOEXEC.GSM
SET GSMCFG=C:\GSM\CFILES
(The statement above defines the environment variable GSMCFG. There must be no spaces
on either side of the “=” sign.)
2. If installing the GSM software on a PC with a monochrome monitor, add the
following command to the AUTOEXEC.BAT file:
MODE CO80
3. Restart the PC so that the modifications to the AUTOEXEC.BAT and CONFIG.SYS
will take effect.
Network GSM Operation (or Both Local and Network)
For network operation, the GSM uses an NDIS-compliant PC network card for connec-
tion to the 802.3 network. NDIS-related files will be installed in a C:\GEFNDIS directory
created by the install program. NDIS (Network Driver Interface Specification) defines
the interconnection between a PC network card and the PC application software (GSM
in this case).
3
3-9
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
During GSM installation for network operation, sample DOS system configuration files
will be created in the GSM directory.
These files are,
CONFIG.GSM
AUTOEXEC.GSM
PROTOCOL.GSM
After installing the software, these files will contain the requirements for the DOS sys-
tem files, CONFIG.SYS and AUTOEXEC.BAT, located in the root directory and the PRO-
TOCOL.INI file located in the GEFNDIS directory. When the software installation is
complete, be sure to look in the .GSM sample files to see the requirements to run the
GSM software. Then, refer to the appropriate sub-section below for setting-up the DOS
system files.
Checking for Existing NDIS Applications on Your PC
Before you setup your DOS system files for network operation, you must first determine
whether another NDIS network application has already been installed on your comput-
er. To do this, check your CONFIG.SYS file for a PROTMAN.xxx device definition. If
this definition is in CONFIG.SYS, then a network application does already exist. In this
case, skip the section below and refer to the section, “Adding the GSM When an NDIS
Application Already Exists”. If you do not find a PROTMAN.xxx device definition in
your CONFIG.SYS file, follow just the instructions immediately below.
When the GSM is the Only NDIS Application on the PC
1. To set up your DOS system files so the GSM software will run, you must ensure that
your CONFIG.SYS file and AUTOEXEC.BAT file contain certain commands. Sample
files, showing the commands needed have been created for you during the
installation procedure. These sample files are named CONFIG.GSM and
AUTOEXEC.GSM and are located in the GSM directory. Sample contents are shown
in Appendix D. Note that the content is different for different PC network cards.
Please enter these commands individually into your existing CONFIG.SYS and
AUTOEXEC.BAT files using an editor.
If installing the GSM software on a PC with a monochrome monitor, add the
following command to the AUTOEXEC.BAT file:
MODE CO80
2. When you selected the PC network card during the GSM installation, the file,
PROTOCOL.GSM, was created. This file contains default information about the
communications driver of the PC network card. If you used default hardware
settings on your PC network card, you will not have to edit this file. Just copy it to
C:\GEFNDIS\PROTOCOL.INI. Otherwise, you must edit any non-default
information into the PROTOCOL.GSM and then copy it into
C:\GEFNDIS\PROTOCOL.INI.
3. Restart the PC so that the modifications to the AUTOEXEC.BAT, CONFIG.SYS, and
PROTOCOL.INI files will be used.
3
3-10 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
When an NDIS Application Already Exists
To set DOS system files when an NDIS network application already exists, you need to
understand more about how an NDIS application is setup. The following files must be
installed for an NDIS application.
PROTMAN.xxx NDIS Protocol Manager Driver. Extension varies. GE Fanuc
uses PROTMAN.DOS
(Network Card Driver) Provided by PC network card manufacturer. Name varies.
PROTOCOL.INI File listing each driver and operating parameters for each.
For GE Fanuc applications, the LLC driver, GEFNDIS.DOS, must also be installed. For
the GSM, all these files, and some others, are located in the GEFNDIS directory. But, if
an NDIS application has been installed previously, other versions of the files described
above, except for GEFNDIS.DOS, will already have been placed in another location.
The steps below will explain what to do with these NDIS files to ensure proper network
GSM operation.
1. To set up your PC so the GSM software and another NDIS network application can
both run, you must ensure that your CONFIG.SYS file and AUTOEXEC.BAT file
contain certain commands. Sample files showing the commands needed when the
GSM is the only application have been created for you during the installation
procedure. These sample files are named CONFIG.GSM and AUTOEXEC.GSM and
are located in the GSM directory. Sample contents are shown in Appendix D. Note
that the content is different for different PC network cards.
Since you are adding the GSM when a Network application already exists, some of
these commands may already exist, so you will not need to add all of these com-
mands. Edit your CONFIG.SYS and AUTOEXEC.BAT as explained below.
2. CONFIG.SYS Include all entries from CONFIG.GSM except the following command.
device=\gefndis\protman.dos /i:\gefndis
The CONFIG.SYS file will already have a valid Protocol Manager (protman.xxx) de-
vice definition from the existing network application, and need not be changed.
This file will also already have one or more PC network card device definitions from
the existing network application. If a valid definition exists for the PC network card
selected for the Network GSM, that definition need not be changed.
3. AUTOEXEC.BAT Include the SET GSMCFG command in this file, but not the
NETBIND command:
set cfiles = C:\GSM\CFILES (assuming default directory)
rem Bind NDIS drivers
rem \gefndis\netbind
The NETBIND command is a call to an NDIS driver binding utility. Since an NDIS ap-
plication already exists, that application must have a call which does the same thing
although it may not be obvious by looking at AUTOEXEC.BAT. When the PC is
started, binding must occur only once.
If installing the GSM software on a PC with a monochrome monitor, add the
following command to the AUTOEXEC.BAT file:
MODE CO80
3
3-11
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
4. PROTOCOL.INI Do not copy PROTOCOL.GSM to PROTOCOL.INI; the existing
network application will already have a PROTOCOL.INI file, and you would
destroy its contents.
The PROTOCOL.GSM file created during GSM installation contains a separate sec-
tion for defining the operating parameters of each NDIS device: the Protocol Manag-
er driver [PROTMGR], the GSM application driver [GEFNDIS], and all network
card drivers [(name varies)].
The location of the existing PROTOCOL.INI file is specified by the “/i” parameter in
the Protocol Manager (protman.xxx) device specification in the CONFIG.SYS file.
Make sure the network card driver parameters match the settings for your network
card. Refer to Table 3-2 for default settings.
The sample PROTOCOL.GSM file shown below is created if you selected the 3Com
EtherlinkII network card during software installation.
[protocol manager]
DRIVERNAME = PROTMAN$
[GEFNDIS]
DRIVERNAME = GEFNDIS$
BINDINGS = ETHERLINKII
MAX_RX_SIZE = 560
NUM_RX_BUFS = 8
; Caution: Interrupt conflicts may arise when using default hardware
; configurations for many Ethernet Adapters. For example,
; interrupt IRQ3 is commonly used for the COM2 serial port
; and most Ethernet adapters.
;
; The following information must match the hardware configuration
; of the Ethernet Adapter as installed on your computer. Please
; modify this information as necessary.
[ETHERLINKII]
DRIVERNAME = ELNKII$
DMACHANNEL = 1
INTERRUPT = 3
IOADDRESS = 0x300
MAXTRANSMITS = 8
You must add the device definition sections for only the [GEFNDIS] device and any new net-
work card [name varies] device from the PROTOCOL.GSM file into your existing PROTO-
COL.INI file.
5. Restart the PC so that the modifications to the AUTOEXEC.BAT, CONFIG.SYS, and
PROTOCOL.INI files will be used.
3
3-12 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Unusual Procedures
Updating or Adding to Existing GSM Software
Whenever you purchase the TCP/IP Ethernet Software, whether for the first time or as
an update, you receive all three parts: the Configuration Editor, the Communications
Software, and the GSM Software.
Normally, you will install all three parts of this software when you purchase it the first
time. If you receive an update, or are adding a new GEnet product, you may install all
or part of this software as appropriate. To install a specific part, follow the instructions
below.
1. To install only the LAN Interface Configuration Editor, type:
C:\GSM> a:install c
2. To install only the LAN Interface Communications Software, type:
C:\GSM> a:install x
3. To install only the GSM Software, type:
C:\GSM> a:install g
4. To install all 3 components, type:
C:\GSM> a:install
Changing the PC Network Card
If you change the PC network card type for any reason, follow the instructions below.
1. Power down the PC. Remove the existing PC network card. Follow the
manufacturer’s instructions to install the new PC network card.
2. Power up the PC. Change directory to the GSM directory.
C:\> cd\gsm
3. Run the LANIFSET utility.
C:\GSM> lanifset
4. This utility accesses the same menu as found in step 7 of the section, “Installing the
GEnet System Manager (GSM) Software”. Complete the remaining steps of that
section. This section describes the hardware requirements for running the GEnet
System Manager (GSM) software, and tells you how to install the GSM on the hard
disk of your personal computer.
3
3-13
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Starting-Up the GSM
To start-up the GSM software on the PC, follow the steps listed below:
1. Set the default directory to the GSM directory, and then type:
C:\GSM> gsm
2. Proceed past the copyright notice by pressing any key. The GSM will then prompt
you for the main menu password. The default password is “gsm” (lower case).
After the correct password has been entered, the GSM will then display the main
menu.
Note
If an error occurs in the Data Link software or hardware when starting
up the GSM configured for network operation, an error code is displayed
on the screen. In this case, carefully review your installation steps again.
Appendix E lists the possible error codes and descriptions.
Figure 3-2. GSM Main Menu
The GSM Main Menu lists the functions available in the GSM software. The functions
are ordered generally by their frequency of use with the most used function listed first.
Use the Arrow keys to highlight the desired function and press Enter to select. The func-
tions are summarized here, and then described in more detail later in this chapter.
Download communications software and configuration information to the LAN
Interface.
Access Station Manager allows the PC to run in a terminal mode of operation for
access to the Station Manager residing on a LAN Interface.
3
3-14 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Configure a Station provides the means for setting the various parameters of the
LAN Interface. The Configuration Editor is a menu-driven software package that is
called from the GSM main menu. There is a unique Configuration Editor for each
type of LAN Interface. For example, there are different Configuration Editors for
PLCs and CNCs. The Configuration Editor is used to examine and modify the
configuration parameters for a station. These configuration parameters are stored in
files on the PC hard disk and subsequently downloaded to the LAN Interface.
Configure Network-wide Parameters allows a set of system-wide parameters to be set
(such as the GSM Loader Multicast Address).
List All Stations displays a list of all LAN interfaces known to this GSM.
List all Configured Applications provides a listing of all Applications that have previously
been configured under this GSM. (Not used for the TCP/IP Ethernet Interface.)
Setup GSM provides for certain settings affecting the operation of the GSM (such as
local or network attachment).
The remainder of this chapter discusses various sub-menus used to configure a LAN In-
terface for a basic network.
Working Your Way through the GSM Menus
The GSM is a menu-driven software package that is comprised of a single main menu
and a number of sub-menus. Using the PC keyboard, you can move easily through the
menus. The GSM uses the PC screen to display its information. Certain areas of the
screen are reserved for error, warning, or help messages, while the center is typically
used to display the menus.
The GSM uses monitor display lines 1 through 25, with line 1 at the top. The lines dis-
play the following type of information:
Line 1: displays error messages. For example, if you enter an invalid character in a
field, or if the field value is out of range, an error message is displayed on line 1
to indicate the nature of the problem.
Lines 2-22: displays the current GSM menu and its related set of fields.
Line 23: displays a help line for the current field that is being examined or modi-
fied. This line gives a description of the field, along with the field value ranges,
and the field’s default value.
Line 24: provides instructions for using the screen in general.
Line 25: displays important function keys for the current menu. Always present
are the keys: Alt-K for Key help and Alt-H for Procedure help.
When a sub-menu is displayed, the parent menu(s) are overlaid by the sub menu. This
gives a visual indication of where you are located in the GSM menu hierarchy.
Fields on the GSM screen have a field name and a field value. A sample field name is
FIELD_1_1. Field entries which are marked by reverse-video are input/display fields.
You may modify the data in these fields. A field may require the entry of an alphanu-
meric, hexadecimal, or decimal value. Fields that display an “*” require you to press the
Tab key to cycle through the possible selections.
For systems which have color graphics hardware, the GSM menus are displayed in color.
Selection menus (like the main menu) are displayed as WHITE text on a RED back-
ground. Menus with data input/display fields are displayed as WHITE text on a BLUE
background.
3
3-15
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
GSM Keyboard Functions
The functions of the GSM keys are shown in the table below. In each screen, pressing
the Esc key will return you to the previous screen without saving changes.
Note
If you change the value of a field or fields you must press Alt-U to save
the changes. Pressing Alt-U after a field change will also cause you to
return to the previous screen.
If you press Esc from a screen in which you have made field changes,
those changes will be lost and you will return to the previous screen.
On all screens, pressing Alt-K will display a table describing the special keys used with
the GSM. Pressing Alt-H displays a help screen (or a series of help screens) describing
how to use the screen that is currently displayed.
Table 3-3. GSM Keyboard Functions (Alt-K)
GSM Keyboard
Keys Function
Esc (or F1) Return to previous menu.
Enter Accept field contents, move to next field.
Backspace Delete character to left of cursor.
Del (Delete) Delete character.
Alt-A Abort procedure.
Alt-C Clear field contents.
Alt-D (or F3) Delete entry.
Alt-E Enter Selected Configuration Editor from Configure a Station screen.
Alt-F If in Station Manager Access, enables logging to a file.
Alt-H Display procedure help screen.
Alt-K Display key help.
Alt-L Display list of stations for selection.
Alt-P Create printable file of station’s configuration. If the GSM is in Station
Manager Access and you have enabled Station Manager logging to a
file (Alt–F), Alt–P will close the file.
Alt-U (or F2) Save current menu data, return to previous menu.
Alt-V View contents of table entry.
Alt-S Search for specified table entry.
Tab (or F9) Cycle forward through field entries.
Shift-Tab (or F10) Cycle backward through field entries.
Ins Character insert or replace mode.
↑ (Up Arrow) Move to previous field.
↓ (Down Arrow) Move to next field.
→Move right one character in field.
←Move left one character in field.
PgUp (Page Up) Display previous page, or previous entry.
PgDn (Page Down) Display next page, or next entry.
Home Display first page, or first entry.
End Display last page, or last entry.
3
3-16 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
GSM Menu Structure
The menu structure of the of the GEnet System Manager software is shown below.
**
*
These parameters are not normally changed by the user.
**
Not applicable to the TCP/IP Ethernet Interface.
Download Station
Access Station Manager
Configure a Station
Configure Network-Wide Parameters
List All Stations
List All Configured Applications
Setup GSM
Exit to DOS
GSM Main Menu
Configure a Station Menu
Press Alt-E
System Network Parameters Menu
Load Group Parameters
802.4 Network Parameters
a45403
Data Link Parameters
System Parameters
**
Advanced Parameters Menu
Series 90-70 TCP/IP Station
Configuration Editor Menu
TCP/IP Parameters
Advanced Parameters
Print Configuration File
Change Password
Set Download Mode
Set Station Manager Mode
GSM Setup Menu
NOTE:
*
Figure 3-3. GSM Menu Structure
3
3-17
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Section 2: Configuring a Station
Aside from possibly using the GSM to access the Station Manager for field network test-
ing, the first major GSM operation you will perform in bringing-up your network is con-
figuring a station.
Within the GSM there are various configuration screens. There are screens for configur-
ing stations, for tuning a network for ultimate performance, and for routing communica-
tions through network routers.
Information Needed to Configure a TCP/IP Ethernet Interface
Station
The most important information you will need to know before configuring a station is:
Station Name
Station Type
Station MAC Address (the default MAC address can be found on the label on the
faceplate of the TCP/IP Ethernet Interface).
IP Address
If your network includes a gateway, you will also need the following information.
Subnet Mask
Gateway Address
Configure a Station Screen
A number of different LAN Interface products may be present on the LAN. Each LAN
Interface must be configured using that product’s Configuration Editor before it can be
downloaded. Before entering the Configuration Editor you must first access the Config-
ure a Station Screen from the GSM Main Menu.
The Configure a Station Screen allows you to perform 3 main functions.
Create a Station Configuration File
Select an Existing Station Configuration File
Delete a Station Configuration File
The Configure a Station Screen, shown below, is used to specify the Station Type and to
assign a logical name (STATION_NAME) to the station. The STATION_NAME corre-
sponds to the unique MAC_ADDRESS which physically identifies the station on the net-
work. It is also used to modify certain configuration parameters for a station.
3
3-18 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
When the Edit configuration keys (Alt-E) are pressed in this menu, the GSM calls the
Configuration Editor required for that specific Station Type.
Figure 3-4. Configure a Station Screen
Creating a Station Configuration File
1. Type in or select desired values for the STATION_NAME, STATION_TYPE fields, etc.
See the description of screen fields below.
2. Press Alt-E to enter the Configuration Editor.
Field Definitions for the Configure a Station Screen
STATION_NAME - A name (1 to 20 characters) which is used to uniquely identify the
station on the GSM hard disk.
STATION_TYPE - The type of device containing the LAN Interface.
The value for this field is selected from a set of choices; press the Tab key to view
the choices. The available choices depend on what products have been installed
into the GSM system.
To configure a TCP/IP Ethernet station, press the Tab key until SERIES 90-70
appears.
LOAD_TYPE - The type of station being configured. For the TCP/IP Ethernet station
press the Tab key until TCP appears.
MAC_ADDRESS - The 12 hex digit MAC address of the station being configured. This
will be either the Default MAC Address as delivered with your board, or a Locally
Administered MAC Address in the case where you have specified the MAC address
yourself. See the description on the structure of the MAC Address later in this sec-
tion and in Appendix G.
3
3-19
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Each LAN Interface is delivered with a Default Station Address already set. There
are several ways to determine this value:
Look at the label located on the LAN Interface
Use the Station Manager NODE command.
Press the Restart button to see the MAC address appear on the Local Station
Manager terminal screen (be sure the Station Manager terminal is connected to
the Interface).
The Default Station (MAC) Address is a globally administered address; the global
administration process assures that each default MAC address is unique. Your orga-
nization may have its own scheme of how addresses are administered. In this case
you will not use the default address, but will assign a different address from a set of
numbers established by your address administrator.
LOAD_GROUP - The number of the selected download group for the station. The Load
Group selects which multicast address is used when loading the station. The multi-
cast addresses and slot times are assigned to the Load Groups via the System Net-
work Parameters menu. Value may be 0 to 4 (default is 0).
Note
The LOAD_GROUP is only needed when more than one network GSM
is in use. Otherwise you can let this field stay at its default value.
COMMENTS - This field is optional, but may be used to insert a comment line up to 40
characters long for the station being configured. These comments will be displayed
on the List All Stations Screen.
Note
To keep a record of IP addresses you can add the IP address in the
COMMENTS field for each station .
3
3-20 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Selecting a Station Configuration File
Select a station by filling in the STATION_NAME field in one of three ways.
Type in the Station Name, or
Type in a << MAC Address>> specified as exactly 12 hexadecimal digits within a
double set of brackets (for example, <<08001901001d>>). The GSM will convert
the MAC address into the corresponding station name, or
Select a station from a list of stations. Press Alt-L for the list. From this list, you select
the desired station, which is then displayed on the Configure a Station Menu.
The Up Arrow, Down Arrow, Pg Up, Pg Dn, Home, and End keys may be used to move
within the list. You may also begin a search by pressing Alt-S. When the desired station
is displayed at the top of the list, press the Enter key to select that station. The selected
station name is then displayed on the Configure a Station Screen.
After selecting a station, you may press Alt-E to enter the Configuration Editor.
Deleting a Station Configuration File
1. Select the station you want to delete. (See description above on Selecting a Station.)
2. Press Alt-D.
Structure of the MAC Address
The MAC Address is a 12-digit hexadecimal number that identifies the station on the
physical network. This 12-digit number is organized as 6 bytes, each byte is represented
by a pair of hexadecimal digits. A typical default MAC Address is shown below.
Byte 1 2 3 4 5 6
Hex No. 0_8 0_0 1_9 0_0 5_3 1_2
For more information on assigning MAC Addresses, refer to Appendix G.
3
3-21
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Configuration Editor Menu for Series 90-70 PLCs
Once a station has been defined in the Configure a Station Menu, you may proceed to
the Configuration Editor Menu (by pressing Alt-E) to define that station’s communica-
tion parameters in more detail. Or, you can return to this menu at any time in the future
to examine or modify these parameters. The screen below is the Configuration Editor
for the STATION_TYPE, SERIES_90-70 and LOAD_TYPE, TCP.
Figure 3-5. Configuration Editor Menu
From this menu you can access the screens that allow you to enter the IP address, and if
needed, the Subnet Mask and the Gateway address.
Saving Changes Before Exiting the Configuration Editor Main Menu
The Configuration Editor Main Menu is the first screen displayed when entering the Con-
figuration Editor and is the last displayed before exiting the Configuration Editor.
Typically, after you have entered the Configuration Editor, you will go into sub-screens
and enter or change values for the parameters included in them. After you have made
changes in a sub-screen, you must press Alt-U to save them temporarily while you go to
other sub-screens.
After you have finished making changes in the sub-screens and back-out to the Configu-
ration Editor Main Menu, you must press Alt-U again to permanently save the changes
to disk. If you press Esc to exit the Configuration Editor Main Menu, a prompt will appear
requesting you to confirm the exit without saving to disk; if you confirm exit, your
changes are discarded.
Note
The first time you create a station configuration, you must enter Alt-U to
save the file even if you make no changes to default configuration
parameters.
3
3-22 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
TCP/IP Parameters Screen
The TCP/IP Parameters screen is used to set the IP_ADDRESS of the station and if your net-
work includes a gateway, the IP_NETWORK_MASK and the DEFAULT_GATEWAY address.
Figure 3-6. TCP/IP Parameters Screen
The values for these parameters (IP_ADDRESS, IP_NETWORK_MASK, and DE-
FAULT_GATEWAY) should be assigned by the person in charge of the network (the net-
work administrator). TCP/IP network administrators are familiar with these parameters
and they are not described in this manual. It is important that these parameters are cor-
rect, otherwise the Ethernet Interface may be unable to communicate on the network
and/or network operation may be corrupted.
However, if you have a simple isolated network with no gateways, you can use the fol-
lowing range of values for the assignment of local IP Addresses:
IP Address Address as Configured on the Screen
3.0.0.1 003 000 000 001
3.0.0.2 003 000 000 002
3.0.0.3 003 000 000 003
... ...
3.0.0.255 003 000 000 255
Note
If the isolated network is ever connected to another network, the IP
addresses 3.0.0.1 through 3.0.0.255 must not be used. The IP addresses
must be assigned so that they are compatible with the connected
network. Refer to Appendix G for more information on IP addressing.
3
3-23
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Determining If an IP Address Has Already Been Used
It is very important not to duplicate IP addresses. To determine if you have configured your
Series 90-70 TCP/IP-Ethernet station with the same IP address as another station,
disconnect the station in question from the LAN, then try a PING command to that IP
address from another station. If you get an answer to the PING, then the chosen IP
address is already in use.
Precedence of TCP/IP Parameter Sources
The Ethernet Interface receives TCP/IP parameters from the GEnet System Manager
(GSM) each time the board is downloaded from the GSM. It is also possible that a
Logicmaster 90 system which uses TCP/IP configuration mode (“Config Mode”) will be
able to specify the same TCP/IP parameters to the PLC CPU, which passes them on to
the Ethernet Interface through Soft Switches. With two sources for the same
information, it is important to understand which set of parameters apply in any given
situation.
As a general rule, the TCP/IP parameters for the Series 90-70 TCP/IP Ethernet Interface
will be applied in the following prcedence order:
1. If Logicmaster 90 configures the Ethernet Interface in TCP/IP Config Mode and this
configuration information is passed from the PLC CPU through Soft Switches, the
Logicmaster parameters will be used.
2. If Logicmaster configures the Ethernet Interface in MMS-Ethernet Config Mode and
this configuration information is passed from the PLC CPU through Soft Switches,
the GSM paramters will be used.
3. If the Ethernet Interface is in an unconfigured slot (no configuration in the PLC
CPU, or Logicmaster configuration in the PLC CPU not showing an Ethernet
Interface) and therefore not receiving soft switches, the Ethernet Interface will use
the last set of TCP/IP parameters it received. This is true whether they originally
came from Logicmaster or GSM. This will remain true through power cycles and
Ethernet Interface restarts until either the Ethernet Interface receives Soft Switches
from the PLC or until the Ethernet Interface is downloaded from the GSM.
4. If the Ethernet Interface is in an unconfigured slot and is downloaded from the
GSM, the Ethernet Interface will assume MMS-Ethernet Config Mode and use the
parameters from the GSM.
Note
For Logicmaster 90 to be able to use TCP/IP Config Mode, the PLC CPU
must have firmware version 5.03 or later, and the Ethernet Interface
firmware and software must be version 2.00 or later.
3
3-24 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Advanced Parameters Menu
The Advanced Parameters menu (shown below) provides access to the Data Link Param-
eters, the System Parameters, and the Station Manager password. These parameters
should only be changed by authorized personnel.
Figure 3-7. Advanced Parameters Menu
3
3-25
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Data Link Parameters Screen
The Data Link Parameters Screen allows you to modify the Data Link Layer communica-
tions parameters. In most cases the values of these parameters will remain the default
values. The Data Link Parameters menu is shown below.
Figure 3-8. Data Link Parameters Screen
The Data Link Parameters are defined as follows:
TX_RING_LEN - The maximum number of frames which can be queued for transmis-
sion on the network. Valid values are 8, 16, 32, 64, and 128 frames. Defaults to 8
frames. Value selected by Tab or Shift-Tab keys. Corresponds to Station Manager
Parameter ltxringlen.
RX_RING_LEN - The maximum number of incoming frames received by this station
which can be queued for processing. Valid values are 8, 16, 32, 64, and 128 frames.
Defaults to 64 frames. Value selected by Tab or Shift-Tab keys. Corresponds to Sta-
tion Manager Parameter lrxringlen.
LLC_MAX_BUF - The maximum data size of Link Layer receive buffers. This the largest
possible receive frame for the Link Layer. Valid range of 128 to 1497 bytes. Defaults
to 1497 bytes. Should be at least 70 less than the Maximum Buffer Size (see the Sys-
temParameters Menu). Corresponds to Station Manager Parameter lmaxdb.
DISAB_TX_RTRY - Prevents the normal automatic TX retries when a frame collision oc-
curs during transmission. Valid values are “Y” and “N”. “Y” specifies that TX retries
are disabled. “N” specifies that each TX frame will be retried up to 16 times. Defaults
to “N”. Corresponds to Station Manager Parameter ldrtry.
3
3-26 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Up to 8 Receive data Group Addresses may be programmed for frame reception.
Multicast receive frames are accepted if they match one of these Group Addresses.
ADDRESS - One of 8 Group Addresses used for reception of multicast frames. A 6-byte
hexadecimal byte string which represents a valid multicast address. Individual sta-
tion addresses, or the broadcast address <<FFFFFFFFFFFF>> are not permitted.
Entry 0 defaults to <<09002B000004>>,which is the All-ES MAC address; all other
entries default to zero<<000000000000>> to indicate that the entry is not used.
Corresponds to Station Manager Parameter lgrpmsk0 - lgrpmsk7.
3
3-27
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
System Parameters Screen
The System Parameters Screen selection is used to modify parameters which determine
how the Ethernet Interface allocates its available buffer memory. This screen is also used
to modify Station Manager parameters.
The System Parameters Screen is shown below:
Figure 3-9. System Parameters Screen
Memory Pool Allocation Parameters
The Memory Pool Allocation fields define the buffer pools used by the Ethernet Inter-
face. The Ethernet Interface RAM memory available after all the Ethernet Interface
executive software and configuration information has been loaded is broken into four
fixed size pools.
The MEMORY ALLOCATION parameter specifies the percentage of available memory
to be allocated to each pool. For example, a value of 10 in this field would assign 10 per-
cent of available memory to be allocated to this pool. The total of the MEMORY AL-
LOCATION for all buffer pools cannot exceed 100 percent. If the total is less than 100
percent, some of the available memory will not be used.
Buffers are used to hold messages which are sent or received on the network and to save
state information regarding the communications software. IN ALL CASES, there must
be buffers available and of sufficient size to contain the messages sent or received.
Note
You should not change Memory Pool Allocation parameters without first
consulting GE Fanuc Automation
The Buffer Size of the Buffer Pools must be specified in increasing order as follows:
3
3-28 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Buffer Size Pool 1 < Buffer Size Pool2 < Buffer Size Pool3 < Buffer Size Pool 4
The ranges for the Buffer Pool Parameter values are:
BUFFER_POOL_1 - Buffer Pool 1 memory allocation
BUFFER SIZE - Valid range of 1 to 1024 bytes. Defaults to 44. Corresponds to
Station Manager Parameter bbuff1.
MEMORY ALLOCATION - Valid range of 1 to 97 percent. Defaults to 11 percent.
Corresponds to Station Manager Parameter balloc1.
BUFFER_POOL_2 - Buffer Pool 2 memory allocation
BUFFER SIZE - Valid range of 1 to 2048 bytes. Defaults to 380. Corresponds to
Station Manager Parameter bbuff2.
MEMORY ALLOCATION - Valid range of 1 to 97 percent. Defaults to 12 percent.
Corresponds to Station Manager Parameter balloc2
BUFFER_POOL_3 - Buffer Pool 3 memory allocation
BUFFER SIZE - Valid range of 1 to 4096 bytes. Defaults to 1580. Corresponds to
Station Manager Parameter bbuff3.
MEMORY ALLOCATION - Valid range of 1 to 97 percent. Defaults to 43 percent.
Corresponds to Station Manager Parameter balloc3
BUFFER_POOL_4 - Buffer Pool 4 memory allocation
BUFFER SIZE - Valid range of 1 to 8192 bytes. Defaults to 2140. Corresponds to
Station Manager Parameter bbuff4.
MEMORY ALLOCATION - Valid range of 1 to 97 percent. Defaults to 34 percent.
Corresponds to Station Manager Parameter balloc4.
The Station Manager Parameters are as follows:
PASSWORD - The password that is used to modify the secure mode of the Station Man-
ager. Case sensitive. Consists of up to 8 characters. Defaults to “system” (lower
case).
LSAP - The Station Manager Link Service Access Point (LSAP) to be used to send and
receive Station Manager REMote commands and responses. Defaults to E8 (hexade-
cimal). Corresponds to Station Manager Parameter bremlsap.
PRIORITY - The Link Layer priority used to send Station Manager REMote commands
and responses. Valid range of 0 to 7. Defaults to 0. Corresponds to Station Manager
Parameter brempri.
3
3-29
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Section 3: Downloading a Station
This section describes only the activities at the GSM associated with downloading a sta-
tion. For a complete procedure on downloading communication software and configu-
ration information to a station, see Chapter 2, Procedure 4.
Download Station Screen
The Download Station screen provides a means to download LAN Interfaces via local
serial port or the network (depending on selection in the System Network Parameters
Menu). After a configuration file has been created and saved, the communication soft-
ware and configuration file must be loaded into the desired station. The GSM Down-
loader Screen is used to load the station.
Figure 3-10. Download Station Screen
Downloading Locally (Over the Serial Port)
If you have selected Local Download Mode in the GSM Setup menu, you will be
prompted for the name of the station to be downloaded. This is the same 20 character
name you used when you configured the station from the Configure a Station menu.
Note that the station must be previously configured. As an alternate method of identify-
ing the station to be downloaded, you may enter its MAC address, or you may select the
station name from a list by entering Alt-L.
3
3-30 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
After you enter the STATION_NAME, the GSM will download the communications soft-
ware and configuration file over the serial link. It takes 5 minutes or more to serially
load a station, but it is necessary only to perform the procedure when you are perform-
ing a software or configuration upgrade to your LAN Interface.
There are 3 files that are downloaded to the LAN Interface. While the station is being
downloaded, the name of the current file being loaded is displayed along with the file
block count. The download may be aborted by pressing Alt-A key or Esc key. Once
aborted, the download may not be resumed, but must be restarted from the beginning.
If an error occurs during the download process, an error message is displayed on the
screen to indicate the nature of the error.
Once the download is complete, a message is displayed on the screen indicating that the
download was successful. Control is then transferred automatically to the Local Station
Manager Terminal screen so you may view the LAN Interface initialization messages.
Downloading Over the Network
The Network Downloader uses a special download protocol to transfer information to
the GEnet LAN Interfaces on the network that require a download. The download pro-
tocol is described in this section.
1. The Network Downloader transmits a download multicast message once per
second, when idle, to a specified multicast address.
2. The LAN Interface requiring a download receives the download multicast message
and sends a “Request for Load” message to the Network Downloader. Download
multicast addresses are defined in the GSM System Network Parameters menu. A
Load Group number is assigned to each multicast address. Each LAN Interface must
define a Load Group number so it obtains its download using the correct multicast
address.
Notes
The Network Downloader will support up to five different Load Groups
each with a unique load multicast address and IEEE 802.4 slot time. This
feature is not applicable to Ethernet (IEEE 802.3) networks and so the
default Load Group 0 is sufficient.
3. When the Network Downloader receives a “Request for Load” message from a LAN
Interface, it loads the necessary files into the LAN Interface across the LAN.
While the station is being downloaded, the name of the current file being loaded is dis-
played along with the file block count. If an error occurs during the download process,
an error message is displayed on the screen to indicate the nature of the error.
If an error occurs in the Data Link software or hardware, an error code is displayed on
the screen. Appendix E lists the error codes that can be displayed, along with their de-
scriptions.
When the download is complete, a message is displayed on the screen indicating that
the download was successful.
3
3-31
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
The Downloader transfers three files to the LAN Interface (in this order):
*.XFM - LAN Interface communications software.
Cxxxxxx.xxx - LAN Interface configuration file.
GO - Commands the LAN Interface to start execution of loaded software.
Before the LAN Interface is downloaded, the GSM Downloader will check the GSM Sys-
tem Files to see if the configuration file needs to be updated. The System Files consist of
the System Slot Time and the Application DIBs. If any of these files have been updated
more recently than the configuration file, the Downloader displays the following mes-
sage.
System files integrated for Station: Station Name
Note
The DOS time and date on the PC must be correct whenever the GSM is
run, as the GSM uses the date and time associated with each file to
determine if configuration files need to be updated.
The Network Downloader can also be entered directly from the DOS prompt by typing:
C:\GSM> gsm dnld
This can be used to invoke the Network Downloader from a batch file. This can be used
to automatically run the Network Downloader after a power outage of the PC.
The Alt-F and Alt-P keys are used to enable and disable the logging of downloader activ-
ity to a user-specified file. The log file is automatically closed when returning to the
GSM main menu.
The Esc key is used to exit the Network Downloader and to return to the GSM main menu.
Notes
1. A LAN Interface MUST be configured on the GSM before it can be
downloaded.
2. The LAN Interface Soft Switch, Network Load Address (LDMAC),
must match one of the LOAD_MULTICAST_ADDR parameters on
the GSM in order for a Network download to take place for the
LAN Interface.
3. The MAC Address of the Station selected MUST match the LAN
Interface MAC Address Soft Switch parameter (MAC) in order for
the LAN Interface to be fully operational after loading.
3
3-32 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 4: Accessing the Station Manager
This section describes how to access the Station Manager software that resides on the
Ethernet Interface.
Access Station Manager Screen
The Access Station Manager Screen is used to access the Station Manager on the Ether-
net Interface. This access will occur over either the serial port, or the network (depend-
ing on the selection in the System Network Parameters Menu). If you are using network
access, you will be prompted for the name of the station you wish to access.
Figure 3-11. Access Station Manager Screen
Once you are in the Access Station Manager screen, the PC acts like a dumb terminal
connected to the Ethernet Interface. The GSM sets up the screen to display the interac-
tions with the local Ethernet Interface Station Manager.
The logging of Station Management activity can be started or stopped from this menu.
To request logging to start, press Alt-F. You will be prompted for the log file name. The
log file is automatically closed when leaving this menu, or when you press Alt-P.
3
3-33
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Section 5: Using the GSM Support Functions
This section describes the GSM support functions. The GSM Menu topics discussed in
this section are:
List All Stations
List all Configured Applications
Setup GSM
Exit to DOS
List All Stations Screen
The List All Stations screen displays a list of all of stations that are configured in the
GSM directory on the hard disk. A typical List All Stations screen is shown below.
Figure 3-12. List All Stations Screen
This screen displays the following information about each station:
Station Name
Station Type
Load Type
Station MAC Address
Comments
Use the Up Arrow, Down Arrow, PgUp, PgDn, Home, and End keys to examine the list
of configured stations. The details about a specific station can be examined by pressing
the Alt-V key. When you press the Alt-V key, you are prompted for the name of the sta-
tion to examine. If you enter a blank field, the top item in the menu is examined.
3
3-34 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
The detailed information about a specific station additionally includes:
Configuration File Name
Date and time Last configured
Date and time Last Downloaded
Station’s Load Group (with values selected by the Load Group)
The Alt-S key is used to search the list of stations for a specified entry. When you press
the Alt-S key, you select the data field and value to seek and select the search direction.
Press the Alt-S key again to initiate the search, or the Esc key to abort the search.
Press the Alt-P key to create a list file, “STANAMES.LIS”, of the configured stations.
Press the Esc key to exit the Show Stations screen and to return to the GSM Main menu.
3
3-35
GFK-1004B Chapter 3 The GEnet System Manager–Station Configuration
Setup GSM Menu
The Setup GSM screen (shown below) includes the following functions.
Change the password that must be entered to access the GSM main menu
Set Download Mode (Local or Network)
Set Station Manager Mode (Local or Network)
Figure 3-13. Setup GSM Menu
Changing the GSM Password Screen
When you select this function, the GSM clears the screen, and prompts for the following
information:
Enter old password:
Enter new password:
Verify new password:
You are given three chances to enter the above information properly. Please note that all
characters which are typed after the password prompt except for the Return key are as-
sumed to be part of the password. Specifically, the delete and backspace characters do
not have their usual meaning and are interpreted simply as password characters. When
this process is completed (successfully or unsuccessfully), control is returned to the GSM
main menu.
Note
The password is case sensitive.
3
3-36 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Set Download Mode Screen
This screen permits you to toggle the download mode between Local and Remote.
To Set the Download Mode:
1. Enter the Set Download Mode Screen.
2. Press Tab to toggle the Mode.
3. Press Alt-U to update.
4. Press Esc to return to the GSM Main Menu.
Set Station Manager Mode Screen
This screen permits you to toggle the Station Manager mode between Local and Remote.
To Set the Station Manager Mode:
1. Enter the Set Station Manager Mode Screen.
2. Press Tab to toggle the Mode.
3. Press Alt-U to update.
4. Press Esc to return to the GSM Main Menu.
Note
You can also toggle the Station Manager Mode by pressing Alt-M from
the GSM Main Menu.
Exit to DOS
When the EXIT TO DOS menu item is selected, the GSM clears the screen, and returns
control to the PC operating system.
4section level 1
figure bi level 1
table_big level 1
4-1
GFK-1004B
Chapter 4Programming Communications Requests
This chapter describes how to program PLC to PLC communications over the Ethernet
Network. Details of the COMMREQ function and the Channel commands are pres-
ented here. The chapter is divided into 5 sections:
Section 1: The Communications Request
Section 2: The COMMREQ Function Block and Command Block
Section 3: Channel Commands
Section 4: Status Data
Section 5: Controlling Communications in the Ladder Program
Note
This chapter applies only to PLCs being used as client PLCs to initiate
TCP/IP communications. No programming is required for server
operation.
4
4-2 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 1: The Communications Request
“Communications Request” is a term used to describe all the user elements required for
correctly initiating Channel Commands from a Series 90 PLC. This section describes the
elements of the Communications Request.
No programming of Communications Requests is required for PLCs acting as servers
which are merely targets of other systems’ requests but do not themselves initiate re-
quests.
Structure of the Communications Request
The Communications Request is made up of the following elements.
The COMMREQ Function Block (ladder instruction)
The COMMREQ Command Block
The Channel Command
Status Data (COMMREQ Status word, LAN Interface Status and Channel Status
bits)
The logic program controlling execution of the COMMREQ Function Block
The figure below illustrates the relationship of these elements:
a44916c
INPUTS
AND
OUTPUTS
FOR COMMREQ
FUNCTION
COMMAND
BLOCK
POINTER
COMMREQ
FUNCTION BLOCK
DETAILS
OF THE
CHANNEL
COMMAND
COMMREQ
COMMAND BLOCK COMMREQ
STATUS WORD
STATUS
CODES
COMMREQ
STATUS
WORD
POINTER
STATUS BITS
LAN INTERFACE STATUS
AND CHANNEL STATUS
BITS
Location in PLC memory spe-
cified when configuring the In-
terface using Logicmaster 90
Configuration Software
INITIATES
COMMREQ
FUNCTION
BLOCK
CONTROL
LOGIC
Figure 4-1. Elements of the Communications Request
4
4-3
GFK-1004B Chapter 4 Programming Communications Requests
COMMREQ Function Block
The COMMREQ Function Block is the ladder instruction that triggers the execution of
the Channel Command. In the COMMREQ Function Block, you specify the rack and
slot location of the Ethernet Interface and a pointer to a location in memory that con-
tains the Command Block. There is also a fault output on the COMMREQ Function
Block that indicates certain programming errors. See Section 2 for details.
COMMREQ Command Block
The COMMREQ Command Block is a structure that contains information about the
Channel Command to be executed. The Command Block consists of two parts:
Common Area - includes a pointer to the COMMREQ Status word (CRS word)
Data Block Area - describes the Channel Command to be executed.
When the COMMREQ function is initiated, the Command Block is transferred to the
Ethernet Interface for action.
See Section 2 for a description of the common area of the Command Block and Section 3
for details on the Data Block area and Channel Commands.
Channel Commands
The Channel Commands are a set of client PLC commands used to communicate with a
server PLC.
Advantages of Channel Commands
The advantage of Channel Commands is their ability to establish a channel to execute
multiple periodic reads or writes with a single initiation of a COMMREQ function. A
Channel Command can also be used to execute a single read or write.
Up to 16 channels (numbered 1-16) can be established by a client PLC. The channel
number is specified in the Command Block for the Channel Command. The channel can
be monitored using the Channel Status bits and the Detailed Channel Status words.
See Section 3 for more information.
4
4-4 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Status Data
There are several types of status available to the client PLC logic program.
LAN Interface Status Bits (LIS Bits): The LIS bits comprise bits 1-16 of an 80-bit status
area.* The location of this 80-bit status area is assigned using the Logicmaster 90
Configuration Package in the “Status Address” field. The LIS bits contain information on
the status of the Local Area Network (LAN) and the Ethernet Interface itself. See Section 4
for more information.
Channel Status Bits: The Channel Status bits comprise bits 17-80 (64-bits) of the status
indication area. The first 32 bits consist of an error bit and a data transfer bit for each of the
16 channels that can be established. The last 32 bits are reserved for future use and set to
zero by the Ethernet Interface. See Section 4 for more information.
COMMREQ Status Word (CRS Word): The 16-bit CRS word will receive the initial status
of the communication request. The location of the CRS word is assigned for each
COMMREQ function in the COMMREQ Command Block. See Section 4 for more
information.
Detailed Channel Status Words (DCS Words): This detailed status data is retrieved for a
particular channel using the Retrieve Detailed Channel Status Command. See Section 3
for information on the command and Section 4 for the contents and format of the
retrieved channel status.
FT Output of the COMMREQ Function Block: This output indicates that the PLC CPU
detected errors in the COMMREQ Function Block and/or Command Block and did not
pass the Command Block to the Ethernet Interface. See Section 4 for details.
The Logic Program Controlling Execution of the COMMREQ Function Block
Care must be taken in developing the logic that controls the execution of the COMMREQ
function. The COMMREQ function must be initiated by a one-shot to prevent the
COMMREQ from being executed repeatedly each CPU scan, as this will overrun the
capability of the Ethernet Interface and possibly require a manual restart. Checking
certain status bits before initiating a COMMREQ function is also important. In particular,
the LAN Interface OK bit should be used as an interlock to prevent execution of the
COMMREQ function when the Ethernet Interface is not operational.
See Section 5 and Appendix D for tips on developing your program.
*This Section assumes you have configured your Ethernet Interface in TCP/IP con-
figuration mode rather than MMS-ETHERNET configuration mode. MMS-ETHER-
NET configuration mode provides only 16 bits of LIS.
4
4-5
GFK-1004B Chapter 4 Programming Communications Requests
Operation of the Communications Request
The figure and text below explains how a Communications Request is executed. The
figure specifically illustrates the operation of an Establish Read Channel Command.
Client
Series 90–70
PLC CPU Backplane
Ethernet
Interface Server
Series 90 PLC
LAN
Power flows to COMMREQ
in ladder program
Command Block sent to
Interface Verify
Command Block
and set up channel
to server PLC
Read Request
Data
Data
Read Request
Data
Data
Client
Data
Data
COMMREQ
Status Word
Return COMMREQ
Status Word (CRSW)
to CPU
.
.
.
.
.
.
Read Request
Data
Data
Data
Pulse Data Transfer bit
Pulse received
Pulse Data Transfer bit
Pulse received
Pulse Data Transfer bit
Pulse received
Data
Domain of a channel
Domain of a TCP connection
Figure 4-2. Operation of the Communications Request for an Establish Read Channel-
Command
1. A Communications Request begins when there is power flow to a COMMREQ func-
tion in the client PLC. At this time, the Command Block data is sent from the PLC
CPU to the Ethernet Interface.
2. For the Establish Read Channel Channel command, the COMMREQ Status word
(CRS word) is returned immediately if the Command Block is invalid. If the syntax is
correct, then the CRS word is returned after the next significant event: upon failure to
establish a channel correctly and in a timely manner or upon the first successful trans-
fer of data.
Once the channel is successfully set up to the server PLC, the Ethernet Interface
performs the periodic reads as specified in the Command Block.
4
4-6 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 2: The COMMREQ Function Block and Command Block
This section describes the programming structures common to all Communications
Requests: the COMMREQ Function Block and the Command Block.
The COMMREQ Function Block
The Communications Request is triggered when the logic program passes power to the
COMMREQ Function Block. For the Series 90-70 PLC, the COMMREQ Function Block
has four inputs and two outputs:
(Enable ) –––––––––––––– COMM
REQ
(Command Block Pointer)
(Rack/Slot Location of
the Ethernet Interface)
(Always zero) 00000000
–
–
–
IN FT
SYSID
TASK
– Function Faulted (logic)
– OK
Each of the inputs and the output are discussed in detail below. It is important to under-
stand that the Command Block pointer points to the location in memory you are using
for the Command Block.
Enable: Control logic for activating the COMMREQ Function Block. See Section 5 and
Appendix D for tips on developing your program.
IN: The location of the Command Block. It may be any valid address within a word-ori-
ented area of memory (%R, %AI, %AQ, %P, or %L).
SYSID: A hexadecimal value that gives the rack (high byte) and slot (low byte) location
of the Ethernet Interface.
Examples:
Rack Slot Hex Word Value
0 4 0004h
3 4 0304h
2 9 0209h
4 2 0402h
Note
This Series 90-70 Ethernet Interface is only supported in the main PLC
rack (rack number 0).
4
4-7
GFK-1004B Chapter 4 Programming Communications Requests
TASK: This must always be set to zero for the Ethernet Interface
Caution
Entering a number other than zero for TASK may cause the Ethernet Interface to
fail.
OK Output: The OK output is set if the PLC CPU was successful in handing off the
COMMREQ to the Ethernet Interface.
FT Output: The FT output is set if the PLC (rather than the Ethernet Interface) detects
that the COMMREQ fails. In this case, the other status indicators are not updated for
this COMMREQ. See Section 3 for more information.
The COMMREQ Command Block
When the COMMREQ function is initiated, the Command Block is sent from the PLC
CPU to the Ethernet Interface. The Command Block contains the details of a Channel
Command to be performed by the Interface.
The address in CPU memory of the Command Block is specified by the IN input of the
COMMREQ Function Block. This address may be in any word-oriented area of memory
(%R, %AI, or %AQ). The Command Block is set up using an appropriate programming
instruction (the BLOCK MOVE Function Block is recommended).
The Command Block has the following structure:
Word 1 Data Block Length (words)
Word 2 WAIT/NOWAIT Flag = 0
Word 3 CRS Word Pointer Memory Type
Word 4 CRS Word Pointer Offset
Word 5 Reserved
Word 6 Reserved
Words 7 up to 31
(decimal) Data Block (Channel Command Details)
When entering information for the Command Block, refer to these definitions:
(Word 1) Data Block Length: This is the length in words of the Data Block portion of the
Command Block (up to 25 words-decimal). The Data Block portion starts at Word 7 of
the Command Block. The length is measured from the beginning of the Data Block at
Word 7, not from the beginning of the Command Block. The correct value for each com-
mand, and the associated length of each command, is specified in Section 3.
(Word 2) WAIT/NOWAIT Flag: This flag must be set to zero for TCP/IP Ethernet Commu-
nications.
4
4-8 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
COMMREQ Status Word: The Ethernet Interface updates the CRS word to show success
or failure of the command. Command words 3 and 4 specify the PLC memory location
of the CRS word.
(Word 3) COMMREQ Status Word Pointer Memory Type: This word specifies the memory
type for the CRS word. The memory types are listed in the table below.
Type Value
(Decimal) Value
(Hex.) Description
%R 8 08h Register memory (word mode)
%AI 10 0Ah Analog input memory (word mode)
%AQ 12 0Ch Analog output memory (word mode)
%I 16
70 10h
46h Discrete input memory (byte mode)
Discrete input memory (bit mode)
%Q 18
72 12h
48h Discrete output memory (byte mode)
Discrete output memory (bit mode)
%T 20
74 14h
4Ah Discrete temporary memory (byte mode)
Discrete temporary memory (bit mode)
%M 22
76 16h
4Ch Discrete momentary internal memory (byte mode)
Discrete momentary internal memory (bit mode)
%G 56
86 38h
56h Discrete global data table (byte mode)
Discrete global data table (bit mode)
(Word 4) COMMREQ Status Word Pointer Offset: This word contains the offset within
the memory type selected. The status word pointer offset is a zero-based number. For ex-
ample, if you want %R1 as the location of the CRS word, you must specify a zero for the
offset. The offset for %R100 would be 99. Note, however, that this is the only zero-
based field in the Channel commands.
For information on the contents of the COMMREQ Status word, see Section 4.
(Word 5): Reserved. Set to zero.
(Word 6): Reserved. Set to zero.
(Words 7 - 31) Data Block: The Data Block defines the Channel command to be per-
formed. For information on how to fill in the Channel command information, see Sec-
tion 3.
4
4-9
GFK-1004B Chapter 4 Programming Communications Requests
Section 3: Channel Commands
This section describes the Channel Commands. A detailed description and example of
each channel command is included. There are five Channel Commands.
1. Establish Read Channel
2. Establish Write Channel
3. Abort Channel
4. Retrieve Detailed Channel Status
5. Assign Channel Status Vector
Establishing a Channel
The Ethernet transfers data to or from another PLC using a channel. There are two
channel commands for transferring data between PLCs.
Establish Read Channel
Establish Write Channel
These Channel Commands are based on the concept of periodic data transfers. The
client (local) PLC uses a single COMMREQ function to establish a channel (connection)
to a server (remote) PLC and to request that specific data be periodically transferred
between the PLCs.
Note
To simplify the discussion of the Command Blocks, we make the
assumption that the operator/programmer is local to the client PLC and
the server is remote from this operator/programmer.
The Ethernet Interface automatically manages the establishment of communications and
the periodic data transfer. Parameters in the Command Block specify the frequency and
direction of the transfer, and the memory locations in the client and server to be used in
the transfer.
Aborting and Re-tasking a Channel
There are 4 ways a channel can be aborted.
1. When the PLC CPU is stopped, all channels in use are aborted.
2. A channel (or all channels) can be aborted by issuing an Abort Channel command.
3. A channel in use can be re-tasked by issuing an Establish Read Channel or Establish
Write Channel command for its channel number. This aborts the previous channel
operation and then performs the new channel operation.
4. A channel is also automatically aborted if a fatal error occurs.
4
4-10 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Retrieving Detailed Status on the Channel
As discussed before, there are several forms of status available to the ladder program.
These are all discussed in Section 4. One form of status is obtained through the Retrieve
Detailed Channel Status (RDCS) command described later in this section.
Specifying the Location of the Channel Status
The Assign Channel Status Vector (ACSV) command tells the Ethernet Interface what
the PLC reference table memory location will be used for the 64-bit Channel Status bits.
This Channel Command is required for users who have configured the Ethernet Interface
using MMS-ETHERNET configuration mode with Logicmaster 90-70. If Logicmaster
90-70 configuration software has been used to configure the client Ethernet Interface in
TCP/IP configuration mode, this Channel Command must not be used.
Note
Using TCP/IP configuration mode requires both Logicmaster 90-70 release
6.02 (or later) and Series 90-70 CPU firmware release 5.03 (or later).
If TCP/IP configuration mode has been used, then Logicmaster 90-70 has already
specified an 80-bit area to hold the sixteen LAN Interface Status (LIS) bits and the
sixty-four Channel Status bits. In this case, the PLC CPU will update these 80 bits once
each scan with the latest data from the Ethernet Interface. Attempting to specify an
additional 64-bit area would mean that the PLC CPU would update the
Logicmaster-specified 80-bit area and the Ethernet Interface would update the
user-specified 64-bit area. This would be wasteful in addition to slowing down overall
PLC system performance. If possible, GE Fanuc recommends using TCP/IP
configuration mode when using the TCP client capability of this Ethernet Interface.
If MMS-ETHERNET configuration mode must be used (such as when using a CPU 780,
which will never be updated to firmware level 5.03 or later), then this Channel
Command is the only way you may specify the location of the sixty-four Channel Status
bits to the Ethernet Interface. Note that in MMS-ETHERNET configuration mode,
Logicmaster 90-70 still specifies the location of the sixteen LIS bits.
4
4-11
GFK-1004B Chapter 4 Programming Communications Requests
Establish Read Channel (2003)
The Establish Read Channel Command requests that a channel be associated with a
remote PLC and that data from the remote PLC be transferred (periodically) to the local
PLC. The Command Block specifies the period, the number of reads from the remote to
perform, and the timeout allowed in waiting for each transfer to complete. The first
read is performed immediately, regardless of the period specified.
Example Command Block
Establish a channel (channel 5) to a remote PLC at IP address 3.0.0.1. Return the
COMMREQ Status word to %R10. Read remote PLC registers %R50-%R57 to local PLC
registers %R100-%R107. Repeat the read 10 times once every 7 seconds with a timeout
of 500 ms for each read.
Dec (Hex)
Word 1 00017 (0011) Length of Channel Command Data Block (17 - 25 words)
Word 2 00000 (0000) Always 0 (no-wait mode request)
Word 3 00008 (0008) Memory type of CRS word (%R)
Word 4 00009 (0009) CRS word address minus 1 (%R10)*
Word 5 00000 (0000) Reserved
Word 6 00000 (0000) Reserved
Word 7 02003 (07d3) Establish Read Channel Command number
Word 8 00005 (0005) Channel number (5)
Word 9 00010 (000A) Number of read repetitions (read 10 times)
Word 10 00003 (0003) Time units for read period (3=seconds)
Word 11 00007 (0007) Number of time units for read period (every 7 seconds)
Word 12 00050 (0032) Timeout for each read (500 ms)
Word 13 00008 (0008) Local PLC - memory type at which to store data (%R)
Word 14 00100 (0064) Local PLC - starting address at which to store data (%R100)
Word 15 00008 (0008) Remote PLC - memory type from which to read data (%R)
Word 16 00050 (0032) Remote PLC - starting address from which to read data (%R50)
Word 17 00008 (0008) Remote PLC - number of memory units (8 registers)
Word 18 00001 (0001) Remote PLC - PLC (node) address type (IP Address)
Word 19 00004 (0004) Remote PLC - PLC (node) address length in words (4)
Word 20 00003 (0003) Remote PLC - Register 1 of IP address (3)
Word 21 00000 (0000) Remote PLC - Register 2 of IP address (0)
Word 22 00000 (0000) Remote PLC - Register 3 of IP address (0)
Word 23 00001 (0001) Remote PLC - Register 4 of IP address (1)
Word 24 - 27 Remote PLC - Program Name (needed for access to remote %P
or %L) (zero terminated and padded)
Word 28 - 31 Remote PLC - Program Block (needed for access to remote %L)
(zero terminated and padded)
* Word 4 (CRS word address) is the only zero-based address in the Command Block.
Only this address requires subtracting 1 from the intended address.
(Word 7) Channel Command Number: Word 7 requests that a read channel be set up. If
the command is processed successfully, it will result in attempting the specified number
of transfers from the server to the client.
The term local PLC is
used here to identify the
client PLC-the PLC
that initiates the
communications
request.
The term remote PLC
is used here to identify
the server PLC -the
PLC that responds to
the request.
4
4-12 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
(Word 8) Channel Number: Word 8 specifies the channel to be used for the read. This value
must be in the range of 1 to 16. If the channel is out of range, a command error indication
will be placed in the COMMREQ Status word. If the channel number is the same as a
channel already in use, the channel will be retasked to perform this new command.
(Word 9) Number of Read Repetitions: Word 9 specifies the number of reads to be
performed before automatically completing the communications request and closing the
channel. If this value is set to 1, only a single read will be issued. If this value is set to 0,
reads will be issued on the requested period until the channel is aborted.
(Word 10) Time Units for Read Period: Words 10-11 together define how often the read
is to be performed (read period). Word 10 specifies the time unit such as seconds or
minutes for the read period. Word 11 specifies the number of those units. The choices
for the time units are specified in Table 4-1.
Table 4-1. Time Unit Values for Read/Write Repetition Period
Value Meaning
1hundredths of seconds
2tenths of seconds
3 seconds
4 minutes
5 hours
(Word 11) Number of Time Units for Read Period: Word 11 specifies the number of time
units for the read period. The read period is in effect even when the Channel Command
is setup to issue a single read.
Example Read Period Calculation: If Word 10 contains a value of 3 specifying seconds
as the time unit and Word 11 contains a value of 20, then the read period is 20 seconds.
A read will normally be issued at the start of each read period. If the pending read
transfer has not completed during the read period, the Channel Error bit and Detailed
Channel Status words will be set to indicate a non-fatal period error. The pending
transfer can still complete after the period error occurs. For Channel Commands set up
to issue multiple reads, the next read transfer will be issued only after the pending read
transfer completes.
If the Number of Time Units is zero, a subsequent transfer will be issued as soon as the
previous transfer completes, no period errors can occur.
(Word 12) Timeout for Each Read: Word 12 specifies the time (in hundredths of a
second) the Ethernet Interface will wait for a read transfer to complete before setting the
Channel Error bit and Detailed Channel Status words to indicate a non-fatal timeout
error. The transfer can still complete even after a timeout occurs. As a result, an
application can choose what to do if one occurs. If the timeout value is specified as zero,
no timeout errors will be reported.
For most applications a timeout need not be specified because the read period, in effect,
acts as a timeout. (Word 12 should be zero for no timeout). However, there are two
special circumstances in which specifying a timeout is recommended:
When the number of time units (word 11) is zero, so that a subsequent transfer will
be issued as soon as the previous transfer completes and no period errors are
reported. In this case a timeout value can be specified so that timeout errors will be
reported by the Channel Error bit.
A Channel Command
set up to issue a single
read can have only one
pending read transfer.
4
4-13
GFK-1004B Chapter 4 Programming Communications Requests
When the read period is very long (minutes or hours). In this case a shorter timeout
value can be specified so the application doesn’t have to wait for the read period to
expire before taking action.
(Word 13) Local PLC - Memory Type: Words 13-14 specify the location in the local PLC
where the Ethernet Interface will store data received from the remote PLC. The size of
this area is set by the size of the data read from the remote PLC (Word 17). The user is
responsible for assuring that this area is large enough to contain the requested data
without overwriting other application data. Valid memory types are listed in Table 4-2.
Table 4-2. Series 90-70 PLC Memory Types
Type Value
(Decimal) Description
%L* 0 Program Block Local register memory (word mode)
%P* 4 Program register memory (word mode)
%R 8 Register memory (word mode)
%AI 10 Analog input memory (word mode)
%AQ 12 Analog output memory (word mode)
%I 16
70 Discrete input memory (byte mode)
Discrete input memory (bit mode)
%Q 18
72 Discrete output memory (byte mode)
Discrete output memory (bit mode)
%T 20
74 Discrete temporary memory (byte mode)
Discrete temporary memory (bit mode)
%M 22
76 Discrete momentary internal memory (byte mode)
Discrete momentary internal memory (bit mode)
%SA 24
78 Discrete system memory group A (byte mode)
Discrete system memory group A (bit mode)
%SB 26
80 Discrete system memory group B (byte mode)
Discrete system memory group B (bit mode)
%SC 28
82 Discrete system memory group C (byte mode)
Discrete system memory group C (bit mode)
%S 30
84 Discrete system memory (byte mode)
Discrete system memory (bit mode)
%G 56
86 Discrete global data table (byte mode)
Discrete global data table (bit mode)
Read-only memory, cannot be written to.
* Can only be accessed in the Remote PLC.
(Word 14) Local PLC - Memory Starting Address: Word 14 specifies the starting address in
the local PLC in which the data from the remote PLC is to be stored (1-based).
(Word 15) Remote PLC - Memory Type: Words 15-16 specify the memory type and
starting address in the remote PLC from which the data is to be read. Valid values for
Word 15 are given in Table 4-2. If %P memory is used, you must specify a Program name
in words 24 - 27. If %L memory is used, you must specify a Program name in words 24 -
27 and a Program Block name in words 28 - 31.
(Word 16) Remote PLC - Memory Starting Address: Word 16 specifies starting address in
the remote PLC from which the data is to be read (1-based). Valid ranges of values depend
on the remote PLC .
(Word 17) Remote PLC - Number of Memory Units: Word 17 specifies the number of
bits, bytes or words to be read, determined by the remote PLC memory type specified.
For example, if the memory type is %I in bit mode this is the number of bits. If the
4
4-14 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
memory type is %R, this is the number of words. A maximum of 16384 bits/2048
bytes/1024 words of data may be specified.
(Word 18) Remote PLC - PLC (Node) Address Type: Word 18 specifies the format of the
remote PLC address. In this release, Word 18 must contain the value one (1), indicating a
dotted-decimal IP address expressed using a separate register for each decimal digit.
(Word 19) Remote PLC - PLC (Node) Address Length: Word 19 specifies the length in
words of the remote PLC IP address. In this release Word 19 must contain four (4).
(Words 20-23) Remote PLC - PLC (Node) IP Address: Words 20-23 specify the four
integers, one integer per word, of the dotted-decimal IP address of the remote PLC to be
accessed.
Words 24 - 27 Remote PLC - Program Name: Word 24 - 27 specify the case-sensitive,
zero-terminated and padded program name (also called task name, which can be found
through the PROG Station Manager command on the server Ethernet Interface) to be
used with access to remote %P or%L memory. These words are required only for access
to such memory and will be ignored if the Memory Type field is not %P or %L. See Note
below.
Word 28 - 31 Remote PLC - Program Block Name: Words 28 - 31 specify the case-
sensitive, zero-terminated and padded program block name (which can be found in the
program block declaration in the server ladder program) to be used with access to remote
%L memory. These words are required only for access to such memory and will be
ignored if the Memory Type field is not %P or %L.
Note
The Program Name (words 24 - 27) and Program Block Name (words
28 - 31) must have each pair of ASCII characters reversed within the PLC
memory. For example, the name “MARY” (“M” = 4DH, “A” = 41H,
“R” = 52H, “Y” = 59H) would have 414D in the first word and 5952 in
the second word.
4
4-15
GFK-1004B Chapter 4 Programming Communications Requests
Establish Write Channel (2004)
The Establish Write Channel command requests that a channel be connected to a remote
PLC and that data from the local PLC be transferred (periodically) to the remote PLC.
The Command Block specifies the period, the number of writes to the server to perform,
and the timeout allowed in waiting for each transfer to complete. The first write is
performed immediately, regardless of the period specified.
Example Command Block
Establish a write channel (channel 6) to a remote PLC at IP address 3.0.0.1. Return the
COMMREQ Status word to %R10. Write local PLC registers %R50-%R57 to remote PLC
registers %R100-%R107. Repeat the write indefinitely once every 7 seconds with a
timeout of 500 ms for each write.
Dec (Hex)
Word 1 00017 (0011) Length of Channel Command Data Block (17 - 25 words)
Word 2 00000 (0000) Always 0 (no-wait mode request)
Word 3 00008 (0008) Memory type of CRS word (%R)
Word 4 00009 (0009) CRS word address minus 1 (%R10) *
Word 5 00000 (0000) Reserved
Word 6 00000 (0000) Reserved
Word 7 02004 (07d4) Establish Write Channel Command number
Word 8 00006 (0006) Channel number (6)
Word 9 00000 (0000) Number of write repetitions (write indefinitely)
Word 10 00003 (0003) Time units for write period (3=seconds)
Word 11 00007 (0007) Number of time units for write period (every 7 seconds)
Word 12 00050 (0032) Timeout for each write (500 ms)
Word 13 00008 (0008) Local PLC - memory type from which to write data (%R)
Word 14 00050 (0032) Local PLC - starting address from which to write data (%R50)
Word 15 00008 (0008) Remote PLC - memory type at which to store data (%R)
Word 16 00100 (0064) Remote PLC - starting address at which to store data (%R50)
Word 17 00008 (0008) Remote PLC - number of memory units (8 registers)
Word 18 00001 (0001) Remote PLC - PLC (node) address type (IP address)
Word 19 00004 (0004) Remote PLC - PLC (node) address length in words (4)
Word 20 00003 (0003) Remote PLC - register 1 of IP address (3)
Word 21 00000 (0000) Remote PLC - register 2 of IP address (0)
Word 22 00000 (0000) Remote PLC - register 3 of IP address (0)
Word 23 00001 (0001) Remote PLC - register 4 of IP address (1)
Word 24 - 27 Remote PLC - Program Name (needed for access to remote %P
or %L) (zero terminated and padded)
Word 28 - 31 Remote PLC - Program Block (needed for access to remote %L)
(zero terminated and padded)
* Word 4 (CRS word address) is the only zero-based address in the Command Block.
Only this address requires subtracting 1 from the intended address.
(Word 7) Channel Command Number: Word 7 requests that a write channel be set up. If
the command is processed successfully, it will result in attempting the specified number
of transfers from the client to the server.
The term local PLC is
used here to identify the
client PLC-the PLC
that initiates the
communications
request.
The term remote PLC
is used here to identify
the server PLC -the
PLC that responds to
the request.
4
4-16 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
(Word 8) Channel Number: Word 8 specifies the channel to be used for the write. This
value must be in the range of 1 to 16. If the channel is out of range, a command error
indication will be placed in the COMMREQ Status word. If the channel number is the
same as a channel already in use, the channel will be re-tasked to perform this new
command.
(Word 9) Number of Write Repetitions: Word 9 specifies the number of writes to be
performed before automatically completing the communications request and closing the
channel. If this value is set to 1, only a single write will be issued. If this value is set to 0,
reads will be issued on the requested period until the channel is aborted.
(Word 10) Time Units for Write Period: Words 10-11 together define how often the write
is to be performed (write period). Word 10 specifies the time unit such as seconds or
minutes for the write period. Word 11 specifies the number of those units. The choices
for the time units are specified in Table 4-1.
(Word 11) Number of Time Units for Write Period: Word 11 specifies the number of time
units for the write period. The write period is in effect even when the Channel
Command is setup to issue a single write.
Example Write Period Calculation: If Word 10 contains a value of 3 specifying seconds
as the time unit and Word 11 contains a value of 20, then the write period is 20 seconds.
A write will normally be issued at the start of each write period. If the pending write
transfer has not completed during the write period, the Channel Error bit and Detailed
Channel Status words will be set to indicate a non-fatal period error. The pending
transfer can still complete after the period error occurs. For Channel Commands set up
to issue multiple writes, the next write transfer will be issued only after the pending
write transfer completes.
If the Number of Time Units is zero, a subsequent transfer will be issued as soon as the
previous transfer completes; no period errors are reported by the Channel Error bit.
(Word 12) Timeout for Each Write: Word 12 specifies the time (in hundredths of a
second) the Ethernet Interface will wait for a write transfer to complete before setting
the Channel Error bit and Detailed Channel Status bits to indicate a non-fatal timeout
error. The transfer can still complete even after a timeout occurs. As a result, an
application can choose what to do if one occurs. If the timeout value is specified as zero,
no timeout errors will be reported.
For most applications a timeout need not be specified because the write period, in effect,
acts as a timeout. (Word 12 should be zero for no timeout.) However, there are two
special circumstances in which specifying a timeout is recommended:
When the number of time units (word 11) is zero, so that a subsequent transfer will
be issued as soon as the previous transfer completes and no period errors are
reported. In this case a timeout value can be specified so that timeout errors will be
reported by the Channel Error bit.
When the write period is very long (minutes or hours). In this case a shorter timeout
value can be specified so the application doesn’t have to wait for the write period to
expire before taking action.
(Word 13) Local PLC - Memory Type: Words 13-14 specify the location in the local PLC
from where the Ethernet Interface will get the data to be written to the remote PLC.
The size of this area is set by the size of the data written to the remote PLC. Permissible
memory types are given in Table 4-2.
A Channel Command
setup to issue a single
write can have only one
pending write transfer.
4
4-17
GFK-1004B Chapter 4 Programming Communications Requests
(Word 14) Local PLC - Memory Starting Address: Word 14 specifies the starting address
in the local PLC from which the data is to be written (1-based).
(Word 15) Remote PLC - Memory Type: Words 15-16 specify the memory type and
starting address in the remote PLC to which the data is to be stored. Valid memory types
are listed in Table 4-2. The user is responsible for assuring that this area is large enough
to contain the requested data without overwriting other application data.
(Word 16) Remote PLC - Memory Starting Address: Word 16 specifies starting address in
the remote PLC to which the data is to be stored. Valid ranges of values depend on the
remote PLC (1-based).
(Word 17) Remote PLC - Number of Memory Units: Word 17 specifies the number of
bits, bytes or words to be written, determined by the remote PLC memory type
specified. For example, if the memory type is %I, this is the number of bits. If the
memory type is %R, this is the number of words. A maximum of 16384 bits/2048
bytes/1024 words of data may be specified.
(Word 18) Remote PLC - PLC (Node) Address Type: Word 18 specifies the format of the
remote IP address. In this release Word 18 must contain one (1), the address type
indicating a word-oriented, dotted-decimal IP address of a remote PLC.
(Word 19) Remote PLC - PLC (Node) Address Length: Word 19 specifies the length in
words of the remote IP address. In this release Word 19 must contain four (4).
(Words 20-23) Remote PLC - PLC (Node) IP Address: Words 20-23 specify the four
integers, one integer per word, of the dotted-decimal IP address of the remote PLC to be
accessed.
Words 24 - 27 Remote PLC - Program Name: Word 24 - 27 specify the case-sensitive,
zero-terminated and padded program name (also called task name, which can be found
through the PROG Station Manager command on the server Ethernet Interface) to be
used with access to remote %P or%L memory. These words are required only for access
to such memory and will be ignored if the Memory Type field is not %P or %L.
Word 28 - 31 Remote PLC - Program Block Name: Words 28 - 31 specify the case-
sensitive, zero-terminated and padded program block name (which can be found in the
program block declaration in the server ladder program) to be used with access to
remote %L memory. These words are required only for access to such memory and will
be ignored if the Memory Type field is not %P or %L.
Note
The Program Name (words 24 - 27) and Program Block Name (words
28 - 31) must have each pair of ASCII characters reversed within the PLC
memory. For example, the name “MARY” (“M” = 4DH, “A” = 41H,
“R” = 52H, “Y” = 59H) would have 414D in the first word and 5952 in
the second word.
4
4-18 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Send Information Report (2010)
The Send Information Report COMMREQ requests that a particular block of memory
within the PLC CPU reference tables be transferred periodically from an Ethernet
Interface (SRTP Client) to a Host Application SRTP Server. The Command Block
specifies the repetition period, the number of transfers to the server to perform, and the
timeout allowed in waiting for each transfer to complete. The first send is performed
immediately, regardless of the period specified.
Example Command Block
Establish a channel (channel 7) to a remote Host application server at IP address 3.0.0.1.
Return the COMM_REQ Status word to %R10. Send local PLC registers %R50–%R57 to
remote host. Repeat the send 10 times once every 7 seconds with a timeout of 500 ms
for each read.
Dec (Hex)
Word 1 00017 (0011) Length of Send Information Report Data Block (17 words)
Word 2 00000 (0000) Always 0 (no–wait mode request)
Word 3 00008 (0008) Memory type of CRS word (%R)
Word 4 00009 (0009) CRS word address minus 1 (%R10)*
Word 5 00000 (0000) Reserved
Word 6 00000 (0000) Reserved
Word 7 02010 (07DA) Send Information Report Channel Command number
Word 8 00007 (0007) Channel number (7)
Word 9 00010 (000A) Number of repetitions (send 10 times)
Word 10 00003 (0003) Time units for send period (3=seconds)
Word 11 00007 (0007) Minimum interval between host accesses (every 7 seconds)
Word 12 00050 (0032) Timeout on each individual transfer response (500 ms)
Word 13 00008 (0008) Local PLC CPU - memory type from which to send data (%R)
Word 14 00050 (0032) Local PLC CPU - starting address from which to send data (%R50)
Word 15 00008 (0008) Local PLC CPU - number of memory units (8 registers)
Word 16 00000 (0000) Reserved
Word 17 00000 (0000) Reserved
Word 18 00001 (0001) SRTP Server Host Address Type (IP Address)
Word 19 00004 (0004) SRTP Server Host Address Word Length (4)
Word 20 00003 (0003) SRTP Server Host Address Data Word 1 (3)
Word 21 00000 (0000) SRTP Server Host Address Data Word 2 (0)
Word 22 00000 (0000) SRTP Server Host Address Data Word 3 (0)
Word 23 00001 (0001) SRTP Server Host Address Data Word 4 (1)
* Word 4 (CRS word address) is the only zero–based address in the Command Block.
Only this address requires subtracting 1 from the intended address.
(Word 7) Channel Command Number: Word 7 requests that a Send Information Report
channel be set up. If the command is processed successfully, it will result in attempting
the specified number of transfers from the client to the server.
(Word 8) Channel Number: Word 8 specifies the channel to be used for the send. This
value must be in the range of 1 to 16. If the channel is out of range, a command error
The term local PLC is
used here to identify the
client PLC-the PLC
that initiates the
communications
request.
The term SRTP
Server is used here to
identify the Host
server.
4
4-19
GFK-1004B Chapter 4 Programming Communications Requests
indication will be placed in the COMMREQ Status word. If the channel number is the
same as a channel already in use, the channel will be re-tasked to perform this new
command.
(Word 9) Number of Send Repetitions: Word 9 specifies the number of transfers to be
performed before automatically completing the communications request and closing the
channel. If this value is set to 1, only a single transfer will be issued. If this value is set to
0, transfers will be issued on the requested period until the channel is aborted.
(Word 10) Time Units for Send Period: Words 10-11 together define how often the
transfer is to be performed (transfer period). Word 10 specifies the time unit such as
seconds or minutes for the send period. Word 11 specifies the number of those units.
The choices for the time units are specified in Table 4-1.
(Word 11) Number of Time Units for Send Period: Word 11 specifies the number of time
units for the send period. The send period is in effect even when the Channel
Command is setup to issue a single send.
Example Send Period Calculation: If Word 10 contains a value of 3 specifying seconds
as the time unit and Word 11 contains a value of 20, then the send period is 20 seconds.
A send will normally be issued at the start of each send period. If the pending transfer
has not completed during the send period, the Channel Error bit and Detailed Channel
Status words will be set to indicate a non-fatal period error. The pending transfer can
still complete after the period error occurs. For Channel Commands set up to issue
multiple sends, the next transfer will be issued only after the pending transfer
completes.
If the Number of Time Units is zero, a subsequent transfer will be issued as soon as the
previous transfer completes; no period errors are reported by the Channel Error bit.
(Word 12) Timeout for Each Send: Word 12 specifies the time (in hundredths of a
second) the Ethernet Interface will wait for a send transfer to complete before setting the
Channel Error bit and Detailed Channel Status bits to indicate a non-fatal timeout error.
The transfer can still complete even after a timeout occurs. As a result, an application
can choose what to do if one occurs. If the timeout value is specified as zero, no timeout
errors will be reported.
For most applications a timeout need not be specified because the send period, in effect,
acts as a timeout. (Word 12 should be zero for no timeout.) However, there are two
special circumstances in which specifying a timeout is recommended:
When the number of time units (word 11) is zero, so that a subsequent transfer will be
issued as soon as the previous transfer completes and no period errors are reported. In
this case a timeout value can be specified so that timeout errors will be reported by the
Channel Error bit.
When the send period is very long (minutes or hours). In this case a shorter timeout
value can be specified so the application doesn’t have to wait for the send period to
expire before taking action.
(Word 13) Local PLC - Memory Type: Words 13-14 specify the location in the local PLC
from where the Ethernet Interface will get the data to be written to the remote SRTP
server. Permissible memory types are given in Table 4-2.
(Word 14) Local PLC - Memory Starting Address: Word 14 specifies the starting address
in the local PLC from which the data is to be sent (1-based).
A Channel Command
setup to issue a single
send can have only one
pending send transfer.
4
4-20 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
(Word 15) Local PLC - Number of Memory Units: Word 15 specifies the number of
memory units that are to be transferred. The units associated with the memory may be
bits, bytes, or words depending on the memory type specified in Word 13. For example,
if the memory type is %I, this is the number of bits. If the memory type is %R, this is the
number of words. A maximum of 16384 bits/2048 bytes/1024 words of data may be
specified.
(Word 16) Reserved: Word 16 is reserved and should contain the value zero.
(Word 17) Reserved: Word 17 is reserved and should contain the value zero.
(Word 18) Remote Host - Node Address Type: Word 18 specifies the format of the
remote IP address. Word 18 must contain one (1), the address type indicating a
word-oriented, dotted-decimal IP address of a remote PLC.
(Word 19) Remote Host - Node Address Length: Word 19 specifies the length in words of
the remote IP address. Word 19 must contain four (4).
(Words 20-23) Remote Host - Node IP Address: Words 20-23 specify the four integers,
one integer per word, of the dotted-decimal IP address of the remote PLC to be
accessed.
4
4-21
GFK-1004B Chapter 4 Programming Communications Requests
Abort Channel (2001)
The Abort Channel command immediately disconnects an active channel from its
remote PLC and renders the channel idle. The Channel Transfer bit, the Channel Error
bit, and the Detailed Channel Status words for the channel are set to zero.
Example Command Block
Abort Channel 5. Return the CRS word to %R10.
Dec (Hex)
Word 1 00002 (0002) Length of Channel Command Data Block (2 words)
Word 2 00000 (0000) Always 0 (no-wait mode request)
Word 3 00008 (0008) Memory type of CRS word (%R)
Word 4 00009 (0009) CRS word address minus 1* (%R10)
Word 5 00000 (0000) Reserved
Word 6 00000 (0000) Reserved
Word 7 02001 (07d1) Abort Channel Command number
Word 8 00005 (0005) Channel number 5
* Word 4 (CRS word address) is the only zero-based address in the Command Block.
Only this address requires subtracting 1 from the intended address.
(Word 7) Channel Command Number: This command parameter requests that a channel
be aborted. If the command is processed successfully, it will terminate the processing on
the channel by the time success is indicated in the COMMREQ Status word.
(Word 8) Channel Number: The channel number specifies the channel to be
disconnected (1-16). As a convenient way to abort all channels, if the channel number
parameter is -1 (ffffH), all channels in use will be aborted. It is not an error to abort all
channels when there are none in use. Neither is it an error to abort an idle channel.
Note
For the Abort Channel, Retrieve Detailed Channel Status, and Assign
Channel Status Vector commands, no actual data is transmitted on the
network. Communication occurs between the client PLC CPU and the
local Ethernet Interface only. For these commands, the actual function is
performed locally and then the COMMREQ Status word is sent
immediately to the CPU.
4
4-22 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Retrieve Detailed Channel Status (2002)
The Retrieve Detailed Channel Status command requests that the current Detailed
Channel Status words be returned for a channel. The Detailed Channel Status words
contain an active/inactive channel indicator and the last channel error codes seen (see
Section 4 for more details). These two words of detailed status supplement the
information available in the COMMREQ Status word and the Channel Status bits. The
command has no effect on the value of the Channel Status bits.
Be aware that the Detailed Channel Status words are updated every time the status of
the channel changes. If, for example, the channel is operating with a fast repetition
period, the status words may change faster than the ladder executes the COMMREQ to
retrieve them. Therefore, some status values will be missed from the ladder’s point of
view.
Example Command Block
Retrieve detailed channel status for channel 5. Store the Detailed Channel Status words
to Registers 100-101. Return the COMMREQ Status word to %R10.
Dec (Hex)
Word 1 00004 (0004) Length of Channel Command Data Block (4 words)
Word 2 00000 (0000) Always 0 (no-wait mode request)
Word 3 00008 (0008) Memory Type of CRS word (%R)
Word 4 00009 (0009) CRS word address minus 1 (%R10)*
Word 5 00000 (0000) Reserved
Word 6 00000 (0000) Reserved
Word 7 02002 (07d2) Retrieve Detailed Channel Status Command number
Word 8 00005 (0005) Channel number 5
Word 9 00008 (0008) Local PLC - memory type to store Detailed Chan. Stat. (%R)
Word 10 00100 (0064) Local PLC - starting address (%R100)
* Word 4 (CRS word address) is the only zero-based address in the Command Block.
Only this address requires subtracting 1 from the intended address.
(Word 7) Channel Command Number: The command parameter in Word 7 requests that
Detailed Channel Status words be returned. If the command is processed successfully,
the Detailed Channel Status words will be written to the location specified in Words 9
and 10. Then the CRS word will indicate successful completion of the command. If the
specified channel is not currently in use, the latest status will be returned.
(Word 8) Channel Number: The channel number in Word 8 specifies the channel whose
status is to be read. This value must be a channel number in the range of 1 to 16 decimal.
(Word 9) Local PLC - Memory Type: Words 9 and 10 specify the starting point in the
client CPU memory where the Detailed Channel Status words are to be written. The
length of the transfer is implied and is equal to 2 words. Section 4 describes the format
of the DCS words. Word 9 specifies the memory type (See Table 4-2).
The term local PLC is
used here to identify the
client PLC-the PLC
that initiates the
communications
request.
4
4-23
GFK-1004B Chapter 4 Programming Communications Requests
(Word 10) Local PLC - Memory Starting Address: Starting address to store the Detailed
Channel Status words.
For more information on detailed channel status, see Section 4.
Note
For the Abort Channel, Retrieve Detailed Channel Status, and Assign
Channel Status Vector commands, no actual data is transmitted on the
network. Communication occurs between the client PLC CPU and the
local Ethernet Interface only. For these commands, known as “local”
commands, the actual function is performed locally and then the
COMMREQ Status word is sent immediately to the CPU.
4
4-24 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Assign Channel Status Vector (2000)
The Assign Channel Status Vector (ACSV) command specifies the location in local PLC
CPU reference table memory of the sixty-four (64) Channel Status bits. This command is
required for COMMREQ support when the Ethernet Interface has been configured by
Logicmaster 90-70 to be in MMS-ETHERNET configuration mode. If, however, the
Ethernet Interface has been configured in TCP/IP configuration mode, this command
must not be used. When in TCP/IP configuration mode, Logicmaster 90-70 configures the
location of the sixteen LAN Interface Status (LIS) bits as well as the sixty-four Channel
Status bits, and all eighty (80) status bits are updated once each PLC scan.
Example Command Block
Specify %T56 (in bit mode) as the starting location for the sixty-four Channel Status bits.
Return the COMMREQ Status (CRS) word in %AQ14.
Dec (Hex)
Word 1 00003 (0003) Length of Assign Channel Status Vector data block (3 words)
Word 2 00000 (0000) Always 0 (no-wait mode request)
Word 3 00012 (000c) Memory type of CRS word (%AQ)
Word 4 00013 (000d) CRS word address minus 1 (%AQ14)
Word 5 00000 (0000) Reserved
Word 6 00000 (0000) Reserved
Word 7 02000 (07d0) Assign Channel Status Vector command number
Word 8
Word 9 00074 (0040)
00056 (0038) Memory type where to put Channel Status bits (%T)
Starting address of Channel Status bits
* Word 4 (CRS word address) is the only zero-based address in the Command Block.
Only this address requires subtracting 1 from the intended address.
(Word 7) Channel Command Number: The command parameter in Word 7 requests that
the sixty-four (64) bits of Channel Status be assigned to a local reference table address
(specified in Words 8 and 9). If the command is processed successfully, the CRS word
will indicate successful completion. From that point on, the Ethernet Interface will
update sixty-four bits at the specified location each time the status changes. This will
continue until either the channel is aborted or another ACSV command is issued.
(Word 8) Memory Type: Words 8 and 9 specify the starting address in local PLC
memory for the sixty-four (64) bits of Channel Status. Word 8 specifies the memory type
(see Table 4-2).
(Word 9) Starting Address: Starting address to store the Channel Status bits.
Note
If both Word 8 and Word 9 are zero (0), this means “none”, which will
cause the Ethernet Interface to stop updating memory with the Channel
Status bits. If the address in Words 8 and 9 is valid, the Ethernet
Interface will update that memory location with 64 bits of information
each time one of those bits change.
4
4-25
GFK-1004B Chapter 4 Programming Communications Requests
Section 4: Status Data
This section describes all the status data that is available to the ladder program to deter-
mine the state of the Ethernet Interface and its channels.
Types of Status Data
There are four main types of status data available to your ladder program.
1. OK Output of the COMMREQ Function Block. This output is set if the PLC CPU was
successful in transferring the COMMREQ data from the reference table memory
specified by the COMMREQ function block into the memory local to the Ethernet
Interface. This does not indicate that the Ethernet Interface has processed the
COMMREQ, only that it has been received by the Ethernet Interface.
Barring ladder programming errors, the OK and FT outputs should not both be set
in the same scan by the same COMMREQ.
2. FT Output of the COMMREQ Function Block. This output is set if there is a
programming error in the COMMREQ Function Block itself, if the rack and slot
specified in the COMMREQ Task parameter is not configured by Logicmaster 90-70
to contain an Ethernet Interface, or if the data block length specified in the
Command Block is out of range. This output also may indicate that no more
COMMREQ functions can be initiated in the ladder program until the Ethernet
Interface has time to process some of the pending COMMREQ functions.
If the FT Output is set, the CPU does not transfer the Command Block to the
Ethernet Interface. In this case, the other status indicators are not updated for this
COMMREQ.
3. Status Bits. The status bits are updated in the CPU once each PLC scan by the
Ethernet Interface. These bits are generally used to prevent initiation of a
COMMREQ function when certain errors occur or to signal a problem on an
established channel. The status bits include the LAN Interface Status bits and the
Channel Status bits. The starting location of these bits is user-configurable. See
Chapter 2 for more information.
The LAN Interface Status bits monitor the health of the Ethernet Interface itself such
as the LAN Interface OK bit and the AUI Fuse Blown bit. The Channel Status bits
monitor the health and progress of a channel established using the Establish Read/
Write Channel Commands.
4. Communications Status Words. There are two types of words that provide detailed
information: The COMMREQ Status word (CRS word) and the Detailed Channel
Status words (DCS words). The communications status words are not updated in
the CPU each scan as are the status bits. They are generally used to determine the
cause of a communications error after the COMMREQ function is initiated. The
cause is reported in the form of an error code described later in this section.
4
4-26 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
The COMMREQ Status word (CRS word) is returned from the Ethernet Interface to
the CPU immediately if the Command Block contains a syntax error or if the command
is local. For remote commands with no syntax error, it is returned either after the chan-
nel is established successfully and the first transfer has completed or if there is an error
establishing the channel. The location of the CRS word is defined in the Command
Block for the COMMREQ function.
The Detailed Channel Status words (DCS words) are returned to the CPU only by
executing the Retrieve Detailed Channel Status Command. If a channel error is indi-
cated (by the Channel Error bit) after the channel is established, the first word of the
DCS words will contain an error code indicating the cause of the error. The second
word of the DCS words indicates whether the channel is active or idle.
Be aware that the Detailed Channel Status words are updated every time the status
of the channel changes. If, for example, the channel is operating with a fast
repetition period, the status words may change faster than the ladder executes the
COMMREQ to retrieve them. Therefore, some status values may be missed from the
ladder’s point of view.
Description of the Status Data
The errors and status reported in each type of status data are described below.
OK Output of the COMMREQ Function Block
The OK output passes power when the COMMREQ has successfully been deposited
into memory local to the target Ethernet Interface.
FT Output of the COMMREQ Function Block
The FT Output passes power upon the following errors.
Invalid rack/slot specified. The module at this rack/slot is unable to receive a
COMMREQ.
Task ID not valid. (Task ID should be set to zero.)
Data Block length is zero or greater than 128.
Too many simultaneous active COMMREQs (overloading either the PLC CPU or the
Ethernet Interface).
Status Bits
The status bits normally occupy a single block of memory. The location of this block is
specified during module configuration in the Logicmaster Configuration Software (see
Chapter 2 for details). The first 16 bits of the block (see table below) comprise the LAN
Interface Status (LIS) bits. The next 32 bits comprise the Channel Status bits (2 for each
channel). The last 32 bits are reserved for future use. A detailed explanation of the sta-
tus bits is given following the table.
Note
Unless the “LAN Interface OK” bit is set (bit 16 in the following table),
the other status bits are invalid.
4
4-27
GFK-1004B Chapter 4 Programming Communications Requests
Note
If you use the Logicmaster “MMS-Ethernet configuration mode”
(instead of “TCP/IP configuration mode”) you will only have the sixteen
(16) LIS bits transferred automatically from the Ethernet Interface to the
PLC CPU memory on each input scan. You may assign an additional
location into which the Ethernet Interface will store the sixty-four (64)
Channel Status bits by using the Assign Channel Status Vector
COMMREQ.
Table 4-3. Status Bits (LIS Bits and Channel Status Bits)
Status Bits Brief Description
1-7 Reserved
8AUI Fuse Blown
9Any Channel Error (error on any channel)
10-12 Reserved
13 LAN OK
14 Resource Problem
15 Reserved
16 LAN Interface OK
17 Data Transfer - Channel 1
18 Channel Error - Channel 1
... ...
47 Data Transfer - Channel 16
48 Channel Error - Channel 16
49-80 Reserved for future use
Note
Unless the “LAN Interface OK” bit is set (Status Bit 16), the other status
bits are invalid.
(Status Bit 8) AUI Fuse Blown: This bit is set to 1 when the AUI Fuse is blown. Other-
wise it is set to 0.
(Status Bit 9) Any Channel Error: This bit is set to 1 if there is presently an error on any
of the established channels; i.e., if the individual Channel Error bit is set for any channel.
(Status Bit 13) LAN OK: This input will be held at the value 1 as long as the Ethernet
Interface software is able to communicate on the network. If the network should be-
come inaccessible from this Interface, due either to local or network problems, this bit
will be set to 0. If LAN communication becomes possible, it is set to 1.
(Status Bit 14) Resource Problem: This input is set to 1 whenever the Ethernet Interface
software experiences a resource problem (i.e., lack of data memory). The bit is reset to 0
on a subsequent PLC sweep. The Ethernet Interface may or may not be able to continue
functioning, depending on the severity of the problem. Use the PLC Fault Table to un-
derstand the problem. See Chapter 6, Troubleshooting, for further information. In
addition, you can use the Station Manager STAT B and LOG commands to further under-
stand the problem. See Chapter 5, The Station Manager, for more information.
(Status Bit 16) LAN Interface OK Bit: This input is set to 1 by the Ethernet Interface each
PLC scan. If the Ethernet Interface cannot access the PLC, the CPU will set this bit to 0.
When this bit is 0, all other Ethernet Interface Status bits are invalid.
4
4-28 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Each channel has a dedicated pair of bits as follows:
(Status Bits 17, 19, 21 ... 47) Data Transfer Bit: This bit is normally set to 0. It is pulsed
to 1 and back to 0 on successive PLC scans each time a transfer completes successfully.
Do not assume that when the Data Transfer bit goes to 1 that a transfer has just completed during
the last scan. The Data Transfer bit is not closely synchronized in time with the transfer.
The bit only indicates that a transfer has occurred during the preceding read (or write)
period. A rising edge on the Data Transfer bit indicating that a transfer has completed
successfully does not guarantee that the next transfer has not begun or completed. In
the case of an Establish Channel command, the CRS word is always updated before the
Data Transfer bit is set to 1.
(Status Bits 18, 20, 22 ... 48) Channel Error Bit: This bit is set to 1 when an error is de-
tected on this channel. It is set to 0 when the channel is initially established and if the
channel resumes normal operation after a transient error condition subsides. The Chan-
nel Error bit is also set to 0 when the channel is aborted by an Abort Channel command
or when the PLC CPU transitions from RUN to STOP. In the case of an Establish Chan-
nel command, the CRS word is always updated before the Channel Error bit is set to 1.
4
4-29
GFK-1004B Chapter 4 Programming Communications Requests
Communications Status Words
The COMMREQ Status word (CRS word) and the first word of the two Detailed Chan-
nel Status words (DCS words) report status and errors in the same format, as shown be-
low. The second word of the DCS words indicates when the channel is active.
The CRS word location is specified in Words 3 and 4 of the Command Block. The DCS
words location is specified in the Retrieve Detailed Channel Status Command. The con-
tents of these status words are defined below:
The initial value of the Detailed Channel Status words is all zeros. DCS words are reset
to zero when:
The Ethernet Interface is powered up or restarted
The CPU transitions from STOP to RUN
A channel abort COMMREQ aborts the channel
Hex Format
High Low
00 00
Minor Error Codes (high byte)
Success and Major Error Codes (low byte)
CRS Word in
Figure 4-3. Format of the COMMREQ Status Word (CRS Word)
High Low
00 00
Minor Error Codes (high byte)
Success and Major Error Codes (low byte)
0000
Channel Active (0001 = channel active,
0000 = channel not active)
DCS Word in Hex Format
Word 1Word 2
Figure 4-4. Format of the Detailed Channel Status Words (DCS Words)
There are several points to remember when interpreting the contents of the COMMREQ
Status word and Word 1 of the Detailed Channel Status words:
1. Display the Status Words in hexadecimal form to more easily differentiate the high and
low bytes. A good way to do this is to use a MOVE WORD function block to display
the hexadecimal value within the ladder program.
2. The Ethernet Interface will never send a zero for the COMMREQ Status word to the
PLC CPU. The user program should zero the COMMREQ Status word before issuing
4
4-30 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
the COMMREQ function and then check for a non-zero value indicating that the
Ethernet Interface is responding to the COMMREQ. A good way to do this is to use
a MOVE WORD function block to zero the CRS word.
3. A status code of 1 in the low byte and 0 in the high byte indicates that the request
was successful. All other non-zero values indicate errors. Refer to the tables below
for a complete listing of major and minor error codes.
The following tables list the error codes that are reported in the COMMREQ Status word
after the execution of a COMMREQ function. These codes also may appear in Word 1 of
the Detailed Channel Status words.
Table 4-4. Major Error Codes
Error Status Major Error Description
Hexadecimal
01H Successful Completion. (This is the expected completion value in
the COMMREQ Status word.)
02H Insufficient Privilege at server PLC. For a Series 90-70 server PLC, the
minor error code contains the privilege level required for the service
request.
04H Protocol Sequence Error. The server CPU has received a message that is
out of order. Call GE Fanuc Automation for assistance.
05H Service Request Error at server PLC. The minor error code contains the
specific error code. See table of Minor Error codes below.
06H Illegal Mailbox Type at server PLC. Service request mailbox type is ei-
ther undefined or unexpected. Call GE Fanuc Automation for assistance.
07H The server PLC CPUs Service Request Queue is full. The client should
retry later. It is recommended that the client wait a minimum of 10 mil-
liseconds before sending another service request.
0bH Illegal Service Request. The requested service is either not defined or
not supported at the server PLC. (This value is returned in lieu of the
actual service request error (01h), to avoid confusion with the normal
successful COMMREQ completion.) Call GE Fanuc Automation for assis-
tance.
11H SRTP Error Codes at server. An error was detected at the SRTP server.
See table of Minor Error codes below.
82H Insufficient Privilege at client PLC. For Series 90-70 PLC, the minor er-
ror code contains the privilege level required for the service request.
84H Protocol Sequence Error. The CPU has received a message that is out
of order. Call GE Fanuc Automation for assistance.
85H Service Request Error at the client PLC. The minor error code contains
the specific error code. See table of Minor Error codes below.
86H Illegal Mailbox Type. Service request mailbox type is either undefined
or unexpected. Call GE Fanuc Automation for assistance.
87H The client PLC CPUs Service Request Queue is full. The client should
retry later. It is recommended that the client wait a minimum of 10 mil-
liseconds before sending another service request.
8bH Illegal Service Request. The requested service is either not defined or
not supported. (This value is returned in lieu of the actual service re-
quest error (01h), to avoid confusion with the normal successful
COMMREQ completion.). Call GE Fanuc Automation for assistance.
90H Client API error. See table of Minor Error codes below.
4
4-31
GFK-1004B Chapter 4 Programming Communications Requests
Minor Error Codes
The meaning of each Minor Error Code depends upon the Major Error Code for which it
is defined. Consult the appropriate Minor Error Code table for the indicated Major Error
Code.
Table 4-5. Minor Error Codes for Major Error Codes 05H (at Remote Server PLC) and
85H (at Client PLC)
Error Status Service Request Error Description
(Hexadecimal)
c105H/c185H Invalid block state transition.
c305H/c385H Text length does not match traffic type.
c605H/c685H Control Program (CP) tasks exist but requestor not logged into main CP.
c705H/c785H Passwords are set to inactive and cannot be enabled or disabled.
c805H/c885H Password(s) already enabled and cannot be forced inactive.
c905H/c985H Login using non-zero buffer size required for block commands.
ca05H/ca85H Device is write-protected.
cb05H/cb85H A comm or write verify error occurred during save or restore.
cc05H/cc85H Data stored on device has been corrupted and is no longer reliable.
cd05H/cd85H Attempt was made to read a device but no data has been stored on it.
ce05H/ce85H Specified device has insufficient memory to handle request.
cf05H/cf85H Specified device is not available in the system (not present).
d105H/d185H Packet size or total program size does not match input.
d205H/d285H Invalid write mode parameter.
d505H/d585H Invalid block name specified in datagram.
d605H/d685H Total datagram connection memory exceeded.
d705H/d785H Invalid datagram type specified.
d805H/d885H Point length not allowed.
d905H/d985H Transfer type invalid for this Memory Type selector.
da05H/da85H Null pointer to data in Memory Type selector.
db05H/db85H Invalid Memory Type selector in datagram.
dc05H/dc85H Unable to find connection address.
dd05H/dd85H Unable to locate given datagram connection ID.
de05H/de85H Size of datagram connection invalid.
df05H/df85H Invalid datagram connection address.
e005H/e085H Service in process cannot login.
e405H/e485H Memory Type for this selector does not exist.
e905H/e985H Memory Type selector not valid in context.
ea05H/ea85H Not logged in to process service request.
ee05H/ee85H Could not return block sizes.
ef05H/ef85H Programmer is already attached.
f005H/f085H Request only valid in stop mode.
f105H/f185H Request only valid from programmer.
f205H/f285H Invalid program cannot log in.
f405H/f485H Invalid input parameter in request.
f505H/f585H Invalid password.
f605H/f685H Invalid sweep state to set.
4
4-32 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Table 4-5. Minor Error Codes for Major Error Codes 5H and 85H (Continued)
Error Status Service Request Error Description
(Hexadecimal)
f705H/f785H Required to log in to a task for service.
f805H/f885H Invalid task name referenced.
f905H/f985H Task address out of range.
fc05H/fc85H I/O configuration is invalid.
fe05H/fe85H No privilege for attempted operation.
ff05H/ff85H Service request has been aborted.
Table 4-6. Minor Error Codes for Major Error Code 11H (at Remote Server PLC)
Error Status SRTP Error Description
(hexadecimal)
0111H Generic SRTP error.
0211H The PLC is inaccessible.
0311H Reserved.
0411H Unexpected SRTP version encountered in received message.
0511H Unrecognized SRTP message received.
0611H Data present in SRTP message which should not contain data.
0711H Generic resource problem detected.
0811H SRTP message encountered in inappropriate connection state.
0911H Generic refusal by backplane driver to handle request.
0a11H Recognized but unsupported SRTP message received.
0b11H Lost transaction in server.
1411H Request failed due to an error in the remote device. The Remote
device log will have more information.
2711H Backplane driver not initialized.
2a11H The backplane driver could not access the PLC.
2b11H Invalid binding on the message sent to the backplane driver.
2c11H The message could not be sent to its destination because the mailbox was
not open.
2d11H The maximum number of transfers to the destination is already
taking place.
2e11H The maximum number of transfers of this transfer type is
already taking place.
2f11H Cannot obtain a backplane transfer buffer.
3011H Cannot obtain resources other than backplane transfer buffers.
3111H Connection ID or block transfer ID is not valid.
3211H Timed out waiting for PLC CPU response.
3311H The PLC CPU aborted the request.
3411H An invalid message type was specified.
3511H The specified task is not registered.
3611H The mailbox offset specified is invalid.
3a11H More than the allowable byte length in a single transfer.
3b11H Bad sequence number in the request.
3c11H Invalid command in request.
3f11H Request failed due to error on remote device, most likely running out of Dual-
Port RAM text buffers.
4
4-33
GFK-1004B Chapter 4 Programming Communications Requests
Table 4-7. Minor Error Codes for Major Error Code 90H (at Client PLC)
Error Status Application Interface Error Description
(Hexadecimal)
0190H Timeout expired before transfer completed; still waiting on transfer.
0290H Period expired before transfer completed; still waiting on transfer.
8190H COMMREQ data block too short for the command.
8290H COMMREQ data block too short for server PLC node address.
8390H Invalid server memor y type.
8490H Invalid Program Name.
8590H Invalid Program Block Name.
8690H Zero server unit length is not allowed.
8790H Server unit length is too large. (Maximum permitted 1024 bytes)
8890H Invalid channel number.
8990H Invalid time unit for period. (Maximum permitted 3965 hours)
8a90H Period value is too large.
8b90H Zero server starting address is not allowed.
8c90H Invalid client memory type.
8d90H Invalid server host address type.
8e90H Invalid IP address integer value. (Must be 0-255)
8f90H Invalid IP address class.
9090H Insufficient TCP connection resources to do request.
9190H Zero local starting address is not allowed.
9290H Server host address length value is too short for server host
address type.
9390H COMMREQ data block too short for Program Block name
(including 0 pad).
9490H COMMREQ data block too short for Program name
(including 0 pad).
9590H Internal API error. See PLC fault table or exception log for details. This
problem may occur due to the Ethernet Interface being asked to per-
form beyond its capacity. Try transferring less data per message or es-
tablishing fewer simultaneous connections.
9690H Underlying TCP connection aborted (reset) by server end point.
9790H Underlying TCP connection aborted by client end point.
9890H The remote server has no Service Request Processor.
9a90H Response to session request did not arrive in proper order.
9b90H Session denied by server PLC.
9c90H Data response did not arrive in proper order.
9d90H Data response had unexpected size.
9e90H Unrecognized COMMREQ command code.
a190H Invalid CRS word memory type.
a290H Failed an attempt to update the CRS word.
4
4-34 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 5: Controlling Communications in the Ladder Program
This section provides tips on how to control communications in your ladder program.
Only segments of actual ladder logic are included. For a sample of a complete working
program, see Appendix D. Topics discussed are:
Essential Elements of the Ladder Program
Troubleshooting Your Ladder Program
Monitoring Communications in the Ladder Program
Sequencing Communications Requests
Essential Elements of the Ladder Program
Every ladder program, whether in the developmental phase or the operational phase,
should do the following before initiating a COMMREQ function.
1. Initiate the COMMREQ function with a one-shot transitional coil or contact. This
prevents accidentally sending the same COMMREQ Command Block more than
once.
2. Include at least the LAN Interface OK bit in the LAN Interface Status Word as an
interlock contact for the COMMREQ function. You may choose to add more
interlocks.
3. Zero the word location you specify for the COMMREQ Status (CRS) word, and OK
and FT Outputs of the COMMREQ Function Block before the COMMREQ function
is initiated.
4. Move the command code and parameters for the Channel Command into the
memory location specified in IN input of the COMMREQ Function Block before the
COMMREQ function is initiated.
4
4-35
GFK-1004B Chapter 4 Programming Communications Requests
The ladder program segment below illustrates how to incorporate these important
points in your program.
Note
The input values for the Block Move Functions in this example are taken
from the Establish Read Channel Command example in Section 3 of this
chapter.
Nicknames have used in this example to make the ladder program
easier to follow. LANIFOK is bit 16 of the LAN Interface Status bits. All
other nicknames can be assigned as you desire.
| << RUNG 1 >>
|
|LANIFOK HEALTHY
+——] [—————————————————————————————————————————————————————————————————————( )——
|
| << RUNG 2 >>
|
|BEGREAD READREQ
+——] [—————————————————————————————————————————————————————————————————————(↑)——
|
| << RUNG 3 >>
|
|HEALTHY READREQ +—————+ CMRQFLT
+——] [—————] [———+MOVE_+———————————————————————————————————————————————————(R)——
| |WORD |
| | |
| CONST —+IN Q+—%R00010
| +0000 | LEN |
| |00001|
| | |
| +—————+
| << RUNG 4 >>
|HEALTHY READREQ +—————+ +—————+ +—————+
+——] [—————] [———+BLKMV+—————————————————+BLKMV+—————————————————+BLKMV+
| | INT | | INT | | WORD|
| | | | | | |
| CONST —+IN1 Q+—%R00301 CONST —+IN1 Q+—%R00308 CONST —+IN1 Q+—%R00315
| +00017 | | +00005 | | +00008 | |
| | | | | | |
| CONST —+IN2 | CONST —+IN2 | CONST —+IN2 |
| +00000 | | +00010 | | +00050 | |
| | | | | | |
| CONST —+IN3 | CONST —+IN3 | CONST —+IN3 |
| +00008 | | +00003 | | +00008 | |
| | | | | | |
| CONST —+IN4 | CONST —+IN4 | CONST —+IN4 |
| +00009 | | +00004 | | +00001 | |
| | | | | | |
| CONST —+IN5 | CONST —+IN5 | CONST —+IN5 |
| +00000 | | +00050 | | +00004 | |
| | | | | | |
| CONST —+IN6 | CONST —+IN6 | CONST —+IN6 |
| +00000 | | +00008 | | +00003 | |
| | | | | | |
| CONST —+IN7 | CONST —+IN7 | CONST —+IN7 |
| +02003 +—————+ +00100 +—————+ +00000 +—————+
|
|
4
4-36 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
| << RUNG 5 >>
|
|HEALTHY READREQ +————–+
+——] [—————] [———+BLKMV+—
| | INT |
| | |
| CONST —+IN1 Q+—%R00322
| +00000 | |
| | |
| CONST —+IN2 |
| +00001 | |
| | |
| CONST —+IN3 |
| +00000 | |
| | |
| CONST —+IN4 |
| +00000 | |
| | |
| CONST —+IN5 |
| +00000 | |
| | |
| CONST —+IN6 |
| +00000 | |
| | |
| CONST —+IN7 |
| +00000 +—————+
|
| << RUNG 6 >>
|
|HEALTHY READREQ +—————+
+——] [—————] [———+COMM_+—
| | REQ |
| | | CMRQFLT
| %R00301—+IN FT+———————————————————————————————————————————————————(S)
| | |
| CONST | |
| 0004—+SYSID|
| | |
| CONST —+TASK |
| 00000000 +—————+
|
Rung # 1: Input LANIFOK (bit 16 of the LAN Interface Status bits) monitors the health
of the Ethernet Interface. If it is OK to send a COMMREQ, the HEALTHY coil is ON.
HEALTHY is used as an interlock for Rungs 3-6.
Rung # 2: Input BEGREAD triggers READREQ, which enables execution of the MOVE
and COMMREQ functions. READREQ is a one-shot coil, activating once when BE-
GREAD transitions from OFF to ON.
Rung # 3: The MOVEWORD function moves a zero to the CRS word referenced in the
Command Block (see rung #4). This clears the CRS word. This rung also resets the FT
output coil of the COMMREQ Function Block in rung #6.
It is vital that the CRS Status Word be cleared and the COMMREQ fault output coil be
cleared each time before initiating a COMMREQ function.
Rungs # 4-5: The BLKMVINT functions set up the COMMREQ Command Block con-
tents. When these rungs are activated, the constant operands are moved into the
memory beginning at the address indicated in the instruction. The constant operands in
this example are defined in the Establish Read Channel Example in Section 3 of this
chapter.
Rung # 6: The COMMREQ Function Block has 3 input parameters and two output pa-
rameters.
The IN field points to the starting location of the Command Block parameters
(%R00301 in this example).
4
4-37
GFK-1004B Chapter 4 Programming Communications Requests
The SYSID field of the COMMREQ Function Block defines the target rack and slot of
the Ethernet Interface to receive the command data. The first two digits of SYSID
(00 in this example) indicate the rack number, the last two digits (04 in this example)
indicate the slot number of the Ethernet Interface.
The TASK field of the COMMREQ Function Block indicates which mailbox task ID to
use for the specified rack and slot. This field should always be zero (0) for the
Ethernet Interface.
The FT output (CMRQFLT in this example) is turned on (set to 1) if there were
problems preventing the delivery of the Command Block to the Ethernet Interface.
In this case, the other status indicators are not updated for this COMMREQ.
Note
The OK output is not used in this example so that the sample code can
equally apply to a 90-70 or a 90-30 PLC.
Troubleshooting Your Ladder Program
As explained in Section 4 of this chapter, there are several forms of status data which can
be used in your ladder program. The use of the LAN Interface OK bit in the LAN
Interface Status Word was described in the ladder program fragment above. Some of
the status data can be used to troubleshoot your program in its developmental stage.
The two primary sources of this data are the FT Output on the COMMREQ Function
Block and the COMMREQ Status word (CRS word).
FT Output is ON
If after executing a COMMREQ Function, the FT Output is ON, then there is a
programming error in one or more of the following areas.
Invalid rack/slot specified. The module at this rack/slot is unable to receive a
COMMREQ Command Block.
Task ID not valid. (Should be set to 0.)
Data Block length is specified as 0 or greater than 128.
COMMREQ Status Word is Zero (0) and FT Output is OFF
If after executing a COMMREQ function, the CRS word is zero (0) and the FT Output is
OFF, then the Command Block has been sent to the Ethernet Interface, but no status has
been returned yet. If this condition persists, check the PLC fault table for information.
COMMREQ Status Word is Not One (1)
If after executing a COMMREQ function, the CRS word is not one (1) indicating success,
then there were:
Errors in the Command Block (the Channel Command code or parameters), or
For an Establish Read or Write Channel Command, the command parameters were
valid but there was an error in establishing a channel.
If the CRS word does not contain a 1 indicating success, then it contains either a 0 or a
code indicating what error occurred. See Section 4 of this chapter for CRS word error
codes.
4
4-38 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Monitoring the Communications Channel
Once you have a working ladder program, you can use the status data to monitor your
communications activity and take the desired action upon certain events. The primary
indicators of a communications channel are the Channel Status bits: Channel Error bit
and Data Transfer bit. In addition, the CRS word and the DCS words can be used to
more precisely troubleshoot any problems that may occur.
Monitoring the COMMREQ Status Word
It is critical to monitor the CRS word for each COMMREQ function you initiate. First,
zero the associated CRS word before executing the COMMREQ function. Then when
the CRS word becomes non-zero, you know the Ethernet Interface has updated it. If the
CRS word is updated to a one (1), then the Command Block was processed successfully
by the Ethernet Interface. If the CRS word is updated to a value other than 1, then an
error has occurred in processing the Command Block. See Section 4 of this chapter for
CRS word error codes.
Do not use data received from a server until the CRS word for that channel is 1 or the
Data Transfer bit goes to 1.
Monitoring the Channel Error Bit
This bit (normally 0) is the primary indicator for an error on a channel. It indicates any
channel error, fatal or non-fatal. It does not necessarily indicate that the channel is down
(idle). You may want to monitor this bit and simply reinitiate the Read or Write
command if the bit indicates an error. Or you may want to execute the Retrieve Detailed
Channel Status Command to find out if the channel is down and possibly why it went
down. Keep in mind, however, that the status code may change from between the time
the Channel Error bit indicates an error and the time the Retrieve Detailed Channel
Status Command retrieves the code.
The Channel Error bit for a channel is not meaningful until after the Ethernet Interface
updates the CRS word confirming the Read or Write command for that channel. In the
case of an Establish Channel command, the CRS word is updated before the Channel
Error bit is set to 1.
Monitoring the Data Transfer Bit
Typically you will set up a channel to perform repetitive reads or writes. The Data
Transfer bit pulses ( 0 →1 →0) each time there is a successful read or write. This can be
an indicator to the ladder program to move the most recent data to another location.
The Data Transfer bit for a channel is not meaningful until after the Ethernet Interface
updates the CRS word confirming the Read or Write command for that channel.
Do not use data received from a server until the CRS word confirming the Read
command for that channel is 1 or the Data Transfer bit goes to 1. Do not assume that when
the Data Transfer bit goes to 1 that a transfer has just completed during the last scan. The Data
Transfer bit is not closely synchronized in time with the transfer. The bit only indicates
that a transfer has occurred in a past scan. A rising edge on the Data Transfer bit
indicating that a transfer has completed successfully does not guarantee that the next
transfer has not begun or completed.
4
4-39
GFK-1004B Chapter 4 Programming Communications Requests
Sequencing Communications Requests
If the Ethernet Interface receives Command Blocks from the PLC faster than the Inter-
face can process them, the Interface will log an exception event 08, Entry 2=0024 and
will log the PLC Fault Table entry:
“Backplane Communications with PLC Fault; Lost Request”
Only one COMMREQ function per channel can be pending at one time. A COMMREQ
function is pending from the time it is initiated in the ladder program until its CRS word
has been updated to a non-zero value by the Ethernet Interface.
Data Transfers with One Repetition
If your ladder program for issuing COMMREQs is constructed so it does all the follow-
ing, all available TCP connections can quickly be used up.
The number of repetitions (word 9 in an Establish Channel COMMREQ) is set to 1
and a new COMMREQ is issued immediately upon completion of the prior one.
Each successive COMMREQ is directed to the same target device (same IP address).
Each successive COMMREQ is directed to the same channel number.
To avoid using up all TCP connections, set the number of repetitions (COMMREQ word
9) to 2 and set the read/write period (COMMREQ words 10 and 11) to be very large, for
example, 60 seconds. With these parameters the ladder program will issue the first
COMMREQ, wait for the COMMREQ Status (CRS) word to turn to 1, then issue the next
COMMREQ, wait for the CRS word to turn to 1, and so forth.
By interrupting an active channel, you allow the reuse of an existing TCP connection,
while a repetition count of 1 started the time-consuming TCP connection teardown
immediately.
5section level 1
figure bi level 1
table_big level 1
5-1
GFK-1004B
Chapter 5The Station Manager
This chapter describes how to access and use the Station Manager software which re-
sides on the Ethernet Interface. Each command is also defined here. The chapter is di-
vided into three sections.
Section 1. Accessing the Station Manager
Section 2. Using the Station Manager
Section 3. Command Descriptions
The Station Manager is a part of the communications software in the Ethernet Interface.
The Station Manager executes as a background function on the Ethernet controller board
to provide interactive supervisory access to the Ethernet Interface.
The Station Manager is available when the Ethernet Interface is fully operational or
when it is running either the Soft Switch Entry or Field Network Test utilities. The Sta-
tion Manager is not available when running Power-Up Diagnostics or the Loader Utility.
Station Manager Services
The Station Manager provides the following services:
An interactive set of commands to interrogate and control the Ethernet Interface.
Access to observe internal statistics, an exception log, and configuration parameters.
Password security for commands that change the Ethernet Interface parameters or
states.
The Station Manager allows you to monitor the operation of the local station and the
network. If a problem occurs at the local station or on the network, the Station Manager
may be used to pinpoint the source of the problem through the various Monitor com-
mands.
5
5-2 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Section 1: Accessing the Station Manager
The Station Manager on the Ethernet Interface can be accessed in three primary ways:
1. Through the 9–pin serial port on the Ethernet Interface by a GEnet System Manager
(GSM) in Local Station Manager Mode or by an ASCII terminal. See Figure 5-1.
2. Directly over the Ethernet network by a GSM in Network Station Manager Mode.
See Figure 5-2.
3. Remotely over the Ethernet network via another Ethernet Interface with an attached GSM
in Local Station Manager Mode or by an ASCII terminal. This method requires the use
of the REM (Remote) command to access the remote station. See Figure 5-3.
TRANSCEIVER
STATION MANAGER
SERIES 90-70 PLC
ETHERNET
INTERFACE
a45166
RS-232
SERIAL LINK
GEnet SYSTEM MANAGER
in Local Station Manager Mode
(or an ASCII Terminal)
802.3 LAN
Figure 5-1. Station Manager Accessed Locally through the 9–pin Serial Port by a GSM in
Local Station Manager Mode (or an ASCII Terminal)
STATION MANAGER
TRANSCEIVER
SERIES 90-70 PLC
ETHERNET
INTERFACE
a45167
GEnet SYSTEM MANAGER
in Network Station Manager Mode
802.3 LAN
TRANSCEIVER
Figure 5-2. Station Manager Accessed Directly over the Network by a GSM in Network
Station Manager Mode
5
5-3
GFK-1004B Chapter 5 The Station Manager
a45168
TRANSCEIVER
ETHERNET
INTERFACE
STATION MANAGER
SERIES 90-70 PLC
RS-232
SERIAL
LINK
802.3 LAN
GEnet SYSTEM MANAGER
in Local Station Manager Mode
(or an ASCII Terminal)
Must be the REM (Remote)
Command to access Station
Manager with MAC Address
080019010020
MAC Address
080019010020
TRANSCEIVER
STATION MANAGER
SERIES 90-70 PLC
ETHERNET
INTERFACE
Figure 5-3. Station Manager Accessed Remotely over the Network by a GSM in Local
Station Manager Mode using the REM (Remote) Command
Accessing the Station Manager Using the GSM
The Station Manager may be accessed by connecting the Ethernet Interface to a Work-
master or IBM PC Compatible computer running the GSM software in Local or Network
Station Manager mode.
1. Do either A or B below as desired.
A. Local Connection. Connect the COM1 RS–232 serial port on the device running
the GSM to the 9–pin connector on the Ethernet Interface. Refer to Appendix B,
for instructions on how to make the RS–232 cable.
B. Network Connection. Connect the PC network card on the device running the
GSM to the Ethernet Network.
2. Power–up the computer running the GSM into DOS. (See Chapter 3. The GEnet
System Manager for installation of the GSM).
3. Set the PC default directory to the GSM directory, by typing:
C:\> cd gsm
4. Start–up the GSM by typing:
C:\GSM> gsm
5. Once the GSM Main Menu appears, go into the Setup GSM functions to set the
Station Manager Mode to Network or Local.
6. From the GSM Main Menu, cursor to the Access Station Manager function and press
Enter.
A. Local Mode. If you are in Local Mode you will automatically go into the Station
Manager of the locally connected Ethernet Interface.
5
5-4 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Note
When you enter the Local Station Manager or the Local Downloader,
the GSM automatically configures COM1 of the PC as follows:
9600 bits per second
8 data bits
No parity
1 stop bit
COM1 will retain this configuration even after exiting the Local Station
Manager or Local Downloader.
B. Network Mode. If you are in Network Mode, you will be prompted to enter the
Station Name or MAC address of the station you want to access.
Accessing the Station Manager Using an ASCII Terminal
1. Connect a serial cable from the ASCII terminal to the 9–pin connector of the
Ethernet Interface. Refer to Appendix B, for instructions on making the cable.
2. Set up the communication parameters of the terminal as follows:
9600 bits per second
8 data bits
No parity
1 stop bit
3. Press the Enter key to see the Station Manager prompt character.
Remote Operation of the Station Manager
The Station Manager commands can be invoked over the network from other GEnet
devices (other Series 90-70 and Series 90-30 PLC Ethernet Interfaces, GE Fanuc CNC
OSI–Ethernet Interfaces, or Series Six PLC LAN Interfaces) by using the REM com-
mand. When invoked remotely, the Station Manager software processes the command
as if it had been entered from a device attached to the serial port but automatically di-
rects output from the command over the LAN to the station which issued the request.
There is no indication on the local station serial device when a remote command is being
processed. Refer to Figure 5–2 for LAN configurations that use remote Station Manager
operations.
Note
Both the local console and any remote access share the same security
level. See the “LOGIN” and “LOGOUT” commands descriptions.
5
5-5
GFK-1004B Chapter 5 The Station Manager
Section 2: Using the Station Manager
The Station Manager commands are divided into two groups:
Monitor commands
Modify commands
The Monitor commands provide information about the station and the network. Execut-
ing these commands will not affect the operation of the station or the network, and they
are available to anyone using the Station Manager. See Table 5-1 for a list of Monitor
commands.
The Modify commands perform functions that may change the operation of the station
and the network. These commands are secure and may only be executed when the se-
cure level of operation has been selected by “logging in” with the current password.
These commands will be printed in italics. See Table 5-2 for a list of Modify commands.
The complete sets of Monitor commands and Modify commands are available when the
Ethernet Interface is in the fully operational state. Subsets of these commands are avail-
able when in the Soft Switch Entry and Field Network Test Utilities.
The Station Manager is a “background” task. It only executes when communication pro-
cessing is not occurring. Because of this, the command response time is sensitive to the
communication load of the station––the greater the load, the longer it takes for the com-
mands to execute.
5
5-6 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Using the Monitor Commands
All of the Monitor commands can be executed from either the Monitor “>” prompt or
the Modify ”=” prompt. To display a list of the Monitor commands on the screen, type:
HELP <RET> or
? <RET>
The following table provides a brief description of the Monitor commands.
Table 5-1. Monitor Commands
Command Description
?Display list of commands
bps Display serial port data rate
chan-
nel Display the status of a communication channel
date Display current date
exs Display Extended Status buffer (Unused by the TCP/IP Ethernet Interface.)
help Display list of commands
log Display Exception log
login Login for Modify mode
ltime Display login timeout
node Display sign-on message
prog Display the name of the PLC program in the CPU
show Display a configuration parameter’s value, or list the configuration
parameters for a task(s)
sosw Display current Soft Switch data
stat Display task(s) status
tally Display task(s) tallies
time Display current time
For most commands, simply enter the command and press Enter. Some commands re-
quire additional information to be entered along with the command. Those arguments
should be separated from the command and from each other by one or more spaces.
The Command Descriptions section in this chapter provides a complete description of
each command.
The LOGIN command is required to access the Modify commands. To execute the
LOGIN command you must know the current password.
5
5-7
GFK-1004B Chapter 5 The Station Manager
Using the Monitor Commands to Troubleshoot the Network
There are three Monitor commands that are especially useful to troubleshoot the net-
work:
The NODE command
The EXS command
The LOG command
The TALLY command
NODE Command: The NODE command displays the TCP/IP Ethernet sign-on mes-
sage, identifying the node by its MAC and IP addresses and identifying the resident
firmware and software.
EXS Command: The EXS command displays the Extended Status Buffer. This buffer
maintains information about COMMREQs issued to this Ethernet Interface from the
PLC ladder program of the local station.
LOG Command: The LOG command displays a log of exception conditions occurring at
the local station. The events are counted, time stamped, and differentiated by an error
code.
TALLY Command: The TALLY command displays counts of transactions of the specific
tasks.
Using the Modify Commands
To use any of the Modify commands you must obtain the modify ”=” prompt using the
LOGIN command. To do this you must know the current password. The default pass-
word is “system” (lower case characters).
To log in, type from the “>” prompt:
LOGIN <RET>
The password prompt will then be displayed.
Password:
Type in the current password and press Enter. If the entered password matches the current
password for the station, the modify “= ” prompt is displayed. The password is case sensitive.
One may execute all Monitor and Modify commands from the Modify “=” prompt. If
no commands are executed within 10 minutes, the Modify login will time-out and you
will have to login again. This 10 minute timeout between commands can be changed if
desired by using the CHLTIME command.
Note
The security feature is intended to prevent inadvertent misuse of the
Modify commands. It is not a foolproof mechanism to prevent
unauthorized changes. For the greatest protection, restrict the number
of people who know the password, restrict access to the Station
Manager terminal, and always log off when you leave the Station
Manager.
5
5-8 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
To list the Monitor commands and Modify commands on the screen, type:
HELP <RET> or
? <RET>
The following table provides a brief description of the Modify commands.
Table 5-2. Modify Commands
Command Description
chbps Change serial port data rate
chdate Change date (Not recommended if PLC CPU is configured
properly.)
chltime Change login timeout
chsosw Change Soft Switch data (Not recommended .)
chtime Change time (Not recommended if PLC CPU is
configured properly.)
clear Clear Extended Status buffer, Exception Log,Tallies, or Heap
clsosw Clear Soft Switch values on TCP/IP Ethernet Interface (Not
recommended.)
load Force TCP/IP Ethernet Interface to be loaded
logout Exit modify mode
net Disable/Enable node from network
ok Turns on STATUS OK LED
ping Issues ICMP echo request
rem Send command to remote station
report Report test results
repp Report ping results
restart Restart the TCP/IP Ethernet Inter face
stopp Stop ping command
stopt Stop test command
test Send test commands to station(s)
trace Turn on specific task trace flags
Date and Time
The Station Manager provides commands to examine the date and time. Any time the
TCP/IP Ethernet Interface is restarted or power to it is cycled, it will attempt to read the
date and time from the PLC CPU. If this fails, the time reverts to midnight and the date
to January 1, 1989; it is only in the case of failure to read date/time from the CPU that
you must set it using the Station Manager. If accurate time stamp information is to be
generated in the Exception Log, the system date and time must be set using the Station
Manager.
Station Manager Command Syntax
The Command Descriptions section which follows provides an alphabetical listing of the
commands. Each entry describes the input and output for each command.
All commands have the format of a command followed by a variable number of argu-
ments separated by spaces. Details about the arguments are discussed with each com-
5
5-9
GFK-1004B Chapter 5 The Station Manager
mand. All arguments to the commands, will be automatically converted to all lower case
characters unless they are enclosed in double quotation marks (e.g., “A”).
Task Identification
Several commands refer to “tasks” or subsystems of the operating software. Each task
has a unique identifying letter which is used to select the desired task or tasks. The fol-
lowing table shows the task identifiers and their associated tasks.
Table 5-3. Task Identifiers
Identifier Task
bSystem Memory
cPLC Driver
f ARP
hChannel API
iIP Layer
j ICMP
lData Link Layer
vSRTP Server Agent
wTCP Layer
Display Data Representation
The data that is displayed by the Station Manager is formatted in one of several ways
depending on the type of data being input or output.
Note
The Ethernet Interface has a limited output buffer for storing Station
Manager command results. If a command’s output exceeds this size,
part of the command output will be lost, and will not be displayed.
Numeric Values
Numeric values are displayed as decimal values with the hexadecimal equivalent
printed in parenthesis beside it. An exception is baud rate which are printed only in dec-
imal. Hexadecimal values are represented with a “H” as their last character.
An example of numeric output is shown below.
bbuff4 = 2140 (085cH)
When numeric values are entered, they may be entered as either a decimal value or as a
hexadecimal value. Hexadecimal values must be entered using the trailing “H” (either
upper or lower case) as their last character.
5
5-10 TCP/IP Ethernet Communications User’s Manual – January 1996 GFK-1004B
Byte String Values
Byte strings represent each successive byte as a pair of hexadecimal digits enclosed in
double angle brackets (<<...>>). An examples of a byte string output is shown below.
MAC address = <<080019010842>>
IP Address
IP addresses are displayed and entered in dotted decimal format. An example is shown
below:
= ping 3.4.5.6 10
<<< Ping Results >>>
Command: ping 3.4.5.6 10 100 64
Sent = 10, Received = 10, No Timely Response = 0
Late/Stray Response = 0
Round-trip (ms) min/avg/max 0/1/10
5
5-11
GFK-1004B Chapter 5 The Station Manager
Station Manager in Utility Programs
The Ethernet Interface has two utility functions provided as a part of the PROM-based
software. These utilities allow selected station management functions to be performed,
even when no operating software is loaded. This allows the Ethernet Interface hard-
ware and the network to be verified without requiring that any software be loaded into
the Ethernet Interface.
Soft Switch Entry Utility
The Ethernet Interface stores its Soft Switch data in an EEPROM. If Soft Switches have
not been configured through Logicmaster 90-70 and the values in the EEPROM are in-
valid, the Soft Switch Entry utility is entered. Also, when certain other faults are de-
tected, control will revert to the Soft Switch Entry utility.
Caution
The Soft Switch parameters are critical to proper startup of the
Ethernet Interface. Improper settings of Soft Switch values can
prevent the station from functioning with the PLC, from being loaded,
or from being accessible to other stations on the network.
The Soft Switch Entry utility is entered if the data in the Soft Switches
are determined to be invalid on power-up or restart of the Ethernet
Interface, or if certain other faults occur.
The Soft Switch Entry utility runs a subset of the Station Manager commands. It pro-
vides a unique prompt, an asterisk (“*”). The Station Manager commands shown in the
following table can be used while in the Soft Switch Entry utility. Some of the com-
mands have restrictions due to the limited services available in this utility.
All commands in the Soft Switch Entry utility are accessible at the initial security level. It
is not necessary to login to use the Modify commands while in the Soft Switch Entry util-
ity.
A typical initialization message from the Soft Switch Entry utility is shown below:
IC697 PLC Factory LAN Interface
Copyright (c) 1990-1995. All rights reserved.
PROM Version 2.00 (xxAx) Ethernet
MAC address = <<08001901001f>> MAC default = <<08001901001f>>
EM7A2
<<< Soft Switch Entry Utility >>>
Soft Switch Values Not Defined
*
Just before the “*” prompt is printed, the reason for entry into the Soft Switch Entry util-
ity is printed. Some examples of entry reasons are: soft switch values not defined,