Technical information
3/17
Modicon M340 automation 
platform
Ethernet Modbus/TCP network
SOAP/XML Web services
SOAP/XML Web services  
BMX NOE 0110, BMX NOC 0401 Ethernet network modules and BMX NOR 0200H 
RTU modules incorporate a standard SOAP/XML data server that provides direct 
interoperability between control system devices and computer management 
applications (MES, ERP, SAP, 
pNet application, etc).
SOAP/XML Web services embedded in the PLC
These Web services conform to the W3C 
(World Wide Web Consortium) Web 
service standards. They offer standard open communication resources thanks to 
which the control peripherals can interact directly with computer management 
applications using a non-proprietary SOAP protocol.
SOAP/XML Web services are based on the following standards:
SOAP (Simple Object Access Protocol), the exchange protocol executed via the 
HTTP (HyperText Transfer Protocol) channel
WSDL (Web Services Description Language), in XML formatXML formatformat
XML 
(eXtensible Markup Language), the universal standard for data exchange
ModbusXMLDa Web services:  SOAP server interface
The implementation of ModbusXMLDa 
(Modbus XML Data access) services in 
control system device Web servers means IT engineers can easily create their own 
application to access the desired information directly in the PLC, in real time.
Applications such as Microsoft.NET, SQL Server, Microsoft Office (Excel), IBM 
(WebSphere), SUN (Java, Eclipse), Lotus, Oracle, SAP, MES, ERP, etc can interact 
directly with the PLC module Web server.
Exchanges are initiated by the SOAP client application (the server responds to these 
requests). Data exchanges are made in XML standard format in response to a request 
using the SOAP protocol.
Step 
1: Creation of the client application with learning of the Web services. 
The development environment (for example, Visual Studio 
pNET) looks in the 
FactoryCast server for the list of available services and their WSDL standard 
interfaces provided by the module.
Step 
2: Development of the client application. The developer integrates the 
Web service functions using the code retrieved at step 1 of the learning process.
Step
 3: Execution of the client application. The client application 
communicates in real time with the FactoryCast Web server module using the SOAP 
protocol.
b
b
b
b
b
b
Functions (continued)
1, 2
3
SOAP 
request 
WSDL
Visual Studio pNET
pNET Java
FactoryCast 
module
BMX NOE 0110
SOAP 
server 
Development tool
Processors:
page 1/2
I/O:
pages 2/2 and 2/14
Software:
page 4/2
Ruggedized Modicon M340 modules:
page 6/2
1
2
3
4
5
6
7
8
9
10










