iQuest iRIS 350FX Basic User's Manual

iRIS 350FX

Basic User Guide

For Software

Version: 1.30

Requires Firmware

Version: Vz/1.40+

iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Disclaimer
Under no circumstances will iQuest (NZ) Ltd be liable or responsible for any consequential damage or loss
that may arise from the use of this product.
All examples and diagrams shown in this manual and any supplied software examples are intended as a
guide to understanding this product, not to guarantee operation. iQuest (NZ) Ltd accepts no responsibility
for use of this product based on this information or these examples. Owing to the wide variety of possible
applications of this product, you must satisfy yourself as to its suitability to your specific application.

© 2014, iQuest (NZ) Ltd

All rights reserved.
This publication, or any part of it, and any software accompanying it may not be copied, photocopied,
reproduced, translated or communicated to any third party, or reduced to electronic medium without prior
written permission from iQuest (NZ) Ltd.

Revision History

Issue 1

Version 1.00

8th Apr 2013

Preliminary release of basic guide.
Adapted from the iRIS 350X Reference Guide V1.70.

Issue 2

Version 1.30

12th Dec 2013

Corrected physical dimensions in specification.
Added section on using Modbus.

iRIS 350FX Reference Manual V1.00

i iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Contents

Contents ........................................................................................................................................ i

2.1 About this Basic User Guide ........................................................................................................... 2

2.2 Support ........................................................................................................................................... 2

3.1 Introduction ................................................................................................................................... 3

3.2 Features ......................................................................................................................................... 3

3.3 Key Features ................................................................................................................................... 4

Terminal Diagnostics ........................................................................................................................ 4

Wireless IP Connectivity ................................................................................................................... 4

Alternative Wireless Connectivity (SMS or FTP) .............................................................................. 4

Power Management ......................................................................................................................... 4

Data Logging ..................................................................................................................................... 5

Logged Data Array Identification ..................................................................................................... 6

Alarm Processing .............................................................................................................................. 6

Real Time Clock & Calendar ............................................................................................................. 7

Security ............................................................................................................................................. 7

Gateway Communication ................................................................................................................. 7

5 Installation ................................................................................................................................. 9

5.1 Opening / Closing the Housing....................................................................................................... 9

5.2 Removing / fitting the SIM card ..................................................................................................... 9

5.3 Terminal Connection .................................................................................................................... 10

5.4 Terminal Security Code ................................................................................................................ 10

5.5 Terminal Menus ........................................................................................................................... 11

Main Menu (Level 1) ...................................................................................................................... 11

Main Menu (Level 1) ...................................................................................................................... 12

6 Operation ................................................................................................................................ 15

6.1 LED Indicators .............................................................................................................................. 15

Status LED ....................................................................................................................................... 15

Diagnostic LEDs .............................................................................................................................. 15

6.2 LCD & Keypad ............................................................................................................................... 15

LCD Operation ................................................................................................................................ 15

Status Icons .................................................................................................................................... 16

Display Menu Structure.................................................................................................................. 17

Keypad Buttons .............................................................................................................................. 18

Primary LCD Display Screens .......................................................................................................... 18

Sensor Related Screens .................................................................................................................. 20

Totaliser Related Screens ............................................................................................................... 22

Comms Related Screens ................................................................................................................. 23

6.3 SMS Communication .................................................................................................................... 26

SMS Text Commands ...................................................................................................................... 26

6.4 General Hints ............................................................................................................................... 27

6.5 RS232 Interface Telemetry / Gateway Comms ............................................................................ 28

Overview ........................................................................................................................................ 28

RS232 Port Telemetry .................................................................................................................... 28

RS232 Only Telemetry Mode ......................................................................................................... 28

iRIS 350FX Reference Manual V1.30

ii iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Non-Dedicated RS232 Telemetry Mode ........................................................................................ 28

6.6 Gateway Communication............................................................................................................. 29

Aliased Gateway explained ............................................................................................................ 30

Gateway Example ........................................................................................................................... 30

7 Using Modbus Slave Mode ....................................................................................................... 31

Configuring iRIS 350FX to use Modbus ......................................................................................... 31

Enabling RS232 Modbus Operation using Keypad/LCD ................................................................. 33

7 Troubleshooting ....................................................................................................................... 34

7.1 Can’t connect to the iRIS via the RS232 port. .............................................................................. 34

7.2 iRIS will not start when the battery is first connected. ................................................................ 34

7.3 Pulse lost when iRIS connected to other equipment. .................................................................. 34

7.4 Unable to connect to an IP network. ........................................................................................... 34

7.5 iRIS will not respond to SMS requests. ........................................................................................ 34

7.6 iRIS 350FXV answers a voice call, but no sound is heard. ............................................................ 35

7.8 Unable to access terminal menu. ................................................................................................ 35

7.9 Digital Output activates when user is logged on. ........................................................................ 35

7.10 SDI-12 sensors log a “NaN” value. ............................................................................................. 35

7.11 Sensor values not included in SMS reply to “RQ”. ..................................................................... 35

7.12 External 12V battery not charging as expected. ........................................................................ 35

8 Appendix A – Specific Information ............................................................................................ 36

8.1 General Characteristics ................................................................................................................ 36

8.2 Technical Specifications ............................................................................................................... 37

8.3 Mounting ...................................................................................................................................... 38

8 User Notes ............................................................................................................................... 39

Tables / Figures

Table 1 - Feature Summary ............................................................................................................................... 3

Table 2 - iRIS 350X / iRIS 350FX Differences ...................................................................................................... 8

Table 3 - Status LED Indication Modes ............................................................................................................ 15

Table 4 – RS232 Port Telemetry Control ......................................................................................................... 28

Table 5 – RS232 Telemetry Mode Indications ................................................................................................. 28

Figure 1 - SIM Carrier ......................................................................................................................................... 9

Figure 2 - RS232 Cable Pin Designations ......................................................................................................... 10

Figure 3 - Terminal Menu Structure ................................................................................................................ 11

Figure 4 - Typical RS232 / Data Radio Cable .................................................................................................... 29

Figure 5 - iRIS 350FX External View ................................................................................................................. 36

Figure 6 - Mounting Diagram........................................................................................................................... 38

1 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

1 Declaration of Conformity

We, iQuest(NZ) Ltd
of Waikato Innovation Park

Ruakura Road, Hamilton 3214
New Zealand
Ph: [phone]
Fax: [phone]

in accordance with the following Directives:

2004/108/EC The Electromagnetic Compatibility Directive

Standards met:

BS EN 55022:2010: Incorporating Corrigendum No. 1 and Amendments Nos. 1 & 2

Information Technology Equipment –
Radio Disturbance Characteristics –
Limits and Methods of Measurement

BS EN 55024:2010: Incorporating Amendments Nos. 1 & 2

Information Technology Equipment –
Immunity Characteristics –
Limits and Methods of Measurement

FCC Code of Federal Regulations 47: Telecommunication

Part 15 – Radio Frequency Devices

Subpart A – General
Subpart B – Unintentional Radiators

I hereby declare that the equipment named above has been designed to comply with the relevant sections of
the above referenced standards and all products supplied under this Declaration will be identical to the
sample tested.

Signed:

Name: David Richards
Position: Managing Director
Place: Hamilton

Date: 20/09/2012

iRIS 350FX Reference Manual V1.30

2 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

2 Introduction

2.1 About this Basic User Guide

This guide is intended to assist with the operation of the iRIS 350FX datalogger.

It should be read in conjunction with the detailed Reference Guide for the preceding iRIS 350X datalogger
and the integrated help file included with the iLink 2012 support application.

This guide is available on-line in Adobe Acrobat® PDF format for registered users at: www.iquest.co.nz
Throughout this document, small icons are used to identify additional information. These are as follows:

NOTE Indicates extra detail to expand the current discussion.

WARNING Describes something that may cause problems if not heeded.

The term “iRIS” is generally used throughout this manual in reference to the iRIS 350FX
datalogger.

2.2 Support

Technical support for the iRIS 350FX datalogger is available by contacting:
iQuest (NZ) Ltd
PO Box 15169
Dinsdale
Hamilton 3243
NEW ZEALAND

Tel: [phone]
Fax: [phone]
Email: [e-mail]

For latest information and software updates, visit the iQuest (NZ) Ltd web site at: www.iquest.co.nz.

3 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

3 Overview

3.1 Introduction

The iRIS 350FX (iQuest Remote Information Source) datalogger range has been designed as cost effective,
low power, self-contained information source for use in a wide range of data gathering and logging
applications.

The iRIS achieves network connectivity through the use of an integral wireless modem. Depending on the
version and target market, this modem will be one of the following:

 Multi-band 900/1800/1900 MHz Wavecom 2406 or Q24+ GSM/GPRS in older iRIS 350 hardware.
 Multi-band 3G HSDPA/WCDMA (for example Telecom XT® in New Zealand and Telstra NextG® in

Australia). This may be either a Maxon 6280E module in older iRIS 350 hardware or a Sierra
Wireless Q26 Extreme module in current production units.

3.2 Features

Wireless IP Mode

SMS Mode

CSD Mode

Voice Annunciation Support

IRIS-CAM Camera Support

Digital inputs (pulse).

Analogue Inputs (0-5V or 0-20mA)

Digital Control Outputs (shared with inputs)

SDI-12 Interface

RS-232 Interface

Number of Simultaneous Logging Channels

Internal Temperature Logging

Internal Battery Logging

Supply Voltage Logging

Alarms . Can be assigned to any sensor.
Rated at IP65 or better

Heavy Duty Aluminium Case

Internal 3.6V Lithium Backup Battery

Internal 12V Rechargeable Battery

Internal Battery Charger

Direct Solar Panel Connection

External RF Antenna Connector (SMA)

Keypad / LCD

iRIS 350FX





 4 4 4





20

  

40

      



iRIS 350FXV

   4 4 4   20    40        

Table 1 - Feature Summary

iRIS 350FX Reference Manual V1.30

4 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

3.3 Key Features

Terminal Diagnostics

A small number of diagnostic and initialisation options are available via a standard ASCII terminal
connected to the RS232 serial interface. In previous models (350 / 350X) nearly all the configuration was
also done using the terminal. This has been removed because of the increased features of the FX and data
unloading is done using the iQuest logger support application, iLink 2012.
Refer to Section 5.5 for details on the terminal options.

Wireless IP Connectivity

Wireless Internet Protocol connectivity is provided via the on-board modem. Through this interface it is
possible to perform configuration changes and retrieve logged data using HydroTel™ or iLink 2012
software. To facilitate IP connectivity, a suitably activated SIM card must be inserted in the device. It is
also necessary to program the unit with appropriate IP connection settings through a terminal connected to
the RS232 serial interface. The iRIS communicates using IP over a wireless network using either UDP or
TCP protocol.

Alternative Wireless Connectivity (SMS or FTP)

Another wireless connection mode other than IP is also possible on all hardware variants. This is SMS (Short
Message Service). As with the IP mode described above in Section 0, using the SMS service requires a SIM
card with the SMS service enabled by the service provider.

The SMS option works by sending a pre-set text message to up to ten destination cell phones or SMS
receivers. This message contains the iRIS site identification and the current values of all enabled sensors.
See Section 6.3 SMS Communication for more information on using the SMS feature.

Irrespective of the modem call-back mode setting (IP or SMS), the iRIS will only respond to
incoming SMS requests when it is not connected in IP mode. The modem call-back mode setting

only changes the service that is used to notify an alarm or generate a communications test. In
this case, the selected service and destination phone numbers are used to send a text message
(SMS).

Finally, FTP file transfer is provided for installations requiring a stand-alone data uploads. This option is
only available for units equipped with the Sierra Wireless Q26 modem.

Power Management

The iRIS supports four power management modes which are described below. Power management
features that operate in all modes include:

 Deactivation of RS232 driver chip when the DSR signal is not present (unless the unit is active in

RS232 telemetry mode).

 Turning off the backlight after a period of inactivity when no user is logged-in.
 Ability to activate an IP session at scheduled times of day for pre-set period even if the modem is

otherwise disabled in full power save mode.

5 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

No Power Save

With power management disabled, the internal wireless modem is maintained in a powered on state
even if an IP session is not currently active. While in this state, periodic signal strength measurements are
made and it is possible to interrogate the internal modem using the AT command set via a terminal
connected to the serial interface. All on-board communication, I/O and all status LED’s are permanently
enabled in this mode.

Partial Power Save

With the power management mode set to Partial Save, the on-board LEDs are disabled but the internal
wireless modem remains in the same fully active state as in the No Power Save mode.

Full Power Save

When power management is set to full save mode, the internal LEDs are disabled and the internal wireless
modem remains in a powered off state until a wireless session is activated by the scheduler, a user or an
alarm (if this feature is enabled).

While the modem is in this state, it is not possible to obtain signal strength measurements or
interrogate the modem via the AT command set using the Modem Terminal mode as the
modem is shut down.

RS232 Only

This mode is provided for applications where the internal modem is not used and telemetry is achieved by
a data radio or modem connected to the RS232 port. When in this mode, the RS232 port is used for all
call-back communication. The RS232 port behaviour also changes depending on whether the iRIS is in
“Normal” or “Telemetry” mode. See Section 0 6.5 RS232 Interface Telemetry for further details on RS232
telemetry communications.

Data Logging

The iRIS supports the logging of data from up to twenty virtual sensors. Each of the virtual sensors can
obtain information from one of the following data sources:

 Analogue input on AIN1 – AIN4
 Pulse counter attached to DIO1 - DIO4
 Simulated pulse counter enabled by DIO1 - DIO4
 Frequency counter attached to DIO1 or DIO2
 Up/down counter attached to DIO1 and DIO2 simultaneously
 Internal database location (for values obtained via user script or communications link)
 SDI-12 instrument channel
 Quadrature shaft encoder attached to DIO3 and DIO4 simultaneously
 Change of status on charger input (dc supply)
 Battery voltage
 Supply (charger) voltage
 Logger temperature
 Received Signal Strength Indication (RSSI)
 Derived via a lookup table (e.g. flow rate) sourced from sensor 1's measured value.
 Change Of State on digital I/O channels DIO1 - DIO4

iRIS 350FX Reference Manual V1.30

6 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Each sensor can be set up to scale the raw data source into engineering units through the application of a
multiplier and offset (slope and constant). The scaled value can be logged to non-volatile memory at rates
between once per minute to once per hour or immediately in true event mode for pulse inputs.

It is also possible to configure a sensor to also log associated values such as minimum, maximum, standard
deviation (for all source types) or a calculated flow rate or volume (pulse type sources only). See the next
section for further details on configuring these extended logging features as part of the Sensor Cfg menus.

Logged Data Array Identification

Each sensor’s logged data is identified by an array ID number. For the primary logged data, the ID is the

sensor number itself. For the optional supplementary data (min, max, deviation, flow/vol), the array ID has
an offset added to the sensor number that it is associated with. These ID offsets are as follows:

Minimum: +20
Maximum: +40
Deviation: +60
Flow/Volume +80
Check Count +100

For example, Sensor 4 has been configured to log the average value, plus the maximum and standard
deviation. Three data arrays will be logged for this sensor at each logging interval with IDs of 4, 44 and 64
respectively. In HydroTel™ these require point identifiers of 4, 44 and 64 respectively.

Array 0 (zero) is a special array identifier and is used as a system event log. Currently this is only
used to log a restart (either at the initial connection of power, on a watchdog reset or a user
program start after an upgrade). The logged value in this case contains a value that can be
decoded to determine the cause of the restart. In HydroTel the identifier for this item is 0.

Alarm Processing

There is a “pool” of up to 40 free-format alarms. These can be assigned to any virtual sensor. So it is
possible to have up to two alarms on every sensor or else more on some sensors and less or none on
others. Each alarm has separate trigger and reset levels, and also an activation delay or accumulation
period depending upon the data type.

Each sensor has an associated flag that is set if any alarm on the sensor is active. This can be used to vary
the logging rate for the sensor. For example taking more frequent logs when water level is high compared
to a less frequent “routine” log in normal conditions.

The iRIS also maintains a global “alarms active” flag that is set if any alarm on any sensor in the device is
active. This is used to trigger a call-in or data transfer to the designated host. As well as the call-in, this flag
can also control the digital outputs or trigger a camera image for the iRIS-CAM variant.

7 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Real Time Clock & Calendar

The iRIS has a non-volatile real time clock that can be read and/or synchronised using HydroTel™ or iLink

2012.

The iRIS 350FX differs from its predecessors in that the internal clock runs in UTC (GMT) and all
logged data is time/date stamped in this time zone. HydroTel™ and/or iLink 2012 automatically
adjust for this. The configured UTC offset is only used to adjust the date/times on the LCD (as
viewed by users) to the local standard time zone.

Security

The iRIS can be configured with a PIN code to prevent unauthorised access to restricted information
through the LCD and keypad. This is especially useful when the iRIS is installed in a location where it is
accessible to the general public.

A second level of security is also provided to prevent access to the terminal via a serial connection. This is
achieved by a security string that if used requires correct entry before access to the terminal is granted.
This is typically to protect the totalisers and logged data from being cleared.
See Section 0 for more details on using the security string.

Gateway Communication

The iRIS supports iQuest protocol gateway functionality between the wireless network and the RS232 serial
interface. This enables the unit to be used as a bridge between the wide area wireless network and a
localised radio or other network. It is possible to connect a datalogger that does not have wireless
capability such as the iQuest DS-4483 to the serial port of the iRIS and communicate with it via the

gateway. Also, by connecting a data radio to the unit’s serial port it is possible to communicate with

several devices in a multi-drop radio network from the wireless network.

When the gateway option is enabled, any data packets that are not addressed to the iRIS and match the
gateway criteria are readdressed and redirected. The port that the redirected packet is sent from depends
on the configuration of the iRIS.

Refer to Section 6.5 RS232 Interface Telemetry for further information on using the gateway.

iRIS 350FX Reference Manual V1.30

8 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

4 iRIS 350X and iRIS 350FX Comparison

The iRIS 350FX is an enhanced firmware/software set that can be applied to any existing iRIS 350 or iRIS
350X datalogger. Primarily this update changes the fundamental datalogging format to floating-point and
is built around a new IEEE-745 2008 compliant library.

Aside from this many other functions have been reviewed and improved. The FX variant will become the
only firmware/software developed and supported in the future for the iRIS 350 hardware.

Because the changes are very significant, the upgraded iRIS 350 / 350X personality is a different model.

Key differences between iRIS 350X and iRIS 350FX

• Standard IEEE-754-2008 compliant Floating Point library.

• Datalogging sample values are floating-point. Logging multiplier removed.

• All timestamping is in UTC to enhance use internationally.

• Configuration via text terminal removed and only basic terminal diagnostics supported.

• SDI-12 firmware engine re-engineered and now fully compliant (retries etc).

• Supports a custom SDI-12 command with a separate schedule from measurements

• Default RS232 port speed increased from 38,400 to 115,200bps.

• Sensor logging rate can be different when alarm(s) on that sensors are active.

• All schedules have separate on/off/alarm intervals.

• Totalisers: YTD (Year To Date) and Last Year. Settable roll-over time (daily) or date (yearly).

• Capable of native FTP file transfer (CSV format) to one or two destinations.

(Requires Sierra Wireless Q26 modem)

• Analogue input ranges are now settable. Nine ranges provided between 0-80mV and 0-5V.

• Optional linearisation provided using a custom polynominal.

• Sensor display format is settable (number of decimal places).

• Support for up to two look-up tables for ratings / conversions.

Supports ad-hoc connection to IP host via extended SMS command (GOL )

• Multi-language support for internal date/times etc. Five supported (EN, DE, FR, ES, PT)

• Secure and reliable OTA (Over The Air) firmware and software upgrades now possible.

Table 2 - iRIS 350X / iRIS 350FX Differences

9 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

5 Installation

5.1 Opening / Closing the Housing

The front of the iRIS enclosure is secured by four M4 machine screws with Phillips® heads.

There are two small plastic hinges on the case. These are designed to hold the lid once it is
released.

To Open: Lift off the two grey plastic side covers to expose the screws securing the cover. Put them
in a safe place. Undo all four screws. There is no need to remove them completely as they are retained in
the lid. The front cover should then be able to be swung open, to a maximum angle of 90.
To Close: Check that the black sealing strip is fully installed in its retaining groove and there are no
wires likely to be trapped under the cover. Gently swing the front cover closed, holding it straight while
refitting the screws. Tighten screws securely to maintain the IP66 rating of the enclosure. Replace the grey
plastic side covers. Finally ensure the black rubber sealing cap is refitted to protect the RS232 connector.

5.2 Removing / fitting the SIM card

Important! Ensure the iRIS is depowered before attempting to remove or fit the SIM card. Exercise
care when inserting or removing the SIM card, as the carrier is fragile.

Open the front cover as described above.
Using a finger nail or small screwdriver inserted into one of the two oval holes on the sliding holder, gently
lower the slide downwards to unlock it. The slide can now be swung forwards from its top end to enable
the SIM card to be inserted or removed. Reverse the procedure to close and lock the card into place.

Figure 1 - SIM Carrier

Finger nail or
tool access

Unlock

SIM

iRIS 350FX Reference Manual V1.30

10 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

5.3 Terminal Connection

The iRIS RS232 port is a DTE (Data Terminal Equipment) configured port and is identical in pin-out and
signal allocation to that of an IBM compatible PC’s RS232 port. Therefore the cable required is the same as
that for computer-to-computer communication and is termed a null-modem cable. These are available
from most electronics retailers if required.
To access the iRIS diagnostic terminal a full null-modem cable (wired as shown below) between a
communication port (e.g. COM1) on your computer and the RS232 port of the iRIS. The null modem cable
configuration has the three main signal pairs crossed over. These pairs are TXD/RXD, RTS/CTS and DTR/DSR.
The signal ground (SG) line is connected straight through. The CD and RI lines are unused.
The iRIS RS232 serial port is set by default to a speed of 115200bps, 8 data bits, 1 stop bit and no parity.
Flow control is not required.

Computer iRIS

DB9F DB9F

1 CD CD 1
2 RXD TXD 3
3 TXD RXD 2
4 DTR DSR 6
5 SG SG 5
6 DSR DTR 4
7 RTS CTS 8
8 CTS RTS 7
9 RI RI 9

Figure 2 - RS232 Cable Pin Designations

5.4 Terminal Security Code

The iRIS supports the use of a text-based security code (of up to 10 characters) that may be used to prevent
unauthorised access to the terminal menus.

If used, the code is set using iLink that is registered to “Administrator” level. If it is empty, the terminal is

immediately available as soon as the RS232 connection is made. If the code has been set, then a prompt
message is shown and the code must be entered before the terminal becomes available.

The security code is case-sensitive. The code cannot be viewed or changed except by an authorised
user using iLink which is registered to Administrator level.

> Enter Security Code (max 10)=

11 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

5.5 Terminal Menus

Main Menu (Level 1)

Throughout all the terminal menus, there are two common entry codes.

 Menu option 0 (zero) always returns you to the level above your current position.
 Entering “r” or “R” when in a menu being prompted for an option will refresh the menu without

selecting anything.

When a terminal session has been established with the iRIS through the RS232 port you will be presented
with the main menu. To make a menu selection, type a number followed by <Enter>. Invalid menu
selections will result in the display of an error message on the terminal. The current value of each settable
item is enclosed in square braces e.g. [1234].

Level1 Level2 Level3 Level4 Level5

Main Menu
Totals
Totaliser 1
Totaliser 2
Totaliser 3
Totaliser 4

Modem Diagnostics
Modem Terminal
SDI-12 Terminal

Initialise

Figure 3 - Terminal Menu Structure

iRIS 350FX Reference Manual V1.30

12 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Main Menu (Level 1)

The first menu displayed is the Main Menu. From here, you can make the following choices:

iRIS 350FX Cellular(W)
AG4-1234, F1.0, S1.0, O1.10
My Site Name

1 Totals
2 Modem Diagnostics
3 Modem Terminal
4 SDI-12 Terminal
5 Miscellaneous
>

Option 1 – Totalisers

This menu option provides access to the four totalisers which are associated with each of the digital I/O
channels. A sub menu displays the current totals and also provides a means of either resetting all totals for
the channel or setting the running total to match a flow meter.

1* Totaliser Selection

0 Exit
1 Totaliser 1
2 Totaliser 2
3 Totaliser 3
4 Totaliser 4
>

* Totaliser 1 Cfg
Last Year: 3457765.0
Year To Date: 96339.0
Yesterday: 1337.2
Today: 149.7
Running: 158823.0

0 Exit
1 Reset All Totals
2 Edit Running Total
>

Option 1 reset ALL totals for this channel . It will need to be done for each channel separately.

Option 2 is only possible if the totals have been cleared and is intended only as an initialization task when
the logger is first commissioned.

13 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Option 2 - Modem Diagnostics

Select this option to display the current modem identification parameters, status and signal strength. After
listing the status information, this option then provides a running diagnostic log of communication with the
wireless modem. Please see the next section for more details on the diagnostics that are available in this
menu option.

Modem Diagnostics

Example Status Information:

Modem Diagnostics. Enter 0 to exit

Modem: Sierra Wireless (W)
Version: R7.44.0.201007221223.Q26EX001 1608904 072210 12:23
IMEI: 351919030231951
IMSI: 530011102111028
LIP: 10.236.7.252
RSSI: -83 dBm BER: 0
Status: Connected
>
09:13:00 STATE: Connected PM1 SR0 LC1 LS1 PB CT60 CW179 LT60

IMEI: International Mobile Equipment Identifier. This is stored in the wireless module at the factory and

uniquely identifies the hardware by manufacturer and serial number.

IMSI: International Mobile Subscriber Information. This is obtained from the SIM card
LIP: The last local IP address that was allocated to the iRIS when it was last online.
RSSI: This displays the Received Signal Strength Indication in units of dBm. This is useful for determining

the strength of the signal. A value of 0 indicates that the RSSI value is not available.

The iRIS will not attempt to connect to the network if the RSSI is 0 or less than -113dBm.

Example diagnostic information. This will differ between units with either the earlier (Maxon
module) or the later (Wavecom or Sierra Wireless modules).

The < character indicates data received from the modem and the > character indicates data sent

to the modem.
The current communication state is shown with a preceding STATE: message that includes several
additional diagnostic e.g. PM1 SR0 TC0 TE0 TM0 LC0 LS0 PB CT3600. These are:

- PM Actual Power Management level being used. 0=No Save, 1=Partial Save, 2 = Full Save.

- SR Sync Request. (0 = clock in sync, 1=need clock sync from network)

- LC Link Control. Requested link control (to the modem module). (Wavecom only).

- LS Link State. Actual link state (from modem module). (Wavecom only).

- PB Current base (host) that is (or will be) connected. PB=Primary, SB=Secondary.

