Software

1) Open HWg-PDMS or HWg-Trigger. In this case, the HWg-PDMS is used as an example; however, the same steps apply to HWg-Trigger, too.

2) Click Help – Registration.

3) The registration form opens. Click Next to continue.

4) A new form appears, showing all the data kept with your license. Check the Only Save to Activation File box and click Commit.

5) Select a location for saving the .txt file.

6) As the last step, a window appears, confirming that the file has been saved.

HW group customers can use the SensDesk Technology online portal to remotely monitor their devices. The online portal was originally designed for remote monitoring of sensor readings (temperature, humidity, ...) and to detect device communication failures. Due to popular demand, we added the possibility to control DO (Digital Outputs) of the devices from the portal Web interface.

SensDesk can be used to control the DO of

• Poseidon2 (3268, 3468, 4002)
• Damocles2 (MINI, 1208, 2404)
• Ares 12/14 (with an optional relay output module)
• Ares 12 LTE (with an optional relay output module)
• SD-2xOutput

That is, all HW group devices that feature digital outputs (DO) and are SensDesk-enabled.

Relay output reaction time

All products connected to the SensDesk portal communicate at least once every 15 minutes. This saves network traffic (and money in case of GSM communication) but means that a relay output needs 0.1 to 15 minutes to react. That's far from convenient, and so we have introduced the CheckPeriod setting (CheckPush function) that can be activated from the SensDesk portal for any product with digital outputs.

The CheckPeriod function shortens the reaction time, in which the relay output at the remote device switches, to 0.1 to 60 seconds.

What outputs can be controlled

Digital (DO) outputs of Poseidon2 or Damocles2 units can be linked to a local condition. An output can be controlled by the “Thermostat” local function (e.g. to turn on a fan when the temperature exceeds 30°C). Such a DO cannot be controlled remotely (remains read-only).

Only outputs in the “Manual” mode (with no conditions or triggers) can be controlled from the SensDesk portal.

Controlling digital (relay) outputs from SensDesk

Outputs can be controlled from SensDesk at the corresponding output page, device page or outputs overview page.:

If the switch is moved to one side or the other, SensDesk instructs the output to be set accordingly:

Depending on the device settings, this instruction is executed within the standard Push period (15 minutes), or in the shortened period (60s). Before the instruction is executed, the output state can be changed again, or the change canceled. The device page does not refresh automatically; it must be refreshed manually. After the instruction is executed, the switch returns to the final position.

If you wish to leave an output unchanged, leave the switch in the neutral position. This avoids unnecessary communication between the device and the portal.

CheckPeriod: Shortened output reaction time

In order to shorten the time it takes for the outputs of a device to react to SensDesk requests, the CheckPush function was introduced. It is activated with the CheckPeriod option that is set to 60s. This faster communication mode is configured in SensDesk individually for each device. CheckPeriod only applies to outputs. It does not shorten the update period for sensor readings or input states.

For settings and activity verification we use Device Explorer Twin software. It can be downloaded on https://github.com/Azure/azure-iot-sdks/releases/download/2016-11-17/SetupDeviceExplorer.msi When open application we enter string into window IoT Hub Connection String, which was recieved when account. After that, click on the update button.  MS Azure was created and we generate SAS key for required time. In our case 365 days:

Now please switch on Management tab and create new product on Device IP with name e.g.  Poseidon24002Demo

Creation is confirmed by this window:

Now you can see the device in the list of devices

We will select new device  and by pressing SAS Token password can be generated:

Here we notice DeviceID column which contains right device and field TTL (Days) should have suitable lenght, the lenght indicate the lenght of validity:

We copy password from Token. It contains everything what starts with string SharedAccessSignature sr

Now we set Poseidon unit:

On MQTT page we enable MQTT protocol support. Enter server address which was assigned to us when creating MS Azure account, port add 8883 and at the same time we check Secure SSL Mode. Into field Password we enter password generated by previous step. Username is always a compound of server address and DeviceID, for example hwg.azure-devices.net/Poseidon24002Demo and Client ID is in this case on same level as DeviceID.

At the same time, you still need to allow user defined Topic and as Topic name set: devices/YOUR_DEVICE_ID/messages/events/, for example devices/Poseidon24002Demo/messages/events/:

Into Topic Value we can fill definated content using macros:

// XML template

<?xml version="1.0" encoding="utf-8" ?>
<BinaryInSet>%LOOP_IN%<Entry>
<ID>%VAL_ID%</ID>
<Name>%VAL_NAME%</Name>
<Value>%VAL_VALUE%</Value>
<State>%VAL_STATE%</State>
</Entry>%LOOP_IN_END%</BinaryInSet>

