UniData Communication Systems Neon 3016A User manual

Manual
Neon 3000 Family
Neon Remote Loggers (NRL)
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC
Rules in the U.S.A. These limits are designed to provide reasonable protection against harmful interference when the equipment
is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to
correct the interference at his own expense.
This equipment has been tested for compliance with European regulations as follows:
Application of Council Directive:
2014/30/EU
Standards to which Conformity is declared:
CISPR 11:2010, Group 1, Class A
EN-61000-4-2:2008
EN-61000-4-3:2010
EN-61000-4-4:2012
EN-61000-4-5:2005
EN-61000-4-6:2008
Any changes or modifications to this equipment not expressly approved by the manufacturer Unidata Pty Ltd could void the
user’s authority to operate this equipment.
Revision History
File name/Revision Date Author & Change Details Checked/
approved
Unidata Manual - 30xxA NRL Family - 14 06 2017.docx 14 06 17 IM - draft MS
Unidata Manual - 30xxA NRL Family - 16 06 2017.docx 16 06 17 RS&IM – adding specs and
LCD functions MS
Unidata Manual - 30xxA NRL Family - 20 06 2017 20 06 2017 MS- added text CB
Unidata Manual - 30xxA NRL Family - 11 07 2018.docx 11 07 2018 IM New Specs for 3004B MS
Unidata Manual - 30xxA NRL Family - 23 07 2018 23 07 2018 MS connectivity additions CB
Unidata Manual - 3000 NRL Family - 13 09 2018 13 09 2018 AG MS Updates IM
Unidata Manual - 3000 NRL Family - 17 09 2018.docx 17 09 2018 IM adding 3001B Info
Copyright © Unidata Pty Ltd 2000-2013. All rights reserved. No part of this publication may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any spoken or computer language, in any form or by any means.
Electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without prior written permission of Unidata Pty
Ltd 40 Ladner St, O’Connor Western Australia 6163.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 2
TABLE OF CONTENTS
1.0Neon Technology and System Overview..........................................................................3
1.1Neon Remote Loggers ...................................................................................................... 5
1.2Typical Neon Measurement System.................................................................................. 5
1.3The NRL Stand Alone Data logger Implementation........................................................... 6
1.4The NRL Full Protocol Implementation - Internet Connection Required ............................ 6
1.5The NRL Message Based Implementation- LoRa LPWAN & Satellite Services ................ 6
1.6NRL Internal Architecture .................................................................................................. 7
1.7NRL Models ...................................................................................................................... 8
1.8NRL Programs (Schemes) and Prologger / Starlogger Emulation Mode ........................... 8
1.9NRL New Features............................................................................................................ 8
1.10NRL Data Storage options ................................................................................................ 9
2.0NRL LED Indicators ............................................................................................................9
2.13016, 3008, 3004 “High End” ............................................................................................ 9
2.23004M “Low End”............................................................................................................ 10
2.3Normal Scheme Indication .............................................................................................. 10
2.4Telemetry Indication........................................................................................................ 10
2.5Direct Connection Indication ........................................................................................... 10
2.6Firmware Update Indication ............................................................................................ 11
3.0NRL Status Menu Screens ...............................................................................................11
3.1Logger Status Screen Navigation.................................................................................... 12
3.2Scheme Status Data ....................................................................................................... 13
3.3Configure Logger ............................................................................................................ 14
4.0Summary of Neon Remote Loggers................................................................................16
4.13016A Neon Remote Logger – 16 Analogue Channels................................................... 16
4.23008A Neon Remote Logger – 8 Analogue Channels..................................................... 18
4.33004A Neon Remote Logger – 4 Analogue Channels..................................................... 20
4.43004B-MC Neon Remote Logger Cellular....................................................................... 22
4.53004B-ME Neon Remote Logger Ethernet...................................................................... 23
4.63004B-MH Neon Remote Logger Microsatellite .............................................................. 24
4.73004B-MI Neon Remote Logger Iridium Short Burst Data............................................... 26
4.83004B-ML Neon Remote Logger LoRa ........................................................................... 27
4.93001B-MC/L/I/H Borehole Neon Remote Logger Cellular, LoRa, Iridium SBD or
Microsatellite................................................................................................................................ 28
5.0Connections ......................................................................................................................30
5.13016A Neon Remote Logger – Connections/Terminations ............................................. 30
5.23008A Neon Remote Logger – Connections/Terminations ............................................. 33
5.33004A Neon Remote Logger – Connections/Terminations ............................................. 35
5.43004B-M000 – Connections/Terminations ...................................................................... 37
5.53001B-M0 – Connections/Terminations .......................................................................... 39

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 3
References
This manual should be read in conjunction with the associated
- Starlog 4 User Manual Management Software for Loggers and Neon Terminals and Loggers
Manual
- Neon Server Applications Software Documentation which is available on help screens on any
Neon Installation and in PDF form from the main Unidata web site
This manual and the StarlogV4 User Manual and the Neon Server User & Administrator Documentation
form part of the documentation suite for the overall Neon System.
1.0 NEON TECHNOLOGY AND SYSTEM OVERVIEW
The Neon system collects measurements from Neon Field Units / Neon Remote Loggers
(NRL) connected to field instruments and sensors and transmits these measurements to a
central Neon Web based system for data storage, analysis, data presentation, graphical
analysis and reporting and data transfer to other external systems.
The Neon system also provides facilities for remote management of Neon Field Units /
Neon Remote Loggers via the Neon Web interface to allow for remote reconfiguration,
sensor input changes and local program changes thereby minimising trips to site and
reducing cost.
The communication protocol between Neon Field Units / Neon Remote Loggers and the
central Neon Server is Internet Protocol / TCPIP and LoRa LPWAN technology protocol.
The communications method between Neon Field Units / Neon remote Loggers and the
central Neon Server can be any method which utilises TCPIP, and we support Cell Phone,
Wi-Fi, Direct Ethernet, Inmarsat BGAN M2M Satellite, Globalstar Satellite, Iridium Satellite
and LoRa LPWAN across public and private networks.
The Starlog 4 software is a desktop application which assists with the setup of Neon Field
Unit / Neon Remote Logger configuration. This software allows for a point and click setup
of Neon Field Unit / Neon Remote Logger internal programs, called schemes. Schemes
are downloaded to the Neon Field Units / Neon Remote Loggers via a serial interface
direct to the Neon Field Unit / Neon Remote Logger or uploaded to the Neon Web
interface to be downloaded to a neon Field Unit / Neon Remote Logger in the field via the
Neon network.
The Neon system is offered to customers based on two options:
- A customer owned server model, where the customer purchases a Neon Application
Software licence from Unidata and runs that software on their own servers,
or
- A hosted application service model where Unidata provides access to run the system
on Unidata secure cloud servers on a fee for service basis.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 4
Overview of the Neon System

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 5
1.1 Neon Remote Loggers
There are many different models of Neon Remote Loggers available. While the models
may be different, and the interfaces available in various models are different, the basic
operation of all Neon Remote Loggers is the same.
Typical Neon Measurement System
1.2 Typical Neon Measurement System
The figure above is an example of a Neon installation showing an NRL connected to a
Modbus sensor. Every day the NRL will send, via the Inmarsat satellite network, to the
Neon server a “packet” of information containing the data in raw format.
The Neon Server then extracts the raw data from the packet. The data is then stored on a
secure server until the client accesses the data using a standard Web Browser.
The Neon Server receives, processes, displays, stores and reports collected data in many
ways.
The Neon Server also can issue control commands based on pre-set algorithms and issue
alarms and notifications via several mediums.
Alarm set points can be set up on the NRL units as well as the Neon Server and alarm
notifications can be sent via several methods including email and SMS text messages.
Alarm triggers can initiate physical actions in the field such as turning pumps on and off or
activating other control functions based on the internal program within the NRL.
The Neon system has fully bi-directional communications between the NRL and the Neon
Server. This allows for remote diagnosis, remote programming and remote firmware
updating for operation of the remote equipment and thereby reducing costly site visits.
NRL units can be configured to read sensors, log data internally to local memory and push
data to the central Neon server at user settable intervals such as once a minute, every
few minutes, every hour, or once a day.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 6
Data can be viewed on the Neon Web interface in near real time from any browser and
the comprehensive reporting engine within Neon allows for reporting out to other systems
using email, FTP, and web services, either dynamically, every minute, or on a daily,
monthly, quarterly or annual basis.
1.3 The NRL Stand Alone Data logger Implementation
The NRL can be programmed with a program (scheme) in the factory or in a remote office
and then transported to the field to work as a stand-alone system, without the need to
have an internet connection. For this operation method the program (scheme) is
downloaded to the NRL using the Starlog 4 Logger configuration software. The data is
stored in the NRL and can be unloaded using the Starlog 4 Logger configuration software.
The Starlog 4 Logger configuration can be used to set up legacy logger emulations, such
as the Star logger and Prologger, so applications using these older loggers can continue
using the newer NRL models. If the emulation modes are used, the new features available
in the NRL are not available. Unidata suggests the program (scheme) should be updated
to utilise the features available in the newer NRL models.
1.4 The NRL Full Protocol Implementation - Internet Connection Required
The Internet provides the transport mechanism between the Neon Servers and the
telecommunication provider gateways. This means that NRL units can be used anywhere
in the world provided there is an internet connection available. The connection to the
internet can be via a cell phone data service, a satellite service or a Wi-Fi or Ethernet
connection.
With the full protocol service the communications between the NRL and the Neon Server
are closely coupled and each transmission is checked and acknowledged, such that a
beak in communications does not result in lost data. Rather the NRL attempts to
communicate with the Neon Server on a pre-set schedule and continues to log and store
data and then re-send if and when the communications link and/or the Neon Server
service is restored.
Also the remote NRL can be configured online, parameters can be adjusted and a new
program (scheme) and updated firmware can be downloaded remotely from the Neon
Server.
1.5 The NRL Message Based Implementation- LoRa LPWAN & Satellite Services
There are communications services available which provide a short message service,
similar to an SMS text message service.
The NRL supports LoRa LPWAN, Iridium Short Burst Data service and also other
emerging message based services. These services are in general terms message only
services, where a message is sent from the NRL to the Neon Server without
acknowledgement, without the ability to reconfigure NRL on line and without the ability to
download programs (schemes). These message based services are generally lower cost
and they suit low data rate applications very well and are less expensive.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 7
1.6 NRL Internal Architecture
The NRL Internal architecture is shown below. It contains two discrete sections:
1. A LOGGER section where the terminal connects to the field transducers and the
logging scheme, scan rates and diagnostics are managed.
The StarlogV4 support software allows a user to generate a logger program (called a
scheme) which defines transducer information, logging scan rates, logger interval etc
and various engineering unit definitions. These files are called, for example the LDR
and KBD files.
2. A COMMUNICATOR section which deals with communications to the server. This
section contains, for example, a scheduler component and the modem component,
either a Cellular Network modem or a Satellite Network modem. The communicator
manages functions such as the reporting interval, the number of communications
attempts per communications session, etc.
The StarlogV4 support software allows a user to generate a configuration file for the
Communicator section, called an FPO file in which the user sets the required
communications parameters.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 8
1.7 NRL Models
There are many different models of NRL, and while the software architecture remains the
same with all models, the larger models have more connectivity and more input channels
than the lower models.
There are two main groups:
1. The 3016, 3008 and 3004 are the higher end models with higher connectivity and are
housed inside metal enclosures with input terminals exposed on the side, for easy
sensor connection.
2. The 3004M models are lower end models with lower connectivity and are housed
inside smaller polycarbonate enclosures, or metal enclosures for high IP rating
applications.
All of the models and the connectivity details are listed in this manual in the section
Summary of Remote Loggers.
1.8 NRL Programs (Schemes) and Prologger / Starlogger Emulation Mode
NRL loggers operate in two modes: Native or Emulation.
In Native mode the logger operates much like a Neon Remote Terminal (NRT) and has a
memory layout and configuration settings broadly the same. It allows existing NRT
schemes to be used immediately without change.
In Emulation mode the logger operates like a Prologger (3016) or Starlogger (all other
3xxx models) with compatible memory layout and configuration options. It is intended to
allow the use of existing Prologger or Starlogger schemes immediately and later transition
to Native mode.
To access new NRL features requires porting both NRT and Prologger/Starlogger
schemes to the new NRL scheme type.
1.9 NRL New Features
The NRL offers several new features not available in earlier NRT and
Prologger/Starlogger loggers:
Critical data is stored in non-volatile FRAM, rather than volatile RAM, to allow for
faster recovery after power interruptions.
Improved memory management allows for more complicated scheme programs.
Floating-point support.
Support for >16-bit analog channels.
Support for 32-bit counter channels.
Support for multiple SDI-12 busses.
Support for multiple Modbus busses.
Support for burst transmission of each log record. This is particularly suitable for
IoT technologies such as LoRa, microsatellite systems or Iridium Short Burst Data.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 9
1.10 NRL Data Storage options
1.10.1 Flash
NRLs have internal Flash memory that is used to store internal data, the scheme program,
and all logged data.
1.10.2 MMC/SD Card
Not currently available, but future updates to NRLs will add support for saving logged data
to MMC/SD cards and for loading scheme programs saved to those cards.
1.10.3 USB Thumbdrive
Not currently available, but future updates to NRLs will add support for USB thumbdrives
with the same functionality intended for MMC/SD cards.
2.0 NRL LED INDICATORS
2.1 3016, 3008, 3004 “High End”
These loggers have six bi-colour (red/green) LEDs:
Label Description
Power Turns on when the NRL performs a scan, typically every few seconds. Green
indicates good power voltage. Red indicates the power is low.
Config Turns on when activity is detected on the USB configuration port, which is
used for configuration and local programming/unloading. Red indicates the
logger has detected something plugged in, but not communicating. Green
indicates successful communication.
Scheme Turns on every scan when the scheme program is being executed. The colour
is under scheme control. By default red indicates the scheme has stopped and
is not logging, while green indicates the scheme is running and logging as
programmed.
Neon Turns on when the logger is communicating with the Neon server. Red
indicates the logger is attempting to establish a connection, which takes
around 10 to 20 seconds. When the connection is successful the LED turns
green. When the communication completes (successfully or otherwise) it turns
off.
Status Indicates MMC/SD card activity. Green indicates a card has been detected.
Red indicates the card is busy and should not be removed.
USB This LED is located either on the top and labelled “USB”, or is located next to
the “USB Drive” on the side.
Green indicates a USB storage device has been detected. Red indicates the
device is busy and should not be removed.

