T1H–EBC(100) - Host Engineering

T1H–EBC(100) - Host Engineering
Terminator I/O
Ethernet Base Controller
Manual
Manual Number T1H–EBC–M
WARNING
Thank you for purchasing automation equipment from Automationdirect.com, doing business as
AutomationDirect. We want your new DirectLOGIC automation equipment to operate safely. Anyone who installs
or uses this equipment should read this publication (and any other relevant publications) before installing or operating
the equipment.
To minimize the risk of potential safety problems, you should follow all applicable local and national codes that regulate
the installation and operation of your equipment. These codes vary from area to area and usually change with time. It is
your responsibility to determine which codes should be followed, and to verify that the equipment, installation, and
operation are in compliance with the latest revision of these codes.
At a minimum, you should follow all applicable sections of the National Fire Code, National Electrical Code, and the
codes of the National Electrical Manufacturer’s Association (NEMA). There may be local regulatory or government
offices that can also help determine which codes and standards are necessary for safe installation and operation.
Equipment damage or serious injury to personnel can result from the failure to follow all applicable codes and
standards. We do not guarantee the products described in this publication are suitable for your particular application,
nor do we assume any responsibility for your product design, installation, or operation.
Our products are not fault–tolerant and are not designed, manufactured or intended for use or resale as on–line control
equipment in hazardous environments requiring fail–safe performance, such as in the operation of nuclear facilities,
aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in
which the failure of the product could lead directly to death, personal injury, or severe physical or environmental
damage (”High Risk Activities”). AutomationDirect specifically disclaims any expressed or implied warranty of fitness
for High Risk Activities.
For additional warranty and safety information, see the Terms and Conditions section of our Desk Reference. If you
have any questions concerning the installation or operation of this equipment, or if you need additional information,
please call us at 770–844–4200.
This publication is based on information that was available at the time it was printed. At AutomationDirect we
constantly strive to improve our products and services, so we reserve the right to make changes to the products and/or
publications at any time without notice and without any obligation. This publication may also discuss features that may
not be available in certain revisions of the product.
Trademarks
This publication may contain references to products produced and/or offered by other companies. The product and
company names may be trademarked and are the sole property of their respective owners. AutomationDirect
disclaims any proprietary interest in the marks and names of others.
Copyright 2004, Automationdirect.com Incorporated
All Rights Reserved
No part of this manual shall be copied, reproduced, or transmitted in any way without the prior, written consent of
Automationdirect.com Incorporated. AutomationDirect retains the exclusive rights to all information included in
this document.
AVERTISSEMENT
Nous vous remercions d’avoir acheté l’équipement d’automatisation de Automationdirect.comE, en faisant des affaires
comme AutomationDirect. Nous tenons à ce que votre nouvel équipement d’automatisation DirectLOGIC fonctionne en
toute sécurité. Toute personne qui installe ou utilise cet équipement doit lire la présente publication (et toutes les autres
publications pertinentes) avant de l’installer ou de l’utiliser.
Afin de réduire au minimum le risque d’éventuels problèmes de sécurité, vous devez respecter tous les codes locaux et
nationaux applicables régissant l’installation et le fonctionnement de votre équipement. Ces codes diffèrent d’une région à
l’autre et, habituellement, évoluent au fil du temps. Il vous incombe de déterminer les codes à respecter et de vous assurer
que l’équipement, l’installation et le fonctionnement sont conformes aux exigences de la version la plus récente de ces
codes.
Vous devez, à tout le moins, respecter toutes les sections applicables du Code national de prévention des incendies, du
Code national de l’électricité et des codes de la National Electrical Manufacturer’s Association (NEMA). Des organismes de
réglementation ou des services gouvernementaux locaux peuvent également vous aider à déterminer les codes ainsi que
les normes à respecter pour assurer une installation et un fonctionnement sûrs.
L’omission de respecter la totalité des codes et des normes applicables peut entraîner des dommages à l’équipement ou
causer de graves blessures au personnel. Nous ne garantissons pas que les produits décrits dans cette publication
conviennent à votre application particulière et nous n’assumons aucune responsabilité à l’égard de la conception, de
l’installation ou du fonctionnement de votre produit.
Nos produits ne sont pas insensibles aux défaillances et ne sont ni conçus ni fabriqués pour l’utilisation ou la revente en tant
qu’équipement de commande en ligne dans des environnements dangereux nécessitant une sécurité absolue, par
exemple, l’exploitation d’installations nucléaires, les systèmes de navigation aérienne ou de communication, le contrôle de
la circulation aérienne, les équipements de survie ou les systèmes d’armes, pour lesquels la défaillance du produit peut
provoquer la mort, des blessures corporelles ou de graves dommages matériels ou environnementaux (”activités à risque
élevé”). La société AutomationDirect nie toute garantie expresse ou implicite d’aptitude à l’emploi en ce qui a trait aux
activités à risque élevé.
Pour des renseignements additionnels touchant la garantie et la sécurité, veuillez consulter la section Modalités et
conditions de notre documentation. Si vous avez des questions au sujet de l’installation ou du fonctionnement de cet
équipement, ou encore si vous avez besoin de renseignements supplémentaires, n’hésitez pas à nous téléphoner au
770–844–4200.
Cette publication s’appuie sur l’information qui était disponible au moment de l’impression. À la société AutomationDirect,
nous nous efforçons constamment d’améliorer nos produits et services. C’est pourquoi nous nous réservons le droit
d’apporter des modifications aux produits ou aux publications en tout temps, sans préavis ni quelque obligation que ce soit.
La présente publication peut aussi porter sur des caractéristiques susceptibles de ne pas être offertes dans certaines
versions révisées du produit.
Marques de commerce
La présente publication peut contenir des références à des produits fabriqués ou offerts par d’autres entreprises. Les
désignations des produits et des entreprises peuvent être des marques de commerce et appartiennent exclusivement à
leurs propriétaires respectifs. AutomationDirectE nie tout intérêt dans les autres marques et désignations.
Copyright 2004, Automationdirect.comE Incorporated
Tous droits réservés
Nulle partie de ce manuel ne doit être copiée, reproduite ou transmise de quelque façon que ce soit sans le consentement
préalable écrit de la société Automationdirect.comE Incorporated. AutomationDirect conserve les droits exclusifs à
l’égard de tous les renseignements contenus dans le présent document.
1
Manual Revisions
If you contact us in reference to this manual, be sure and include the revision number.
Title: Terminator Installation and I/O Manual
Manual Number: T1H–EBC–M
Edition/Rev
Date
Description of Changes
Original
11/01
original issue
2nd Edition
08/04
added T1H–EBC100, NetEdit3
HTML Configuration
Table of Contents
ii
Chapter 1: Introduction
Manual Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Reference Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Who Should Read This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Key Topics for Each Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Base Controller Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Values Stored in Cache Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Industry Standard Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1H–EBC/T1H–EBC100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS–232C Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–2
1–2
1–2
1–2
1–2
1–3
1–4
1–4
1–5
1–5
1–5
Chapter 2: Installation and Setup
Installing the Ethernet Base Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2
Setting the Node Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Several Methods for Setting Node Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Node Address Using the Rotary Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Node Address with Software Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10BaseT / 100BaseT Network Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10BaseT/100BaseTconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port (RS–232) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum 10BaseT / 100BaseT Cable Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–3
2–3
2–3
2–3
2–4
2–4
2–5
2–5
T1H–EBC Ethernet Base Controller Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–6
T1H–EBC100 Ethernet Base Controller Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–7
LED Indicators and Hot Swapping I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check External 24VDC Wiring Before Hot Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hot Swap: I/O Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–8
2–9
2–9
2–10
Chapter 3: Configuring the T1H–EBC(100) Using NetEdit3
NetEdit3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing NetEdit3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Launching NetEdit3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The NetEdit3 Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Network Protocol Support to the NetEdit3 PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using NetEdit3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–2
3–2
3–3
3–3
3–4
3–5
Ethernet Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module Type, IP Address and ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module Info>General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Module Info>Ethernet Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EBC Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EBCSettings>Configuration>General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EBC Settings>Configuration>Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EBC Settings>Utils>Show Base Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EBC Settings>Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FileMenu>Live Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F / B / C Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locating the MAC Address Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–5
3–6
3–6
3–7
3–7
3–7
3–8
3–8
3–9
3–9
3–10
3–10
3–11
3–11
Chapter 4: MODBUSr TCP/IP for T1H–EBC100
MODBUS TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Client / Server Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported MODBUS Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–2
4–2
4–2
4–4
MODBUS 584/984 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–5
T1H–EBC100 System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–6
Current / Last State Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–9
Extended Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–9
Analog Input Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–10
Analog Output Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–10
Chapter 5: T1H–EBC100 DHCP & HTML Configuration
T1H–EBC100 DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5–2
Disabling DHCP and Assigning a Static IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5–2
Using HTML Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the T1H–EBC100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5–3
5–3
Appendix A: Using the T1H–EBC(100) with Think & DO
Mapping T1H–EBC(100) I/O Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Launching Connectivity Center Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the EBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping I/O Points to Data Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hot Swap Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hot Swap: Automatic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hot Swap: Manual Mode Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A–2
A–2
A–2
A–2
A–3
A–3
A–3
Analog I/O Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A–4
I/O Module Status Word / Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A–4
Using EZTouch/EZText Panel with the RJ–12 Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Operator Interface Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Monitor I/O to Verify Panel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A–5
A–5
A–6
Appendix B: Using the T1H–EBC(100) with
KEPDirect OPC Server
Introduction to KEPDirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DDE Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KEPDirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KEPDirect Project: Adding and Configuring a Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting the Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting the Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Server Writes Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving the New Channel Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Multiple Channels in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KEPDirect Project: Adding and Configuring a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting the Device Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Device Timeout Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic OPC Tag Database Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving the New Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KEPDirect Project: Adding Tags to the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Defined Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a User Define Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1H–EBC(100) I/O Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1H–EBC(100) I/O Addressing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Analog Output Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B–2
B–2
B–2
B–2
B–4
B–4
B–4
B–5
B–5
B–6
B–7
B–7
B–8
B–8
B–8
B–9
B–10
B–10
B–11
B–11
B–13
B–14
B–14
B–15
Appendix C: Using the KEPDirect OPC Quick Client
Creating a KEPDirect Quick Client Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the Client to the OPC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Client Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting a Group Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Item Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the RJ12 Serial Port in ASCII Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C–2
C–2
C–2
C–3
C–4
C–5
Introduction
In This Chapter. . . .
— Manual Overview
— Ethernet Base Controller Overview
11
1–2
Introduction
Introduction
Manual Overview
Overview of this
Manual
This manual describes the installation and
operation of the Ethernet Base
Controller (EBC). You will find the
necessary information for configuring the
T1H–EBC or T1H–EBC100, installing the
module, and connecting the EBC to a
10Base-T or 100BaseT Ethernet network.
In this manual, the EBC designation is
used when the subject applies to both the
T1H–EBC and T1H–EBC100. Otherwise,
the specific part number will be listed.
Other Reference
Materials
You may find other technical manuals useful for your application. For technical
information related to your PC–based control software, your PC or other network
masters, please refer to the appropriate manual for that product.
You will find this manual helpful for setup and installation if you have chosen to use
the following:
• Network master – PC-based Control with embedded Ethernet I/O
drivers, KEPDirect EBC I/O Server or DirectLogic PLCs/WinPLC using
the Ethernet Remote Master (ERM) module
• Automationdirect Terminator I/O
Who Should Read
This Manual
A familiarity with Ethernet communications and with the setup and installation of
industrial controls is helpful. An understanding of electrical codes is essential.
Installation and
Safety Guidelines
Technical Support
We strive to make our manuals the best in the industry. We rely on your feedback to
let us know if we are reaching our goal. If you cannot find the solution to your
particular application, or, if for any reason you need additional technical assistance,
please call us at
770–844–4200.
Our technical support group is glad to work with you in answering your questions.
They are available weekdays from 9:00 a.m. to 6:00 p.m. Eastern Time. We
encourage you to visit our site on the worldwide web where you can find technical
and nontechnical information about our products and our company.
http://www.automationdirect.com.
If you have a comment or question about any of our products, services, or manuals,
please fill out and return the ‘Suggestions’ card that was shipped with this manual.
1–3
Introduction
When you see the “exclamation mark” icon in the left-hand margin, the paragraph to
its immediate right will be a warning. This information could prevent injury, loss of
property, or even death.
Key Topics for
Each Chapter
The beginning of each chapter will list the
key topics that can be found in that chapter.
Introduction
When you see the “notepad” icon in the left-hand margin, the paragraph to its
immediate right will be a special note.
1
Installation and
Safety Guidelines
1–4
Introduction
Introduction
Ethernet Base Controller Overview
The Ethernet Base Controllers provide a low-cost, high-performance Ethernet link
between a network master controller and an Automationdirect Terminator I/O slave
system. Network masters include the DL205, DL405 DirectLogic PLCs and
WinPLCs using the Ethernet Remote Master module (ERM), and PCs using
PC–based control software that includes embedded Ethernet I/O drivers or through
a compatible OPC server. The T1H–EBC100 also supports the MODBUS TCP/IP
protocol.
The Ethernet Base Controller serves as an interface between the master control
system and the Terminator I/O modules. The control function is performed by the
master controller, not the EBC slave. The EBC is positioned immediately to the right
of the first power supply and communicates across the backplane to input and output
modules. The function of the EBC is to:
• process analog and digital input signals
• format the I/O signals to conform to the Ethernet standard
• transmit the signals to the network master
• receive and translate output signals from the network master
• distribute the output signals to the appropriate output module in the
base
Installation and
Safety Guidelines
I/O Values Stored
in Cache Memory
The EBC module continually scans all I/O and stores the most recent values in
cache memory. The cache memory contents are available to the master controller
as a block of data or by individual slot location. The EBC reads all channels of digital
and analog modules on each scan.
Typically, the network master will request all input and output values at the same time
from the EBC. The EBC passes the cache memory values for all channels of all input
and output modules. By using this method, very fast response times can be
achieved by the network master control system. Various master controllers with
EBC slaves are shown below.
Example EBC Systems: Various Masters with EBC Slaves
MODBUS TCP/IP Masters
(T1H–EBC100)
DirectLogic PLC/
WinPLC with ERM
OR
OR
T1H–EBC
UDP/IP, IPX
10Mbps
PC–based Control System
Operator Interface
Serial
Ethernet
Hub
EBC
T1H–EBC100
TCP/IP, UDP/IP, IPX
MODBUS TCP/IP
10/100Mbps
EBC
EBC
1–5
Introduction
Industry Standard
Ethernet
WARNING: For deterministic Ethernet communication you must use a dedicated
network of EBC modules connected to your master control system. The EBC
modules and the master controller must be the only devices on the network.
T1H–EBC/
T1H–EBC100
The EBC installs to the right of the
first power supply (see chapter 2
for basic installation steps). For
further information about installing
power supplies and I/O modules,
consult the Terminator I/O
Installation and I/O Manual
(T1K–INST–M).
RS–232C
Serial Port
An RJ12 RS232C serial port
on-board the EBC module allows
serial communication to an
operator interface device or other
serial device. See your master
controller
documentation
to
determine whether this EBC
feature is supported.
Installation and
Safety Guidelines
Important Note: The T1H–EBC100 is configured at the factory to look for a DHCP
(Dynamic Host Configuration Protocol) server at power up. Refer to Chapter 5 for
information on DHCP.
Introduction
The T1H–EBC module supports industry standard 10Base-T Ethernet communications.
It allows up to10Mbps transfer rates between your master controller and and your I/O.
The T1H–EBC100 module supports industry standard 10/100Base-T Ethernet
communications. It allows up to100Mbps transfer rates between your master controller
and your I/O.
Installation and Setup
12
In This Chapter. . . .
— Installing the Ethernet Base Controller
— Setting the Node Address
— 10BaseT / 100BaseT Network Cabling
— Maximum 10BaseT / 100BaseT Cable Length
— Specifications
— LED Indicators and Hot Swapping I/O Modules
— Ethernet Standards
2–2
Installation and Setup
Installing the Ethernet Base Controller
Installation
and Setup
The EBC installs to the right of the first power supply. To mount the module on the
DIN rail, follow steps 1 through 3 below.
1. Push in the locking tab on the bottom of the module.
2. Hook the upper tab over the upper flange of the DIN rail.
3. Tilt the module toward the DIN rail until it snaps securely into place.
Note: Do not force the base controller on the DIN rail. Due to
slight size variations in different manufacturers’ DIN rail, it may be
necessary to first unlock the locking tab, rotate the module into
place, then latch the locking tab.
Installation and
Safety Guidelines
Assure that power wiring is not connected.
When the module is securely attached to the DIN rail, push the module toward the
power supply until the connectors are joined and the release arm of the EBC has
clamped the two modules together.
Continue to add I/O modules to the right of the EBC as necessary for your
application. More information about power wiring and power budgeting is available
in the Terminator I/O Installation Manual, T1K–INST–M.
2–3
Installation and Setup
Setting the Node Address
Each Ethernet Base Controller residing on a network must have a Node Address,
and each Node Address must be unique. Duplicate Node Addresses on the same
network will cause unpredictable results and must be avoided.
Setting the
Node Address
Using the Rotary
Switches
Two rotary switches, each labeled 0 – 9, are located on the face of the EBC. Use a
small screwdriver to set the switches to a two-digit number.
The upper switch sets the tens
position and the lower switch sets
the ones position. Setting the
upper switch to 1 and the lower
switch to 4 yields a Node Address
of 14.
Do not use Node Address “0” for
communications. Node Address
“0” is used only to allow
communications with a PC while
changing the Node Address
(Module ID) in software. If the
rotary switches are set to a
number greater than 0, the
software tools are disabled from
setting the Node Address.
NOTE: The rotary switch settings are read only at powerup. You must cycle
power if you change the rotary switches. If you change the rotary switches and cycle
power, the rotary switch setting will override any previous software setting.
Setting Node
Address with
Software Tool
Software changes to the Node Address do not require cycling power. To set the
Node Address using one of the available software tools, do the following:
• Check to be sure both rotary switches are set to the “0” position
• Connect module to the Ethernet network
• Apply power
• Link to the module and change the Node Address using the software of
your choice. Remember to “update” the module before exiting the software.
Installation and
Safety Guidelines
There are several methods for setting the Node Address:
• The rotary switches on the face of the EBC module
• The NetEdit3 software utility (described in Chapter 3)
• HTML Confguration (after IP address is assigned to module using
NetEdit3; described in Chapter 5)
• The software utility in your PC-based Control software
(if a utility is provided)
Installation
and Setup
Several Methods
for Setting Node
Address
2–4
Installation and Setup
10BaseT / 100BaseT Network Cabling
The T1H–EBC module supports the Ethernet 10BaseT standard. The
T1H–EBC100 module supports the Ethernet 10/100BaseT standard. The standards
call for twisted pairs of copper wire conductors.
Diagnostic LEDs
Installation
and Setup
RJ12
Serial
Port
RS232
Rotary Switches
RJ45
for
10BaseT
Installation and
Safety Guidelines
10BaseT/100BaseT The EBC has an eight-pin modular jack that accepts RJ45 connector plugs. UTP
(Unshielded Twisted-Pair) cable is rated according to its data-carrying ability
connections
(bandwidth) and is given a “category” number. We strongly recommend using a
Category 5 (CAT5) cable for all Ethernet 10BaseT/100BaseT connections. For
convenient and reliable networking, we recommend that you purchase
commercially manufactured cables (cables with connectors already attached).
To connect an EBC (or PC) to a hub or repeater, use a patch cable (sometimes
called a straight-through cable). The cable used to connect a PC directly to an EBC
or to connect two hubs is referred to as a crossover cable. Some hubs provide a
crossover port which eliminates the need for a crossover cable.
Crossover Cable
Patch (Straight–through) Cable
EBC
10BaseT/100BaseT
1 2 3 4 5 6 78
8-pin RJ45 Connector
(8P8C)
TD+ 1
TD– 2
RD+ 3
4
5
RD– 6
7
8
RJ45
OR/WHT
OR
GRN/WHT
BLU
BLU/WHT
GRN
BRN/WHT
BRN
OR/WHT
OR
GRN/WHT
BLU
BLU/WHT
GRN
BRN/WHT
BRN
1
2
3
4
5
6
7
8
HUB
EBC
RD+
RD–
TD+
TD+ 1
TD– 2
RD+ 3
4
5
RD– 6
7
8
TD–
RJ45
OR/WHT
OR
GRN/WHT
GRN
GRN/WHT
GRN
OR/WHT
OR
RJ45
This diagram illustrates the standard wire positions in the RJ45 connector.
We recommend that you use only Category 5, UTP cable.
PC
1
2
3
4
5
6
7
8
TD+
TD–
RD+
RD–
RJ45
2–5
Installation and Setup
Serial Port
The Serial Port on the EBC can be used to
communicate with operator interfaces or
ASCII devices. The T1H–EBC100 also
supports MODBUS RTU serial protocol.
1234 56
Serial Port
(RS–232)
Use Automationdirect.com cable Part
Number D2–DSCBL to connect your PC
to the RJ12 Serial Port.
1 2 3 4 5 6
Serial Port Pinout
Pin
Signal
0V
2
+5V
3
RXD
4
TXD
5
RTS
6
CTS
Installation
and Setup
1
Maximum 10BaseT / 100BaseT Cable Length
The maximum distance per 10BaseT/100BaseT cable segment is 100 meters or
328 feet. Repeaters extend the distance. Each cable segment attached to a repeater can be
100 meters long. Two repeaters connected together extend the total range to 300 meters.
Installation and
Safety Guidelines
2–6
Installation and Setup
T1H–EBC Specifications
Installation
and Setup
T1H–EBC Ethernet Base Controller
Module Type
Ethernet slave
Communications
10BaseT
Auto-configuring
I/O type/position automatically identified during
power-up
Ethernet Protocols
UDP/IP, IPX
Ethernet Port
RJ45
Node Address
1 to 99 (decimal)
set by rotary switches or software
(0 used for setting address via software only)
Link Distance
100 meters (328 feet)
Data Transfer Rate
10Mbps
LED Indicators
MODULE GOOD (green):
On = module passed diagnostic check
during last power-up
Fast blink = configured I/O module no
longer reporting
(see auto-configuring, above)
Slow blink = unconfigured I/O module
added to system
(see auto-configuring, above)
LINK GOOD (green):
On = 10Base-T link pulses are being
received
ACTIVITY (red):
On= Ethernet network activity detected
ERROR (red):
On = watchdog timer timeout represents
hardware, communications, or network
fault; power-on reset or reset within
master device software
Installation and
Safety Guidelines
Note: All indicators re-initialize
during power-up.
Serial Communications Port
RJ12, RS232C K–Sequence protocol, ASCII
(not functional when used with H2–ERM / H4–ERM)
Base Power
Requirement
350mA @ 5VDC
General Specifications
Installation Requirements
mounts to right of first power supply
Operating Temperature
32° F to 131° F (0° C to 55° C)
Storage Temperature
–4° F to 158° F (–20° C to 70° C)
Relative Humidity
5 to 95% (non-condensing)
Environmental Air
No corrosive gases, pollution level = 2
(UL 840)
Vibration
MIL STD 810C 514.2
Shock
MIL STD 810C 516.2
Noise Immunity
NEMA ICS3–304
Impulse noise 1us, 1000V
FCC class A
RFI (144MHz, 430MHz, 10W, 10cm)
2–7
Installation and Setup
T1H–EBC100 Specifications
T1H–EBC100 Ethernet Base Controller
10/100BaseT
Auto-configuration
I/O type/position automatically identified during
power-up
IP Configuration
–Obtain an IP address from a DHCP Server automatically at power–up (Default);
–Dedicated IP address using NetEdit3 or HTML configuration
Ethernet Protocols
TCP/IP, UDP/IP, IPX, MODBUS TCP/IP
Ethernet Port
RJ45
Node Address
1 to 99 (decimal)
set by rotary switches or software
(0 used for setting address via software only)
Link Distance
100 meters (328 feet)
Data Transfer Rate
10/100Mbps
LED Indicators
MODULE GOOD (green):
On = module passed diagnostic check
during last power-up
Fast blink = configured I/O module no
longer reporting
(see auto-configuring, above)
Slow blink = unconfigured I/O module
added to system
(see auto-configuring, above)
LINK/ACTIVITY (green):
On= Ethernet network activity detected
100MBIT (green):
On= Ethernet activity is auto–detected at 100bps
Off = (with LINK/ACTIVITY On) Ethernet activity
is auto–detected at 10Mbps
ERROR (red):
On = watchdog timer timeout represents
hardware, communications, or network
fault; power-on reset or reset within
master device software
SERIAL TX (green):
On= EBC RJ12 serial port is transmitting
SERIAL RX (green):
On= EBC RJ12 serial port is receiving
Note: All indicators re-initialize
during power-up.
Serial Communications Port
RJ12, RS232C K–Sequence protocol, ASCII,
MODBUS RTU serial
(not functional when used with H2–ERM / H4–ERM at
this time)
Base Power
Requirement
350mA @ 5VDC
General Specifications
Installation Requirements
mounts to right of first power supply
Operating Temperature
32° F to 131° F (0° C to 55° C)
Storage Temperature
–4° F to 158° F (–20° C to 70° C)
Relative Humidity
5 to 95% (non-condensing)
Environmental Air
No corrosive gases, pollution level = 2
(UL 840)
Vibration
MIL STD 810C 514.2
Shock
MIL STD 810C 516.2
Noise Immunity
NEMA ICS3–304
Impulse noise 1us, 1000V
FCC class A
RFI (144MHz, 430MHz, 10W, 10cm)
Installation and
Safety Guidelines
Ethernet slave
Communications
Installation
and Setup
Module Type
2–8
Installation and Setup
LED Indicators and Hot Swapping I/O Modules
The “Hot Swap” feature allows Terminator I/O modules to be replaced with
Terminator I/O system power ON. Be careful not to touch the terminals with your
hands or any conductive material to avoid the risk of personal injury or equipment
damaged. Always remove power if it is equally convenient to do so.
Installation and
Safety Guidelines
Installation
and Setup
WARNING: Only authorized personnel fully familiar with all aspects of the
application should replace an I/O module with system power ON.
LED Indicators when Hot Swapping an I/O Module
2–9
Installation and Setup
Check External
24VDC Wiring
Before Hot
Swapping
Before “Hot Swapping” an analog I/O module or a DC output module in a
Terminator I/O system, make sure that each of the analog I/O and DC output
module’s 24VDC and 0VDC base terminals are wired directly to the external
power supply individually (see diagram below). If the external 24VDC / 0VDC is
jumpered from base to base in a daisy chain fashion, and an analog I/O or DC output
module is removed from its base, the risk of disconnecting the external 24VDC to the
subsequent I/O modules exists.
Installation
and Setup
Do not jumper
modules together
creating 24VDC
bus for Hot Swap.
Wire each analog I/O and DC
output module independently
to the external power supply.
The following steps explain how to “Hot Swap” an I/O module.
1. Remove I/O module from base. (If necessary, refer to the Terminator I/O
Installation & I/O Manual for steps on removing an I/O module).
2. The EBC Module Good LED will begin to fast blink.
3. Install a new I/O module with the exactly the same part number.
4. Verify that the EBC LEDs have returned to normal.
Installation and
Safety Guidelines
Hot Swap:
I/O Module
Replacement
2–10
Installation and Setup
Installation and
Safety Guidelines
Installation
and Setup
Ethernet Standards
Various institutes and committees have been involved in establishing Ethernet data
communication standards. These specification standards assure Ethernet network
compatibility for products from a broad variety of manufacturers.
The EBC module complies with American National Standards Institute (ANSI) and
Institute of Electrical and Electronic Engineers standard ANSI/IEEE 802.3, Carrier
Sense Multiple Access with Collision Detection (CSMA/CD) Access Methods and
Physical Layer Specifications. This standard has been adopted by the International
Organization for Standardization (ISO) as document ISO/IEC 8802–3.
The Electronic Industries Association (EIA) and Telecommunications Industries
Commercial Building Telecommunications Wiring Standard designated
EIA/TIA–568A defines implementation of 10Base-T (twisted pair) Ethernet
communications.
The same two organizations produced EIA/TIA TSB40–Additional Transmission
Specifications for Unshielded Twisted-Pair Connecting Hardware. The purpose of
this document is to specify transmission performance requirements and connecting
hardware requirements.
Configuring the
T1H–EBC(100)
Using NetEdit3
In This Chapter. . . .
— NetEdit3 Software
— Using NetEdit3
— Locating the MAC Address Label
3
3–2
Using NetEdit3
NetEdit3 Software
NetEdit3 is a software utility which can be used to set network identifiers (Module ID
or IP Address), configure the EBC serial port, perform diagnostic and
troubleshooting tasks and upgrade the firmware in the EBC module if necessary.
The T1H–EBC100 requires NetEdit 3.x or later.
You can install NetEdit3 on Windows98/ME/2000/XPt or Windows NT4t. NetEdit3
is included with this manual on the AutomationDirect Software Product Showcase
CD (also available online at www.automationdirect.com). After inserting the CD into
the drive, the following window will appear.
Using
NetEdit3
Installing NetEdit3
Installation and
Safety Guidelines
Click on the Essential Tools button. The following window will be displayed.
Click on Install NetEdit3. A series of windows will step you through the installation
process. Fill in the necessary information as the installation wizard prompts through
the install. In the Setup Type window, select Typical setup. This setup type is
recommended for most users. The installation process places NetEdit3 in the
C:\HAPTools directory (default).
3–3
Using NetEdit3
There are three methods to launch NetEdit3.
The three methods are:
• using the Windows Start menu Programs>AutomationDirect Tools>
NetEdit3 as shown below
• launching DirectSoft32 (if installed), from the programming window,
select PLC>Tools>NetEdit3
• launching DirectSoft32 (if installed), then select Utilities>NetEdit3
The NetEdit3
Screen
Starting NetEdit brings up the screen below. All NetEdit3 functions are accessed
from this screen.
Using
NetEdit3
Launching
NetEdit3
Installation and
Safety Guidelines
3–4
Using NetEdit3
Adding Network
You may have already set up your PC with selected networking protocols for
Protocol Support Ethernet communications. If not, you will need to select the protocols now for
to the NetEdit3 PC communication with the Ethernet modules. We strongly recommend that you
include the IPX protocol. For Windows 2000, go from My Computer on your
Windows desktop to Control Panel. Double click on Network and Dial–up
Connections, then double click on the desired Network Device to see the installed
Protocols. If IPX is not listed among the protocols already loaded, add it now by
clicking on the Install button. For Windows XP, go from Start>Settings>Control
Panel. The steps are the same as Windows 2000 from this point.
Add the TCP/IP protocol if it is necessary for your application. The TCP/IP selection
will give you support for the UDP/IP protocol. Also, add the IPX protocol if it is not
already active.
Installation and
Safety Guidelines
Using
NetEdit3
→
→
NOTE: We strongly recommend you load IPX protocol on your PC for the connection
from your PC to the ethernet modules. Use UDP/IP in your application, if required,
but also add IPX to your list of active protocols. Having IPX loaded on your PC gives
you a backup for troubleshooting communication problems.
3–5
Using NetEdit3
Using NetEdit3
This section steps through the features and uses of NetEdit3. We will describe the
individual segments of the NetEdit3 screen and the function of each.
NOTE: Your PC-based Control software may be capable of configuring the EBC
module. If so, please refer to the appropriate documentation for that software
product to determine the best method to configure the EBC. Depending on which
software you are using, it may not be necessary to use NetEdit3.
Ethernet
Communication
Protocol
In the upper left corner of the NetEdit3 screen, you will find buttons labeled IPX and
TCP/IP. The EBC module understands these protocols. Both protocols are
permanently resident in the firmware of the module.
When you click on one of these buttons, you are selecting the protocol you want your
PC to use to communicate with the EBC module. You are not telling the module
which protocol to use, because it is using both protocols all the time. IPX is a Novell
standard in widespread use, and UDP/IP is a popular protocol supported by the
TCP/IP suite of protocols in your PC.
Installation and
Safety Guidelines
Some PC-based control software
products may support only one of
these
protocols.
Read
the
documentation for your software to be
sure the protocol you select is
supported.
Using
NetEdit3
The figure to the right shows the
Protocol selection buttons in the upper
left corner of the NetEdit3 screen. The
choice you make here tells your PC
which protocol to send to the EBC to
link NetEdit3 to the module.
3–6
Using NetEdit3
Ethernet Address
The upper left section of the NetEdit3
screen
displays
the
Ethernet
Address of the modules currently on
the network.
If modules are added or removed from
the network, click on the Scan Network
button
to
update
the
list.
Notice that the MAC Address is the
factory-assigned address that is on the
permanent label on the module.
Select a specific module here by
clicking on the MAC Address or by
using the arrow keys. The selected
module is highlighted.
Using
NetEdit3
NOTE: The Module window may list the MAC Addresses of devices not covered by
this manual.
Module Type, IP
Address and ID
Installation and
Safety Guidelines
The upper mid section of the NetEdit3 screen displays the Module Type,
IP Address, module ID, Name and Description of the modules currently
on the network.
A new EBC will have an IP Address of 0.0.0.0, a Module ID of 0 (zero),
and no Module Name or Description. To assign or change a module an
IP address, ID, name or description refer to the EBC Settings>General
Information description later in this section.
Right clicking on an EBC module listed
on the NetEdit3 screen will display the
window to the right. This is an
alternative to using the Module Info or
EBC settings tabs (shown below) to
access the module’s configuration
settings. The settings are discussed
later in this section.
3–7
Using NetEdit3
Module Info>
General
Information
When the Module Info tab is selected, the General Info box lists the
selected module’s Firmware Revision, Booter Revision, DIP Switch
Setting, PWB Revision, PLD Revision and CPU Revision.
This box is in the lower left section of the NetEdit3 screen.
Module Info>
Ethernet Stats
When the Module Info tab is selected, the
Ethernet Stats box displays statistics related
to the selected module’s communication
errors. Click on the Reset Stats button to reset
all categories to 0 (zero).
When the EBC Settings tab is selected, the selected module’s
Configuration, Utilities and Firmware tools can be accessed.
This box is in the lower middle section of the NetEdit3 screen.
Installation and
Safety Guidelines
EBC Settings
Using
NetEdit3
This box is in the lower middle section of the
NetEdit3 screen.
3–8
Using NetEdit3
EBC Settings>
Configuration>
General
Clicking the General button in the EBC
Settings>Configuration box brings up the General
Settings window below.
The General Settings box allows you to assign a Module ID. Module IDs must
be unique for each EBC, but they do not have to be in sequence. The module’s
Node Address rotary switches must both be set to zero to allow NetEdit3 to
set a Module ID. Do not use address zero for communications.
Installation and
Safety Guidelines
Using
NetEdit3
The Name field and Description field are optional.
To set an IP Address, highlight the number in each of the four boxes, and
overwrite the number. Use the twelve-digit number assigned to the EBC
module by your network administrator. If you change the IP Address, do not use
the number “255” in any field. Doing so will cause communication problems.
The OK button sends all the entries to the module’s flash memory.
EBC Settings>
Configuration>
Serial Port
Clicking the Serial Port button in the EBC
Settings>Configuration box brings up the
Serial Port Settings window below.
On the Serial Port Settings window, make
any necessary changes to the serial
communication
parameters.
After
making changes, be sure to click on the
OK button. Also, Be sure these
parameters match the parameters of the
serial device with which you are
communicating.
Note: Some PC-based Control software
packages may automatically overwrite
settings selected here. Refer to the
documentation for your PC-based
Control software.
The OK button sends all the entries to the
module’s flash memory.
3–9
Using NetEdit3
EBC Settings>
Utils>Show Base
Contents
Clicking the Show Base Contents button in
the EBC Settings>Utilities box brings up
the Show Base Contents Window shown
below.
This function queries the EBC for a list of I/O modules it has in its base. The Module
Type and the MODBUS 584/984 addressing will be listed as well. This will help
confirm that the EBC can recognize all the I/O modules connected to the EBC
controller. The Show Base Contents information can be saved as a (*.txt) file or
printed for reference or future use.
Using
NetEdit3
The functions in the Firmware box are used
to update the selected module’s Firmware
and Booter versions. The Restore Factory
Settings buttons resets the selected
module’s IP address, ID, Name and
Description to factory defaults. Refer the
sections on the next page to determine if
updates are necessary.
Clicking on the either of the Update
buttons opens the appropriate EBC
folder within the Images folder, which
is created during the install of
NetEdit3. The Images folder is located
in the same folder as NetEdit3.exe.
Each module folder contains the
module’s firmware and boot loader
files. The next section discusses
keeping the firmware files up to date.
Installation and
Safety Guidelines
EBC Settings>
Firmware
3–10
Using NetEdit3
FileMenu>
Live Update
Using
NetEdit3
When you click the Go! button
on the Live Update window,
NetEdit3 will compare the
version information of the files
on the Host Engineering web
site against the files you have
locally on your PC, and it will
download any newer files. Once
this process is complete,
NetEdit3 will rescan the devices
on your network and refresh the
“F” and “B” columns next to the
listed devices.
F/B/C
Columns
Installation and
Safety Guidelines
The Live Update will retrieve the latest firmware
and boot loader files from the Host Engineering
web site and place them in the NetEdit3 Images
folder that was created during the install of
NetEdit3. The feature requires that you have a
functional Internet connection (dial–up or
broadband). If the Images folder does not exist
on your PC, it will be created as part of the
retrieval process.
The F, B, and C columns are provided
to signify potential issues with
devices on the network.
The “F” column will display an
asterick beside any device whose
firmware is older than its firmware file
in your Images folder.
The “B” column will display an asterick beside any device whose boot loader is
older than its boot loader file in your Images folder.
The “C” column will display an asterick beside any device that has a
configuration conflict with another device on the network. Duplicate module IDs
(that are non–zero) and duplicate IP Addresses (that are not 255.255.255.255)
will report as conflicts.
3–11
Using NetEdit3
Locating the MAC Address Label
Factory-assigned MAC Address
Host Auto. Products
T1H–EBC100
5A
0704
00 E0 62 40 03 B7
MAC Address
MFG.IES
Using
NetEdit3
A unique Media Access Control (MAC) Address is assigned to each module at the
factory and cannot be changed. It is a twelve digit number, and it is printed on a label
permanently attached to the EBC circuit board. The MAC address label can be
viewed through the translucent module cover. NetEdit3 and HTML Configuration
can be used to read the MAC address.
Installation and
Safety Guidelines
MODBUSr TCP/IP
for T1H–EBC100
In This Chapter. . . .
— MODBUS TCP/IP
— Supported MODBUS Function Codes
— MODBUS 584/984 Addressing
— T1H–EBC100 System Memory
— Current / Last State Error Codes
— Extended Error Codes
— Analog Input Module Configuration
— Analog Output Module Configuration
14
4–2
MODBUS TCP/IP
For T1H–EBC100
MODBUS TCP/IP
MODBUS TCP/IP
Client / Server
Model
MODBUS TCP/IP is essentially the serial MODBUS RTU protocol encapsulated in a
TCP/IP wrapper. MODBUS RTU is used for serial communications between a
master and slave(s) devices. MODBUS TCP/IP is used for TCP/IP communications
between client and server devices on an Ethernet network. The TCP/IP version of
Modbus follows the OSI Network Reference Model.
The MODBUS messaging service provides a Client/Server communication
between devices connected on an Ethernet TCP/IP network. This client / server
model is based on four type of messages:
• MODBUS Request – the message sent on the network by the Client to
initiate a transaction
• MODBUS Confirmation – the Response Message received on the Client
side
• MODBUS Indication – the Request message received on the Server
side
• MODBUS Response – the Response message sent by the Server
Client / Server Model
Request
Indication
Client
Server
Confirmation
Protocol
Description
A typical MODBUS TCP/IP frame consists of the following fields:
TCP HEADER
Installation and
Safety Guidelines
Response
The T1H–EBC100
is an example of a Server
MBAP HEADER
FUNCTION
DATA
The MBAP header (MODBUS Application Protocol header) is seven bytes long. It
consists of the following fields.
• Transaction Identifier – It is used for transaction pairing, the MODBUS
server copies in the response the transaction identifier of the request. (2
bytes)
• Protocol Identifier – It is used for intra–system multiplexing. The
MODBUS protocol is identified by the value 0. (2 bytes)
• Length – The length field is a byte count of the following fields, including
the Unit Identifier and data fields. (2 bytes)
• Unit Identifier – This field is used for intra–system routing purpose. It is
typically used to communicate to a MODBUS or a MODBUS+ serial line
slave through a gateway between an Ethernet TCP/IP network and a
MODBUS serial line. This field is set by the MODBUS Client in the
request and must be returned with the same value in the response by
the server. (1 byte)
This header provides some differences compared to the MODBUS RTU application
data unit used on serial line:
4–3
MODBUS TCP/IP
•
•
MODBUS TCP/IP
For T1H–EBC100
•
The MODBUS “slave address” field usually used on MODBUS Serial
Line is replaced by a single byte “Unit Identifier” within the MBAP
Header. The “Unit Identifier” is used to communicate via devices such
as bridges, routers and gateways that use a single IP address to
support multiple independent MODBUS end units.
All MODBUS requests and responses are designed in such a way that
the recipient can verify that a message is finished. For function codes
where the MODBUS PDU has a fixed length, the function code alone is
sufficient. For function codes carrying a variable amount of data in the
request or response, the data field includes a byte count.
Protocol Identifier – It is used for intra–system multiplexing. The
MODBUS protocol is identified by the value 0. (2 bytes)
The function code field of a message contains 8 bits. Valid function codes are in the
range of 1 – 255 decimal. The function code instructs the slave what kind of action to
take. Some examples are to read the status of a group of discrete inputs; to read the
data in a group of registers; to write to an output coil or a group of registers; or to read
the diagnostic status of a slave.
When a slave responds to the master, it uses the function code field to indicate either
a normal response or that some type of error has occurred. For a normal response,
the slave echoes the original function code. In an error condition, the slave echoes
the original function code with its MSB set to a logic 1.
Installation and
Safety Guidelines
The data field is constructed using sets of two hexadecimal digits in the range of 00
to FF. According to the network’s serial transmission mode, these digits can be made
of a pair of ASCII characters or from one RTU character.
The data field also contains additional information that the slave uses to execute the
action defined by the function code. This can include internal addresses, quantity of
items to be handled, etc.
The data field of a response from a slave to a master contains the data requested if
no error occurs. If an error occurs, the field contains an exception code that the
master uses to determine the next action to be taken. The data field can be
nonexistent in certain types of messages.
4–4
MODBUS TCP/IP
For T1H–EBC100
MODBUS TCP/IP
Note: ModScan32 is a Windows based application program that can be used as a
MODBUS master to access and change data points in a connected slave device
(T1H–EBC100) The utility is ideally suited for quick and easy testing of MODBUS
TCP network slave devices. Visit www.win–tech.com to download a free
ModScan32 trial demo and for more information on ModScan32.
Supported MODBUS Function Codes
The following MODBUS function codes are supported by the T1H–EBC100 base
controller.
Installation and
Safety Guidelines
MODBUS
Function Code
Function
01
Read Output Table
02
Read Input Table
03
Read Holding Registers (when addressing
mode is 584/984, this function is used to access analog output registers)
04
Read Input Registers (when addressing mode
is 584/984, this function is used to access
analog input registers)
05
Force Single Output
06
Preset Single Registers
08
Loop back / Maintenance
15
Force Multiple Outputs
16
Preset Multiple Registers
4–5
MODBUS TCP/IP
T1H–EBC100
Modbus
Data Type
Range (Decimal)
Access
1024
Discrete Output
R/W
1025 – 10000
–
Reserved
–
10001 – 11024
1024
Discrete Input
R only
11025 – 20000
–
Reserved
Range (Decimal)
Words
Channel
(16– bit) (32– bit)
Memory Type
Analog Input
30001 – 30512
512
256
Analog Input Register
R only
Input Register
30513 – 32000
–
–
Reserved
–
Bit Input Register 32001 – 32064
64
32
Discrete Input Bit
Register
R only
Input Register
32065 – 37000
–
–
Reserved
–
Analog output
40001 – 40512
512
256
Analog Output
Register
R/W
Hold Register
40513 – 42000
–
–
Reserved
–
Bit Output
Register
42001 – 42064
64
32
Discrete Output Bit
Register
R/W
Hold Register
42065 – 44000
–
–
Reserved
–
Input
Modbus Data Type
Hold Register
Memory Type
1 – 1024
Coil
Input Register
Points
Installation and
Safety Guidelines
Note: NetEdit3 Show Base Contents function will list the MODBUS addressing for each I/O
module on the base. For the analog I/O, the module Configuration Data registers are also
listed. Refer to Chapter 3 for information on NetEdit3.
MODBUS TCP/IP
For T1H–EBC100
MODBUS 584/984 Addressing
4–6
Installation and
Safety Guidelines
MODBUS TCP/IP
For T1H–EBC100
MODBUS TCP/IP
T1H–EBC100 System Memory
T1H–EBC100
Modbus Addressing
Range (Decimal)
Words
(16–bit)
Word Descriptions
Access
37001 – 37006
6
1 – OS Major Version
2 – OS Minor Version
3 – OS Build Version
4 – Booter Major Version
5 – Booter Minor Version
6 – Booter Build Version
R only
37007 – 37010
–
Reserved
–
Device Data
37011 – 37100
90
1 – Version of Device
2 – Family
3 – Processor
4 – Module Type
5 – Status Code
(6–8) – Ethernet Address
9 – RAM Size
10 – Flash Size
11 – Batt Switch
12 – DIP Settings
13 – Media Type
(14–15) – Reserved
16 – Reserved
17 – Reserved
18 – Model Number
19 – Ethernet Speed
20 – Reserved
21 – IO Total Byte Count
22 – Bit Input Byte Count
23 – Bit Output Byte Count
24 – Non–bit Input Byte Count
25 – Non–bit Output Byte Count
(26–90) – Reserved
R only
I/O Module ID’s
37101 – 37132
32
(1 word
per slot)
I/O module ID numbers per slot location
R only
37133 – 37200
–
Reserved
–
37201 – 37328
128
(4 words
per slot)
1 – Bit Input Count
2 – Bit Output Count
3 – Non–bit Input Count
4 – Non–bit Output Count
R only
37329 – 37400
–
Reserved
–
Module Version
Information
Module Information
(continued)
4–7
MODBUS TCP/IP
T1H–EBC100
Words
(16–bit)
Word Descriptions
Access
EBC Dynamic
Module Data
50001 – 50020
20
1 – See Error Codes on p. 4–9.
2 – Error bit–per–slot for first 16 slots
If any bit is set, see extended error info of Module Status data for specific problem
3 – Error bit–per–slot for second 16 slots (if present)
If any bit is set, see extended error info of Module Status data for specific problem
NOTE: Any write to [1], [2], or [3] above will clear the
module / slot errors.
4 – Flags:
Bit 0: If 1, module has rebooted since this bit
was cleared, a write to the Flags word with this
bit set will clear this reboot bit.
Bit 1: Write Only Bit – A write to the Flags word
with this bit set will cause the base to be re–
scanned.
Bit 2: Write Only Bit – If Bit 1 is set to do rescan,
this bit is used to indicated if
RESCAN_LEAVE_IMAGE_RAM or
RESCAN_CLEAR_IMAGE_RAM
Bit 3–7: Reserved
5 – Reboot Count (LSW) – Read Only
6 – Reboot Count (MSW) – Read Only
7 – Link Monitor Timeout – 0 to disable
8–20 – Reserved
R/W
Configuration
Data
50021 – 50052
32
1 word per slot to read/write module configuration data
(See Analog I/O Module Configuration tables at the
end of this chapter for bit definitions)
R/W
50053 – 65536
–
Reserved
–
Installation and
Safety Guidelines
Modbus Addressing
Range (Decimal)
MODBUS TCP/IP
For T1H–EBC100
T1H–EBC100 System Memory (continued)
4–8
Installation and
Safety Guidelines
MODBUS TCP/IP
For T1H–EBC100
MODBUS TCP/IP
T1H–EBC100 System Memory (continued)
T1H–EBC100
I/O
Module
Status
Modbus Addressing Words
Range (Decimal)
(16–bit)
Word Descriptions
Access
37401 – 38040
640
(20 words
per slot)
1 – Flags with bits indicating presence of Error, Warning, Info Values
Bit 0: If set, indicates that Error Value is non–zero
Bit 1: If set, indicates that Warning Value is non–zero
Bit 2: If set, indicates that Info Value is non–zero
Bit 3: Reserved
Bit 4: If set, indicates that Extended error info is present
Bit 5: Reserved
Bit 6: Reserved
Bit 7: Reserved
For Words 2–4, refer to Current/Last State Error Codes Table (p.4–9)
2 – Error Code
3 – Warning Code
4 – Info Code
For Words 5–20, refer to Extended Error Codes Table (p.4–9)
5 – Extended Error Code 1 (i.e channel 1 of an analog module)
6 – Extended Error Code 2 (i.e channel 2 of an analog module)
7 – Extended Error Code 3 (i.e channel 3 of an analog module)
8 – Extended Error Code 4 (i.e channel 4 of an analog module)
9 – Extended Error Code 5 (i.e channel 5 of an analog module)
10 – Extended Error Code 6 (i.e channel 6 of an analog module)
11 – Extended Error Code 7 (i.e channel 7 of an analog module)
12 – Extended Error Code 8 (i.e channel 8 of an analog module)
13 – Extended Error Code 9 (i.e channel 9 of an analog module)
14 – Extended Error Code 10 (i.e channel 10 of an analog module)
15 – Extended Error Code 11 (i.e channel 11 of an analog module)
16 – Extended Error Code 12 (i.e channel 12 of an analog module)
17 – Extended Error Code 13 (i.e channel 13 of an analog module)
18 – Extended Error Code 14 (i.e channel 14 of an analog module)
19 – Extended Error Code 15 (i.e channel 15 of an analog module)
20 – Extended Error Code 16 (i.e. channel 16 of an analog module)
R only
38041 – 40000
–
Reserved
–
(continued)
4–9
MODBUS TCP/IP
The following table lists the error codes for Words 2–4 in the Module Status System Memory area.
Error Code
(Decimal)
Description
E0
No error.
E121
Channel failure.
E122
Unused analog input channels exist.
E139
Broken transmitter on one of the analog input channels (if supported by analog module)
E142
Multiple channels failed.
E153
The module which was in this slot is no longer responding. User has removed a module in a Terminator
I/O slave system.
If Automatic Reset (default) is enabled for this slave, it will reset itself once the replacement module is
inserted.
If Manual Reset is enabled for this slave, the user must 1) SET the slave disable flag for that slave in the
first diagnostic output word, 2) wait for bits 8–15 in second diagnostic input word to equal 1, then 3)
RESET the slave disable flag in the first diagnostic output word.
E154
I/O configuration has changed. See E153 for reset methods.
E200–
E216
Unused analog input channels exist at channel xx (1–16), where xx = Value –200.
(example: E212 indicates unused analog channel exists at channel 12.
MODBUS TCP/IP
For T1H–EBC100
Current / Last State Error Codes
Extended Error Codes
The following table lists the error codes for Words 5–20 in the Module Status System Memory area.
Description
E32–
E63
Bitwise error where bit 5 is always SET. Look at bit 0 thru bit 4 to get a possible list of errors. Example 34
decimal =22 hexadecimal (Bit 5 SET and Bit 1 SET).
BIT
Type of Error
0
Terminal block off
1
External P/S voltage low
2
Fuse blown
3
Bus error
4
Module initialization error (intelligent module)
5
Fault exists in module (this bit is SET if any of the above bits are
SET)
E117
Write attempt to an invalid analog channel.
E119
Data not valid. Subnet mask or IP address not allowed // EBC SDK data packet not constructed properly.
E121
Analog input channel error.
E122
Unused analog input channels exist.
E139
Broken transmitter on one of the analog input channels.
E142
Channel failure.
E146
Communications failure. Hitachi drive on–board relay set.
E153
The module which was in this slot is no longer responding. User has removed a module in a Terminator
I/O slave system.
If Automatic Reset is enabled for this slave, it will reset itself once the replacement module is inserted.
If Manual Reset is enabled for this slave, the user must 1) SET the slave disable flag for that slave in the
first diagnostic output word, 2) wait for bits 12–15 in second diagnostic input word to equal 1, then 3)
RESET the slave disable flag in the first diagnostic output word.
E154
One or more new modules has been inserted into the base. See E153 for reset methods.
E155
Terminator module status error.
One or more of the modules in the T1H–EBC100 base has an error. For more detail check extended
errors
E200–
E216
Unused analog input channels exist at channel xx (1–16), where xx = Value –200.
Installation and
Safety Guidelines
Error Code
(Decimal)
4–10
MODBUS TCP/IP
For T1H–EBC100
MODBUS TCP/IP
Analog Input Module Configuration
The Terminator I/O analog input modules are configured using the following bit
definitions located in the Configuration Data memory area of the T1H–EBC100’s
System Memory. Only the T1F–08AD1 and T1F–08AD2 support Fast Response
mode.
Analog Input Module Configuration Bits
Bit 0–4
Input Enable
0 = All Channels Enabled
1 – 31 = Number of Channels
Enabled Starting With Channel 1
Write
Bit 5–6
Reserved
–
Bit 7
0 = Normal Response
1 = Fast Response
(T1F–08AD1 and T1F–08AD2 only)
Write
Bit 8–15
Reserved
–
Analog Output Module Configuration
The Terminator I/O analog output modules are configured using the following bit
definitions located in the Configuration Data memory area of the T1H–EBC100’s
System Memory.
Installation and
Safety Guidelines
Analog Output Module Configuration Bits
Bit 0
Outputs Enable
0 = All outputs OFF
1 = All outputs Enabled
Write
Bit 1
Unipolar / Bipolar
0 = Unipolar selected
1 = Bipolar selected
Write
Bit 2
5V / 10V Range
0 = 5V range
1 = 10V range
Write
Bit 3
0 – 20mA / 4–20mA Range
0 = 0 – 20mA range
1 = 4 – 20mA range
Write
Bit 4–15
Reserved
–
T1H–EBC100 DHCP &
HTML Configuration
15
In This Chapter. . . .
— T1H–EBC100 DHCP
— Disabling DHCP and Assigning a Static IP Address
— Using HTML Configuration
5–2
DHCP & HTML
Configuration
T1H–EBC100 DHCP Issues and HTML Configuration
T1H–EBC100 DHCP
DHCP Issues
The T1H–EBC100 is configured at the factory to look for a DHCP (Dynamic Host
Configuration Protocol) server at power up. DHCP provides a way to allocate IP address
dynamically to devices on a local area network (LAN). A system or network
administrator configures a DHCP server with a range of IP addresses that can be
assigned to DHCP enabled clients (i.e. T1H–EBC100).
In addition to an IP address, a DHCP server can provide other information such as
DNS domain or a gateway IP address.
DHCP uses the concept of a “lease” or amount of time that an assigned IP address
will be valid for a client. The lease time can vary depending on how long a user is
likely to require the network connection at a particular location. Since the TCP/IP
configuration is “leased” to the client, that is, it’s not a permanent configuration. This
information can change from one power up session to the next. While this is an
acceptable solution for the initial testing and setup of your T1H–EBC100 device, we
do not recommend that you use DHCP to assign IP addresses for your runtime
operation. Use NetEdit3 or the T1H–EBC100’s HTML Configuration page to assign
a static IP address to the module (shown below).
NetEdit3 can be used to connect to a T1H–EBC100 using the IPX protocol,
regardless of the IP address that was assigned to it by a DHCP server.
Disabling DHCP and Assigning a Static IP Address
You can use NetEdit3 or the T1H–EBC100’s HTML Configuration page to disable
DHCP and assign a static IP address to the module. Click on the Use the following IP
Address button and enter a valid IP address for your network application.
NetEdit3 (refer to chapter 3)
Installation and
Safety Guidelines
.
HTML Configuration
5–3
T1H–EBC100 DHCP Issues and HTML Configuration
Using HTML Configuration
Connecting to the
T1H–EBC100
DHCP & HTML
Configuration
The T1H–EBC100 can be configured by using your PC’s internet browser to access
the module’s HTML configuration page. This method of configuration uses the
TCP/IP protocol, so you must know T1H–EBC100’s IP address to establish
communications. The IP address may have been assigned by a DHCP server
(default) or may have been set by using NetEdit3.
Enter the module’s IP address in
your browsers Address field.
Connecting to the module’s HTML
Configuration utility brings up the
window below
Module ID: Module IDs must be unique for each EBC, but they do not have to be in
sequence. The module’s Node Address rotary switches must both be set to allow the
HTML configuration tool to set a Module ID. Do not use address zero for
communications.
Module Name field and Module
Description fields are optional to
identify the module. Click the
Send button to write to the
module’s flash memory.
Installation and
Safety Guidelines
To configure the module, click on the desired parameter field. A new window will
open, which are all described below and on the following page. Clicking the Back
button will take you back to the main configuration screen shown above. Clicking the
Send button writes the entry or change to the module’s flash memory and clicking
the Reset button reads the module’s flash memory.
5–4
DHCP & HTML
Configuration
T1H–EBC100 DHCP Issues and HTML Configuration
Ethernet Address: this is the MAC Address. It is a factory-assigned address that is
on the permanent label on the module.
IP Configuration: Set IP
Address, Subnet Mask and
Gateway addresses. Click the
Send button to write to the
module’s flash memory.
The module’s current Booter Version and OS Version are listed. The latest
versions can be found by clicking Hosteng.com in the Firmware Updates field.
Installation and
Safety Guidelines
Serial Port Setup: configure or make necessary changes to the serial port
communication parameters. Click the Send button to write to the module’s
flash memory.
The module’s current CPU Rev and PWB/PLD Rev are listed. The latest versions
can be found by clicking Hosteng.com in the Firmware Updates field.
Firmware Updates: If your PC is connected to the internet, clicking on Hosteng.com
will take you to Host Engineering’s web site where the most current firmware files are
available for downloading to your PC. You must use NetEdit3 to upgrade the module.
Using the
T1H–EBC(100)
with Think & Do
In This Appendix. . . .
1A
Ċ Mapping T1H-EBC(100) I/O Points
Ċ Hot Swap Setup
Ċ Analog I/O Module Configuration
Ċ I/O Module Status Words / Bits
Ċ Using EZTouch/EZText Panel with the RJ-12 Serial Port
A–2
Appendix A
Using EBC(100) with T&D
Using T1H–EBC(100) with Think & Do
Mapping T1H–EBC(100) I/O Points
We recommend that you are familiar with the “Getting Started” and “Creating a
Project” chapters in the Think & Do Studio Learning Guide before attempting to map
the EBC I/O points/channels to Data Items using ConnectivityCenter.
Launching
Connectivity
Center Tool
To launch ConnectivityCenter:
Connecting
to the EBC
ConnectivityCenter will draw a picture of your EBC I/O system.
1) Launch Think & Do Studio ProjectCenter from the Windows desktop by clicking on
Start > Programs > Think & Do Studio > ProjectCenter. Or, click on the ProjectCenter
icon to start.
2) Click on the File Menu and either Open your Think & Do Project or select New.
3) Within ProjectCenter select Windows 2000 or NT Certified PC as the Runtime
Target.
4) Then click Tools > ConnectivityCenter to launch ConnectivityCenter. Or, click on
the ConnectivityCenter shortcut in the Project Explorer.
5) Once in ConnectivityCenter click on Drivers > Add and select
Automationdirect.com Ethernet I/O Driver.
5)Then click on Configuration > Connect or click on the Connect toolbar button.
Board View
Automationdirect.com
I/O Driver
Mapping I/O Points This procedure is discussed in detail in the “Creating a Project” chapter in the Think
& Do Studio Learning Guide. This will map your real world I/O to Data Items.
to Data Items
A–3
Using T1H–EBC(100) with Think & Do
Hot Swap:
Automatic Mode
Click on the T1H–EBC(100) graphic and the Module Info tab in ConnectivityCenter.
The Hot Swap Settings can be set to either Automatic or Manual mode. If Automatic
mode is selected, the base will automatically rescan once a module has been “Hot
Swapped”.
T1H–EBC
Module Info tab
Hot Swap:
Manual Mode
Reset
If Manual mode is selected, you will need to write a logical “1” to the Eth_Rescan And
Clear Errors Status Item Value to force the base rescan once the module Hot Swap
has been performed. This information is listed under the Board Status Mapping tab.
Write a “1” here
Board Status Mapping tab
Appendix A
Using EBC(100) with T&D
Hot Swap Setup
A–4
Appendix A
Using EBC(100) with T&D
Using T1H–EBC(100) with Think & Do
Analog I/O Module Configuration
Click on the analog I/O module graphic to be configured and the Module Info tab in
ConnectivityCenter. For the analog output modules, select the module Signal Sign
and Range. For the analog input modules (T1F–08AD1 and T1F–08AD2 only),
select either Fast Response or Normal Response (default) mode.
Analog Output Module
Module Info Tab
Analog Input Module
Module Info Tab
I/O Module Status Word / Bits
I/O Module diagnostic information is listed for each I/O module under the Module
Status Mapping tab. Click on a module graphic to display its Status Item
Descriptions.
Status Indicator
1 = Error
Module Status Mapping Tab
A–5
Using T1H–EBC(100) with Think & Do
The T1H–EBC has a built–in RS232C serial port that can be used to connect to an
operator interface panel. Use ConnectivityCenter to configure the connection from
the T1H–EBC to the EZTouch or EXText panel. The “HMI Options for Remote Base
Controllers” section in the “Operator Screen Techniques” chapter in the Think & Do
Studio Learning Guide discusses configuring and using Optimate Panels with the
EBC.
Adding Operator
Interface Device
Click on the T1H–EBC graphic and Module Info tab in ConnectivityCenter. The
Serial Port Settings attribute is only visible in ConnectivityCenter when the I/O is
disconnected. Following the steps below will configure the EBC’s RJ12 serial port to
be used with the EZTouch or EZText panels.
1. Click to access port settings
2. Select to Enable
the serial port. These
settings must match
the port configuration
of the EZ panel.
3. Click to Add
Panel
4. Set the Family to
Modbus Master and
the Panel Type to
EZTouch/Text.
Appendix A
Using EBC(100) with T&D
Using EZTouch/EZText Panel with the RJ–12 Serial Port
A–6
Appendix A
Using EBC(100) with T&D
Using T1H–EBC(100) with Think & Do
Once the EZTouch or EZText panel has been added, it will show up in the list of the
configured devices, and an EZTouch/Text panel graphic symbol will be located
under the I/O base next to the EBC.
Using Monitor I/O
to Verify Panel
Operation
Re–connect to the I/O in ConnectivityCenter by clicking on the Configuration menu >
Connect or by clicking on the Connect toolbar button. Then Scan the I/O by clicking
on the Configuration menu > Scan or by clicking on the Scan toolbar button.
Doubleclick on the EZ panel box graphic to launch the Monitor I/O Dialog Box. The
Monitor I/O tool allows the user to update the fields at any moment, but the panel
continuously updates the fields with any changes as well. All of the “Value” fields in
the Monitor I/O Dialog Box are read/write and updates from the the Monitor I/O
Dialog box take precedence over updates from the panel.
The user can update bit values (Input, Output and Flag) immediately by one mouse
click or by pressing the “space bar”.
When typing in numbers, the grid enters the “edit mode”, which blocks off any
conflicting updates from the panel. The “edit mode” entry completes after pressing
“Enter”, any arrow key or selecting a new line.
Monitor I/O
Dialog Box
Using the T1H–EBC(100)
1B
with KEPDirect OPC Server
In This Appendix. . . .
Ċ Introduction to KEPDirect
Ċ KEPDirect Project: Adding and Configuring a Channel
Ċ KEPDirect Project: Adding and Configuring a Device
Ċ KEPDirect Project: Adding Tags to the Project
Ċ T1H-EBC(100) I/O Addressing
Ċ Analog Output Module Configuration
B–2
Using T1H–EBC(100) with KEPDirect OPC Server
Appendix B
EBC(100) with KEPDirect
Appendix A
Introduction to KEPDirect
Introduction
to OPC
OPC, OLE (Object Linking and Embedding) for Process Control, is an industry
standard created by a number of worldwide leading hardware and software
suppliers in cooperation with Microsoft. The OPC Data Access specification, as
maintained by the OPC Foundation, is a non–proprietary technical specification that
defines a set of standard interfaces based upon Microsoft’s OLE/COM technology.
An OPC server (driver) allows items such as distributed control systems,
programmable logic controllers, I/O systems and smart field devices to
communicate with a wide range of HMI/SCADA (client) software packages residing
on a PC. Traditionally, each software or application developer was required to write a
custom interface, or server/driver, to exchange information with hardware field
devices. OPC eliminates this requirement allowing manufacturing customers true
plug and play connectivity and the freedom to choose products based on their
automation requirements.
DDE Support
While KEPDirect is first and foremost an OPC server, KEPware recognized that a
number of legacy applications still depend upon DDE for their underlying client
server technology. Early in the development of Windows, Microsoft provided a
generic client server technology called DDE (Dynamic Data Exchange). DDE did
provide a basic architecture that would allow many windows applications from a
wide range of vendors to share data. But there was one problem, DDE was not
designed for the industrial market lacking much of the speed and robustness desired
in an industrial setting. However, this did not stop DDE from becoming a dominant
client/server architecture, largely due to its availability in most windows applications.
KEPDirect
KEPDirect Enhanced OPC/DDE Server is a 32 bit windows application that provides
a means of bringing data and information from a wide range of industrial devices and
systems into client applications on your Windows PC. KEPDirect falls under the
category of a ”Server” application. It is very common to hear the term ”client/server
application” in use across many software disciplines and business segments. In the
industrial market, it has usually come to mean the sharing of manufacturing or
production data between a variety of applications ranging from human machine
interface software and data historians, to large MES and ERP applications.
At a high level, the KEPDirect OPC Server is comprised of several objects that are
described on the next page.
Channel Object
Device Object
Group Object
Tag Object
B–3
Using T1H–EBC(100) with KEPDirect OPC Server
Channel Object: Each protocol or driver used in a KEPDirect project is referred to
as a channel. A channel refers to a specific communications driver. A KEPDirect
project can consist of many channels each with unique communications drivers or
each with the same communications driver.
Each channel name must be unique in a KEPDirect application. The channel name
entered here will be part of the OPC browser information.
Group Object: KEPDirect allows tag groups to be added to your project. Tag groups
allow you to tailor the layout of OPC data in logical groupings that fit the needs of your
application. Using tag groups allows multiple sets of identical tags to be added under
the same device. This can be very convenient when a single device handles a
number of similar machine segments. From an OPC client standpoint, the use of tag
grouping allows you to segregate your OPC data into smaller tag lists, which can
make finding a specific tag easier when browsing the server.
Tag Object: KEPDirect allows both dynamic tags, (tag entered directly at the OPC
client that specify device data) and user defined tags. User defined tags have the
benefit of allowing the tag to be browsed from an OPC client that supports tag
browsing. User defined tags also support tag scaling. Unlike many of the dialogs you
will find in KEPDirect, the tag properties dialog has a number of features that are
driven by icons. The tag name is part of the OPC browse data. Tag names must be
unique within a given device branch or tag group branch. If your application is best
suited by using blocks of tags with the same names, use tag groups to segregate the
tags.
Appendix B
EBC(100 with KEPDirect
Device Object: Unlike the channel name, ”Device names” can be the same from
one channel to the next. The device name is a user defined logical name for the
device. The device name and channel name will be part of the OPC browser
information as well as a DDE item name. Within an OPC client the combination of
channel name and device name would appear ”ChannelName.DeviceName”.
B–4
Using T1H–EBC(100) with KEPDirect OPC Server
Appendix B
EBC(100) with KEPDirect
Appendix A
KEPDirect Project: Adding and Configuring a Channel
Running the Server KEPDirect, like any OPC server, can be started a number of ways. One of the
benefits of OPC technology is that your OPC client can automatically invoke the
server when it attempts to connect and collect data from it. In order for this automatic
mode of operation to occur you must first create and configure a project. Once you
have created a project, KEPDirect will automatically select the most recently used
project when it is invoked by an OPC client.
Initially however, you need to manually invoke KEPDirect using either the desktop
icon, if you chose to install it, or by selecting KEPDirect from the windows start menu.
Depending on any changes you may have made to the appearance of KEPDirect,
once invoked you should be presented with the following interface. To learn more
about the various elements of the user interface see (Basic KEPDirect
Components).
While discussing how to start KEPDirect its important to understand what the system
requirements are for running the server. KEPDirect has been designed to place as
little strain on your system as possible.
Recommended System Requirements:
400Mhz Pentium
64 Megs of Ram
10 Megs of Hard Disk Space
Windows NT(SP6a)/2000 (Strongly recommended for industrial settings)
Available Ethernet Card
Adding a Channel
A channel refers to a specific communications driver. A KEPDirect project can
consist of many channels each with unique communications drivers or each with the
same communications driver. Depending on the driver or drivers you have installed
you can define a number of channels within a single project. A channel acts as the
basic building block of an OPC link. Properties like communications port, baud rate,
and parity are contained at the channel level. Each channel name must be unique in
a KEPDirect project. The channel name can be up to 31 characters long.
To add a new channel to your project you can use the Edit menu > New Channel, the
Toolbar Add Channel, or the “Click to add a channel” dialog.
B–5
Using T1H–EBC(100) with KEPDirect OPC Server
Selecting the
Device Driver
Select the device driver you want to assign to the channel. A driver list will be
presented displaying all of the device drivers that are installed in your system.
Appendix B
EBC(100 with KEPDirect
Selecting the ”Enable diagnostics” check box will enable diagnostic information to
be available to your OPC application for this channel. With diagnostic functions
enabled, diagnostic tags are available for use within client applications. In addition
to diagnostic tags, a diagnostic window is also available when this feature is
enabled. The diagnostic features of KEPDirect do require a minimal amount of
overhead processing. For this reason it is recommended that you only use the
diagnostic features when needed and disable them when not in use which is the
default case.
Selecting the
Network Adapter
The Network Interface selection allows you to select a specific NIC card for the
Automationdirect EBC Ethernet driver to use based on the NIC name or its assigned
IP address. By selecting a specific NIC interface you will be able to force the driver to
send all Ethernet communication through the specified NIC. If you do not know
which NIC you should use, select the ”Default” condition.
B–6
Appendix B
EBC(100) with KEPDirect
Appendix A
Using T1H–EBC(100) with KEPDirect OPC Server
Setting the
Server Writes
Optimizations
As with any OPC server, writing data to your device may be the most important
aspect of your application. Insuring that the data written from your OPC client
application gets to the device in a timely manners is the goal of the server. KEPDirect
provides a number of optimization settings that can be used to tailor the server to
meet the needs, and improve the responsiveness of your application.
There are currently three write optimization modes. The following is a brief
description of the modes. For a detailed explanation, refer to the “Channel
Properties – Write Optimizations” section in the KEPDirect on–line help file.
NOTE: We strongly suggest that you characterize your application for
compatibility with these write optimization enhancements before using them
in a production environment.
The default mode, ”Write all values for all tags” will force the server to attempt to
write every value to the controller. This mode insures that everything written from
your OPC client applications will be sent to the target device. While writing every
value to the device may seem like the best course of action, there are a number of
applications where writing every value, many of which may be the same value, over
and over may be simply a waste of communications bandwidth.
The ”Write only latest value for non–boolean tags” allows any value that is not a
boolean value to be updated in the server’s internal write queue and will then be sent
to the device at the next possible opportunity. This can dramatically improve the
overall performance of your application. This feature must be used with a clear
understanding of how it will affect the operation of your application.
The final write optimization mode, ”Write only the latest value for all tags”, takes
the operation described for the second mode and applies it to all tags.
The Duty Cycle selection allows you to control the ratio of write operations to read
operations. By default the duty cycle is set to ten. This means that ten writes will
occur for each read operation. If your application is doing a large number of
continuous writes but you need to insure that read data is still given time to process,
you may want to reduce the Duty Cycle. A setting of one will result in one read
operation for every write operation. In all cases if there are no write operations to
perform, reads will be processed continuously.
B–7
Using T1H–EBC(100) with KEPDirect OPC Server
Saving the New
Channel Settings
With “Channel1” channel added to the server, the KEPDirect window will appear as
follows:
Using Multiple
Channels in a
Project
KEPDirect supports the use of multiple channels. As you add channels to your
project you can specify either the same communications driver or different
communications drivers. Most communication drivers offered by KEPware support
operation on up to 16 communications ports or ethernet network connections
simultaneously. By defining multiple channels you can improve the overall
performance of you application. In the case of either a serial driver or Ethernet driver
using multiple channels allows you to spread large communications loads across
the multiple channels. A good example of this would be a serial driver that is being
used to communicate with eight devices on the serial line. Normally the
communications driver used in this application would be responsible for gathering
data from all eight devices in a round robin fashion. If this same application is
reconfigured to use multiple channels assigned to multiple communications ports,
the device load can be divided across the channels. The end result is reduce work
load on each channel and dramatic improvements in the responsiveness of your
application. The need to use multiple channels is dependent solely on the needs of
your application. In either case there is no additional cost involved to use a licensed
driver on multiple communications or Ethernet ports.
Appendix B
EBC(100 with KEPDirect
Note that the channel is shown using the channel name given, but it is also has a
small red ”x” below the channel icon. The red ”x” indicates that the channel does not
contain a valid configuration. “Channel1” is not valid because a device has not yet
been added to the channel.
B–8
Using T1H–EBC(100) with KEPDirect OPC Server
Adding a Device
Once a channel has been configured in a KEPDirect project, a device must be added
to the channel. Devices represent PLCs, I/O devices or other hardware that the
server will communicate with. Device selection is restricted by the device driver the
channel is using.
To add a device to a channel, select the desired channel and use the Edit menu >
New Device, the Toolbar Add Device, or the “Click to add a device” dialog.
Selecting the
Device Model
The ”Model” parameter allows you to select the specific type of the device
associated with a device ID. The contents of the model selection drop down will vary
depending on the chosen communication driver.
Appendix B
EBC(100) with KEPDirect
Appendix A
KEPDirect Project: Adding and Configuring a Device
B–9
Using T1H–EBC(100) with KEPDirect OPC Server
Selecting the
Device Model
The ”Device ID” parameter allows you to specify the driver specific station or node
address for a given device. Since the Automationdirect EBC driver is an Ethernet
based driver, a unique and valid TCP/IP address must be entered. IPX protocol is not
supported.
Appendix B
EBC(100 with KEPDirect
Setting the Device Device timeout parameters allow a driver’s response to error conditions to be
Timeout Properties tailored to the needs of your application. The timeout parameters are specific to each
device you configure. Each of the field parameters is defined in detail in the “Device
Properties – Timeout” section in the KEPDirect on–line help file.
The ”Connection timeout” allows the time required to establish a socket
connection to a remote device to be adjusted. The ”Request timeout” is used by all
drivers to determine how long the driver will wait for a response from the target
device. The ”Fail after” parameter is used to determine how many times the driver
will retry a communications request before considering the request to have failed. If
your environment is prone to noise induced communications failures you may want
to increase the number of retries the driver performs.
B–10
Automatic OPC
Tag Database
Generation
The automatic OPC tag database generation features of KEPDirect have been
designed to make the setup of your OPC application a Plug and Play operation.
Since the Automationdirect EBC communication driver supports this feature, you
can configure it to automatically build a list of OPC tags within KEPDirect that
correspond to device specific data. The automatically generated OPC tags are then
browsable from your OPC client. The OPC tags that are generated are dependent
upon the nature of the supporting driver. Each field selection is defined in detail in the
“Automated OPC Tag Base Generation” section in the KEPDirect on–line help file.
Appendix B
EBC(100) with KEPDirect
Appendix A
Using T1H–EBC(100) with KEPDirect OPC Server
The ”Automatic tag database generation on device startup” selection allows you to
configure when OPC tags will be automatically generated. There are three possible
selections. The default condition, ”Do not generate on startup”, will prevent the driver
from adding any OPC tags to tag space of KEPDirect. The selection ”Always
generate on startup”, will cause the driver to always evaluate the device for tag
information and to add OPC tags to the tag space of the server each time the server
is launched. The final selection ”Generate on first startup” will cause the driver to
evaluate the target device for tag information the first time this KEPDirect project is
run and to add any OPC tags to the server tag space as needed. When the automatic
generation of OPC tags is selected, any tags that are added to the server’s tag space
must be saved with the project. You can configure your KEPDirect project to auto
save from the Tools > Options menu.
Saving the New
Device Settings
With “Device1” added to “Channel1”, the KEPDirect window will appear as follows:
B–11
Using T1H–EBC(100) with KEPDirect OPC Server
KEPDirect Project: Adding Tags to the Project
User Defined Tags
Each field selection is defined in detail in the “Tag Properties” section in the
KEPDirect on–line help file. A brief description of each is listed below.
The tag ”Name” parameter allows you to enter the string that will represent the data
available from this tag. The tag name can be up to 31 characters in length. While
using long descriptive names is generally a good idea, keep in mind that some OPC
client applications may have a limited display window when browsing the tag space
of an OPC server. The tag name is part of the OPC browse data. Tag names must be
unique within a given device branch or tag group branch. If your application is best
suited by using blocks of tags with the same names, use tag groups to segregate the
tags.
Appendix B
EBC(100 with KEPDirect
There are two ways to get data from a device to your client application using
KEPDirect. The first method and most common method of defining tags is called
User Defined Tags. This requires that you define a set of tags in the server project
and then use the name you assigned to each tag as the item of each OPC/DDE link
between the client and the server. The primary benefit to this method is that all user
defined tags are available for browsing within OPC clients. Additionally, user defined
tags also support scaling.
The second method of defining tags is called Dynamic Tags. Dynamic tags allow
you to define tags in the client application. Instead of providing the server with a tag
name as the OPC/DDE item, you would provide the device address (and optionally a
data type). The server will create a tag for that location and start scanning for data
automatically. KEPDirect allows tag groups to be added to your project.
Tag groups allow you to tailor the layout of OPC data in logical groupings that fit the
needs of your application. Using tag groups allows multiple sets of identical tags to
be added under the same device. This can be very convenient when a single device
handles a number of similar machine segments. From an OPC client standpoint, the
use of tag grouping allows you to segregate your OPC data into smaller tag lists,
which can make finding a specific tag easier when browsing the server.
B–12
Appendix B
EBC(100) with KEPDirect
Appendix A
Using T1H–EBC(100) with KEPDirect OPC Server
The ”Address” parameter allows you to enter the desired driver address for this tag.
To determine how an address should be entered, you can use the Hints button next
to the address parameter. Hints provide a quick reference guide to the address
format of the driver. Once you have entered an address you can test it using the
check address button. When pressed, the check address button attempts to validate
the address with the driver. If the driver accepts the address as entered no message
will be displayed. If an error is detected a pop–up will inform you of the error. Keep in
mind that some errors will be related to the data type selection and not the address
string.
The ”Description” parameter allows you to attach a comment to this tag. A string of
up to 64 characters can be entered for the description. If you are using an OPC client
that supports Data Access 2.0 Tag Properties, the description parameter will be
accessible from the Item Description property of the tag.
The ”Data Type” selection allows you to specify the format of the tag’s data as it is
found in the physical device. The data type setting is an important part of how a
communication driver reads and writes data to a device. For many drivers the data
type of a particular piece of data is rigidly fixed.
The available data type selections are:
S
S
Default – This type allows the driver to choose its default data type see the
specific driver help for details
Boolean – Single bit data On or Off
S
Char – Signed 8 bit data
S
S
Byte – Unsigned 8 bit data
Short – Signed 16 bit data
S
S
Word – Unsigned 16 bit data
Long – Signed 32 bit data
S
Dword – Unsigned 32 bit data
S
S
Float – 32 bit Real value IEEE format
String – Null terminated ASCII string
S
Double – 64 bit Real value IEEE format
S
S
BCD – Two byte packed BCD value range is 0 – 9999
LBCD – Four byte packed BCD value range is 0 – 99999999
The ”Client access” selection allows you to specify whether this tag is Read Only or
Read/Write. By selecting Read Only you can prevent client applications from
changing the data contained in this tag. By selecting Read/Write you are allowing
client applications to change this tag’s value as needed.
The ”DDE scan rate” parameter allows to you specify the the update interval for this
tag when used in a DDE client. OPC clients can control the rate at which data is
scanned by using the update rate that is part of all OPC groups.
The ”Allow client to override data type” selection allows you force OPC clients to
use the data type you have specified for this tag. OPC clients can specify how they
desire to view the data from a particular tag.
B–13
Using T1H–EBC(100) with KEPDirect OPC Server
Creating a
User Define Tag
To determine how an address should be entered, use the Hints button “?” to the right
of the address field. Hints provide a quick reference guide to the address format of
the driver.
The window below shows a valid configured channel, device and several user
defined tags.
Appendix B
EBC(100 with KEPDirect
Once you have entered an address you can test it using the check address “n”
button. When pressed, the check address button attempts to validate the address
with the driver. If the driver accepts the address as entered no message will be
displayed. If an error is detected a pop–up will inform you of the error. Keep in mind
that some errors will be related to the data type selection and not the address string.
Below is an example of a valid tag properties.
B–14
Using T1H–EBC(100) with KEPDirect OPC Server
Appendix A
T1H–EBC(100) I/O Addressing
I/O slots must be individually addressed in the following form: S<ss>:<t><nn> where
ss is the slot number (1 to 93), t is the address type (DI, DO, WI, WO, etc.), and nn is
the address. The address ranges from 0 to an upper limit determined by the module
occupying the slot.
Appendix B
EBC(100) with KEPDirect
I/O Type
T1H–EBC(100) I/O
Addressing
Example
Terminator I/O
EBC Module
Slot 0
Serial I/O Port
EBC:SP0.item
Syntax
Data Type
Discrete Inputs
DI<nn>
nn = Bit Number (decimal)
Boolean, Byte, Char,
Word, Short, DWord, Long
Discrete Outputs
DO<nn>
nn = Bit Number (decimal)
Boolean, Byte, Char,
Word, Short, DWord, Long
Byte Inputs
BI<nn>
nn = Bit Number (decimal)
Byte, Char
Byte Outputs
BO<nn>
nn = Bit Number (decimal)
Byte, Char
Word Inputs
WI<nn>
nn = Bit Number (decimal)
Word, Short
Word Outputs
WO<nn>
nn = Bit Number (decimal)
Word, Short
DWord Inputs
DWI<nn>
nn = Bit Number (decimal)
DWord, Long
DWord Outputs
DWO<nn>
nn = Bit Number (decimal)
DWord, Long
Float Inputs
FI<nn>
nn = Bit Number (decimal)
Float
Float Outputs
FO<nn>
nn = Bit Number (decimal)
Float
Double Inputs
DBI<nn>
nn = Bit Number (decimal)
Float
Double Outputs
DBO<nn>
nn = Bit Number (decimal)
Float
Each field selection is defined in detail in the “Tag Properties” section in the
KEPDirect on–line help file.
Slot 1
Slot 2
8 Digital Input 16 Digital Input
Addresses
S1:DI0
to
S1:DI7
Addresses
S2:DI0
to
S2:DI15
Slot 3
8 Digit Output
Addresses
S3:DO0
to
S3:DO7
Slot 4
16 Digital
Output
Addresses
S4:DO0
to
S4:DO15
Slot 5
8 Analog Input
Addresses
S5:DWI0
to
S5:DWI7
Slot 6
16 Analog
Output
Addresses
S6:DWO0
to
S6:DWO15
B–15
Using T1H–EBC(100) with KEPDirect OPC Server
Analog Output Module Configuration
Analog Output Module Configuration Byte
KEPDirect
Byte
Description
Bit 24
DO0_POINT
Outputs Enable
0 = All outputs OFF
1 = All outputs Enabled
Write
Bit 25
DO1_POINT
Unipolar / Bipolar
0 = Unipolar selected
1 = Bipolar selected
Write
Bit 26
DO2_POINT
5V / 10V Range
0 = 5V range
1 = 10V range
Write
Bit 27
DO3_POINT
0 – 20mA / 4–20mA Range
0 = 0 – 20mA range
1 = 4 – 20mA range
Write
Bit 28–31
DO4_POINT
–
DO7_POINT
Reserved
–
The following example shows the KEPDirect OPC Quick Client (discussed in
Appendix C) used to setup a Terminator I/O analog output voltage module in slot 3.
The highlighted selections are configured for Output Enabled (DO0_Point=1),
BiPolar (DO1_Point=1), and 5V (DO2_Point=0). The analog output data value is
1024 decimal and results in a voltage output of –2.5V.
Appendix B
EBC(100 with KEPDirect
Module
Control
Byte
B–16
Appendix B
EBC(100) with KEPDirect
Appendix A
Using T1H–EBC(100) with KEPDirect OPC Server
Diagnostic bits for Terminator I/O family of analog I/O are supported differently on
each module but will present themselves as error bits/values or messages to the
KEPDirect EBC I/O server using a common convention. A complete definition of the
error information, and it’s format convention, is available in the AutomationDirect
EBC Help file. This can be accessed either from the Start Menu > Program >
KEPDirect EBC I/O Server > Help
Documentation or through the Help menu from within the server. The example below
shows the list of error codes supported by the EBC I/O server. The most common
errors for analog I/O are 139, 142, 155, and 200–216 depending on the features
supported in the specific analog module.
Using the KEPDirect
OPC Quick Client
In This Appendix. . . .
1C
Ċ Creating a KEPDirect Quick Client Project
Ċ Using the RJ12 Serial Port in ASCII Mode
C–2
Using the KEPDirect OPC Quick Client
KEPDirect Quick Client can be used to assist in the test and development of
KEPware’s OPC Data Access 1.0 and 2.0 Servers.
Connecting the
Client to the
OPC Server
Appendix C
EBC(100) / KEPDirect
Appendix A
Creating a KEPDirect Quick Client Project
A server connection provides a link between the Quick Client and the KEPDirect
OPC server. To add a server connection to the Quick Client, you can use the Edit
menu>New Server Connection or click on the New Server icon in the toolbar menu.
Specify the Prog ID of the OPC Server the client should connect to. You can browse
for registered servers by expanding any of the branches. Double–clicking on any
registered server will automatically update the Prog ID field. For more information on
the registered servers, click on the “Help” button to display the “Server Connection”
section of the on–line help file. Once a connection to the OPC server has been
established, additional “Server Operations” can be accessed by right clicking on the
highlighted server in the right window column or by using the Tools menu>Server
selection.
Creating a Client
Group
A group is used to organize a collection of items with a common set of properties. To
add a Group to the Quick Client, you can use the Edit menu>New Group or click on
the New Group icon in the toolbar menu.
The group specifies the following properties: group name, update rate, time bias,
percent deadband, language ID, active state, and the type of data connection that
should be made to the server. For detailed information on the group properties, click
on the “Help” button to display the “Group” section of the on–line help file. Once a
Group has been created, additional “Group Operations” can be accessed by right
clicking on the highlighted branch Group or by using the Tools menu>Group
selection.
C–3
Using the KEPDirect OPC Quick Client
Selecting a
Group Item
Items represent data that may be accessed via the OPC server. An item specifies the
following properties: item ID, access path, requested data type and active state. For
detailed information these properties, click on the Help button to display the “Item”
section of the on–line help file. To add an Item to the Quick Client Group, you can use
the Edit menu>New Item or click on the New Item icon in the toolbar menu.
4
2
1
3
After clicking on the “OK” button, the following window will be display the created
items.
Appendix C
EBC(100) / KEPDirect
If the OPC Server was configured to automatically generate OPC tags, the
generated tags would be browsable from the OPC client. If automatic tag generation
was not selected, create an item by:
1) browsing the OPC Server branch tags
2) highlighting the desired tag in the right column
3) clicking on the “Add Leaves” button
4) clicking on the “Green Check Mark” button to validate the item
5) and clicking on the “OK” button.
C–4
Using the KEPDirect OPC Quick Client
Appendix C
EBC(100) / KEPDirect
Appendix A
Item Operations
Item operations can be accessed by right clicking on the desired item or by using the
Tools menu>Group selection.
After clicking on the desired item operation, a window similar to the following will be
displayed. In this example, a logical “1” (Boolean data type) is being written to a
discrete output to turn it on. The item operations can be used to read discrete/analog
inputs and write to discrete/analog outputs, etc.
C–5
Using the KEPDirect OPC Quick Client
Using the RJ12 Serial Port in ASCII Mode
The EBC RJ12 serial port can be configured for generic ASCII communications
(refer to the “Advanced Settings” section in the “Using NetEdit” chapter to confirm or
change the RJ12 serial port settings). Both the transmit buffer and receive buffer of
the driver are 127 bytes in size. Thus, the corresponding tags can be a maximum of
127 bytes. Incoming bytes are appended to the receive buffer.
Port specifiers precede the serial port address. It defines which port the serial port
address corresponds to. To define an EBC address the mnemonic ”EBC” is used
and the mnemonic SP0 specifies serial port 0. For addressing the EBC serial port, no
base or slot information is needed.
As shown below in the Hints dialog, there are several port address parameters. In
many cases the default values can be used. A detailed list explaining the parameters
are found by clicking on the “Help” button in the Hints window. Then click on the
“Index” button in the Terminator I/O, I/O Addressing window. Then locate the “H2,
H4, Terminator I/O Serial Port Addressing” help section.
Appendix C
EBC(100) / KEPDirect
The communication parameter defaults are:
9600 baud
8 data bits (7 may be selected)
no parity (odd or even may be selected)
1 stop bits (2 may be selected)
C–6
Appendix C
EBC(100) / KEPDirect
Appendix A
Using the KEPDirect OPC Quick Client
The following tags were created in the KEPDirect OPC server for this example.
EBC:SP0.MODE
EBC:SP0.DATAIN
The tags created above were browsed and selected as items within the Quick Client
as shown below. The EBC.SP0.MODE address must be set to a value of 1 to select
the ASCII communications mode. The ASCII string “ASCII String Input Test
Successful” was entered via the RJ12 serial port. The ASCII Sting displays in the
“ASCII Data Input “ Item ID’s Value column.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement