beangateway management on a lan · pdf fileinternal reference project code n.a. document name...
TRANSCRIPT
Ref : RF_TN_009 V1.6
www.beanair.com
TECHNICAL NOTE BeanGateway® management on a LAN and 3G/4G infrastructure
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 1 / 59
DOCUMENT
Document number Version V1.6
External Reference RF_TN_009 Publication date 22/12/2016
Author Christophe DONTEGREUIL Internal Reference Project Code N.A.
Document Name BeanGateway® management on a LAN and 3G Infrastructure
VALIDATION
Function Recipients For Validation
For information
Reader X
Author X
MAILING LIST
Function Recipients For action For Info
Staffer 1 Christophe DONTEGREUIL X
Staffer 2 Maneli PARSY X
Updates
Version Date Author Evolution & Status
V1.0 10 /06/2011 Christophe Dontegreuil
First version of the document
V1.1 19/10/2012 Christophe Dontegreuil
Typical network configuration chapter added
V1.2
05/01/2012 Christophe Dontegreuil
Troubleshooting chapter added
V1.3 21/04/2012 Christophe Dontegreuil
3G Router Configuration added
V1.4 29/05/2012 Christophe Dontegreuil
BeanScape Keep Alive description added
V1.5 01/09/2016 Salah Riahi
Teltonika 3G/4G Modem example added
V1.6 22/12/2016 Salah Riahi
Remote access to a Wireless Sensor Network video added
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 2 / 59
1. TECHNICAL SUPPORT ............................................................................................................................. 5
2. VISUAL SYMBOLS DEFINITION ............................................................................................................... 6
3. ACRONYMS AND ABBREVIATIONS ........................................................................................................ 7
4. RELATED DOCUMENTS ........................................................................................................................... 8
4.1 Applications Notes .............................................................................................................................. 8
4.1 Technical Notes .................................................................................................................................. 9
4.1 Related videos .................................................................................................................................. 10
5. AIM OF THIS DOCUMENT ...................................................................................................................... 11
6. SOME DEFINITIONS ............................................................................................................................... 12
6.1 What is a DNS? ................................................................................................................................ 12
6.2 What is DHCP ? ............................................................................................................................... 12
6.3 Port Forwarding ................................................................................................................................ 14
7. BEANSCAPE® AND BEANGATEWAY® COMMUNICATION MECHANISMS OVERVIEW .................. 15
7.1 Regular Communication : TCP LINK................................................................................................ 15
7.1.1 LAN overview .......................................................................................................................... 15
7.1.2 Initiating connection ................................................................................................................ 16
7.2 Communication for BeanGateway® LAN configuration : UDP Link ................................................. 20
7.2.1 Overview ................................................................................................................................. 20
7.2.2 Communication steps ............................................................................................................. 21
7.3 Keep Alive feature ............................................................................................................................ 23
8. BEANSCAPE® AND BEANGATEWAY® NETWORKS RELATED FEATURES CONFIGURATION...... 24
8.1 BeanGateway® LAN configuration (for advanced user only) .......................................................... 24
8.1.1 Configuration from serial Port ................................................................................................. 27
8.1.2 Configuration from Ethernet ................................................................................................... 28
8.2 BeanScape configuration ................................................................................................................. 32
8.2.1 LAN configuration (for advanced users only) ......................................................................... 32
Contents
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 3 / 59
8.2.2 TCP Port configuration (for expert users only) ....................................................................... 32
8.3 KEEP ALIVE configuration ............................................................................................................... 33
8.3.1 BeanGateway® side ............................................................................................................... 33
8.3.1 BeanScape® side ................................................................................................................... 35
8.4 Security option: deactivate BeanGateway® LAN configuration via ethernet ................................... 36
9. MULTI-WSN CONFIGURATION .............................................................................................................. 37
10. INTERFACING THE BEANGATEWAY® WITH A 3G/4G ROUTER ........................................................ 38
10.1 Material requirement ........................................................................................................................ 39
10.2 Network configuration ....................................................................................................................... 40
10.2.1 BeanGateway® Configuration ................................................................................................ 40
10.2.2 ADSL MODEM (NAT ROUTER configuration) ....................................................................... 42
10.2.3 BeanScape® (PC ) Configuration........................................................................................... 43
10.2.4 3G/4G Modem Configuration .................................................................................................. 44
10.3 Example: Teltonika RUT950 3G/4G Modem .................................................................................... 45
11. TYPICAL NETWORK CONFIGURATION EXAMPLES ........................................................................... 50
11.1 Beanscape® and Beangateway® connected through direct ethernet link ....................................... 50
11.2 Beanscape® and Beangateway® connected to a LAN network without dhcp server ..................... 53
11.3 Beanscape® and Beangateway® connected on a LAN network with dhcp server ......................... 55
12. TROUBLESHOOTING .............................................................................................................................. 57
12.1 How can I Get the IP Configuration on my PC? ............................................................................... 57
12.2 How can I modify my PC network interface configuration? .............................................................. 58
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 4 / 59
Disclaimer The information contained in this document is the proprietary information of BeanAir GmbH. The contents are confidential and any disclosure to persons other than the officers, employees, agents or subcontractors of the owner or licensee of this document, without the prior written consent of BeanAir GmbH, is strictly prohibited. BeanAir makes every effort to ensure the quality of the information it makes available. Notwithstanding the foregoing, BeanAir does not make any warranty as to the information contained herein, and does not accept any liability for any injury, loss or damage of any kind incurred by use of or reliance upon the information. BeanAir disclaims any and all responsibility for the application of the devices characterized in this document, and notes that the application of the device must comply with the safety standards of the applicable country, and where applicable, with the relevant wiring rules. BeanAir reserves the right to make modifications, additions and deletions to this document due to typographical errors, inaccurate information, or improvements to programs and/or equipment at any time and without notice. Such changes will, nevertheless be incorporated into new editions of this document. Copyright: Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and communication thereof to others without express authorization are prohibited. Offenders will be held liable for payment of damages. All rights are reserved.
Copyright © BeanAir GmBh 2015
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 5 / 59
1. TECHNICAL SUPPORT
For general contact, technical support, to report documentation errors and to order manuals, contact BeanAir Technical Support Center (BTSC) at: [email protected] For detailed information about where you can buy the BeanAir equipment/software or for recommendations on accessories and components visit: www.beanair.com To register for product news and announcements or for product questions contact BeanAir’s Technical Support Center (BTSC). Our aim is to make this user manual as helpful as possible. Please keep us informed of your comments and suggestions for improvements. BeanAir appreciates feedback from the users.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 6 / 59
2. VISUAL SYMBOLS DEFINITION
Visual Definition
Caution or Warning – Alerts the user with important information about BeanAir wireless sensor networks (WSN), if this information is not followed, the equipment /software may fail or malfunction.
Danger – This information MUST be followed if not you may damage the equipment permanently or bodily injury may occur.
Tip or Information – Provides advice and suggestions that may be useful when installing BeanAir Wireless Sensor Networks.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 7 / 59
3. ACRONYMS AND ABBREVIATIONS
AES Advanced Encryption Standard
CCA Clear Channel Assessment
CSMA/CA Carrier Sense Multiple Access/Collision Avoidance
GTS Guaranteed Time-Slot
kSps Kilo samples per second
LLC Logical Link Control
LQI Link quality indicator
LDCDA Low duty cycle data acquisition
MAC Media Access Control
PAN Personal Area Network
PER Packet error rate
RF Radio Frequency
SD Secure Digital
SSD Smart shock detection
WSN Wireless sensor Network
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 8 / 59
4. RELATED DOCUMENTS
In addition to this User manual, please consult the application notes & technical notes mentioned below:
4.1 APPLICATIONS NOTES
Document name (Click on the weblink)
Related product Description
AN_RF_007 :“ Beanair_WSN_Deployment“
All BeanAir products Wireless sensor networks deployment guidelines
AN_RF_006 – „How to extend your wireless range“
All BeanAir products A guideline very useful for extending your wireless range
AN_RF_005 – BeanGateway ® & Data Terminal Equipment Interface
BeanGateway ® DTE interface Architecture on the BeanGateway ®
AN_RF_003 - “IEEE 802.15.4 2.4 GHz Vs 868 MHz”
All BeanAir products Comparison between 868 MHz frequency band and a 2.4 GHz frequency band.
AN_RF_002 – “Structural Health monitoring on bridges”
All BeanAir products
The aim of this document is to overview Beanair® products suited for bridge monitoring, their deployment, as well as their capacity and limits by overviewing various Data acquisition modes available on each BeanDevice®.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 9 / 59
4.1 TECHNICAL NOTES
Document name (Click on the weblink)
Related product Description
TN_RF_013 – « OPC configuration » BeanScape® Premium+ The aim of this document is to help deploying the OPC DA and all associated services.
TN_RF_012– « BeanDevice® battery life in streaming mode »
All the products
The aim of this document is to describe the autonomy performance of the BeanDevice® SmartSensor® and ProcessSensor® product line in streaming and streaming packet mode.
TN_RF_011 – « Coexistence of Beanair WSN at 2.4GHz »
All the products
This document aims to highlight the issues affecting co-existence of Beanair WSN (IEEE 802.15.4) in the presence of interference.
TN_RF_010 – « BeanDevice® Power Management »
All the BeanDevice® This technical note describes the sleeping & active power mode on the BeanDevice®.
TN_RF_009 – « BeanGateway ® management on LAN infrastructure »
BeanGateway ® BeanGateway ® integration on a LAN infrastructure
TN_RF_008 – “Data acquisition modes available on the BeanDevice®”
All the BeanDevice® Data acquisition modes available on the BeanDevice®
TN_RF_007 – “BeanDevice® DataLogger User Guide ”
All the BeanDevice® This document presents the DataLogger feature on the BeanDevice®
TN_RF_006 – “WSN Association process”
All the BeanDevice®
Description of the BeanDevice® network association
TN_RF_005 – “Pulse counter & binary Data acquisition on the BeanDevice® SUN-BN”
BeanDevice® SUN-BN
This document presents Pulse counter (ex: energy metering application) and binary Data acquisition features on the BeanDevice® SUN-BN.
RF_TN_003- “Aggregation capacity of wireless sensor networks”
All the products Network capacity characterization of Beanair Wireless Sensor Networks
RF_TN_002 V1.0 - Current consumption in active & sleeping mode
BeanDevice® Current consumption estimation of the BeanDevice in active and sleeping mode
RF_TN_001 V1.0- Wireless range benchmarking
BeanDevice® Wireless range benchmarking of the BeanDevice®
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 10 / 59
4.1 RELATED VIDEOS
All the videos are available on our Youtube channel
Beanair video link (Youtube) Related products
Company Presentation All
BeanGateway ® - Ethernet Outdoor version introduction
BeanGateway ® - Ethernet Outdoor version introduction
BeanGateway ® – Ethernet Indoor version presentation BeanGateway ® Ethernet Indoor version
BeanDevice® AN-XX wireless range demonstration BeanDevice® AN-XX & BeanDevice® AN-XX Extender
BeanDevice® AN-XX presentation BeanDevice® AN-XX & BeanDevice® AN-XX Extender
BeanDevice® AX-3D presentation BeanDevice® AX-3D
BeanDevice® HI-INC presentation BeanDevice® HI-INC
BeanDevice® AX-3DS presentation BeanDevice® AX-3DS
BeanScape® – WSN supervision software BeanScape®
BeanGateway ® Ethernet/LAN Configuration, directly connected to the Laptop/PC
BeanGateway ®
Wireless sensors profile deletion from the BeanGateway ® Database
All
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 11 / 59
5. AIM OF THIS DOCUMENT
The aim of this document is to describe closely all the parameters related to the LAN configuration of your BeanGateway®.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 12 / 59
6. SOME DEFINITIONS
6.1 WHAT IS A DNS?
The DNS Domain Name System is a database system that translates the BeanGateway®'s fully qualified domain name into an IP address.
The BeanGateway® uses IP addresses to locate and be located in order to communicate. However, IP addresses can be difficult to remember. For example, while browsing the web it is much easier to remember
domain names such www.benair.com rather than its associated IP address (207.171.166.48). The DNS
allows you to manage a BeanGateway® on your Network by using its user-friendly domain name rather than its numerical IP address. Conversely, Reverse DNS (rDNS) translates an IP address into a domain name.
Each organization that maintains a computer network will have at least one server handling DNS query. The name server, will hold a list of all the IP addresses within its network, plus a cache of all IP addresses for recently accessed computers outside the network. Each computer on each network needs to know the location of only one name server. When your BeanGateway® requests an IP address, one of the three following cases may happen, depending on whether or not the requested IP address is within your local network:
If the requested IP address is registered locally (i.e., it's within your organization's network), you' will receive a response directly from one of the local name servers listed in your workstation configuration. In this case, there usually is little or no wait for a response.
If the requested IP address is not registered locally (i.e., outside your organization's network), but someone within your organization has recently requested the same IP address, then the local name server will retrieve the IP address from its cache. Again, there should be little or no wait for a response.
If the requested IP address is not registered locally, and you are the first person to request information about this system in a certain period of time (ranging from 12 hours to one week), then the local name server will perform a search on behalf of your workstation. This search may involve querying two or more other name servers at potentially very remote locations. These queries can take anywhere from a second or two up to a minute (depending on how well connected you are to the remote network and how many intermediate name servers must be contacted). Sometimes, due to the lightweight protocol used for DNS, you may not receive a response. In these cases, your workstation or client software may continue to repeat the query until a response is received, or you may receive an error message.
A good analogy is to think of DNS as an electronic telephone book for a BeanGateway® on your network. If you know the name of the BeanGateway® in question, the name server will look up its IP address.
6.2 WHAT IS DHCP ?
Dynamic Host Configuration Protocol (DHCP) is a network protocol that enables a server to automatically assign an IP address to a computer from a defined range of numbers (i.e., a scope) configured for a given network.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 13 / 59
DHCP assigns an IP address whenever the BeanGateway® is started, for example:
1. A user turns on the BeanGateway® with DHCP client activated.
2. The BeanGateway® sends a broadcast request (called a DISCOVER or DHCPDISCOVER), looking for a DHCP server to answer.
3. The router directs the DISCOVER packet to the correct DHCP server.
4. The server receives the DISCOVER packet. Based on availability and usage policies set on the server, the server determines an appropriate address (if any) to give to the client. The server then temporarily reserves that address for the client and sends back to the client an OFFER (or DHCPOFFER) packet, with that address information. The server also configures the client's DNS servers, NTP servers, and sometimes other services as well.
5. The client sends a REQUEST (or DHCPREQUEST) packet, letting the server know that it intends to use the address.
6. The server sends an ACK (or DHCPACK) packet, confirming that the client has been given a lease on the address for a server-specified period of time.
When a BeanGateway® uses a static IP address, it means that the BeanGateway® is manually configured to use a specific IP address. One problem with static assignment, which can result from user error or inattention to detail, occurs when two BeanGateway® are configured with the same IP address. This creates a conflict that results in loss of service. Using DHCP to dynamically assign IP addresses minimizes these conflicts.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 14 / 59
6.3 PORT FORWARDING
Port forwarding or port mapping is a name given to the combined technique of:
1. Translating the address and/or port number of a packet to a new destination
2. Possibly accepting such packet(s) in a packet filter (firewall)
3. Forwarding the packet according to the routing table.
The destination may be a predetermined network port (assuming protocols like TCP and UDP, though the process is not limited to these) on a host within a NAT-masqueraded, typically private network, based on the port number on which it was received at the gateway from the originating host.
The technique is used to permit communications by external hosts with services provided within a private local area network.
ADSL Modem
Example of PORT FORWARDING
Real-Time WSN Supervision
Ethernet connexion
Ethernet Switch Router
Wireless SensorNetworks
Internet
Public PORT
Private PORT
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 15 / 59
7. BEANSCAPE® AND BEANGATEWAY® COMMUNICATION MECHANISMS OVERVIEW
7.1 REGULAR COMMUNICATION : TCP LINK
7.1.1 LAN overview
PC/BeanScape® IP Address must be known by the BeanGateway®
BeanScape®(TCP server)
BeanGateway®(TCP client)
Wireless SensorNetwork
Management Data
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 16 / 59
7.1.2 Initiating connection
•When the BeanScape® is launched , it starts listening for a TCP socket connection
•When you power up the BeanGateway®, a request for socket connection is established between the Beanscape® and the BeanGaterway®
•If this request is accepted by the BeanScape®, an confirmation (or ACK) is transmitted by the BeanGateway® to the BeanScape®
Step 1: Socket connection
TCP Socket Connection Request
BeanScape® BeanGateway®
ACK
Listen for TCP socket connection
Static or DynamicIP
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 17 / 59
•The BeanGateway® profile is recorded on its flash memory. This profile contains informations regarding the BeanGateway® adress (NWK Add, PAN ID, MAC ID, IP...) , versions ID (Hardware, embedded software, stack...), Radio Management parameters (Radio channel, TX Power, ....);
•The BeanGateway® profile is transmitted to the BeanScape®
Step 2: BeanGateway®
Profile Transmission
BeanGateway®profile Transmission
BeanScape® BeanGateway®
ACK
BeanGateway ® profile is
backuped on BeanScapeDatabase
BeanGateway®profile is backed
up on a Flash memory
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 18 / 59
• The WSN mapping concerns all Beandevice® profiles. The WSN mapping is backed up on the BeanGateway® flash memory. When a new BeanDevice® joins a WSN, its profile is transmitted to the BeanGateway® and the BeanScape®.
• The BeanScape® displays the WSN Mapping within the BeanDevice® profile;
• WSN Mapping is also backed up on the BeanScape® Database.
Step 3: WSN Mapping
transmission
BeanDevice®profile Transmission
BeanScape® BeanGateway®
ACK
BeanDevice®profile are
backuped on a Flash memory
WSN mappng isregistered on the
BeanScape® database
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 19 / 59
Time transmission throughNTP (Net Time protocol)
BeanScape® BeanGateway®
ACK
BeanGateway® Time and Date is synchronizedwith your PC
The WSN Time & Date is synchronized with your PC. The User must make sure that the Date on his computer is not wrong.
• The Date is transmitted to the BeanGateway by NTP (Net-Time Protocole)
•Time & Date are updated on the BeanGateway instantly
• The BeanGateway integrates a Real-Time-Clock directly powered by th internal battery which allows to maintain the Date when the BeanGateway® is powered down
• The Date is updated instantly on the BeanGateway®
Step 4: Time & Date update
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 20 / 59
7.2 COMMUNICATION FOR BEANGATEWAY® LAN CONFIGURATION : UDP LINK
The BeanScape® provides a LAN configuration tool allowing the user to accelerate the integration of the BeanGateway® on a LAN infrastructure.
7.2.1 Overview
The BeanGateway® UDP Port must be known by the BeanScape®.
BeanScape®(UDP client)
BeanGateway®(UDP server)
BeanGateway ® LAN Configuration Data
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 21 / 59
7.2.2 Communication steps
•The BeanScape® broadcasts an UDP frame for locating the BeanGateway®.
•All the BeanGateways® present on the Ethernet network replies with an ACK.
• All the discovered BeanGateway® are listed by the "BeanGateway® LAN configuration Tool".
Step 1: Localization
Broadcast UDP localization frame « Are you on my network ?»
BeanScape® BeanGateway®
ACK
Listen for UDP localization frame
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 22 / 59
•The user validates a configuration for a BeanGateway®. This configuration will be sent by the BeanScape® to the targetted BeanGateway®
•Once the configuration is received and validated by the BeanGateway®, it will reply by an ACK to the BeanScape®.
Step 2: Configuration
UDP LAN configuration frame
BeanScape® BeanGateway®
ACK
Listen for UDP LAN configuration
frame
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 23 / 59
7.3 KEEP ALIVE FEATURE
On both side BeanScape® and BeanGateway®, a “keepalive” signal is often sent at predefined intervals. If an emitted signal is left without any response signal, then the link will be assumed as “Dead”. A “keepalive” signal can also be used to indicate to the Network Infrastructure that the connection should be preserved. Without the “keepalive” signal intermediate routers can drop the connection after the timeout occurs.
Since the main purpose of the “keepalive” functionality is either to find links that do not work or to indicate links that should be preserved, “keepalive” messages tend to be short and not take much bandwidth. However, their precise format and usage terms depend on the communication protocol.
The “keepalive” time is the duration between two “keepalive” transmissions in idle condition. TCP “keepalive” time period is required to be configurable and by default is set to no less than 2 hours.
The “keepalive” interval is the time duration between two successive “ keepalive” retransmissions, (In case if no response to the first “Keepalive” has been issued from the target).
The “Keepalive retry” is the number of retransmissions to be carried out before declaring that remote end is either not reachable or out of service.
Keep Alive TransmissionBeanScape®BeanGateway®
Keep Alive Transmission
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 24 / 59
8. BEANSCAPE® AND BEANGATEWAY® NETWORKS RELATED FEATURES CONFIGURATION
8.1 BEANGATEWAY® LAN CONFIGURATION (FOR ADVANCED USER ONLY)
Please check your Network settings before you make any changes.
By default, the BeanGateway® is configured with a static IP address: 192.168.4.123. This allows the user to quickly connect the Beangateway® to a PC.
If the user wants to set the BeanGateway® IP on the business network and get a dynamic IP address (via DHCP), you can configure the BeanGateway® from a serial port or from the Ethernet.
Go on your Beangateway® profile and click on Tools, then click on Beangateway® Ethernet/LAN Config.(BeanScape® version superior to 1.24.1296.8).
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 25 / 59
A new window will open called Beangateway® configuration / Beangateway Ethernet/LAN Config depending on the BeanScape version you use.
DHCP Enabled: Check this box if you want to enable the DHCP. For further information about DHCP read section: “What is DHCP?”.
If DHCP is not enabled, the user must configure the Beangateway® IP parameters:
IP Address: BeanGateway® IP Address. The BeanGateway® IP address should have the following format: “X.Y.Z.B“. With A, B, X, Y and Z numbers between 0 and 255
Subnet mask: mask of the network.
IP address of your BeanGateway®
Subnet network mask
Subnet Gateway IP Address
DHCP Enabled (if the case checked)
BeanScape®/ PC Socket Port
BeanScape® / PC IP Address
Select the Serial Port on your PC
Keep alive Timeout (ms)
Keep alive interval (ms)
Keep alive max retry
UDP Port
Localize devices connected to the LAN router
Choose the configuration Port: Serial Port or Ethernet
DNS Enabled (if the case is checked)
BeanScape® Domain name (if DNS is enabled)
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 26 / 59
Gateway IP Address: The network router IP address. It should have the following format “X.Y.Z.1”. If the BeanGateway® and the BeanScape® are on the same sub network, this value has no effect;
DNS Enabled: Check this box if you want to enable the DNS. For further information about DNS read the read section 2.1 of this document: “What is DNS ?”.
If DNS Server IP is given by the DHCP server, check DNS IP Auto, else DNS Sever IP must be fulfilled.
BeanScape configuration :
Port: By default the communication port used is «5313". This port is generally free, if not choose another Socket Port. The socket port must be the same for the BeanScape® and BeanGateway®. (sees Section TCP Port configuration (for experts user only)).
BeanScape® Domain Name must be fulfilled if DNS is enabled.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 27 / 59
8.1.1 Configuration from serial Port
For this operation, a serial RS232 cable as well as a serial port is needed. A configuration from a serial port is more secured; you can “locally” configure your LAN parameters on your BeanGateway®.
If you don’t have a RS232 port on your PC, use an USB/RS232 converter (provided as an option by Beanair):
RS232 Cable
BeanScape® BeanGateway®
Step 1
•Connect the serial cable to both your PC and your BeanGateway®
•Open the "Beangateway® configuration" window
Step 2
•Choose Serial port for LAN Network configuration option
• Select the serial Port connected to the BeanGateway®
Step 3
•Start configuring LAN parameters your BeanGateway® (DNS, DHCP, IP ...)
•Click on validate in order to validate your configuration
Step 4•Configuration will be acked if the operation is successful
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 28 / 59
8.1.2 Configuration from Ethernet
A configuration via the Ethernet link can be done. This operation offers more flexibility than a configuration via the RS232. The configuration can be done either directly or through the local network, as shown in the diagrams below.
Ethernet Cable
BeanScape®
BeanGateway®
Ethernet Cable
BeanScape®
BeanGateway®
LAN SWITCH / HUB
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 29 / 59
Step 1•Connect the BeanGateway® to your PC or to a LAN Switch
•Open the "BeanGateway® configuration" window
Step 2•Choose "Ethernet" for LAN Network configuration option
•Select the IP Address of your Ethernet interface on your PC
Select configuration with Ethernet
Choose the IP of your Ethernet card
Click on Localize in order to scan all the BeanGateway® present on your network
List of BeanGateway localized on your LAN Network
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 30 / 59
Step 3
•Click on "localize" in order to scan all the BeanGateway® present on your network. BeanGateway® localization starts. When this process is done, a new window occurs"localization finished"
•A list of BeanGateway® present on the LAN Network is updated
A new window occurs, the scan is finished
List of BeanGateway® present on the LAN Network
BeanGateway® Location starts
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 31 / 59
You will not succeed in localizing your BeanGateway® if it is on another subnetwork than your BeanScape®, i.e if there is a LAN Router between them.
Step 4
•Select the BeanGateway® which must be configured
•Start configuring the BeanGateway® LAN features ("TCP/IP Configuration" frame)
•Click on "validate" button (TCP/IP Configuration frame) in order to validate your configuration
BeanScape®
BeanGateway®
LAN Router
SubNetwork 1
SubNetwork 2
IP /DNS/DHCP Configuration is not possible
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 32 / 59
8.2 BEANSCAPE CONFIGURATION
8.2.1 LAN configuration (for advanced users only)
The BeanScape LAN configuration is given by the PC LAN default configuration. To change the LAN configuration, you should change you LAN parameters on Windows.
To do this, please have a look in the troubleshooting section: Troubleshooting
If your computer has two or more networks interfaces, you can equally connect BeanGateway® to each interface, but you must ensure that BeanGateway® is well configured, i.e. that it is configured with the interface IP address that it is connected to (directly or indirectly).
8.2.2 TCP Port configuration (for expert users only)
The default port used for communication between BeanScape and BeanGateway is the 5313 port. This port is generally free, but if not, you can choose another Port.
To change this configuration:
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 33 / 59
Changing this parameter involves changing the BeanGateway configuration. Please refer to this section.
8.3 KEEP ALIVE CONFIGURATION
8.3.1 BeanGateway® side
BeanGateway® Keep Alive configuration can be performed in the same window. You can enable or disable this feature by checking/unchecking the check box.
Step 1•Go to your Beangateway® profile and click on Tools, then click on Options
Step 2
•In the TCP/IP section, you can change the “Tcp port to listen”
•Apply the changes and save
Step 3
•If the server was previously started, stop it and start again, if else then just start the server.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 34 / 59
If the “KeepAlive” feature is enabled, Keep Alive Timeout / Interval and retry number can be configured:
Timeout is the time the BeanGateway® may wait before it sends a KeepAlive frame.
Interval is the time duration between two successive “ keepalive” retransmissions, (In case if no response to the first “Keepalive” has been issued from the target).
Max retry nbr is the number of KeepAlive frame transmissions retrieval to be carried out before closing the Ethernet socket (= the internet link is broken between the BeanGateway® and the BeanScape®).
Click on Validate in order to validate your configuration, a window will appear “Config is Acked”
A new window appears, your new configuration is ACKED
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 35 / 59
8.3.1 BeanScape® side
Click on the tab “Tools” then “Options”
If the “KeepAlive” feature is enabled, Keep Alive Timeout / Interval and retry number can be configured:
Timeout is the time the BeanScape® may wait before it sends a KeepAlive frame.
Interval is the time duration between two successive “ keepalive” retransmissions, (In case if no response to the first “Keepalive” has been issued from the target).
Max retry nbr is the number of KeepAlive frame transmissions retrieval to be carried out before closing the Ethernet socket (= the internet link is broken between the BeanGateway® and the BeanScape®).
Click on Apply then Save in order to validate your configuration.
BeanScape® keep alive configuration
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 36 / 59
8.4 SECURITY OPTION: DEACTIVATE BEANGATEWAY® LAN CONFIGURATION VIA ETHERNET
By default, the BeanGateway® can be configured equally via Serial Port or Ethernet as shown in the section 4.1. For a better network security, the end user can disable the LAN configuration via Ethernet. Then, the only possible way to configure your BeanGateway® will be to use a Serial Port.
For this operation, a serial RS232 cable as well as a serial port is needed. A configuration via a serial port is more secured; the user can “locally” configure the LAN Network parameters on his BeanGateway®.
If you don’t have a RS232 port on your PC, use a USB/RS232 converter (provided as an option by Beanair):
Step 1
•Connect your PC to your BeanGateway® through the serial cable
•Open the "Beangateway configuration" window
Step 2•Choose Serial port for LAN Network configuration option
• Select the serial Port connected to the BeanGateway®
Step 3
•In the Configuration via Ethernet Box, uncheck "Enabled"
•Click on validate in order to validate your configuration
Step 4•Configuration will be ACKED if the operation is successful
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 37 / 59
9. MULTI-WSN CONFIGURATION
Figure 1 : A multi-WSN architecture
These settings are mandatory:
PAN ID should be different between each BeanGateway®
These settings are highly recommended:
The distance between each BeanGateway® should be at least 2 meters;
Each BeanGateway® should use different Radio channel;
2 2
Ethernet/LAN
AX-3D
HI-INCSensor Cloud n°2
Premium+
AX-3D
HI-INCSensor Cloud n°3
AX-3D
HI-INCSensor Cloud n°1
Ethernet/LAN
Ethernet/LAN
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 38 / 59
10. INTERFACING THE BEANGATEWAY® WITH A 3G/4G ROUTER
See “Remote access to a Wireless Sensor Network” Youtube video
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 39 / 59
10.1 MATERIAL REQUIREMENT
BeanGateway® version BeanGateway® Ethernet
3G Gateway
TECHNOLOGY • HSUPA with fallback to: HSDPA, UMTS, EDGE Bands Tri-Band UMTS/HSDPA/HSUPA 850, 1900, 2100 MHz Or Quad-Band UMTS/HSDPA/HSUPA 850, 900, 1900, 2100 MHz HOST INTERFACES Ethernet: 10/100 BASE-T RJ-45 APPLICATION INTERFACES TCP/IP, UDP/IP, DHCP, HTTP, SNMP, SMTP, SMS, MSCI
ADSL Modem ADSL Modem with NAT Configuration software
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 40 / 59
10.2 NETWORK CONFIGURATION
10.2.1 BeanGateway® Configuration
BeanGateway® IP Address
A static IP Address is assigned to the BeanGateway®
The IP is assigned by the 3G Router (A DHCP server is available on the 3G
Router)
Example: 192.168.0.100 Assigned by the 3G router
Sub Network Mask Specify the default Sub Network Mask value : 255.255.255.0
Assigned by the 3G router
Default Gateway IP Specify the IP address of your 3G router
Example : 192.168.0.1
Assigned by the 3G Router
DHCP Configuration DHCP should be deactivated DHCP should be activated
Co
nfi
gu
rati
on
fo
r B
ean
Sca
pe®
co
mm
un
ica
tio
n
Pu
blic
IP A
dd
ress
(IP
Ad
dre
ss o
f th
e A
DSL
M
od
em)
Specify the Public IP address of your ADSL Modem Ex: 178.18.20.123
Make sure that the Public IP Address is not renewed by your provider, otherwise you can lose the connection between the 3G Router and the BeanScape® software application.
Pu
blic
PO
RT
Specify your Public PORT
Example : 5314
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 41 / 59
Keep Alive configuration
Due to a random time response of a 3G Network, it’s highly recommended to configure a high value on the Keep Alive. We recommend to use the following values :
Timeout 300.000 ms ( 5 minutes )
Interval 60.000 ms ( 1 minute )
Max Retry nbr. : 5
It’s difficult to guarantee the time response of a 3G network, this parameter depends highly the Quality of service of your telecom provider.
Example 1: Static IP Assigned to the BeanGateway®
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 42 / 59
10.2.2 ADSL MODEM (NAT ROUTER configuration)
Public IP The Public IP should be static. Ask to your chief information officer (CIO) your IP address.
Port forwarding
Use the port forwarding tool of your ADSL Modem to translate the Public PORT and Private PORT.
Redirect the PORT declared on your gateway to your BeanScape Address
Example: An Example of PORT Forwarding
BeanScape Private PORT (declared on the BeanScape®) : 5313
IP address of your BeanScape: 192.168.1.22
Public PORT declared on the BeanGateway : 5314
For further information, please read the user manual of your ADSL Modem.
Private Port ( declared on
the BeanScape)
Public Port ( declared on
the BeanGateway)
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 43 / 59
For further about the IP config on your PC, read this section “How can I get the IP configuration on my PC”
10.2.3 BeanScape® (PC ) Configuration
Private PORT Specify your PRIVATE Port. By Default, the port is fixed at 5313 on your BeanScape.
Private Address
IP Address of your PC where the BeanScape® is installed, this address should be affected by your DHCP Server.
Make sure that the IP Address of your PC is always the same. If you are not sure, we suggest you to use a static IP Address.
Example: 192.168.1.100
Keep Alive configuration
Due to a random time response of a 3G Network, it’s highly recommended to configure a high value on the Keep Alive. We recommend to use the following values :
Timeout 300.000 ms ( 5 minutes )
Interval 60.000 ms ( 1 minute )
Max Retry nbr. : 5
It’s difficult to guarantee the time response of a 3G network, this parameter depends highly the Quality of service of your telecom provider.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 44 / 59
Example:
Important: Click on “Apply” then “Save”.
10.2.4 3G/4G Modem Configuration
Sim card configuration
The user should configure the APN, Login, Password and PIN code.
IP Config of the Ethernet PORT
Configure the IP Address of your 3G/4G Modem.
For further information, please read the user manual of your 3G/4G Router.
Configure your Private PORT
Configure the Keep Alive
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 45 / 59
10.3 EXAMPLE: TELTONIKA RUT950 3G/4G MODEM
In the following example, we’ll show you how to interface the Teltonika RUT950 3G modem with our WSN application.
On site, the BeanGateway should connected to the Teltonika 3G/4G modem via Ethernet cable. I need to monitor this WSN installation from my office.
Make sure there is 3G/4G network coverage in your area.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 46 / 59
On site:
BeanGateway
BeanDevices
Teltonika 3G/4G modem
Laptop (for quick configuration)
BeanScape application
In my office:
ADSL Modem
PC
BeanScape application
In order to establish a port forward, please refer to the steps below:
1) In my office:
a) Determine the Public IP address of your ADSL router. You can use Google:
b) Determine your private IP address:
i) Open a command window: Start Window -> cmd
ii) Type: ipconfig
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 47 / 59
iii) My private IP address is: 192.168.1.8
c) Check BeanScape application port: Tools -> options:
d) Create a NAT virtual server: Write down 192.168.1.1 in a tab on your internet browser, then add a port forward:
Server IP Address 192.168.1.8
External Port Start 5313
External Port End 5313
Protocol TCP
Internal Port Start 5313
Internal Port End 5313
Enable NAT Loopback Yes
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 48 / 59
Note: It’s recommended to do the aforementioned steps on site using TeamViewer. Therefore, you can check if the fort forward has been established successfully or not.
See “Remote access to a Wireless Sensor Network” Youtube video
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 49 / 59
2) On the site: Open BeanScape. Tools -> Beangateway Ethernet/LAN config Localize your BeanGateway then enter your ADSL router public IP address for BeanScape. Also check if the port is the same as configured on your router.
3) In my office again:
Open BeanScape then start server.
Check that your Firewall is disabled or BeanScape is added as an exception then start server:
Note: Please make sure that your IP addresses are static on both sides.
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 50 / 59
11. TYPICAL NETWORK CONFIGURATION EXAMPLES
In this section you can find some examples of network configurations that you can set up. The IP address and Subnet mask given in those examples can be changed to fit your own architecture. If static IP configuration is used, be sure to set the right subnet mask regarding your network IP address system.
11.1 BEANSCAPE® AND BEANGATEWAY® CONNECTED THROUGH DIRECT ETHERNET LINK
Watch the video
BeanScape®
BeanGateway®
IP staticX.Y.Z.A
IP staticX.Y.Z.B
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 51 / 59
The PC running the BeanScape® must have a static IP configured on its Network interface:
IP address: 192.168.4.2
Subnet mask: 255.255.255.0
Default Gateway not necessary
DNS Server addresses not necessary
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 52 / 59
The BeanGateway® will be configured with a static IP address
IP address: 192.168.4.123
Subnet mask: 255.255.255.0
Default Gateway will not be used but can be filled
BeanScape IP address must be the same as the one defined above
BeanScape Port must be the same than the one defined in your BeanScape options
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 53 / 59
11.2 BEANSCAPE® AND BEANGATEWAY® CONNECTED TO A LAN NETWORK WITHOUT DHCP SERVER
BeanScape®
LAN switch(No DHCP Server)
BeanGateway®
IP staticX.Y.Z.A IP static
X.Y.Z.B
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 54 / 59
Assign a static IP address on the PC running the BeanScape® :
IP address: 10.0.0.3
Subnet mask: 255.0.0.0
Default Gateway not necessary
DNS Server addresses not necessary
Assign a static IP Address on your BeanGateway®:
Enter your IP address (example: 10.0.0.4)
Enter the subnet mask: 255.0.0.0
Default Gateway will not be used but can be filled
Your PC IP Running the BeanScape® must be the same than the one defined above
BeanScape® Port must be the same than the one defined in your BeanScape options
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 55 / 59
11.3 BEANSCAPE® AND BEANGATEWAY® CONNECTED ON A LAN NETWORK WITH DHCP SERVER
Choose the “option obtain an IP address automatically” on your PC
BeanScape®
LAN switch
BeanGateway®
IP allocated by DHCP Server
X.Y.Z.AIP allocated by DHCP Server
X.Y.Z.B
LAN Router withDHCP Server
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 56 / 59
Configure the BeanGateway® with a dynamic IP address
DHCP enabled
Enter the IP address of your PC running the BeanScape®
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 57 / 59
12. TROUBLESHOOTING
12.1 HOW CAN I GET THE IP CONFIGURATION ON MY PC?
Open up your windows start menu and Type cmd in the “Search programs and files box” and press Enter on your keyboard. This will call the Windows command prompt window.
The IP Address can be finded by launching DOS command Window and entering the console application IPconfig. This application displays all current TCP/IP network configuration values and can modify Dynamic Host Configuration Protocol DHCP and Domain Name System DNS settings.
I
IP config command
IP Address of your PC
“Rethinking sensing technology” Document version : 1.4
BeanGateway management on a LAN and 3G infrastructure Document Type : Technical Note
Please consider the environnement before printing this document.
Page : 58 / 59
12.2 HOW CAN I MODIFY MY PC NETWORK INTERFACE CONFIGURATION?
Please visit Microsoft support pages that will show how you can access and modify your PC interface configuration.
http://windows.microsoft.com/en-US/windows7/Change-TCP-IP-settings