Software manual

1.1. About this document

Present manual describes in details all functionalities of WE300, implemented in the Software version 3.1.1, released on November 2015. Please make sure that the Software Version of your WE300 is updated to the latest release mentioned on this manual, in order to avoid discrepancies between the versions.

In case of questions and issues not covered by present manual, you can contact Nethix Customer Support for further information:

Email: support@nethix.com

Phone: +39 0423 770750

Web Site: nethix.com

1.2. Overview

WE300 is an easy-to-use remote monitoring and control system complete with an integrated web interface, where every single functionality of the system can be managed. The basic elements to start up the system are a variable, an event and an action. The first sections will therefore concentrate on the description of these elements and on the Modbus protocol, the most used communication device protocol.

Further relevant concepts for a more comprehensive use of all available device functions are the data logging and the network configuration.

In the following sections all these concepts and their use through the WE300 will be described.

2.1. Generic variables

Many different types of variables are available, and for each of them parameters may differ. Only the section Generic Variable is valid for all types of variables. This section is structured as follows:

• Name: The name to be assigned to the variable. All alpha-numeric characters, and the character “_” are supported.
• Type: This allows to select the type of the variable. For each variable type the setting-parameters are different, see chapter 2.2. Type.
• Variable Status: enable/disable the variable
• Portal sending: it allows to enable/disable the sending of the variable value to an external portal/server. For further information regarding the data-sending, see relevant section 7. Data sending data sending.
• Non-volatile value: it allows to save the variable value every X minute and everytime the device is switched off or rebooted.
• Skip first read: enabling this optional function the system won’t read the first value of the variable. For example, if an event has been defined on the variable, and at the reboot of the system the variable is in alarm status, through this optional function no action will be enabled.
• Local log (min): it allows to set a different sampling time (in minutes) for each variable. The recorded data can be then exported or displayed in charts or tabs. For further information see section 8. Datalogger.

2.2. Type

Here are the different types of variables:

• Analog Input: Variables associated to the analogue inputs available on the WE300. AI1 has to be selected to associate the variable with the analogue input 1 (connectors AN1 and GND) while AI2 has to be selected to associate the variable with the analogue input 2 (connectors AN 2 and GND). Further information on paragraph 2.3. Analog input variables (AI).
• Digital Input: Variables associated to the digital inputs available on the WE300. It’s possible to choose among DI1, DI2, DI3 and DI4. Further information on paragraph 2.4. Digital input vriables (DI).
• Digital Output: Variables associated to the digital (relay) outputs available on the WE300. Select DOUT1 for the digital output 1 (connectors RL1A and RL1B) or DOUT2 for the digital output 2 (connectors RL2A and RL2B). Further information on paragraph todo 2.5. Digital output variables (DO).
• Modbus: Variables associated to Modbus registers. Further information on paragraph 3.2. Creation of Modbus variables.

2.3. Analog input variables (AI)

In order to create a AI variable, i.e. associated to one of the analogue inputs available on WE300, enter the page Administration → Variables. Clicking on New, it’s possible to enter the variable configuration page. Select Analogue Input on the field Type. Under the section Generic Variables all standard settings for any type of variable are available. For the description of all the fields of this section, see 2.1. Generic variables.

Let’s skip into the section Analogue Input: Variable Specific Settings.

First of all is requested to confirm the choice of the input, where to read the value. The choice is among AI1 or AI2. Then it has to be entered the measurement unit that will be displayed on charts and on Status -> Variable Status. Through the tabs Minimum value and Maximum value is possible to scale the variable. The minimum tension or current value will be associated to the Minimum Value; the same will be for setting the maximum value.

EXAMPLE: considering a temperature probe, controlled in tension, having min. value -20° and max. value 30°C, corresponding to 0V and 5V, it’s possible to configure the variable minimum value at -20, and the maximum at 30, in order to display the temperature directly expressed in degrees. Using the Decimals field, it will be possible to specify the number of decimals to be displayed.

WE300 analogue inputs have 10bit resolution and are hardware-configurable at factory (software configuration is not possible) in current (0-20mA), in tension (0-5V or 0-10V) and in temperature (NTC). The input value is constantly checked by the WE300, thus keeping controlled any configured thresholds.

2.4. Digital input vriables (DI)

In order to create a DI Variable, i.e. associated to one of the digital inputs available on WE300, enter the Administration → Variables page. Clicking on New, it’s possible to enter the variable configuration page.

Select Digital Input on the field Type. Under the section Generic Variables all standard settings for any type of variable are available For the description of all the fields of this section, see 2.1. Generic variables.

Let’s skip into the section Digital Input: Variable Specific Settings.

First of all is requested to confirm the digital input to be associated to the variable. It’s possible to choose among DI1, DI2, DI3 and DI4. Irrespective of the selected input, the fields Close label and Open label need to be completed. Close label refers to the value (or status), that will be displayed when the relevant digital input is closed, Open label refers to the open input. For WE300 a closed Digital Input variable has a logic value of 1. In case of an open input, the logic value is 0. This becomes a very important information for the definition and setting of the events. Once filled in above mentioned fields, the operating mode has to be selected:

