Driver and Protocol Objects 3 This chapter describes LookoutDirect Driver and protocol object classes, listed in alphabetical order. Input parameter syntax and data members are documented for each object class, along with a description of the functionality of each object class. © Automationdirect.
Chapter 3 Driver and Protocol Objects AB_PLC5, AB_SLC500 LookoutDirect uses the AB object classes to communicate with the Allen-Bradley family of PLC controllers using a variety of interfaces.
Chapter 3 • Driver and Protocol Objects Through a direct DH485 connection using a 1784-PCMK card in conjunction with either a 1747-AIC or 1761-NET-AIC module. PLC Address refers to the PLC network node address setting as configured on the physical device. If devices share a common Interface, they require unique addresses. When using DF1 protocol (serial communications), valid addresses range from 0 to 254 decimal. When using DH+, valid addresses range from 0 to 77 octal.
Chapter 3 Driver and Protocol Objects Retry attempts specifies the consecutive number of times LookoutDirect attempts to establish communications with a device if it is not getting a valid response. After it tries the number of Retry attempts specified, the object generates an alarm and begins to Skip every n poll requests after comm failure. Once LookoutDirect reestablishes communications, it polls the device on its regular cycle, as defined by PollRate.
Chapter 3 Driver and Protocol Objects Allen-Bradley DH+ Interface Parameters When you configure an AB_PLC2, AB_PLC5, or AB_SLC500 for DH+, LookoutDirect creates a file called ALLBRAD.INI. This file contains the configuration settings that you enter for your KT card(s). If you plan to run the process file on a LookoutDirect Runtime System, be sure to copy the INI file along with your process (.lkp) file to the target computer.
Chapter 3 Driver and Protocol Objects For this reason, if you are using a memory manager such as EMM386 it is important to add a memory exclusion statement to your CONFIG.SYS file. The table on the following page lists base memory address selections and corresponding exclusions for all legal memory addresses for the 1784-KT card. Use Max node address to maximize the performance of a DH485 network by assigning addresses to nodes on the network using consecutive numbers starting with zero.
Chapter 3 Driver and Protocol Objects Table 3-1.
Chapter 3 Driver and Protocol Objects IRQ (all cards) identifies the interrupt setting of all DH+ interface cards installed in the computer. This selection should match the IRQ settings on all of the interface cards. Assigning an interrupt to the interface card(s) improves overall computer performance somewhat. Any time one of the cards receives an input, it generates an interrupt recognized by LookoutDirect.
Chapter 3 Driver and Protocol Objects Using the 5136-SD card from S-S Technologies, Inc. To use the 5136-SD card, select the S-S 5136-SD interface in the Create Object dialog box. It is not necessary to run the sdinst.exe program that ships with the card because LookoutDirect downloads the KT-emulation module automatically as part of the initialization process. It is, however, necessary to tell LookoutDirect the port address specified by the switch settings on the card. © Automationdirect.
Chapter 3 Driver and Protocol Objects Allen-Bradley Register Addressing LookoutDirect has adopted a sequential, flat addressing scheme for the Allen-Bradley PLCs. The addresses are sequential by data type, having nothing to do with the actual slot number.
Chapter 3 Driver and Protocol Objects Table 3-2. AB_PLC2 Data Members (Continued) Data Member Type Read Write Description OffHook logical no yes When true, instructs the PLC to retain exclusive use of its assigned communication port. This prevents LookoutDirect from hanging up between polls, saving the redial overhead. This also prevents other blocks from communicating over the same channel.
Chapter 3 Driver and Protocol Objects Table 3-3. AB_SLC500 Data Members (Continued) Data Member Type Read Write Description C:0_OV C255:255_OV logical yes yes Counter overflow bit. C:0_UA C255:255_UA logical yes yes Counter update accumulation bit (HSC in fixed controller only) C:0_UN C255:255_UN logical yes yes Counter underflow bit. C:0_CD -C255:255_CD logical yes yes Counter down-enable bit.
Chapter 3 Driver and Protocol Objects Table 3-3. AB_SLC500 Data Members (Continued) Data Member Type Read Write Description PollRate numeric no yes Specifies the frequency at which the LookoutDirect object polls the SLC device R:0_FD - R255:255_FD logical yes yes Control “found” single-bit logical indicator R:0.LEN R255:255.LEN numeric yes yes Control “length” signed integer ranging from –32,768 to +32,767 R:0.POS R255:255.
Chapter 3 Driver and Protocol Objects Table 3-3. AB_SLC500 Data Members (Continued) Data Member Type Read Write Description T:0.ACC T255:255.ACC numeric yes yes Accumulated timer value ranging from –32,768 to +32,767 T:0.PRE T255:255.
Chapter 3 Driver and Protocol Objects Table 3-4. AB_PLC5 Data Members (Continued) Data Member Type Read Write Description C:0_CD - C999:999_CD logical yes yes Counter down-enable bit. C:0_CU - C999:999_CU logical yes yes Counter up-enable bit. C:0_DN C:999:999_DN logical yes yes Counter done bit. C:0_OV C999:999_OV logical yes yes Counter overflow bit. C:0_UA C999:999_UA logical yes yes Counter update accumulation bit (HSC in fixed controller only).
Chapter 3 Driver and Protocol Objects Table 3-4. AB_PLC5 Data Members (Continued) Data Member Type Read Write Description OffHook logical no yes When true, instructs the PLC to retain exclusive use of its assigned communication port. This prevents LookoutDirect from hanging up between polls, saving the redial overhead. This also prevents other blocks from communicating over the same channel.
Chapter 3 Driver and Protocol Objects Table 3-4. AB_PLC5 Data Members (Continued) Data Member Type Read Write Description R:0_UL - R999:999_UL logical yes yes Control “unload” single-bit logical indicator. S:0 - S:127 numeric yes yes PLC status file containing a signed integer ranging from –32,768 to +32,767 (see Allen-Bradley documentation). S:0_0 - S:127_15 logical yes yes Individual PLC status bits (see Allen-Bradley documentation). ST9:0 - ST255:255 text yes T:0.ACC T999:999.
Chapter 3 Driver and Protocol Objects Allen-Bradley Error Messages AB objects report the statuses of commands they issue to AB devices. When LookoutDirect receives a response from an AB device, it reads the status (STS) byte and, if necessary, the extended status (EXT STS) byte to verify the device executed the LookoutDirect command properly. If the command was not executed properly, LookoutDirect reports the failure as an alarm containing the status code and its meaning.
Chapter 3 Driver and Protocol Objects 5136-SD cards support different sets of valid memory addresses. See the documentation that shipped with the card for details. Invalid node address for card: xx Node addresses must be between 0 and 63 decimal. Invalid port number for SS card: 0xPPP The port number specified for the 5136-SD card is invalid. See the documentation that shipped with the card for the list of valid port addresses.
Chapter 3 Driver and Protocol Objects KT card timed out while loading protocol code KT card failed with status code xx while loading protocol LookoutDirect was not able to transfer a loader file to the card and subsequently download the card protocol firmware. Try to restart the interface card by calling up the AB object definition dialog box and selecting OK. If that does not work try rebooting the computer.
Chapter 3 Driver and Protocol Objects KT card SI0 test timed out KT card SI0 test failed with status code xx The interface card failed the Serial Input Output test when it was first powered on. You may need to restart, reseat, or replace the interface card. KT card send mailbox timed out The AB object timed out while waiting for the KT card to signal that it is ready to be given a new message to send. This is most likely due to a communication problem between the computer and the PLC.
Chapter 3 Driver and Protocol Objects No response within timeout period No response received after receiving ENQ The AB object received an acknowledgment of its poll from the device. The device accepted the command from LookoutDirect. However, the device did not appear to send anything else back in response. You may have to increase Receive timeout to make sure LookoutDirect allows enough time to receive the message.
Chapter 3 Driver and Protocol Objects sdinst.exe program that ships with the 5136-SD card, using the CHK option to confirm that the card is working properly. Unable to access physical memory at segment 0xAAAA LookoutDirect was unable to access the memory at the given segment address. The memory may already be in use by the operating system or by another application.
Chapter 3 Driver and Protocol Objects ASCII ASCII is a protocol driver class LookoutDirect uses to communicate with any serial device that accepts ASCII characters. This object is only available with 32-bit versions of LookoutDirect. An ASCII object contains no predefined data points. When you create an ASCII object, you must define your data request strings as well as the template LookoutDirect uses to parse the response frame.
Chapter 3 Driver and Protocol Objects Phone number specifies the number to be dialed if the selected serial port is configured for dial-up. This number only applies to the individual protocol object. Monitor Serial Port specifies whether you can receive unsolicited frames. Communication alarm priority determines the priority level of alarms generated by the ASCII object. Such alarms are typically related to communications with the physical device.
Chapter 3 Driver and Protocol Objects Table 3-5. ASCII Data Members (Continued) Data Member Type Read Write Description RQSum:1:1 RQSum255:255 numeric yes no Request byte sum RQV1, RQV512 numeric no yes Variable list used to populate request frame with numeric values. RQV1.logical, RQV512.logical logical no yes Variable list used to populate request frame with logical values. RQV1.txt, RQV512.txt text no yes Variable list used to populate request frame with text values.
Chapter 3 Driver and Protocol Objects of data which should be found there, such as five characters read as an unsigned integer, for example. The ASCII object constructs a request frame by processing the sequence of static characters and markers in the request format string, and including data from RQV data members. The response format string decodes a response frame using an analogous process, storing the results in RSV data members.
Chapter 3 Driver and Protocol Objects If nothing halts the process, decoding terminates when the end of the response frame string is reached. There are examples of both request frames and response frames at the end of this section, but for the examples to make sense, you must first understand the ASCII object markers. ACSII Object Markers The general format for a marker is: %[width][type] Each field in the marker format is a single character or a number signifying a particular format option.
Chapter 3 Driver and Protocol Objects Table 3-6. Data Types Allowed by ASCII b* Byte (binary) *For the %b data type: – Number of bytes can be specified, for example %3b, %2b. – Response format can read as either signed or unsigned, for example %^b and %3^b are signed and %b is unsigned. – Endian order can be specified, for example %3~b is big endian and %3b is little endian. %5~^b and %2^~b forms are also valid.
Chapter 3 Driver and Protocol Objects character. The corresponding input field is read up to the first character that does not appear in the bracketed character set. Using a caret (^) as the first character in the set reverses this effect: the ASCII object reads input field up to the first character that does appear in the rest of the character set. Response Format String RSV1.
Chapter 3 Driver and Protocol Objects Entering ASCII Object Format String For a static connection to one of the format data members, enter your format string in the yellow field box in the Edit Connections dialog box. Remember to begin and end the format strings with quotation marks so that LookoutDirect accepts the string input. You can also connect any valid text data member, such as a text entry object, to the format data members.
Chapter 3 Driver and Protocol Objects The space between the words terminates the conversion. See the preceding bracketed character example in order to span a space or other special characters. Response Frame Response Format String >>Test Text<< >>%s%s<< RSV1.txt=Test RSV2.txt=Text >>DogCat<< >>%3s%3s<< RSV1.txt=Dog RSV2.txt=Cat RSV The response format uses a space as a delimiter. Using Sum Data Members The ASCII object includes summing data members you can use to calculate checksum characters.
Chapter 3 Driver and Protocol Objects ASCII Error Messages No response from device within timeout period LookoutDirect received no response from the device within the Receive timeout period. The ASCII object was able to establish a socket, but when it sent a message to the device, the device did not respond—as if it were not there. You may have to significantly increase Receive timeout (and Poll Rate) to ensure LookoutDirect is allowing enough time to receive the expected response.
Chapter 3 Driver and Protocol Objects Object Reference Manual 3-34 www.Automationdirect.
Chapter 3 Driver and Protocol Objects DeltaTau DeltaTau is a protocol driver object class LookoutDirect uses to communicate with Delta Tau Data Systems PMAC Motion Controllers. Create a DeltaTau object for each card installed in the computer. This object class communicates with Delta Tau PMAC cards through dual-ported memory, so be sure that your PMAC hardware includes the dual-ported RAM option. The following figure shows a Delta Tau card configured to use PC memory beginning at address D000.
Chapter 2 System Objects Table 3-7.
Chapter 3 Driver and Protocol Objects DirectLogic The DirectLogic protocol driver object class is used to communicate to PLC Direct by Koyo 105, 205, 305, and 405 PLCs. This driver object supports additional Koyo private labeled PLCs under GE Series One, Texas Instruments Series 305, 405 and Siemens Simatic TI305, TI405 names. Please see the Protocol Reference Chart within the LookoutDirect Learning Guide to verify the part numbers of these additional Koyo PLCs.
Chapter 2 System Objects After the DirectLogic driver class is selected the following dialog appears. The selections are as follows: Tag: User defined object name that can be referenced for connecting other objects. Comm Link: The associated link chosen for the configured driver object. When the “…” button is pressed the Select Link dialog will appear. Poll Rate= is a numerical expression that determines how often to poll the device in milliseconds. Poll is a logical expression.
Chapter 3 Driver and Protocol Objects NOTE: If you are creating a serial Link that will connect through a modem, see the Modem Setup Guide Appendix C in the LookoutDirect Learning Guide. If you are creating an Ethernet Link, refer to the DirectSoft Communications Server online help. Note After making your choice click on the Next button. Select the PLC family by single clicking on the appropriate choice.
Chapter 2 System Objects Select either the DirectNET or K-Sequence protocol. If during the previous step you selected one of the families listed, the highlight bar will be on a valid protocol for that family of PLC. The choice of protocol to use will depend on two factors: • Whether or not the PLC you are connected to supports the protocol on the port where the cable is connected.
Chapter 3 Driver and Protocol Objects configuration, or you can consult the Appendix B Communications Troubleshooting Guide in the LookoutDirect Learning Guide. DirectLogic Protocol Status The DirectLogic driver object monitors protocol statistics and the data can be viewed by selecting Options >> DirectSoft Link Status. This menu selection will only be visible in the Options menu if a DirectLogic driver object was previously created in your lookout process.
Chapter 2 System Objects Table 3-8. 105/205/350/405 DirectLogic PLC Data Members CTA0:DB – CTA376:DB Numeric Yes Yes Counter current value double words (two adjacent addresses; 32-Bit) BCD – addressed in octal and mapped to V01000 – V01377 Failed Logical Yes No Object-generated signal when TRUE, this flag signifies the process file is no longer communicating with the PLC.
Chapter 3 Driver and Protocol Objects Table 3-8.
Chapter 2 System Objects Table 3-8.
Chapter 3 Driver and Protocol Objects Table 3-8. 105/205/350/405 DirectLogic PLC Data Members X0 – X1777 Logical Yes Yes Inputs – addressed in octal and mapped to V40400 – V40477 Y0 – Y1777 Logical Yes Yes Outputs – addressed in octal and mapped to V40500 – V40577 305/305S Direct Logic PLC Family Data Members Table 3-9.
Chapter 2 System Objects Table 3-9. 305/305S DirectLogic Data Members Data Member Type Read Write Description R0:W – R776:W Numeric Yes Yes Single (16-Bit) word registers decimal R0:WB – R776:WB Numeric Yes Yes Single (16-Bit) word registers BCD RC160 – RC370 Numeric Yes Yes Single (8-Bit) byte Control Relay and Special Relay registers decimal Aliases. Numeric Yes Yes Single (16-Bit) word Control Relay and Special Relay registers decimal Aliases.
Chapter 3 Driver and Protocol Objects Table 3-9.
Chapter 2 System Objects GE_Series90 GE_Series90 is a protocol driver class LookoutDirect uses to communicate with GE Series 90-30 and GE Series 90-70 programmable logic controllers (PLCs) using SNPX, a Series Ninety Protocol. PLC Address is a slave address and refers to the PLC address setting as configured on the device. The address can be up to eight ASCII characters. Model chooses either 90-30 or 90-70. Interface selects the protocol. You can choose between SNPX and Ethernet.
Chapter 3 Driver and Protocol Objects PollRate is a numeric expression that determines how often to poll the device. GE_Series90 then polls the device at the specified time interval. Normally, this is a simple time constant such as 0:01 (one second). See Numeric Data Members in Chapter 2, How LookoutDirect Works, of the Getting Started with LookoutDirect manual for information on entering time constants. Poll is a logical expression.
Chapter 2 System Objects Table 3-10.
Chapter 3 Driver and Protocol Objects Table 3-10.
Chapter 2 System Objects could be caused by an audible squelch tail occurring at the end of a radio transmission. Try adjusting RTS delay off and CTS timeout. No attach response within timeout period An attempt was made to establish communications with the PLC without any response. Check your cabling and COM port selections, power, configuration settings, and polling addresses. Invalid response [x] An error in the structure of a response frame was detected. You may have two PLCs with the same address.
Chapter 3 Driver and Protocol Objects Modbus Modbus and ModbusMOSCAD are protocol driver classes LookoutDirect uses to communicate with equipment such as programmable logic controllers (PLCs), remote terminal units (RTUs), or any other piece of equipment using Modbus Serial (ASCII or RTU) or Modbus Plus communication protocol.
Chapter 2 System Objects In this example, LookoutDirect is connected to a Modbus-speaking PLC with an address of 5 using serial port 1 (which was previously configured for hardwired communications), and polling the device every second. Modbus Serial indicates that the slave device talks either Modbus ASCII or Modbus RTU. When you select this option, LookoutDirect first tries to communicate using the RTU format. If unsuccessful, it then tries the ASCII format (a little slower).
Chapter 3 Driver and Protocol Objects modem connected to your communication port, you must also specify a Phone Number. If you select Modbus Plus Network, you need only specify the remote device Address. If you select Modbus Ethernet you must specify the IP address in addition to Alarm Priority, Poll Rate, Poll Retry attempts, and Receive timeout. Address is a slave address and refers to the PLC or RTU address setting as set on the device dip switches.
Chapter 2 System Objects valid response. After it tries the number of Retry attempts specified, the Modbus object generates an alarm and releases the communication port back to the communications subsystem which then moves on to the next device in the polling queue (if any). Refer to Chapter 3, Serial Communications, in the LookoutDirect Developer’s Manual for more information. Receive timeout is the time delay LookoutDirect uses in waiting for a response from a device before retrying the request.
Chapter 3 Driver and Protocol Objects The Modbus object class uses Modbus Function Codes 01, 02, 03, 04, 05, 06, 15, and 16; and expects the remote I/O device to support these codes as specified by Modbus. The driver can communicate with up to 247 Modbus slave devices on each serial port. The Maximum values per message settings specify the maximum number of elements LookoutDirect attempts to read (fc 1 – fc 4), or write (fc 15 and fc 16), in a single Modbus message.
Chapter 2 System Objects Activating the Daniel option deactivates all Modbus holding register members (on that device) except for 40001 – 49999 and 4000001 – 465000. If you attempt to read D40001, for example, the returned value is 0, and LookoutDirect will not attempt to write D40001 to the RTU. Of course, in devices that do not support this option, you can still read and write two adjacent holding registers as a floating point value with the Modbus data members F40001 – F4999.
Chapter 3 Driver and Protocol Objects The Count column contains the accumulated number of messages received from the selected Device that fall into each respective category since the last time the Reset button was pressed. The percent column (%) indicates the percentage of messages received that fall into each respective category since the last time the Reset button was pressed. When you depress the Reset button, the ResetCounts data member is set TRUE, setting all statistical values to zero.
Chapter 2 System Objects Modbus Data Members The Modbus object class supports both 5-digit and 6-digit addressing. When you use a 6 digit address, the left-most digit represents the address type as follows: Table 3-11. 6-Digit Address Coding First Digit Address Type 0 Single-bit coils 1 Discrete inputs 3 Input registers 4 Holding registers The remaining 5 digits represent the actual address of the coil, input or holding register.
Chapter 3 Driver and Protocol Objects Table 3-12. Modbus Data Members (Continued) Data Member Type Read Write Description 400001 – 465000 numeric yes yes 6-digit addresses of 16-bit input registers encoded as unsigned binary integers ranging from 0 to 65535 400001.1 – 465000.16 logical yes yes 6-digit address used to access individual bits out of holding registers and read them as logical ON/OFF values. The least significant bit is 1; the most significant, 16.
Chapter 2 System Objects Table 3-12. Modbus Data Members (Continued) Data Member Type Read Write Description CommFail logical yes no Driver-generated signal that is ON if LookoutDirect cannot communicate with the device for whatever reason D400001 – D465000 numeric yes yes 6-digit addresses of 32-bit unsigned holding register—reads two adjacent holding registers as a single 32-bit number ranging from 0 to 4,294,967,296.
Chapter 3 Driver and Protocol Objects Table 3-12. Modbus Data Members (Continued) Data Member Type Read Write Description PollRate numeric no yes LookoutDirect expression that determines the device polling frequency.
Chapter 2 System Objects When using OffHook, consider defining the driver object PollRate to poll fast when OffHook is TRUE, and poll at its normal rate when OffHook is FALSE. You might tie a Switch object to the OffHook writable data member for this very purpose. Object Reference Manual 3-64 www.Automationdirect.
Chapter 3 Driver and Protocol Objects National Instruments FieldPoint FieldPoint is a protocol driver class LookoutDirect uses to communicate with FieldPoint devices using an enhanced version of the Optomux communication protocol. This object works with the FieldPoint models FP-1000, FP-1001, FP-AI-110, FP-AO-200, FP-DI-330, and FP-DO-400. This protocol uses no parity, eight data bits and one stop bit. In LookoutDirect, a single FieldPoint object represents all devices connected to the same COM port.
Chapter 2 System Objects FieldPoint Explorer to update your .IAK file. If necessary, consult your FieldPoint online help for detailed instructions on using FieldPoint Explorer. To re-import the .IAK file, unselect the Import alias information checkbox and click on OK. Reopen the FieldPoint object dialog box and select the Import alias information checkbox again. When you click on OK, LookoutDirect re-imports the new .IAK file infomation.
Chapter 3 Driver and Protocol Objects The Skip every n setting instructs LookoutDirect to not poll a device it has lost communication with on every scheduled poll. Instead, LookoutDirect skips the device in the polling cycle. Once communications have been reestablished, the device is polled on its regular cycle. IAK configuration file is a dialog for selecting an IAK configuration file. The IAK file contains alias and scaling information which is extracted for use in LookoutDirect.
Chapter 2 System Objects Table 3-13. National Instruments FieldPoint Data Members (Continued) Data Member Type Read Write Description Poll logical no yes When transitioned from low to high, LookoutDirect begins a poll cycle on the device. PollRate numeric no yes Specifies the frequency at which LookoutDirect polls the device. PW000.00 - PW255.15 numeric yes yes Sets the FieldPoint pulse module duty cycle on/off ratio. A setting of 10.
Chapter 3 Driver and Protocol Objects types you are able to select the full range of device addresses and channels. So if you select DO123.03, you need to be certain that the device at address 123 is in fact a discrete output module. For a more complete definition of the function of these data members, see FieldPoint documentation. In the event of a power cycle to the FieldPoint device during use, the configuration of the device reverts to some default state, which is configurable.
Chapter 2 System Objects These data members will not enumerate. You may use them either by importing configurations from FieldPoint Explorer or by entering the data member name explicitly. Note FieldPoint Error Messages No response within timeout period LookoutDirect received no response from a device within the Receive timeout period. The FieldPoint object is able to use the COM port, but when it polls the device, the device does not respond.
Chapter 3 Driver and Protocol Objects FP error: Undefined command The addressed module does not support this command. (for example, trying to write to an input module) Check to see if you are sending a command appropriate to the module. FP error: Checksum error This means the checksum (CRC in this case) failed in a frame sent by LookoutDirect. Check the LookoutDirect receive gap setting. FP error: Input buffer overrun The command sent to the FieldPoint module was too long.
Chapter 2 System Objects FP error: Addressed module does not exist Make sure that you are addressing a valid module address. FP error: Invalid channel One or more channels specified in the command either do not exist or do not support the operation specified. FP error: Invalid range setting Check to see that the range information on the module has not changed, possibly due to a loss of power.
Chapter 3 Driver and Protocol Objects If you are using the National Instruments OPC IATest server, there is no device to poll. Triggering the PollDevice data member returns a zero (0). Simulated data will be restored shortly after such a poll. Note The Server Name box enumerates all of the OPC servers registered on the local computer. Select the appropriate server. The Server Name listbox contains only local servers. It has no effect on what you find when you browse remote servers.
Chapter 2 System Objects enable flat browsing all data members appear in any LookoutDirect windows displaying OPC client data members. If you select Hierarchical, the data members are arranged in hierarchical folders. To browse remote servers, click on the browsing button next to the Remote Server field. The following dialog box appears. Browse for the computer you want, and select the OPC server running on the computer that you want to access.
Chapter 3 Driver and Protocol Objects other system variables, including communications speed and what other tasks are being performed at any particular moment. Update Rate is a numeric expression that determines how often the OPC server updates the client. Enter this time interval in milliseconds. Deadband sets the percentage change that must take place in a data member before the OPC server reports a change in value to LookoutDirect. Poll Device is a logical expression.
Chapter 2 System Objects If you selected flat browsing, you will see a long list of available data members without hierarchical organization into folders. If you did not enable browsing, or your computer cannot browse certain OPC servers, you will only see the data members built into the LookoutDirect OPCClient. The LookoutDirect OPCClient object class currently contains the built-in data members contained in the following table. Table 3-15.
Chapter 3 Driver and Protocol Objects Table 3-15. OPCClient Data Members (Continued) Data Member Type Read Write Description PollDevice logical no yes When transitioned from FALSE to TRUE, the object polls the server. Update logical yes no Pulses high and low when the OPC server updates LookoutDirect or LookoutDirect successfully polls the server. The data members for the OPC Client depend on your OPC server.
Chapter 2 System Objects The access path is Null and the OPC item ID is 4:0. Note You cannot browse access paths for an item. You must enter access paths manually. Object Reference Manual 3-78 www.Automationdirect.
Chapter 3 Driver and Protocol Objects Omron Omron is a protocol driver class LookoutDirect uses to communicate with Omron devices using the Host Link serial communication protocol. An Omron object contains a great deal of data. It supports reading and writing of all predefined data points. When you create an Omron object, you have immediate access to all the data members for that object (see Omron Data Members list in Table 3-16).
Chapter 2 System Objects Parity indicates the parity that LookoutDirect uses to communicate with the hardware device. This Parity setting should match the selection made on the physical device. Phone number specifies the number to be dialed if the selected serial port is configured for dial-up. This Phone number only applies to the individual protocol object. PollRate is a numeric expression that determines how often to poll the device. The object then polls the device at the specified time interval.
Chapter 3 Driver and Protocol Objects Table 3-16. Omron Data Members Data Member Type Read Write Description AR0–AR27 numeric yes yes Auxiliary relay area, read as 16-bit word. AR0.0–AR27.15 logical yes yes Auxiliary relay area, read as 1-bit discrete. DM0–DM9999 numeric yes yes Data memory area, 16-bit word. CommFail logical yes no Object-generated signal that is on if, for any reason, LookoutDirect cannot communicate with the device(s).
Chapter 2 System Objects Cannot set PLC to MONITOR mode The Omron object is trying to set the PLC in MONITOR mode in order to communicate with the PLC correctly, but cannot perform the operation. Incorrect address in response The frame received had an incorrect source address. Check for two or more devices with the same address. Incorrect command in response The frame received had an incorrect command. Check for two or more devices with the same address.
Chapter 3 Driver and Protocol Objects Tiway Tiway is a protocol driver object Lookout uses to communicate with series 5xx PLCs manufactured by Siemens, formerly made by Texas Instruments. Protocol driver objects contain a great deal of data. All readable and writable members (inputs/outputs), polling instructions, read/write blocking, serial port usage, and so on are bundled with the object.
Chapter 2 System Objects Receive timeout is the time delay Lookout uses in waiting for a response from a device before retrying the request. Retry attempts specifies the consecutive number of times Lookout attempts to establish communications with a device it does not get a valid response from. After Retry attempts times, Tiway generates a communication alarm and Lookout moves on to the next device in the polling queue (if any). Alarm priority determines the priority level of Tiway generated alarms.
Chapter 3 Driver and Protocol Objects Local Port The Local port settings determine the serial port, data rate, and phone number (if any) to be used in a direct connect setup. Because the Local port protocol does not include address information, this option is limited to only one (1) PLC per serial port. Unilink Host Adapter If Unilink Host Adapter is selected, you must specify the Serial port to be used and the NIM (Network Interface Module) address as set at the PLC.
Chapter 2 System Objects Enabling Automatic redundant media instructs the Unilink Host Adapter to attempt communications over a redundant TIWAY network to any secondary it loses communications with. The TIWAY I Network Settings configure the communication parameters for the TIWAY network. This network runs between the Unilink Host Adapter and its secondaries. The Lookout default network settings correspond to the default NIM settings as shipped from Siemens.
Chapter 3 Driver and Protocol Objects The PC Adapter Operating Mode determines if the Unilink PC Adapter is the network manager (Master Host Interface Unit) or just another network secondary (Host Interface Unit). There must be exactly one MHIU per TIWAY network. Enabling Automatic redundant media has no effect with the PC Adapter card because it has only one port. If Siemens adds a second port, Lookout automatically supports this option.
Chapter 2 System Objects You can add a secondary IP address to the CTI TCP/IP parameter. Lookout now toggles between the primary and secondary IP address after a COM failure (assuming a secondary address exists). Enter the secondary ID after the first, preceded by a space or a comma. For example: 207.68.156.61, 1.2.3.4 Tiway Data Members Table 3-17.
Chapter 3 Driver and Protocol Objects Table 3-17. Tiway Data Members (Continued) Data Members Type Read Write Description K1 – K32000 numeric yes yes K-memory unsigned 16-bit integer value ranging from 0 to 65535 K1. – K32000.
Chapter 2 System Objects Table 3-17.
Chapter 3 Driver and Protocol Objects Table 3-17. Tiway Data Members (Continued) Data Members Type Read Write Description WX1 – WX32000 numeric yes no Word Image Inputs—16-bit values that typically range from 6400 – 32000 for 4 – 20 mA signals, and 0 – 32000 for 0 – 5V signals. WY1 – WY32000 numeric yes yes Word Image Outputs—16-bit values that typically range from 6400 – 32000 for 4 –20 mA signals, and 0 – 32000 for 0 – 5V signals.
Chapter 2 System Objects Object Reference Manual 3-92 www.Automationdirect.