Manual – 3000 NRL Family
Unidata Manual - 3000 NRL Family - 17 09 2018.docx Page 10
2.2 3004M “Low End”
These loggers have three bi-colour (red/green) LEDs:
Label Description
PWR Same as the Power LED described above.
SCHM Same as the Scheme LED described above.
COMS A combination of the Config, Neon, and Status LEDs described above. If any of
those LEDs would be green, this LED will be green. Otherwise, if any of those
LEDs would be red, this LED will be red. If all of those LEDs are off, this LED
will be off.
2.3 Normal Scheme Indication
In normal operation the Power/PWR LED comes on first, quickly followed by the
Scheme/SCHM LED, then both turning off. This occurs at regular scan intervals as
specified by the scheme, which can range from one second to many minutes.
At each interval the Power/PWR LED is turned on for the duration of the scan, which is
typically less than a second, and is when the various logger inputs are read and the
scheme program executed.
The scheme also operates during each scan, after the sensors have been read. While the
scheme is executing, the Scheme/SCHM LED is lit. The colour of the LED is under
scheme control, but by default green indicates correct operation.
Unless the logger is communicating, no other LEDs will be lit.
2.4 Telemetry Indication
When the logger communicates with Neon, the Neon/COMS LED will be lit. It will start red
until a connection is established with Neon, at which time it will turn green. When the
communication process completes, the LED is turned off.
2.5 Direct Connection Indication
If you are using the USB port to directly connect to the logger, then the Config/COMS LED
will turn red when the logger detects a cable has been connected. When the logger
receives a command it recognises, it will turn the LED green to indicate a successful
connection. If no commands are quickly received, usually within half a second, the logger
will turn the port off to conserve power. It will also turn the port off when instructed by a
connected computer. It will check the port again after a few seconds.
As a result, the LED will blink red when a cable is plugged in, but the software is not
communicating. If the software is communicating, the LED will briefly light red before
changing to green when the logger received the first command. It will stay green while the
software is communicating (for example, updating test displays, or programming or
unloading the logger), then turn off when the software is finished.