• Normal
• Counter
• Time counter

Depending on selection, the meaning of the following fields will change.

2.4.1. Normal

A DI → Normal type variable allows to display the status of the digital input. It is then possible to define events/actions connected to the status change (from open to closed and vice-versa).

The only additional field to be configured is the Inverted led. This can change the visualization of the variable on the page Status → Variables Status. If this option is disabled, the open status of the input will be associated to a grey spot, while the closed status to a green one. With enabled option, the situation will be the opposite. For further information see relevant section 6.1. Variables status.

2.4.2. Counter

A DI → Counter type variable allows to count impulses on a digital input.

The first field to be completed is Count start, i.e. the starting point of the counter. This value will be considered only the first time: if the counter should be reset, it would then restart from 0.

• Counter end refers the maximum limit to be reached for resetting the counter. If this field is configured at zero, the counter will increase indefinitely without reverting to zero.
• Count increment is the increment unit value of each impulse of the counter.
• Measurement unit is the unit of measurement assigned to the counter. This will be displayed on charts and on the page Status → Variable Status.

The last field to be configured is Edge trigger, i.e. the edge to be considered for the impulse. Selecting Falling edge the counter will increase when the input changes form closed to open; selecting Rising edge the counter will increase when the input changes from open to closed; selecting Rising and falling edge the counter will increase at every edge changing.

2.4.3. Time counter

A DI → Time counter type variable allows to count the opening/closing time of a contact (expressed in seconds). This variable can be used for calculating the total operating time of a defined machinery.

After the configuration of the Edge Trigger (reminding that Falling edge refers to the change from closed to open, Rising edge refers to the opposite and Rising and falling edge to both of them) the type of counter has to be selected among following possibilities:

• Permanent: After the start of the counter, WE300 will increase the value at every second, until the user will reset it
• Stop on opposite edge: the counting will start at the occurrence of an edge change according to the choice made on the relevant field; the counting will stop when reaching the opposite edge and restart again at next change.
• Reset on opposite edge: the counting will be reset when reaching the opposite edge, and restart from 0 when the selected edge will be reached again.

2.5. Digital output variables (DO)

In order to create a DO variable, i.e. associated to one of the digital outputs available on WE300, enter the page Administration → Variables. Clicking on New, it’s possible to enter the variable configuration page.

Select Digital Output on the field Type.

Under the section Generic Variables all standard settings for any type of variable are available. For the description of all the fields of this section, see 2.1. Generic variables.

Let’s skip into the section Digital Output: Variable Specific Settings.

After the selection of the Output (between DOUT1 and DOUT2) to be associated to the variable to be created, it’s required to set the operating mode in the Output mode field. The available options are:

• Normally open: The output is normally open. Open label refers to the open status of the contact. Close label will close the contact.
• Normally closed: The output is normally closed. Open label refers to the open status of the contact. Close label will close the contact.
• Pulse open: The output operates in pulse mode. Open label refers to the open status of the contact. Close label will close the contact. Once closed, the outputs keeps this status for the time configured on the field Pulse duration, after that it returns automatically to the open status.
• Pulse closed: The output operates in pulse mode. Open label refers to the open status of the contact. Close label will close the contact. Once opened, the outputs keeps this status for the time configured on the field Pulse duration, after that it returns automatically to the closed status.

Regardless of the selected option, the field Status change delay(s) must be filled in with the number of seconds of delay required between an impulse and the enabling/disabling of the output.

Please note that the Non-volatile value option can be combined with the Output mode. If this option is not enabled, the start output status after a power-off or reboot will depend on the Output mode, i.e.: in case of Normally open/Pulse open output, the contact will start from open status; in case of Normally closed/Pulse closed output, the start of the contact will be from closed status. On the other hand if the non-volatile value option is enabled, the start output status will be the same as at the power-off or reboot of the system.

The status of the digital outputs can be modified through their association to an event either by an SMS command or directly from the page Status → Variables status.

3.1. Master Modbus

WE300 allows to create one master Modbus network on one of the available physical network: TCP/IP, 232, 485.

3.2. Creation of Modbus variables

To create a variable (of any type) enter Administration → Variables → Variables.

If some variables are already available, they will be displayed in the table with some of their main features.

To edit an existing variable click on its name, to create a new one click on New.

The name of the new variable is entered in the page for creating variables: the field Name accepts alpha-numeric characters and “_”. The space is not allowed.

Then select Modbus in the Type field.

Under the section Generic Variables all standard settings for any type of variable are available For the description of all the fields of this section, see 2.1. Generic variables.

According to the type of variable selected, the following section will have a specific structure:

• Modbus net: It allows to select the Modbus network to be associated with the new variable to be created. If no Modbus network is available, this field must be left blank.
• Modbus address: this field must be completed with the slave address of the device to be connected to the WE300.
• Memory address: this field must be completed with the slave memory register, where to read/write.

