User’s Guide
®
®
Shop on line at
omega.com
e-mail: info@omega.com
For Latest Product Manuals
omegamanual.info
zSeries Wireless Sensor System
It isthe policy of OMEGA to complywith all worldwide safety and EMC/EMI regulations that apply.
OMEGAis constantly pursuing certificationof its products to the European New Approach Directives. OMEGAwill add the CE mark
to every appropriatedevice upon certification.
The information contained in this document is believed to be correct, but OMEGA Engineering, Inc. accepts no liability for any
errors it contains, and reserves the right to alter specifications without notice.
WARNING:Theseproducts are not designedfor use in, and should not be used for, patient-connected applications.
This device is marked with the international caution symbol. It is important to read the Setup Guide before installing or
commissioning this device as the guide contains important information relating to safety and EMC.
TABLE OF CONTENTS
Part 1: Introduction
Part 2: Hardware
Part 3: Network Configuration
Part 4: Operations
1.1 Safety and EMC Considerations .................................................................2
1.2 Before You Begin .........................................................................................2
1.3 Description....................................................................................................2
2.1 Parts of the End Device ..............................................................................5
2.2 Dimensions and Mounting - End Device ..................................................6
2.3 External Sensors/Probes for the End Device ..........................................6
2.4 Disassembly - End Device...........................................................................7
2.5 Parts of the Coordinator ..............................................................................8
2.6 Dimensions and Mounting - Coordinator...................................................9
2.7 DIP Switches...............................................................................................10
2.7.1 DIP Switch Setup: Device ID (DID) .............................................10
2.7.2 DIP Switch Setup: Network ID (NID) ...........................................10
2.7.3 DIP Switch Setup: Ethernet Coordinator ...................................11
2.8 Network Communication Interfaces ........................................................13
2.8.1 10Base-T RJ-45 Pinout.................................................................13
2.8.2 10Base-T Crossover Wiring.........................................................13
3.1 Ethernet (MAC) Address ...........................................................................14
3.2 Network Protocols .....................................................................................14
3.3 DHCP .......................................................................................................14
3.4 DNS .......................................................................................................15
3.5 IP Address ..................................................................................................15
3.5.1 Default IP Address........................................................................15
3.5.2 Changing TCP/IP Properties on Your Computer .......................15
4.0 Testing the Connection .............................................................................17
4.1 iConnect Software......................................................................................17
4.2 Setting a new IP Address over the Network ...........................................20
4.3 Coordinator’s Configurations and Operations .......................................21
4.3.1 Power Up Device ..........................................................................22
4.3.2 Get Readings from the End Device ............................................24
4.3.3 Java Runtime Environment Setup .............................................25
4.3.3.1 Java Runtime Environment 1.4 Setup Instructions...................25
4.3.3.2 Java Runtime Environment 1.5 (5.0) Setup Instructions ..........26
4.3.3.3 Browser Proxy Selection .............................................................27
4.3.4 Java Policy ....................................................................................28
4.3.5 Chart ..............................................................................................30
4.3.6 Diagnostic .....................................................................................32
4.3.7 Configuration ................................................................................33
4.3.8 Sensor Setup.................................................................................34
4.3.9 Access Control ............................................................................37
4.4 Telnet Setup ...............................................................................................38
4.5 HTTPget Program.......................................................................................38
4.5.1 HTTPget using Port 2000 ............................................................38
4.5.2 HTTPget and ARP to Setup Device IP Address ........................40
i
TABLE OF CONTENTS
(continued)
4.6 ARP Protocol ..............................................................................................40
4.7 iLog Software..............................................................................................42
4.8 Mail Notifier Software.................................................................................43
4.8.1 Installation.....................................................................................43
4.8.2 Program Options Setup and Configuration ..............................44
4.8.3 Device Setting Setup and Configuration ....................................45
Part 5: Environment / Operating Conditions...................................................................... 47
Part 6: Specifications .......................................................................................................... 52
Part 7: Factory Preset Values ..............................................................................................54
Appendix A Glossary......................................................................................................55
Appendix B IP Address ..................................................................................................56
Appendix C IP Netmask..................................................................................................57
Appendix D ASCII Chart ................................................................................................58
Appendix E iLog Error Messages..................................................................................60
Appendix F Telnet Commands Table ............................................................................61
Appendix G Frequently Asked Questions (FAQ)..........................................................63
5.1 General Deployment Guidelines .............................................................. 47
5.2 With Line-of-Sight ......................................................................................49
5.3 Without Line-of-Sight ................................................................................50
5.4 Casing and Closure Around the Antenna ................................................50
5.5 Fine Adjustment in Performance ..............................................................51
ASCII Chart Control Codes .......................................................................59
ii
LIST OF FIGURES:
Figure 1.1 zSeries Wireless System on the Ethernet Network...................................4
Figure 2.1 Parts of the End Device .............................................................................5
Figure 2.2 Mounting the End Device ..........................................................................6
Figure 2.3 External Sensors/Probes ...........................................................................6
Figure 2.4 Disassembly of the End Device .................................................................7
Figure 2.5 Parts of the Coordinator .............................................................................8
Figure 2.6 Mounting the Coordinator .........................................................................9
Figure 2.7 Device ID (DID) - 8 Position DIP Switch Setup ........................................10
Figure 2.8 Network ID (NID) - 8 Position DIP Switch Setup .....................................11
Figure 2.9 Ethernet - 4 Position DIP Switch Setup ...................................................12
Figure 2.10 RJ45 Pinout ................................................................................................13
Figure 2.11 10Base-T Crossover Cable Wiring ...........................................................13
Figure 3.1 4 Position DIP Switch on Bottom Side of Coordinator ..........................14
Figure 3.2 Network Connections ...............................................................................16
Figure 3.3 Network Connections ...............................................................................16
Figure 4.1 Pinging the Coordinator from MS-DOS Prompt .....................................17
Figure 4.2 Assigning an IP Address using iConnect ...............................................18
Figure 4.3 Accessing the zSeries System for Configuration ..................................19
Figure 4.4 Access Control .........................................................................................20
Figure 4.5 Home Page Menu .....................................................................................21
Figure 4.6 Login and Administrator Password .........................................................21
Figure 4.7 Select Readings by Group .......................................................................22
Figure 4.8 Readings ..................................................................................................23
Figure 4.9 Java 1.4.2.x Screen Shot ...........................................................................25
Figure 4.10 Java 1.5.x.x Screen Shot ...........................................................................26
Figure 4.11 Java Policy..................................................................................................28
Figure 4.12 Java Policy..................................................................................................29
Figure 4.13 Select Chart by Group ...............................................................................30
Figure 4.14 Chart ........................................................................................................30
Figure 4.15 Diagnostic ...................................................................................................32
Figure 4.16 Configuration ............................................................................................33
Figure 4.17 Sensor Setup by Group .............................................................................34
Figure 4.18 Sensor Setup ..............................................................................................35
Figure 4.19 Sensor Parameters ....................................................................................36
Figure 4.20 Access Control ..........................................................................................37
Figure 4.21 HTTPget Example of Polling End Device #1, 2, 3, 4 ................................39
Figure 4.22 ARP Commands and Responses .............................................................41
Figure 4.23 iLog Software Logging Data for End Device #1, 3, 4 ..............................42
Figure 4.24 Mail Notifier Main Window.........................................................................43
Figure 4.25 Mail Notifier Profile Setup..........................................................................44
Figure 4.26 Mail Notifier Device Setting ......................................................................46
Figure 5.1 Operation in Buildings ..............................................................................48
Figure 5.2 Fresnel Zone ..............................................................................................49
Figure 5.3 Materials in Buildings ...............................................................................50
Figure 5.4 Channels ....................................................................................................51
iii
iv
NOTES, WARNINGS and CAUTIONS
Information that is especially important to note is identified by the following labels:
• NOTE
• WARNING or CAUTION
• IMPORTANT
• TIP
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 effect the instrument’s functionality and must
refer to accompanying documents.
TIP: Provides you helpful hints.
FEATURES
⻬⻬
Temperature
⻬⻬
Humidity
⻬⻬
Barometric Pressure
⻬⻬
Email Alarms
⻬⻬
Web Server
⻬⻬
No Special Software
Required
1
PART 1
INTRODUCTION
1.1 Safety and EMC Considerations
Refer to the Environment/Operating Conditions Section
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.
The wireless End Devices are powered by two AA 1.5 volt alkaline batteries.
The End Devices transmit up to 300 feet (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.4GHz.
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. Each End Device
supports one or two sensors. 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, in
freezers and refrigerators.
2
1.3 Description (continued)
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. The
Coordinators include AC adapters to operate on any voltage worldwide from 100-240 Vac
and 50-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 "Chicago 5") 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.
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.
3
1.3 Description (continued)
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
4
PART 2
FRONT
REAR
11
9
10
7
8
MODEL #
SERIAL #
#.#
1
4
3
5
6
2
Unit Addr Group Net. Addr
HARDWARE
2.1 Parts of the End Device
1 8 position DIP switch (under cover), sets the NID and DID of the End Device
(see Section 2.7 for details)
2 Optional rear entry for external probes
3 Label for Unit Address, Group No. and Network Address
4 Wall mounting holes
5 Label with model and serial numbers
6 Radio module firmware revision location on label
7 Case’s tray, where the PCB, sensor and batteries are mounted
8 Case’s cover
9 Transmit LED (blue)
10 Case’s latch: squeeze sides to pull the cover off
11 Optional external probe with sensor
Figure 2.1 Parts of the End Device
5
2.2 Dimensions and Mounting - End Device
0.94
[23.8]
2.54 [64.5]
SIDE AND FRONT VIEWS INSIDE CASE, MOUNTING
2.54 [64.5] REF
0.32 [8.1]
3.61 [91.8]
3.61 [91.8] REF
1.81 [45.9]
Optional
External
Sensor
0.140
[3.56]
2 PLCS
1.90 [48.3]
Position unit where required. Mark and drill holes as required, using a #6 screw.
Material: PBT (Valox) Plastic
Figure 2.2 Mounting the End Device
2.3 External Sensors/Probes for the End Device
FROM TOP TO BOTTOM:
1) External Industrial Probe ,
Temperature / Humidity -THP
or
Barometric Pressure /
Temperature -BTP
2) External Temperature Stick
Probe -TP1
3) External Temperature Lug
Mount Probe -TP2
Figure 2.3 External Sensor/Probes
6
2.4 Disassembly - End Device
COVER
LATCH
SENSOR
BOARD
EXTERNAL
SENSOR/
PROBE
TRAY
POWER SWITCH
BATTERY CLIPS
LATCH
DIP SWITCH
MOUNTING SCREW
JTAG
8
1
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.2 for mounting dimensions.
• To connect or replace the batteries, (note the polarity of batteries).
• To access JTAG connector.
Remove Cover as shown below, by pressing sides of cover to release latches.
Figure 2.4 Disassembly of the End Device
7
2.5 Parts of the Coordinator
Figure 2.5 Parts of the Coordinator
1 Wall mounting bracket clip holes (3 places)
2 Label with model and serial numbers
3 Coordinator’s firmware revision on label
4 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)
5 Ethernet: RJ45 interface for 10BASE-T connection.
6 Case’s tray, where the PCB is mounted
7 4 position DIP switch, sets the DHCP and Factory Defaults
8 Coordinator’s radio module firmware revision on label
9 Label with default IP address, remove and then write your IP address, in the space
provided
10 Label with MAC address (in hex code)
11 Wall mounting bracket
12 Case’s cover mounting screw (2 places)
13 Label for Network address
14 Power supply: Plus (+) power supply wire connection inside the plug;
Minus (-) power supply wire connection outside the plug
15 Reset button: Used for power reseting the Ethernet board
16 Case’s cover
8
2.5 Parts of the Coordinator (continued)
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
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.
Figure 2.6 Mounting the Coordinator
9
OFF ON
1
8
1 SERIAL
2 DEFAULT
3 DHCP
4 TERMINAL
ON
OFF
1
8
OFF
ON
1
8
End Device
(cover removed)
Coordinator
(Shown in
"OFF" Position)
DID
NID
OFF
ON
6
7
8
1
(Shown in
"OFF" Position)
2 - 5
not used
NID
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.
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.
Figure 2.7 Device ID (DID) - 8 Position DIP Switch Setup
Device 12345
ID
0 OFF OFF OFF OFF OFF
1 ON OFF OFF OFF OFF
2 OFF ON OFF OFF OFF
3 ON ON OFF OFF OFF
4 OFF OFF ON OFF OFF
5 ON OFF ON OFF OFF
GROUP A
6 OFF ON ON OFF OFF
7 ON ON ON OFF OFF
8 OFF OFF OFF ON OFF
9 ON OFF OFF ON OFF
10 OFF ON OFF ON OFF
11 ON ON OFF ON OFF
12 OFF OFF ON ON OFF
13 ON OFF ON ON OFF
GROUP B
14 OFF ON ON ON OFF
15 ON ON ON ON OFF
Device 12345
ID
16 OFF OFF OFF OFF ON
17 ON OFF OFF OFF ON
18 OFF ON OFF OFF ON
19 ON ON OFF OFF ON
20 OFF OFF ON OFF ON
GROUP C
21 ON OFF ON OFF ON
22 OFF ON ON OFF ON
23 ON ON ON OFF ON
24 OFF OFF OFF ON ON
25 ON OFF OFF ON ON
10
10
26 OFF ON OFF ON ON
27 ON ON OFF ON ON
28 OFF OFF ON ON ON
GROUP D
29 ON OFF ON ON ON
30 OFF ON ON ON ON
31 ON ON ON ON ON
OFF ON
1
8
1 SERIAL
2 DEFAULT
3 DHCP
4 TERMINAL
ON
OFF
1
8
OFF
ON
1
8
End Device
(cover removed)
Coordinator
(Shown in
"OFF" Position)
DID
NID
OFF
ON
6
7
8
1
(Shown in
"OFF" Position)
2 - 5
not used
NID
2.7.2 DIP Switch Setup: Network ID (NID)
Each sensor network has a unique Network ID (or NID).
For the End Device and the Coordinator 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.
Figure 2.8 Network ID (NID) - 8 Position DIP Switch Setup
NID #6 #7 #8
13106 (0x3332) OFF OFF OFF
13107 (0x3333) ON OFF OFF
13108 (0x3334) OFF ON OFF
13109 (0x3335) ON ON OFF
13110 (0x3336) OFF OFF ON
13111 (0x3337) ON OFF ON
13112 (0x3338) OFF ON ON
13113 (0x3339) ON ON ON
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 and 0x3332.
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.
11
2.7.3 DIP Switch Setup: Ethernet - Coordinator
O
FF ON
1
8
1 SERIAL
2 DEFAULT
3 DHCP
4 TERMINAL
Coordinator
OFF
ON
14
(Shown in
"OFF" Position)
1) N/C
2) To change to default factory settings
3) To enable/disable DHCP
4) N/C
Figure 2.9 Ethernet - 4 Position DIP Switch Setup
To set the Coordinator to factory default settings:
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.
12
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 Name Description
1 +Tx + Transmit Data
2 -Tx - Transmit Data
3 +RX + Receive Data
4 N/C Not Connected
5 N/C Not Connected
6 -Rx - Receive Data
7 N/C Not Connected
8 N/C 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.
Figure 2.11 10Base-T Crossover Cable Wiring
Use straight through cable for connecting the Coordinator to an Ethernet hub.
The ports on the hub are already crossed
13
PART 3
OFF
ON
4
3
2
1
OFF
ON
4
3
2
1
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 individual computers or devices to
extract their IP configurations from a server (DHCP server).
If the 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.
14
3.4 DNS
DNS, Domain Name System enables individual computers and devices to be recognized
over a network based on a specific name instead of an IP address.
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 the DHCP and its existing configurations on the host server,
before enabling the 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 Novell networks or Windows 2000 where the DCHP is an updated
function of DNS this feature may be beneficial since a particular name can be
assigned eliminating the need for the IP address.
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.
Your PC’s IP address cannot
be the same as the Coordinator’s IP address.
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.
15
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
Figure 3.2 Network Connections
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.
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
16
PART 4
C:\>ping z03ec
Pinging z03ec with 32 bytes of data:
Reply from z03ec: bytes=32 time=15ms TTL=60
Reply from z03ec: bytes=32 time=8ms TTL=60
Reply from z03ec: bytes=32 time=8ms TTL=60
Reply from z03ec: bytes=32 time=8ms TTL=60
Pinging statistics for z03ec:
Packets: Sent=4, Received=4, Lost=0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum=8ms, Maximum=15ms, Average=9ms
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 Netscape
or 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 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 always set your PC back to its original settings. (See Section 3.5.2
for more details).
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
This proves that the connection is proper and you can get into configuration or run mode
using the Telnet or Web browser.
Figure 4.1 Pinging the Coordinator from MS-DOS Prompt
17
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.
Figure 4.2 Assigning an IP Address using iConnect
1) Place the IP address in this box.
2) Take the MAC address from the label attached to the bottom of the Coordinator and
place it in this box.
3) Click here to send the above IP address to the Coordinator.
4) After the IP address is assigned to the Coordinator, click here to access it’s web
pages.
5) Click here to Ping the Coordinator whose IP address is shown in the IP address
box.
6) Click here to find all the
Coordinator
s on your network .
7) The IP addresses for the Coordinators found by the iConnect will be listed here.
8) These fields indicate the IP address and the subnet mask of the PC on which the
iConnect is running.
18
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
19
4.2 Setting a New IP Address over the Network
ACCESS CONTROL
ACCESS CONTROL
http://192.168.1.200
Address
Main Menu
Login Password 12345678
Admin Password
00000000
IP Address 192.168.1.200
Gateway Address
0.0.0.0
Subnet Mask
255.255.255.0
MAC Address 00:03:34:00:85:C4
Web Server enable
Host Name z85C4
Save Reset
Power Recycle
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.
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 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.
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.
For the IP address to take effect, the Coordinator needs to be turned OFF and ON using
the “Power Recycle” button. Pressing the physical button marked “RESET” on the
Coordinator does the same thing.
Figure 4.4 Access Control
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.
20
4.3 Coordinator’s Configurations and Operations
ADMINISTRATOR
ADMINISTRATOR
LOGIN
LOGIN
http://192.168.1.200 http://192.168.1.200
WIRELESS SENSORS HOME PAGE
Firmware Version x.x
H
OME PAGE
http://192.168.1.200
Address
Readings
Diagnostic
Configuration
Chart
Sensor Setup
Access Control
The Blue LED should blink for ~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.
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.
There are 2 different access levels:
1. ADMINISTRATOR Password
access and modify "entire" parameters without any restrictions.
Figure 4.6 LOGIN and ADMINISTRATOR Passwords
(administrator) allows certain groups and individual users to
The default password is 00000000. This password can be up to 16 alphanumeric case-
sensitive characters.
2. LOGIN Password
except “Access Control” which requires an Administrator password.
The default password is 12345678. This password can be up to 16 alphanumeric
case-sensitive characters.
(operator) allows users to access and modify all of the parameters,
21
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 in roughly 36 hours.
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 retransmits 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.
22
4.3.2 Get Readings from the End Device
READINGS: BY GROUP
READINGS
http://192.168.1.200
Address
Main Menu
Wireless Sensors ID: 0 - 7
Wireless Sensors ID: 8 - 15
Wireless Sensors ID: 16 - 23
Wireless Sensors ID: 24 - 31
Sensor Setup
Group A
Group B
Group C
Group D
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 from the Home Page, the following page will appear. Select the proper
Readings
Group to view the readings.
Figure 4.7 Select Readings by Group
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
23
4.3.2 Get Readings from the End Device (continued)
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 4.3.3.1. If you do not have Java Runtime Environment, you may
download it from our website or contact the Customer Service Department
nearest you.
The”Readings” fields are defined as follows:
Name: Sensor name.
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.
Second Reading Pressure reading or Humidity reading, depending on sensor or the
external sensor reading.
Third Reading Humidity reading, if the End Device is a -BTH version) or the external
sensor reading.
Fourth Reading: The external sensor reading.
Reading “Open” indicates that no sensing device is detected.
Data Logging: Press to activate/deactivate 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 format, which can also be opened in Excel.
Please name file with .csv extension.
ACTIVE data is currently being logged in the specified file.
INACTIVE data logging is not executed.
Update: How often the current applet asks for data from embedded server.
See Section 4.3.4 before activating data logging.
24
4.3.3 Java Runtime Environment Setup
Java (TM) Plug-in Control Panel
AdvancedBasic ProxiesBrowser CertificatesCache About
Update
Enable Caching
Cache Settings
View Clear
Location
Size
Jar Compression
MB
Unlimited
C:\Documents and Settings\AppData\Sun\Java\Deploymentcache\java
None High
Apply Reset Help
Maximum
50
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.
4.3.3.1 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.
Figure 4.9 Java 1.4.2.x Screen Shot
25
4.3.3.2 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.10 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.
26
4.3.3.3 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 Read Sensor 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 a 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 zSeries 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 zSeries 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."
27
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:
grant codeBase “http://192.168.1.200/*”
{
Permission java.security.AllPermission “*”, “*”;
};
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:\\zServer_TEST”. 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.
Figure 4.11 Java Policy
28
4.3.4 Java Policy (continued)
Java Runtime Settings
Control Panel
Java Control Panel
Control Panel
Address
CommentsName
Java Java(TM) Control Panel
General Update Security AdvancedJava
Java Applet Runtime Settings
Runtime settings are used when an applet is executed in the browser.
Java Applet Runtime Settings
Product Name Version Location Java Runtime Parameters
JRE 1.5.0_06 C:\Program Files\java\jre1.5.0_06 -Djava.security.policy=C:\0_JAVAPOLICY\java_policy.txt
OK Cancel
OK Cancel Apply
View...
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:
“-Djava.security.policy=C:\0_JAVAPOLICY\java_policy.txt”
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.
The “Data Logging” and “Save Current Graph” buttons in the “Readings”,
Figure 4.12 Java Policy
“Charts”, and “Diagnostic” pages will not be active if the instructions explained in
the above Section 4.3.4 are not followed.
29
4.3.5 Chart
zSeries
Group A
Main Menu
CHART
(5 Seconds/Div)
1 Minute
1 Minute
1 Day
1 Week
1 Month
1 Year
0
5
C/Div
50
1200
300
100%
0%
10
%/Div
90
hPa/Div
LAB 100 RH LAB100 Pres
C hPa
Tue Jun 5 10:19:10 PDT 2007Tue Jun 5 10:18:10 PDT 2007
http://192.168.1.200
LAB 100 Temp
30 1010
P0 Primary
P1 Primary
P2 LAB 100
P3 Primary
P4 Primary
P5 Primary
P6 Primary
P7 Primary
S0 Secondary
S1 Secondary
S2 LAB 100
S3 Secondary
S4 Secondary
S5 Secondary
S6 Secondary
S7 Secondary
Save Current Graph
CHART: BY GROUP
C
HART
http://192.168.1.200
Address
Main Menu
Wireless Sensors ID: 0 - 7
Wireless Sensors ID: 8 - 15
W
ireless Sensors ID: 16 - 23
Wireless Sensors ID: 24 - 31
Sensor Setup
Group A
Group B
Group C
Group D
Click on , from the Home Page,
Chart
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-100% RH) or within any
narrow range (such as 20 to 30ºC).
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 4.3.3.1). If you do
not have Java Runtime Environment, you may download it from our website or
contact the Customer Service Department nearest you.
Figure 4.13 Select Chart by Group
Figure 4.14 Chart
30
4.3.5 Chart (continued)
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.
Temperature Unit Drop-down List: Temperature unit to be used, either ºC or ºF
Max/Min Humidity: Maximum and minimum humidity of the current graph.
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.
If a sensor is selected (trend line and sensor name turns bold), it’s most current pressure
reading is shown here.
Reading “Open” indicates that no sensing device is detected.
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 once,it turns bold, highlights primary 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.
Chart Area: Display the trend lines of the sensors.
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.
S# button (Secondary): S# shows the sensor name, displays error messages [Lost/ID]
and controls the secondary (external) sensor readings.
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.
Applet Start Date and Time:
X-axis Drop-down List:
Activates when the chart page opens up.
Time scale for the chart.
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.
31
31
4.3.6 Diagnostic
N
ODE-3
S
uccess 10%
Strength 9%
Update 10s
Battery 3.08V
L
ab 100
S
uccess 100%
Strength 79%
Update 10s
Battery 3.21V
L
ab 50
S
uccess 100%
Strength 84%
Update 10s
Battery 3.06V
N
ODE-4
S
uccess 100%
Strength 77%
Update 10s
Battery 3.14V
N
ODE-5
S
uccess 100%
Strength 89%
Update 10s
Battery 2.34V
Click on , the following page will appear.
Diagnostic
Figure 4.15 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 (tree 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.
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.45V; Red: <2.45V
32
4.3.7 Configuration
CONFIGURATION
CONFIGURATION
http://192.168.1.200
Address
Main Menu
Name zSeries
Reset Network
Temperature C Pressure mbar
TCP Connections 1 Port 02000
Save Reset
Channel
Set Radio
11
PID 13111
Version x.x
Transmit Power Range 20dBm
Please refer to local regulation for maximum transmit power range
Click on from the Home Page, the following page will appear.
Configuration
Figure 4.16 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 on the Configuration page.
Reset: This will put the previous values back in the fields ifSave button is not yet clicked.
Version
PID
: Firmware version of the radio module, also shown on model/serial label.
: The Personal Network ID is automatically detected and displayed.
33
4.3.7 Configuration (continued)
SENSOR SETUP: BY GROUP
SENSOR SETUP
http://192.168.1.200
Address
Main Menu
Wireless Sensors ID: 0 - 7
Wireless Sensors ID: 8 - 15
Wireless Sensors ID: 16 - 23
Wireless Sensors ID: 24 - 31
Sensor Setup
Group A
Group B
Group C
Group D
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.
Transmit Power Range: This determines the signal power transmitted by the Receiver.
The options are 10dBm and 20dBm.
Refer to your local regulations for the allowed maximum transmit power.
Reset Network: Power resets the radio module in the Coordinator.
4.3.8 Sensor Setup
Click on from the Home Page, the following page will appear. Select the
proper Group.
Sensor Setup
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.
Figure 4.17 Sensor Setup by Group
34
4.3.8 Sensor Setup (continued)
SENSOR SETUP
Main Menu
Click on Sensor # to modify Sensor Parameters
S
ETUP-
http://192.168.1.200
Update Checked Box
Take Readings
View Charts
Select Another Group
0
1
2
3
4
5
6
7
#
ABCDEFGH
ABCDEFGH
LAB 100
ABCDEFGH
ABCDEFGH
ABCDEFGH
ABCDEFGH
ABCDEFGH
Sensor Name
10
10
10
10
10
10
10
10
Update Seconds
0
0
2.0
0
0
0
0
0
Firmware
-
-
C,mbar
-
-
-
-
-
Units
-
-
Battery
-
-
-
-
-
PowerCheck
#: Sensor ID configured by dip switches on the End Device. Click on the number to view
and modify Sensor Parameters. See Figure 4.9.
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,
Figure 4.18 Sensor Setup
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 form sensors
inside an End Device that has joined the network will be displayed. [ ºC, ºF or % or
mbar, inHg. mmHg ].
Firmware: Version number of the End Device firmware
Update Checked Box: After checking/unchecking the boxes, make sure this is clicked
to save the changes.
35
4.3.8 Sensor Setup (continued)
SENSOR PARAMETERS
Sensor #3, Group A
SENSOR PARAMETERS
http://192.168.1.200
Address
Main Menu
Sensor Name
ABCDEFGI
Select Another Group
Identify: INACTIVE
Reset Sensor
Cancel
U
pdate
10
Update Reset Value
(seconds)
O
ffset1 (xxxx.x)
0
Offset2 (xxxx.x)
0
(% or mbar)
Offset3 (xxxx.x)
0
Offset4 (xxxx.x)
0
(% or mbar)
(
C)
(C)
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.
Sensor Name: Name of this End Device.
Update (seconds): How often this sensor is sending its data to the Coordinator.
Offset: Since the sensing technology in an End Device is solid state electronics, there is
no need for calibration. If it is determined that the readings are slightly off, the user can
manually assign numerical values to adjust the readings for temperature (in degree 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
Figure 4.19 Sensor Parameters
Reset Value: Ignores changes and puts to 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.
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.
36
4.3.9 Access Control
ACCESS CONTROL
ACCESS CONTROL
http://192.168.1.200
Address
Main Menu
Login Password 12345678
Admin Password
00000000
IP Address 192.168.1.200
Gateway Address
0.0.0.0
Subnet Mask
255.255.255.0
MAC Address 00:03:34:00:85:C4
Web Server enable
Host Name z85C4
Save Reset
Power Recycle
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.
Figure 4.20 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.
37
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.
Power Recycle: 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 Power
Recycle button). Pressing the Reset button will set all the fields back to their
default values.
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 get a response back.
4.5 HTTPget Program
The HTTPget software is used to send a single HTTP or TCP request to an 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.
38
4.5 HTTPget Program (continued)
C:\
C:\WINDOWS\system32\cmd.exe
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.135:2000 -C1 -q
where:
-r –S are parameters needed for the the command string
192.168.1.135 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
Figure 4.21 HTTPget Example of Polling End Device #1, 2, 3, 4
39
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-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-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.
40
4.6 ARP Protocol (continued)
C:\>ping 192.168.1.96
Pinging 192.168.1.96 with 32 bytes of data:
Reply from 192.168.1.96=bytes=32 time=5ms TTL=32
Reply from 192.168.1.96=bytes=32 time=3ms TTL=32
Reply from 192.168.1.96=bytes=32 time=3ms TTL=32
Reply from 192.168.1.96=bytes=32 time=4ms TTL=32
C:\>arp -a 192.168.1.96
Interface: 192.168.1.118
Internet Address Physical Addresss Type
192.168.1.96 00-03-34-00-00-23 dynamic
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:\>
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
Figure 4.22 ARP Commands and Responses
41
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.23 iLog Software Logging Data for End Deice #1, 3, 4
42
4.8 Mail Notifier Software
iServer Mail Notifier
Status Indicators
Data Email Error
F
ile Monitor Mail View Help
Alerts List
Connected to Email Complete
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
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.
Figure 4.24 Mail Notifier Main Window
43
4.8.2 Program Options Setup and Configuration
Name/Profile
Password
Email Address MS Outlook Outlook 2002
MAPI
Mail Server
Use Login
Box
Email Setup Content Startup GeneralSend To
Help OK Cancel
Options
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.
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 OutlookTMand OutlookTM2002 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.
Figure 4.25 Mail Notifier Profile Setup
44
4.8.3 Device Setting and Configuration
Make sure that the Coordinator is configured (using web access) 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 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.
Desired Value to Monitor Reading Cmd string Actual Command String
(see Note 2)
Reading A zRdgA ERDB003
Reading B zRdgB ERDB003
Reading C zRdgC ERDB003
Reading D zRdgD ERDB003
Battery voltage (mV) zBatt EQPE003
Signal Level zSignal EQPE003
Sleep Interval zSleep EQPE003
Status (see Note 4) zAddress 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.
45
4.8.3 Device Setting and Configuration (continued)
Alarm Editor
OK
Cancel
Help
Add
Del
Bus Address/Device ID
Socket Number
Description
Src ID
Reading Cmd
Server IP Address
3
2000
Dev1
zRdgA
192.168.1.200
Device Info (1 of 2)
Alarm Type
Alarm High
Alarm Low
Alarm High
73
0
Info Message
Email Interval
Monitor Interval
0.05
Alarm Hold Time 0.0
0.5
hrs.
min.
min.
Alarm Configuration
Only Monitor Access
to iServer device
Figure 4.26 Mail Notifier Device Setting
46
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%.
47
5.1 General Deployment Guidelines (continued)
Coordinator
CONTROL ROOM
PC
MANUFACTURING
AREA
MANUFACTURING
AREA
End Device
OFFICE OFFICE
STORAGE ROOM
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.
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.
Figure 5.1 Operation in Buildings
48
5.2 With Line-of-Sight
FRESNEL ZONE
END DEVICE
ANTENNA
COORDINATOR
ANTENNA
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.
Figure 5.2 Fresnel Zone
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.
49
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 Possible Signal Reduction
Wood, Plaster, Sheetrock, Fiberglass
Uncoated Glass w/out Metal 0 to 10%
Brick, Pressboard 5 to 35%
Reinforced Concrete 10 to 90%
Metal Walls, Metal Doors, Elevators, Metal Piping,
Metal Stair Cases, Metal Mesh, Metal Screening 90 to 100%
Figure 5.3 Materials in Buildings
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.
50
5.5 Fine Adjustment in Performance
US WLAN
(IEEE 802.11B)
non-overlapping
European WLAN
(IEEE 802.11B)
non-overlapping
IEEE 802.15.4
2400 MHz PHY
C
hannel
1116
1137
Channel
Channel
2400 MHz 2483.5 MHz
2412 2437 2462
2400 MHz 2483.5 MHz
2400 MHz 2483.5 MHz
2412 2442 2472
22 MHz
2 MHz
2625242322
2120191817161514131211
2405 2410 2415 2420 2425 2430 2435 2440 2445 2450 2455 2460 2465 2470 2475 2480
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.
2. 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.
3. 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.
4. To achieve satisfactory IEEE 802.15.4 performance in the presence of WLAN
interference, a channel center-frequency offset of 7 MHz is recommended.
5. 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.
6. To achieve satisfactory IEEE 802.15.4 performance in the presence of Bluetooth
interference, a separation distance of 6.5 ‘ (2 m) is recommended.
Figure 5.4 Channels
51
PART 6 SPECIFICATIONS
SENSOR SPECIFICATIONS (zED)
RELATIVE HUMIDITY
Accuracy/Range: zED-BTH, zED-TH, -THP
±2% for 10 to 90%; ±3% for 0 to 10% and 90 to 100%
Hysteresis: ±1% RH
Non-linearity: ±3%
Repeatability: ±0.1%
Resolution: 0.1%
TEMPERATURE
Accuracy/Range*:
zED-T (internal sensor)
±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)
-TP1, -TP2 (external sensor)
±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)
Accuracy/Range*:
zED-BTH, zED-TH (internal sensor)
±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)
-THP (external sensor)
±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 70ºC (±1.8ºF for -0.4º to 32ºF and 113º to 158ºF)
±2ºC for -40º to -18ºC and 70º to 124ºC (±3.6ºF for -40º to -0.4ºF and 158º to 255ºF)
Accuracy/Range*:
zED-BT (internal sensor)
±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)
-BTP (external sensor)
±0.8ºC @ 20ºC (±1.5ºF @ 68ºF)
±2ºC for -40º to 85ºC (±3.6ºF for -40º to 185ºF)
*Note: extended temperature ranges are for External Probes only, the End Device’s operating
temperature is -18 to 55ºC (-0.4 to 131ºF)
Repeatability: ±0.1ºC for zED-BTH, zED-TH, -THP
Resolution: 0.1ºC
BAROMETRIC PRESSURE
Accuracy/Range: zED-BTH, zED-BT, -BTP
±2 mbar for 10 mbar to 1100 mbar (1 KPa to 110 KPa)
Resolution: 0.1 mbar
52
EXTERNAL PROBE SPECIFICATIONS (zED)
Industrial Probe: SS 316 housing, 137mm x Ø16mm
(5” x Ø 0.63”) for zED-xx-BTP, zED-xx-THP
Stick Probe: ABS tubing, 152.4 mm x Ø6.35 mm
(6” x Ø 0.25”) for zED-xx-TP1
Lug Mounted Probe:
Copper tubing, 53.4 mm x Ø 7.92mm (2.1” x Ø 0.312”); mounting hole Ø 4.72mm (Ø 0.186”) for
zED-xx-TP2
Cable: 3 m (10’) long x Ø 5.72 mm (0.225”)
Cable Operating Temperature: -40º to 125ºC (-40º to 257ºF)
INTERFACE SPECIFICATIONS (zCDR)
Ethernet: 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.
POWER (zCDR)
Power Input:
9-12 Vdc
Consumption: 2.5 W max.
Safety Qualified ac Power Adapter (included)
Nominal Output: 9 Vdc @ 0.5 A
Input:
100-240 Vac, 50/60 Hz
POWER (zED)
Alkaline Battery: two 1.5 Vdc, supplied
Lifetime: Estimated 2 years with frequency of 1 reading per 2 minutes
WIRELESS COMMUNICATION
Standard: IEEE 802.15.4
Frequency: 2.4 GHz (2400 - 2483.5 MHz), DSSS, 16 channels
Network Topology: Star Topology
Range: Up to 91 m (300 ft) without obstructions or interference
ENVIRONMENT
Operating Temperature: -18º to 55ºC (-0.4º to 131ºF) 90% RH, non-condensing
Storage Temperature: -40º to 125ºC (-40º to 257ºF)
APPROVALS
FCC: Part 15C.
CE: EMC 2004/108/EC, LVD 2006/95/EC, RTT&E 1999/5/EC. This product is in compliance
with the essential requirements and other relevant provisions of directive EMC 2004/108/EC,
LVD 2006/95/EC, RTT&E 1999/5/EC. 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).
53
PART 7
FACTORY PRESET VALUES
PRESET PARAMETERS FACTORY DEFAULTS
IP Address 192.168.1.200
Gateway Address 0.0.0.0
Subnet Mask 255.255.255.0
Device Host Name z and last 4 digits from the MAC address
Login Password 12345678
Admin Password 00000000
DHCP Disabled
Web Server Enabled
TCP Connections 1
Port # 2000
Channel Auto Detect
PID Unit Address 13106 (0x3332)
Group A
Network ID Address 000
Name zSeries
End Device Name ABCDEFGH
Check Box Checked
Update readings (seconds) 10 seconds
Temperature Unit C
Pressure Unit mbar
DIP Switches:
Coordinator 4 Position all OFF
Coordinator 8 Position all OFF
End Device 8 Position all OFF
54
APPENDIX A GLOSSARY
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.
55
Appendix B IP Address
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.
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
56
Appendix C IP Netmask
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.
Address Class Mask Binary Value Mask Decimal Value
or Dotted Notation
Class A 255.0.0.0
Class B 255.255.0.0
Class C 255.255.255.0
11111111
11111111
11111111
00000000
11111111
11111111
00000000
00000000
11111111
00000000
00000000
00000000
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 Mask Binary Mask Bits
Class A
255.0.0.0 (Default) 0
255.192.0.0 2
255.224.0.0 3
255.240.0.0 4
255.248.0.0 5
255.252.0.0 6
255.254.0.0 7
255.255.0.0 8
255.255.128.0 9
255.255.192.0.0 10
……………......... .
255.255.255.252 22
11111111
11111111
11111111
11111111
11111111
11111111
11111111
11111111
11111111
11111111
. . . . . . . .
11111111
00000000
11000000
11100000
11110000
11111000
11111100
11111110
11111111
11111111
11111111
. . . . . . . .
11111111
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
10000000
11000000
. . . . . . . .
11111111
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
. . . . . . . .
11111100
Class B
255.255.0.0 (Default) 0
255.255.192.0 2
……………......... .
255.255.255.252 14
11111111
11111111
. . . . . . . .
11111111
11111111
11111111
. . . . . . . .
11111111
00000000
11000000
. . . . . . . .
11111111
00000000
00000000
. . . . . . . .
11111100
Class C
255.255.255.0 (Default) 0
255.255.255.192 2
…………………. .
255.255.255.254 6
11111111
11111111
. . . . . . . .
11111111
11111111
11111111
. . . . . . . .
11111111
11111111
11111111
. . . . . . . .
11111111
00000000
11000000
. . . . . . . .
11111100
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.
57
Appendix D ASCII Chart
ASCII Dec Hex Binary ASCII Dec Hex Binary
Char No Parity Char No parity
NUL 00 00 00000000 @ 64 40 01000000
SOH 01 01 00000001 A 65 41 01000000
STX 02 02 00000010 B 66 42 01000010
ETX 03 03 00000011 C 67 43 01000011
EOT 04 04 00000100 D 68 44 01000100
ENQ 05 05 00000101 E 69 45 01000101
ACK 06 06 00000110 F 70 46 01000110
BEL 07 07 00000111 G 71 47 01000111
BS 08 08 00001000 H 72 48 01001000
HT 09 09 00001001 I 73 49 01001001
LF 10 0A 00001010 J 74 4A 01001010
VT 11 0B 00001011 K 75 4B 01001011
FF 12 0C 00001100 L 76 4C 01001100
CR 13 0D 00001101 M 77 4D 01001101
SO 14 0E 00001110 N 78 4E 01001110
SI 15 0F 00001111 O 79 4F 01001111
DLE 16 10 00010000 P 80 50 01010000
DC1 17 11 00010001 Q 81 51 01010001
DC2 18 12 00010010 R 82 52 01010010
DC3 19 13 00010011 S 83 53 01010011
DC4 20 14 00010100 T 84 54 01010100
NAK 21 15 00010101 U 85 55 01010101
SYN 22 16 00010110 V 86 56 01010110
ETB 23 17 00010111 W 87 57 01010111
CAN 24 18 00011000 X 88 58 01011000
EM 25 19 00011001 Y 89 59 01011001
SUB 26 1A 00011010 Z 90 5A 01011010
ESC 27 1B 00011011 [ 91 5B 01011011
FS 28 1C 00011100 \ 92 5C 01011100
GS 29 1D 00011101 ] 93 5D 01011101
RS 30 1E 00011110 ^ 94 5E 01011110
US 31 1F 00011111
SP 32 20 00100000
_
`
95 5F 01011111
96 60 01100000
! 33 21 00100001 a 97 61 01100001
" 34 22 00100010 b 98 62 01100010
# 35 23 00100011 c 99 63 01100011
$ 36 24 00100100 d 100 64 01100100
% 37 25 00100101 e 101 65 01100101
& 38 26 00100110 f 102 66 01100110
‘ 39 27 00100111 g 103 67 01100111
( 40 28 00101000 h 104 68 01101000
) 41 29 00101001 I 105 69 01101001
* 42 2A 00101010 j 106 6A 01101010
+ 43 2B 00101011 k 107 6B 01101011
, 44 2C 00101100 l 108 6C 01101100
- 45 2D 00101101 m 109 6D 01101101
. 46 2E 00101110 n 110 6E 01101110
58
Appendix D ASCII Chart Continuation
/ 47 2F 00101111 o 111 6F 01101111
0 48 30 00110000
1 49 31 00110001
p
q
112 70 01110000
113 71 01110001
2 50 32 00110010 r 114 72 01110010
3 51 33 00110011 s 115 73 01110011
4 52 34 00110100 t 116 74 01110100
5 53 35 00110101 u 117 75 01110101
6 54 36 00110110 v 118 76 01110110
7 55 37 00110111 w 119 77 01110111
8 56 38 00111000 x 120 78 01111000
9 57 39 00111001
y
121 79 01111001
: 58 3A 00111010 z 122 7A 01111010
; 59 3B 00111011
< 60 3C 00111100
= 61 3D 00111101
{
|
}
123 7B 01111011
124 7C 01111100
125 7D 01111101
> 62 3E 00111110 ~ 126 7E 01111110
? 63 3F 00111111 DEL 127 7F 01111111
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
59
Appendix E iLog Error Messages
Error # Description Note
-8003 User stopped logging readings.
-10005 Failed to find the Coordinator. Ethernet cable is disconnected,
Coordinator is powered off,
connections across the firewall
require longer “connection to socket
time out” setting.
-10006 Windows socket was closed.
-10007 Windows socket error. Wrong IP or wrong Port number
was used.
-10008 The Coordinator failed to respond to a request. Wrong IP or wrong Port number
was used.
-10011 Response came empty. No data was sent.
-10012 Device responded with Possibly the iLog is configured for
"Serial Time Out" string. wrong product model.
-10014 Terminal Server Mode when the Port is 1000. Try Port 2000 in iLog configuration.
-15100 Error on obtaining the temperature reading. Possibly the iLog is configured for
wrong product model.
-15105 Error on obtaining the humidity reading. 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.
60
Appendix F 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
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, * internal state and firmware Get name, for sensor
version of an End Device 15 EQNF015
EQNG Group ID00A - 00D, ALL Get name, * internal state and firmware Get name, for all
version of a group/all groups of sensors 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 configur- FACTORY xxxxxxxx
AdminPassword ations to Factory Defaults xxxxxxxx is the Admin
Password
*1 Argument: 1 – 32767 (1 seconds to about 9 hours)
*2 Argument: xxxxxxxx (8 characters)
61
Appendix F TELNET COMMANDS TABLE (continued)
* An example of the internal state 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).
2.0 is version of the firmware in the End Device.
Bit 7 shows if the sensor is plugged into the End Device. ‘1’ means there is no
sensing device detected.
Bit 6 shows if the communication to the End Device is lost. ‘1’ means there has not
been any data received from that particular End Device for 1 minute or 4 times the
update rate, whichever is a longer time interval.
Bit 5 shows if there is more than one End Device having the same dip switch
configuration. ‘1’ means more than 1 End Device has the same Network ID and Device
ID.
Bit 4 shows if there is any pending “identify mode request” command for the End
Device. ‘1’ means a “start” command is issued.
Bit 3 not used
Bit 2 shows if there is any pending “reset” command for the End Device. ‘1’ means a
“reset” command is issued.
Bit 1 shows the source of power supply to the End Device. ‘1’ means it’s powered by
an adapter and ‘0’ means it’s powered by batteries.
Bit 0 shows the operation mode of the End Device. ‘1’ means it is in identification
mode and ‘0’ means it is in normal operation mode.
Based on the above information, End Device # 7 has not been communicating with the
Coordinator and its power is supplied by an adapter.
62
Appendix G Frequently Asked Questions (FAQ)
Q: Update rates are not saved after power cycling Coordinator?
A: In order for the Coordinator to read back and use saved update rates, channel, and
offset values; DIP switch #1 must be turned ON.
The Coordinator will count 5 minutes after the last changes made to update rates,
channel, and offset. Once 5 minutes are passed, data will be saved in flash. If
Coordinator is power cycled during this period of time, changes will not be saved.
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.
63
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.
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: 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.
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.
64
WARRANTY/DISCLAIMER
MEGA ENGINEERING, INC. warrants this unit to be free of defects in materials and workmanship for a period of one (1) year
O
from the date of purchase. In addition to OMEGA’s standard warranty period, OMEGA Engineering will extend the warranty
period for one (1) additional year if the warranty card enclosed with each instrument is returned to OMEGA.
If the unit malfunctions, it must be returned to the factory for evaluation. OMEGA’s Customer Service Department will issue an
Authorized Return (AR) number immediately upon phone or written request. Upon examination by OMEGA, if the unit is found
o be defective, it will be repaired or replaced at no charge. OMEGA’sWARRANTY does not apply to defects resulting from any
t
ction of the purchaser, including but not limited to mishandling, improper interfacing, operation outside of design limits,
a
mproper repair, or unauthorized modification. This WARRANTY is VOID if the unit shows evidence of having been tampered
i
with or shows evidence of having been damaged as a result of excessive corrosion; or current, heat, moisture or vibration;
improper specification; misapplication; misuse or other operating conditions outside of OMEGA’s control. Components which
wear are not warranted, including but not limited to contact points, fuses, and triacs.
OMEGA is pleased to offer suggestions on the use of its various products. However, OMEGA 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 OMEGA, either verbal or written. OMEGA warrants only that the
parts manufactured by it will be as specified and free of defects. OMEGA MAKES NO OTHER WARRANTIES OR
REPRESENTATIONS OF ANY KIND WHATSOEVER, EXPRES S 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 OMEGA 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 OMEGA be liable for consequential, incidental or special damages.
CONDITIONS: Equipment sold by OMEGA 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, used on
humans, or misused in any way, OMEGA assumes no responsibility as set forth in our basic WARRANTY/DISCLAIMER
language, and, additionally, purchaser will indemnify OMEGA and hold OMEGA harmless from any liability or damage
whatsoever arising out of the use of the Product(s) in such a manner.
RETURN REQUESTS/INQUIRIES
Direct all warranty and repair requests/inquiries to the OMEGA Customer Service Department. BEFORE RETURNING
ANY PRODUCT(S) TO OMEGA, PURCHASER MUST OBTAIN AN AUTHORIZED RETURN (AR) NUMBER FROM
OMEGA’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 OMEGA:
1. Purchase Order 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.
OMEGA’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.
© Copyright 2008 OMEGA ENGINEERING, 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 the prior
written consent of OMEGAENGINEERING, INC.
TRADEMARK NOTICE:
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. Other US and International Patents pending or
applied for.
®
, omega.com
®
, , and®are Trademarks of OMEGA ENGINEERING, INC.
FOR NON-WARRANTY REPAIRS,
repair charges. Have the following information available
BEFORE contacting OMEGA:
1. Purchase Order 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.
consult OMEGA for current
Where Do I Find Everything I Need for
Process Measurement and Control?
OMEGA…Of Course!
Shop on line at omega.com
TEMPERATURE
Ther
PRESSURE, STRAIN AND FORCE
FLOW/LEVEL
pH/CONDUCTIVITY
mocouple, RTD & Thermistor Probes, Connectors, Panels & Assemblies
Wire: Thermocouple, RTD & Thermistor
Calibrators & Ice Point References
Recorders, Controllers & Process Monitors
Infrared Pyrometers
Transducers & Strain Gauges
Load Cells & Pressure Gauges
Displacement Transducers
Instrumentation & Accessories
Rotameters, Gas Mass Flowmeters & Flow Computers
Air Velocity Indicators
Turbine/Paddlewheel Systems
Totalizers & Batch Controllers
pH Electrodes, Testers & Accessories
Benchtop/Laboratory Meters
Controllers, Calibrators, Simulators & Pumps
Industrial pH & Conductivity Equipment
M4585/0408
DATA ACQUISITION
Data Acquisition & Engineering Software
Communications-Based Acquisition Systems
Plug-in Cards for Apple, IBM & Compatibles
Datalogging Systems
Recorders, Printers & Plotters
HEATERS
Heating Cable
Cartridge & Strip Heaters
Immersion & Band Heaters
Flexible Heaters
Laboratory Heaters
ENVIRONMENTAL
MONITORING AND CONTROL
Metering & Control Instrumentation
Refractometers
Pumps & Tubing
Air, Soil & Water Monitors
Industrial Water & Wastewater Treatment
pH, Conductivity & Dissolved Oxygen Instruments
Loading...