<BinaryOutputSet>%LOOP_OUT%<Entry>
<ID>%VAL_ID%</ID>
<Name>%VAL_NAME%</Name>
<Value>%VAL_VALUE%</Value>
<State>%VAL_STATE%</State>
</Entry>%LOOP_OUT_END%</BinaryOutputSet>

<SensorSet>%LOOP_SENSOR%<Entry>
<ID>%VAL_ID%</ID>
<Name>%VAL_NAME%</Name>
<Value>%VAL_VALUE%</Value>
<State>%VAL_STATE%</State>
</Entry>%LOOP_SENSOR_END%</SensorSet>

<BinaryOutputSet>%ID_OUT_3%<Entry>
<ID>%VAL_ID%</ID>
<Name>%VAL_NAME%</Name>
<Value>%VAL_VALUE%</Value>
<State>%VAL_STATE%</State>
</Entry>%ID_OUT_END%</BinaryOutputSet>

// Json template

{
"sensors": [
%LOOP_SENSOR%{"id":%VAL_ID%,
"name":"%VAL_NAME%",
"value":%VAL_VALUE%,
"state":%VAL_STATE%
},

%LOOP_SENSOR_END%,],
"inputs": [
%LOOP_IN%{"id":%VAL_ID%,
"name":"%VAL_NAME%",
"value":%VAL_VALUE%,
"state":%VAL_STATE%
},
%LOOP_IN_END%,],

"outputs": [
%LOOP_OUT%{"id":%VAL_ID%,
"name":"%VAL_NAME%",
"value":%VAL_VALUE%,
},
%LOOP_OUT_END%,]
}

 

Connecting your first device

1. Find the "Portal" tab in your device configuration interface
2. Enable the portal and type in the SensDesk address "www.sensdesk.com/portal.php".
3. Fill in the username with your SensDesk account.
4. The password to your device is the PUSH device password.
   You can find it in your SensDesk account (click on "My account" from the top menu).
5. Click on "Manual Push" button and follow the instructions.

In the "UDP Config" tab of the Hercules utility its possible to search a local network segment for our device using UDP broadcast. The you can for example change the device's IP address, MASK and GateWay. This application note describes the format used to search for devices only, it does not describe the codes for entering the configuration in the module.

How does device lookup/setup work?

• The PC software sends a message as UDP broadcast on port 9999 in this format:

  \377\377\377\377\377\377IIIIMMMMFFFFWWWWUC12345678(c)HW-server.com

• All devices with activated UDP Config on the specific network segment will answer this message. The answer format is described below.
  All the devices, which answered the request, are now in the "UDP Config mode" until a timeout expires. This means, that they wait for an UDP frame with new settings for a certain time. Until the frame comes, the device works normally.
   
• If the device receives an UDP frame with new settings and a corresponding cipher, the new settings are saved and the device is restarted. This document describes only the process of searching for the device, not the configuration change.

Module identification and codes

The device will answer the UDP broadcast with a frame, where it send its setting and a special code. Then the device (module or a HW unit) awaits another frame with configuration from the PC (the Hercules utility). The received frame is verified, and if the encoding is correct it's accepted, otherwise it's ignored. This way also the recipient is identified, if the frame from the PC is sent as UDP broadcast. But this is not necessary, it can also be sent as Unicast, and then it will be answered only by the target device.

Device answers (module or HW unit)

00	unsigned char	MAC[6];	// MAC address of the module
06	unsigned char	IP[4];	// IP address
0A	unsigned char	Mask[4];	// Subnet mask
0E	unsigned char	FwIP[4];	// Acceptable address range IP
12	unsigned char	FwMask[4];	// Acceptable address range MASK
16	unsigned char	Unit[2];	// Device type - more
1A	unsigned char	GW[4];	// GW address (sometime called User1)
1E	unsigned char	User2[2];	// DEVICE CTRL bits settings - more
20	unsigned char	Port[2];	// incomming TCP port number
22	unsigned char	crypt[16];	// Cryption for Write

Device type
Unit2[1]	A0 A1 A2 A3 A4 B0 B1 B2
Unit2[0]	C0 C1 C2 C3 D0 D1 D2 D3
A - Device type	5 bits	// Device FW type name (e.g. Poseidon)
B - General firmware version	3 bits	// Device FW main number (1.8.2]
C - Firmware version	4 bits	// Device FW second number (1.8.2]
D - Firmware sub-version	4 bits	// Device FW third number (1.8.2]

 