It’s now necessary to select the Access mode, i.e. the type of Modbus variable, among the following options:

• Read only: It’s possible to read the variable value but not to change it
• Write only: It’s possible to set the variable value but not to read it.
• Read and write: The variable value can be read and written.

In the field Data type is possible to select the variable number of bit.

3.2.1. 1Bit data type

In this field is requested to specify the position of the bit inside the word (1word=16 bit). Inside one single word there can be up to 16 variables of 1 bit each. If the variable, that we want to create, is on the first position of the word, the value “0” must be selected in the field Bit position. Alternatively if the variable, that we want to create, is on the last position of the word, the value “15” in the field Bit position must be entered.

In order to complete the creation of the variable, just set up a string for the open status (corresponding to value 0) and a string for the closed status (corresponding to value 1). These strings will allow to display the variable status (for example Open/closed, on/off, and so on..)

3.2.2. 8 bit data type

For the 8 bit variables is requested to specify the Bit position (it’s possible to choose only between 0 and 7, since 8 bit corresponds to half a word) and some other information available also for 16-32-32inv variables. If the variable, that we want to create, is in the first word position, the value “0” must be entered in the field Bit position. Alternatively if the variable, that we want to create, is in the middle of the word, the value “7” must be entered in field Bit position.

3.2.3. 16-32 bit data type

Selecting 16, 32 or 32inv on the field Data type, the following fields must be completed and specified:

• Measurement unit: measurement unit selected to be assigned to the variable
• Decimals number: quantity of decimal numbers to be displayed
• Minimum value: set the minimum (normally “0”) according to the type of variable
• Maximum value: set the maximum (for example 65535 for 16 bit variables) according to the type of variable.
• Scaled Minimum value/Scaled Maximum value: the two above mentioned fields are necessary for a correct interpretation of the read/written data by the WE300, even though they might not be relevant for the end-user.

Considering for example a 16 bit variable with min./max. values of respectively 0/65535: a user should need to measure a level from 0 to 10 meters. To this purpose it’s enough to set “0” as Scaled Minimum value and “10” as Scaled Maximum value.

3.2.4. 32 bit float data type

For the 32 Float / 32 Float inv variables it’s enough to set the measurement unit and the number of decimals. This type of variable doesn’t require any scaling.

By clicking Save the variable will be created.

Note

Information as Modbus address, Memory address, Access mode, Data type, Bit position are normally described in the data sheets of the Modbus devices.

It’s important to make sure that all parameters are correct, in case of doubts contact the salve device’s manufacturer or the Support at Nethix.

For further information about the use of the Modbus Protocol, visit the official site Modbus.org.

The following step is to create a Modbus command, suitable to interact by reading or writing with the new created variable. In order to enter the section dedicated to the Modbus commands, select Administration → Modbus → Commands on the menu.

3.3. Creation of Modbus commands

For granting a correct operating, all Modbus variables need to belong to one or more Modbus commands, according to the type of operation required.

Under the section Administration → Modbus → Commands all available commands (if previously created) will be displayed. In order to create a new command click on Add new command.

According to the type of variable to be written/read and to the requirements of the slave device connected to WE300, one of the following available functions has to be selected:

• Read coils -0x01
• Read holding registers -0x03
• Read input registers -0x04
• Write single coil -0x05
• Write single register -0x06
• Write multiple registers -0x10

All functions available in WE300 respect the Modbus standard.

Once made the selection of the function to be used, the following parameters need to be set:

• Slave address: it’s the address of the slave device, where to send all requests/writings. This address must be the same as the one entered in the field Modbus address, previously set in the variable configuration.
• Memory address: it’s the memory address of the slave device to be accessed. This must be the same as the one previously accessed in the field Memory address of the variable.
• Words number: it’s the number of word where to use the command. Some functions allow to enter more than one word (to be checked on slave device’s documentation). Setting for example “1” as Memory address and “10” as Words number, it should be possible to use one single command to enter 10 consecutive registers.
• Interval: Interval of time for the reading function. For the write function this option is not available (the writing of a register is enabled at request). Setting for example “5”, the reading of one or more registers/word is made every five seconds.
• Modbus Networks: If one Modbus network have already been created, it’s possible to select it.

Clicking on Save the command will be saved.

It’s important to make sure that all parameters are correct, in case of doubts contact the salve device’s manufacturer or the Support at Nethix.

For further information about the use of the Modbus Protocol, visit the official site Modbus.org.

Once created the command, it’s possible to proceed with the definition of the Modbus network. To enter this section, select Administration-> Modbus-> Networks from the menu, click the tab Networks on the top left side or click the link Create new network on the right side of the Save button.

In this last case, when the page for the creation of Modbus networks opens, the new created command is already associated with the network.

3.4. Modbus network creation

All Modbus variables and commands need to belong to a Modbus network to grant a correct functioning. WE300 supports several Modbus networks of different physical types.

