WSN-Device SDK - Revision history

Eric.liang: /* Sample Code Overview */

2022-10-12T10:57:58Z

‎Sample Code Overview

Eric.liang at 03:08, 20 March 2020

2020-03-20T03:08:17Z

Eric.liang at 03:07, 20 March 2020

2020-03-20T03:07:44Z

Eric.liang at 02:59, 20 March 2020

2020-03-20T02:59:38Z

Eric.liang at 05:57, 20 December 2019

2019-12-20T05:57:10Z

Eric.liang at 07:37, 26 July 2019

2019-07-26T07:37:07Z

Show changes

Eric.liang: Created page with "= Introduction = EdgeSense is a Advantech software stack on Edge site. EdgeSense adapots MicroService software archit..."

2019-07-26T07:34:02Z

Created page with "= Introduction = EdgeSense is a Advantech software stack on Edge site. EdgeSense adapots MicroService software archit..."

New page

= Introduction =

      EdgeSense is a Advantech software stack on Edge site. EdgeSense adapots MicroService software architecture as Figure 1. There are three main service categories 1. Southbound, 2. MQTT Broker, 3. Northbound services. 

 It is easy to add / remove services for customization. 

*'''Southbound:''' It collects managed enquirments with Modbus, OPC-UA, ODBC and wireless protocols. Southbound service converts sensor data to Adv-JSON format and sends to local MQTT Broker.

*'''MQTT Broker:''' MQTT broker as the asynchronous communication bus for Inter-service communication. Inter-service communication protocol base on MQTT standard and IETF (The Internet Engineering Task Force) defined media types for Sensor Makeup Language (SenML) in JSON format. 

*'''Northbound:'''  An agent (WISEAgent) connects to its Cloud solution ( e.g. WISE-PaaS/DeviceOn ). It receives southbound sensor data from MQTT Broker and transfers to cloud. 

= EdgeSense =

[[File:EdgeSense-Architecture-v3.jpg|1400x800px|EdgeSense SW Architecture 1.jpg]]

                                                                                                                                               Figure 1. Software Architecture of EdgeSense   

  EdgeSense provides varies southbound and northbound services at edge. All of EdgeSense services's sensor data will be packed as [[IoTGateway/AdvJSON|AdvJSON]] data format and use the [[Connectivity/Agent_Communication_Protocol_in_MQTT|EdgeSense Protocol as]] standard communicate rotocol.

'''Southbound''' provides two SDK to integrate "Wire" (e.g. COM, RS-232... ) and "Wireless" ( e.g. LoRa, EnOcean...) devices. 

*Wire : A stanard wire servic protocol (e.g. Modbus, OPC-UA, SNMP-NMS...) to get, set and transfer device's sensor data to MQTT broker by "Device SDK" ( C/C++ or Node.js ).
*Wireless: A wireless device management service to send register message for a wireless sensor hub device (e.g. lora, dust-link...) and transfer its sensor data to local MQTT broker with WSN-Device SDK ( C/C++ ). 

'''Northbound''' agent (WISEAgent) receives data from MQTT broker ( - Wire devices ) or API-GW ( - Wireless sensor hub devices ) and transfer to Cloud ( e.g. WISE-PaaS/DeviceOn ).

= How To =

==  EdgeSense Southbound Services ==

  User can use Advantech developed southbound services (e.g. Modbus, ODBC, OPC-UA, ReyLax LoRa ... ) to integrate with devices and applications easily. Please refer to [[EdgeSense_Portal|EdgeSense_Portal]] ( at Software Solution Section ) for detail.

==  Developing a southbound service ==

   User can easy to develop a new soouthbound service with EdgeSense SDK ( [[EdgeSense_Southbound_Service_Development|Device SDK]]  or [[WSN-AgentLite|WSN-Device SDK]] ).

=== [[WSN-AgentLite|WSN-Device SDK]] ===

 It is a layer to define the topology and behavior of sensor network. A complete device represented in WSN-Device SDK includes one virtual gateway, one sensor connectivity interface and several sensor devices. WSN-Device SDK provides a form-like array which we call it infospec array to define tha parameters of sensor device. And a form-like data array updates your real time data. So, you can easy to represent your device by creating several arrays. 

'''Application:'''  To integrate a new wireless sensor device ( e.g. bluetooth, lora...) with EdgeSense gateway and WISE-PaaS/DeviceOn. There is a wireless module card ( e.g. COM port ) at edge and these wirelss devices with uniquide device ID. 

=== [[EdgeSense_Southbound_Service_Development|Device SDK]] ===

@@ Line 563: / Line 563: @@
 				"/Info/Name",
 				"",
-				.string = "SenHub1",  // Device Name of SenHub (*)
+				"SenHub1",  // Device Name of SenHub (*)
 ,
 ,

@@ Line 553: / Line 553: @@
      printf("(GPIO 2) = %d\r\n",data->value);
+}
-void SetSHName(WiseSnail_Data*data) {    printf("( SHName ) = %s\r\n", data->string);}
+void SetSHName(WiseSnail_Data*data) {

@@ Line 553: / Line 553: @@
      printf("(GPIO 2) = %d\r\n",data->value);
+}
+void SetSHName(WiseSnail_Data*data) {    printf("( SHName ) = %s\r\n", data->string);}
@@ Line 565: / Line 565: @@
 ,
 				"",
-				//SetSHName,
+				SetSHName
 		},
+		{
@@ Line 618: / Line 617: @@
 				"Humidity",			//name
 				//value
+		}
 };

@@ Line 554: / Line 554: @@
+}
 WiseSnail_InfoSpec infospec[] = {
@@ Line 623: / Line 605: @@
                          	"",
                          	SetGPIO_2
+		}
 };

@@ Line 666: / Line 666: @@
 	//initial
 	WiseSnail_Init("IotGW",NULL, NULL, NULL, 0);
-	WiseSnail_RegisterInterface("000E4CAB1234", "Ethernet", -1, interface, 1);
+	WiseSnail_RegisterInterface("000E4CAB1234", "Ethernet", 0, interface, 1);
 	if(WiseSnail_Connect(SERVER_ADDRESS, 1883, "", "", NULL, 0) == 0) {
@@ Line 709: / Line 709: @@
+}
 </syntaxhighlight>
 == Get Project ==