- CT Connection Timer. Connection time remaining. Set to duration when not connected.

- CW Connection Watchdog. Time before a hard reset of the modem is done. Is 3 times the

comms schedule interval. E.g. interval = 60 mins invokes reset if no connection in 3 hrs.

- LT TCP Server Listening Time (TCP mode only).

iRIS 350FX Reference Manual V1.30

14 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Option 3 - Modem Terminal

By using this terminal mode, it is possible to perform two distinct functions depending on the state of the
internal modem. If the terminal is available, this message is displayed.

> Terminal Mode active. Press <ESC> and then <Enter> to exit.

If the internal modem is powered down, the terminal mode is unavailable and this message will appear:

> Wireless module inactive. Terminal unavailable.

Assuming the modem is active, the two scenarios are as follows:

 If the internal modem is powered up, but an IP session is not in progress, then it is possible to

interact with the modem using the standard AT command set.

 If the internal modem is powered up and an IP session is currently in progress, then it is possible to

interact with a terminal at the remote end of the connection.

When using transparent terminal mode you must press the <Enter> key after each command or message
you wish to send. Press <ESC> followed by <Enter> to exit the modem terminal session and return to the
communication menu.

Option 4 - SDI-12 Terminal

The SDI-12 terminal mode allows direct access to instruments connected to the SDI-12 interface. This is
useful when a manual check or changes need to be made, such as address changes, scale factors etc.
Knowledge of SDI-12 commands is required to make use of this feature.

> SDI-12 Terminal mode active. Press <ESC Enter> to exit

Option 5 – Initialise

This option is used to initialise the unit. This is generally done just after installation as part of the
commissioning process to eliminate any test or residual data or totals. It resets the memory pointers to
zero and also resets all totalisers. To ensure this task is not accidentally invoked, a specific string must be
typed in order to execute the initialisation process.

> Type 'init' to initialise the unit

15 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

6 Operation

6.1 LED Indicators

The iRIS has several LED indicators. The main status LED and eight diagnostic LEDs are visible from the front
of the enclosure.

Status LED

The status LED is a tri-colour device that is used to indicate the unit status.

Status

LED Indication

Idle, low or no signal strength

Flashes red once every three seconds

Idle, adequate signal strength

Flashes green once every three seconds

Connecting to network

Flashes blue every half a second

Connected to network

Flashes blue once every three seconds

Failed to connect

Flashes red every half a second

Table 3 - Status LED Indication Modes

Diagnostic LEDs

The iRIS has eight LED indicators that are useful for diagnostic purposes. These are visible through the
front of the enclosure.

With the exception of the SDI-12 TX LED, these indicators are only active when the power

management mode is set to No Power Save (see the Features Section 0 for details on power
management).

DIO1 Illuminated red when Digital I/O #1 is active.
DIO2 Illuminated red when Digital I/O #2 is active.
DIO3 Illuminated red when Digital I/O #3 is active.
DIO4 Illuminated red when Digital I/O #4 is active.
RS232 RX Flashes green when data is received from the RS232 port.
RS232 TX Flashes green when data is transmitted out the RS232 port.
Modem Flashes green when there is receive or transmit activity to/from the modem.
SDI-12 Flashes green when an SDI-12 message is transmitted or received.

6.2 LCD & Keypad

LCD Operation

The iRIS LCD is controlled to optimise power consumption. If the display has powered down (in full power
save mode), the unit is in the lowest power mode and can be woken by pressing any key on the keypad.
After a certain period of no key presses, the display and backlight will power down again, although other
functions continue normally. If the user was logged on (PIN entered), they will be logged off. This version
of software has the timeout period set to 5 minutes.

iRIS 350FX Reference Manual V1.30

16 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Status Icons

At the top of the LCD is a row of status icons.

Indicates current connection state as given below:

 Invisible Modem shut down.
 Outline Disconnected in wireless mode
 Solid Connected in wireless mode
 Solid with ‘R’ Connected in RS232 only mode
 Double triangle Listening in TCP server mode

Indicates active RS232 or IP terminal connection.

 Invisible No terminal connected
 Outline Terminal connected

Indicates transparent (modem or SDI-12) terminal mode is active

 Invisible no transparency
 Solid transparent terminal active

Indicates signal strength.
Only updated when wireless modem is powered up but
wireless IP session is not active.

Flashes when an unsolicited call-in is pending or in progress. This
can be the result of an alarm activation or a user request for a test
call-in.

Indicates current battery charge. The level indication
bars cycle when charging is in progress.

If the supply voltage input is 15V or greater, the battery
icon is replaced with wither a power plug icon when the
source is set to external DC). Or if the charge source is
set to solar, a sun icon is displayed.

Indicates current access level

 Invisible logged in
 Outline logged out
 Solid secure (PIN is set to zero)

These three icons are specific to the Modbus feature or
the camera and voice versions respectively.
They will appear if Modbus mode is active or a picture is
being taken or a voice call is in progress.

17 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Display Menu Structure

The actual LCD screens that are available will depend upon the level of access that has been enabled (no
access, not logged-in, or logged-in). The screens available in each mode are shown below:

1. Minimum Access (PIN code = 0, Log-in is not possible)

Level 0 Level 1 Level 2 Level 3 Level 4 Level 5 Level6

Status 1
Status 2
Status 3
Status 4 Totalisers [1..4]

2. View Only Access (PIN code <> 0, but user is not logged-in)

Level 0 Level 1 Level 2 Level 3 Level 4 Level 5 Level6

Log-In

Status 1
Status 2
Status 3
Status 4 Main Menu

Sensors [1..20]

Sensor Menu

Sensor Data

Totalisers [1..4]

Comms Status

3. Full Access (PIN code <> 0 and user is logged-in)

Level 0 Level 1 Level 2 Level 3 Level 4 Level 5 Level6

Log-Out

Status 1
Status 2
Status 3
Status 4
Log Control Main Menu

Sensors [1..20]
Sensor Menu
Sensor Settings [1..5]

Sensor Calibration
Sensor Data

Totalisers [1..4]

Totalisers Reset

Comms Status

Comms Menu
Comms Settings [1..9]
RS232 Cfg
Comms Test

iRIS 350FX Reference Manual V1.30

18 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Keypad Buttons

The four keypad buttons are used to navigate through the LCD screens. Their use varies depending upon
the current screen in view; however the key combinations listed below are constant for all screens.

To move down a level in the menu structure, press the <Enter> key. To move up a level press the <Alt> and
<Enter> keys simultaneously. You can scroll through the screens that are followed by a number in square
brackets (e.g. [1..4]) by pressing the + or - keys (stepping forwards and backwards respectively).

Primary LCD Display Screens

Log In Screen (Level 0, when not logged in)

The Log-In screen is a special screen that is allocated level 0. It is used to enter a PIN number and then
enable access to restricted screens. It is reached by pressing the Alt and Enter keys simultaneously from
any of the four System Status screens when the unit is not logged in.

Once the PIN number matches that programmed into the device and the <Enter> key is pressed, the user
will be logged in and returned to the top-level Welcome (System Status 1) screen. A successful login will
also remove the padlock icon from the top of the display.

System Status 1 Screen (Level 1)

The System Status 1 screen is the default screen shown at system power up, hence its designation as
display level 1. Useful information shown on this screen includes the site name, model, serial number,
iQuest protocol communications address and the current time and date.

System Status 2 Screen (Level 1)

The System Status 2 screen is always available, no matter what level of access has been selected. The
information shown on this screen includes the firmware (F) and software (S) version numbers,
communications module and if applicable, the scripted variant.

My Site Name
iRIS 350FX AG4-1234
Address: 1
14:39:23 07 Oct 13

- Unused
+ Move across to System Status 2 screen
Enter Move down to main menu screen
Alt Enter Log in (If PIN code <> 0), otherwise unused

LOG IN
Pin No. 0000

+/- Increment/decrement PIN number
Enter Multiply PIN number by 10 or accept

PIN number as displayed. Moves back
to System Status 1 screen

Firmware: 1.40
Software: 1.30
Comms: Sierra Q26
Modbus (RTU 9600)

- Move back to System Status 1 screen
+ Move forward to System Status 3 screen
Enter Move down to Main Menu screen
Alt Enter Log in (If PIN code <> 0), otherwise unused

19 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

System Status 3 Screen (Level 1)

The System Status 3 screen is always available, no matter what level of access has been selected. The
information shown on this screen includes the internal battery voltage, supply voltage, internal
temperature and if applicable the RSSI (signal strength).

System Status 4 Screen (Level 1)

The System Status 3 screen is always available, no matter what level of access has been selected. The
information shown on this screen includes the voltage being measured at the AI1 – AI4 terminals in volts.
These values are useful for checking input signals and also for the calibration process.

System Status 5 Screen (Level 1)

The System Status 5 screen is also always available, no matter what level of access has been selected. The
information shown on this screen includes the current status of the digital channels whether they are an
input (DIx:y) or an output (DOx:y) (where x is the channel and y is the state 0=OFF, 1=ON). This screen also
shows the current alarms status (A) which is 1 if any alarms are active and also the currently selected
communications scheduler interval in minutes. Finally is displays the Start Of Data (SOD) and End Of Data
(EOD) pointer values.

