text:
Are you sure?
This action might not be possible to undo. Are you sure you want to continue?
zED, zED-P, zED-LCD, zED-LCD-AA, zED-CCELL, zED-DCELL, zCDR
Operator's Manual
NEWPORT Electronics, Inc.
Additional products from
NEWPORT Electronics, Inc.
Counters Frequency Meters PID Controllers Clock/Timers Printers Process Meters On/Off Controllers Recorders Relative Humidity Transmitters Thermocouples Thermistors Wire Wireless Rate Meters Timers Totalizers Strain Gauge Meters Voltmeters Multimeters Soldering Iron Testers pH pens pH Controllers pH Electrodes RTDs Thermowells Flow Sensors
It is the policy of NEWPORT to comply with all worldwide safety and EMC/EMI regulations that apply. NEWPORT is constantly pursuing certification of its products to the European New Approach Directives. NEWPORT will add the CE mark to every appropriate device upon certification. WARNING: These products are not designed for use in, and should not be used for, patient connected applications.
NEWPORTnet On-Line Service www.newportUS.com
In the U.S.A. and Canada: 1-800-NEWPORT In Mexico: (95) 800-NEWPORTSM Or call your local NEWPORT Office.
For Immediate Assistance
Internet e-mail firstname.lastname@example.com
The information contained in this document is believed to be correct but NEWPORT Electronics, Inc. accepts no liability for any errors it contains, and reserves the right to alter specifications without notice.
TRADEMARK NOTICE: , NEWPORT®, NEWPORT® and newportUS.com are trademarks of NEWPORT Electronics, Inc. PATENT NOTICE: This product is covered by one or more of the following patents: U.S. Pat. No. Des. 336,895; 5,274,577/ CANADA 2052599; 2052600/ ITALY 1249456; 1250938 / FRANCE BREVET No. 91 12756 / SPAIN 2039150; 2048066 / UK PATENT No. GB2 249 837; GB2 248 954 / GERMANY DE 41 34398 C2. The ® is a Trademark of OMEGA Engineering, Inc. Used Under License. Other US and International Patents pending or applied for. This device is marked with the international caution symbol. It is important to read the Setup Guide before installing or commissioning this device as it contains important information relating to safety and EMC.
Part 3: Network Configuration 3.1 Ethernet (MAC) Address ...........................................................................24 3.2 Network Protocols .....................................................................................24 3.3 DHCP .......................................................................................................24 3.4 DNS .......................................................................................................25 3.5 IP Address ..................................................................................................25 3.5.1 Default IP Address........................................................................25 3.5.2 Changing TCP/IP Properties on Your Computer .......................26
Part 1: Introduction 1.1 Safety and EMC Considerations .................................................................2 1.2 Before You Begin .........................................................................................2 1.3 Description....................................................................................................2 Part 2: Hardware 2.1a Parts of the End Device - zED-P/-LCD/-AA ................................................5 2.1b Parts of the End Device - zED/-CCELL/-DCELL .........................................6 2.1c Parts of the End Device - zED-AA-H/zED-LCD-AA-H ................................7 2.1d Parts of the End Device - zED .....................................................................8 2.2a Dimensions and Mounting - End Device - zED-P/-LCD/-AA/-DCELL/-H 9 2.2b Dimensions and Mounting - End Device - zED .......................................10 2.3 External Sensors/Probes for the End Device ........................................10 2.4a Disassembly - End Device - zED-x-P/-LCD ..............................................11 2.4b Disassembly - End Device - zED-x-LCD-AA.............................................12 2.4c Disassembly - End Device - zED-x-CCELL ..............................................13 2.4d Disassembly - End Device - zED-x-DCELL ..............................................14 2.4e Disassembly - End Device - zED-x-AA-H and zED-x-LCD-AA-H ............15 2.4f Disassembly - End Device - zED...............................................................16 2.5 Parts of the Coordinator ............................................................................17 2.6 Dimensions and Mounting - Coordinator.................................................18 2.7 DIP Switches...............................................................................................19 2.7.1 DIP Switch Setup: Device ID (DID) .............................................19 2.7.2 DIP Switch Setup: Network ID (NID) ...........................................21 2.7.3 DIP Switch Setup: Ethernet - Coordinator .................................22 2.8 Network Communication Interfaces ........................................................23 2.8.1 10Base-T RJ-45 Pinout.................................................................23 2.8.2 10Base-T Crossover Wiring.........................................................23 2.9 Thermocouple Wiring ...............................................................................23
Part 4: Operations 4.0 Testing the Connection .............................................................................27 4.1 iConnect Software......................................................................................28 4.2 Setting a new IP Address over the Network ...........................................30 4.3 Coordinator's Configurations and Operations .......................................31 4.3.1 Power Up Device ..........................................................................32 4.3.2 Get Readings from the End Device ............................................33 4.3.3 Java Runtime Environment Setup .............................................35 126.96.36.199 Java Runtime Environment 1.4 Setup Instructions...................35 188.8.131.52 Java Runtime Environment 1.5 (5.0) Setup Instructions ..........36 126.96.36.199 Browser Proxy Selection .............................................................37 4.3.4 Java Policy ....................................................................................38 4.3.5 Chart ..............................................................................................40
4.3.6 4.4 4.5 4.6 4.7 4.8 Diagnostic ...................................................................................................42 4.3.7 Configuration ................................................................................43 4.3.8 Sensor Setup.................................................................................44 4.3.9 Access Control ............................................................................48 Telnet Setup ...............................................................................................49 HTTPget Program ......................................................................................49 4.5.1 HTTPget using Port 2000 ............................................................50 4.5.2 HTTPget and ARP to Setup Device IP Address ........................50 ARP Protocol ..............................................................................................52 iLog Software..............................................................................................53 Mail Notifier Software.................................................................................55 4.8.1 Installation.....................................................................................55 4.8.2 Program Options Setup and Configuration ..............................56 4.8.3 Device Setting Setup and Configuration ....................................57 4.8.4 Sending Text Messages to a Cell Phone........................................58
Part 5: Environment / Operating Conditions ......................................................................59 5.1 General Deployment Guidelines .............................................................. 59 5.2 With Line-of-Sight ......................................................................................61 5.3 Without Line-of-Sight ................................................................................62 5.4 Casing and Closure Around the Antenna ................................................62 5.5 Fine Adjustment in Performance ..............................................................63
Part 6: Specifications .......................................................................................................... 64
Appendix E Appendix F Appendix G Appendix H Appendix I
Appendix A Appendix B Appendix C Appendix D
Part 7: Factory Preset Values ..............................................................................................69
Glossary ......................................................................................................70 IP Address ..................................................................................................71 IP Netmask ..................................................................................................72 ASCII Chart ................................................................................................73 ASCII Chart Control Codes .......................................................................74 iLog Error Messages..................................................................................75 ASCII / Telnet Commands Table ...............................................................76 Frequently Asked Questions (FAQ)..........................................................78 Warnings and Regulatory Information .....................................................80 Sensor Information ....................................................................................81
Figure 2.5 Figure 2.6 Figure 2.7 Figure 2.8 Figure 2.9 Figure 2.10 Figure 2.11 Figure 2.12 Figure 3.1 Figure 3.2 Figure 3.3 Figure 4.1 Figure 4.2 Figure 4.3 Figure 4.4 Figure 4.5 Figure 4.6 Figure 4.7 Figure 4.8 Figure 4.9 Figure 4.10 Figure 4.11 Figure 4.12 Figure 4.13 Figure 4.14 Figure 4.15 Figure 4.16 Figure 4.17 Figure 4.18 Figure 4.19 Figure 4.20a Figure 4.20b Figure 4.21 Figure 4.22
Figure 1.1 Figure 2.1a Figure 2.1b Figure 2.1c Figure 2.1d Figure 2.2a Figure 2.2b Figure 2.3 Figure 2.4a Figure 2.4b Figure 2.4c Figure 2.4c Figure 2.4e Figure 2.4f
Parts of the Coordinator ...........................................................................17 Mounting the Coordinator .......................................................................18 Device ID (DID) - 8 Position DIP Switch Setup ........................................19 Network ID (NID) - 8 Position DIP Switch Setup .....................................21 Ethernet - 4 Position DIP Switch Setup ...................................................22 RJ45 Pinout ................................................................................................23 10Base-T Crossover Cable Wiring ...........................................................23 Thermocouple Wiring & TC Wire Color Chart ........................................23 4 Position DIP Switch on Bottom Side of Coordinator ..........................24 Network Connections ...............................................................................26 Network Connections ...............................................................................26 Pinging the Coordinator from MS-DOS Prompt .....................................27 Assigning an IP Address using iConnect ...............................................28 Accessing the zSeries System for Configuration ..................................29 Access Control .........................................................................................30 Home Page Menu .....................................................................................31 Login and Administrator Password .........................................................31 Select Readings by Group .......................................................................33 Readings .....................................................................................................33 Comma Separated Value Format ...........................................................34 Java 1.4.2.x Screen Shot ...........................................................................35 Java 1.5.x.x Screen Shot ...........................................................................36 Java Policy..................................................................................................38 Java Policy..................................................................................................39 Select Chart by Group ...............................................................................40 Chart - End Device #1 LAB 50 ................................................................40 Diagnostic ...................................................................................................42 Configuration ............................................................................................43 Sensor Setup by Group .............................................................................44 Sensor Setup ..............................................................................................45 Sensor Parameters ....................................................................................46 Sensor Parameters for Thermocouple Option .......................................47 Access Control ..........................................................................................48 HTTPget Example of Polling End Device #1, 2, 3, 4 ................................50
zSeries Wireless System on the Ethernet Network...................................4 Parts of the End Device - zED-P/-LCD/-AA ................................................5 Parts of the End Device - zED-CCELL/-DCELL .........................................6 Parts of the End Device - zED-AA-H/zED-LCD-AA-H ...............................7 Parts of the End Device - zED ....................................................................8 Mounting the End Device - zED-P/-LCD/-AA/-DCELL/-H ..........................9 Mounting the End Device - zED ................................................................10 External Sensors/Probes...........................................................................10 Disassembly of the End Device - zED-x-P/LCD .......................................11 Disassembly of the End Device - zED-x-LCD-AA ....................................12 Disassembly of the End Device - zED-x-CCELL......................................13 Disassembly of the End Device - zED-x-DCELL......................................14 Disassembly of the End Device - zED-x-LCD-AA-H ...............................15 Disassembly of the End Device - zED ......................................................16
Figure 4.23 Figure 4.24 Figure 4.25 Figure 4.26 Figure 4.27 Figure 5.1 Figure 5.2 Figure 5.3 Figure 5.4 Figure I.1 Figure I.2 Figure I.3 ARP Commands and Responses .............................................................52 iLog Software Logging Data for End Device #1, 3, 4 ..............................53 Mail Notifier Main Window .........................................................................55 Mail Notifier Profile Setup..........................................................................56 Mail Notifier Device Setting ......................................................................58 Operation in Buildings ..............................................................................60 Fresnel Zone ..............................................................................................61 Materials in Buildings ...............................................................................62 Channels ....................................................................................................63 RH Accuracy Chart ..................................................................................81 Temperature Accuracy Chart ...................................................................81 Normal Range ............................................................................................81
Table 4.1 Table 4.2 Table 6.1 Table 6.2
iLog Excel Applications.............................................................................54 Mail Notfier Commands .............................................................................57 Thermocouple Chart ..................................................................................65 Estimated Battery Lifetime Chart..............................................................67
Information that is especially important to note is identified by the following labels: • NOTE • WARNING or CAUTION • IMPORTANT • TIP
NOTES, WARNINGS and CAUTIONS
NOTE: Provides you with information that is important to successfully setup and use the zSeries Wireless System. CAUTION or WARNING: Tells you about the risk of electrical shock. CAUTION, WARNING or IMPORTANT: Tells you of circumstances or practices that can affect the instrument's functionality and must refer to accompanying documents. TIP: Provides you helpful hints.
Web Server Email Alarms Temperature Humidity Barometric Pressure Dual Thermocouple Input No Special Software Required
PART 1 INTRODUCTION 1.1 Safety and EMC Considerations Refer to the Environment/Operating Conditions Section.
• Plastic connector of the antenna • LCD display • Metal connectors for signal and power • Metal body of the sensor probe EMC Considerations • Whenever EMC is an issue, always use shielded cables. • Never run signal and power wires in the same conduit. • Use twisted-pair wires for signal connections. • Install Ferrite Bead(s) on signal wires close to the instrument if EMC problems persist. Failure to follow all instructions and warnings may result in injury! 1.2 Before You Begin Inspecting Your Shipment: Remove the packing slip and verify that you have received everything listed. Inspect the container and equipment for signs of damage as soon as you receive the shipment. Note any evidence of rough handling in transit. Immediately report any damage to the shipping agent. The carrier will not honor damage claims unless all shipping material is saved for inspection. After examining and removing the contents, save the packing material and carton in the event reshipment is necessary. Customer Service: If you need assistance, please contact the Customer Service Department nearest you. Manuals, Software: The latest Operation Manual as well as free configuration software (iConnect), data-logging software (iLog) and Mail Notifier are available at the website listed on the cover page of this manual or on the CD-ROM enclosed with your shipment. 1.3 Description The zSeries wireless sensor system provides Web-based monitoring of Temperature, Humidity, and Barometric Pressure in critical HVAC and Refrigeration applications. The compact wireless "End Devices" mount discretely on the wall in clean rooms, laboratories, museums, computer server rooms, warehouses, and any remote facility. Compact End Devices (zED) are powered by two AA 1.5V alkaline batteries. High performance, high power End Devices in NEMA4 enclosures come with two choices. The AC version (zED-P/-LCD) is powered by a 5 Vdc universal AC power adapter that operates on any voltage worldwide (110 to 240 Vac). Should AC power fail, the unit can operate on a 3.6V ultra-long-life lithium back-up battery (included). A number of completely wireless wireless End Devices are powered by two AA (zED-LCD-AA), two C-cell (zED-CCELL), or two D-cell (zED-DCELL) alkaline batteries. These End Devices can operate for weeks, months, or years before changing the batteries. Battery life depends on the type of sensor and other user settings such as the frequency of transmission. The zED-DCELL version is not recommended for shock, vibration or in moving equipment.
Warning: the following parts of the unit are ESD sensitive:
1.3 Description (continued) The End Devices transmit up to 300 feet/91m (zED) or 3280 feet/1000m (zED-P/-LCD/ -AA/-CCELL/-DCELL), without obstructions or interference, to a "Coordinator" connected directly to an Ethernet network and the Internet. The wireless system complies with IEEE 802.15.4 operating at 2.4 GHz and the user can switch to different communication channels to avoid interference with other wireless technologies (e.g. Wi-Fi). To achieve robust and reliable wireless communication, End Devices retransmit data adaptively to the environment so that power consumption is optimized in harsh conditions. The Coordinator also provides error detection mechanism for inactive communication and diagnostic information including signal strength and data transmission success rate to help trouble shooting potential wireless system installation issues. The zSeries system allows you to monitor and record Temperature, Relative Humidity, and Barometric Pressure over an Ethernet network or the Internet without any special software-just your Web Browser. We offer a selection of End Devices for a variety of applications. End Devices can take thermocouple types J, K, T, E, R, S, B, C, N and L (DIN J) measuring temperatures up to 2320ºC from two different locations. Also, End Devices are available with built-in sensors, with external sensor probes, and with both built-in and external sensors. The external sensors are designed for harsh environments such as outdoor weather, in HVAC ducts, freezers and refrigerators. For example, you can select one End Device that has one internal and one external sensor to monitor temperature and humidity both inside and outside a climate-controlled facility. Each zSeries Coordinator can directly support up to thirty-two (32) End Devices and a maximum of 8 Coordinators can be setup in the vicinity. The Coordinators include AC adapters to operate on any voltage worldwide from 100 to 240 Vac and 50 to 60Hz. The Coordinator connects directly to an Ethernet Network or the Internet. Unlike an RS232 or USB device, it does not require a host computer. The zSeries Coordinator is an independent node on the network sending and receiving data in standard TCP/IP packets. It is easily configured from a Web Browser and can be password protected. From within an Ethernet LAN or over the Internet, the user simply types the IP address (such as 192.168.1.200) or an easy to remember name (such as "ServRoom" or "Chicago5") and the Coordinator serves a Web Page with the current readings. The device can trigger an alarm if variables go above or below a set point that you determine. Your alarm can be sent by email to a single user or to a group distribution list, including text messages to Internet enabled cell phones and PDA's. The "Mail Notifier" software is free and easy to use program for this application. The zSeries wireless sensor system is easy to install, simple to operate, and features award-winning iServer technology with an Embedded Web Server that requires no special software. The zSeries system serves Active Web Pages to display real time readings and charts of temperature, humidity, and barometric pressure. You can also log data in standard data formats for use in a spreadsheet or data acquisition program such as Excel or Visual Basic. iLog is a free and easy to use program for logging data to Excel. The virtual chart viewed on the web page is a Java™ Applet that records a chart over the LAN or Internet in real time. With the zSeries system there is no need to invest time and money learning a proprietary software program to log or chart the data.
1.3 Description (continued) Chart scales are fully adjustable on the fly. For example, the chart can display one minute, one hour, one day, one week, one month or one year. Temperature and humidity can be charted across the full span (-40 to 125°C, and 0 to 100% RH) or within any narrow range such as (20 to 30°C). The OPC Server software makes it easy to integrate the zSeries wireless sensor system with many popular Data Acquisition and Automation programs offered by Omega, Wonderware, iConics, Intellution, Rockwell Automation, and National Instruments, among others. The following example illustrates how you can hookup zSeries wireless system to your network: The zSeries wireless system consists of a single Coordinator and one or more End Devices. End devices will send data periodically to the Coordinator where it serves as a gateway between the users and the End Devices. The users can access the data through the Coordinator's web server and provided data acquisition software. A standard web browser can be used to monitor and chart temperature, humidity, and barometric pressure. The browser can also be used to configure the device's IP address, passwords for access and overall configuration parameters.
Figure 1.1 zSeries Wireless System on the Ethernet Network
2.1a Parts of the End Device (zED-P/-LCD/-AA)
Warning: the following parts are ESD sensitive.
15 1 2 9 16 10
6 5 3 4
+ +
Unit Addr Group Net. Addr
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
8 position DIP switch (under cover), sets the NID and DID of the End Device (see Section 2.7 for details) Power Switch Label for Unit Address, Group No. and Network ID Address (NID) Wall mounting holes Label with model and serial numbers Radio module firmware revision location on label Case's tray, where the PCB, sensor and batteries are mounted Case's cover Transmit LED (blue) 4 Screws attaching Cover External probe/sensor, through cable gland (for zED-TC-x) or quick disconnect connector . Refer to Figure 2.2a for connector configurations. Power Input, through quick disconnect connector (for zED-P & zED-LCD) Antenna Mount Thermocouple (if ordered) removable terminal block connector (under cover) LCD Display (for zED-LCD & zED-LCD-AA) Two AA alkaline batteries (for zED-LCD-AA) or one lithium back-up battery (for zED-P & zED-LCD) (located under cover) Figure 2.1a Parts of the End Device (zED-P/-LCD/-AA)
2.1b Parts of the End Device (zED-CCELL/zED-DCELL)
11 2 6 5 3 4
Unit Addr Group Net. Addr
9 1 14 10
Warning: the following parts are ESD sensitive.
2 3 4 5 6 7 8 9 10 11 12 13 14
8 position DIP switch (under cover), sets the NID and DID of the End Device (see Section 2.7 for details) Power Switch (under cover) Label for Unit Address, Group No. and Network ID Address (NID) Wall mounting holes Label with model and serial numbers Radio module firmware revision location on label Case's tray, where the PCB, sensor and batteries are mounted Case's cover Transmit LED (blue) Four (4) Screws attaching Cover Two (2) C-cell or D-cell batteries (under cover) External probe/sensor, through cable gland (for zED-TC-x) or quick disconnect connector . Refer to Figure 2.2a for connector configurations. Antenna Mount Thermocouple (if ordered) removable terminal block connector (under cover) Figure 2.1b Parts of the End Device (zED-CCELL/zED-DCELL)
2.1c Parts of the End Device (zED-AA-H/zED-LCD-AA-H)
13 2 1
14 9
Unit Addr Group Net. Addr
2 3 4 5 6 7 8 9 10 11 12 13 14
8 position DIP switch (under cover), sets the NID and DID of the End Device (see Section 2.7 for details) Power Switch (under cover) Label for Unit Address, Group No. and Network ID Address (NID) Wall mounting holes Label with model and serial numbers Radio module firmware revision location on label Case's tray, where the PCB, sensor and batteries are mounted Case's cover Transmit LED (blue) Four (4) Screws attaching Cover Two (2) AA alkaline batteries (under cover) External probe/sensor, through quick disconnect connector . Refer to Figure 2.2a for connector configurations. Antenna Mount LCD Display (if ordered) Figure 2.1c Parts of the End Device (zED-AA-H/zED-LCD-AA-H)
2.1d Parts of the End Device (zED)
12 3 4 5 6
Unit Addr Group Net. Addr
11 1
2 3 4 5 6 7 8 9 10 11 12
8 position DIP switch (under cover), sets the NID and DID of the End Device (see Section 2.7 for details) Power Switch Label for Unit Address, Group No. and Network ID address (NID) Wall mounting holes Label with model and serial numbers Radio module firmware revision location on label Case's tray, where the PCB, sensor and batteries are mounted Case's cover Transmit LED (blue) Case's latch: squeeze sides to pull the cover off Cable for optional external probe with sensor Optional rear entry for external probes Figure 2.1d Parts of the End Device (zED)
2.2a Dimensions and Mounting - End Device (zED-P/-LCD/-LCD-AA/-CCELL/-DCELL/-H)
DIMENSIONS ARE Dimensions are in InchesIN INCHES with MM in [ ]. WITH MM IN [ ]. Material: Polycarbonate Makrolon Protection: NEMA4/IP65 rated housing
3.23 [82.0] 2.046 [51.97]
0.236 [5.99]
0.59 [15.0]
1) Position unit where required. Mark and drill holes as required, using a #6 screw. 2) Attach antenna (refer to Section 5 for Environmental/Operating Conditions) and attach power supply.
1.56 [39.7]
4.24 [107.7]
5.35 [135.8]
4.873 [123.77]
zED-THP2-AA-H zED-THP2-LCD-AA-H
(mounting pattern same as vertical models)
1.75 [44.5] 2.25 [57.2]
3.08 [78.1]
zED-TC-CCELL zED-TC-LCD-AA zED-THP-CCELL/-DCELL/-LCD-AA zED-TP1-CCELL/-DCELL/-LCD-AA zED-TP2-CCELL/-DCELL/-LCD-AA zED-BTP-CCELL/-DCELL/-LCD-AA zED-BTHP-CCELL/-DCELL/-LCD-AA
(earlier gland version)
1.0 [25]
Figure 2.2a Mounting the End Device (zED-P/-LCD/-AA/-CCELL/-DCELL/-H)
2.2b Dimensions and Mounting - End Device (zED) Position unit where required. Mark and drill holes as required, using a #6 screw.
Optional External Sensor
Material: PBT (Valox)
3.61 [91.8]
0.94 [23.8]
2.54 [64.5]
0.32 [8.1]
2.3 External Sensors/Probes for the End Device
Figure 2.2b Mounting the End Device (zED)
1.90 [48.3]
FROM TOP TO BOTTOM: 1) External Industrial Probe , Temperature / Humidity -THP or Barometric Pressure / Temperature -BTP, -BTHP 2) External Temperature Stick Probe -TP1 3) External Temperature Lug Mount Probe -TP2
Figure 2.3 External Sensor/Probes
1.81 [45.9]
2.4a Disassembly - End Device (zED-x-P/-LCD or zED-TC-P/zED-TC-LCD) You may need to open the unit for one of the following reasons: • To turn on Power Switch. • To mount unit to wall. Refer to Figure 2.2a for mounting dimensions. • To connect or replace the 3.6 Vdc lithium back-up battery, (note the polarity of battery). • To access Thermocouple's Terminal Block Connector. • To access programming connector. Remove Cover as shown below, by removing the 4 Cover Mounting Screws.
8 1
1 1
8 1
6 1
Figure 2.4a Disassembly of the End Device (zED-x-P/zED-x-LCD or zED-TC-P/zED-TC-LCD)
2.4b Disassembly - End Device (zED-x-LCD-AA or zED-TC-LCD-AA) You may need to open the unit for one of the following reasons: • To turn on Power Switch. • To mount unit to wall. Refer to Figure 2.2a for mounting dimensions. • To connect or replace the AA alkaline batteries, (note the polarity of battery). • To access Thermocouple's Terminal Block Connector. • To access programming connector. Remove Cover as shown below, by removing the 4 Cover Mounting Screws.
8 1
6 1
Figure 2.4b Disassembly of the End Device (zED-x-LCD-AA or zED-TC-LCD-AA)
2.4c Disassembly - End Device (zED-x-CCELL or zED-TC-CCELL) You may need to open the unit for one of the following reasons: • To turn on Power Switch. • To mount unit to wall. Refer to Figure 2.2a for mounting dimensions. • To connect or replace the two C-cell alkaline batteries, (note the polarity of batteries). • To access Thermocouple's Terminal Block Connector. • To access programming connector. Remove Cover as shown below, by removing the 4 Cover Mounting Screws.
1 6
Figure 2.4c Disassembly of the End Device (zED-x-CCELL or zED-TC-CCELL)
2.4d Disassembly - End Device (zED-x-DCELL or zED-TC-DCELL) You may need to open the unit for one of the following reasons: • To turn on Power Switch. • To mount unit to wall. Refer to Figure 2.2a for mounting dimensions. • To connect or replace the two D-cell alkaline batteries, (note the polarity of batteries). • To access Thermocouple's Terminal Block Connector. • To access programming connector. Remove Cover as shown below, by removing the 4 Cover Mounting Screws.
Figure 2.4d Disassembly of the End Device (zED-x-DCELL or zED-TC-DCELL)
2.4e Disassembly - End Device (zED-x-AA-H or zED-x-LCD-AA-H) You may need to open the unit for one of the following reasons: • To turn on Power Switch. • To mount unit to wall. Refer to Figure 2.2a for mounting dimensions. • To connect or replace the AA alkaline batteries, (note the polarity of battery). • To access programming connector. Remove Cover as shown below, by removing the 4 Cover Mounting Screws.
8 1
Figure 2.4e Disassembly of the End Device (zED-x-AA-H or zED-x-LCD-AA-H)
2.4f Disassembly - End Device (zED) You may need to open the unit for one of the following reasons: • To turn on Power Switch. • To mount unit to wall. Refer to Figure 2.2b for mounting dimensions. • To connect or replace the two 1.5 Vdc AA alkaline batteries, (note the polarity of batteries). • To access programming connector. Remove Cover as shown below, by pressing sides of cover to release latches.
8 1
Figure 2.4f Disassembly of the End Device (zED)
2.5 Parts of the Coordinator
1 2 3 4 5 6 7 8 9
10 11 12 13 14
15 16
Wall mounting bracket clip holes (3 places) Label with model and serial numbers Coordinator's firmware revision on label 8 position DIP switch, from which the last 3 positions are used to assign the NID, network ID number (see Section 2.7 for details) Ethernet: RJ45 interface for 10BASE-T connection. Case's tray, where the PCB is mounted 4 position DIP switch, sets the DHCP and Factory Defaults Coordinator's radio module firmware revision on label Label with default IP address, remove and then write your IP address, in the space provided Label with MAC address (in hex code) Wall mounting bracket Case's cover mounting screw (2 places) Label for Network ID address (NID) Power supply: Plus (+) power supply wire connection inside the plug; Minus (-) power supply wire connection outside the plug Reset button: Used for power reseting the Ethernet board Case's cover
Figure 2.5 Parts of the Coordinator
2.5 Parts of the Coordinator (continued)
2.6 Dimensions and Mounting - Coordinator Position unit where required. Mark and drill the two #4 screw holes. Once the bracket is mounted to the wall: align back of unit over the three bracket clips, when engaged, slide downward, the unit will snap in place If unit is to be mounted on a flat surface, you may take the bottom rubber feet off the unit.
17 Diagnostics LED: (Yellow and Green) Diagnostics: at boot-up they light up for 2 seconds, then turn off; DHCP: if DHCP is enabled, they blink and stay solid periodically Network Link LED: (Green) Solid: Indicates good network link. Activity LED: (Red) Blinking: Indicates network activities (receiving or sending packets). 18 Receive LED (blue) while blinking, the Coordinator looks for the clearest channel to communicate. Once it finds that channel, the light will change to solid. 19 Antenna connector 20 Power LED: (Green) Solid: Indicates Power-ON
Material: Steel
Figure 2.6 Mounting the Coordinator
2.7 DIP Switches 2.7.1 DIP Switch Setup: Device ID (DID)
The End Device is shipped with all DIP switches in the "OFF" position.
1 (Shown in "OFF" Position)
+ +
AA Alkaline Battery AA Alkaline Battery
End Device: zED
C-cell or D-cell Alkaline Battery
C-cell or D-cell Alkaline Battery
THERMOCOUPLE INPUT BOARD (if -TC Ordered)
6 5 4 3 2 1
THERMOCOUPLE INPUT BOARD (if -TC Ordered)
+ +
6 5 4 3 2 1
Lithium Back-up Battery (For -P or -LCD only)
AA Battery
AA Battery (For LCD-AA only)
End Device: zED-CCELL, zED-DCELL
Figure 2.7 Device ID (DID) - 8 Position DIP Switch Setup
End Device: zED-P, zED-LCD, zED-LCD-AA
2.7.1 DIP Switch Setup: Device ID (DID) continued
For each End Device you can setup the unique Device ID using DIP switch #1 - 5.
The Device ID also determines the Group of the End Device. The Coordinator puts every eight End Devices into a Group so that the system is more manageable. You can setup the Network ID (NID) (which is the same as the Coordinator's) with DIP switches # 6 - 8. Refer to Section 2.7.2.
Device ID 0 1 2 3 4 5 6 7 8 GROUP B 10 12 13 14 15 11 9 GROUP A OFF OFF OFF OFF OFF OFF OFF OFF ON ON ON ON ON ON ON ON 1 OFF OFF ON ON 2 OFF OFF OFF OFF ON ON ON OFF OFF ON ON ON ON OFF OFF ON 3 OFF OFF OFF OFF OFF OFF OFF OFF ON ON ON ON ON ON 4 OFF OFF OFF OFF OFF OFF OFF OFF OFF GROUP D OFF OFF OFF OFF OFF 5 Device ID 16 17 GROUP C 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 OFF OFF OFF OFF OFF OFF OFF OFF ON ON ON ON ON ON ON ON 2 OFF ON ON OFF 3 OFF OFF ON ON ON ON OFF OFF 4 OFF OFF OFF OFF ON ON ON ON ON ON ON ON OFF OFF OFF OFF 5 ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
2.7.2 DIP Switch Setup: Network ID (NID) Each sensor network has a unique Network ID (or NID). For the End Device (see Figure 2.7) and the Coordinator (see Figure 2.8) setup the Network ID with DIP switches #6 - 8 If there is no other IEEE 802.15.4 system, the default NID can be used where all three dip switches are OFF.
Coordinator Rear View
nd Device: Figure 2.8 Network ID (NID) - 8 Position DIP Switch Setup Coordinator h cover removed Rear View NID PID #6 #7 #8 with cover removed 13106 (0x3332) 0 OFF OFF OFF om tray not shown
13107 (0x3333) 13108 (0x3334) 13109 (0x3335) 13110 (0x3336) 13112 (0x3338) 13113 (0x3339) 13111 (0x3337) 1 2 3 OFF ON ON ON OFF ON ON OFF ON ON ON OFF OFF ON 4 6 7 OFF OFF ON OFF ON ON
(Shown in "OFF" Position)
6 7 8
2-5 not used
Definitions: DID (Device ID): The first 5 DIP switches used to assign a device number to an End Device. NID (Network ID): The last 3 DIP switches used to assign a unique network number to a network of a Coordinator and End Device(s). PID (Personal Network ID): The sum of the Network ID (NID) and 13106 (0x3332). The PID as defined by IEEE for 802.15.4 standard is an identifying factor for separating 802.15.4 wireless networks to avoid overlapping and allow interoperability. Once the End Devices and the Coordinator start communicating, make sure to push DIP switch #1, located on the back of the Coordinator to the ON position. This will lock the Coordinator on the same channel it initially established the connection. It's a good practice to record NID and DID numbers on designated labels placed on the Coordinator and End Devices, see Figure 2.1 and 2.5.
2.7.3 DIP Switch Setup: Ethernet - Coordinator
Coordinator Rear View
Figure Coordinator 2.9 Ethernet - 4 Position DIP Switch Setup Rear the Coordinator to factory default settings: To set View
ON (Shown in "OFF" Position)
1) N/C 2) To change Ethernet settings to factory default 3) To enable/disable DHCP 4) N/C
1) Slide DIP switch #2 to ON position. 2) Power the Coordinator on and wait about 10 seconds until the Coordinator fully boots up. 3) Set the DIP switch #2 back to OFF position (it does not matter if the Coordinator is powered ON or OFF, just make sure that the DIP switch is set to OFF, otherwise, every time the unit is power-cycled the factory settings will take over).
2.8 Network Communication Interfaces 2.8.1 10BASE-T RJ-45 Pinout The 10BASE-T Ethernet network (RJ-45) system is used in the Coordinator for network connectivity. The 10 Mbps twisted-pair Ethernet system operates over two pairs of wires. One pair is used for receiving data signals and the other pair is used for transmitting data signals. This means that four pins of the eight-pin connector are used.
Pin 1 2 3 4 5 6 7 8 Name +Tx -Tx +RX N/C N/C -Rx N/C N/C Description + Transmit Data - Transmit Data + Receive Data Not Connected Not Connected - Receive Data Not Connected Not Connected
Figure 2.10 RJ45 Pinout 2.8.2 10BASE-T Crossover Wiring When connecting the Coordinator directly to the computer, the transmit data pins of the computer should be wired to the receive data pins of the Coordinator, and vice versa. The 10Base-T crossover cable with pin connection assignments are shown below. Use straight through cable for connecting Figure 2.11 10BASE-T Crossover the Coordinator to an Ethernet hub. The Cable Wiring ports on the hub are already crossed. 2.9 Thermocouple Wiring The figure below shows the wiring hook-up for thermocouples. You may install 2 thermocouples. Example: for Type K thermocouple, connect WIRE the yellow wire to the "1 (+)" terminal (J1) J1 ENTRY and the red wire to the "2 (-)" terminal. 6
TYPE J K T E N R S B C DIN J ANSI Color Coding Lead (-) Lead (+) Red White Red Yellow Red Blue Red Purple Red Orange Red Black Red Black Red Gray Red White Red Blue
zED-TC-CCELL zED-TC-DCELL
5 4 3 2 1
zED-TC-P zED-TC-LCD zED-TC-LCD-AA
6 5 4 3 2 1
Figure 2.11 Thermocouple Wiring and TC Wire Color Chart
NETWORK CONFIGURATION 3.1 Ethernet (MAC) Address MAC (Media Access Control) address is your computer's unique hardware number. When you're connected to the LAN from your computer, a correspondence table relates your IP address to your computer's physical (MAC) address. The MAC address can be found on the label of your device and contains 6 bytes (12 characters) of hexadecimal numbers XX:XX:XX:XX:XX:XX hex For Example: 0A:0C:3D:0B:0A:0B Remove the small label with the default IP address and there will be room to put your IP address. See Figure 2.5.
3.2 Network Protocols
The Coordinator can be connected to the network using standard TCP/IP protocols. It also supports ARP, HTTP (WEB server), DHCP, DNS and Telnet protocols. 3.3 DHCP DHCP, Dynamic Host Configuration Protocol enables computers and devices to extract their IP configurations from a server (DHCP server).
If DHCP is enabled on your Coordinator, as soon as the Coordinator is connected to the network, there is an exchange of information between DHCP server and the Coordinator. During this process the IP address, the Gateway address, and the Subnet Mask will be assigned to the Coordinator by the DHCP server. Note that the DHCP server must be configured correctly to do such assignment. The Coordinator is shipped with DHCP disabled (factory default). If fixed or static IP address is desired, the DHCP must be disabled. The DHCP can be enabled by setting the DIP switch #3 to the "ON" position
DIP switch # 3 shown in "ON" position
Figure 3.1 4 Position DIP Switch on the Bottom Side of Coordinator Setting the Coordinator's IP address to 0.0.0.0 will also enable DHCP.
DNS, Domain Name System enables computers and devices to be recognized over a network based on a specific name instead of IP addresses.
For example, instead of having to use http://192.168.1.200 (IP address), you would use only http://z03ec or any sixteen character name stored as Host Name under Access Control menu in the zSeries Home Page. The default DNS name for the Coordinator is "z" followed by the last four digits of the MAC address of that particular Coordinator. 1. It is very important to communicate with the network administrator in order to understand DHCP and its existing configurations on the host server, before enabling DHCP on the Coordinator. 2. The Coordinators are shipped with a default static IP address of 192.168.1.200 and Subnet Mask of 255.255.255.0. 3. On Windows servers where DCHP and DNS are separate functions it is very important to configure the DHCP server to communicate with the DNS in order for the iServer's Host Name to correctly respond. If you cannot access the iServer using its Host Name, please contact your network administrator to make sure the DHCP and DNS servers are linked together.
3.5 IP Address
Every active device connected to the TCP/IP network must have a unique IP address. This IP address is used to establish a connection to the Coordinator. Every computer using TCP/IP should have a unique 32-bit address which is divided into two portions, the network ID and the host ID. For instance, every computer on the same network uses the same network ID. At the same time, all of them have a different host ID. For more details about the IP address see Appendix B. 3.5.1 Default IP Address The Coordinator is shipped with a default IP address of 192.168.1.200 and Subnet Mask of 255.255.255.0. If you are going to use a Web browser or Telnet program to access the Coordinator using its default IP address, make sure that the PC from which you're establishing the connection has an IP address that is in the same range as the Coordinator's IP address (192.168.1.x, where x can be any number from 1 to 254). See Section 3.5.2. You also need to make sure that your PC's Subnet Mask is 255.255.255.0. This is a good way to access the Coordinator over the network and make any configuration changes needed. If 192.168.1.200 is already in use on your network, use an Ethernet crossover cable between your computer and the Coordinator to change the IP address or any other settings within the Coordinator.
Your PC's IP address cannot be the same as the Coordinator's IP address.
3.5.2 Changing TCP/IP Properties on Your Computer
Go to your computer's Control Panel then Network Connections.
Pick the network with the proper Ethernet card. Right click and choose Properties.
Look for Internet Protocol, click on it and press Properties
Setup the IP address (in this case, 192.168.1.1) as shown below and press OK. You can access the Coordinator's web server via any internet browser using IP address of 192.168.1.200. Once you log into the Coordinator's web server, you will be able to change its IP configuration according to Section 4.2.
Figure 3.2 Network Connections
After you configure the Coordinator's IP configurations, you should go back and set your PC's previous IP settings.
Figure 3.3 Network Connections
PART 4 OPERATIONS This Coordinator can be used and configured in several ways, depending on user's preference and network setup. It can be configured using a Web browser, like Internet Explorer. It can also be configured using the iConnect Configuration Software. If DHCP and DNS servers are configured to exchange information, the connection will be very simple. All you need to do is to enable DHCP on the Coordinator (see Section 3.3) and use a straight through network cable to connect the Coordinator to an Ethernet hub or switch and power it up. Now, you can use the Coordinator's default Host (Domain) Name, which is zxxxx (where xxxx are the last four characters of its MAC address) to access the Coordinator's Web Server. If DHCP is not the preferred method, you can configure your PC's network connection (see Section 3.5.2 for more details) with an IP address of 192.168.1.x that is in the same range as the Coordinator's default IP address (192.168.1.200) and connect to the Coordinator using a cross-over network cable between your PC's network port and the Coordinator. After you're done with configuring the Coordinator, you can set your PC's network connection back to its original settings. On your computer, from the MS-DOS Prompt window type "ping 192.168.1.200" and press Enter. If DHCP and DNS servers are used type "ping zxxxx", where xxxx are the last four digits of the Coordinator's MAC address, located on the back of the device. You should get a reply as shown in Figure 4.1. 4.0 Testing the Connection
Figure 4.1 Pinging the Coordinator from MS-DOS Prompt This proves that the connection is proper and you can get into configuration or run mode using the Telnet or Web browser.
4.1 iConnect Software The Coordinator may also be assigned an IP Address by using the iConnect software. a) Download the iConnect software from the website listed in this manual. b) Install iConnect software on a networked PC. This software is compatible with Windows 95, 98, NT, 2000, and XP. c) Use iConnect to assign an IP address to the Coordinator and access its web pages for configuration. You can also use any standard web browser to access the zSeries system's web pages. Consult with your IT department for obtaining an IP address.
1) 2) 3) 4) 6) 7) 8) 5)
Figure 4.2 Assigning an IP Address using iConnect Place the IP address in this box. Take the MAC address from the label attached to the bottom of the Coordinator and place it in this box. Click here to send the above IP address to the Coordinator. After the IP address is assigned to the Coordinator, click here to access it's web pages. Click here to Ping the Coordinator whose IP address is shown in the IP address box. Click here to find all the Coordinators on your network . The IP addresses for the Coordinators found by the iConnect will be listed here. These fields indicate the IP address and the subnet mask of the PC on which the iConnect is running.
4.1 iConnect Software (continued) d) To access the zSeries system for Configuration: Click on the "View Webpage" button, you will access the zSeries home page, refer to Section 4.3 for details.
Figure 4.3 Accessing the zSeries System for Configuration
Select Access Control , button, you'll be asked for the password. You should be on the Access Control page were you can simply type in the desired Static IP address, and click Save. For more details about the "Access Control" page refer to Section 4.3.9.
The Coordinator is shipped with a default IP address of 192.168.1.200 and Subnet Mask of 255.255.255.0. You can configure your PC's Network connection (See Section 3.5.2 for more details) with an IP address that is in the same range as the Coordinator's IP address (192.168.1.x) and connect to the Coordinator using a crossover network cable between your PC and the Coordinator. With this completed, you can go to the DOS-Prompt and ping 192.168.1.200. If you receive responses back (Figure 4.1), you can go to the Web browser and type in http://192.168.1.200 and it will take you to the zSeries Home Page.
4.2 Setting a New IP Address over the Network Besides using the iConnect software, you may use the Coordinator's default IP address to access it and assign a new IP address to it.
Web Server enable IP Address Admin Password 00000000 Login Password 12345678 Host Name z85C4 MAC Address 00:03:34:00:85:C4 Gateway Address Subnet Mask 192.168.1.200 0.0.0.0 255.255.255.0
Save Reset
Network Reset Main Menu
Figure 4.4 Access Control For the IP address to take effect, the Coordinator needs to be turned OFF and ON using the "Network Reset" button. Pressing the physical button marked "RESET" on the Coordinator does the same thing. You can now connect the Coordinator to an Ethernet hub using a straight through cable, power it up, and follow the ping routine mentioned in the previous section.
4.3 Coordinator's Configurations and Operations The Blue LED should blink for about 8 seconds and then stay on. It indicates that the Coordinator is searching for the least noisy channel and starts listening there. That's when the blue LED changes from blinking to solid. Using a web browser, you should be able to view the homepage. • Start your web browser. • From the browser you type http://zxxxx using the last four-digits from the MAC address label located on the device if DHCP and DNS are used. If a static IP address is used, then simply type http://x.x.x.x, where x.x.x.x is the Coordinator's IP address. • The Home Page, will be displayed.
Readings Diagnostic Chart Sensor Setup
Access Control
Firmware Version x.x
Figure 4.5 Home Page Menu In order to access certain menu items of the Home Page, users may be prompted for a password, as shown in the two figures below.
LOGIN http://192.168.1.200
Figure 4.6 LOGIN and ADMINISTRATOR Passwords There are 2 different access levels: 1. ADMINISTRATOR Password (administrator) allows certain groups and individual users to access and modify "entire" parameters without any restrictions. The default password is 00000000. This password can be up to 16 alphanumeric casesensitive characters. 2. LOGIN Password (operator) allows users to access and modify all of the parameters, except "Access Control" which requires an Administrator password. The default password is 12345678. This password can be up to 16 alphanumeric case-sensitive characters.
4.3.1 Power Up Device To verify that an End Device is working before deploying remotely, install batteries and power it on right next to the Coordinator. When the End Device is powered on, it will search for the Coordinator in all 16 channels reserved for IEEE 802.15.4 (channel 11 through 26) by sending request packets. While it's searching, the blue LED on the End Device blinks every second. Once the Coordinator responds to the End Device request, the LED will blink only when the End Device sends data to the Coordinator (default is every 10 seconds). If the Coordinator is not powered on or it's out of reach, the End Device will keep searching until the batteries discharge (e.g. roughly 36 hours for zED). Once the Coordinator responds back to the End Device it will include its network number in the response packet called Beacon. At this time the End Device would know what the correct Coordinator is (there could be more than one Coordinator responding to the End Device's request packet). The channel on which the Coordinator responds back is automatically picked to be the clearest among all 16 channels and therefore the End Device starts sending data to the Coordinator on that particular channel. Once the End Devices and the Coordinator start communicating, make sure to push DIP switch #1 located on the back of the Coordinator to ON position. This will lock the Coordinator on the same channel it initially established the connection. After the End Device transmits data to the Coordinator, it expects an acknowledgment packet back from the Coordinator. If the End Device does not receive an acknowledgment packet back within 50ms, it will go to sleep mode for 2 seconds and then will transmit the data. This cycle will be repeated for 10 times and if it still does not receive the acknowledgment packet back, the End Device takes a longer sleep time of 3 minutes. After 3 minutes, the End Device retransmits the data every 2 seconds for 4 times and each time it waits for 50ms for an acknowledgment. If it still does not receive a response back from the Coordinator it will take another 3 minutes of sleep. This last sequence will continue until the batteries are drained. Through the whole retransmission cycle explained above the blue LED on the End Device will blink anytime retransmission takes place. The data being retransmitted will automatically gets updated as new readings take place. If the communication channel is manually selected in the Coordinator, the End Devices must be power-cycled in order to establish connection over the new channel. If it's not possible to power-cycle the End Devices locally, a remote option is available through the Coordinator's Web server or Telnet console. When there are two End Devices with the same Device ID, both will be transmitting data every second with their LEDs blinking once a second. The Coordinator will receive data from both End Devices and will display their data alternately. On the "Readings", "Chart", and "Diagnostic" pages of the Coordinator's Web server, the phrase "ID" error code will be placed indicating the conflict. Once the problem is resolved, click on the "Reset Sensor" button located on the Sensors Parameters page to remove the "ID" error code. In case of power failure/outage during normal operation, the zED-P/-LCD will automatically switch its power supply from AC adapter to back-up battery. However, power switching may fail if the End Device is on and consumes lots of energy. Therefore, "LOST" will be detected, the LED stops blinking periodically and the unit must be power cycled manually.
4.3.2 Get Readings from the End Device Once you see the End Device's LED blinking periodically, it means it is sending data which will appear on the "Readings" page. To view the data in a chart format, you can use the "Chart" page. Click on Readings from the Home Page, the following page will appear. Select the proper Group to view the readings.
Group C Group D Group B Group A
Wireless Sensors ID: 0 - 7 Wireless Sensors ID: 8 - 15 Wireless Sensors ID: 16 - 23 Wireless Sensors ID: 24 - 31
Sensor Setup Main Menu
Figure 4.7 Select Readings by Groups In a few seconds the following page will appear, showing updates of the Temperature, Barometric Pressure and Humidity values (depending on your available sensors).
Figure 4.8 Readings While accessing the "Readings" page, If a blank screen appears without any "java application running" or image of a "Java logo", please verify you have the latest Java Runtime Environment installed and configured according to the Section 18.104.22.168. If you do not have Java Runtime Environment, you may download it from our website or contact the Customer Service Department nearest you.
4.3.2 Get Readings from the End Device (continued) The "Readings" fields are defined as follows: Title: Coordinator's name, assigned in "Configuration" page. Name: End Device's name, assigned in "Sensor Parameters" page. ID: Sensor ID. Sequence: Sequence number [0-255, Lost, ID ]. The Sequence number is incremented for each newly received data. Therefore, it indicates if the sensor is transmitting data successfully. This area also will display error messages: Lost Coordinator has not received data from the sensor. ID More than one sensor is configured with the same Device ID. Reading Values: The order from left to right is Temperature, Barometric Pressure then Humidity. First Reading Temperature reading with temperature unit from the primary sensor. Second Reading Pressure reading or Humidity reading, depending on the primary sensor or the secondary sensor reading. Third Reading Humidity reading, if the End Device is a -BTH version or the secondary sensor reading. Fourth Reading: The secondary sensor reading. Data Logging: Press to activate/de-activate data logging. When it is pressed to activate data logging, a file browser pops up to ask for which file data will be saved. Data is in Comma Separated Value (csv) format, which can also be opened in Excel. Please name file with .csv extension. Reading "Open" indicates that no sensing device is detected.
Figure 4.9 Comma Separated Value Format Columns from left to right: Date and time, Device ID, Sequence number, Device type, Reading 1, Unit 1, Reading 2, Unit 2, Reading 3, Unit 3 (up to 4 readings and units), next Device ID, next Sequence number, ... (up to 8 End Devices). ACTIVE data is currently being logged in the specified file. INACTIVE data logging is not executed. Refresh: How often the current applet asks for data from embedded server. See Section 4.3.4 before activating data logging.
4.3.3 Java Runtime Environment Setup If your computer does not have Java installed, please download from java.sun.com. You can change the Java setting by clicking its icon in Control Panel. To load the applet, you have to enable the web browser and disable cache. 18.104.22.168 Java Runtime Environment 1.4 Setup instructions 1. Go to your computer's Control Panel. Open the Java Plug-in 2. Select the "Cache" Tab Un-check the "Enable Caching" box 3. Select the "Proxy" Tab. Follow these Browser Proxy Selection instructions below. (Generally, un-check the box if accessing Coordinator on your local network and check the box for access from your internal network to the internet.) 4. Refresh or restart the webpage. To disable cache setting: For Java Version 1.4.2.x it is found under the CACHE TAB.
Java (TM) Plug-in Control Panel
Enable Caching Advanced Browser
Location Size
Cache Settings
C:\Documents and Settings\AppData\Sun\Java\Deploymentcache\java
Jar Compression
Unlimited Maximum 50
Figure 4.10 Java 1.4.2.x Screen Shot
126.96.36.199 Java Runtime Environment 1.5 (5.0) Setup instructions 1. Go to your computer's Control Panel. Open the Java Plug-in 2. Click on "Settings" & "View Applets" in the "General" tab. 3. Select the "Settings" button on the General Tab Un-check the "Enable Caching" box. Then close dialog box to show the General Tab again 4. Select the "Network Settings" button on the General Tab. Proceed to the Browser tab. Follow the Browser Proxy Selection instructions below.You should either select the "Use Browser Settings" option or the "Direct Connection" option depending on the network connections between your computer and the Coordinator. (Generally, select "Direct Connection" if accessing Coordinator on your local network and select "Use Browser Settings" option for access from your internal network to the internet.) 5. Refresh or restart the webpage. For Java Version 1.5.x.x it is found under "General" > "Settings" > "View Applets" and then at the bottom there is the Checkbox to REMOVE CACHE .
Figure 4.11 Java 1.5.x.x. Screen Shots For Java 1.6.x.x it is similar to Java 1.5.x.x but there is no need to remove CACHE.
220.127.116.11 Browser Proxy Selection Accessing Coordinators within your internal network • Usually when the computer and Coordinators are on an internal network, you will not use Proxy server access. • You should un-check the "Use Browser Settings" option on the "Proxy" tab. Accessing Coordinators units using the internet • Often the web browser will use Proxy server access to the internet. In such cases, the default Java runtime settings on the "Proxy" tab should suffice. The default setting is the "Use Browser Settings" option. • If the default proxy setting doesn't work, then you may have a situation where the proxy settings of the web browser are incorrect. Diagnostics: If the web page of the zSeries system appears, then the HTTP Proxy is working fine. If the data isn't updated on the zSeries system upon selecting the "Readings" web page, there may be a problem with access through a winsock proxy server. In such cases your network administrator will need to provide the winsock proxy server and port #s. (The TCP ports the Coordinator uses for Java applets are 1000 and 1001). These values should be entered into the Socks line on the "Proxy" tab (of the Java Plugin control panel) or into the "connections" tab on the View,Internet Options dialog and make sure that the Proxy tab shows that the "Use Browser Settings" option is not selected (i.e. when you specify proxy connections in the Java Plugin control panel). Accessing Coordinators units over Peer-to-Peer network A simple peer-to-peer network is setup by disconnecting from the main network (as users will often do when trying to do initial setup of the zSeries system) and then connecting the Coordinator to another computer using an ethernet hub, an ethernet switch, or a Cross-over cable connection. Often when using a peer-to-peer network, the Java plugin and the web browser (such as Internet Explorer) have internet connections configured to connect through proxy servers. In such case, you will need to simply assign the final IP address on this peer to peer network and then view the Wireless System's charts after connecting the Coordinator into the regular network. Otherwise you can disable the Java plug-in's "Use Browser Settings" temporarily and then reconfigure the Java plug-in settings for regular network access after testing the Wireless System's chart access on your peer-to-peer network. The "Use Browser Settings" should not be selected. And the HTTP and Socks proxy entries should be blank. Also, setup the internet browser so that proxy servers are disabled.
Java and the Java Coffee Cup Logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries."
4.3.4 Java Policy To activate data logging and save graphs from the Java applets, it is necessary to create a Java Policy file and copy it onto a folder. 1) Open a Notepad file and using the IP address of the Coordinator type the following:
This file should have the IP address of the Coordinator; in this case the default IP address is 192.168.1.200. If the IP address is changed, then the IP address shown in the file needs to be changed; otherwise, it will not work. If more than one Coordinator is being monitored from the same computer, it is necessary to repeat the above for each of the Coordinators in the same "java_policy.txt" file. If DHCP/DNS is enabled, the unique Coordinator's name using DNS should replace the IP address. Example: "http:\\zSvrTEST". Make sure the DHCP server updates the DNS table to keep track of the Coordinator's name and IP addresses (consult with your network administrator). 2) Save the file as java_policy.txt. 3) Create a folder in your C: drive called "0_JAVAPOLICY". 4) Place the java.policy.policy file into the "0_JAVAPOLICY" folder.
grant codeBase "http://192.168.1.200/" { permission java.security.AllPermission "*", "*"; };
Figure 4.12 Java Policy Java Policy instructions continued on next page.
4.3.4 Java Policy (continued)
5) Change Java Applet's Runtime Parameters found on the following path: a. Control Panel --> Java --> Java Control Panel --> Java Tab --> View b. Inside the box under the Java Runtime Parameters type the following:
If you have multiple Java Runtime Versions listed, add this line to the version that you are using; if you update your Java, you will need to add this line again. c. Click OK on the Java Runtime Settings window. d. Click Apply on the Java Control Panel window and then OK. 6) Close all opened Web browser.
Control Panel
Name Java
Control Panel
Comments Java(TM) Control Panel
Java Security Advanced
Add text here
Java Control Panel
Java Applet Runtime Settings
JRE Product Name 1.5.0_06 Version
Java Runtime Settings
Runtime settings are used when an applet is executed in the browser.
Java Applet Runtime Settings
C:\Program Files\java\jre1.5.0_06
Java Runtime Parameters
OK View... OK Cancel Apply
Figure 4.13 Java Policy The "Data Logging" and "Save Current Graph" buttons in the "Readings", "Charts", and "Diagnostic" pages will not be active if the instructions explained in the above Section 4.3.4 are not followed.
4.3.5 Chart
Click on Chart , from the Home Page, the following page will appear. Select the proper Group to view the Chart. In a few seconds the following page will appear. The Java™ Applet graph displays Temperature, Humidity, and Barometric Pressure. It can be charted across the full span (-40 to 124ºC, and 0 to 100% RH) or within any narrow range (such as 20 to 30ºC).
Group C Group D Group B Group A
Wireless Sensors ID: 0 - 7 Wireless Sensors ID: 8 - 15 Wireless Sensors ID: 16 - 23 Wireless Sensors ID: 24 - 31
Sensor Setup Main Menu
Figure 4.14 Select Chart by Groups If a blank screen appears without any "java application running" or image of a "Java logo", please verify you have the latest Java Runtime Environment installed and configured according to the instructions (refer to Section 184.108.40.206). If you do not have Java Runtime Environment, you may download it from our website or contact the Customer Service Department nearest you.
Save Current Graph P0 Primary P1 LAB 50 P2 LAB 100 P3 CLN RM1 P4 CLN RM2 P5 Primary P6 OVEN5 P7 Primary
LAB 50 Temp
Group A
LAB 50 Pres
1200 100%
S0 Secondary S1 LAB 50 S2 LAB 100
5 C/Div
90 10 hPa/Div %/Div
S3 CLN RM1 S4 CLN RM2 S5 Secondary S6 OVEN5
Tue Jun 5 18:05:27 PDT 2009
1 Minute 1 Minute 1 Day 1 Week 1 Month 1 Year
(5 Seconds/Div)
Tue Jun 5 18:11:55 PDT 2009
S7 Secondary
Main Menu
Figure 4.15 Chart - End Device #1 LAB 50
4.3.5 Chart (continued) Title: Coordinator's name, assigned in "Configuration" page. Save Current Graph: Save the current graph in PNG (Portable Network Graphics) format. The filename has extension .png. Max/Min Temperature: Maximum and minimum temperature of the current graph. If a sensor is selected (trend line and sensor name turns bold), its most current temperature reading is shown here. Max/Min Humidity: Maximum and minimum humidity of the current graph. Temperature Unit Drop-down List: Temperature unit to be used, either ºC or ºF. If a sensor is selected (trend line and sensor name turns bold), it's most current humidity reading is shown here. Max/Min Pressure: Maximum and minimum pressure of the current graph. Reading "Open" indicates that no sensing device is detected. If a sensor is selected (trend line and sensor name turns bold), it's most current pressure reading is shown here. Pressure Unit Drop-down List: Pressure unit to be used.
P# button (Primary): P# shows the sensor name and controls the primary sensor readings. when clicked twice, it turns white and the trend line will disappear. When clicked again, it comes back to normal operation. Chart Area: Display the trend lines of the sensors.
When clicked once,it turns bold, highlights primary sensor trend line and displays current sensor readings.
Range of temperature can be controlled by the upper and lower boxes on the left and range of pressure can be controlled by the upper and lower boxes on the right. When clicked once,it turns bold, highlights secondary sensor trend line and displays current sensor readings. When clicked twice, it turns white and the trend line will disappear. When clicked again, it comes back to normal operation. X-axis Drop-down List: Time scale for the chart. Applet Start Date and Time: Activates when the "Chart" page opens up.
S# button (Secondary): S# shows the sensor name, displays error messages [Lost/ID] and controls the secondary (external) sensor readings.
The chart area can be shown based on 1 min, 1 hour, 1 day, 1 week, 1 month, or 1 year time intervals. Last Update Date and Time: The last date and time when data arrived.
4.3.6 Diagnostic Click on Diagnostic , the following page will appear.
Fri Jun 05 17:55:14 PDT 2009
Lab 50 Success 100% Strength 70% Update 10s Battery 2.68V
Lab 100 Success 100% Strength 68% Update 10s Battery 2.69V
CLN RM1 Success 100% Strength 77% Update 10s Battery 3.0V
CLN RM2 Success 100% Strength 100% Update 10s Power Adaptor
NODE-5 Success 100% Strength 94% Update 10s Battery 3.14V
Figure 4.16 Diagnostic Date and Time: Most recent time when data is received. Save Current Graph: Save the current graph in PNG format. The filename has extension .png. Parameters Logging: Click to activate/deactivate parameters logging. When it is activated, a file browser screen will allow you to name and save the logging file. The file is in Comma Separated Value (.csv) format. ACTIVE – parameters are currently being logged in the specified file. INACTIVE – parameters logging is not activated. Coordinator (yellow box): Coordinator is always at the top of the wireless network hierarchy (star topology). Sensor: Name of the sensor. Success Rate: (0-100%), a low success rate indicates a longer data delay, shorter battery lifetime and high network traffic. Any error messages (LOST, ID, OPEN) will be shown here as well. Radio Signal Strength: (0-100%), the higher the better. The blue line and blue triangle (roof) connecting to the Coordinator indicates the radio signal strength. Darker blue means a stronger radio signal. Dark Blue: between 100% and 79%; Medium Blue; 78% to 11%; Light Blue: 10% to 0% Update Rate: The time interval the Coordinator received data from the End Device. Battery Voltage: The total voltage of the batteries in the End Device. Once the voltage gets to 2.7V, it's recommended to change the batteries. The box (house) color indicates battery voltage. Green: >2.7V; Red: <2.7V
4.3.7 Configuration Click on Configuration from the Home Page, the following page will appear.
Temperature C Name zSeries TCP Connections 1 Pressure mbar Port 02000
Please refer to your local regulations for the allowed maximum transmission power
Transmission Power 20dBm Save
Channel 25
Radio Version x.x
Radio Reset Main Menu
Figure 4.17 Configuration Name: Coordinator name [maximum of 16 alphanumeric characters] Temperature: Unit of temperature readings, [ ºC or ºF ]. Pressure: Unit of pressure readings [ mbar, inHg or mmHg ]. TCP Connections: Number of TCP connections available for data query. If "0" is selected no TCP connection can be made to the indicated port number [ 0 through 5 ]. Port: Port number for TCP connections. [invalid ports: <500, >65536, 1000, 1001 ]. Save: Saves any changes for above settings.
4.3.7 Configuration (continued) PID: The Personal Network ID is automatically detected and displayed. Channel: Choose the operation channel defined in IEEE 802.15.4 for the sensor network. This allows you to select a wireless channel to communicate with the End Devices. It is strongly suggested to let the Coordinator to search for the best channel automatically, and by not touching this field. Transmission Power: This determines the signal power transmitted by the Coordinator. The options are 10 dBm and 20 dBm. Save: Saves changes for Channel and Transmission Power. Radio Reset: Power resets the radio module in the Coordinator. Radio Version: Firmware version of the radio module, also shown on model/serial label. Refer to your local regulations for the allowed maximum transmission power.
4.3.8 Sensor Setup Click on Sensor Setup from the Home Page, the following page will appear. Select the proper Group.
Group C Group D Group B Group A
Wireless Sensors ID: 0 - 7 Wireless Sensors ID: 8 - 15
Wireless Sensors ID: 16 - 23 Wireless Sensors ID: 24 - 31
Sensor Setup Main Menu
Figure 4.18 Sensor Setup by Group The Sensor Setup Page is for configuring End Device parameters such as name and update rate. A faster update period consumes more energy and creates more traffic. The update time must be selected to satisfy acceptable network performance and desired battery lifetime.
4.3.8 Sensor Setup (continued)
0 1 2 3 4 5 6 7
Update # Check Sensor Name Seconds
10 10 10 10 10 10 10 10
F,%,inHg F, % -F F, %
Battery Battery Battery ---
F,%,inHg Power Adapter --
Click on Sensor # to modify Sensor Parameters
Update Checked Box Readings Chart Select Another Group
Clicking this box will take you directly to the Readings page. Clicking this box will take you directly to the Chart page.
Main Menu
Figure 4.19 Sensor Setup #: Sensor ID configured by dip switches on the End Device. Click on the number to view and modify Sensor Parameters. See Figure 4.20. Check: Each check box controls whether or not readings from the End Device will be outputted. If unchecked the readings from the End Device will not be displayed on the "Readings", "Chart", and "Diagnostic" pages. Nor it will respond to Telnet connection. Sensor Name: Name of an End Device shows on the "Readings" and "Chart" pages, this is a text field and can take up to 8 alphanumeric characters. Updates Seconds: How often an End Device sends its data to the Coordinator. Units: Type of data and the corresponding units. Units of measurement from sensors inside an End Device that has joined the network will be displayed. [ ºC, ºF, %, mbar, inHg, or mmHg ]. Power: Type of power of the End Device [Battery or Power Adapter]. Firmware: HP (High Power) or SP (Standard Power) followed by the version number of the End Device. Update Checked Box: After checking/unchecking the boxes, make sure this is clicked to save the changes.
Clicking this box will take you to the Sensor Setup: By Groups page
4.3.8 Sensor Setup (continued)
Update Sensor Name
Sensor #1, Group A
Offset2 (xxxx.x) 0 Offset4 (xxxx.x) 0 Offset3 (xxxx.x)
Offset1 (xxxx.x)
(% or mbar) (% or mbar)
Reset Value Cancel
Reset Sensor Identify: INACTIVE Select Another Group Main Menu
Update rate is closely related to the lifetime of the battery. Since the End Device is in low power consumption (sleep mode) when idle, a longer update rate will cause less energy usage and prolong the life of the battery. On the other hand, a faster update rate shortens the battery life and results in a busy network, which will increase the chance of signal interference. As a general rule of thumb, minimum update rate should be proportional to the number of sensors in the network.
Figure 4.20a Sensor Parameters Sensor Name: Name of this End Device. Update (seconds): How often this sensor is sending its data to the Coordinator. For thermocouple input End Device, Continuous should be selected for continuous mode operation(20 samples/second) see Figure 4.20b. Periodic (1 sample/update). A faster update period consumes more energy and creates more traffic. The update time must be selected to satisfy acceptable network performance and desired battery lifetime. Cold Junction Compensation: This option is only available for thermocouple. Click on the link to follow instructions to perform cold junction compensation for the selected thermocouple channel. Cold junction compensation will allow you to adjust (calibrate) the thermocouple in reference to 0°C environment. See Figure 4.20b. TC Type: Select the proper thermocouple type for the channel or you select "disabled" to disable the channel.
Proper TC must be selected before doing cold junction compensation.
4.3.8 Sensor Setup (continued) Offset: If it is determined that the readings are slightly off, the user can manually assign numerical values to adjust the readings for temperature (in ºC) , humidity (in percentage), and barometric pressure (in mbar). The offset value can either be a positive or a negative number with one decimal point. Update: Saves changes Reset Value: Ignores changes and puts previous values back in the fields. Cancel: Ignores all the changes and goes back to the "Sensor Setup" page. Reset Sensor: Reset the End Device readings and status. If the End Device is not on the network, the data will be cleared after about 3 minutes. Otherwise, the End Device will reset itself and re-join the network after a minute. Identify: INACTIVE: End device is in running mode and sending data to the Coordinator periodically. ACTIVE: End device is in identify mode and it keeps its blue LED on solid so that operator can identify the corresponding sensor easily. Select Another Group: Go back to the group selection page to setup sensors.
Update Periodic 10 Cold Junction Compensation for Ch1 TC type K type TC type Sensor Name
Sensor #6, Group A
Offset1 (xxxx.x) 0 (C) Cold Junction Compensation for Ch2 Offset3 (xxxx.x) K type 0 (C)
Reset Value Cancel
Reset Sensor Identify: INACTIVE Select Another Group Main Menu
Figure 4.20b Sensor Parameters for Thermocouple Option
4.3.9 Access Control This section describes the "Access Control" page of the Web interface. This page allows the users to set up the network and security parameters of the zSeries wireless system. At the initial entrance to the "Access Control" page you may be prompted for the LOGIN Password (see Figure 4.6) prior to an ADMINISTRATOR Password.
Web Server enable Host Name IP Address z85C4 Admin Password 00000000 MAC Address 00:03:34:00:85:C4 Gateway Address Subnet Mask 192.168.1.200 0.0.0.0 255.255.255.0 Login Password 12345678
Save Reset
Network Reset Main Menu
Figure 4.21 Access Control Login Password: This allows users to access and modify all of the zSeries Home Page menu items, except "Access Control", which requires an Administrator password. The default Login password is 12345678. This password can be up to 16 alpha-numeric case-sensitive characters. If there is no Login Password assigned (blank box) the zSeries system will not require a password to access and modify zSeries Home page menu items. Admin (administrator) Password: This allows users to access and modify the "Access Control" page. The default password is 00000000. This password can be up to 16 alphanumeric case-sensitive characters. If there is no Administrator Password assigned (blank box) the zSeries system will not require password to access and modify "Access Control" page. Web Server: To enable or disable the embedded webpages. Host Name: Name of the server (DNS) max 16 characters, default is "z" and the last 4 digits of the MAC address. Refer to Section 3.4, DNS. MAC Address: This is also called Hardware address or Ethernet address, which is assigned to the Coordinator at production. The MAC (Media Access Control) address is the Coordinator's unique hardware number and is not changeable.
4.3.9 Access Control (continued) IP Address: The IP (Internet Protocol) address is a 32-bit number that identifies each sender or receiver of information that is sent in packets across the Ethernet or the Internet. The Coordinator's default IP address is 192.168.1.200. The Coordinator's IP address should be changed to fit user's networking environment. Consult with your IT department for obtaining an IP address. The DHCP will be enabled in the Coordinator if its IP address is set to 0.0.0.0. The DHCP can also be enabled by setting the DIP switch #3 to ON position. Gateway Address: A gateway is a network point that acts as an entrance to another network. A gateway is often associated with a router, which knows where to direct a given packet of data that arrives at the gateway. If the Coordinator is sending packets to another network node that is not on the same network on which the Coordinator is connected, a gateway address needs to be given to the Coordinator. The gateway address should be the IP address of the router connected to the same LAN to which the Coordinator is connected. The Coordinator default gateway address is 0.0.0.0. Consult with your IT department for obtaining a gateway address. Subnet Mask: It's a 32-bit number that is used to determine which part of the IP address is the network portion and which part is the host portion. The Coordinator default subnet mask is 255.255.255.0. Consult with your IT department for obtaining a subnet mask. Save: Saves any changes for above settings. Reset: Pressing the Reset button will set all the fields back to their original values. Network Reset: Reboots the embedded server. Note that all updated network parameters take effect after reboot. Changes made in the "Access Control" page can be saved permanently by pressing the Save button and power recycling the Coordinator (press Network Reset button). 4.4 Telnet Setup In the Configuration page, set the TCP Connections to 1 - 5 other than 0, and use a telnet simulation program to connect to the Coordinator (using Port 2000). The command can be sent to query the Coordinator and you will get a response back. For a list of commands refer to ASCII/TELNET Commands Table in Appendix F.
4.5 HTTPget Program The HTTPget software is used to send a single HTTP or TCP request to a Coordinator. In contrast, the telnet or Hyperterminal programs allow a continuous connection with multiple requests to be sent to the Coordinator. Generally HTTPget is used for simply programming an IP address to the Coordinator or for quickly obtaining a reading from a device. The Coordinator must be configured from the configuration web page so that the "TCP Connections" indicates any number between 1 and 5. Make sure that the Port Field number indicates 2000.
4.5 HTTPget Program (continued) Whenever Terminal Server service (using Port 2000 by default) is required, the # of connections must be set to a value from 1 to 5. The Terminal Server mode is the recommended mode for the most reliable connection when operating with NEWPORT software or with other programs supporting TCP/IP communications. The Port 2000 access can be used with NEWPORT software and may be needed with some zSeries wireless system products when you need to view readings from the web page while simultaneously collecting data through TCP/IP communications. 4.5.1 HTTPget using Port 2000 You can setup and read the information from the zSeries wireless system by using the HTTPget program. The following program can be used to read data from the embedded server firmware by using TCP port 2000. The command string is sent to this TCP port, then the response can be read back from the same socket. The HTTPget.exe file is used to setup and read information from the zSeries system. This file will be automatically installed when you install the MailNotifier software available on our website and CD. Notes on using HTTPget : The HTTPget.exe program is installed to the windows directory (usually c:\winnt or c:\windows) when installing the Mail Notifier software. 1. Open up a command window (or have a DOS window) a) Click on start menu b) Click on "Run" c) In the dialog box that appears, type "cmd" or "command" and click on "OK" button. d) A command window should now appear. 2. If you now type "httpget" and press the "enter", the program options should be displayed. 3. Next run HTTPget with the options displayed below httpget -r -S ERDGALL 192.168.1.200:2000 -C1 -q where: -r –S are parameters needed for the the command string ERDGALL is the Telnet command (refer to Appendix F) 192.168.1.200 is an IP address 2000 is a socket port number -C1 closes the TCP connection after 1 second -q displays no error messages once the connection is closed
ID # of End Device
End Device Type Sensor Value & Unit
Sequence #
Figure 4.22 HTTPget Example of Polling End Device #1, 2, 3, 4
4.5.2 HTTPget and ARP to Setup Device IP Address Use the iConnect software, which may be downloaded from our website, to do these IP changes whenever possible. Use ARP first to assign the mac address to a static IP address in computer arp table by this command: arp –s 192.168.1.200 00-03-34-00-06-b6 Then use the following command to assign new IP to the device: Httpget –r –S "00000000" 192.168.1.200:1
where: "0000000" is admin. password. If the password is wrong, the unit will ignore the new IP. If the new IP is taken, you will get the message "New IP is Assigned" after the HTTPget command. The device will reset automatically. "192.168.1.200" is an example of an IP address. It is replaced with IP address suitable for your network. "00-03-34-00-06-b6" is replaced with your Coordinator MAC address. 4.6 ARP Protocol ARP is the Internet layer protocol responsible for matching or obtaining the MAC (hardware) address that corresponds to a particular IP address. The ARP command allows the user to view the current contents of the ARP cache of the local computer (residing on the same network). Microsoft includes the ARP.EXE utility for viewing and modifying the ARP cache with its Windows products. The following ARP commands can be used to view cache entries: • arp –a © Use this command to view all ARP cache entries. • arp –a plus IP address © Use this command to view ARP cache entries associated with one particular interface on a network with multiple adapters. • arp –g © Same as arp –a. • arp –N © Use this command to display ARP entries for specific network interface. • arp – s plus IP address plus Physical address © Use this command to manually add a permanent static entry to the ARP cache. • arp –d plus IP address © Use this command to manually delete a static entry.
4.6 ARP Protocol (continued)
The following window shows examples of arp commands and responses. • Your computer has an IP address of 192.168.1.118 • The destination computer has an IP address of 192.168.1.96
C:\>ping 192.168.1.96 Pinging 192.168.1.96 with 32 bytes of data: Reply Reply Reply Reply from from from from 192.168.1.96=bytes=32 192.168.1.96=bytes=32 192.168.1.96=bytes=32 192.168.1.96=bytes=32 time=5ms time=3ms time=3ms time=4ms TTL=32 TTL=32 TTL=32 TTL=32
C:\>arp -a 192.168.1.96 Interface: 192.168.1.118 Internet Address Physical Addresss 192.168.1.96 00-03-34-00-00-23 00-03-34-00-00-23 C:\>arp -d 192.168.1.96 C:\>arp -a 192.168.1.96 No ARP Entries Found C:\>
Type dynamic
Figure 4.23 ARP Commands and Responses
4.7 iLog Software
This is an Excel application software that can log temperature, humidity and barometric pressure from the Coordinator over the local network (Ethernet) or the internet. a) Download the iLog software from the website listed in this manual. b) Install iLog software on a networked PC. This software is compatible with Windows 95, 98, NT, 2000, and XP. c) For complete information of how to use the iLog software, click on the HELP button. d) There is a list of Error Messages in Appendix E.
Figure 4.24 iLog Software Logging Data for End Deice #1, 3, 4
4.7 iLog Software (continued)
Table 4.1 iLog Excel Applications The iLog application actually consists of several Excel files, though most supported devices can be accessed by the main iLog program. The main program is listed as "iLog", plus a version number, under the Start Menu program links (those links available by clicking the Start button on the Windows taskbar). In the following table, the iLog File column shows how many sensors are logged by the main iLog file. If more than 3 sensors are available, then the Alternate column shows how many sensors the device can support. Devices with more than 3 sensors will have their own Excel file. For these files, click on the model device found in the Start Menu. Networked Product iTHX-W, iTHX-2 iTHX-M, iTHX-SD iTHX-W Dual Probe iSE-TC, iSD-TC iSE-TH, iSD-TH iBTHX-W, iBTHX-D iBTX-M, iBTX-SD iPTX-W iTCX iTH Controller iVI iSeries iDRX/iDRN INF-B iLOG File 3 column 3 column 1st probe / 3 column 3 column 3 column 3 column 2 column 2 column 3 column 3 column 3 column 1 column 1 column 1 column Alternate 6 column 5 column 5 column 4 column
4 column
Wireless Devices The "Auto" column shows number of columns per remote device that are possibly displayed. The Full column shows number of columns allocated per device for the "Full" spreadsheet, which will be able to display all data for all active devices. Networked Product zSeries Receiver and Remotes wiSeries with zED Remotes UWTC REC-3 and Remotes wiSeries with UWTC Remotes Auto 1 to 4 column / device 1 to 2 column / device 1 or 2 column / device 1 to 2 column / device
The active wireless devices, when shown in the Excel application, will be shown with the device number and the units returned.
Full 4 column / 32 device 2 column / 32 device 2 column / 32 device 2 column / 32 device
4.8 Mail Notifier Software
For complete information of how to use the Mail Notifier software, click on the Help menu of the main window. The Mail Notifier software generates email notifications for alarm conditions. Users can be notified automatically of alarm conditions monitored via internet connections throughout the world. By use of the email forwarding of alarm conditions, alarm conditions can be monitored on a network isolated from the internet and forwarded to connections on the Internet. The Mail Notifier utility operates under Windows 98, NT 4.0, 2000, and XP in conjunction with existing email that supports the MAPI messaging interface. If MS Outlook has been loaded, the MAPI support should be available. 4.8.1 Installation The Mail Notifier must be loaded on a computer running Microsoft Windows (versions specified earlier) using an email program that provides MAPI access. Network access must be available between this computer and the zSeries wireless system. Network access must also be available from this computer to the appropriate email server and from the email server to the recipient's email server.
File Monitor Mail View Help Status Indicators Data Email Error
iServer Mail Notifier
Alerts List
Dev1 alarm: 74.6 Dev2 alarm: 89 Dev1 alarm: 74.7 Dev1 alarm: 74.7 Dev2 alarm: 89 Dev1 alarm: 74.7 Dev1 alarm: 74.6 Connected to Email
Figure 4.25 Mail Notifier Main Window
4.8.2 Program Options Setup and Configuration Complete program setup requires: • Entering a recipient for the email • Specifying connection details to MAPI services. • Defining alarms for devices, and selecting how and when the email will be active.
Send To Email Setup Content Startup General
Mail Server
MAPI Name/Profile Password
Use Login Box
Email Address
MS Outlook
Outlook 2002
Figure 4.26 Mail Notifier Profile Setup Email Address Setup The email addresses must be entered using individual addresses or alias. Select "Options" from the "View" menu and enter the email addresses on the "Send To" screen. This will be the list of email addresses to which alarm notifications will be sent. Email Setup The Mail Notifier is compatible with original MS OutlookTM and OutlookTM 2002 to 2005. The Mail Notifier will attempt to automatically identify whether the Outlook is a newer version. A red bar appears under the Mail Notifier splash window to confirm that the detection of the 2002 or newer version is acceptable. With the newer versions, no additional steps should be taken to enable the connection between the Mail Notifier and the Email server. MS Outlook tends to require that the users respond to a "login box" in order for email access to be activated for Mail Notifier. Some other email clients may allow for Mail Notifier to gain access without user login, as may be desired for a system recovering from a power outage. See the Help files for more information.
4.8.3 Device Setting and Configuration Make sure that the Coordinator is configured (using web access, see Figure 4.17) to the settings below. TCP Connection = any value from 1 to 5 Port number = 2000 (other values may be acceptable as long as Mail Notifier is setup with the same Port number). Then on the Mail Notifier Alarm Editor: 1) Set the "IP address" (for example 192.168.1.200). 2) Specify "Socket Number" 2000. 3) Set the "Address/RS485 Unit" to the Device ID number for an End Device. 4) Set the "Reading Cmd" using general commands in the following Table below. 5) Define the Alarm Configuration (High/Low, High value, or Low value). Specify Email Interval. This determines how many seconds each subsequential alarm notification will be sent. Determine Monitor interval. This establishes the interval or time resolution in seconds for which readings will be obtained from the device. Table 4.2 Mail Notifier Commands Desired Value to Monitor Reading Cmd string Reading A Reading B Reading C Reading D Battery voltage (mV) Signal Level Sleep Interval Status (see Note 4) zRdgA zRdgB zRdgC zRdgD zBatt zSignal zSleep zAddress Actual Command String (see Note 2) ERDB003 ERDB003 ERDB003 ERDB003 EQPE003 EQPE003 EQPE003 EQNF003
1. The End Devices are configured in Mail Notifier with symbolic commands rather than actual device commands. 2. zRdgA with RS485 Device Unit # as 3, for example, is sent as ERDB003. 3. "Reading A" will be the first value returned for a device in response to a command such as ERDB003. 4. "Status" can be used to detect an address conflict. The value should be tested to be at value 32 if there is an address conflict.
4.8.3 Device Setting and Configuration (continued)
Device Info (1 of 2)
Alarm Editor
192.168.1.200 2000 3
Server IP Address Socket Number Bus Address/Device ID Description Src ID Reading Cmd
Alarm Configuration
OK Cancel Help Add Del
Dev1 zRdgA
Only Monitor Access to iServer device
Alarm Type Alarm High Alarm Low
Alarm High 73 0
Info Message Email Interval 0.05 hrs. min. min.
Monitor Interval 0.5 Alarm Hold Time 0.0
4.8.4 Sending Txt Messages to a Cell Phone
Figure 4.27 Mail Notifier Device Setting
Once you install the Mail Notifier Software and configure it to work with any of our networking products, you can use the following format to have Mail Notifier send a text message to your cell phone. Since most cell phones are capable of receiving text messages you just need to find the correct email format for your cell phone provider and use it within the Mail Notifier environment. T-Mobile Virgin Mobile Cingular AT&T Sprint Verizon Nextel firstname.lastname@example.com firstname.lastname@example.com email@example.com firstname.lastname@example.com email@example.com email@example.com firstname.lastname@example.com
"phone_number" is your 10 digit cell phone number. 58
PART 5 ENVIRONMENT / OPERATING CONDITIONS End Device/Coordinator are designed to be fixed mounted and operated in a clean and dry environment. Care should be taken to prevent the components of your wireless system from being exposed to moisture, toxic chemicals, extreme cold or hot temperature that are outside the specification listed in this manual. The following is a list of basic good practice you should apply when operating this Wireless System. 1. Do not operate the wireless device in flammable or explosive environments. 2. Do not use the wireless device in medical, nuclear or any other critical application where failure can cause damage or harm. 3. Always operate the wireless device within the recommended environmental limits specified in this manual. 4. Do not operate your wireless device with a battery or AC adapter other than what's supplied or specified in this manual or on the battery compartment label. 5. Keep each wireless device at least 8 inches (20 cm) from other radio transmitters, antennas, and people. 6. The FCC approval for this device specifies the specific antenna supplied with this device. 5.1 General Deployment Guidelines 1. Position Coordinator in a central location. When multiple End Devices are in operation, position your Coordinator in a central space if possible in equal distance to each End Device. 2. Test your system before permanent mounting. Try to move the devices to different location around and mounting angles to determine what installation achieves the best signal strength before permanently mounting the End Device. 3. Move your system components higher off the floor and away from exterior walls. The closer the End Device/Coordinator are, the greater the interference and lose of signal strength will be. 4. Maintain a line-of-sight between antennas and keep Fresnel zone free of obstruction. See Figure 5.2. 5. Maintain a constant ambient temperature environment. Exposing your system components to extreme cold or hot temperatures, or sudden changes in ambient conditions will have an effect on the performance of your system. 6. As a general rule in buildings, head height or above is preferred. On the other hand, End Device stays close to the floor may have their range reduced by 50% to 90%.
5.1 General Deployment Guidelines (continued) 7. Where possible, try to ensure an uninterrupted line-of-sight between nodes. Avoid obscuring objects (e.g. metal pillars, posts, sign) near the antenna. A close object obscures a wider range of solid angle. 8. It is important to understand that the environment may change over time due to new equipment or machinery being installed, building construction, etc. If new obstacles exist between your End Device and Coordinator, antenna angle may need to be re-adjusted and/or the unit has to be relocated. 9. An IEEE 802.15.4 wireless network will not work under water. Wet condition (e.g. in heavy rainfall) may exhibit some degradation. In most cases, water droplets on or close to the antenna are more serious than the rain itself. Humidity can affect radio performance as well. 10. Reduced performance scenario: a. A large building may have few obstructions between nodes but large amount of metallic paneling that cause reflections. b. A small domestic installation may have numerous brick walls between nodes in individual rooms. c. An office building may have metalized dry-wall partitions together with mezzanine ceilings.
End Device End Device
End Device
End Device
Figure 5.1 Operation in Buildings Data is sent through radio signal at 2.4 GHz. Radio signals are electromagnetic waves, hence the signal becomes weaker the further it travels. While radio waves can penetrate some solid materials like a wall, they can diminish more than when a direct line-of-sight between the transmitting and receiving antenna exist. Therefore, it is generally a good idea to place Coordinator at the center while End Devices are located about the same distance away from it. If possible, keeping clearance around the line of site will improve performance as well.
5.2 With Line-of-Sight When installing your Coordinator it is important to position your device in such a way to optimize the antenna location within what's known as the "Fresnel Zone". The Fresnel Zone can be thought of as a football-shaped invisible tunnel between two locations that provides a path for RF signals between your End Device and your Coordinator.
END DEVICE ANTENNA or
In order to achieve maximum range, the football-shaped path in which radio waves travel must be free of obstructions. Obstacles in the path (especially metal) will decrease the communication range between your End Device and Coordinator. Also, if the antennas are mounted just barely off the ground or below the ceiling, over half of the Fresnel zone ends up being obstructed resulting in significant reduction in range. Below is the calculated radius of the football-shaped tunnel for different distance range: Distance (feet) Radius (feet) 100 3.2 200 4.5 300 5.5 It is recommended that within the tunnel of the above radius, at least 60% of space is free of obstruction. Since signal reaches destination directly in a line-of-sight situation, it is important to adjust antenna properly to achieve maximum performance. Antenna for the Coordinator and End Device should be perpendicular to the plane where Coordinator and End Device is located.
Figure 5.2 Fresnel Zone
5.3 Without Line-of-Sight When line-of-sight is not possible, signal penetrates and is reflected by different objects to reach the destination. Therefore, it is important to learn about how these materials would affect signal propagation. Depending on the thickness, moisture content and angle of incidence, a wall may allow between 1% and 25% of the radio power to pass through. Metal panel or metalized glass window will not allow much radio power to pass through. Signal will be reflected if the panel is a mirror. Some radio power may propagate through small holes in the panel or around metal edges through the process of diffraction. Material Type Wood, Plaster, Sheetrock, Fiberglass Uncoated Glass w/out Metal Brick, Pressboard Reinforced Concrete Possible Signal Reduction 0 to 10% 5 to 35% 10 to 90%
Metal Walls, Metal Doors, Elevators, Metal Piping, Metal Stair Cases, Metal Mesh, Metal Screening
In a non-line-of-sight situation at 2.45 GHz, it is possible to move the receive antenna only 1 to 1 1/2" (3 to 4 cm) and see signal strength varies from 6 dB to -20 dB due to multiple signal reflection path. Therefore, there should be about 20 dB path loss margin to take signal fading into account. 5.4 Casing and Closure Around the Antenna 1. Metallic structure should be kept at least 0.8" (2 cm), although 2.4" (6 cm) is recommended away from the antenna. 2. Any casing that encloses the antenna should be plastic. In addition, it is also wise to avoid plastic case with dark fillers or colorants.
Figure 5.3 Materials in Buildings
90 to 100%
5.5 Fine Adjustment in Performance 1. To avoid interference from WiFi / IEEE 802.11, one could consult the figure below to choose the best channel through the Configuration webpage. In all, channels 15, 20, 25 and 26 are not overlapping with any WiFi / IEEE 802.11 bands in the United States while channels 15, 16, 21 and 22 can be used in Europe.
US WLAN (IEEE 802.11B) non-overlapping 2400 MHz
2437 Channel 22 MHz
2483.5 MHz
European WLAN (IEEE 802.11B) non-overlapping 2400 MHz
2472 2 MHz
2442 Channel 17 18 19 20
2483.5 MHz
IEEE 802.15.4 2400 MHz PHY
14 15
24 25
5. 6.
Figure 5.4 Channels It is possible that IEEE 802.15.4 devices experience interference from Wi-Fi / IEEE 802.11 and Bluetooth devices and certain microwave ovens. Therefore, it is worth locating nodes as far as possible to minimize effect. Note that international radio regulations which govern radio equipment ensure that cell phones use their allocated band only. It is highly unlikely that cell phones will interfere with IEEE 802.15.4 equipment. In some cases, a short RF cable may be used to connect an antenna to your device. Please note that RF extension cables will always add some loss to the transmitting signal strength. The longer the cable the more signal will be lost over that cable. Therefore, the length of the cable should be kept as short as possible. Also, note that use of any other antenna other then what's shipped with your device will void FCC and CE regulatory complicance. To achieve satisfactory IEEE 802.15.4 performance in the presence of WLAN interference, a channel center-frequency offset of 7 MHz is recommended. For co-channel operation, a physical separation from the WLAN Access Point (AP) of 26.2' (8 m) is recommended to achieve a Packet Error Rate (PER) of 1%. For a particularly saturated WLAN link, 29.5' to 32.8' (9 to 10 m) may be necessary. To achieve satisfactory IEEE 802.15.4 performance in the presence of Bluetooth interference, a separation distance of 6.5 ' (2 m) is recommended.
2400 MHz
2483.5 MHz
RELATIVE HUMIDITY Accuracy/Range: zED-BTH, zED-TH, zED-THP; zED-BTHP (-P/-LCD/-AA/-CCELL/-DCELL); zED-THP (-P/-LCD/-AA/-CCELL/-DCELL); zED-THP2 (-H) Hysteresis: Non-linearity: Repeatability: Resolution:
SENSOR SPECS (zED, zED-P zED-LCD, zED-LCD-AA, zED-CCELL, zED-DCELL, zED-H) , ±2% for 10 to 90%; ±3% for 5 to 10% and 90 to 95%; ±4% for 0 to 5% and 95 to 100% ±1% RH ±3% ±0.1% 0.1% ±0.5ºC for 10º to 55ºC (±0.9ºF for 50º to 131ºF) ±1ºC for -18º to 10ºC (±1.8ºF for -0.4º to 50ºF)
TEMPERATURE Accuracy/Range*: (Internal Sensor) zED-T
(External Sensor) zED-TP1, -TP2; zED-TP1/TP2 (-P/-LCD/-AA/-CCELL/-DCELL) Accuracy/Range*: (Internal Sensor) zED-BTH, zED-TH Refer to chart in Appendix I
±0.5ºC for 10º to 85ºC (±0.9ºF for 50º to 185ºF) ±1ºC for -40º to 10ºC and 85º to 125ºC (±1.8ºF for -40º to 50ºF and 185 to 257ºF) ±0.5ºC for 0º to 45ºC (±0.9ºF for 32º to 113ºF) ±1ºC for -18º to 0ºC and 45º to 55ºC (±1.8ºF for -0.4º to 32ºF and 113º to 131ºF)
(External Sensor) zED-THP (-P/-LCD/-AA/-CCELL/-DCELL); ZED-THP2 (-H)
zED-BTHP (-P/-LCD/-AA/-CCELL/-DCELL) Refer to chart in Appendix I Accuracy/Range*: (Internal Sensor) zED-BT
±0.5°C for 5 to 45°C (±1°F for 41 to 113°F); ±0.5° to ±1.5°C for -40 to 5°C and 45 to 124°C (±1° to ±2.7°F for -40 to 41°F and 113 to 255°F) ±0.5°C for 5 to 45°C (±1°F for 41 to 113°F) ±0.5 to ±1.5°C for -40 to 5°C and 45 to 85°C (±1 to ±2.7°F for -40 to 41°F and 113 to 185°F)
(External Sensor) ±0.8ºC @ 20ºC (±1.5ºF @ 68ºF) zED-BTP; ±2ºC for -40º to 85ºC (±3.6ºF for -40º to 185ºF) zED-BTP (-P/-LCD/-AA/-CCELL/-DCELL) *Note: extended temperature ranges are for External Probes only. Repeatability: Resolution: BAROMETRIC PRESSURE Accuracy/Range: ±2 mbar for 10 to 1100 mbar (1 to 110 KPa) zED-BTH, zED-BT, -BTP; zED-BTP/BTHP (-P/-LCD/-AA/-CCELL/-DCELL) Resolution: 0.1 mbar 64 ±0.1ºC for -BTH, -BTHP, -TH, -THP, -THP2 0.1ºC
±0.8ºC @ 20ºC (±1.5ºF @ 68ºF) ±2ºC for -18º to 55ºC (±3.6ºF for -0.4º to 131ºF)
EXTERNAL PROBE SPECIFICATIONS Industrial Probe:
(zED, zED-P, zED-LCD, zED-LCD-AA, zED-CCELL, zED-DCELL, zED-THP2-x-H)
Short Quick Disconnect Probe: Stick Probe:
Lug Mounted Probe: Cable Dimensions and Operating Temperature:
THERMOCOUPLE INPUT Temperature Range & Accuracy: Temperature Stability: Temperature Coefficient: Thermocouple Cold End Tracking: Thermocouple Lead Resistance: Thermocouple Type (ITS 90): Warm-Up to Rated Accuracy:
TABLE 6.1 Input Type Iron - Constantan
SS 316 housing, 137 mm x Ø16 mm (5" x Ø 0.63") for zED-xx-BTP; zED-xx-THP; zED-BTP/BTHP/THP (-P/-LCD/-AA/-CCELL/-DCELL) SS 316 housing, 78 mm x Ø16 mm (3.1" x Ø 0.63") for zED-THP2-xx-H ABS tubing, 152.4 mm x Ø6.35 mm (6" x Ø 0.25") for zED-xx-TP1; zED-TP1 (-P/-LCD/-AA/-CCELL/-DCELL) Copper tubing, 53.4 mm x Ø 7.92mm (2.1" x Ø 0.312"); mounting hole Ø 4.72mm (Ø 0.186") for zED-xx-TP2; zED-TP2 (-P/-LCD/-AA/-CCELL/-DCELL) 3 m (10') long x Ø 5.72 mm (0.225") -40º to 125ºC (-40º to 257ºF) for zED-xx-THP; zED-xx-TP1; zED-xx-TP2 3 m(10') long x Ø4.45 mm (0.175") -55º to 105ºC (-67º to 221ºF) for zED-xx-BTP; zED-BTP/BTHP (-P/-LCD/-AA/-CCELL/-DCELL) 3 m (10') long x Ø2.62 mm (0.103") -80º to 200ºC (-112º to 392ºF) for zED-THP/TP1/TP2 (-P/-LCD/-AA/-CCELL/-DCELL) Refer to Thermocouple Chart 0.08°C/°C ±25 ppm/°C 0.1°C/°C 100 ohm max. J, K, T, E, R, S, B, C, N, L 30 minutes
THERMOCOUPLE CHART Range -210 to 760°C / -346 to 1400°F -270 to -160°C / -160 to 1372°C -454 to -256°F / -256 to 2502°F -270 to -190°C / -190 to 400°C -454 to -310°F / -310 to 752°F -270 to -220°C / -220 to 1000°C -454 to -364°F / -364 to 1832°F -50 to 40°C / 40 to 1768°C -58 to 104°F / 104 to 3214°F -50 to 100°C / 100 to 1768°C -58 to 212°F / 212 to 3214°F 100 to 640°C / 640 to 1820°C 212 to 1184°F / 1184 to 3308°F 0 to 2320°C / 32 to 4208°F -250 to -100°C / -100 to 1300°C -418 to -148°F / -148 to 2372°F -200 to 900°C / -328 to 1652°F
CHROMEGA®- ALOMEGA® CHROMEGA® - Constantan Pt / 13%Rh-Pt Pt / 10%Rh-Pt Copper - Constantan
30%Rh-Pt / 6%Rh-Pt 5%Re-W / 26%Re-W Nicrosil - Nisil J DIN
Accuracy 0.4°C / 0.7°F 1.0°C / 0.4°C 1.8°F / 0.7°F 1.0°C / 0.4°C 1.8°F / 0.7°F 1.0°C / 0.4°C 1.8°F / 0.7°F 1.0°C / 0.5°C 1.8°F / 0.9°F 1.0°C / 0.5°C 1.8°F / 0.9°F 1.0°C / 0.5°C 1.8°F / 0.9°F 0.4°C / 0.7°F 1.0°C / 0.4°C 1.8°F / 0.7°F 0.4°C / 0.7°F
INTERFACE SPECIFICATIONS (zCDR) Ethernet: Standards Compliance IEEE 802.3 10Base-T (RJ45) Supported Protocols: TCP/IP, ARP, ICMP, DHCP, DNS, HTTP, and Telnet LED Indicators: Network Activity, Network Link, Diagnostics, Receive and Power Management: Device configuration and monitoring through embedded WEB server Embedded WEB Server: Serves WEB pages (Java™ Applets) containing real-time data and live updated charts within definable time intervals WIRELESS COMMUNICATION Standard: IEEE 802.15.4, DSSS Frequency: 2.4 GHz (2400 to 2483.5 MHz), 16 channels Network Topology: Star Topology Radio Power Output: 100 mW (20 dBm); 10 mW (10 dBm) Limitations on Equivalent Isotropic Radiated Power (EIRP) levels in the European Community and other countries applies. An improper combination of power level can result in an EIRP above the allowed amount per regulations. See Appendix H. Data Rate: Bit rate 250 Kp/s; Symbol rate 62.5 Symbol/s; Chip rate 2000 kchip/s Orthogonal Quaternary Phase Shift Keying (O-QPSK) -100 dBm
Modulation: Receiver Sensitivity: Range: zED Up to 91 m (300 ft) without obstructions or interference zED-P/-LCD/-H Up to 1000 m (3280 ft) without obstructions or interference -AA/-CCELL/-DCELL The above ranges assume a line-of-Sight (LOS) between the Meter/Receiver and End Device without obstructions or interference at which the diagnostic signal strength web interface registers approximately 25%. Antenna Frequency: Impedance: Connector: 2400 to 2500 Mhz 50 ohm Reverse Polarity SMA Plug
POWER (zCDR) Power Input: 9 to 12 Vdc Consumption: 2.5 W max. Safety Qualified ac Power Adapter (included) Nominal Output: 9 Vdc @ 0.5 A Input: 100 to 240 Vac, 50/60 Hz POWER (zED) Alkaline Battery: Lifetime: Two AA 1.5 Vdc, supplied Estimated 2 years with frequency of 1 reading per 2 minutes
POWER (zED-P, zED-LCD) Power Input: 5 Vdc Consumption: 0.8 W max Safety Qualified ac Power Adapter (included) Nominal Output: 5 Vdc @ 0.6 A Input: 100 to 240 Vac, 50/60 Hz Back-up Lithium Battery: One 3.6 Vdc, supplied; re-order # UWTC-BATT Lifetime: Estimated 2 years with frequency of 1 reading per 2 minutes Estimated 7 months with frequency of 1 reading per 2 minutes for zED-TC-P, zED-TC-LCD POWER (zED-LCD-AA, zED-LCD-AA-H, zED-AA-H) Alkaline Battery: Two AA 1.5 Vdc, supplied Lifetime: Estimate of 2.5 years with frequency of 1 reading per 2 minutes Estimated 8 months with frequency of 1 reading per 2 minutes for zED-TC-LCD-AA POWER (zED-CCELL) Alkaline Battery: Two C-cell 1.5 Vdc, supplied Lifetime: Estimate of 7 years with frequency of 1 reading per 2 minutes Estimated 2.3 years with frequency of 1 reading per 2 minutes for zED-TC-CCELL POWER (zED-DCELL) Alkaline Battery: Two D-cell 1.5 Vdc, supplied Lifetime: Estimate of 7 years with frequency of 1 reading per 2 minutes Estimated 5.6 years with frequency of 1 reading per 2 minutes for zED-TC-DCELL Table 6.2
Frequency continuous 10 sec 30 sec 60 sec 120 sec 300 sec Frequency 10 sec 30 sec 60 sec 120 sec 300 sec
Alkaline Battery Estimated Lifetime zED-TC/VI-LCD-AA zED-TC/VI-CCELL
5 days 5 months 7.2 months 7.9 months 8 months 8.6 months 2 weeks 1.4 years 2 years 2.2 years 2.3 years 2.4 years
4.5 years 3.5 years 4.8 years 5.6 years 5.6 years 5.8 years
zED-TP/THP/BTP/BTHP -LCD-AA & zED-THP2-LCD-AA-H/-AA-H
5.3 months 1.1 years 1.7 years 2.5 years 3.3 years
zED-TP/THP/BTP/BTHP -CCELL
1.7 years 4.3 years 7 years max 7 years max 7 years max
zED-TP/THP/BTP/BTHP -DCELL
4 years 7 years max 7 years max 7 years max 7 years max
ENVIRONMENT Operating Temperatures: zED-P: zCDR: zED-LCD:
zED, zED-CCELL, -DCELL, -AA-H: zED-LCD-AA, zED-LCD-AA-H: AC Power Adapter:
-18º to 55ºC (-0.4º to 131ºF) 90% RH, non-condensing -20º to 70ºC (-4º to 158ºF) 90% RH, non-condensing 0º to 70ºC (32º to 158ºF) 90% RH, non-condensing 0º to 40ºC (32º to 104ºF) -10º to 60ºC (14º to 140ºF) 90% RH, non-condensing -10º to 55ºC (14º to 131ºF) 90% RH, non-condensing
Storage Temperatures: zED, zED-P/-CCELL/DCELL, zCDR: -40º to 125ºC (-40º to 257ºF), with exception of batteries zED-LCD, Antenna, AC Adapter: -20º to 70ºC (-4º to 158ºF) SAFETY & REGULATORY COMPLIANCE Safety: EN60950-1:2006 (IEC 60950-1:2005) Safety Requirement under article 3.1.a of the R&TTE EMC: EN 301 489-1, V1.6.1:2005-09 Electromagnetic compatibility article 3.1.b of the R&TTE EN 301 489-17, V1.2.1:2002-08 Electromagnetic compatibility article 3.1.b of the R&TTE EN 55022:2006 + A1:2007, Class B, (CISPR 22 +A1:2005) Radio: EN 300 328 V1.7.1:2006-10 Spectrum article 3(2) of the R&TTE FCC: Part 15C, Class DTS Intentional radiator tested for 15.205, 15.209, 15.247(d), 15.215(c), 15.247(a)(2), 15.247(b), 15.247(e) (See Appendix H). CE: The product herewith complies with the essential requirements and other relevant provisions of the R&TTE Directive 1999/5/EC, the EMC Directive 2004/108/EC, and the Low Voltage Directive 2006/95/EC, and carries the CE-marking accordingly. The following CE Mark is affixed to this equipment. See Appendix H. The CE declaration is available at the website listed on the cover page of this manual. PACKAGING See Section 2.0 GENERAL Software: The software packages available for the zSeries wireless system are iConnect (configuration software for the Ethernet interface), iLog (Excel-based software for automatic data logging), and Mail Notifier (email alarm notification software).
PART 7 FACTORY PRESET VALUES PRESET PARAMETERS IP Address Gateway Address Subnet Mask Device Host Name Login Password Admin Password DHCP Web Server TCP Connections Port # Channel PID Unit Address Group Network ID Address Name End Device Name Check Box Update readings (seconds) Offset1, Offset2, Offset3, Offset4 TC Type Temperature Unit Pressure Unit DIP Switches: Coordinator 4 Position Coordinator 8 Position End Device 8 Position
192.168.1.200 0.0.0.0 255.255.255.0 z and last 4 digits from the MAC address 12345678 00000000 Disabled Enabled 1 2000 Auto Detect 13106 (0x3332) A 000 zSeries ABCDEFGH Checked 10 seconds 0 K Type C mbar all OFF all OFF all OFF
User of this manual should be familiar with following definitions:
ARP (Address Resolution Protocol) is a protocol for mapping an Internet Protocol address (IP address) to a physical machine address that is recognized in the local network. For example, the IP address in use today is an address that is 32-bits long. In an Ethernet local area network, however, addresses for attached devices are 48-bits long. (The physical machine address is also known as a Media Access Control or MAC address.) A table, usually called the ARP cache, is used to maintain a correlation between each MAC address and its corresponding IP address. ARP provides the protocol rules for making this correlation and providing address conversion in both directions.
Ethernet is a network protocol defined by the IEEE 802.3 standard. Ethernet-based networks use MAC Address rather then IP Address to exchange data between computers. By using ARP and adding TCP/IP support, Ethernet devices may be connected as part of the Internet. An Ethernet LAN typically uses coaxial cable or special grades of twisted pair wires. The most commonly installed Ethernet systems are called 10BASE-T and provide transmission speeds up to 10 Mbps. Devices are connected to the cable and compete for access using a Carrier Sense Multiple Access with Collision Detection (CSMA/CD) protocol. IP (Internet Protocol) is the method or protocol by which data is sent from one computer to another on the Internet. IP address (Internet Protocol address) is a 32-bit number that identifies each sender or receiver of information that is sent in packets across the Internet. IP Netmask is a 32-bit pattern of bits used to determine which part of the IP address is the network portion and which part is the host portion. MAC (Media Access Control) Address is your computer's unique hardware number. When you're connected to the Internet from your computer, a correspondence table relates your IP address to your computer's physical (MAC) address on the LAN. Ping is a utility that tests the network connectivity. It is used to determine if the host is capable of exchanging information with another host.
Port number/Socket number is a way to identify a specific process to which an Internet or other network message is to be forwarded when it arrives at a server. It is a predefined address that serves as a route from the application to the Transport layer or from the Transport layer to the application of the TCP/IP system. Sockets are a method for communication between a client program and a server program in a network and defined as "the endpoint in a connection". Information transferred across the Internet primarily occurs between sockets.
TCP/IP (Transmission Control Protocol/Internet Protocol) is the basic communication language or protocol of the Internet. When you are set up with direct access to the Internet, your computer is provided with a copy of the TCP/IP program just as every other computer that you may send messages to or get information from also has a copy of TCP/IP. TCP/IP often is used as a general term to indicate generic access to the Internet.
Appendix B
An IP address is a unique 32-bit address assigned to a computer and includes: • A network ID number identifying a network. • A host ID number identifying a computer on the network.
IP Address
All IP addresses have been divided into three smaller groups (classes) A, B and C
• Class A addresses have 8-bits of network ID and 24-bits of host ID. They can support a large number of hosts, approximately 2 = 16,777,216 computers per network. The IP addresses range in binary from 00000001.xxxxxxxx.xxxxxxxx.xxxxxxxx to 01111111.xxxxxxxx.xxxxxxxx.xxxxxxxx The IP addresses range in decimal from 1.x.x.x to 127.x.x.x Class A network ID's support a very large number of hosts.
• Class B addresses have 16-bits of network ID and 16-bits of host ID. They can support approximately 216 = 65,536 computers per network.
The IP addresses range in binary from 10000000 00000000.xxxxxxxx.xxxxxxxx to 10111111 11111111.xxxxxxxx.xxxxxxxx The IP addresses range in decimal from 128.0.x.x to 191.255.xxx.xxx Class B network ID's support a medium number of hosts.
• Class C addresses have 24-bits of network ID and 8-bits of host ID. They can support approximately 28 = 256 computers per network. The IP addresses range in binary from 11000000.00000000.00000000.xxxxxxxx to 11011111.11111111.11111111.xxxxxxxx The IP addresses range in decimal from 192.0.0.xxx to 223.255.255.xxx Class C network ID's support a small number of hosts.
The rest of the addresses are divided into two classes, D and E. Class D networks are not assigned to the host. They are used for multicasting. The address range from 224.x.x.x to 239.x.x.x Class E networks are experimental or reserved addresses. The address range from 240.x.x.x to 247.x.x.x
Appendix C
IP Netmask or Subnet Mask is a 32-bit pattern of ones and zeros used to determine network portion of an IP address from the host portion of the IP address. Subnet mask is a network ID that is created by borrowing bits from host portion of IP address and using them as part of a network ID. The table below shows a default subnet mask for address Classes A, B, and C. Each bit that is set to "1" in the subnet mask corresponds to the bit in the IP address that is to be used as the network ID. Each bit that is set to "0" in the subnet mask corresponds to a bit in the IP address that is to be used as the host ID. Class A Class B Class C Address Class 11111111 00000000 00000000 00000000 11111111 11111111 00000000 00000000 11111111 11111111 11111111 00000000 Mask Binary Value Mask Decimal Value or Dotted Notation 255.0.0.0 255.255.0.0 255.255.255.0
IP Netmask
If your network requires more network ID's, you can extend the default subnet mask to include additional bits from the host ID. This allows for additional network ID's within the network. The table below shows some examples of subnet masks and bits moved from the hosts ID to create a new subnet. Mask Dotted Notation 255.0.0.0 (Default) 255.192.0.0 255.224.0.0 255.240.0.0 255.248.0.0 255.252.0.0 255.254.0.0 255.255.0.0 255.255.128.0 255.255.192.0.0 ……………......... 255.255.255.252 11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111 ........ 11111111 Mask Binary Class A 00000000 00000000 11000000 00000000 11100000 00000000 11110000 00000000 11111000 00000000 11111100 00000000 11111110 00000000 11111111 00000000 11111111 10000000 11111111 11000000 ........ ........ 11111111 11111111 Class B 11111111 00000000 11111111 11000000 ........ ........ 11111111 11111111 Class C 11111111 11111111 11111111 11111111 ........ ........ 11111111 11111111 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ........ 11111100 0 2 3 4 5 6 7 8 9 10 . 22
Mask Bits
255.255.0.0 (Default) 255.255.192.0 ……………......... 255.255.255.252
To determine the number of valid hosts ID's remaining after subnetting, use the following equation: 2n – 2, where n is the number of octet digits left after the subnet mask.
255.255.255.0 (Default) 255.255.255.192 …………………. 255.255.255.254
11111111 11111111 ........ 11111111 11111111 11111111 ........ 11111111
00000000 00000000 ........ 11111100 00000000 11000000 ........ 11111100
0 2 . 14 0 2 . 6
Appendix D ASCII Char NUL SOH STX ETX EOT ENQ ACK BEL BS HT LF VT FF CR SO SI DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US SP ! " # $ % & ' ( ) * + , .
Dec 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
Hex 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E
Binary No Parity 00000000 00000001 00000010 00000011 00000100 00000101 00000110 00000111 00001000 00001001 00001010 00001011 00001100 00001101 00001110 00001111 00010000 00010001 00010010 00010011 00010100 00010101 00010110 00010111 00011000 00011001 00011010 00011011 00011100 00011101 00011110 00011111 00100000 00100001 00100010 00100011 00100100 00100101 00100110 00100111 00101000 00101001 00101010 00101011 00101100 00101101 00101110
ASCII Chart ASCII Char @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h I j k l m n
Dec 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110
Hex 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E
Binary No parity 01000000 01000000 01000010 01000011 01000100 01000101 01000110 01000111 01001000 01001001 01001010 01001011 01001100 01001101 01001110 01001111 01010000 01010001 01010010 01010011 01010100 01010101 01010110 01010111 01011000 01011001 01011010 01011011 01011100 01011101 01011110 01011111 01100000 01100001 01100010 01100011 01100100 01100101 01100110 01100111 01101000 01101001 01101010 01101011 01101100 01101101 01101110
Appendix / 0 1 2 3 4 5 6 7 8 9 : ; < = > ?
ASCII Control Codes ASCII Dec Hex Ctrl Key Definition ASCII Dec Hex Ctrl Key Definition Char Equiv. Char Equiv. NUL 00 00 Crtl @ Null Character DC1 17 11 Crtl Q Data Control 1 - XON SOH 01 01 Crtl A Start of DC2 18 12 Crtl R Data Control 2 Header STX 02 02 Crtl B Start of Text DC3 19 13 Crtl S Data Control 3 - XOFF ETX 03 03 Crtl C End of Text DC4 20 14 Crtl T Data Control 4 EOT 04 04 Crtl D End of NAK 21 15 Crtl U Negative Transmission Acknowledge ENQ 05 05 Crtl E Inquiry SYN 22 16 Crtl V Synchronous Idle ACK 06 06 Crtl F Acknowledge ETB 23 17 Crtl W End of Trans Block BEL 07 07 Crtl G Bell CAN 24 18 Crtl X Cancel BS 08 08 Crtl H Back Space EM 25 19 Crtl Y End of Medium HT 09 09 Crtl I Horizontal SUB 26 1A Crtl Z Substitute Tabulation LF 10 0A Crtl J Line Feed ESC 27 1B Crtl [ Escape VT 11 0B Crtl K Vertical FS 28 1C Crtl \ File Separator Tabulation FF 12 0C Crtl L Form Feed GS 29 1D Crtl ] Group Separator CR 13 0D Crtl M Carriage RS 30 1E Crtl | Record Return Separator SO 14 0E Crtl N Shift Out US 31 1F Crtl _ Unit Separator SI 15 0F Crtl O Shift In SP 32 20 Space DLE 16 10 Crtl P Data Link Escape
ASCII Chart Continuation 00101111 o 111 p 00110000 112 q 00110001 113 00110010 r 114 00110011 s 115 00110100 t 116 00110101 u 117 00110110 v 118 00110111 w 119 00111000 x 120 y 00111001 121 00111010 z 122 { 00111011 123 | 00111100 124 } 00111101 125 00111110 ~ 126 00111111 DEL 127
01101111 01110000 01110001 01110010 01110011 01110100 01110101 01110110 01110111 01111000 01111001 01111010 01111011 01111100 01111101 01111110 01111111
Appendix E
Error # Description -8003
iLog Error Messages
Note Ethernet cable is disconnected, Coordinator is powered off, connections across the firewall require longer "connection to socket time out" setting. Wrong IP or wrong Port number was used. No data was sent.
-10005 Failed to find the Coordinator.
User stopped logging readings.
-10006 Windows socket was closed. -10007 Windows socket error.
-10008 The Coordinator failed to respond to a request. Wrong IP or wrong Port number was used. -10011 Response came empty. -10012 Device responded with "Serial Time Out" string.
-10014 Terminal Server Mode when the Port is 1000. -15100 Error on obtaining the temperature reading. -15105 Error on obtaining the humidity reading.
Try Port 2000 in iLog configuration. Possibly the iLog is configured for wrong product model. Possibly the iLog is configured for wrong product model.
Possibly the iLog is configured for wrong product model.
-15110 Error on obtaining the dew point reading.
Possibly the iLog is configured for wrong product model.
Appendix F ASCII / TELNET COMMANDS TABLE Command Device / Group ID Description (see notes below if *) Example ERDB Device ID: 000 – 031 Get sensor readings of an End Device Get reading for sensor 15, ERDB015 ERDR Device ID: 000 – 031 Get individual reading or parameter Get the first temp. reading Reading/parameter: a-s *4 for sensor 1, ERDR001c ERDG Group ID: 00A - 00D, ALL Get sensor readings of a group / Get readings for all groups of sensors group B, ERDG00B EQNF Device ID: 000 – 031 Get name, *3 status and firmware Get name for sensor 15, version of an End Device EQNF015 EQNG Group ID00A - 00D, ALL Get name, *3 status and firmware Get name for all sensors, version of a group/all groups of sensors EQNGALL EQPE Device ID: 000 – 031 Get sleep period, battery voltage, signal Get sleep period for strength, success, network address and sensor 15, EQPE015 parent address of an End Device EQPG Group ID: 00A - 00D Get sleep period, battery voltage, signal Get sleep period of strength, success, network address and group B, EQPG00B parent address of a group / all groups of sensors ESPD Device ID: 000-031, ALL Set the sleep period for an End Device / Set sensor 15's sleep all sensors *1 period to 30 seconds, ESPD015 30 ESNM Device ID: 000 – 031 Set the name of an End Device *2 Set the name of sensor 15, ESNM015 z15 ERST Device ID: 000 – 031, ALL Reset an End Device / all sensors Reset all sensors, ERSTALL ESTR Device ID: 000 – 031, ALL Request End Device(s) to go into Put all sensors into identify mode identify mode, ESTRALL ESTP Device ID: 000 – 031, ALL Request End Device(s) to resume Resume all sensor to normal operation normal operation, ESTPALL CRST Reset wireless network Reset network, CRST CSTS Get personal network ID and channel Get wireless network information information, CSTS FACTORY Sets the Coordinators Ethernet FACTORY xxxxxxxx AdminPassword configurations to Factory Defaults xxxxxxxx is the Admin Password *1 Argument: 1 – 32767 (1 seconds to about 9 hours) *2 Argument: xxxxxxxx (8 characters) *3 and *4 See the following page
Appendix F ASCII /TELNET COMMANDS TABLE (continued) * An example of the status of an End Device Command: EQNG00A Response: 7 EngrLAB 01000010 2.0 7 is the Device ID (DID) of the End Device. EngrLAB is the name for the End Device. "01000010" is the bitmap representation of the internal state. The meaning for each bit is described below (bit 7 starts from the left). Bit 4 shows if there is any pending "identify Bit 7 shows if the sensor is plugged mode request" command for the End Device. into the End Device. '1' means there is '1' means a "start" command is issued. no sensing device detected. Bit 3 not used Bit 6 shows if the communication to the End Device is lost. '1' means there Bit 2 shows if there is any pending "reset" has not been any data received from command for the End Device. '1' means a that particular End Device for 1 minute "reset" command is issued. or 4 times the update rate, whichever is Bit 1 shows the source of power supply to a longer time interval. the End Device. '1' means it's powered by an Bit 5 shows if there is more than one adapter and '0' means it's powered by End Device having the same dip switch batteries. configuration. '1' means more than 1 Bit 0 shows the operation mode of the End End Device has the same Network ID Device. '1' means it is in identification mode and Device ID. and '0' means it is in normal operation mode. 2.0 is version of the firmware in the End Device. Based on the above information, End Device # 7 has not been communicating with the Coordinator and its power is supplied by an adapter. Reading/parameter for ERDR command
Options (lower case) a b c e i j k l q r s f d Sequence number Device type First temp / error message First RH / barometric pressure / error message Second temp / error message Second RH / barometric pressure / error message Update rate Battery voltage Signal strength Success rate Name Status Firmware version Reading/parameter ZED_T ZED_T_BTP ZED_T_THP ZED_T_TP ZED_TH ZED_TH_BTP ZED_TH_THP ZED_TH_TP ZED_BT ZED_BT_BTP
End Device Types
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 20
Appendix G
Frequently Asked Questions (FAQ)
Q: Java applet is not loaded? A: Check Java Setting (icon in Control Panel). Make sure cache is disabled and your web browser is enabled for Java. Q: I do not see any readings even if the applet is loaded, what could be wrong? A: 1) Make sure the Coordinator and the End Device have the same Network ID (NID). 2) Check if the battery is still good. You should be able to see the blue LED when you power the End Device on. 3) If the End Device keeps blinking every second after it is powered on, that means it cannot find the Coordinator. Try to adjust the antenna and relocate the End Device according to Section 5.1.
Q: What are the error messages that appear on the "Reading", "Chart", and "Diagnostic" pages? Open A: It means that the End Device cannot detect any of its sensors. Check the connections for the internal sensor and the external probe if any. ID A: It means that there are more than one End Device sharing the same Device ID (DIP switches #1-5). Remember, each sensor should have a unique Device ID in the same wireless network. Turning the device into Identify Mode may help searching for the physical location of such End Devices. Once the problem is resolved, click on the "Reset Sensor" button located on the Sensors Parameters page to remove the "ID" error code. Lost A: It means that the End Device found the Coordinator when it was powered on, but it cannot communicate with it currently. Make sure the Coordinator and the End Device have the same Network ID (NID). Also, make sure the Coordinator is powered on, the IEEE802.15.4 communication channel is unchanged, DIP switch #1 (of the 8-DIP switch row) on the Coordinator was ON during the last Coordinator's power reset, and there is no obstructive objects blocking the communications path (see Section 5 for more details). If the obstructive object is only temporary, you will get the sensor readings once the path is open. Q: Nothing happens when I click on the Data Logging button, what could be wrong? A: The Java policy file is not setup properly. Make sure you get a Java policy file and copy it to a folder in the host computer. Then input the java runtime argument in Java Setup (Control Panel) with the appropriate path to the policy file. Close all web browser and re-open the applet again. See Java Setup Section.
Appendix G Frequently Asked Questions (FAQ) (continued) Q: The Chart trend line for all the variables are broken, what could be wrong? A: It indicates that a TCP connection to the Coordinator was timed-out and no data was obtained. Make sure the Coordinator is still on in the network and powered up. If there are too many broken lines, it may indicate that the network load is too heavy.
Q: The trend line for one of my sensors inside one End Device is broken, what could be wrong? A: It indicates that TCP connection to the Coordinator is good but the Coordinator did not have any readings from the corresponding End Device. Make sure End Device is still blinking according to the update rate. It could be caused by a reset/power cycling of the Coordinator as well. Q: Nothing happens when I click on the Save Current Graph button, what could be wrong? A: The Java policy file is not setup properly. Make sure you get a Java policy file and copy it to a folder in the host computer. Then input the java runtime argument in Java Setup (Control Panel) with the appropriate path to the policy file. Close all web browser and re-open the applet again. See Java Setup Section.
Q: The End Device repeatedly makes 4 blinks every 2 seconds and then goes off for 3 minutes, what does this mean? A: It is equivalent to getting a "Lost" message in the Java applets. It means that the End Device found the Coordinator when it was powered on, but it cannot communicate with it currently. Make sure the Coordinator and the End Device have the same Network ID (NID). Also, make sure the Coordinator is powered on, the IEEE802.15.4 communication channel is unchanged, the first DIP switch (of the 8-DIP switch row) on the Coordinator was on during the last Coordinator's power reset, and there is no obstructive objects blocking the communications path (see Section 5 for more details). If the obstructive object is only temporary, you will get the sensor readings once the path is open. Q: While the End Device is up and running I notice a sequence of blinking patterns that seem to repeat themselves, what could be wrong? A: It means that the End Device needs several retransmissions before getting an acknowledgement packet back from the Coordinator. This indicates a reduced performance since more retransmissions required. Retransmissions consume power and cause shorter battery lifetime. Adjust the antenna and relocate the End Device for better communications. See Section 5 for more details.
Q: Nothing is shown inside the Diagnostic page/applet, what could be wrong? A: The first thing you want to try is to click your mouse right inside the box. Then minimize and restore the web browser. Try to move the scrollbar as well. If nothing works after about a minute, check the TCP connection to the Coordinator.
Appendix H
This device complies with part 15 rules. Operation is subject to the following two conditions: 1) this device may not cause harmful interference, and 2) this device must accept any interference received, including interference that may cause undesired operation.
In order to comply with FCC radio frequencies (RF) exposure limits, dipole antennas should be located at a minimum 7.9" (200mm) or more from the body of all persons.
Warnings and Regulatory Information
This equipment has been tested and found to comply with the limits of a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a residential environment. This equipment generates, uses, and radiates radio frequency energy, and if not installed and used in accordance with the instructions, may cause harmful interference. However, there is no guarantee that interference will not occur. If this equipment does cause interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to correct the interference by one of the following measures: • Reorient or relocate the receiving antenna. • Increase separation between the equipment and receiver. • Connect the equipment to an outlet on a circuit different from which the receiver is connected. • Consult dealer or an experienced radio/TV technician. The following alert sign indicates that there are restrictions on usage of the equipment in regards to power limitations on Equivalent Isotropic Radiated Power (EIRP) levels in the European Community. The following are user restrictions: • Wideband Data Transmission Systems on the band 2400 – 2483.5 MHz in Europe is limited to a Maximum of 10 mW (10dBm) for Direct Sequence Spread Spectrum (DSSS). See Annex 3 of ERC/REC 70-03, decision ERC/DEC/ (01)07. • Combinations of power levels and antennas resulting in a radiated power level above 10 mW - EIRP for Direct Sequence Spectrum (DSSS) devices are considered as not compliant, and are not allowed for use within the European Community and other countries that have adopted the European R&TTE directive 1995/5/EC or the CEPT recommendation ERC/REC 70-03 or both.
• The users in Europe are instructed to change the default 20 dBm level to 10 dBm via the Web Interface of the Coordinator. The End Devices will follow the power level set on the Coordinator upon power-up; failure to change the default U.S.A. power level setting will violate the regulations requirements for Europe
Appendix H
Warnings and Regulatory Information (continued)
MAXIMUM POWER LEVELS AND ANTENNA GAINS Antenna Gain 2.2 dBi 2.2 dBi Output Max 18.0 dBm Maximum Radiated 10 dBm 20 dBm
U.S.A (Regulatory 4W) (DSSS)
EUROPE (Regulatory 10mW)
7.0 - 7.5 dBm
The default 20 dBm must be changed to 10 dBm to comply with power level regulations. The 0.5 dBm variation depends on the internal DC power used (3V, 3.3V, 3.7V max) of the different models.
Appendix I
I.1 Accuracy
Sensor Information
Accuracies are tested at Manufacture's Outgoing Quality Control at 25°C (77°F) and 3.3V. Values exclude hysteresis and non-linearity, and is only applicable to noncondensing environments. I.2 Operating Conditions Sensor works stable within recommended normal range – see Figure. Long term exposures to conditions outside normal range, especially at humidity >80%RH, may temporarily offset the RH signal (+3 %RH after 60h). After return to normal range it will slowly return towards calibration state by itself. See Section I.4 "Reconditioning Procedure" to accelerate eliminating the offset. Prolonged exposure to extreme conditions may accelerate ageing. Figure I.3 Normal Range
RH Accuracy Chart
Figure I.1
Temperature Accuracy Chart
Figure I.2
Appendix I Sensor Information (continued)
I.3 Storage Conditions and Handling Instructions It is of great importance to understand that a humidity sensor is not a normal electronic component and needs to be handled with care. Chemical vapors at high concentration in combination with long exposure times may offset the sensor reading. For these reasons it is recommended to store the sensors in original packaging including the sealed ESD bag at following conditions: Temperature shall be in the range of 10°C – 50°C (0 – 80°C for limited time) and humidity at 20 – 60%RH (sensors that are not stored in ESD bags). For sensors that have been removed from the original packaging we recommend to store them in ESD bags made of PE-HD8. In manufacturing and transport the sensors shall be prevented of high concentration of chemical solvents and long exposure times. Out-gassing of glues, adhesive tapes and stickers or out-gassing packaging material such as bubble foils, foams, etc. shall be avoided. Manufacturing area shall be well ventilated. I.4 Reconditioning Procedure As stated above extreme conditions or exposure to solvent vapors may offset the sensor. The following reconditioning procedure may bring the sensor back to calibration state: Baking: 100 – 105°C at < 5%RH for 10h Re-Hydration: 20 – 30°C at ~ 75%RH for 12h. (75%RH can conveniently be generated with saturated NaCl solution. 100 – 105°C correspond to 212 – 221°F, 20 – 30°C correspond to 68 – 86°F) I.5 Temperature Effects Relative humidity reading strongly depends on temperature. Therefore, it is essential to keep humidity sensors at the same temperature as the air of which the relative humidity is to be measured. In case of testing or qualification the reference sensor and test sensor must show equal temperature to allow for comparing humidity readings. The packaging of sensor is designed for minimal heat transfer from the pins to the sensor. Still, if the sensor shares a PCB with electronic components that produce heat it should be mounted in a way that prevents heat transfer or keeps it as low as possible. Furthermore, there are self-heating effects in case the measurement frequency is too high. I.6 Light The sensor is not light sensitive. Prolonged direct exposure to sunshine or strong UV radiation may age the housing.
I.7 Materials Used for Sealing / Mounting Many materials absorb humidity and will act as a buffer increasing response times and hysteresis. Materials in the vicinity of the sensor must therefore be carefully chosen. Recommended materials are: Any metals, LCP, POM (Delrin), PTFE (Teflon), PE, PEEK, PP, PB, PPS, PSU, PVDF, PVF. For sealing and gluing (use sparingly): Use high filled epoxy for electronic packaging (e.g. glob top, underfill), and Silicone. Out-gassing of these materials may also contaminate the sensor (see Section I.3). Therefore try to add the sensor as a last manufacturing step to the assembly, store the assembly well ventilated after manufacturing or bake at 50°C for 24h to outgas contaminants before packing.
NEWPORT Electronics, Inc. warrants this unit to be free of defects in materials and workmanship for a period of one (1) year from the date of purchase. In addition to NEWPORT's standard warranty period, NEWPORT Electronics will extend the warranty period for one (1) additional year if the warranty card enclosed with each instrument is returned to NEWPORT.
If the unit should malfunction, it must be returned to the factory for evaluation. NEWPORT's Customer Service Department will issue an Authorized Return (AR) number immediately upon phone or written request. Upon examination by NEWPORT, if the unit is found to be defective it will be repaired or replaced at no charge. NEWPORT's WARRANTY does not apply to defects resulting from any action of the purchaser, including but not limited to mishandling, improper interfacing, operation outside of design limits, improper repair, or unauthorized modification. This WARRANTY is VOID if the unit shows evidence of having been tampered with or shows evidence of being damaged as a result of excessive corrosion; or current, heat, moisture or vibration; improper specification; misapplication; misuse or other operating conditions outside of NEWPORT's control. Components which wear are not warranted, including but not limited to contact points, fuses, and triacs.
NEWPORT is pleased to offer suggestions on the use of its various products. However, NEWPORT neither assumes responsibility for any omissions or errors nor assumes liability for any damages that result from the use of its products in accordance with information provided by NEWPORT, either verbal or written. NEWPORT warrants only that the parts manufactured by it will be as specified and free of defects. NEWPORT MAKES NO OTHER WARRANTIES OR REPRESENTATIONS OF ANY KIND WHATSOEVER, EXPRESSED OR IMPLIED, EXCEPT THAT OF TITLE, AND ALL IMPLIED WARRANTIES INCLUDING ANY WARRANTY OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY DISCLAIMED. LIMITATION OF LIABILITY: The remedies of purchaser set forth herein are exclusive and the total liability of NEWPORT with respect to this order, whether based on contract, warranty, negligence, indemnification, strict liability or otherwise, shall not exceed the purchase price of the component upon which liability is based. In no event shall NEWPORT be liable for consequential, incidental or special damages.
CONDITIONS: Equipment sold by NEWPORT is not intended to be used, nor shall it be used: (1) as a "Basic Component" under 10 CFR 21 (NRC), used in or with any nuclear installation or activity; or (2) in medical applications or used on humans. Should any Product(s) be used in or with any nuclear installation or activity, medical application, or used on humans, or misused in any way, NEWPORT assumes no responsibility as set forth in our basic WARRANTY / DISCLAIMER language, and additionally purchaser will indemnify NEWPORT and hold NEWPORT harmless from any liability or damage whatsoever arising out of the use of the Product(s) in such a manner.
Direct all warranty and repair requests/inquiries to the NEWPORT Customer Service Department. BEFORE RETURNING ANY PRODUCT(S) TO NEWPORT, PURCHASER MUST OBTAIN AN AUTHORIZED RETURN (AR) NUMBER FROM NEWPORT'S CUSTOMER SERVICE DEPARTMENT (IN ORDER TO AVOID PROCESSING DELAYS). The assigned AR number should then be marked on the outside of the return package and on any correspondence. The purchaser is responsible for shipping charges, freight, insurance and proper packaging to prevent breakage in transit. FOR WARRANTY RETURNS, please have the following information available BEFORE contacting NEWPORT: 1. P.O. number under which the product was PURCHASED, 2. Model and serial number of the product under warranty, and 3. Repair instructions and/or specific problems relative to the product. FOR NON-WARRANTY REPAIRS, consult NEWPORT for current repair charges. Have the following information available BEFORE contacting NEWPORT: 1. P.O. number to cover the COST of the repair, 2. Model and serial number of product, and 3. Repair instructions and/or specific problems relative to the product.
Return Requests/Inquiries
NEWPORT's policy is to make running changes, not model changes, whenever an improvement is possible. This affords our customers the latest in technology and engineering. NEWPORT is a registered trademark of NEWPORT Electronics, Inc. © Copyright 2010 NEWPORT Electronics, Inc. All rights reserved. This document may not be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without prior written consent of NEWPORT Electronics, Inc.
For immediate technical or application assistance please call:
Newport Electronics, Inc. 2229 South Yale Street • Santa Ana, CA • 92704 • U.S.A. TEL: (714) 540-4914 • FAX: (203) 968-7311 Toll Free: 1-800-639-7678 • www.newportUS.com • e-mail:firstname.lastname@example.com ISO 9001 Certified Newport Technologies, Inc. 976 Bergar • Laval (Quebec) • H7L 5A1 • Canada TEL: (514) 335-3183 • FAX: (514) 856-6886 Toll Free: 1-800-639-7678 • www.newport.ca • e-mail:email@example.com
Newport Electronics, Ltd. One Omega Drive • River Bend Technology Centre Northbank, Irlam • Manchester M44 5BD • United Kingdom Tel: +44 161 777 6611 • FAX: +44 161 777 6622 Toll Free: 0800 488 488 • www.newportuk.co.uk • e-mail:email@example.com Newport Electronics B.V. - Benelux TEL: +31 20 3472121 • FAX: +31 20 6434643 Toll Free: 0800 0993344 • www.newport.nl • e-mail: firstname.lastname@example.com
Newport Electronics GmbH Daimlerstrasse 26 • D-75392 Deckenpfronn • Germany TEL: 49 7056 9398-0 • FAX: 49 7056 9398-29 Toll Free: 0800 / 6397678 • www.newport.de • e-mail: email@example.com Newport Electronique S.A.R.L. - France TEL: +33 1 61 37 29 00 • FAX: +33 1 30 57 54 27 Toll Free: 0800 466 342 • www.newport.fr • e-mail: firstname.lastname@example.com Mexico and Latin America FAX: 001 (203) 359-7807 TEL En Español: 001 (203) 359-7803
Newport Electronics spol s.r.o. Frystatska 184, 733 01 Karviná • Czech Republic TEL: +420 59 6311899 • FAX: +420 59 6311114 Toll Free: 0800-1-66342 • www.newport.cz • e-mail: email@example.com