M340 MODBUS TCP communicate with OPC

lijochrn

Member
Join Date
Jul 2015
Location
Seoul
Posts
31
Hello Experts,

We are currently in the design phase of a system with 24 PLC's.
CPU is BMXP342020 [ CPU onboard Serial and Ethernet ports, both capable of MODBUS]

Each PLC's are stand-alone and have communication with 9 Modbus RTU slaves.
Also, each PLC will be connected to OPC at central SCADA room via MODBUS TCP.


Questions:
Regarding Serial MODBUS RTU
1. CPU onboard RJ45 Serial port can directly make communication with all 9 slaves via multidrop? Using READ VAR/WRITE VAR function?
2. How many READ VAR/WRITE function can be used simultaneously?

Regarding MODBUS TCP
1. Which module is required for connecting to OPC?
BMX NOC 0401 or BMX NOE 0100?
Can the above two modules be connected to OPC without any programming? We need to read/write data to each CPU all the time.

2. Does BMX NOC 0401/BMX NOE 0100 need programming in PLC for communication?

3. Does CPU onboard ethernet port require programming for communicating on MODBUS TCP?

Please guide.



We have used M580 CPU in 10 projects and all the time DCS [Client] can read/write data with M580[server] without any programming. But we used CPU onboard port or BME NOC 0301.2

So does that sounds similar to BMX NOC 0401/BMX NOE 0100
 
Serial port can directly make communication with all 9 slaves via multidrop?
1a. Assuming the serial port is RS-485, then yes, RS-485 is likely to support 9 slaves. Baud rate can be limited by total bus distance.

Modbus is always a sequential polling protocol, so one only gets around to polling slave #1 after having polled slaves 2-9. If a slave goes off-line or fails, the master's time-out will likely slow the entire throughput cycle, as the master waits for reply that will not be forthcoming.


Using READ VAR/WRITE VAR function?
1b. It depends on what you mean by that.

The Modbus spec has defined a Function Code 23 (FC23), read/write Multiple Registers, that both reads and writes in one master message/transaction..

I know of only one a commercial implementation of FC23 by a vendor who uses it to upload and download configuration parameters for single loop controllers within their own software package, but it is intended for general use. I know of no commercial implementations otherwise (HMI's, field devices) on either the Master/client end or the slave/server end.
That doesn't mean FC23 is not out there, but good luck finding a commercial package that supports it.

Remember that both ends have to support any given Function code 23, so finding a master that supports FC23, but the slaves do not (or vice versa), does not allow you to use FC23.

What is almost universally supported are separate read functions from write functions. Widely implemented Read functions are FC01, FC02, FC03, FC04. Widely implemented write functions are FC05, FC06, FC15 (0Fh), FC16 (10h).

But read functions (messages) are implemented separately from write functions.

If you discover that your master hardware/firmware, slave hardware firmware network does support FC23, this forum like to hear about that.

How many READ VAR/WRITE function can be used simultaneously?
2. None. Nothing in Modbus RTU is simultaneous. All actions in Modbus RTU are sequential, one at a time. See item 1a above.

The rest of your questions are very hardware/firmware specific for which I have no experience.

I would think that in a project involving 24 PLC's that the PLC vendor should be capable of providing guidance on these points.
 
Answers in line below

Hello Experts,

We are currently in the design phase of a system with 24 PLC's.
CPU is BMXP342020 [ CPU onboard Serial and Ethernet ports, both capable of MODBUS]

Each PLC's are stand-alone and have communication with 9 Modbus RTU slaves.
Also, each PLC will be connected to OPC at central SCADA room via MODBUS TCP.


Questions:
Regarding Serial MODBUS RTU
1. CPU onboard RJ45 Serial port can directly make communication with all 9 slaves via multidrop? Using READ VAR/WRITE VAR function? Yes
2. How many READ VAR/WRITE function can be used simultaneously? 1, they should be sequenced one after another after each rad is successful or has timed out

Regarding MODBUS TCP
1. Which module is required for connecting to OPC? Either
BMX NOC 0401 or BMX NOE 0100? The NOE will be fine, it can be Modbus TCP slave
Can the above two modules be connected to OPC without any programming? We need to read/write data to each CPU all the time. they are default slaves/master, all you need to do is assign the IP in the PLC application

2. Does BMX NOC 0401/BMX NOE 0100 need programming in PLC for communication? No, as above

3. Does CPU onboard ethernet port require programming for communicating on MODBUS TCP? No, as above

Please guide.



We have used M580 CPU in 10 projects and all the time DCS [Client] can read/write data with M580[server] without any programming. But we used CPU onboard port or BME NOC 0301.2

So does that sounds similar to BMX NOC 0401/BMX NOE 0100 Yes
 

Similar Topics

Hello, this is a message for specialists in Schneider, I am trying to establish communication in modbus tcp between a schneider M340 (P3420302)...
Replies
2
Views
1,574
Hi, I hope everyone's week is going great. I have ADAM-6217 Analogue module which supports Modbus TCP and I am trying to get the AI values of the...
Replies
2
Views
1,610
I've got 16-bit data at address 40200 on a Schneider Scapack 350. I can grab the data over Modbus TCP using Kepware at IP 172.16.1.100. When I...
Replies
8
Views
2,427
Hi has any one linked a Schneider Electric Smart UPS to a PLC through Modbus TCP? Supposedly it can do it, I'm told. but I'm not entirely sure...
Replies
3
Views
2,399
Hi Guys, I have a project that requires a M340 PLC to communicate with a PM5340 power meter over Modbus TCP. I have previously used the same type...
Replies
3
Views
3,173
Back
Top Bottom