Logging Control Screen (only accessible when logged in)

The Logging Control screen is a special screen that is only available on level 1 when a user is logged in. It
can be used to temporarily disable logging when the logged in user is making changes to or testing sensors
and does not want to have the data logged. It is reached by pressing the + key from Status Screen 4. Use
the Enter key to toggle logging on or off. If the logging is disabled, it is always re-enabled automatically
when the user logs out, either manually or on an inactivity timeout (30 minutes).

Use the – or + keys to switch the logging on or off. Pressing the <Enter> key will return the display to the
top-level Welcome (System Status 1) screen.

Battery: 12.57 V
Supply: 23.78 V

Temp: 21.6 C

RSSI: -75 dBm

- Move back to System Status 2 screen
+ Move forward to System Status 4 screen otherwise unused.
Enter Move down to Main Menu screen
Alt Enter Log in (If PIN code <> 0), otherwise unused

DI1:0 DI2:1 A: 0
DI3:0 DO4:0 I: 360
SOD Ptr: 177104
EOD Ptr: 177336

- Move back to System Status 3 screen
+ Move to Logging Control screen if logged in. Otherwise unused.
Enter Move down to Main Menu screen
Alt Enter Log in (If PIN code <> 0), otherwise unused

LOGGING CONTROL
Use Enter key to
Enable/disable.
=> Enabled

- Move back to System Status 4 screen
+ Unused
Enter Toggle logging on or off
Alt Enter Unused

AIN1: 1.7541 V
AIN2: 0.6821 V
AIN3: 1.2390 V
AIN4: 0.0006 V

- Move back to System Status 3 screen
+ Move forward to System Status 5 screen
Enter Move down to Main Menu screen
Alt Enter Log in (If PIN code <> 0), otherwise unused

iRIS 350FX Reference Manual V1.30

20 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Main Menu Screen (Level 2)

The Main Menu screen is used to select which type of information you want to look at.

Sensor Related Screens

Sensor Status Screen (Level 3)

This screen provides an overview of each sensor.

Line 1 indicates sensor ID, data source and its composite status including:

 ‘.’ if sensor is enabled
 ‘:’ if sensor and alarm(s) are enabled
 ‘*’ if sensor and alarm(s) are enabled and alarm(s) currently active

Line 2 indicates the raw input value.
Line 3 indicates the scaled (engineering unit’s) value.
Line 4 indicates the last logged value.

Sensor Menu Screen (Level 4)

The Sensor Menu screen is used to select sensor options.

Sensor Settings Screen 1/3 - Process (Level 5)

The Sensor Process screen shows the processing mode used to convert the incoming raw data to
engineering units. For pulse input sources I also shows the check counter.

MAIN MENU
>Sensors
Totals
Comms

1: Battery Volts
Input: 12.57
Scaled: 12.57
Logged: 12.62

SENSOR MENU
>Settings
Calibration
Data

+/- Move down/up through menu
Enter Select menu item
Alt Enter Move up to System Status 1 screen

+/- Move forwards/backwards through sensors
Enter Move down to Sensor Menu screen
Alt Enter Move up to Main Menu screen

+/- Move down/up through menu
Enter Select menu item
Alt Enter Move up to Sensor Status screen

PROCESS 1/3
Mode: Avg
+Min+Max
Chk Cnt: 0.0

+/- Move forwards/backwards through sensor setting screens.
Alt Enter Move up to Sensor Status screen

21 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Sensor Settings Screen 2/3 - Scaling (Level 5)

The Sensor Scaling screen shows the multiplier and offset used to convert the incoming raw data to
engineering units. It also shows the user calibration value (which is generated by the calibration operation)
and is added to the basic scaled value. See the calibration section on the next page.

Sensor Settings Screen 3/3 - Logging (Level 5)

The Sensor Logging screen shows the defined normal and alarm logging rates for this sensor and the
currently selected one. All rates are in minutes.

Sensor Calibration Screen (Level 5)

The Sensor Calibration screen is provided as a convenient tool for adjusting the sensor scaling offset on site,
without a tool such as a laptop being required. The calibration process is done by entering the actual
sensor value as measured by an external reference source such as a gauge board, EPB or thermometer.

 The top value on the display is the current, unadjusted sensor value reading. This is the value as it

would be with the offset set to zero (y=mx+0). I.e. Raw value (x) multiplied by the multiplier (m).

 The middle value is the interim calibration offset that is calculated continually by the iRIS, subtracting

the unadjusted value from the target value being entered via the keypad.

 The bottom value on the display is the target value which is entered by the user to match the actual

value measured externally. NOTE: When this screen is first shown, the target value will be set to
zero.

Sensor Calibration Acceptance Screen (Level 5)

SCALING 2/3
Mult 1.0000
Offset: 0.0000
Usr Cal: 7.544

LOGGING 3/3
Normal Rate: 60
Alarm Rate: 5
Is Norml: 60

+/- Move forwards/backwards through sensor setting
screens.
Alt Enter Move up to Sensor Status screen

+/- Move forwards/backwards through sensor setting
screens.
Alt Enter Move up to Sensor Status screen

CALIBRATION

11.6000
+ 0.8000
= 12.4000

+/- Increment / decrement target value on bottom line.

NOTE: If Enter is pressed while either the + or – key is already
down, the interim target value is reset to zero. This is useful
when removing a value that is excessive.

Enter only Multiply target value by factor of 10
Alt Enter Move to Calibration Acceptance screen

iRIS 350FX Reference Manual V1.30

22 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

The Sensor Calibration Acceptance screen is used to accept or decline the sensor calibration. If No is
selected, the calibration offset is discarded. If Yes is accepted, the interim offset entered in the calibration
screen previously is stored in the sensor’s offset location and overwrites the previous value.

Sensor Data Screen (Level 5)

The Sensor Data screen is used to view the logged sample data for a sensor. The data pointer value for the
top sample is displayed on the top right hand side.

Totaliser Related Screens

The Totaliser screens show yesterday's total (from 00:00:00 to 23:59:59 yesterday), the daily (since
00:00:00 today) and running (since last totaliser reset) totals for the four pulse input counters.

Total Screen x/4 (Level 3)

Reset Total Screen (Level 4)

The Total Reset screen is used to reset the two daily and the running totals for the selected totaliser.

DATA @ 53500
12/08/12
13:30

13.71

TOTALISERS 1/4
Y’day 134.6
Today 17.8
Run 5432.4

RESET TOTALISER 1?

Enter to initiate

+/- Move forwards/backwards through sample values.
Alt Enter Move up to Sensor Status screen
Alt +/- Pan left/right to view the rest of the sample time & date
information.

+/- Move forwards/backwards through sensor total screens
Enter Move down to Total Reset screen
Alt Enter Move up to Main Menu screen

Enter Reset total and move up to Sensor Total screen
Alt Enter Move up to Sensor Total screen

ACCEPT?
> No
Yes

+/- Move down / up through available options
Enter Accept current selection

23 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Comms Related Screens

Comms Status Screen (Level 3)

The Comms Status screen displays the current state of the wireless IP or CSD connection. The RSSI display
shows the Received Signal Strength Indication (RSSI) in dBm followed by the Bit Error Rate (BER).

The iRIS will not attempt to connect if the RSSI value is invalid (0 or < -113dBm).

Comms Menu Screen (Level 4)

The communications menu screen is used to select communication options.

Comms Setting Screen 1/8 - Protocol (Level 5)

The Protocol screen displays the current IP protocol and the logger’s communication address.

Comms Setting Screen 2/8 – APN / Local IP (Level 5)

The APN screen displays the name of the access point used to connect to the wireless network. It also
displays the local IP address allocated to the SIM card inserted in the unit for static IP address applications
or the most recent IP address assigned by the network when in dynamic IP mode.

MODEM IP STATUS
Ready

- Off Line ­RSSI: -75dBm

COMMS MENU
>Settings
Test Call-In

IP 1/8
PROTOCOL - UDP
Address 123

IP
2/8
APN/LOCAL IP
iquest.co.nz

Enter Move down to Comms Menu screen
Alt Enter Move up to Main Menu screen

+/- Move down/up through menu
Enter Select menu item
Alt Enter Move up to Comms Status screen

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

iRIS 350FX Reference Manual V1.30

24 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Comms Setting Screen 3/8 - Primary Base (Level 5)

This screen displays the remote IP address and port number to use for communication with the primary
base.

Comms Setting Screen 4/8 - Secondary Base (Level 5)

This screen displays the remote IP address and port numbers to use for communication with an optional
secondary base. If only a single base is used, these settings should be the same as the primary base.

Comms Setting Screen 5/8 - Schedule 1 (Level 5)

This screen displays the time range during which the unit is allowed to make a connection to the wireless
network. Refer to the Communications Schedule (Section Error! Reference source not found.) for details
n how these settings affect the communication availability.

Comms Setting Screen 6/8 - Schedule 2 (Level 5)

This screen displays the duration that the unit will stay connected to the wireless network and the interval
between connections during the allowable time range