Selecting Administration → Modbus → Networks from the menu, it’s possible to create a new network clicking on Add new network.

Through the fields Peer type and Physical network type is possible to get 2 different combinations:

• Master-RTU
• Master-TCP

3.5. Istant reading

It’s possible to read or write one or more Modbus registers without creating a variable or a command.

Entering the page Administration → Modbus → Raw, it’s possible to start an instant reading/writing of a given register, just by properly completing the following fields:

• Networks: Select the available network. This function is possible only if one network is already available.
• Function: Select the Modbus function to be used in order to read or write the register/s.
• Words number: indicate the word number “1” in case of 1-8-16 bit variables, and the “2” in case of 32 bit or float variables.
• Slave address: indicate the slave address to be entered
• Memory address: indicate the memory address to be entered.

In the field Value it will be displayed the value read (in case of reading functions) and a notification message of successfully executed reading/writing will be sent by the WE300.

3.6. Modbus expansions

WE300 includes 4 digital inputs, 2 analogue inputs and 2 digital outputs. The I/O module of WE300 can nevertheless be expanded with one or more additional expansion units of the range XP500.

In order to add or edit an expansion unit is necessary to enter the page Administration → Modbus → Expansions and click on New or select one of the previously added expansions.

• Name: Enter the name to be assigned to the expansion. This name will be used to create a variables group, where the variables referred to the inputs/outputs of the expansion unit will be saved.
• Type: It’s possible to select the type of expansion unit to be added.
• Client address: In this field is selected the slave address to be assigned to the expansion.

Once clicked on Save, the WE300 will try to set the client address entered in the connected expansion unit, using the default communication parameters (38400, 8, N,1) and assuming that the expansion is connected to the slave address 1 (according to manufacturing settings). It’s therefore recommended, always to keep the slave address 1 free.

Once added the expansion, the WE300 will automatically create all variables and Modbus commands (beside the network, if not already available) in order to allow the communication with the XP500. The variables name can be then later on modified from todo_link_variables.

3.7 Manage Modbus errors

WE300 allows to manage the modbus errors on the page Administration → Modbus → Errors handling, clicking on new.

At the occurence of a modbus error it’s possible to set a variable at a specific value:

• Network: the network where the error occurs
• Slave ID (address): the slave address to be monitored ( this field appears only in case of master networks)
• Timeout (seconds): the error is displayed only if available for more than X seconds
• Variable: the variable to be set. Selecting None, it’s possible to avoid the setting of any variable
• Value: the value, that the variable should assume at the occurence of the error

Clicking on Save the error handling is configured and starts monitoring the errors that may occur on the selected network.

4.1. Events

The events allow the WE300 to acknowledge when a monitored parameter reaches a relevant threshold for the user.

Different types of events are available and each type of event is composed of several parameters, in order to reach a high flexibility in controlling and monitoring the system.

WE300 allows to create 10 different events.

To create an event, enter the page Administration/Events/Actions and click on New.

The tab Delete allows to cancel one or more selected events. With the tab Update it’s possible to edit the enabling/disabling of one or more events, to configure events as alarms and send them to a web portal. For a quick search by name of one or more events the Tab Find can be used.

All occurred events can be displayed in a chronological chart, entering the page Status → Logger status → Events.

From this page it’s possible to display one or more events, by selecting them, and the time interval to be considered, from the relevant list, and possibly export data on CSV or Excel format.

During the creation of an event, and after entering the name, must be selected the type of event among Variable, Incoming data or Scheduler (see 5. Scheduler).

Some generic options can be activated according to the selected type of event: it’s possible to decide the enabling of the event from Status, the visualization as an alarm on the field Set as alarm and to send it to a web portal from the field Send to portal.

4.1.1. Event on variable

Event on variable refers to an event that occurs when a variable reaches a defined value or a defined status.

First of all a variable in the field variable has to be selected.

In the drop-down menu is possible to see all previously created variables and select the one to be associated to an event.

The second parameter to be selected is the Condition, among the following possibilities: EQUAL, NOT EQUAL, GREATER THAN, GREATER OR EQUAL THAN, LESS THAN and LESS OR EQUAL THAN.

It’s now necessary to set the threshold value for the event triggering, i.e. a numeric value will be entered in the field Value, according to the type of the selected variable.

It’s possible to set a value in the field Delay. The value is expressed in second, the function of this parameter is to postpone the triggering of the event for a defined time.

Finally it’s also possible to enable the field Skip first event, that allows the WE500 to ignore the first time that an event occurs.

This can be useful, for instance, in case of an analogue variable (with an ever changing value, having a floating mode). Setting a delay it’s possible to avoid the triggering of any event, before the value has come to a stabilized value. If the delay has been for example set at 10 seconds, the value entered in the relevant field will be kept until the expiry of the 10 seconds, allowing the execution of any possible events.

Once set all parameters, the situation may be the following:

Variable: Var1

Condition: EQUAL

Value: 3

Delay:10

According to this configuration the event would be triggered 10 seconds after the variable Var1 has reached the value 3.

