Equipment configuration

This article explains how to program a BACnet scheduler with the Wattsense Console.

Some BACnet equipments have schedulers. It is now possible to program them directly from the Wattsense console. The scheduler is stored in the BACnet device (not embedded in the Box) and allows specific values to be sent to other BACnet equipments according to a defined schedule map.

Case study :

- 3 BACnet devices are connected on a network. Equipment 3 holds a scheduler property which will be linked to 2 properties (targets) from the 2 other equipments.

Note that the scheduler is based on the reference time of the master BACnet device (Equipment 3 in our example).

Bacnet properties info for example:
Object instance : 1 // PropertyId : 88 // Object Type : 17

How to proceed ?

First of all, use the Bacnet Scan in order to scan the network and get these properties.
Then in the Wattsense Console (Live data Tab), click on the modification button of the BACnet schedule property :

The scheduler configuration is splitted into 3 Tabs :

• Target
• General Settings
• Schedule

These 3 tabs are by default pre-populated with the scheduler configuration stored on the device. These informations were retrieved during the scan.
(In our example, the target property = objectInstance:1-objectType:17-propertyId:88).

Targets

To add a new target property (Several properties can be added), just click in the field “properties targeted by the scheduler”
This targets properties would be monitored by the Bacnet Scheduler.

Then select the properties from the list (only BACnet items will be displayed because they will be monitored by a BACnet device).

Properties are grouped by equipments. It may happen that a group named “Not In configuration” appears in this list.

In this case, It means that the scheduler is already programmed and the target device / property is not known in the Wattsense application (missing BACnet scan or property not imported)

General Settings

The General Settings allow you configure the priority, the object type, the default value and the effective period :

	Priority level : (from 1 to 16) sets by the programmer to prioritize the command controls.
	Object type : (unsigned / real / enumated).

Schedule:

In this page you would be able to program your scheduler.

You can associate specific values with time slots and specify how the scheduler behaves troughout the week. The programming table of one day can be duplicated for the other days of the week.

Send the scheduler to the BACnet device

Click on the Save button to validate the modifications. You will have the message :

If you need any additional information, please contact us here.

This article is a tutorial for installing and setting up an Eastron SDM230/SDM630mct - LoRaWAN energy metering to your Wattsense product. This equipment is communicating through LoRaWAN. You can learn more about our LoRaWAN architecture in this article.

You can find attached the Eastron's datasheets for your information. Most of the informations in the current article are sourced from it.

Eastron side

Please follow the installation guide to set-up your equipment correctly. From chapter 4.3: Setting 2, you will start the LoRaWAN configuration. Note the DevEUI, the AppEUI and the AppKey of your equipment. You will need those informations later. Be sure your equipment is set in OTAA join-mode and not ABP.

Example:

DevEUI:8680000130268676
AppEUI:8680000230268676
AppKey:0B11EB267EC70FBEDCC85C1379C2D74A

I will be using an Eastron SDM630mct for the examples of this article. The principle is the same with the SDM230.

Wattsense side

You can now add your equipment to your Wattsense Tower/Bridge from the console.

Go to Configuration > Equipment tab and add an equipment from the Configuration Wizard.

Select your Eastron equipment in the list and choose LoRaWAN protocol. You can now enter your credentials from earlier.

You can enter 0 in the two additionnal parameters Active parameters configuration downlink and Active parameters per batch. We will come back to it later.

Set up your device as a Class C type.

On the properties selection page, you can select the points you want to monitor. In addition, you have to enable the Encoded downlink message and Raw encoded payload properties.

Save your configuration and push it to your box.

Check on the sensor if the JOIN procedure succeeded. If not, verify if the DevEUI, AppEUI and AppKey are matching. You can force a re-JOIN attempt directly on the sensor (chapter 4.3.3 of the user guide)

Enable the properties on the Eastron

An Eastron LoRaWAN equipment is expecting some commands in order to push the correct properties to the Wattsense. Those commands are sent from the Encoded downlink message property on the console.

To learn more about downlink commands from the Wattsense console, you can follow this tutorial.

Every commands informations are explained in Eastron's user guides and datasheets. We sum up the different steps to make it easier for the customer.

I. Authentication

First the equipment requires an authentication with a password. Three different downlinks are expected for that first step. Send them successively:

010300180002440C:1
01100018000204447A0000C62C:1
0103000E0002A5C8:1

 

II. Batch size

The next downlink is to define the number of parameters to send per batch (range 3~8). If the number of measured properties is higher than the batch size, the equipment will send them in multiple payloads.

Example: [Batch size = 5  |  active properties = 12]  --> The sensor will send 3 different payloads to communicate every properties.

0110FE1200010200057AEE:1

This part depends on the Batch Size you want. Here Batch Size = 5
The CheckSum (CRC) can be calculated using this website. Here CRC = 7AEE

 

III. Active parameters

Finally, the last downlink to send is the definition of the parameters. Every HEX registers for each parameters are defined in the Lorawan Table datasheet from Eastron. In the following example, I am requesting for Total active power, Total current and L1/L2/L3 voltage.

