Difference between revisions of "Monitoring Solution"

From OROS Wiki
Jump to navigation Jump to search
 
(49 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Introduction==
==Introduction==
The OROS Monitoring solution is a tool dedicated to advanced triggering based on analysis results. It includes a "watch dog" feature to keep NVGate and analyzer running over a long period of time.
The OROS Monitoring solution can continuously supervise the noise and vibration levels of your critical assets, notifying alerts autonomously when predetermined levels are exceeded and catching real time high added value data on the spot.


[[File:15216.png|700px]]
[[File:monitoring_drawing.jpg|700px]]


[[File:monitoring.PNG|1000px]]
This solution is dedicated for mid to long term monitoring application, and the main features are:


It can manage the automatic recovery of the Monitoring module, restart the analysis, NVGate, as well as the analyzer (using the additional USB/RJ11 autonomy box).
* Operate standalone: power cut and restart management
* From basic to advanced event triggering conditions
* Pre-trigger time domain signal recording remotely downloadable for further analysis
* Advanced and flexible actions on events
* Automatic alert notifications for rapid countermeasures
* Database and remote access to event log, trend, and measurement data for initial diagnostics at any time
* Flexible storage capabilities, suitable for site with or without a network connection


This module routinely identifies and evaluates user selected parameters and provides a panel of conditional actions to complete. The main features are:
==Installation==
===Download===
Download last version of [https://my.oros.com/categories/software/monitoring/ Monitoring Solution].


* Ensure that the analyzer is running.
===Equipment required for the installation===
* Ensure that NVGate is running.
USB drive containing Monitoring software installation setups “SetupM-Logger.exe” and "SetupM-View.exe".
* Trigger actions (macro, exe, etc.) depending on conditional measured scalar values.


This module is dedicated for mid to long term monitoring in order to have an autonomous recording and analysis.
NVGate software must have been installed first (from V16.00.002).


<font color="#FFFFFF">
===Installation of NVGate software===
[[Image:Monitoring_OROS_02.png|800px]]
First you need to [[NVGate_V16:_Install_Process|install NVGate]].


</font>''Figure 1 - Monitoring application interface''
===Installation of Monitoring software===
In the PC that is connected to OROS analyzer, run “SetupM-Logger.exe” program, and the following window is displayed:


----
[[File:Screenshot 2023-05-05 161522.png|400px]]


==Installation==
Click on “Next”, and the following window is displayed:
===Download===
 
Download last version of [https://orossas.sharepoint.com/:u:/g/support/EVxwgs_YRy9Dud6Yp50-c9QBzdeEq6YkrMSnCtoZxr2nCw?e=DK6HQw Monitoring V1.0].
[[File:Screenshot 2023-05-05 161641.png|400px]]
 
Read the terms in the license agreement and check “I accept the terms in the License Agreement” if you agree. Click on “Next”, the following window is displayed:
 
[[File:Screenshot 2023-05-05 161737.png|400px]]
 
Select the installation directory. It is highly recommended to keep the default location: C:\OROS\Programs\M-Logger. Click on “Install” to start the installation, and wait until the following window is displayed:
 
[[File:Screenshot 2023-05-05 161903.png|400px]]
 
Click on “Next”, the following window is displayed:


===Equipment required for the installation===
[[File:Screenshot 2023-05-05 162029.png|400px]]
USB drive containing Monitoring software installation setup “SetupMonitoring.exe”.


NVGate software must have been installed first.
Click on “Finish” to exit the setup wizard, and OROS M-Logger software is successfully installed.  


===Installation of NVGate software===
The drivers for the Autonomy kit are installed during the default installation.
First you need to [[NVGate_2021:_Install_Process|install NVGate]].


===Installation of Monitoring software===
Next, run “SetupM-View.exe” program in the PC which is used for checking collected data (usually is not the same PC which runs M-Logger), and the following window is displayed:
Run “SetupMonitoring.exe” program, and the following window is displayed:


[[File:image_2021-05-17_113913.png|400px]]
[[File:Screenshot 2023-05-05 162338.png|400px]]


Click on “Next”, and the following window is displayed:
Click on “Next”, and the following window is displayed:


[[File:image_2021-05-17_113933.png|400px]]
[[File:Screenshot 2023-05-05 162433.png|400px]]


Read the terms in the license agreement and check “I accept the terms in the License Agreement” if you agree. Click on “Next”, the following window is displayed:
Read the terms in the license agreement and check “I accept the terms in the License Agreement” if you agree. Click on “Next”, the following window is displayed:


[[File:image_2021-05-17_113955.png|400px]]
[[File:Screenshot 2023-05-05 163249.png|400px]]
 
Select the installation directory. It is highly recommended to keep the default location: C:\OROS\Programs\Monitoring. Click on “Install” to start the installation, and wait until the following window is displayed:


[[File:image_2021-05-17_114021.png|400px]]
Select the installation directory. It is highly recommended to keep the default location: C:\OROS\Programs\M-View. Click on “Install” to start the installation, and wait until the following window is displayed:


Click on “Finish” to exit the setup wizard, and OROS Monitoring software is successfully installed. It will create a shortcut on your desktop but also to NVGate "Links" folder in order to have a direct access from NVGate via the link section.
[[File:Screenshot 2023-05-05 163430.png|400px]]


The drivers for the Autonomy Box are installed during the default installation.


In order to ensure an autonomous monitoring, it is necessary that both the PC and Monitoring Application are able to be automatically restarted. To allow that, create a shortcut of the Monitoring application into the windows startup directory (C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup). The monitoring application will take care of restarting NVGate if it is not already running.
Click on “Finish” to exit the setup wizard, and OROS M-View software is successfully installed.


===Autonomy kit installation (optional)===
===Autonomy kit installation (optional)===
The autonomy kit must be plugged on the RJ11 analyzer<nowiki>'</nowiki>s port and to the USB slot of the computer, and drivers should be installed. Drivers are provided in the installation and can also be installed manually in case troubleshooting is necessary.
The autonomy kit must be plugged to the analyzer<nowiki>'</nowiki>s RJ11 port and to the PC USB port, and drivers should be installed. Drivers are installed automatically during the installation of M-Logger, and can also be installed manually in case troubleshooting is necessary.


This autonomy kit is dedicated to OROS analyzers. Do not use with any other device.
This autonomy kit is dedicated to OROS analyzers. Do not use it with any other device.


Only use original components furnished.
Only use original components provided.


[[Image:Monitoring_OROS_03.gif|framed|none]]
[[Image:Monitoring_OROS_03.gif|framed|none]]
Line 70: Line 82:




''Figure 2 – Autonomy kit installation in case of OR36''</font>
''Figure 1 – Autonomy kit installation with OR36''</font>


[[Image:Monitoring_OROS_01.png|50px]]This '''Autonomy Kit''' contains electronic equipment. It should not be mixed with general household waste. For proper treatment, return this product to OROS or to any local company authorized to recycle waste electrical and electronic equipment.
[[Image:Monitoring_OROS_01.png|50px]]This '''Autonomy Kit''' contains electronic equipment. It should not be mixed with general household waste. For proper treatment, return this product to OROS or to any local company authorized to recycle waste electrical and electronic equipment.
Line 81: Line 93:
* 2012/19/EU WEEE directive
* 2012/19/EU WEEE directive


===PC and Windows configuration===
In order to guarantee a full autonomy, the computer must be configured to reboot in case of any power failure. The following PC parameters are advised:


<u>'''PC automatic restart due to power failure:'''</u>
===Database installation and management===
 
====Database installation====
 
MongoDB is a document-oriented NoSQL database used for high volume data storage and used by OROS Monitoring. OROS Monitoring solution is compatible with MongoDB 6.0.x only. MongoDB can be installed on different platform, and following instructions explain how to install it on Windows or Linux system.
 
=====Installation on Windows system=====
 
a. Pre-requisites
MongoDB support these Windows versions :
* Windows 10 et 11 64 bits
* Windows Server 2016, 2019, 2021 64bits
 
Download installation files:
* MongoDB: https://fastdl.mongodb.org/windows/mongodb-windows-x86_64-6.0.5-signed.msi
* Mongosh: https://github.com/mongodb-js/mongosh/releases/download/v1.8.0/mongosh-1.8.0-x64.msi
 
b. MongoDB installation
 
Execute mongodb-windows-x86_64-6.0.5-signed.msi and click on “Complete”:
 
[[File:Picture1.png|400px]]
 
Let default parameters filled:
 
[[File:Picture2.png|400px]]
 
Install
 
c. Configure MongoDB
Open with a text editor mongod.cfg file located in mongodb folder, default : "C:\Program Files\MongoDB\Server\6.0\bin\mongod.cfg".
 
We need to enable zstd compression, find wiredTiger block and edit it as followed :
<code>
  wiredTiger:
    collectionConfig:
      blockCompressor: zstd
</code>
 
Configure the net part as needed, example with port 27017 and allowing any external IP address :<code>
  # network interfaces
  net:
    port: 27017
    bindIpAll: true
    #  bindIp: 127.0.0.1"
</code>
 
If you want to secure the connection to MongoDB, only allow know IP address.
 
Documentation is available on official website: https://www.mongodb.com/docs/manual/reference/configuration-options/
 
d. MongoDB Shell installation
 
Run mongosh-1.8.0-x64.msi, uncheck “Install just for you” and continue installation.
 
[[File:Picture3.png|400px]]
 
Run mongosh.exe from "C:\Program Files\mongosh". A command window will popup asking MongoDB information, do not write anything and press Enter, connection should be done:
 
[[File:Picture4.png|400px]]
 
e. Create an admin user
 
In the shell windows type: ''use admin''
 
Then the following command will create an administrator user for MongoDB, which is mandatory. You will be able to create standard ReadOnly or Write access user using Monitoring dedicated M-DBTools.
 
In this example the admin user created is named “oros” and his password is “oros”, please use a strong password for the admin user:
 
''db.createUser({ user: "oros" , pwd: "oros", roles: ["userAdminAnyDatabase", "dbAdminAnyDatabase", "readWriteAnyDatabase"]})''
 
[[File:Picture5.png|400px]]
 
Restart the computer, and now MongoDB is configured and ready to be used.
 
=====Installation on Linux system=====
 
Installation on Debian
 
https://www.mongodb.com/docs/v6.0/tutorial/install-mongodb-on-debian/
 
https://www.mongodb.com/docs/mongodb-shell/install/
 
a. Pre-requisites
 
Packages: gnupg2, wget, sudo, net-tools, curl
 
b. MongoDB installation
 
* Add MongoDB server key
 
wget -qO - https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add –
 
* Add MongoDB repository
 
Debian 11
 
echo "deb http://repo.mongodb.org/apt/debian bullseye/mongodb-org/6.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list
 
Debian 10
 
echo "deb http://repo.mongodb.org/apt/debian buster/mongodb-org/6.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list
 
Debian 9
 
echo "deb http://repo.mongodb.org/apt/debian stretch/mongodb-org/6.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list.
 
* Install MongoDB
 
sudo apt-get update
 
sudo apt-get install -y mongodb-org
 
sudo apt-get install -y mongodb-mongosh
 
c. Configure MongoDB
Open with a text editor mongod.cfg file : /etc/mongod.conf
 
We need to enable zstd compression, find wiredTiger block and edit it as followed :
<code>
  wiredTiger:
    collectionConfig:
      blockCompressor: zstd
</code>
 
Configure the net part as needed, example with port 27017 and allowing any external IP address :<code>
  # network interfaces
  net:
    port: 27017
    bindIpAll: true
    #  bindIp: 127.0.0.1"
</code>
 
Documentation is available on official website: https://www.mongodb.com/docs/manual/reference/configuration-options/
 
d. Enable MongoDB as a service
 
systemctl enable mongod.service
 
e. Create an admin user


To account for any potential power failure at the analyzers location the following settings should be programmed on the PC to automatically switch on the PC once the power is restored.
mongo


Access the PC<nowiki>'</nowiki>s BIOS:
use admin


* Restart PC, press F12 (on most PC<nowiki>'</nowiki>s) to access the PC<nowiki>'</nowiki>s Bios.
db.createUser({ user: "oros" , pwd: "oros", roles: ["userAdminAnyDatabase", "dbAdminAnyDatabase", "readWriteAnyDatabase"]})
* Check the Bios parameters.
* On power management check the option "power on AC".


Specific settings should be chosen in the computer
f. Start MongoDB
* PC


Contact you IT manager to properly configure the computer : disable low-power sleep mode, no password to automatically restart windows, no low-energy or powering-off option …). In addition, installation of Teamviewer is recommended in order to monitor from a remote access.
sudo systemctl start mongod


If you plan to monitor your application for more than a couple of hours, it is advised to power both the computer and the OROS analyzer by mains (not on battery).
====Database management====


Consider installing a remote access software.
MongoDB is the database engine, and at least one database needs to be created to be used by OROS Monitoring solution.


It could be useful to control the computer when an alert is trigged for example.
Run M-DBTools.exe, which is installed in M-Logger or M-View folder (by default C:\OROS\Programs\M-Logger or C:\OROS\Programs\M-View), and login:


==Operating the Monitoring solution==
* Server address: Your server address, localhost if database is installed on running PC
===First steps in NVGate===
* Server port: 27017 (by default, other if you changed it in your MongoDB configuration file)
* User name: Defined in “Create an admin user” chapter
* Password: Defined in “Create an admin user” chapter


One should go first through the basic settings of the acquisition of NVGate. From NVGate, setup a project dedicated to monitoring and display the scalar values which should be monitored on the current layout.
[[File:Picture6.png|400px]]


<font color="#4DA836">'''Create a new project'''</font>
Please note that only administrators are allowed to run this tool, otherwise it will not connect to MongoDB.


A new project, with the name "Monitoring App", should be created as below when first starting.
Server information and databases list will be displayed once connected.


Then a new setup configuration should be started
[[File:Picture7.png|400px]]


[[Image:Monitoring_OROS_04.png|framed|none]]
=====Manage databases=====


<font color="#4DA836">'''Setting up the inputs and analysis'''</font>
a. Create a database


Then one should go through inputs, analysis and display setups using for example ''Gotoresult''
Fill a name in the dedicated field then press create, after few seconds/minutes the database will appear into the list.


[[Image:Monitoring_OROS_05.png|framed|none]]
[[File:Picture8.png|400px]]


<font color="#1F497D">''Figure 5 - Inputs setup''
b. Database information


</font>
Clicking on your database will show some information like the version, number of object, space used ...
[[Image:Monitoring_OROS_06.png|framed|none]]


Figure 6 - <font color="#1F497D">''Adding displays of Scalar values''</font>
[[File:Picture9.png|400px]]


It is necessary to display scalar values: those will be the ones to be monitored and trigger actions
c. Update database


<font color="#4DA836">'''Adding/naming a layout:'''</font>
Due to an upgrade of M-Logger / M-View, it might be necessary to update your database, and thus M-DBTools is needed.


<big>'''This current layout must be named "monitoring" (in lowercase)'''</big>. Here below is shown one way to rename the current layout: right click on "Layout1" and the rename possibility is shown
Select the desired database and press update. Depending on the number of objects this may take some time, you will be notified once it's done.


[[Image:Monitoring_Layout_Rename.png|framed|none]]
=====Manage users=====


<font color="#1F497D">''Figure 7 - Renaming the layout''</font>
Users are manageable in the "Users" panel:


<font color="#4DA836">'''Saving the project and the model'''</font>
[[File:Picture10.png|400px]]


[[Image:Monitoring_OROS_08.png|framed|none]]
a. Create user


Then the project should be saved
Click on "Create new user" button, a dialog will popup asking for an username and a password, then click on create, the user will appears in the user list.


===First steps in the Monitoring Application===
b. Grant access to user
Launch "Monitoring_Settings.exe" which is located into Monitoring folder. You will be able to fill some values which are necessary to monitor and operate the watchdog. Those are:


* '''NVGate location''': NVGate folder location (containing NVGate.exe).
* Grant access to a dedicated database
* '''Workbook name''': Name of the monitoring model.
* '''Project name''': Name of the monitoring project.
* '''Autonomy kit connection''': Analyzer type should be detected automatically. This is necessary to ensure the Monitoring Box functions properly. It supports V2 and V3s instruments (for OR36 and OR38) as well as OR35TW
* '''Analyzer IP''': If the IP is not defined correctly, the application will not be able to check if the unit is on and therefore will also not be able to boot or shutdown the Analyzer.
* '''RebootBox COM:''' Select the Monitoring Box COM Port. This is required to boot/shutdown the analyzer. If the Monitoring Box is not connected, or the correct drivers are not installed the list will be empty. If more than one COM port are listed, please ensure you are selecting the rebootbox one.
* '''Significant digits:''' Set significant digits to display.


As shown in the dialog window as below
Clicking on a user and a database will show the access rights for this user:


[[Image:Monitoring_OROS_09.png|800px]]
[[File:Picture11.png|400px]]


<font color="#1F497D">''Figure 10 - Monitoring and Autonomy box parameters settings''</font>
Access can be granted by clicking on the desired rights, below "READ_WRITE" is selected, allowing the user to write to the database, which is mandatory for a M-Logger user.


In the following window, settings can be entered in order to let the system use the email Action
[[File:Picture12.png|400px]]


[[Image:Monitoring_OROS_10.png|800px]]
Then click on "Update rights" to apply the new rights.


<font color="#1F497D">''Figure 11 – Setup of the email''</font>
* Grant access to all databases


===First start of the Monitoring Application===
Checking "Any databases" will display different access rights, which will be applied to all database + MongoDB instance. Also, if you need to create another MongoDB administrator then it’s an "Any Databases" rights, and select "ROOT" + "DB_ADMIN" + "USER_ADMIN" rights.
After parameters set-up, launch the Monitoring application, press "Refresh", It will recognize some parameters and display your scalars in the current layout.


Then, configure the condition you want for each scalar and linked actions. To do that, select an operator to compare the measured value with the target value (which must also be defined). For example, if you select "<nowiki>></nowiki>" and "2" for an acceleration scalar, when this value is larger than 2 the selected action will be triggered.
[[File:Picture13.png|400px]]


Finally, close the Monitoring Application, close NVGate, shutdown your analyzer, and then launch the Monitoring Application. If everything starts by itself, Monitoring was setup properly and monitoring has initiated.
Then click on “Update rights” to apply the new rights.


===User interface===
===PC and Windows configuration===
The user interface main window is as below. It is built with 3 main sections: Parameters (as described previously), Monitoring panel, and the Logbook.
In order to guarantee a full autonomy, the computer must be configured to reboot in case of any power failure. The following PC parameters are advised:


[[Image:Monitoring_OROS_11.png|framed|none]]
<u>'''PC automatic restart due to power failure:'''</u>


<font color="#1F497D">''Figure 12 - Main user interface window''</font>
To account for any potential power failure at the analyzers location the following settings should be programmed on the PC to automatically switch on the PC once the power is restored.


Access the PC<nowiki>'</nowiki>s BIOS:


[[Image:Monitoring_OROS_12.png|800px]]
* Restart PC, press F12 (on most PC<nowiki>'</nowiki>s) to access the PC<nowiki>'</nowiki>s Bios.
* Check the Bios parameters.
* On power management check the option "power on AC".


<font color="#1F497D">''Figure 13 - Main user interface window''</font>
Specific settings should be chosen in the computer
* PC


===Monitoring panel===
Contact you IT manager to properly configure the computer : disable sleep mode, no password to automatically restart windows, no low-energy or powering-off option …).
In addition, installation of Teamviewer is recommended in order to monitor from a remote access.


[[Image:Monitoring_OROS_13.png|900px]]
In order to open your windows session automatically : https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/turn-on-automatic-logon


<font color="#1F497D">''Figure 14 - The Monitoring panel window''</font>
If you plan to monitor your application for more than a couple of hours, it is advised to power both the computer and the OROS analyzer by mains (not on battery).


The columns have the following content:
Consider installing a remote access software.


* Information retrieved from NVGate running project:
It could be useful to control the computer when an alert is trigged for example.
* '''Window: '''Selected scalar window<nowiki>'</nowiki>s name.
* '''Module: '''Selected scalar module<nowiki>'</nowiki>s name.
* '''Result: '''Selected scalar process<nowiki>'</nowiki>s name.
* '''Channel: '''Selected scalar channel<nowiki>'</nowiki>s number.
* '''Label: '''Selected scalar input<nowiki>'</nowiki>s name.
* '''Values: '''Selected scalar values (SI).
* '''Units: '''Selected scalar units.
* Information specified by the user:
* '''Operator: '''Condition to be satisfied for actions:
* '''<nowiki>></nowiki>: '''If the measured value is greater than the target value, then action.
* '''<nowiki><</nowiki>: '''If the measured value is less than the target value, then action.
* '''Trigger Values: '''Condition to be satisfied for actions.
* '''Action: '''What do you want to do when the condition is satisfied:
* Activate / Deactivate outputs.
* Run / Stop analyzer.
* Trigger a User Event.
* Launch a macro (coming from NVGate).
* Email
* '''Hold off (s): '''Time holdoff is the delay between each action coming from this scalar (e.g.: 10s means the action cannot be triggered during the 10s following a triggered action.). Default value is 5 seconds and must be higher than 1 second.
* '''Persistence (s): '''Time persistence is the time necessary to trig the action (e.g.: 2s means the action will be triggered only if the condition is respected during 2s).
* '''Comments: '''Comments, it will be used in Email.
* Information computed by the monitoring application:
* '''Status: '''Green if the condition is not satisfied (no action). Red if the condition is satisfied (action).
* '''Events: '''How many times it has been triggered.


==FAQ==
==FAQ==

Latest revision as of 13:42, 19 June 2023

Introduction

The OROS Monitoring solution can continuously supervise the noise and vibration levels of your critical assets, notifying alerts autonomously when predetermined levels are exceeded and catching real time high added value data on the spot.

Monitoring drawing.jpg

This solution is dedicated for mid to long term monitoring application, and the main features are:

  • Operate standalone: power cut and restart management
  • From basic to advanced event triggering conditions
  • Pre-trigger time domain signal recording remotely downloadable for further analysis
  • Advanced and flexible actions on events
  • Automatic alert notifications for rapid countermeasures
  • Database and remote access to event log, trend, and measurement data for initial diagnostics at any time
  • Flexible storage capabilities, suitable for site with or without a network connection

Installation

Download

Download last version of Monitoring Solution.

Equipment required for the installation

USB drive containing Monitoring software installation setups “SetupM-Logger.exe” and "SetupM-View.exe".

NVGate software must have been installed first (from V16.00.002).

Installation of NVGate software

First you need to install NVGate.

Installation of Monitoring software

In the PC that is connected to OROS analyzer, run “SetupM-Logger.exe” program, and the following window is displayed:

Screenshot 2023-05-05 161522.png

Click on “Next”, and the following window is displayed:

Screenshot 2023-05-05 161641.png

Read the terms in the license agreement and check “I accept the terms in the License Agreement” if you agree. Click on “Next”, the following window is displayed:

Screenshot 2023-05-05 161737.png

Select the installation directory. It is highly recommended to keep the default location: C:\OROS\Programs\M-Logger. Click on “Install” to start the installation, and wait until the following window is displayed:

Screenshot 2023-05-05 161903.png

Click on “Next”, the following window is displayed:

Screenshot 2023-05-05 162029.png

Click on “Finish” to exit the setup wizard, and OROS M-Logger software is successfully installed.

The drivers for the Autonomy kit are installed during the default installation.

Next, run “SetupM-View.exe” program in the PC which is used for checking collected data (usually is not the same PC which runs M-Logger), and the following window is displayed:

Screenshot 2023-05-05 162338.png

Click on “Next”, and the following window is displayed:

Screenshot 2023-05-05 162433.png

Read the terms in the license agreement and check “I accept the terms in the License Agreement” if you agree. Click on “Next”, the following window is displayed:

Screenshot 2023-05-05 163249.png

Select the installation directory. It is highly recommended to keep the default location: C:\OROS\Programs\M-View. Click on “Install” to start the installation, and wait until the following window is displayed:

Screenshot 2023-05-05 163430.png


Click on “Finish” to exit the setup wizard, and OROS M-View software is successfully installed.

Autonomy kit installation (optional)

The autonomy kit must be plugged to the analyzer's RJ11 port and to the PC USB port, and drivers should be installed. Drivers are installed automatically during the installation of M-Logger, and can also be installed manually in case troubleshooting is necessary.

This autonomy kit is dedicated to OROS analyzers. Do not use it with any other device.

Only use original components provided.

Monitoring OROS 03.gif


Figure 1 – Autonomy kit installation with OR36

Monitoring OROS 01.pngThis Autonomy Kit contains electronic equipment. It should not be mixed with general household waste. For proper treatment, return this product to OROS or to any local company authorized to recycle waste electrical and electronic equipment.


CE.pngThis Autonomy Kit complies with following European Standards:

  • 2014/35/EU low voltage directive
  • 2011/65/EU and 2015/863 ROHS directive
  • 2012/19/EU WEEE directive


Database installation and management

Database installation

MongoDB is a document-oriented NoSQL database used for high volume data storage and used by OROS Monitoring. OROS Monitoring solution is compatible with MongoDB 6.0.x only. MongoDB can be installed on different platform, and following instructions explain how to install it on Windows or Linux system.

Installation on Windows system

a. Pre-requisites MongoDB support these Windows versions :

  • Windows 10 et 11 64 bits
  • Windows Server 2016, 2019, 2021 64bits

Download installation files:

b. MongoDB installation

Execute mongodb-windows-x86_64-6.0.5-signed.msi and click on “Complete”:

Picture1.png

Let default parameters filled:

Picture2.png

Install

c. Configure MongoDB Open with a text editor mongod.cfg file located in mongodb folder, default : "C:\Program Files\MongoDB\Server\6.0\bin\mongod.cfg".

We need to enable zstd compression, find wiredTiger block and edit it as followed : 

 wiredTiger:
   collectionConfig:
     blockCompressor: zstd

Configure the net part as needed, example with port 27017 and allowing any external IP address : 

 # network interfaces
 net:
   port: 27017
   bindIpAll: true
   #  bindIp: 127.0.0.1"

If you want to secure the connection to MongoDB, only allow know IP address.

Documentation is available on official website: https://www.mongodb.com/docs/manual/reference/configuration-options/

d. MongoDB Shell installation

Run mongosh-1.8.0-x64.msi, uncheck “Install just for you” and continue installation.

Picture3.png

Run mongosh.exe from "C:\Program Files\mongosh". A command window will popup asking MongoDB information, do not write anything and press Enter, connection should be done:

Picture4.png

e. Create an admin user

In the shell windows type: use admin

Then the following command will create an administrator user for MongoDB, which is mandatory. You will be able to create standard ReadOnly or Write access user using Monitoring dedicated M-DBTools.

In this example the admin user created is named “oros” and his password is “oros”, please use a strong password for the admin user:

db.createUser({ user: "oros" , pwd: "oros", roles: ["userAdminAnyDatabase", "dbAdminAnyDatabase", "readWriteAnyDatabase"]})

Picture5.png

Restart the computer, and now MongoDB is configured and ready to be used.

Installation on Linux system

Installation on Debian

https://www.mongodb.com/docs/v6.0/tutorial/install-mongodb-on-debian/

https://www.mongodb.com/docs/mongodb-shell/install/

a. Pre-requisites

Packages: gnupg2, wget, sudo, net-tools, curl

b. MongoDB installation

  • Add MongoDB server key

wget -qO - https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add –

  • Add MongoDB repository

Debian 11

echo "deb http://repo.mongodb.org/apt/debian bullseye/mongodb-org/6.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list

Debian 10

echo "deb http://repo.mongodb.org/apt/debian buster/mongodb-org/6.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list

Debian 9

echo "deb http://repo.mongodb.org/apt/debian stretch/mongodb-org/6.0 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list.

  • Install MongoDB

sudo apt-get update

sudo apt-get install -y mongodb-org

sudo apt-get install -y mongodb-mongosh

c. Configure MongoDB Open with a text editor mongod.cfg file : /etc/mongod.conf

We need to enable zstd compression, find wiredTiger block and edit it as followed : 

 wiredTiger:
   collectionConfig:
     blockCompressor: zstd

Configure the net part as needed, example with port 27017 and allowing any external IP address : 

 # network interfaces
 net:
   port: 27017
   bindIpAll: true
   #  bindIp: 127.0.0.1"

Documentation is available on official website: https://www.mongodb.com/docs/manual/reference/configuration-options/

d. Enable MongoDB as a service

systemctl enable mongod.service

e. Create an admin user

mongo

use admin

db.createUser({ user: "oros" , pwd: "oros", roles: ["userAdminAnyDatabase", "dbAdminAnyDatabase", "readWriteAnyDatabase"]})

f. Start MongoDB

sudo systemctl start mongod

Database management

MongoDB is the database engine, and at least one database needs to be created to be used by OROS Monitoring solution.

Run M-DBTools.exe, which is installed in M-Logger or M-View folder (by default C:\OROS\Programs\M-Logger or C:\OROS\Programs\M-View), and login:

  • Server address: Your server address, localhost if database is installed on running PC
  • Server port: 27017 (by default, other if you changed it in your MongoDB configuration file)
  • User name: Defined in “Create an admin user” chapter
  • Password: Defined in “Create an admin user” chapter

Picture6.png

Please note that only administrators are allowed to run this tool, otherwise it will not connect to MongoDB.

Server information and databases list will be displayed once connected.

Picture7.png

Manage databases

a. Create a database

Fill a name in the dedicated field then press create, after few seconds/minutes the database will appear into the list.

Picture8.png

b. Database information

Clicking on your database will show some information like the version, number of object, space used ...

Picture9.png

c. Update database

Due to an upgrade of M-Logger / M-View, it might be necessary to update your database, and thus M-DBTools is needed.

Select the desired database and press update. Depending on the number of objects this may take some time, you will be notified once it's done.

Manage users

Users are manageable in the "Users" panel:

Picture10.png

a. Create user

Click on "Create new user" button, a dialog will popup asking for an username and a password, then click on create, the user will appears in the user list.

b. Grant access to user

  • Grant access to a dedicated database

Clicking on a user and a database will show the access rights for this user:

Picture11.png

Access can be granted by clicking on the desired rights, below "READ_WRITE" is selected, allowing the user to write to the database, which is mandatory for a M-Logger user.

Picture12.png

Then click on "Update rights" to apply the new rights.

  • Grant access to all databases

Checking "Any databases" will display different access rights, which will be applied to all database + MongoDB instance. Also, if you need to create another MongoDB administrator then it’s an "Any Databases" rights, and select "ROOT" + "DB_ADMIN" + "USER_ADMIN" rights.

Picture13.png

Then click on “Update rights” to apply the new rights.

PC and Windows configuration

In order to guarantee a full autonomy, the computer must be configured to reboot in case of any power failure. The following PC parameters are advised:

PC automatic restart due to power failure:

To account for any potential power failure at the analyzers location the following settings should be programmed on the PC to automatically switch on the PC once the power is restored.

Access the PC's BIOS:

  • Restart PC, press F12 (on most PC's) to access the PC's Bios.
  • Check the Bios parameters.
  • On power management check the option "power on AC".

Specific settings should be chosen in the computer

  • PC

Contact you IT manager to properly configure the computer : disable sleep mode, no password to automatically restart windows, no low-energy or powering-off option …). In addition, installation of Teamviewer is recommended in order to monitor from a remote access.

In order to open your windows session automatically : https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/turn-on-automatic-logon

If you plan to monitor your application for more than a couple of hours, it is advised to power both the computer and the OROS analyzer by mains (not on battery).

Consider installing a remote access software.

It could be useful to control the computer when an alert is trigged for example.

FAQ

I use microsoft windows on chinese/japanese language. However, monitoring crash when I click on "refresh button". How to solve this ?

On windows regional settings, tab admin, let the unicode program on your language, however click on "beta : use the unicode UTF-8...". This solve the issue.

Faq.PNG

Retrieved from "https://wiki.oros.com/index.php?title=Monitoring_Solution&oldid=11507"