4.1.2. Incoming data

The incoming data are the events coming from external factors. Selecting Ring on Data source there will be the possibility of choosing one or more of the registered users.

The event will occur, when the WE300 receives a ring from one of the authorized users. At ring receipt, the WE300 will disconnect the call, avoiding any costs.

It’s recommended to disable all mailbox or call waiting functions of the SIM installed in the device. For each user is possible to define only a single Ring event.

4.2.1. Send Email

Selecting Send Email, it’s allowed to enter the text to be sent at the occurrence of the event.

If previously used messages are available it’s possible to select them from the field Message, using the drop-down menu.

For entering a new text, select Create new message.

Once the message is defined, it’s possible to select the receivers among the several available users and groups.

After definition of the event and action that generate the email to be sent to a defined user, some more conditions are necessary:

• Availability of a LAN or GPRS/HSPA connection (see section 10.1. Connectivity and 12.3. Ping)
• The configured user/s should be enabled to receive notifications emails at a valid email address ( see 9. Users)
• The mail service must be properly configured (see 10.1.6. Email)

All the text used for the existing actions are available on the page Administration/Event/Actions/Messages. From this page is possible to cancel any message, by clicking on the relevant tab and then Delete, or edit one or more messages by clicking upon it.

4.2.2. Send SMS

Selecting Send SMS it’s possible to enter the text to be sent at the occurrence of a defined event.

If previously used messages are available it’s possible to select them from the field Message, using the drop-down menu.

For entering a new text, select Create new message.

Once the message is defined, it’s possible to select the receivers among the several available users and groups.

After definition of the event and action that generate the SMS to be sent to a defined user, some more conditions are necessary:

Network Availability The configured user/s should be enabled to receive SMS at a valid telephone number ( see section 9.1. How to create a new user) The SMS service must be properly configured (see section 10.1.4. SMS)

All the text used for the existing actions are available on the page Administration/Event/Actions/Messages. From this page is possible to cancel any messages, by clicking on Delete, or edit one or more messages by clicking upon it.

4.2.3. Execute command

Selecting Execute a Command in the field Type is possible to choose a variable among those available in the list below and then specify a value in the filed To.

Thus, at the occurrence of the defined event, the selected variable will be set at the value entered in the field To.

The drop-down menu could miss some of the already created variables. The reason is that the system automatically recognizes the variables, where the value can be modified:

• DO Varaiables
• Modbus write variables
• Modbus write/read variables

For the same reason the following variables will never be included in the menu: * DI variables * AI variables * Modbus read variables

Through an action of Execute a Command, it’s possible to create some automatic operations at the occurrence of a certain event, as for example to close the contact of an output if an analogue input reaches a defined threshold.

4.2.4. Ring a user action

Selecting Ring a user in the field Type it’s possible to choose one or more users/groups of users, that WE300 will send a voice call in case the associated event occurs.

If no feedback will be received, the WE300 will stop the call automatically after 30seconds, and then pass to the following user/s in the list.

If the user rejects the call, the WE300 will immediately pass to the following user. Likewise, if a user should answer, the WE300 will pass to the following user in the list immediately after the termination of the call.

4.2.5. Reboot action

Selecting Reboot in the field Type, it’s possible to reboot the WE300 at the occurrence of the associated event.

4.2.6. Power off action

Selecting Poweroff in the field Type, the WE300 can be turned off at the occurrence of the associated event

A typical situation where the controlled power-off of the device can be useful, is when the WE300 is battery powered ( for example using a UPS500).

When the battery is low, this could send a request of controlled power-off to the WE300 (through a digital/analogue input), in order to avoid unexpected current interruptions while the system is working.

6.2.1. Set

The variables that can be modified in their value through the SET command are the following: counters on digital inputs, digital outputs, Modbus write variables and read/write.

The SET command can be used both through SMS and Email. In both cases it’s necessary to define the parameters of the users, authorized to send commands to a WE300 (telephone number for the SMS, email address for the email). For authorizing the users to send command, it’s necessary to enable the relevant functions on the user configuration page. Also the SMS and/or the Email service (in this last case the incoming email service will be enough) must be enabled.

Once appropriately configured the WE300, it’s possible to use the following syntax:

Set Variable Name=Value

Assuming for example,that the variable “Var1” has to be set with value “5”, the SMS to be sent will be the following:

Set Var1=5

If the command will be sent by Email, the same syntax, as in the above example, has to be reported on the Email’s object. If more than one variables value have to be set, it’s enough to separate each command with a space:

Set Var1=5 Var2=10 Var3=15

When writing the commands it’s important to respect the correct spelling of the variables name.

6.2.2. Get

All variables can be read, with the only exception of the Modbus write-only variables.

The GET command can be used both through SMS and Email. In both cases it’s necessary to define the parameters of the users, authorized to send commands to a WE300 (telephone number for the SMS, email address for the email). For authorizing the users to send commands, it’s necessary to enable the relevant functions on the user configuration page. Also the SMS and/or the Email service (both incoming and outgoing) must be enabled.

