Omicron BETA 9.2 User manual

Manual reference
24042020, Rev. 1.1
April 2020
BETA 9.2
Quick Start Guide

Read this manual before working with the product. For personal and system safety, and
for optimum product performance, make sure you thoroughly understand the contents
before installing, using, or maintaining this product.
If you encounter a problem with your Beta 9.2, review configuration information to verify
that your selections are consistent with your application: input and output configurations;
chosen limits; etc. If the problem persists after checking the above, you can get technical
assistance on [phone], Monday thru Friday, 7:00 a.m. to 5:00 p.m., Eastern
Standard Time. You can also write to [email protected]. Specialized staff will
discuss your application case.
Please have the following information available:
➔All Configuration Information
➔All Provided Manuals
➔Chip ID and a list of parts provided with the equipment.
Contact Information
To contact the manufacturer of Beta 9.2:
LATIN AMERICA:
Tel: [phone]
WhatsApp: [phone]
[email protected]
Visit us: www.omicroning.co
2

Index
1. Power the device to turn it on: 4
2. Send data wirelessly: 5
2.1. Enter Service Mode: 5
2.2. Connect the device to a Wi-Fi® network: 7
3. Enter to remote Monitoring Platform: 9
4. Review Device Dashboard on the Monitoring Platform: 9
5. Remote Configurator: 10
5.1. Remote Configurator elements: 11
5.2 How to use the Remote Configurator: 12
Troubleshooting 14
I can not enter the remote Monitoring Platform 14
The device has stopped updating data on the monitoring platform 14
When trying to save the configuration, I see the message: “You do not have permission to
perform this configuration. It is recommended to check the device ID entered, or the device type
selected. ” 15
I can't find the device ID on its back label 15
3

This quick start guide is designed to start or verify the correct operation of Beta 9.2
controllers; even before mounting. With these devices it is possible to measure variables of
up to five (5) analog or digital sensors; as well as to control processes through five (5) relay
outputs. The information that the devices collect is sent to the Centriomega® monitoring
platform.
To follow this guide you will need:
●Beta 9.2.
●Power cable, for connection to 110 - 220 VAC, 50/60 Hz lines.
●A device enabled for internet navigation (PC, tablet, smartphone).
●Additional cables, cable ties, and tools for electrical work (screwdriver, wire stripper,
and multimeter; mainly).
1. Power the device to turn it on:
Beta 9.2 is powered by a two-wire power cable connecting its AC1 and AC2 inputs
(indicated in Fig. 1) to 110 - 220 VAC, 50/60 Hz lines. In turn, the AC1 line can be bridged to
terminals CM1 and CM2, if you want to use any of the 12A relay outputs: RE1 or RE2 (note
that each 12A output uses 2 terminals).
Please note the following instructions:
●Connections should be made only in the complete absence of supply
voltage, and by trained technical personnel.
●If overvoltage events are foreseeable, surge protectors should be used.
●Before energizing the equipment, check the firmness and continuity of the
connections you make.
●A disconnect switch must be used between the equipment and its power
source, and a 0.5A and 6W fuse must be used between the power supply
and the device.
Once the equipment is energized, it will start its normal operating state, which can be
recognized when the LED indicated in Figure 1 blinks every second.
4

Fig. 1:   Beta 9.2 items of interest.
2. Send data wirelessly:
While the device is in a normal operating state, it will periodically send the data measured
by its enabled sensors (according to the minutes specified by the Publication Time
parameter); through the Sigfox network (to which it connects automatically when it is
turned on), or through a Wi-Fi® network (to which you must connect the device following
the steps in section 2.1. and 2.2.), to the Centriomega® remote monitoring.
NOTE:
In order to connect to the Sigfox network, or to a Wi-Fi® network, the device must have an
internal communication module that allows it. If you did not order it, you can request it from
the manufacturer. Remember that contact information is provided at the beginning of the
document.
2.1. Enter Service Mode:
You can enter Service Mode to configure aspects of the Wi-Fi® network to which you want
to connect the controller. To access the Service Mode, before powering up the device, make
an electrical bridge between terminals S1, S2, and GND (indicated in Figure 2); then energize
the device.
5

