LoRaWAN
Gateway & Node
Configuration Guide
LRPv2 (BB-WSW) Node
Setup Guide
Before to Start – Download the Tool You Need
3
Physical Connection Overview
LRPV2
Connector
Connect to
Console
PWR & Sensor
Connector
Please connect the PC and node with the Micro USB cable. (Micro USB)
The following address direct you to the USB driver if you need it.
https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-
vcp-drivers 4
Physical Connection for RS485(Modbus RTU) SKU
Connector
Brown Red Pink Yellow Green Blue White Gray
8 7 6 5 4 3 2 1
D- D+ NC NC NC NC GND PWR
9~36VDC
BB-WSW2C00015-1
LoRaWAN node w/RS485, external antenna (915MHz)
BB-WSW2C00015-2
LoRaWAN node w/RS485, external antenna (868MHz)
BB-WSW2C00015-3
LoRaWAN node w/RS485, external antenna (923MHz)
5
Physical Connection for AIDIDO SKU 1/2
Connector 1
Brown8 Red Pink Yellow Green Blue White Gray
7 6 5 4 3 2 1
GND AI4 GND AI3 GND AI2 GND AI1
Connector 2
GND DO GND DI2 GND DI1 V- V+ 9~36VDC
BB-WSW2C42100-1 LoRaWAN node
4 x AI, 2 x DI, 1 x DO, conduit, external antenna (915 MHz)
Connector 2
BB-WSW2C42100-2 LoRaWAN node
4 x AI, 2 x DI, 1 x DO, conduit, external antenna (868 MHz)
Connector 1
BB-WSW2C42100-3 LoRaWAN node
4 x AI, 2 x DI, 1 x DO, conduit, external antenna (923 MHz)
6
Physical Connection for AIDIDO SKU 2/2
There are 4 DIP switch for switching
the mode between current and volt
---switch all DIP to the right(Current)
---switch all DIP to the left (Volt)
BB-WSW2C42100-1 LoRaWAN node
4 x AI, 2 x DI, 1 x DO, conduit, external antenna (915 MHz)
BB-WSW2C42100-2 LoRaWAN node
4 x AI, 2 x DI, 1 x DO, conduit, external antenna (868 MHz)
BB-WSW2C42100-3 LoRaWAN node
4 x AI, 2 x DI, 1 x DO, conduit, external antenna (923 MHz) 7
LoRaWAN Node Utility 1/5
After to connect the computer with the node via the
console connector, it’s feasible to execute the utility
and configure the node.
The default login password is “admin”.
8
LoRaWAN Node Utility 2/5
9
LoRaWAN Node Utility 3/5
Radio settings for EU/US SKU
10
LoRaWAN Node Utility 4/5
Under sensor Page, you can configure the sensor node parameter.
(AIDIDO SKU)
The DI Wakeup Trigger can
setup Low to High or High to
Low trigger.
With the LoRa chipset limitation,
the minimum uplink interval should be higher
than 15 sec
11
LoRaWAN Node Utility 5/5
For RS485 (ModbusRTU SKU)
By default setting, it supports 6 read rule.
Each of the rule can read 3 Modbus address(fc:3)
It can read up to 23 address(fc:3) when speeding up the LoRa data rate.
12
WISE-6610 Setup
Guide
GW Setting
Physical Connection Guide – WISE-6610
LoRaWAN gateway Pin Definition
Red Yellow Black Grey
PWR+ DI GND DO
9~36VDC
15
WISE-6610 Overview 1) UM Access
GUI
Default IP is 192.168.1.1
ID/PW: root/root
Menu > Customization > User Module > LoRaWAN
GW
17
WISE-6610 Overview 2) RF Setting
1. Enable radio & Decide the uplink channel
2. No need to input downlink channel. The network server decide the downlink
channel based on the uplink packets
3. Feasible to press Quick Setup to choose the channel
WISE-6610 Overview 3) RF Setting
Choose the channel according to the LoRa node spec
19
WISE-6610 Overview 4) Network Server Setting
Direct the LoRaWAN GW to a network server
Since WISE-6610 supports network server feature,
You can direct the data to WISE-6610(127.0.0.1)
itself.
20
WISE-6610 Overview 5) GW MQTT Setting
WISE-6610 supports MQTT broker to process the
data handled by the network server.
21
WISE-6610 Overview 6) Status Checking
Raw data is received after to enable the LoRaWAN radio, you can check if
wireless functions well in this page.
22
WISE-6610 Overview 7) Network Server Link
After configuring the LoRaWAN setting, please go to LoRaWAN
server(network server) to create the data processing rule on Network server
23
Network Server Setting
Network Server Configuration – Assign the Gateway
1. Please assign the LoRaWAN GW to network server
2. Please leave the Tx chain as 0 (according to WISE6610’s HW spec)
25
Network Server Configuration – Assign the Network
1. Define the network frequency for the network server
2. There are 4 setting(EU/AU/AS/US) are pre-configured by
default. All the parameter are complying with LoRaWAN
regulation.
26
Network Server Configuration – Create the handler
> Configure the handler
> Define what information you want to receive
> It’s a rule for the network server to process data
27
Network Server Configuration – Configure the Handler
Define what information you want to receive
28
Network Server Configuration – Setup the Data Connector
Define how to process the data after to the network server
decrypts the data
Example: Through MQTT
In this example : We save the Topic on localhost’s MQTT
broker
1. Publish Uplink(MQTT topic) for Rx
2. Receive topic (MQTT topic) for Tx
29
Network Server Configuration – Configure the Connector
30
Network Server Configuration – Create Profiles for Nodes
Here, we are starting to configure the LoRa node setting
The target is to pair the handler with the network
frequency for the LoRa node
31
Network Server Configuration – Configure Profiles
To configure the nodes, you need to pair the
handler with the network frequency through
profile setting
Can Join is the option for OTAA setting
Assign Rx1 or Rx2 for the node to receive Tx
Generally, we suggest leave it in AUTO
32
Network Server Configuration – Create Node’s Rule
Please add(configure) the node according to your node’s
type
For ABP type (Ex: Advantech LRPv2 node default setting),
please choose Activated(Nodes)
Please choose the profile
and input DevAddr/
NwkSkey/AppSKey
33
Network Server Configuration – ABP Nodes
On these fields, it will record how
many packets it receives and sends
Also, it shows which gateway receives
the data from this node
34
Network Server Configuration – OTAA Nodes
For OTAA nodes, please configure it through Commissioned
OTAA
Please choose the profile
and input DevEUI/
AppEUI/AppSKey
35
Network Server Configuration – Check Receiving Frames
You can verify if the LoRaWAN network server functions well.
Please check it through “receive frame“
36
Send Tx Frames
send Tx frames to the nodes via the Web UI
send Tx frames to the nodes via MQTT message
e.g. Class A node {"data":"11”,"port":13}
e.g. Class C node {"data":"11","time":"immediately","port":13}
Configure the tx port according to the node
Network server will not resend
the message even it’s dropped
Application Server
Setting
Node-RED Setting 1/4
Since the message are already delivered through MQTT,
you can use any MQTT software to receive the node data.
Or, going to Node-RED to receive the node data
39
Node-RED Setting 2/4
Enable Node-RED on WISE-6610 1880 port
40
Node-RED Setting 3/4
Access http://{WISE-6610_IP}:1880
ID/PW: root/root
41
Node-RED Setting 4/4
You can receive the LoRa node data after to
complete the network server setting. This MQTT
topic shows the raw sensor data
42
Application for Advantech LRPv2 Nodes 1/4
If you have one more App argument setting, you can receive Advantech sensor
data which already be classified.
Please ensure the Application server is enabled and go for “App
argument“ setting
43
Application for Advantech LRPv2 Nodes 2/4
Go to node setting and insert the App Arguments ”Advantech” for BB-WSW node
44
Application for Advantech LRPv2 Nodes 3/4
> Make sure the handler equips the above items, it’s the item
for filtering Advantech BB-WSW nodes
45
Application for Advantech LRPv2 Nodes 4/4
Once the setting is done, the application on the gateway allows you monitor
and manage Advantech nodes. It doesn’t support other nodes come from
other vendor.
If LoRaWAN node is BB-WSW node, it’s feasible to manage
and configure it on WISE-6610’s application server 46
Subscribe the Data which had been Filtered
MQTT topic “Advantech/{DevAddr}/data”
47
Application Server
Modbus TCP
Modbus TCP Mapping 1/3
If you have Application Server enabled. Also, having App argument setting
“Advantech” for BB-WSW node. There is a new ModbusTCP mapping function to
bridge the sensor data (RS485/AI/DI/DO) with your SCADA system.
RS485
AI/DI/DO
Sensor
SCADA Query data
Modbus Master Response Modbus Slave
IP:192.168.1.1 IP:192.168.1.2 49
Modbus TCP Mapping 2/3
Please add the node info and map the slave ID to the BB-WSW node.
We prepare the Modbus Address Table for mapping with the input on BB-WSW
node(see next page).
1. Only Class A type for AI/DI/DO SKU
2. Class A/C was supported on RS485 SKU. If you choose Class C, the Modbus
Table will follow the original Modbus address on the sensor. So you can query
the sensor directly.
50
Modbus TCP Mapping 3/3
Please refer to this FAQ:
What is the Modbus Address definition of BB Wzzard on WISE-6610
https://www.advantech.com/support/details/faq?id=1-21ZCCS1
51
Application Server
Payload Engine
A Local Decoder in The Edge
The Answer is “YES”
Can WISE-6610 support
It’s feasible to decode the data payload
decoding the LoRaWAN
through “Node-RED” or the “payload engine”
sensor raw data payload ?
53
Payload Engine Helps You Define The Decoder For Sensors
Application server > Payload Engine
54
Target: Readable Payload
55
Steps of Adding Payload Engine
Please assign/edit different payload engine name for the different sensor type
The sensor’s App Arguments is the
ID which should match with the
payload engine name 56
Add Payload Engine / Payload Engine Format
Ignore 234 11 434 (Dec)
(Hex)
57
Advanced Payload Engine Format
Using “arithmetic”
for the complicated
calculation.
It will do the
calculation in the
order of your
parameter.
So, it will do +, - ,*
then / in this example.
58
Appendix
How To Have The Local Time in Received Frames
1 Make sure the UM 2 Set the Local Time
version is over
1.0.19
3 Erase the Cookies of the Browser
4 Go to Received Frames
Choose the Local Timezone