Once appropriately configured the WE300, it’s possible to use the following syntax:

Get Variable Name Value

Assuming for example, that the value of the variable “Var1” has to be interrogated, the SMS to be sent will be the following:

Get Var1

If the command will be executed by Email, the same syntax, as in the above example, has to be reported on the Email’s object. If more than one variables value have to be interrogated, it’s enough to separate each command with a space:

Get Var1 Var2 Var3

When writing the commands it’s important to respect the correct spelling of the variables name.

7.2.1. Server

From the Tab Server is possible to activate the data sending to the Nethix Portal or to any other remote server.

Selecting Nethix API from the Protocol field and flagging Enable, the data sending to the portal nethix.co will be activated.

The portal service offered by Nethix allows:

• To send data and to display an overview of all installed devices
• To display the detailed data of every single device and all the records of the sent data in a chart or tab
• To create a synoptic that displays in a simpler and more intuitive way the status of the device.
• To allow a remote access from the device to the portal, in order to read/write the variables value, even if a public IP is not available.
• To establish a VPN connection between a PC and a portal. Activating the remote access, it will be possible to create a private VPN with all the owned devices, avoiding all possible difficulties referred to the non accessible IP addresses.

For further information, contact Nethix Support.

Default Settings are:

• Server address: https://nethix.co
• Server port: 443

The updated parameters will be indicated by Nethix when the service will be activated.

In alternative it’s possible to enable the data sending to an external server. For this it’s enough to choose the option HTTP on the field Protocol.

In the General Setup the following parameters must be defined:

• Enable: enable/disable the sending
• User agent: it’s the user agent that WE300 will use for authenticating in the server
• Device ID: ID of the device (this can be used for managing more than one device inside the same server)
• Server address: server address (complete with http://) where to send the data
• Server port: Port of the server
• Send mode: mode of the sending. It’s possible to choose among POST and GET. Before activating the option, please ask Nethix Support to have an example string sent by WE300.

In Data Delivery is possible to define the path inside the server, where the processing script of the received data is available

• Script address: name and complete path of the script inside the remote server

In IP Delivery it’s possible to specify the path, where to find the script , that will manage the sending of the IP address by the WE300. It’s enough to fill in the field Script Address.

7.2.2. Email report

From the tab Email report it’s possible to configure the sending, of the data collected by WE300, to one or more email address.

• Enable: Enable/disable the sending
• Delivery time: Defines the frequency of the data sending. Delivery and sampling time (field Sampling frequency on tab General) can be different. For example it is possible to sample a variable every minute and to send data once in a day.

For a correct sending of the report, the E-mail account associated to the WE300, 10.1.6. Email), should be properly configured and the option Receive report by email should be enabled in a proper configuration of the users (9. Users).

10.1.1. LAN connection

On the page Administration → Networking → LAN it’s possible to modify all parameters of the RJ45 Interface.

First of all the MAC address of the device will be displayed, with the option of using the LAN network on static IP address or on DHCP.

If the Static address will be selected, the following parameters must be set for the correct operation of the service:

• IP address static IP address assigned to the WE300. Make sure that the address is available and not used on other devices.
• Netmask Subnet mask. A valid netmask must be entered, according to the specifications of the own local LAN.
• Gateway Network gateway
• DNS DNS that can be assigned to the WE300 ( max. 3)

After settings modification the WE300 requires a reboot in order to activate them. If the entered parameters are correct, it’s possible to enter the web interface of the WE300 (even remotely if the network allows it), to send emails and send data to a Portal/Server.

For further information regarding the status of the LAN connection, see page Diagnostics → Networking on section LAN Interface ( see 12. Diagnostic)

10.1.2. SIM parameters

Beside the parameters related to the connectivity, for the correct operating of the SMS and RING services, it could be necessary to define some SIM’s parameters according to the selected provider.

Those parameters are available on page Administration → Networking → SIM.

• APN: It’s the name of the access point of the GPRS/HSPA network. It changes according to the provider and to the contract with it (in some cases this may be not necessary). It’s an important parameter for a proper functioning of the connection. In case this should not be known, please contact the provider or Nethix Support.
• Username: it’s the username for the GPRS/HSPA connection. This field is normally blank, if it’s not differently required by the provider.
• Password: Password to be used for the GPRS/HSPA connection. This field is normally blank, if it’s not differently required by the provider.
• SIM number: It’s the Telephone number of the SIM inserted in the WE300. This is not relevant for the functioning (this number is never used by the WE300), but can be used for identifying the device later on.
• SMS center: It’s the SMS Service Centre of the Provider. With some types of SIM this could not be required. If this number is not known, please contact the Provider or Nethix Support.

10.1.3. GPRS connection

WE300 allows to establish a GPRS connection in order to enter the web interface of the device and send data or emails, even if no Ethernet connection is available.

In order to activate the connection enter the page Administration → Networking → GPRS.