IP 3/8
PRIMARY

192.168.1.10
Port 7778

IP 4/8
SECONDARY

192.168.1.10
Port 7779

IP 5/8
SCHEDULE
Start 0030
End 2359

IP 6/8
SCHEDULE
Duration 120sec
Interval 60min

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

25 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Comms Setting Screen 7/8– SMS Settings (Level 5)

This screen displays the primary and secondary phone numbers for the iRIS to use when it initiates the
sending of a SMS text message (SMS call-back mode).

Comms Setting Screen 8/8 – RS232 Settings (Level 5)

This screen displays the RS232 port status and mode. The port can be in one of two states, “Normal” or
“User”.

Normal: is the default setting and this is the mode that needs to be selected if a terminal session is to be
established with the iRIS.
User: If the application program has the appropriate serial driver code included (a user script), then the
RS232 port can be used to communicate with an external device such as an intelligent sensor. In this
situation, the user script will typically store the retrieved values in reserved database locations for access by
the virtual sensors set to source types 17 or 18. See Section Error! Reference source not found. for details
n sensor sources.

When the RS232 port is set to User mode, the name of the user script (if installed) is displayed on
the LCD as well.

RS232 Port Mode Screen (Level 6)

The RS232 Port Mode screen is used to swap the operating mode of the RS232 port between the Normal
and User modes.

SMS 7/8
PHONE LIST
[phone]
[phone]

+/- Move forwards/backwards through communication setting screens.
Alt Enter Move up to Comms Status screen

RS232 8/8
Port Mode is
NORMAL
Enter to chg

+/- Move forwards/backwards through communication setting screens.
Enter Move to RS232 Mode screen
Alt Enter Move up to Comms Status screen

RS232 PORT
 Enter for User

+/- Not used.
Enter Select new mode displayed and move back to Comms Setting Screen 9
Alt Enter Move up to Comms Setting Screen 9, but with mode left unchanged

iRIS 350FX Reference Manual V1.30

26 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Comms Test Screen (Level 5)

The Comms Test screen is used to initiate a user connection to the wireless network based on the call-back
mode and then send an announcement message to the base station or destination cellular phone. If the
base type is set to “Auto Send” the unit will forward any unreported data to the base station.

This may mean connecting to the wireless network (when mode = IP), or simply sending a text message
(when mode=SMS).

The actual call-back message sent and the communication method used depends on the call-back

mode and base type settings. See Section Error! Reference source not found. (Comms Cfg) for
urther details.

6.3 SMS Communication

The iRIS can send a standard text message in response to a request received via SMS (see Section 0 below).
If the call-back mode is set to 2 (SMS) a message is also sent if an alarm is activated, a comms scheduler
trigger occurs or user initiated communications test is done.
The SMS message is constructed from the site name, logger’s time, plus the sensor name, current value and
units of all the sensors that have their SMS enable flag set.
NOTE: The reply message is limited to 160 characters. If the reply is longer than this it is truncated.
The format is best shown in this example:

My Site Name,12:34:56,Water Level=7.69m,Battery=12.73V,RSSI=-85dBm

If the message was sent because of an alarm event, the message will have the prefix “ALARM!” at
the start of the message.

SMS Text Commands

The iRIS can accept incoming SMS messages and if they are valid it will respond appropriately. Any text
message received that is invalid will be ignored.
To use the SMS receive function, simply send a text to the iRIS voice number with the appropriate message
as described below.

None of the messages are case-sensitive. They are shown in upper case for clarity.

The six commands currently supported are:
RQ - ReQuest current sensor values.
The iRIS will reply with the standard SMS message described above.

GOL - Go On-Line.
This is useful as a poll-on-demand type function. The iRIS will not reply to this command, but will
immediately initiate a wireless connection of the type defined in the Callback Mode setting. Typically this is

CALL-IN TEST
 initiate

Enter Initiate comms test and move up to comms status screen
Alt Enter Move up to comms status screen

27 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

an IP connection, but could be a SMS message (but to the numbers defined in the Phone Number
configuration, not the requester’s number).
This command also supports a on-off request to a different IP address and port to the standard ones
configured.
In this case the usage is formatted as shown:
E.g. GOL 192.168.1.10,7777

INT – Sets the normal communication interval (in minutes).

This is useful for changing the normal call-in interval for the logger. The iRIS will reply indicating the normal
interval has been changed.
E.g. INT=120. This sets the communications schedule normal interval to 2 hourly (120 minutes).

AINT – Sets the alarm communication interval (in minutes).

This is useful for changing the alarms call-in interval. The iRIS will reply indicating the alarm interval has
been changed.
E.g. AINT=30. This sets the communications schedule interval to 30 minutes.

PICx – Take iRIS-CAM picture (where x is the resolution).
Use PIC1 (80x64), PIC3 (160x128), PIC5 (320x240) or PIC7 (640x480). If only PIC is sent, the default
resolution is 5 (320 x 240).
The iRIS will trigger the camera at the selected resolution.

SDI – One-off SDI-12 command.

This is useful as a simple SDI-12 transparent terminal style interface for specialised tasks. It should be used
with extreme care as some command may alter configuration parameters in an attached SDI-12 device.

E.g. SDI=7I! Requests the identifier for SDI-12 device address 7.

The SMS function is only available if the SMS service has been enabled in the SIM card and there
is not a wireless IP session active.

If the call-back mode is set to IP, then the iRIS will respond to incoming SMS requests, but will not
send an SMS message if an alarm occurs or the communication test function is initiated from the
LCD/keypad. If so, the iRIS will attempt to establish a wireless IP link.

6.4 General Hints

 If the iRIS will be installed in an outdoor situation, try to ensure that the LCD is facing away from direct

sunlight. This will help to enhance the readability of the display.

 If the unit is not to be used for some time, disconnect the internal battery to prevent it discharging.
 Always check the time and date are correct when commissioning the unit. The internal clock runs in

UTC (GMT) and all logged data is time/date stamped in this time zone. HydroTel™ and/or iLink 2012

automatically adjust for this. The configured UTC offset is only used to adjust the date/times on the
LCD (as viewed by users) to the local standard time zone.

 Immediately following installation, use the initialisation function (available under the Miscellaneous

terminal menu) to clear data and totals that may have been logged before the commissioning.

 The three iRIS 350FX application program segments (.350fx files) can normally be upgraded with no

effect upon the logged data or iRIS configuration. In the case of a major upgrade that may affect the
internal memory of the unit, iQuest will issue an upgrade notification explaining the procedure that
should be followed when upgrading your unit.

iRIS 350FX Reference Manual V1.30

28 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

6.5 RS232 Interface Telemetry / Gateway Comms

Overview

The iRIS may be used to communicate via external telemetry devices such as data radios or modems using
its RS232 port. When an external RS232 communication device is connected, the iRIS is also capable of
doing “store and forward” or “gateway” communications. This feature allows data packets that are not
addressed to this logger to be redirected to other iQuest devices. This chapter describes using the RS232
Telemetry function and also explains the gateway communications functionality.

RS232 Port Telemetry

If the RS232 port is to be used for telemetry, then its normal terminal/binary mode at 38400bps is disabled
and the port becomes fixed to iQuest binary protocol at the user configured port speed. There are two
methods of enabling the RS232 telemetry mode.

RS232 Only Telemetry Mode

If the iRIS does not have an internal wireless modem or else the internal modem is unused, the iRIS can be

configured for “RS232 Only” telemetry mode. This mode is controlled by the iRIS software based on

various actions (see table below) and the RS232 port does not need a special cable for connection to
external communications devices.

In RS232 Only telemetry mode, any call-back messages will always be directed out the RS232
port. This is why telemetry mode is enabled when a user is logged in. It allows call-back testing to
be done using the LCD/keypad.

Switching between telemetry and “normal” modes is controlled by the following actions:

Action

Mode

Key pressed when user is not logged in

Normal

User is logged in

Telemetry

User has just logged out

Normal

RS232 port activity in terminal or data download modes

Kept in Normal

At least 2 minutes of no activity on keypad or RS232 port

Telemetry

Table 4 – RS232 Port Telemetry Control

Mode

Protocol

House Icon

RS232 Speed

Normal

Terminal or Binary

Outline

115200bps

Telemetry

Binary Only

Filled in with ‘R’

As configured

Table 5 – RS232 Telemetry Mode Indications

Non-Dedicated RS232 Telemetry Mode

If the iRIS is fitted with an active internal wireless modem, then RS232 telemetry mode must be enabled by
a special cable which uses the RI handshake pin to enable the telemetry mode. Refer to the diagram below.

In non-dedicated telemetry mode, any call-back messages will always be directed out the wireless
port. Also, if a packet to be forwarded by the gateway is received from the RS232 port and the
wireless connection is not currently active the iRIS will initiate a connection.

29 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

