Appendix B - AutomationDirect
Contents
1. Device driver AutomationDirect EBC J Enable diagnostics coc o Clients O active tags O of 0 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 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 lt KEPDirect EBC I O Server untitled opf eS 5 x Iiet This channel is configured to communicate over Description a network ou can select the network adapter that the driver should use from the list below Select D efault if you want the operating system to choose the network adapter for you Network Adapter Defaut 3Com EtherLink PCI2. OK Cancel Apply 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 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M B 12 Using T1H EBC 100 with KEPDirect OPC Server 5 D A Ow xX O c 5S a IS O m LUI 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
3. 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 e Default This type allows the driver to choose its default data type see the specific driver help for details e Boolean Single bit data On or Off e Char Signed 8 bit data e Byte Unsigned 8 bit data e Short Signed 16 bit data e Word Unsigned 16 bit data e Long Signed 32 bit data e Dword Unsigned 32 bit data e Float 32 bit Real value IEEE format e String Null terminated ASCII string e Double 64 bit Real value IEEE format e BCD Two byte packed BCD value range is 0 9999 e 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 a
4. r 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 File Edit View Users G l i Os alms 7 lsa Channeli Identification fff Device1 ieee mo g 4 gt poo ajel Address 1 D10 2 l T fox Description M odule Slot 1 DC Pros Sensor 1 _ i Data properties Data type Boolean Client access Read Only ne Scan rate fi 00 H milliseconds M Do not allow clients to override data type OK Cancel Apply Help ctive tags 0of0 The window below shows a valid configured channel device and several user defined tags KEPDirect EBC I O Server untitled opf File Edit view Users Tools Help Dae h ViMoosjos Bex s Scaling JASCII Bata_Input EBC SPO DATAIN String JInput_0 1 010 Boolean Set Port ta ASCII EBC SPO MODE Byte Channeli Description ine m Devicel gt Ready Clients O Active tags O of 0 A Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M qd yum 004 993 g xX ipu ddy Using T1H EBC 100 with KEPDirect OPC Server T1H EBC 100 I O Addressing I O sl
5. 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 anew channel to your project you can use the Edit menu gt New Channel the Toolbar Add Channel or the Click to add a channel dialog O x lt KEPDirect EBC I O Server untitled opf File Edit wiew New Channel Identification Exi channel name can be from 1 to 256 characters in length It must begin with a letter buk the remaining characters can be any combination of letters numbers and the underscore character Channel name lt Back Cancel Help Clients O Active tags 0 of 0 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M Selecting the Device Driver Selecting the Network Adapter 1 KEPDirect EBC I O Server untitled opf a 5 x Fie Edit View Users Tool pee EELEE Using T1H EBC 100 with KEPDirect OPC Server 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 New Channel Device Driver Click ko add a channel Description Select the device driver you want to assign to the channel The drop down list below contains the names of all the drivers that are installed on your system
6. 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 nota 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 O x ou can control how the server processes writes on this channel Set the optimization method and write to read duty cycle below Note Writing only the latest value can aff
7. 152 168 10 50 NDIS 5 0 driver 0 0 0 0 Coed Hoo iClients 0 Active tags 0 of D Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M qd uum 0OL OGS g x ipu ddy 5 D A O uy xx SC C oS a IS O m LUI Setting the Server Writes Optimizations Using T1H EBC 100 with KEPDirect OPC Server 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
8. 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 lt KEPDirect EBC 1 0 Server etl opf File Edit View Use Tools TIIE Bet Channel1 i Click to add a dew New Device Database Creation The device you are defining has the ape to automatically generate a tag databas Determine if the device should create a jatabase on startup what action should be performed on previously generated tags group to add tags to and allowing subgroups Startup Do not generate on startup x Action Delete on create x Add to group M Allow automatically generated subgroups lt Back Next gt Cancel Hee Clients 0 active tags 0of0 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 fina
9. 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 amp AutomationDirect EBC Device Driver Help 0 x 2 A e gt Hide Locate Back Forward Print m ad Previous Next O AutomationDire v a GS Module mon 7a EBC Dive ai Drive Sta Hot Swa TagDat Desecripti Sie Eror bl Contents ndex Search Favorites AutomationDirect EBC E A Getting Started 5 D A O uy xx SC C oS a IS O m LUI Range error 2 Help Contents 134 Length warning 2 Overview 135 Invalid base number he Device Setup 136 Invalid module type H Performance Optimizations 137 Invalid offset gt Data Types 138 Invalid boot version for OS Addressing 139 Broken transmitter nn contains channel number that failed Module Hot Swapping 140 sais stash inl h i f d i 142 Channel fail multiple nn contains channel BITS from module ae Tag papers cone Ex If bit 0 is set then channel O has failed Ay Error Descriptions If bit 1 and 3 are set then channels 1 and 3 have failed 2 Eror Descriptions 153 I O module missing 1 0 module removed in hot swap 2 EBC Error Codes 154 I O Base has changed I O module replaced in hot swap Driver Error Mess
10. 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 g x ipu ddy w A m U g D 2i 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 oy x File Edit wiew Users bee Pime General Scaling arise Address O T vi tal BI X Description OOOO Data properties Data type Defaut bi Client access Read Write r Scan rate fi oo milliseconds V Do not allow clients to override data type
11. Using the T1H EBC 100 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 Outout Module Configuration B 2 Using T1H EBC 100 with KEPDirect OPC Server introduction to KEPDirect 5 D A Ow xx SC C oS a IS O m LUI Introduction to OPC DDE Support KEPDirect Channel Object Device Object Group Object Tag Object 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 Microsofts 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 an
12. ages 155 Module in error Possible errors missing 24V on discrete modules blown fuses on discrete modules missing 24V on analog modules missing CJC black on the T1F 14THM Driver Warning Messages Read Enors Write Errors Application N otes 200 216 xX unused analog input channels exist where XX Value Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M
13. d the freedom to choose products based on their automation requirements 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 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 KEPDi
14. ect batch processing or the equivalent Write all values for all tags Write only latest value for non boolean tags Optimization Method Write only latest value for all tags Buty Cyce Perform fio H writes for every 1 read omei e _ Ready Clients 0 Active tags 0of0 A Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M Saving the New Channel Settings Using Multiple Channels ina Project B 7 Using T1H EBC 100 with KEPDirect OPC Server With Channel1 channel added to the server the KEPDirect window will appear as follows lt KEPDirect EBC I O Server untitled opf File Edit Yiew Users Tools Help D k ima anro ks bex e a g Scaling Description Click to add a device 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 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 overa
15. eli TLHEBC21 5L0T_O1 Co Channell TLHEBC 1 5L07 03 53 DO7_ POINT Boolean gee Channeli TLHEBC 1 5L0T_O2 gt Channel T1HEBC 2 1 5LO0T_ 03 fm Cy Channell TLHEBC21 SL0T_O3 53_D06_POINT Boolean GaChannell TLAEBC 1 SL0T_03 53_D05 POINT Boolean E Channell TLHEBCZ1 5L0T_ 03 53 004 POINT Boolean Channell TLHEBC21 5LO7T_03 53 003 POINT Boolean Channell TLHEBT2 1 SLOT 03 53 DO2 POINT Boolean Channeli TLHEBC21 5L07_ 03 53 001 POINT Boolean fa Channell TLHEBC 1 5L07_03 53_D00_WoORD 3 Channeli TLHEBC 1 5L07_03 53_ 000 _SHORT Short nae Boolean 3 channelt TLHEBC21 5LOT_03 53_Do00_LONG Long Ga Channell TLHEBC 1 5L07_09 53_D00_DwoRD cword 4 Channelt TLHEBC21 5L07_03 53_D00_CHAR Char C3 Channell TLAEBC 1 5L0T_03 53_D00_BYTE Byte bb i bb bo fe it fb Ete ia SA Them Count Al os Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M 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 gt Program gt KEPDirect EBC I O Server gt Help Documentation or through the Help menu
16. gital 8 Analog Input 16 Analog Output Slot 0 Addresses Addresses Addresses Addresses Serial I O Port S1 DI0 S2 DI0 S3 DO0 Addresses S5 DWIO Addresses to to to S4 DO0 to S6 DWOO EBC SP0 item 1 DI7 2 DI15 S3 D07 to S5 DWI7 S4 D015 S6 DW015 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M Using T1H EBC 100 with KEPDirect OPC Server Analog Output Module Configuration Analog Output Module Configuration Byte Module Control Sees Description Byte y Outputs Enable Bit 24 DOO POINT O All outputs OFF Write 1 All outputs Enabled Unipolar Bipolar Bit 25 DO1 POINT O Unipolar selected Write 1 Bipolar selected 5V 10V Range Bit 26 DO2_POINT 0 5V range Write 1 10V range 0 20mA 4 20mA Range Bit 27 DO3_ POINT 0 0 20mA range 1 4 20mA range DO4_ POINT Bit 28 31 Reserved DO7_POINT 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 DOO 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 qd uum 004 993 g xipueddy OPC Quick Client Untitled i Ioj x Fie Edt View Tools Help Dad eee T BEX c 4AutomationDirect kEPDirect Server f Channeli System mn E Channeli TLHEBC 1 Pee DWord Channeli TLHEBCZ1 _ Syskerm Chann
17. ice 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 lt KEPDirect EBC 1 0 Server untitled opf eS Ioj x File Edit wiew Users Tools D k Mae Elaf Channeli New Device ID The device you are defining may be multidropped as Description part of a network of devices In order to communicate with the device it must be assigned a unique ID our documentation for the device may refer to this as a Network ID or Network Address Dewice ID f 92 169 23 14 Clients 0 active tags 0of0 Setting the Device Device timeout parameters allow a drivers 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 lt KEPDirect EBC 1 0 Server untitled opf a Ioj x File Edit view Users Tools uziz rn New Device Communications Parameters Dad 7 il ia E Channeli S ii Click to add a device Description Enter the parameters you wish to use while communicating with the device Connect timeout refers to the time to wait for a successful initia
18. l connection Request timeout refers to the time to wait for a request to be serviced Connect timeout 3 d seconds Request timeout fioo H milliseconds Fail after 3 successive timeouts i lt Back Next gt Cancel Hep Clients 0 Active tags 0of0 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 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M qd uum 004 993 g x ipu ddy 5 D A O uy xx SC C oS a IS O m LUI Automatic OPC Tag Database Generation Saving the New Device Settings Using T1H EBC 100 with KEPDirect OPC Server 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
19. l 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 gt Options menu With Device1 added to Channel1 the KEPDirect window will appear as follows lt KEP Direct EBC 1 0 Server untitled opf File Edit View Users Tools Help Vee POS ei ee xs Scaling cik to add a static tag Tags are not required but are browsable by OPC clients Clients O Active tags O of 0 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M Using T1H EBC 100 with KEPDirect OPC Server B 11 KEPDirect Project Adding Tags to the Project 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
20. ll 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 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M qd uum 0OL OGS g xipueddy B 8 Using T1H EBC 100 with KEPDirect OPC Server KEPDirect Project Adding and Configuring a Device 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 cha
21. nnel select the desired channel and use the Edit menu gt New Device the Toolbar Add Device or the Click to add a device dialog KEPDire ct EBC I O Server untitled opf E ao joj x Fie Edit View Users Tools New Device Name O bell amp i a El Channeli Description device name can be from 1 to 256 characters in length lt must begin with a letter but the remaining characters can be any combination of letters numbers and the underscore character 5 D A O uy xx SC C oS a IS O m LUI Device name lt Back Cancel Help Clients D Active tags Oof 0 Selecting the The Mode parameter allows you to select the specific type of the device Device Model associated with a device ID The contents of the model selection drop down will vary depending on the chosen communication driver 1 KEPDirect EBC 1 0 Server untithed opf ee ee O x The device you are defining uses a device Description diver that supports more than one model The list below shows all supported models Select a model that best describes the device OW are defining Device model Terminator 1 0 r H4 Terminator 1 0 G51 Drive GS Drive G53 Drive lt Back Cancel Help Clients 0 Active tags Oof 0 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M Selecting the Device Model Using T1H EBC 100 with KEPDirect OPC Server The Dev
22. nvoke 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 howto 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 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
23. ots must be individually addressed in the following form S lt ss gt lt t gt lt nn gt where ss is the slot number 1 to 93 tis 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 VO Type Data Type Discrete Inputs Dl lt nn gt Boolean Byte Char nn Bit Number decimal Word Short DWord Long Discrete Outputs DO lt nn gt Boolean Byte Char nn Bit Number decimal Word Short DWord Long Byte Inputs Bl lt nn gt Byte Char nn Bit Number decimal Byte Outputs BO lt nn gt Byte Char nn Bit Number decimal 5 D A Ow xx SC C oS a IS O m LUI WI lt nn gt Word Short nn Bit Number decimal Word Outputs WO lt nn gt Word Short nn Bit Number decimal DWord Inputs DWI lt nn gt DWord Long pwodi im BE Rumoer ecimay PMP DWord Outputs DWO lt nn gt DWord Long nn Bit Number decimal nn Bit Number decimal Float Outputs FO lt nn gt nn Bit Number decimal Double Inputs DBl lt nn gt nn Bit Number decimal Double Outputs DBO lt nn gt nn Bit Number decimal T1H EBC 100 I O Each field selection is defined in detail in the Tag Properties section in the Addressing KEPDirect on line help file Example Terminator I O Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 EBC Module 8 Digital Input 16 Digital Input 8 Digit Output 16 Di
24. re 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 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M 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 lt KEPDirect EBC 0 Sg Tag Properties File Edit wiew Users os ajeme tlre 1 B0000 253 6 0255 B pte a OK 51 D60 000 253 DB0 255 Float 1 D1000 253 D1240 Short 1 B1000 253 D1240 Word 1 D1000 253 D1248 Byte 51 BI000 253 D1 255 Boolean 1 00000 253 00240 Short 1 00000 253 00240 Word i 1 00000 253 00248 Byte 1 00000 253 00255 Boolean 51 D W1000 253 Dwl255 D word x 51 80000 253 B 02 51 DBI000 253 DB1255 Float Cancel Using T1H EBC 100 with KEPDirect OPC Server 55 Char Once you have entered an address you can test it using the check address
25. rect OPC Server is comprised of several objects that are described on the next page lt KEPDirect EBC I O Server untitled opf Fie Edit View Users Tools Help O MADE eo k ae em Channel Sealing Description Eff Devices Tagi 51 BI0 Byte 100 None sEm zj Ready Clients O Active tags O of O fo Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M Using T1H EBC 100 with KEPDirect OPC Server B 3 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 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 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 se
26. ts 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 g x ipu ddy w x m U g D Qo 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 ofthe 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 Terminator I O EBC User Manual 2nd Edition Rev B T1H EBC M 5 D A O uy xx SC C oS a IS O m LUI Using T1H EBC 100 with KEPDirect OPC Server 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 Adding a Channel benefits of OPC technology is that your OPC client can automatically i
Download Pdf Manuals
Related Search