Fig. 2:   Bridge between terminals to access Service Mode.
When in Service Mode, the Beta 9.2 device generates a temporary Wi-Fi® network using
its built-in Wi-Fi® module, named "IoTDevice_", followed by the device ID (for example,
"IoTDevice_bcddc212345"). You must connect to this network with a device enabled for
internet navigation (such as a Smartphone, Tablet, or a PC).
Once connected to the network, we must access a page with the IP address: 192.168.4.1
(whose interface is shown in Figure 3). It is possible to enter the indicated page through any
internet browser; there you will find a menu with the buttons "Set up WiFI", and "More
information".
6

Fig. 3:   Beta 9.2 General Settings Page.
To exit Service Mode, disconnect power to the equipment and remove the jumper between
terminals S1, S2, and GND; after that you can turn it on again.
NOTE:
Exit Service Mode only after making or reviewing the desired settings on the web interface with
IP: 192.168.4.1.
2.2. Connect the device to a Wi-Fi® network:
To configure the credentials (name and password) of the network that will provide internet
access to the Beta 9.2 device, proceed as follows:
1. On the General Configuration Page (Fig. 4), press the Configure Wi-Fi button to go
to a page where you can see a scan of Wi-Fi® networks detected by Beta 9.2, two
fields to enter data, and two buttons (Save and Scan).
The page that loads after selecting Configure Wi-Fi, on the Home Page, is presented in the
following image:
7

Fig. 4:   Beta 9.2 Wi-Fi® Configuration Page.
2. In the fields at the bottom of the Wi-Fi® Configuration page (Fig. 4), enter the
credentials (name and password) of the network to which you want to connect
Beta 9.2; then press Save. If you want to connect the device to an open network,
you should not enter any password.
If the credentials entered are not correct, the following page will appear:
Fig. 5:   Invalid Wi-Fi® setup page.
Otherwise, you will see:
8

Fig. 6:   Correct Wi-Fi® setup page.
3. Enter to remote Monitoring Platform:
To review the data sent to the Centriomega® remote monitoring platform, log in to
iot.omicroning.co (the login form is displayed below), with the credentials provided by the
manufacturer of Beta 9.2:
Fig. 7:   Remote monitoring platform login form.
If you do not have credentials to enter, contact the device manufacturer or provider.
Remember that you can find contact information at the beginning of this document.
4. Review Device Dashboard on the Monitoring Platform:
After entering the remote monitoring platform supported by the manufacturer of Beta 9.2,
you can review the information sent by your device on its unique Dashboard.
To do this, enter the platform, go to a Dashboards (1, in Figure 8); then enter the Dashboard
9

list (2, in Figure 8) and select the Dashboard with your device ID (3, in Figure 8). The unique
identification of each device is marked on its back label.
Fig. 8:   Steps to view a specific Dashboard.
5. Remote Configurator:
Centriomega® platform users have access to a Dashboard that allows them to set
commands to remotely configure their devices (to find it, search for the Dashboard with the
name “Remote Configurator”, following the steps described in the previous section). Said
Dashboard presents users with a summary of the configuration options available for each
type of Omicron Engineering device, and only allows to choose a parameter to configure,
10

after indicating the device model, and the elements or general aspects of the device that are
wish to configure; therefore it contains:
Fig. 9:   Remote Configurator elements.
5.1. Remote Configurator elements:
1. Field for device ID
In this field, users must specify the UID of the device they wish to configure
remotely. Said UID is printed on the back labels of the equipment; or it can be
reviewed among the Device information stored by the platform (to do this, refer to
Troubleshooting section).
2. Device type selector
To select the model of the device to configure.
3. General aspect selector
Here, the user must select the general aspect of the device he wishes to configure.
4. Parameter type selector
This list allows the user to specify the type of parameter to be configured, for the
general aspect of the device chosen with selector 3.
5. Parameter selector
Finally, this list shows the parameters available for configuration, according to what
11