In non-dedicated mode, if gateway communication is configured it will be in “bridging” mode. This is where
data packets are redirected (bridged) between the wireless port (IP or CSD) and the RS232 port. This
scenario is used when for example; an iRIS is used to bridge an IP connection to other loggers only
reachable by radio.
The diagram below shows a typical cable required to enable RS232 telemetry in non-dedicated mode. The
actual modem/radio connections may vary depending on the type of device used. The DSR line from the
modem or radio is used to enable the RS232 port and the RI line enables the binary only mode and sets the
port speed to the one configured in the communications configuration menu.

Figure 4 - Typical RS232 / Data Radio Cable

In this mode, the RS232 telemetry mode is controlled by the cable. If it is unplugged and a
standard null-modem cable connected, the iRIS RS232 port will immediately switch back to
normal port operation, with the usual terminal and binary communications at 38400bps. The
connection icon (house) will always indicate the status of the wireless connection only.

6.6 Gateway Communication

The iRIS supports a powerful communication function - gateway, or redirected communications. Simply
put, this allows an iRIS to transfer packets of data between ports, totally in the background without any
programming required (beyond setting up the gateway offset.)

Uses include:

 Radio comms repeater function
 IP to radio bridging

When an incoming data packet is received from either communications port, the iRIS does the following:

 Is this message for me? If it is, then accept and process it. Gateway redirection is not needed and

no further action is taken.

 Check if the iRIS has a gateway offset configured. If it does, then test the destination address in the

received packet and see if it falls in the range covered by the gateway. If a match is found, then the
packet will have its source and destination addresses changed (aliased) and be transmitted. In non­dedicated mode it will be sent from the other port. In dedicated mode it will be sent from the same
port that the packet was received on.

 If the packet has not been used by this point then it is rejected and lost.

Note: All retries are the responsibility of the transmission originator.
The only setup required to use gateway communications is to set the gateway table offset.

AUX_RXD (IN) 3

AUX_TXD (OUT) 11

0V (SIGNAL) 15

GPIO4 BUSY (OUT) 10
+13V8 (OUT) 8

WHITE

YELLOW

BLACK

BLUE

RED

2 RXD (IN)

3 TXD (OUT)

5 OV (SIGNAL)

8 CTS (IN)

6 DSR (IN)

FRAME GND

Tait TM80xx Radio
DB15 (M)

iRIS Datalogger
DB9 (F)

SCREEN

9 RI (IN)

10K

FLYING LEAD
TO DIG OUT

GPIO6 ENABLE (IN) 9

GREEN

iRIS 350FX Reference Manual V1.30

30 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Aliased Gateway explained

The iRIS uses a gateway method called "Aliased Gateway Communication". In other words, it alters the
destination and source addresses of a received packet before it is redirected back out via the gateway.
The primary reason for this in a radio only situation is to completely separate radio communication paths
between stations. This is to avoid a packet that has been redirected through an intermediate station being
received and replied to by the far destination station at the same time. This might be due to unusual RF
propagation conditions where direct communications is not normally achievable between the originator
and destination stations but suddenly becomes possible.
By addressing the original packet from the originating node (usually HydroTel™) to a notional (non-existent)
number, the gateway iRIS can add an offset to the address (correcting to the real address) and pass it on to
the distant node. Any directly received packet will now be ignored by the distant iRIS as the address will
not match.

Gateway Example

An iRIS, set to address 14, is installed at a hilltop rainfall measuring site. This logger is within range of a
wireless network and it uses IP communications with the HydroTel™ base.
A second iRIS, which is set to address 67, is installed down in the valley at a water quality site. This site has
no wireless network coverage, so a pair of low-power radios is used to link the two sites. Each radio
connects to the RS232 port on its respective iRIS logger.

The hilltop site uses a special cable (see Figure 4 above) to enable non-dedicated RS232 telemetry mode
because it also has wireless connectivity. As the valley site has no modem, it is set to “RS232 only”
telemetry mode and it uses a standard RS232 cable to connect to the radio.
The HydroTel™ base computer (which has a communications address of 0) needs to access both iRIS
loggers. To achieve this, the hilltop iRIS is enabled for gateway communication and for convenience its
offset gateway is set to 1000. This means that the site will redirect any packet with a destination address
between 1000 and 1099.

To enable alarm call-back from the iRIS at the valley site, its call-back address is also set to 1000 to
cause the hilltop gateway logger to redirect messages to the HydroTel™ base.

The only change at the HydroTel™ base is to set the address for the valley site to 1067 in the

station configuration form, rather than its actual address of 67. The address gets changed as it
passes through the gateway iRIS logger as described below.

This is what happens to the data packets during a typical requestresponse data conversation.

 HydroTel™ sends a request packet to the valley site via IP (which has the same IP address as the

hilltop site in HydroTel™). It is addressed to destination address 1067 from sender’s address 0.

 The gateway logger matches the destination address (1067) to be in its gateway address range.
 The packet’s source and destination addresses are aliased by applying the gateway offset (1000).
 The gateway logger sends the aliased packet via the radio down to the remote iRIS. It is now

addressed to destination address 67 from sender’s address 1000.

 The remote iRIS processes the request and sends back its response via the radio. This packet is

addressed to HydroTel™ as destination address 1000 from the valley iRIS sender’s address of 67.

 The gateway logger matches the destination address (1000) to be in its gateway address range.
 The packet’s source and destination addresses are aliased by applying the gateway offset (1000).
 The gateway logger sends the aliased packet via the IP network to the HydroTel™ base. It is now

addressed to destination address 0 from sender’s address 1067.

31 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

7 Using Modbus Slave Mode

The Modbus protocol slave mode support is a feature supported by the standard iRIS 350FX program
variants. Custom variants dor not have support for this feature as the RS232 port is often used by these in
a different way.

When enabled, the iRIS functions as a simple Modbus slave (server). Third party equipment is the master

and can write values to or read values from a set of predefined “holding registers”. In the case of the

written holding registers, the iRIS 350FX can be configured to access these values as sources for one or
more sensor channels.

In order to enable the Modbus operation on the shared RS232 port, the user must do this with the
keypad/LCD interface when on site. If Modbus mode is configured, a safety timeout switches back to
Modbus after a period of no activity on the port, in the event a user forgets to manually reselect that mode.

The iRIS 350FX operates in Modbus RTU mode (Modbus ASCII mode will be added at a later date).
Supported port speeds are 1200, 2400, 4800, 9600, 19200, 38400 and 115200bps. Parity in RTU mode is

settable to Even, Odd or None. In compliance with the Modbus specification, when parity is set to ‘None’,

an extra stop bit is inserted. In RTU mode, 8 data bits are used and in ASCII mode, 7 data bits are used.

If the RTU is writing values to the iRIS frequently, then the iRIS can log a period average and minimum and
maximum values during the log period as well.

There is also a basic write timeout where the holding registers are set to an invalid value after a
predetermined time of no write commands being received from the Modbus master. This can be disabled
by setting the timeout to zero.

Configuring iRIS 350FX to use Modbus

This section explains how to configure an iRIS 350FX to use Modbus input in iLink 2012.

Connect the logger using iLink 2012 and go to the General settings under the Configuration tab. Expand the
sensors tree. In the screenshot on the next page, sensor 12 (Modbus) is selected and the ‘Modbus 2 Byte

Short’ has been chosen from the source dropdown list. So it will use the values that are written to holding

register 40112 for logging (2 Byte Shorts are written in registers 40101-40120 and 4 Byte Floats are written
in registers 40201-40240).

iRIS 350FX Reference Manual V1.30

32 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Also, in the Comms section there is a new tab for Modbus settings as shown below. Set the Mode to ‘RTU’
and enter the address and parity.

33 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Enabling RS232 Modbus Operation using Keypad/LCD

If a user is logged on, they can access the different menu options using the iRIS keypad.

The Modbus operation is enabled by accessing Screen 8 of the Comms Settings. This screen displays the
RS232 port status and mode. The port can be in one of two states, “Normal” or “User”.

Normal: is the default setting and this is the mode that needs to be selected if a terminal session is to be
established with the iRIS.

User: If the application program has the appropriate serial driver code included (The Modbus feature or a
user script), then the RS232 port can be used to communicate with an external device such as an intelligent
sensor.

When the RS232 port is set to User mode, the name of the user script is displayed on the LCD as well.

Click ‘Enter’ to change to User Mode.

Again click ‘Enter’ to set the user ‘Modbus’.

Use the ‘Enter’ key again to change it back to normal mode.

RS232 8/8
Port Mode is
NORMAL
Enter to chg

RS232 PORT
 Enter for User

RS232 8/8
Port Mode is
USR: MODBUS
Enter to chg

iRIS 350FX Reference Manual V1.30

34 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

7 Troubleshooting

This section offers possible answers to common installation and/or configuration issues.

7.1 Can’t connect to the iRIS via the RS232 port.

Check that the PC application (iLink or terminal program such as HyperTerminal®) is set for the correct
comms port and speed (38400bps). Also check that the iRIS is not in RS232 Only Telemetry mode. This is

indicated by a solid black house icon with an ‘R’ symbol in it being displayed on the LCD. If it is in this

telemetry mode, switch back to normal mode by pressing any key or if currently logged in, then log out by
pressing Alt-Enter from a top level screen. See Section 0 for details on using RS232 Telemetry mode.