Once enabled the service with a flag on the field Enable, it’s required to specify whether the connection must be always on or on demand.

• On demand: the connection is activated on request by an authorized user through a wake-up message (11. Commands) and after 15 minutes is automatically disabled. If the activated services require a connection for data sending or email sending.., the connection of the WE300 will automatically be closed at the end of the configured operations.

If the parameters have been properly configured, after a few minutes the GPRS connection will be activated. On the status panel, positioned on the right side of the web interface, the GPRS indicator will become green and beneath it the connection uptime and the relevant IP address will be displayed.

The WE300 offers also the possibility of associating the connection with a dynamic DNS service, choosing from the List of Providers available on section Dynamic DNS. This service allows to access the WE300 even if no static IP is available, since the device will be identified by the selected provider at every single connection, allowing the users to reach the web interface, just entering the hostname as configured on the browser. For further information see the Provider’s site or contact Nethix Support.

Make sure that the GPRS connection has been successfully established, by checking if all necessary operations have been executed:

• Provide the WE300 with an enabled data SIM card (rechargeable or with flat tariff contract)
• Enter the APN (10.1.2. SIM parameters) for the Providers, that require it.
• Connect the antenna and check the strength of the available GSM signal.
• Enable the GPRS service.

It’s possible to check the quality of the connection by using the diagnostic tool Ping (12.3. Ping). Further information regarding the status of the connection can be found on page Administration → Diagnostics → Networking (12.2. Information of connectivity)

10.1.4. SMS

To enable/disable the SMS service go to page Administration → Networking → SMS. Beside the flag for enabling the service, it’s possible to enable or disable the sending of pre-set SMS notifications (4. Events/Actions).

Enabling the service, it should be necessary to enter the SMS Service Centre number (10.1.2. SIM parameters).

Once enabled the SMS service, it’s possible to test the functioning through the section SMS test: entering a valid telephone number, complete with country code (for example +39NNNNNNNNNN for Italy), the WE300 will try to send an SMS with the following text ” Test message from WE300 “.

For granting the proper functioning of the SMS service, allowing the users to communicate with the WE300 and the WE300 to send alarm notifications, the procedure below must be carefully carried out:

• Enter the SMS Service Centre (10.1.2. SIM parameters).
• Enable the SMS service as described before
• Enable the SMS sending on event (field Send events on Administration → Networking → SMS)
• Define at least one user with activated SMS sending/receiving functions (9. Users)
• Create one or more events as Send SMS action (se 4. Events/Actions).
• Make sure that the SIM is properly inserted and with enough credit.
• Make sure that the antenna is properly connected and that the available signal is strong enough.

All sent and received SMS can be displayed on page Status → Services → SMS: the first page to be entered will show the SMS received by the device.

In the table the following information will be available:

• Number: shows the Phone number of the SMS sender
• Reception date: displays the date and time when the WE300 has received the message
• Text: contains the text of the received message

The button Refresh can be clicked at any time in order to update all information; Empty box for deleting all messages stored on Inbox.

Clicking on the drop-down menu on the top of the table, it’s possible to pass from Inbox to Outbox.

On this table is possible to display all the messages not yet delivered by the WE300. The available information are the following:

• Number: refers to the phone number of the message receiver
• Creation date: shows the date and time when the message has been created
• Text: displays the text of the message

The button Refresh can be clicked at any time in order to update all information; Empty box for deleting all messages available on Outbox (such messages won’t be delivered).

Clicking on the drop-down menu on the top of the table, it’s possible to pass from Outbox to Sent.

On this table are displayed some information regarding the SMS already delivered by the WE300:

• Number: shows the receiver of the delivered messages
• Send date: displays the date and time when the WE300 has delivered the message
• Text: contains the text of the sent messages

The button Refresh can be clicked at any time in order to update all information; Empty box for deleting all messages stored on Sent.

10.1.5. Ring

One of the actions that can be associated to an event (incoming or outgoing) is the RING, that can be sent or received to/by one or more registered users (4. Events/Actions).

To enable the Ring Function go to page Administration → Networking → Ring and enable the field Enable rings.

Once enabled the function and clicked on Save, it’s possible to use this option.

To make sure that this function is properly operating, it’s recommended to check the following points:

• Enable the Ring function, as described above.
• Define at least one user with valid telephone number, enabled to receive/send rings (see 9. Users)
• Make sure that the SIM card is properly inserted and voice call enabled.
• Make sure that the SIM card has enough credit to send rings.
• Make sure that the GSM antenna is properly assembled and that the signal is strong enough

10.1.6. Email

Before proceeding with the configuration of the WE300, it’s necessary to make the following:

• After the selection of the provider (Gmail, Yahoo, Hotmail etc..) enter the provider’s site and create a new valid mail account
• In the site of the provider, collect all information regarding the parameters to be entered in order to configure the mail service

Once a new account has been created, it’s possible to proceed with the configuration of the WE300, enabling the outgoing emails, the incoming emails or both of them from the page Administration → Networking → Email.