was chosen in lists 3 and 4.
6. Field for value to configure
In this field, the user must specify the value he wants for the parameter to be
configured, following the indications given by the interface.
7. Save command button
Once the user has chosen the parameter that he wishes to configure, and has
specified a configuration value, he must save the command on the platform so that
the device downloads it once it is ready for it.
5.2 How to use the Remote Configurator:
To configure a parameter using the Remote Configurator, follow these steps:
1. Enter the identification information of the device to be configured in fields 1, and 2.
2. Select the parameter you want to configure using selection lists 3, 4 and 5.
3. Enter the value you wish to assign to the parameter to be configured, in field 6, following
the indications that the interface presents over this field after choosing the parameter to
be configured.
4. After selecting the parameter to be configured, and entered the value to which it will be
configured; press the Save Command button. You will then be asked to confirm the action
in a pop-up window; and in case the configuration is saved successfully, the page will display
a message indicating it below the button.
Pressing the button will not clear the information entered or selected, to make it easier to
configure another device in the same way.
Based on the above, it can be concluded that in case that what is shown in the following
image is selected and entered in the Remote Configurator, the Datalog X-PRO 4a123b device
will configure the TPU of its sensor interface 2, to 10 minutes:
12

Fig. 10:   Example of configuration made with Remote Configurator.
13

Troubleshooting
I can not enter the remote Monitoring Platform
To enter the remote Monitoring Platform, use the credentials provided by the
manufacturer exactly as they are given; i.e., if you get assigned an username or password
with uppercase characters: enter them as assigned.
If you verify that the username or password provided by the manufacturer does not allow
you to enter, ask the manufacturer to change it.
The device has stopped updating data on the monitoring platform
If the monitoring platform does not record recent measurements from the device, do the
following to try to identify the problem:
1. Verify that the equipment is in a normal operating state:
The normal operating status of a Beta 9.2 can be recognized when the LED indicated in
Figure 1 blinks green every second.
2. Avoid interference of the wireless signals of the device:
It is essential to ensure that the device is within the coverage area of the wireless network
that it uses, therefore, try to locate it in a place that does not obstruct its wireless
transmissions (away from metal surfaces or objects, and from robust objects such as walls
or shelves; and preferably located in a high place).
3. If transmitting data via Wi-Fi, check the status of the Wi-Fi network to which it
must be connected, and the device connection to it:
Make sure that the configuration of the network to which the device connects does not
restrict its access (consult the personnel in charge of the network infrastructure in your
organization); on the other hand, verify that the network access credentials configured on
the device correspond to those managed by the network to which you want to connect it;
that is, that the SSID or password that you have configured for the equipment matches
those of the Access Point of the network to which you intend to connect. Typically, to
ensure such a match, the device is reconfigured with the correct credentials.
4. Contact the manufacturer
If after verifying that the problem presented by your device cannot be corrected by
following the recommendations given in the previous points; contact the manufacturer.
Remember that contact information is provided at the beginning of this document.
14

When trying to save the configuration, I see the message: “You do not have
permission to perform this configuration. It is recommended to check the device ID
entered, or the device type selected. ”
The interface does not allow you to configure non-existent devices, or to which you do not
have access from your account; therefore, the message will appear if you enter the ID of a
device not associated with your account, or if you select a type of device that does not
correspond to that of the ID entered. It is recommended to check the ID and the type of
device to be configured, before attempting to perform a configuration. If you see the
message, even after you entered the correct identification information of a device, ask for
help from the technical staff of Omicron Eng. Remember that Contact Information is
provided at the beginning of this document.
I can't find the device ID on its back label
Each device is delivered with a back label where you can find an ID, or MAC fields (these are
different from the FCC ID, which you must ignore). However, if you cannot find the
identification information on the back label of a device, you can review its identification
information on the remote monitoring platform. To do this, after entering the platform, in
the Devices tab, select the Devices option (1, in Figure 11); then, in the list that appears,
search and select the device from which you want to know the identification information (2,
in Figure 11); and finally locate said ID in the API Label field of the page with Device
information (3, in Figure 11).
15

Fig. 11:   Search for device identification information on remote monitoring platform.
The API label of each device is composed of its type, and its ID, separated by a hyphen (for
example: datalogxpro-123abc). Once the ID of interest has been identified, you can use it to
specify the device to be configured with the Remote Configurator.
¡For no reason modify the API label of a device associated with your account!
16

17