DEVICE CTRL bits settings
User2[0] & 1	bit 0	R/W	Enable TCP TEA authorization
User2[0] & 2	bit 1	R/W	Enable NVT
User2[0] & 4	bit 2	R/W	Enable TCP Setup (default on the port 99)
User2[0] & 8	bit 3	Read only	DHCP support (0 = DHCP not supported)
User2[0] & 16	bit 4	R/W	Enable DHCP, fixed IP address ignored

From the previous description you can now see, how to use the module search in your applications. If you also need to modify the configuration of the module, please contact us we will send you detailed information.

The described algorythm, including a MAC address filtering, can be found in the IP Relay Controller software source codes - these codes are compiled using "Borland C++ Builder 6.0".

The Monitor one monitoring system by FineConnection is designed for monitoring network and networking infrastructure status. Products in the Poseidon family are fully integrated with M1 to ensure the best functionality.

In environment monitoring applications, one may need to send a text message (SMS) to the network administrator or a service desk technician whenever a critical problem occurs (such as a water leak, rapid temperature rise, or a power failure). Monitor one allows sending text messages through the use of an external utility, PageGate, by NotePage.

The PageGate utility offers a very variable functionality and is useful in a number of other situations besides those related to Monitor one. However, our in-house tests indicate that the utility does not function correctly in the Czech locale (tested on Windows XP CZ SP2 and Windows Server 2003 CZ), and may have troubles with other non-English locales as well. The tests finished correctly on Windows Server 2003 EN and Windows XP.

Set-up procedure

The following steps assume that a GSM modem is connected to the system and is properly configured. We have used the Teltonica Modemcom G10 modem for the purposes of this example.

1) Installing PageGate and performing initial configuration

There is nothing special about PageGate installation that would require a detailed description. At the beginning of the installation, select PageGate Server from the menu.







 

When the installation completes, launch PageGate Admin. At first, the application starts in the initialization mode, where you need to set certain parameters. To send text messages correctly, the options "GetAscii", "Scheduler", and "Connector1" must be checked. We recommend to keep the default paths.







 

2) Configuring Monitor one

Monitor one configuration is relatively straightforward. First, in the "Options"  -> "Global Configuration" menu, switch to the "Alerting" tab and check the "Send (SMS) alert messages..." box to enable alarm forwarding.







 

Select "Customize", and in the following dialog, check "PageGate" and set the path to the installed PageGate utility.

Next, select the parameters to send.












 

Now, select the groups and users to inform about the alarm via SMS.

First, it is necessary to set up the group of users. Under "Alert groups", right-click the canvas and select "Add a new Alert Group".





 

In the dialog that opens, fill in the group number and name.

Similarly, under "Alert Recipients", add the user by clicking the right mouse button.

In the next dialog, fill in the user group, e-mail address, and the username to use in PageGate.




 

3) Configuring PageGate

Run PageGate Admin and finish the configuration.

In "Program" -> "Settings", under "Run PageGate as", select the Windows Service radio button and click "Apply". 






 

Under "Interfaces" -> "GetAscii" -> "Settings", check "Enable" and select the "Polling Directory" (that is, the directory where PageGate is installed). Confirm the selection by clicking "Apply".







 

In the left panel, right-click "Carriers" and select "Add".







 

In the right-hand side of the window, fill in the name, select "GSM-AT" as the protocol, and set the serial port and modem parameters according to the modem documentation.

The configuration may look like the one in the figure. Click "Apply" to confirm the settings.





 

Next, set the serial port number to which the GSM modem is connected under "Connectors" -> "Connector1". Click "Apply" to confirm.








 

The last step is to add a recipient.

In the left panel, right-click "Recipients" and select "Add".






 

In the right-hand side, fill in the name (Full Name) and username (Recipient - must match the username entered in Monitor one).

In the "ID/PIN" field, enter the telephone number. Leave all other settings at their defaults and click "Apply".

The configuration is now finished. As the final step, run the service by clicking the PageGate icon in the status bar (lower right-hand corner, near the clock) and selecting "Start". From now on, alarms from Monitor one should be forwarded as text messages (SMS).

Conclusion:

This guide presents only a simple configuration of the SMS gateway. Monitor one offers a wide range of alarm functionality. It can be configured, for example, to send the SMS only for important alarms, or only to selected people.

The M1 (Monitor one) monitoring system by FineConnection is designed for monitoring network and networking infrastructure status. Products in the Poseidon family are fully integrated with Monitor one.

In environment monitoring applications, one may need to close a contact (sound a siren, turn on a warning light, etc.) whenever one of the monitored values exceeds a defined threshold.

Monitor one allows to run an external program or batch file upon alarm. In the following example, this feature is used to run the switch_on.cmd script whenever an alarm occurs. The script checks the alarm state message for a given string ("Contact" in this example), and if it is found, invokes the PosDamIO utility to close the contact remotely via the network.