0110FE02000F1E0A13000102FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFAC83:1

0A -> Total Current
13 -> Total Active Power
00 -> L1 volt
01 -> L2 volt
02 -> L3 volt
FF(25x) -> Empty
2B 7A: CRC (needs to be calculated as in the previous step)

The definition of the parameters must be 30 bytes long. Add FF for the empty parameters.

 

You should get a sucess response payload in the Raw encoded payload property when a downlink is received by the sensor. It usually takes the form 0110FE1200019024:1

 

If one of the downlinks could not be processed, you should get an error response payload: 0190018DC0:1 . You should try again and verify the CRC and the format of the downlink.

 

Finish the codec configuration

Now that the sensor is correctly set-up, we can finally synchronize the Wattsense codec with the enabled parameters.

Go back to your sensor's configuration and complete the two remaining fields with the informations sent to the sensor in the previous part (II. and III.)

Save and push the changes to the box. You should be able to read the properties you selected.

For more informations, you can check some configuration examples attached to this article. You can also refer to Eastron documentation for more details.

If you need any additional information, please contact us here.

This article is a tutorial for installing and setting up a SIEMENS Synco controller to your Wattsense product. This equipment is using the KNX communication protocol. You can learn more about the KNX protocol configuration in this tutorial.

You can find attached the Synco RMK770 datasheet for your information. Most of the informations in the current article are sourced in it.

Synco side

In order to correctly set up your equipment to the Wattsense Box, you will need to get a few informations from the Synco.

• Installation

If you don't know the communication settings of your equipment, you can connect one of these HMI to access the internal settings.

The Synco should be powered with a AC - 24V supply. Here is how your installation should look like:

• Communication informations

Before connecting your Synco to the Wattsense Box, you will require the Area, the Line and the Device address of your equipment. In most of cases, you can find it just by turning the navigation button a few times. You should be able to see the Dev addr. information in the format Area.Line.DevAdr.

• • (0.2.50 in the current set-up)

If you can not see these informations, you can click on both Esc and Ok buttons. Then go to Service level > Device information > Communication > Basic settings. You'll be able to see your device's informations from here :

• Wired Connections

The KNX bus needs to be connected to the Wattsense Box KNX port as follows :

• CE -   -->    -  port
• CE +  -->   +  port

Wattsense side

You can now add your RVL to your Wattsense Box from the console.

Go to Configuration / Equipment tab and add an equipment from the library :

Select your Synco equipment in the list and choose KNX protocol. You can now enter your Device address in the format Area.Line.DevAdr. 

• (0.2.50 in our case):

Click on Next, and define the Internal and Individual address of the Wattsense Box. The addresses must be unique and available in the network.

Finally you can select the wanted properties you want to monitor.

If you need any additional information, please contact us here.

This article is a tutorial for installing and setting up a SIEMENS RVL Heating controller to your Wattsense product. This equipment is using the LPB communication protocol. You can learn more about the LPB protocol configuration in this tutorial.

You can find attached the RVL470 datasheet for your information. Most of the informations in the current article are sourced from it.

RVL side

In order to correctly set up your equipment to the Wattsense Tower/Bridge, you will need to get a few informations from the RVL.

• Heating engineer's level

Press   and  simultaneously for 3 seconds to activate the "Heating engineer's" level. It will allow you to access the RVL internal configuration.

• Segment number | Device number

Before connecting your RVL to the Wattsense Tower/Bridge, you will require the Segment Number and the Device Number of your equipment. You can find it from the Heating Engineer's level, usually at the setting numbers 169 and 170. You can navigate in the settings with the Prog buttons. In the following set-up:

• • (169) Device Number: 2
  • (170) Segment Number : 2

The parameters numbers are specified in the RVL's datasheet. For each device, configure a unique device number (from 0 to 16).

• Powered Bus

Be careful to have the communication bus powered. You can see the "Bus" word displayed if it is powered. If not, go to the setting number 179 (or else depending on the datasheet) and enable the Bus with the - and + buttons.

If you connect multiple LPB equipments together, Designate one and only one equipment that supplies the Bus.

• Wired Connections

To access the communication connectors or the RVL, you need to remove the white part. You can unscrew it from its front side.

Once you remove it, you can access the MB and DB communication ports. You need to connect it to the Wattsense Tower/Bridge X-Bus as follow:

• • MB  -->  - port
  • DB  -->   +  port

Be sure that the LPB bus is not powered during your installation to avoid electrical issues. After your installation is completed remember to power it.

Wattsense side

You can now add your RVL to your Wattsense Tower/Bridge from the console.

Go to Configuration > Equipment tab and add an equipment from the decoded equipment library :

Select your RVL equipment in the list and choose LPB protocol. You can now enter your Segment number and Device number from earlier.

Finally you can select the wanted properties you want to monitor.

If you need any additional information, please contact us here.

Installation Information

Be sure that your Tower/Bridge is connected to the network with twisted pair communication cables. Be sure that you know the Modbus RTU register table of the device if you are using one that is not in our compatibility checker.

Step 1

