Difference between revisions of "EnOcean Link Solution"

From ESS-WIKI
Jump to: navigation, search
(update)
(udate software download link)
 
Line 186: Line 186:
  
 
| style="width: 759px;" |  
 
| style="width: 759px;" |  
API-GW 2.0.9
+
[https://www.dropbox.com/s/gqwvai9v8x9fjzw/API-GW-2.0.9.exe?dl=0 API-GW 2.0.9]
  
EoLinkManager 1.0.6
+
[https://www.dropbox.com/s/rkbl747zi02gmzd/EoLinkManager-1.0.6.exe?dl=0 EoLinkManager 1.0.6]
  
MQTTBroker 1.0.6
+
[https://www.dropbox.com/s/rzubwa511g8h5x0/MQTTBroker-1.0.6.exe?dl=0 MQTTBroker 1.0.6]
  
 
USB receiver driver:<br/>[https://www.dropbox.com/s/vi00t4ueb1nwe14/CDM21228_Setup.exe?dl=0 CDM21228_Setup.exe]
 
USB receiver driver:<br/>[https://www.dropbox.com/s/vi00t4ueb1nwe14/CDM21228_Setup.exe?dl=0 CDM21228_Setup.exe]

Latest revision as of 05:00, 23 August 2021

System Architecture

Rohm light tower sensor demokit 01.png

EnOcean Sensor and Light Tower (chip & demo kit vendor: ROHM)

EnOcean light sensor 01.png


Notice: Please make sure DIP switch of Light Tower module is setting in normal mode as below diagram.

RTENOTITLE

Sensor Communication Protocol

EnOcean light sensor 03.png

Lighting Condition Data Format:

  • First 4 bits = pervious status
  • Last 4 bits = current status

Lighting Condition Value Definition:

  • 0x0 Light off
  • 0x1 Fast blink (0.5s per blink)
  • 0x2 Blinking medium speed (1s per blink)
  • 0x3 Slow flashing (2s per blink)
  • 0x4 Light on

For example, value of third light is 41.

  • First 4 bits is 4 , which mean previous status is Light On
  • Last 4 bits is 1 , which mean current status is Fast Blink.

Tower Light Data Format

EnOcean light sensor 02.png


Protocol Specification

http://ess-wiki.advantech.com.tw/wiki/images/d/d9/Advantech_EnOcean_light_tower_2018.03.18.pdf


How to

Software Requirements

  • USB receiver driver
  • MQTT broker
  • WISE-Agent
  • API-GW

Software Installation for Windows 10

Notice: Please connect the gateway to the Internet before performing the installation.

Install Steps

  1. Install USB receiver driver
  2. Install MQTT Broker
  3. Install API-GW
  4. Install EoLinkManager , edit config, then restart service.
  5. Install WISE-Agent

Uninstall Steps

  • Select the Start button, then select Settings > Apps. Choose the program you want to remove, and then select Uninstall.
  1. WISE-Agent
  2. EoLinkManager
  3. API-GW
  4. MQTT Broker

Configuration

In Windows 10

  • You can edit C:\Program Files (x86)\Advantech\EoLinkManager\EoLinkManager.ini to change setting.
  • Notice: Once config is modified, please restart EoLinkManager service in Task Manager or reboot gateway in order to apply new setting.
  • RTENOTITLE

Setting File example:

[Platform]
InterfaceName=EoLinkReceiver
ServerURL=127.0.0.1
ServerPort=1883
ModuleName=EoLinkManager
SensorName=LightSensor
SerialPort=COM3
Interval=1

[Sensors]
NumberOfSensors=2
Sensor0=04016943
Sensor1=0400E889

Notice: Please make sure above settings (in blue color) is correct. And please do not change other settings.

SerialPort

  • Assign serial port which USB receiver (USB300) is using.

Interval

  • The time delay between data access round in second.

NumberOfSensors

  • Assign number of Tower Light Sensor module

Sensor0

  • Assign id for Tower Light Sensor module. Format is Sensor0=<<MODULE_ID>>
  • If you have multi Tower Light Sensor module, please start at a number 0 for the first module.
  • Second module use Sensor1.

Debug

1. Check all installed software versions are correct.

2. Check if service is running

  • Make sure EoLinkManager service is running.
  • Make sure WISEAgent service is running.
  • Make sure APIGateway service is running.
  • Make sure mosquitto service is running.

3. Check EoLinkManger log file

  • log files is available at EoLinkManager installed folder, (ex: C:\Program Files (x86)\Advantech\EoLinkManager\logs)
  • View logs files to check if there are any error messages.

4. Check EoLinkManager configuration

  • Make sure SerialPort setting is the port number USB receiver (USB300) is using.
  • Make sure Tower Light Sensor module id is correct and assigned in Sensors section in configuration file.

5. Check if device id of Tower Light Module is listed in Sensor Hub List

In web browser and open url : http://GATEWAY_IP:3000/restapi/WSNManage/SenHub/AllSenHubList

Once Tower Light Module is managed by EoLinkManager, its device id will be listed in Sensor Hub List as shown on below picture.

RTENOTITLE

6. Check WISE-Agent connection status

  • Launch WISE-Agent shortcut in Windows Desktop.
    RTENOTITLE
  • Check if WISE-Agent is connected as below picture.
    TLS debug wiseagent connection2.PNG

7. Check if sensor data is published to WISE-PaaS/EdgeSense

  • Use web browser to open WISE-PaaS/EdgeSense web pages.
  • Go to Device Page and choose the LightSensor device you are using, click on Monitor icon.
  • In Monitor page, select SenHub , then you can monitor the LightSensor data payload.

Grafana Dashboard



Release

Version Date
Platform
OS
Release Note
Download Link
Note
1.0.6 2021/8/23 x86_64 CPU
Windows 10
  • Add log message
  • Watchdog
  • Improve stability
  • Verified by WISE-Agent 1.2.17

API-GW 2.0.9

EoLinkManager 1.0.6

MQTTBroker 1.0.6

USB receiver driver:
CDM21228_Setup.exe

Notice: If API-GW 2.0.7 is installed in your system, please remove API-GW 2.0.7 first, then install API-GW v2.0.9. Please follow this guide.
1.0.5
2020/6/1
x86_64 CPU
Windows 10
  • Fix same Device Name shown in EdgeSense.
  • Verified by WISE-Agent 1.2.17

API-GW 2.0.8

EoLinkManager 1.0.5

MQTTBrokerSetup 1.0.4

USB receiver driver:
CDM21228_Setup.exe

Notice: If API-GW 2.0.7 is installed in your system, please remove API-GW 2.0.7 first, then install API-GW v2.0.8. Please follow this guide.
1.0.4
2019/12/20
x86_64 CPU
Windows 10
  • Add log message
  • Fix no sensor data received cause lost connection
  • Verified by EdgeSense 1.0.106
  • Verified by WISE-Agent 1.2.17

API-GW 2.0.7

EoLinkManager 1.0.4

MQTTBrokerSetup 1.0.4

USB receiver driver:
CDM21228_Setup.exe


Troubleshooting

After upgrading API-GW, API-GW not running

API-GW v2.0.7 or older version is not able to upgrade to v2.0.8

Please remove older version API-GW first, then install API-GW v2.0.8

Below steps shows how to cleanly remove API-GW v2.0.7 or older version.

Step-1. Remove API-GW

RTENOTITLE

Step-2. Remove service.

If API-GW is still listed in service manager as below picture,

RTENOTITLE

Then, use command line with Administrator privileges to run

sc delete apigw.exe

RTENOTITLE