Set-up procedure

1) Configuring Monitor one

First, it is necessary to create a "Shooter" in Monitor one that acts as the alarm trigger.

To create a "Shooter", follow these steps:

• Right-click the icon of the desired Poseidon device.
• In the pop-up menu, select "Define Shooter (manually)".
• In the MIB browser, find and right-click the value you are interested in (in this example, it is the temperature represented by sensValue in the sensEntry tree), and select "Inspect".
  
  
  
  
  
  
   
• Then, create a Shooter by right-clicking the "Shooters" area on the right-hand side and selecting "Add a Shooter".
  
  
  
  
  
  
  
  
  
  
   
• Set the Shooter type to Threshold (the value in parentheses corresponds to the update interval in seconds), name the Shooter (e.g. Contact) and click "Save" to store it.
  
  
  
  
  
  
  
  
  
  
   
• Select the new Shooter by clicking its icon, right-click "SensValue" in the right-hand MIB browser window and select "Add to the selected Shooter".
  
  
  
  
  
  
  
  
  
  
   
• The "Instance" parameter is the last number in the SNMP address of the variable.
  Poseidon uses ".1" for the first sensor, ".3" for the third sensor.
• A threshold value and an operator need to be specified for the monitored sensor (keep in mind that for a Poseidon, the sensValue variable contains the temperature in °C multiplied by 10).
• After saving the Shooter by clicking the "Add/Modify" button, the MIB browser window may be closed.

2) Creating a script

Now, let us write a simple script that finds the device causing the alarm and closes the contact when appropriate.

Monitor one can pass several parameters to the script. In this case, we are interested in the IP address of the alarmed Poseidon device as well as in the error message text. The error message contains the name of the Shooter causing the alarm. We will use this name to filter the request.

The script can look like this:

@echo off
set IP=%1
set MESSAGE=%2
echo %MESSAGE% | find /C "Contact"
echo %ERRORLEVEL%
if %ERRORLEVEL% EQU 0 posdamio.exe -o 1=ON %IP%
goto eof
:eof

Save the script with a .cmd extension. The PosDamIO.exe file must reside in the same directory as the script; otherwise, the script will not work.

If you used a different Shooter name, replace the "Contact" string in the script with that name. For more information, see AN29: PosDamIO – Controlling outputs from the command line. The script can be modified to filter the alarms according to device name, or to close other contacts upon alarm from other Shooters.

3) Activating the Shooter in Monitor one

The last task is to enable script execution and start the Shooter for the given device.

• Monitor one alarm behavior is configured in the Option -> Global Configuration menu. In the dialog, select the "Alerting" tab and check the "Execute a program or a script" box.
  
  
  
  
  
  
  
  
  
  
   
• Click the "Customize" link. In the next dialog, select the script file (switch_on.cmd) and check the "4 IP address" and "5 Event Message" boxes.
• Close the dialogs and return to the network map.
  
  
  
  
  
  
  
  
  
   
• Left-click the Poseidon icon, switch to the "Background Shooters" tab, select and right-click the newly created Shooter, and select the "Start this Shooter..." option.

Conclusion:

Test the setup by creating an alarm situation on the configured sensor. After a short while, Poseidon will activate the output. The closing of the contact is indicated by an audible click and a LED lighting up (Poseidon 3268).

The script is called in every alarm situation. However, if the alarm description does not contain "Contact", the PosDamIO utility is not invoked and outputs remain unaffected.
The versatility of the solution can be enhanced with a suitable modification of the script, e.g. by controlling more contacts. However, such modifications are outside of the scope of this Application Note, which only suggests a way of approaching such tasks.

Note:

Besides the alarm start condition, Monitor one can react to an alarm end condition, too. This can be useful to reopen the closed contact.

The most important step is to configure Monitor One to inform about alarm end. This option is available in the Option -> Global Configuration menu. In the dialog, select the "Alerting" tab and check the "Enable Reverse alerting" box. Then, the script needs to be modified accordingly. There are many ways of doing that, for instance the following one. @echo off set IP=%1 set MESSAGE=%2 echo %MESSAGE% | find /C "normal" if %ERRORLEVEL% EQU 0 (call :SetOFF) else (call :SetON) goto eof :SetON echo %MESSAGE% | find /C "Contact" if %ERRORLEVEL% EQU 0 posdamio.exe -o 1=ON %IP% goto eof :SetOFF echo %MESSAGE% | find /C "Contact" if %ERRORLEVEL% EQU 0 posdamio.exe -o 1=OFF %IP% goto eof :eof