Flexitron Webdyn WebdynModbus User manual

WebdynModbus
User Manual
www.webdyn.com

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
2
Index
User Manual ..................................................................................................................... 5
1. Glossary................................................................................................................................................. 5
2. About this Document............................................................................................................................ 6
2.1 Scope ........................................................................................................................................ 6
2.2 Target Audience........................................................................................................................ 6
2.3 Product Versions ...................................................................................................................... 6
2.4 Safety advice ............................................................................................................................ 6
3. Principles of Operation......................................................................................................................... 7
3.1 ...................................................................................................................................................
Overview Diagram of a Comprehensive Monitoring Solution ...................................................... 7
4. Unit Characteristics .............................................................................................................................. 8
4.1 Technical Characteristics......................................................................................................... 8
4.2 List of Available Interfaces ...................................................................................................... 9
4.3 Optional Accessories................................................................................................................ 9
4.3.1 DIN Rail Power Supply................................................................................................ 9
4.3.2 GSM/GPRS Right-Angled Stub Antenna ................................................................... 12
4.3.3 GSM/GPRS Externally Mounted Antenna (optional) ................................................ 12
5. Prerequisites ......................................................................................................................................... 13
5.1 Access to the FTP Server ......................................................................................................... 13
5.2 Access to the NTP Server ........................................................................................................ 14
5.3 Connection via GPRS or Ethernet ........................................................................................... 14
5.3.1 Ethernet Connection................................................................................................... 14
5.3.2 GPRS Connection ....................................................................................................... 14
5.3.3 Managing the PIN Code for the SIM Card................................................................. 14
6. Gateway Conguration.......................................................................................................................... 16
6.1 Role of the Conguration Files ................................................................................................ 16
6.1.1 Conguration Files...................................................................................................... 16
6.1.2 Denition Files ............................................................................................................ 17
6.2 Initialization .............................................................................................................................. 17
6.2.1 Conguration via the Built-in Web Server ................................................................. 20
6.2.2 Conguration via SMS................................................................................................ 26

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
3
6.3 Setting the Unit Date and Time............................................................................................... 27
6.4 Connection Modes and Period................................................................................................ 28
6.4.1 Manual Connection .................................................................................................... 29
6.4.2 Periodic Automatic Connection ................................................................................. 29
6.4.3 Automatic Connection at Fixed Times....................................................................... 30
6.4.4 Automatic Connection on Data Capture ................................................................... 31
6.4.5 Keeping the Connection Open .................................................................................. 32
6.4.6 Automatic Connexion on Alarm ................................................................................. 32
6.4.7 Optimizing the Connection......................................................................................... 33
6.5 Acquisition Period and Time Slots........................................................................................... 33
7. Modbus Device Management .............................................................................................................. 35
7.1 ................................................................................................................................................... Bus
Wiring............................................................................................................................................... 35
7.2 Conguring and Declaring Modbus Slave Devices................................................................. 36
7.3 Structure of a Modbus Denition File ..................................................................................... 39
7.4 Checking that Modbus devices are operating correctly......................................................... 45
7.5 Modbus Data ............................................................................................................................ 45
7.5.1 Filename Syntax.......................................................................................................... 45
7.5.2 Data Format ................................................................................................................ 46
7.5.3 Example....................................................................................................................... 48
7.6 Modbus Alarms......................................................................................................................... 51
7.6.1 Alarm Filename Syntax............................................................................................... 51
7.6.2 Format of Alarms ........................................................................................................ 52
7.6.3 Example of Alarm Files ............................................................................................... 52
7.7 Writing Modbus Variables via a Command File...................................................................... 54
8. Updating the Unit.................................................................................................................................. 55
8.1 Updating via the Web Server................................................................................................... 55
8.2 Updating Remotely via the FTP Server ................................................................................... 56
9. Using Web Services .............................................................................................................................. 57
9.1 Enabling and Conguring......................................................................................................... 57
9.2 Format of HTTP Requests........................................................................................................ 57
9.3 Examples of Web Services Requests...................................................................................... 61

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
4
10. Tools and Diagnostics ........................................................................................................................ 62
10.1 Events Journal........................................................................................................................ 62
10.2 Modem Information............................................................................................................... 65
10.3 Detecting Power Connection ................................................................................................. 66
10.3.1 Syntax of the Alarm File Name ................................................................................ 66
10.3.2 Format of Alarms...................................................................................................... 66
10.4 LED Indicators ....................................................................................................................... 67
10.5 Installation Button ................................................................................................................. 69
10.6 Diagnostic SMS...................................................................................................................... 69
10.7 Debug Traces ......................................................................................................................... 70
10.8 Factory Reset Procedure ...................................................................................................... 71
Sales Contact ................................................................................................................... 73

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
5
User Manual
1. Glossary
NAME DESCRIPTION
APN Access Point Name: name of the access point that enables the gateway to
connect to the Internet via a mobile link.
ERDF Électricité Réseau Distribution France, the French National Grid, which denes
connection norms for installations and meters, especially smart meters. See TIC.
FTP File Transfer Protocol: communications protocol used to share data les on a
TCP/IP network.
GPRS General Packet Radio Service: standard for mobile telephone communications
derived from the GSM standard and enabling higher data transfer rates. Also
known as 2.5G.
DL: maximum 86 kbps; UL: maximum 43 kbps
GSM Global System for Mobile Communications: the switched network for mobile
telephones.
HTTP HyperText Transfer Protocol: client-server communications protocol developed for
the Web.
IP Internet Protocol: message protocol controlling the addressing and transmission
of TCP packets over the network.
DIN Rail Standardised 35-mm metal rail used in Europe for rack-mounted industrial
control equipment.
PSTN Public switched telephone network: switched network for telephone land lines.
TCP Transmission Control Protocol: a connection-oriented protocol for the Internet,
which provides data segmentation into packets that are transmitted over the
network via the IP protocol. This protocol provides a reliable data transfer
service. See also IP.
TCP/IP Transmission Control Protocol/Internet Protocol: the suite of network protocols
that provide interconnection services between computers with different
hardware architectures and operating systems. TCP/IP includes standards for
communication between computers and conventions for network interconnection
and for routing.

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
6
2. About this Document
The purpose of this guide is to describe the installation and operation of a WebdynModbus gateway.
2.1 Scope
The present technical description is valid for WebdynModbus gateways from hardware version 1 onwards,
and from software version V3.04.17 and up.
2.2 Target Audience
This guide is intended for users of WebdynModbus gateways.
2.3 Product Versions
Version 1.0.
2.4 Safety advice
It is essential to respect all safety recommendations featured in this guide.
Failure to comply with these recommendations may cause damage to equipment and danger to the
health safety of personnel.
Electrical connections
• All wiring must be carried out only by a specialized qualied electrician.
• Prior to installation, all equipment connected to the corresponding communications bus must
be disconnected on both sides (DC and AC).
The WebdynModbus unit is liable to damage from electrostatic discharge (ESD). Avoid all contact
with component connectors and terminals.

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
7
3. Principles of Operation
The WebdynModbus gateway is the communications hub for your Modbus installation. It continuously
collects desired data from Modbus equipments, concentrates this data into les, and sends these les to
a remote FTP server. In doing so, this gateway enables you to be constantly informed on the operational
state of your installation.
3.1 Overview Diagram of a Comprehensive Monitoring Solution
Inverters
Ethernet/
4G/3G/2G
Modbus
equipment
WebdynModbus
Meters
Sensors
Server User
Modbus
Modbus
Modbus
Modbus
888888
W
ebdynModbu
s

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
8
4. Unit Characteristics
4.1 Technical Characteristics
ELECTRICAL CHARACTERISTICS
Input tension 12 / 24 V
Electricity consumption when idle 1.6 W (1)
Electricity consumption when connected via Ethernet 2 W (1)
Maximum peak power during GPRS connection 3 W (1)
GSM/GPRS antenna: Microel EA-247
Frequency 900/1800 Mhz
Gain 0 dB
Polarisation Vertical
MEMORY
Storage capacity 100 MB of compressed data
Dimensions
Size 70mm*86mm*59mm
(L,h,p) , RAIL DIN
ENVIRONMENTAL CONDITIONS
Operational temperature range -5°C à +55°C
Storage temperature -5°C à +45°C
(1) Measurements carried out on the Unit + DIN Rail DR15-24 power supply assembly

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
9
4.2 List of Available Interfaces
DATA SOURCE INTERFACE CHARACTERISTICS
Modbus equipements RS485 2/4 wires, Ethernet Maximum number 247
COMMUNICATIONS CHANNEL PROTOCOL
Ethernet 10/100Mbits/s IP services
GSM/GPRS modem IP services
REMOTE SERVERS PROTOCOL
FTP server FTP
HTTP server (Web Services option) HTTP
NTP server NTP
4.3 Optional Accessories
4.3.1 DIN Rail Power Supply
Brand: MEANWELL; reference No.: DR-15-24
This power supply unit is mounted next to the gateway on the standard 35-mm DIN RAIL metal rail. This
rail mounting means that no other mounting bracket is required.

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
10
Characteristics:
OUTPUT DC VOLTAGE 24V
RATED CURRENT 0.63A
CURRENT RANGE 0 ~ 0.63A
RATED POWER 15.2W
RIPPLE & NOISE
(max.) Note.2
150mVp-p
VOLTAGE ADJ.
RANGE
21.6 ~ 26.4V
VOLTAGE
TOLERANCE Note.3
±1.0%
LINE REGULATION ±1.0%
LOAD REGULATION ±1.0%
SETUP, RISE TIME 1000ms, 50ms/230VAC; 1000ms, 50ms/115VAC at
full load
HOLD UP TIME
(Typ.)
70ms/230VAC; 16ms/115VAC at full load
INPUT VOLTAGE RANGE 85 ~ 264VAC 120 ~ 370VDC
FREQUENCY
RANGE
47 ~ 63Hz
EFFICIENCY (Typ.) 85%
AC CURRENT (Typ.) 0.88A/115VAC; 0.48A/230VAC
INRUSH CURRENT
(Typ.)
COLD START 35A/115VAC; 65A/230VAC

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
11
PROTECTION OVERLOAD Note.5 105 ~ 160% rated output power; Protection type:
Constant current limiting, recovers automatically after
fault condition is removed
OVER VOLTAGE 27.6 ~ 32.4V
ENVIRONMENT WORKING TEMP. -20°C ~ +60°C (Refer to output load derating curve)
WORKING
HUMIDITY
20 ~ 90% RH non-condensing
STORAGE TEMP.,
HUMIDITY
-40°C ~ +85°C, 10 ~ 95% RH
TEMP.
COEFFICIENT
±0.03%/ (0 ~ 50) °C)
VIBRATION 10 ~ 500Hz, 2G 10min./1cycle, period for 60min.
each along X, Y, Z axes; Mounting: Compliance to
IEC60068-2-6
SAFETY & EMC SAFETY
STANDARDS
UL60950-1, TUV EN60950-1 approved, design refer
to EN50178
WITHSTAND
VOLTAGE
I/P-O/P: 3 KV AC
ISOLATION
RESISTANCE
I/P-O/P: 100 megohm / 500 V DC / 25 / 70% RH
EMI CONDUCTION
& RADIATION
Compliance to EN55011, EN55022 (CISPR22),
EN61204-3 Class B
HARMONIC
CURRENT
Compliance to EN61000-3-2, -3
EMS IMMUNITY Compliance to EN61000-4-2, 3, 4, 5, 6, 8, 11,
ENV50204, EN55024, EN61000-6-2, EN61204-3,
heavy industry level, criteria A
OTHERS MTBF 1172.3K hr min. MIL-HDBK-217F (25 )
DIMENSION 25*93*56mm (W*H*D)

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
12
4.3.2 GSM/GPRS Right-Angled Stub Antenna
Characteristics:
Frequency range 900-1800 MHz
4.3.3 GSM/GPRS Externally Mounted Antenna (optional)
Characteristics:
Cable: RG-58
Cable length: 5,10 or 20 meters available
Frequency ranges 824-960 MHz; 1710-1990 MHz
Options Mounting bracket

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
13
5. Prerequisites
It is crucial for the WebdynModBus to have an internet access, either Ethernet or GPRS, in order to
enable le transfers between the gateway and a congured remote server, to enable the synchronization
of the gateway’s internal clock with the one’s of general purpose systems.
As mentioned above, the gateway exchanges les, of different types containing categorized information,
with an off-board FTP server.
• Alarm, data, log, and debug les must be uploaded by the gateway to the remote server for user
access to this information.
• Update and command les can be downloaded by the gateway from the remote server to take
into account new functionalities and bug xes comprised in new rmware versions and for the
user to transmit commands to the gateway.
• Conguration and denition les can be uploaded and downloaded by the gateway to/from the
remote server to give read and/or write access to the gateway’s conguration.
In addition, the factory default time and date setting of the gateway is 1st January 1970 at 00:00, known
as EPOCH time. In order for the gateway’s time to be synchronized with the time of other systems it must
communicate with an NTP server from which it receives UTC time.
Precisions on these prerequisites are listed below.
5.1 Access to the FTP Server
It is essential that the remote FTP server is congured the following way:
• Read/Write/Rename access authorized
• Passive mode enabled
• Port 21 (by default)
• Short handshake message
• Login and Password must be less than 30 characters
As the WebdynModbus gateway does not create any directories on the remote FTP serverthese must be
manually created by the user or the person in charge of the Information System used by the gateway.
Below is the list of directories which MUST be present on the remote FTP server. These directories don’t
however have to be at the root of the FTP server, a parent directory can be created as long as the path of
the directories below is manually updated in the gateway’s conguration:
• /ALARM: Contains the alarm les./BIN: contains binary les of the gateway for update purposes.
• /CMD: Contains the command and acknowledgement les.
• /CONFIG: Contains the conguration les for the gateway.
• /DATA: Directory for upload of data les. This directory contains four subdirectories:
• /MODBUS: Modbus data.
• /DEF: Contains the denition les for the modules and sensors to be controlled. This directory

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
14
contains the subdirectory:
• /MODBUS: Denition les for the monitored Modbus modules.
• /LOG: Contains the gateway’s system logs (IDSite_DATE.log) and the debug logs,disabled by
default (IDSite_DATE_debug.log).
5.2 Access to the NTP Server
To set its date and time correctly to UTC time, the WebdynModbus synchronises itself with an NTP server
before each connection to the FTP server. By default, the gateway is congured to get the time from
the NTP server “pool.ntp.org”. As this NTP server is accessible only via Internet, the gateway must have
operational Internet access (UDP port 123 must be open for outgoing trafc) for synchronisation to occur.
5.3 Connection via GPRS or Ethernet
Access to the FTP and NTP servers can be done either via an Ethernet connection or a GPRS connection.
5.3.1 Ethernet Connection
For connection to Internet via Ethernet, the following conguration parameters must be correctly informed
to the gateway:
• IP address of the WebdynModbus on the local network (factory IP address: 192.168.1.12)
• Subnet mask
• IP address of the router or ADSL modem
• IP address of the DNS server
5.3.2 GPRS Connection
For connection via GPRS, it is essential to insert an activated SIM card with a DATA option in the gateway,
and to inform it with the following information correctly:
• APN (Access Point Name): Name of the GPRS access point. This depends on the operator and
the type of subscription
• User name and password for connection to the APN
5.3.3 Managing the PIN Code for the SIM Card
The WebdynModbus handles the SIM card’s PIN code automatically, the PIN code cannot be informed to
the gateway. The SIM card must therefore either have no PIN code or have a PIN code set to 0000 when
it is rst inserted.
The management of the SIM card’s PIN code is as follows:
• If the PIN code is deactivated: GPRS communication is operational for the gateway.

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
15
• If the PIN code is activated and equal to “0000”: when the gateway is red up for the rst
time, a new PIN code is attributed to the SIM card. This PIN code is dened on the basis of the
ICCID (Integrated Circuit Card Identication) number of the SIM card installed. It is calculated
using a proprietary Webdyn algorithm. This feature allows fraudulent use of the SIM card to be
prevented, while providing ease of use.
• If the PIN code is activated and different to “0000”: GPRS communication is not operational
for the gateway.
In addition, this same SIM card can be reused in another WebdynModBus, WebdynSun, WebdynPulse,
or WebdynTIC unit without any additional conguration. If the card has a PIN code that is activated but
is neither “0000” nor the code attributed by the WebdynModBus gateway, communications (including
SMSs) will not be operational.
Never insert a SIM card with an activated PIN code that is neither “0000” nor a value attributed
by a WebdynModBus, WebdynSun, WebdynPulse, or WebdynTIC. If you do so, the SIM card will be blocked
and the user will have to unblock it by entering the PUK code manually.

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
16
6. Gateway Conguration
Conguration of the WebdynModbus gateway should be carried out in several stages. The rst stage,
Initialization, consists of conguring the WebdynModbus gateway so that it can connect to the FTP
server. This can be either via the web interface, accessible by connecting the gateway to a PC or local
network via Ethernet, or via SMS. The second stage consists of conguring the gateway remotely via the
previously congured FTP server. During this stage, it is possible to modify the whole set of conguration
parameters via the les available on the server, including the ones concerning ModBus equipments. For
these equipments it is necessary to modify the prex_daq.ini le and to create a denition le for the
addressing of the variables.
6.1 Role of the Conguration Files
Except for the locally, and remotely via SMS, accessible parameters enabling connection to the remote
FTP server, the totalityof the conguration parameters are accessible via conguration les available on
the said server.
Each conguration le is prexed with a unique identier:the “prexID”. This prex enables the
conguration for each gateway connected to a given server to be customised. Two categories of les are
necessary for conguring the unit: the conguration les and the denition les.
The WebdynModbus gateway does not overwrite the conguration and denition les available on
the server. Care must be taken to maintain consistency between the conguration of the gateway and the
les on the server. Where the conguration is modied locally, it is advisable to delete the les from the
server so that the gateway will recreate them. Conversely, if one of the les on the server is modied, the
gateway detects this and will download it. The standard conguration of the gateway is thus overwritten.
6.1.1 Conguration Files
The WebdynModbus has three conguration les:
• prexID_cong.ini: this contains the general parameters of the WebdynPulse
• prexID_daq.ini: this contains the parameters required for data acquisition
• prexID_var.ini: this contains the information for scheduling connection and data acquisition
times
These 3 les are contained in the conguration directory on the FTP server. By default, this directory is
“/CONFIG”, but can be modied by means of the variable “FTP_DirCong” in the le prexID_cong.ini.
If the gateway does not detect these les on the FTP server, it creates them from its current conguration.
Furthermore, at every connection to the server, the gateway checks the modication dates and sizes of
the les to detect any modication(s) on a given le. Should a modication be detected, the gateway
downloads the new le.
The details of each parameter in the conguration les will be explained as required in the remainder of
this documentation.

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
17
6.1.2 Denition Files
The role of the denition le is to inform the gateway on the data which it will be reading/writing on the
Modbus slave as well as how the gateway will access this data.
The link between the denition les and the gateway is provided via the conguration le prexID_daq.
ini. The format of the denition les, including a section dening the requests to be sent and another
describing the variables which are to be written/read is described in chapter 7.3 “Structure of a Modbus
denition le”.
6.2 Initialization
Initial conguration of the unit is necessary to enable connection to the remote FTP server. This
conguration can be carried out either via the on-board Web Server or by SMS if a functional SIM card
has been inserted in the gateway.
Local conguration of the WebdynModbus affects only the variables in the conguration le: prexID_
cong.ini.
Here is a list of the variables accessible via the local web interface (http) and/or via SMS commands:
VARIABLE DEFINITION DEFAULT
VALUE HTTP SMS
ID Gateway identier (up to 29
characters)
WDxxxxxx where
xxx… is the last 6
digits of the MAC
address
X
LAN_IpAddr IP address of the gateway
(router) on the LAN (local
area network)
Communication via Ethernet
(up to 15 characters)
192.168.1.12 X
LAN_SubnetMask LAN subnet mask
Communication via Ethernet
(up to 15 characters)
255.255.255.0 X
LAN_Gateway Address of the gateway
(router) on the LAN
Communication via Ethernet
(up to 15 characters)
0.0.0.0 X

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
18
LAN_DNS Address of the DNS server
on the LAN
Communication via Ethernet
(up to 15 characters)
0.0.0.0 X
LAN_DHCP_Enable Enable/Disable DHCP:
for automatic provision of
Ethernet IP addresses.
0=Disabled; 1=Enabled
0 X
GPRS_APN GPRS Access Point Name
(APN)
Provided by mobile operator
(up to 29 characters)
m2minternet X X
GPRS_Login GPRS APN identier
Provided by mobile operator
(up to 29 characters)
sfr X X
GPRS_Password GPRS APN password
Provided by mobile operator
(up to 29 characters)
sfr X X
GPRS_PhoneNumber Phone number for GPRS
In France: *99***1# (up to
13 characters)
*99***1# X X
FAI_PhoneNumber Phone number for PSTN
Provided by the Internet
Service Provider (ISP) (up to
13 characters)
empty X
FAI_Login PSTN identier
Provided by the ISP (up to
29 characters)
empty X
FAI_Password PSTN password
Provided by the ISP (up to
29 characters)
empty X

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
19
WAN_
ConnectionInterface
Remote server connection
interface selected:
0=Ethernet; 1=GPRS
modem
1 X
FTP_Server Name of remote FTP server
(up to 29 characters)
empty X X
FTP_Login Identier for connection to
remote FTP server (up to 29
characters)
empty X X
FTP_Password Password for connection to
remote FTP server (up to 29
characters)
empty X X
FTP_Port Port used for connection to
remote FTP server
21 X X
FTP_DirCong FTP directory name for
gateway conguration les
(up to 29 characters)
/CONFIG X
FTP_DirDef FTP directory name for
gateway denition les (up
to 29 characters)
/DEF X
FTP_DirData FTP directory name for data
les (up to 29 characters)
/DATA X
FTP_DirLog FTP directory name for log
les (up to 29 characters)
/LOG X
FTP_DirBin FTP directory name for
gateway rmware
Used for upgrading gateway
(up to 29 characters)
/BIN X
FTP_DirAlarm FTP directory name for
alarm les (up to 29
characters)
/ALARM X
FTP_DirCmd FTP directory name for
command les (up to 29
characters)
/CMD X