If your equipment is not listed in the library, this does not mean that the Box cannot connect to it, but only that you will have to configure it manually.
Please feel free to send us your missing equipment and we will add it to our library for you.

Choose the physical connector on the Box (RS485-1 or RS485-2). Indicate the mandatory parameters (Speed, Parity, Data Bits and Stop Bits). They must be identical on all devices that are on the same connector (Box and equipment).

Step 4

1. Add the Box correctly in the KNX network
2. Collect the required equipment information in order to read data.

To correctly add the Box in the KNX LTE network you'll have to assign a free and unique individual address and internal address (required by wattsense software design) :

Example: 0.2.13 and 0.2.14

 

 

Architecture example:

Equipment Configuration

1. Select an equipment in our database. If it's not available, please contact us: support.wattsense.com

2.To complete the example above (Box Address = 0.2.13 / 0.2.14). the device address is 0.2.50.

 

Properties

This article explains how to make a bulk creation for LoRaWAN equipment.

You can now add multiple LoRaWAN types of equipment at once. This feature is only available on the web console. To add a list of equiments, access the bulk creation mode by going through these steps :

Prepare a csv file

First of all, you have to prepare a text file which contains the whole listing of you LoRaWAN sensors. You can first download the WATTSENSE_TEMPLATE.CSV file (file available for download at the end of this article).

Edit this file with a text editor or a spreadsheet editor. Don’t remove the first header line, and fill the file with your data.

For example :

In this example, we will add 8 sensors, which will be divided into two groups MyGroupA and MyGroupB. In order to complete the file you must meet a few prerequisites :

• Manufacturer
• Model
• DevEUI
• AppEUI
• AppKey

Please note that the csv file should respect the format of the template : First header line with imposed field names UTF-8 encoding format comma (,) delimiter

If you are working with a spreadsheet application, save the file as csv with comma delimiter.

Manufacturer and model name in the csv file

In order to successfully import, you must retrieve the manufacturer and model name of your sensor from the wattsense database. If you want to know the exact "names" that you need to put in the csv file, you can simulate adding of a sensor in the Wattsense Console / Configuration / Add Equipment / Pick a decoded equipment.

the manufacturer field of the csv is the first part of the Equipment name (before the first "-") -> nexelec

the model field of the csv is the last part of the Equipment name -> atmo 

On this second example :

manufacturer = Adeunis

model = ARF8230FA - Pulse ATEX

Here's the csv file example with the two sensors above (Nexelec atmo and Adeunis ARF8230FA - Pulse ATEX) :

Import a csv file in the Wattsense Console

Once the csv file is completed, it can be imported in the Wattsense Console.

From the configuration Tab, click on the “Add equipment” button.

Then choose the LoRaWAN bulk creation section.

The next screen allows you to import the csv file :

Select your file in the file explorer :

The preview of the file contents is displayed :

Click on "Next" and select the codec you want to use. Your device names will be scanned and matched with their Wattsense counterparts.

If the pair (manufacturer + model) is knowned is our database, the matching codec is automatically associated.

If it is not the case, you’ll have to select a codec in the list.

If the needed codec is not present in the list, please do ask us to add it (here).

Then click on the “create equipment” button.

To finish, select the properties that you want to synchronize with the Box.

On this page you can edit and change the name of the properties as well as the unit (just click on the fileld).

And save :

The new equipments are imported and displayed in the console interface. Note that the sensors are grouped by group name, as specified in the csv file.

if the field name in console (let empty to use manufacturer & name) in the Csv file is empty, the Equipment name in the wattsense console is manufacturer and model :

To finish, select the properties that you want to synchronize with the Box.

And… that’s it! You can now add in one go multiple devices with their data points.

Direct access to advanced configuration on the bulk importation page

Some Lorawan sensors are programmable via an application from the manufacturer. In this case, the generic Lorawan codec must be supplemented by the description of the programming table in order to retrieve the correct data in the Wattsense Console.
Here’s an example with a programmable LoRaWAN sensor connected to a measurement device.

Another use case is the capability of some lorawan sensors to log data over time. In this case, the configuration file indicates the measurement periods.

Direct access to these advanced configuration files has been implemented to improve the process of adding LoRaWAN sensors (gear button on the right side of the list)

Examples with and Adeunis Modbus sensor :
All the codec fields are displayed. Click on choose a file to import a configuration file provided by the manufacturer.

And select the configuration file of the sensor in the file explorer :

The codec fieds will automatically be filled with the right encryption mode.

Where to find the configuration files ?

They are available through the manufacturer's application of the LoRaWAN sensor via USB or NFC for mobile devices for example via the export function.

We built this new feature with your feedback. Please drop us a line at Wattsense Support to make it even better or to share with us any other feedback.

Installation Information

Step 1

 

Equipment information If your device is not in the Configuration Wizard list, it does not mean that the box can't connect to it but only that you will have to do the setup manually. Feel free to send us your missing equipment and we will add it for you to our library.

Step 2

• IP Address (two devices can't be assigned to the same IP address)
• Port
• Slave ID (has to be unique on a network)