Omron DR 170 14 manual Klinkmann Automation Omron Ethernet DAServer

Page 27

Klinkmann Automation Omron Ethernet DAServer

25

Check or uncheck the Slave Mode check box to select the principles how to obtain data from corresponding controller. If Slave Mode is not checked (Master mode) – DAServer polls data from controller all the time. In Slave Mode (if checked) - DAServer requests data from Controller only once – at communication start-up - and then only waits for unsolicited messages from controller (writing to controller is still supported). Communication status is considered as good even if there is no unsolicited data received. To get more reliable communication status in Slave Mode – activate the Watchdog message processing (details see later in this chapter) or time-by-time write values to PLC. With Watchdog activated – Controller’s communication status depends on success of Watchdog messages. Default processing mode is Master mode.

Enter the necessary setting in Gateway Count (GCT) field (the default setting is

2). GCT setting specifies the number of allowed bridge passes in FINS commands sent to PLC; for example, GCT=7 is needed to support new CS/CJ-series CPU Units with Unit Ver. 2.0 or higher.

If necessary – configure Watchdog. The Watchdog would be useful in case the PLC internal program needs to check, whether there is communication with computer where Omron Ethernet DAServer is runnung or not. With Watchdog activated, DAServer time-by-time writes some predefined value (e.g. 255) into predefined address in PLC’s memory (e.g. into D100). At the same time the PLC program must periodically check the current value in this memory address. If value is equal to Watchdog’s predefined value, then PLC’s program considers communication Status as Good and resets the check address to different (non- predefined) value, e.g. to 0. (It will allow to program to check communication state the next time.) If value differs from predefined, then PLC’s program considers communication Status as Bad.

Note: Because of time synchronizing problems with PLC and PC it is recommended to consider the communication Status as Bad only after few consecutive test value mismatch cases, not immediately after the first mismatch.

To activate the Watchdog processing - set Watchdog Time Interval to non-zero value. Value entered in this field indicates the frequency (in seconds) the DAServer sends Watchdog message to corresponding PLC. This value must be a bit less as time interval the PLC program checks the value in watchdog address in the PLC.

Enter Address to Write field to indicate the watchdog address in PLCs memory that is used as Watchdog check address. Address to Write must be a valid item/point name (see Item Names section.)

Note: Use only Word memory areas for Watchdog. Do not take addresses not presented on current PLC configuration. Do not take addresses, used as PLC system areas or in PLC’s program logic. Do not use specific areas, such as Step Area Present Values in CV-series PLCs, or IR or DR areas in CS1-series. If DAServer does not accept memory area for Watchdog – you will see erro r logging in ArchestrA System Management Console’s Log Viewer.

Enter integer from 0 to 65535 into Value to Write field to set Watchdog predefined value. The same value PLC program expects to see in Watchdog check address.

Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4

17014m14