7.2 iRIS will not start when the battery is first connected.

Check that the battery voltage is at least 12.2V. The internal battery management hardware is designed to
shut the unit down when the battery becomes discharged to a certain point. It will not restart unless the
battery is deemed to have sufficient capacity for normal operation.

7.3 Pulse lost when iRIS connected to other equipment.

In almost all installations where an iRIS is connected in parallel with other equipment to share a common
pulse input (e.g. from a flow meter) there has not been a detrimental effect, as the iRIS presents a relatively
high impedance to the circuit.
However, in the event that connecting an iRIS does cause pulse failure, try removing the debounce
selection link for the appropriate input. This sets the input to electronic switching mode, even if the actual
pulse source is a clean contact (reed switch or similar).

7.4 Unable to connect to an IP network.

SIM Card: Check the SIM card is active and enabled for IP connectivity service.
APN: The unit must be configured for a valid APN that must also match the SIM account APN.
Signal: The iRIS will not attempt to connect if the RSSI is 0 or < -113dBm. Use a higher gain antenna

if the signal strength is marginal.

IP Settings: The iRIS will not attempt to connect unless both the primary and secondary base settings

are defined. (IP addresses and port numbers are non-zero). If the secondary base is not
used, set it to the same values as the primary base.

See Appendix I for a list of the network settings for the iQuest APN or iQuest Global Data Network.

7.5 iRIS will not respond to SMS requests.

Account: Check the account is active and the SMS service is enabled.
Power Mode: If full power save is selected, the wireless modem is shut down.
Connection: If the iRIS is connected on an IP session, the SMS feature is unavailable. Use a scheduled IP

connection to minimise the time that SMS is unavailable.

Voice Call: If an iRIS 350FXV is connected on a voice call, the SMS feature is unavailable.

35 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

7.6 iRIS 350FXV answers a voice call, but no sound is heard.

If the iRIS is currently connected to the wireless network with an IP link the iRIS voice processing function is
disabled. However the internal modem may still answer the incoming call independently but have no audio
available.

Set the IP connectivity using the scheduler so that it has a high availability for voice (short on-line sessions).

7.8 Unable to access terminal menu.

If the security code has been enabled and this is unknown, then access is not possible. Please contact the
person responsible for setting the code in the first instance. The code is set by an authorised user using
iLink.
However, if the security code is known and yet access is still denied, check the case of the entry is correct.
E.g. Caps Lock key is not on. The code is case-sensitive and must match exactly.

7.9 Digital Output activates when user is logged on.

This indicates the output is set to a scheduled mode with special features enabled. This mode is to enable
easy sensor calibration or radio communication testing when the sensor or radio is controlled by a
scheduled digital output. Otherwise the person on site would have to wait until the next scheduled
operation to be able to perform the test.

7.10 SDI-12 sensors log a “NaN” value.

Until an SDI-12 instrument has communicated correctly at least once, all sensors logging values from it are
inhibited. So no logging occurs until the first good measurement is obtained.
If, later the instrument fails to respond all sensors using values from the instrument will use the error value
of NaN (Not a Number).

7.11 Sensor values not included in SMS reply to “RQ”.

Whether or not a sensor is included in the SMS reply is controlled by the “Include in Voice/SMS” checkbox

in the sensor configuration in iLink or HydroTel™. This enables only the wanted sensors to be included.
Ensure that required sensors have this checkbox enabled and the updated configuration has been sent to
the iRIS 350FX.

7.12 External 12V battery not charging as expected.

This effect can occur when a large capacity external 12V lead acid battery and large solar panel are
installed. Over time, if the total current consumption of the iRIS and/or external equipment is significant,
the battery voltage may start to fall, despite a daily charging “spike” in sunlight being observed.

This may be due to the iRIS internal charger reaching its designed input current limit (approx. 900mA)
which means the battery progressively falls behind and may not reach full charge.

For sites with a large solar panel (20watt or greater) an external solar regulator is recommended.

iRIS 350FX Reference Manual V1.30

36 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

8 Appendix A – Specific Information

8.1 General Characteristics

The iRIS 350FX is supplied in an environmentally sealed (IP66) enclosure constructed from a special
corrosion-resistant aluminium alloy that is finished in a hard-anodised coating. This provides a very high
degree of mechanical strength and EMI shielding, and enables completely stand-alone mounting in outdoor
situations. The unit comes standard with an integral 12V gel-cell battery, membrane keypad and a 4 lines x
19 characters (plus icons) LCD.

The iRIS 350FX supports a maximum of twenty external sensors (1-20). Sources for these sensors may be
chosen from physical digital or analogue inputs or virtual sources (via serial communication or calculations).
Sources may also be from internal measurements (battery voltage, supply voltage, temperature and RSSI).
Each sensor has six associated alarms, each with separate trigger and reset levels. Each alarm also has a
duration, which is used to delay the alarm trigger for analogue inputs and to determine the time over which
pulse input counters should be totalised (rainfall etc).

Data from all enabled sensors are logged in a four word (8 byte) compressed format which includes full
date and time stamp to a 1 second resolution. The iRIS 350FX supports SDI-12 communication with a range
of industry standard intelligent sensors.

A variant of the iRIS 350FX which is designated the iRIS 350FXV offers voice annunciation of sensor values
using the voice bearer of the wireless service.

The iRIS 350FX supports the connection of a proprietary serial camera, the iRIS-CAM. This enables the iRIS
to capture colour images which can be unloaded in the same way as logged data. Due to resource
limitations, the iRIS 350FXV is unable to support the iRIS-CAM in conjunction with the voice feature.

Figure 5 - iRIS 350FX External View

37 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

8.2 Technical Specifications

Dimensions: 160mm x 130mm x 67mm (6.30in x 5.11in x 2.64in)
(Excluding glands)

Mass: 1450g (3.19lb) with gel-cell battery fitted.

Power Supply: Internal 12V @ 0.8A/Hr rechargeable sealed lead acid battery. Can also connect an

external regulated 12V dc power supply or rechargeable sealed lead-acid battery.

Charger Supply: External 15-30Vdc supply. Supports a directly connected solar panel (no regulator).

Power Consumption: Less than 6mA @ 12V in idle mode. Actual current consumption is dependent on

power management mode, wireless modem state and I/O configuration.

Comms Interfaces: 1x RS232 DB9, 38,400 bps, DTE configuration.

1x Integral multi-band wireless modem or
1x Plug-in comms adaptor E.g. Ethernet, satellite etc. Requires PCB Rev 1.2+

Digital I/O: 4 x Digital Inputs/Outputs. Each channel configurable as either an input or output.
Digital Input Mode:

- 30Vdc maximum input, switch to 0Vdc to activate.

- Link selectable for either mechanical (<20Hz) or electronic (<5kHz) switching.

Digital Output Mode:
When set for output, the channel can be either:

- Switched 12V out (max 100mA) or

- Open-drain pull-down (max 100mA @ 30V)

Analogue I/O: 4 x 16 bit uni-polar analogue inputs. Range 0 – 5.000V. Input impedance 98kΩ.

Referenced to 0V common. Internal measurements available for monitoring are:

 Battery Voltage
 Supply Voltage
 Internal Temperature (C or F)
 Received Signal Strength (RSSI or RSCP)
 Link selectable for either voltage (0-5V) or current (0-20mA) mode. Integral

current mode resistor value 100R.

SDI-12 Interface: SDI-12 hardware interface that fully complies with the SDI-12 electrical standard.

Software support to SDI-12 standard 1.3.

Logging Memory: Non-volatile 8MB flash storage of 1,085,476 time/date stamped data points.

Circular buffer mode (overwrites oldest data when memory full).
A typical site with 2 parameters logged every 15 minutes plus battery voltage
logged hourly will give 3.3 years of storage before data overwrite occurs.

Audio Memory: iRIS 350FXV only. Non-volatile 8MB flash storage of PCM audio files. Total

cumulative audio playtime 12 minutes at 11.025kHz sampling rate.

Clock/Calendar: Non-volatile with user replaceable lithium back-up battery module. Accurate to +/-

20 seconds / month

iRIS 350FX Reference Manual V1.30

38 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

Environmental: Storage Temperature: -20C - +85C. (-4F - +185F)
Operating Temperature: -10C - +70C. (14F - +158F)

Enclosure sealed to IP66 with gasket and glands.

Mounting: 4 x M4 (3/16”) blind mounting holes in rear of case.

4 x 16mm (¾”) compression glands for power supply and I/O cabling access.

8.3 Mounting

The iRIS can be mounted by installing suitable screws through the mounting pillars which are exposed when
the lid is opened. The recommended mounting screws are M4 machine screws or Twinfast® wood screws.

Figure 6 - Mounting Diagram

It is very important that the four screws retaining the lid are tightened firmly after installation to
maintain the IP66 rating of the enclosure.

The mounting holes are on 142mm (5.11in) width by 80mm (3.2in) height centres.

39 iQuest (NZ) Ltd - PO Box 15169, Hamilton, New Zealand Tel: [phone] Fax: [phone] Email: [e-mail]

8 User Notes