On the section Outgoing mail setup the parameters required for the email sending from the WE300 must be set:

• Enable outgoing mail service it enables/disables the email sending service.
• Server type it allows to choose the type of mail server (at the moment only SMTP available)
• Server address it’s the address of the mail server ( for example smtp.gmail.com)
• Port it’s the number of the access port (for example 587)
• Email address the email address associated to the WE300. This will be the address visualized by the receivers of the emails.
• Username It’s the username of the mail account associated to the WE300.
• Password It’s the password of the mail account associated to the WE300.
• SSL-TLS Encryption

Once clicked on the button Save, a new section, called Outgoing mail test, will appear on the bottom of the page: from this section it’s possible to send a test email to any address.

A properly configured mail service allows the WE300 to send notification mails to the configured users (see 4.2.1. Send Email)or to send scheduled reports (see 7.2.2. Email report).

On the section Incoming mail setup the parameters required for the email sending from the WE300 must be set:

• Enable incoming mail service: Enables/disables the email receiving service.
• Server Type: Type of mail server (at the moment only POP available)
• Server address: the address of the mail server (for example pop.gmail.com)
• Port: Number of the access port (for example 995)
• Email address: the email address associated to the WE300. The commands sent by the authorized users should be sent to this address.
• Username: It’s the username of the mail account associated to the WE300.
• Password: It’s he password of the mail account associated to the WE300.
• SSL-TLS: Encryption

A properly configured mail service allows the authorized users to send commands to the WE300 (see 6.2. Set/Get via SMS/Email commands and 11. Commands)

All sent and received emails can be visualized on the page Status → Services → Email.

The first page shows the emails received by the device:

On the displayed table the following information are available:

• Mail address: the mail address of the sender
• Reception date: Date and time when the WE300 received the email.
• Text: text of the received email.

At any time it’s possible to click on the button Refresh in order to update the information, or Empty box, in order to delete all messages available inside Inbox.

Clicking on the drop-down menu on top of the table, it’s possible to pass from Inbox to Outbox.

On this table it’s possible to visualize all the emails not yet delivered by the WE300. The following information will be shown:

• Mail address: in this filed is shown the address of the receiver of the mail.
• Creation date: It’s the date and time of the mail creation
• Attempts: it shows the sending attempts made by WE300
• Text: it displays the text of the mail

At any time it’s possible to click on the button Refresh in order to update the information, or Empty box, in order to delete all messages available inside Outbox ( deleted mails won’t be sent out)

Clicking on the drop-down menu on top of the table, it’s possible to pass from Outbox to Sent. On this table are displayed some information referred to the email already sent by the WE300:

• Mail address: in this filed is shown the address of the receiver of the mail.
• Creation date: It’s the date and time of the mail delivery
• Attempts: it shows the sending attempts made by WE300 before the successful delivery
• Text: it displays the text of the sent mail

At any time it’s possible to click on the button Refresh in order to update the information, or Empty box, in order to delete all messages available inside Sent.

10.2.1. Information about the system

On the page Administration → General Setup → System, under the section System, it’s possible to configure the contents to be displayed on the page Status → Site immediately after the login. These parameters are not compulsory and are used just to identify the device.

• Site name: the name assigned to the device
• Site id: numeric ID assigned to the device
• Country: Country where the device is installed
• Region: Region/Area where the device is installed
• Picture: when this option is enabled, it’s possible to select an image, by clicking on Select file, and then display the selected image after the login (for example the picture of the installation, of the company..and so on..). The picture will be displayed on the page Status -> Site.

10.2.2. Date and time

On the page Administration → General Setup → System**under the section **Time/Date, it’s possible to set the date and time of the device:

• Installation time/date: It states the date and time, when the device has been installed. This information has no influence on the functioning and has the only reason of identifying the installation.
• Set time/date: It allows to set the date and time of the device.
• Enable NTP: it enables the automatic synchronization of time. Once per day and at every reboot, the WE300 will connect to the server in order to update date and time precisely, according to the relevant timezone.
• Select time-zone: it allows to set the timezone of the device.

It is also possible to specify a custom NTP server, by clicking the Advanced link.

10.2.3. Web interface personalization

Some graphical personalizations of the web interface of the device are possible from page Administration → General Setup → Web Interface, and will be valid for all the users.

• Logo: this allows to choose an image to replace the Nethix logo on the left top of the page.
• Prevalent color: Primary color of the page. (RGB hexadecimal color, for example: #007BC5)
• Secondary color: Secondary color of the page. (RGB Hexadecimal color, for example #009FE9)
• Font color: Color of the text. (RGB Hexadecimal color, for example #007BC5)
• White icons: Disabling this option, all the icons of the header (power-off, reboot, logout) will be displayed in black.
• Background color: Color of page’s background .(RGB Hexadecimal color for example #007BC5 )
• Footer: it allows to configure the footer at convenience (HTML code is allowed)

Clicking on all coloured fields, a “color picker” will allow to select the desired color and automatically insert the relevant hexadecimal value.