Image 27
Contents Ver 1.x Rev DR 170 Omron Ethernet Direct DAServer User’s GuideContents Contents About This User GuideIndex Overview IntroductionCommunication Protocols Application Communications ProtocolsSuiteLink NetDDE Accessing Items via the DAServerFins Message Communication FastDDEDDE/SuiteLink Demo Mode FeaturesKlinkmann Automation Omron Ethernet DAServer Before starting the Omron Ethernet DAServer Ethernet Unit Configuration Example for CS1 PLC Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Example program for sending unsolicited data from PLC Comments on example program ladder diagramKlinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer To prepare the Omron Ethernet DAServer Getting Started Quickly with the DAServerConfiguring the DAServer NewSOCKET000 by defaultAdd Controller Object To prepare the Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer DASOmronEth Hierarchy in the DAServer Manager To create Socket objects from the Configuration branchHost Name IP Addr Port NumberTo add Controller to your Omron Ethernet hierarchy Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Enabling Software License Key for DASOmronEth Device Group Definitions Configuring Device Group DefinitionsTo make edits on device groups To create or add device groupsKlinkmann Automation Omron Ethernet DAServer To configure default update intervals To delete device groupsScan-Based Message Handling To use different configuration sets from the current one Configuring Device Item DefinitionsArchiving Configuration Sets To archive configuration setsTo add item references Device Item DefinitionsName Item Reference To create or add device itemsHot Configuration Klinkmann Automation Omron Ethernet DAServer Pn-PhS Item Name General FormatPnS Pnb or Pnbb or Pn.b or Pn.bbAscii Strings Format BCD FormatLong Format Signed/BCD Floating Point Format IEEE/BCDRead WriteImortant Note CS1/CJ1 PLCs = a To M= a Klinkmann Automation Omron Ethernet DAServer C200HX/C200HG/C200HE PLCs CV-series PLCs PVS Step Status Flag or Bit StatusCPM2x PLCs Klinkmann Automation Omron Ethernet DAServer CQM1 PLCs DAServer Standard System Items System Item Type Description Values System Item Type Description Values Name Access RightsDAServer Global System Item DAServer Device-Specific System ItemsKlinkmann Automation Omron Ethernet DAServer Range DAServer Device-Group-Specific System ItemsRange AREA10.VESSEL1.TIC1.PLC.D100 Generic OPC SyntaxYourOPCAccessPath.$SYS$Status Monitoring Connectivity Status with the PLC=DASOmronEthPLC!$SYS$Status Using DDEStatus and IOStatus in Excel Monitoring the Status of DAS ConversationsReading Values from the DAServer into Excel =TERMINATEchannel Writing Values to the DAServer from ExcelChannel=INITIATEapplicationname,topicname =POKEchannel,itemname, DataReferenceError Messages and Codes DAServer Error MessagesError Message Explanation Probable Cause Solution Log Flag Item Names Creating write Invalid value poked Check Item’s DASProtFail Data, received Take into DASProtWarn Main Code Sub Probable Cause Remedy Log Flag Hex Server-Specific Error CodesError code Logger Message Log Flag Fins Response CodesKlinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer Klinkmann Automation Omron Ethernet DAServer DAServers DAServer ArchitecturePlug-ins DAS EnginePLC Protocol Layer Component Environments Klinkmann Automation
Related manuals
Manual 67 pages 16.17 Kb

DR 170 14 specifications

The Omron DR 170 14 is a leading-edge digital infrared thermometer that has established a strong reputation for its accuracy and efficiency in measuring body temperature. This advanced device is particularly noted for its user-friendly design, making it suitable for both medical professionals and home use.

One of the key features of the Omron DR 170 14 is its non-contact measurement capability, allowing users to obtain temperature readings from a distance of about 1-3 centimeters. This feature is crucial in minimizing the risk of cross-contamination, especially in healthcare settings. The thermometer utilizes infrared technology to detect the infrared energy emitted by the body, ensuring quick and reliable readings in just seconds.

The Omron DR 170 14 also boasts a large, easy-to-read LCD display that provides clear visibility of temperature readings. This display is backlit, allowing for usage in low-light conditions, making it convenient during nighttime monitoring of children's temperatures.

Furthermore, the device includes a memory function that can store multiple temperature readings, assisting users in tracking fever patterns over time. This feature is invaluable for caregivers and healthcare providers as it allows for better assessment and decision-making regarding treatment plans.

In terms of accuracy, the Omron DR 170 14 is equipped with advanced measurement algorithms that enhance precision in readings, positioning it as a reliable option for temperature measurement. The thermometer can measure not only body temperature but also surface temperatures of objects and liquids, providing versatility beyond just clinical settings.

Another notable characteristic is its compact and lightweight design, which makes it highly portable and easy to carry around, whether in a medical bag or a home setting. The thermometer is also powered by batteries, ensuring that it remains operational even in case of power outages.

Overall, the Omron DR 170 14 stands out for its combination of modern technology, ease of use, and reliable performance. With its non-contact functionality, rapid readings, and memory features, it serves as an essential tool for anyone needing accurate temperature assessments, whether in a clinical or home environment. The thermometer exemplifies Omron's commitment to creating healthcare solutions that are not only innovative but also accessible to a wide range of users.