[e-mail] | webdyn.com
V1.0 subject to changes | Webdyn © by Flexitron Group
20
FTP_Option Enable/Disable of two-
phase data uploading.
(File with extension “.tmp”
uploaded, then extension
“.tmp” deleted after
transfer.
0=Disabled; 1=Enabled
0 X
CONFIG_ForceUpload Allow overwriting
conguration and denition
les on the server if a local
change is performed to a
le parameters concerned:
0 = Off; 1 = Enabled
1 X
WebService_Enable Enable/Disable of web
services:
0= Disabled; 1= Enabled
0 X
WebService_Url Web Service http:// address
(up to 29 characters)
X
Language Language chosen for built-in
website:
fr = French; en= English
fr X
These variables can be modied at any time on the remote server.
The server conguration always overrides the local conguration via the web interface. Please
ensure that the two congurations are consistent.
To ensure consistency between the server and the unit, it is advisable to delete the unit’s
conguration le prexID_cong.ini from the remote server before any local modication is carried out.
Thus, the gateway will upload its new prexID_cong.ini conguration le at the next connection to the
FTP server rather than downloading the one present on the remote server. This would cause any
modication brought to the conguration via the web interface to be overridden.
6.2.1 Conguration via the Built-in Web Server
Access to the built-in Web interface on the WebdynModbus gateway is provided via the gateway’s LAN
connection. An Ethernet crossover cable must be used if a direct connection is made between the
computer and the gateway. In addition, both the computer used and the gateway must belong to the
same local network. If the WebdynModbus gateway has a static IP address (the default situation), the