PLC to PLC communication

[Miguel.itlac]

Hello everyone

Does anybody knows how to estblish a communication between 2 Mitsubishi CPUS with modbus?

THey are RCPU and FXCPU

 

Edited June 2, 2020 by Miguel.itlac

[Gambit]

simple PLC comm is easiest just setting up parameters and communicating over the standard ethernet port

 

[Crossbow]

FXCPU is useless information.  There have been FX model CPUs since the 80s.  Need a complete model.  Like FX2N, FX3U, etc.

[Miguel.itlac]

Yes sorry, I mean FX5CPU, im New with Mitsubishi software etc, but i know that the simple communication is the easiest, but my boss told me that with modbus is easier and  i actually dindt catch the whole idea maybe someone can explain it better here.

thank you in advance 

Edited June 5, 2020 by Miguel.itlac

[MrDippy]

The RCPU (iQR) & FX5 (iQF) have built in "Simple PLC Communications". 

As Gambit said, you only have to configure the settings to establish comms between the 2 PLCs using their Ethernets..

The only recommendation is to use either the RCPU or the FX5 to do the talking. The comms allows the transfers of PLC Data & bit registers between the 2 PLCs.

You pnly need to configure the comms from 1 of the PLC.

Eg. Say you use the RCPU to do the transfer of registers. You configure the RCPU settings to transfer D100 to D150 to the FX5 memory at D1100 to D1150. You do not need to perform any setup at the FX5 PLC. (apart from the IPaddress to be in same range)  When the RCPU is rebooted, it will perform the transfer. This also applys to registers it Reads from the FX5 PLC.

 

 

[Miguel.itlac]

yes i understand that, but there is another system where modbus tcp is implemented, and there must be communicating each other 

[Gambit]

well just add a modbus port in the ethernet device settings

For the client  there is a FB in the CPU list

[Gambit]

2 hours ago, Miguel.itlac said:

yes i understand that, but there is another system where modbus tcp is implemented, and there must be communicating each other 

Ok but what is your question ? Will the other system be the client or the server ?

all you have to do to make them modbus servers is to add a modus port to the ethernet settings

The FX5U CPU has a FB for modbus read write. just look under the CPU FB in GX works 3 

Edited June 18, 2020 by Gambit

[Miguel.itlac]

I actually have a FX5UC with only  the modbus TCP connection module in the Ethernet configuration without any library or FB and i can write with a modbus  View TCP tool so no problem to this point, but my RCPU will be my Client and is not possible to add a Modbus TCP connection module as in my FX5UC, so  to this CPU I added the Client library MEU+RCPU_ModbusTCP_00B, added and active connection module pointing to the IP and port of my FX5UC and configure the client FB to talk to my Fx5UC is that correct??

My conclusion is then, that the MODBUS TCP connection module works only as a server am i Right?

[Gambit]

Yes Both the FX5U and de iQ-R CPU have the modbus server for which you only need to setup a port.

When you want to use them as a client then there is a FB for the FX5U. 

For the iQ-R you need the library you mentioned.

Alternatively you can also use the pre-defined protocol function.

 

.

[Miguel.itlac]

one more question is, when all communication is set up, how do I get the data, i mean if i send a value in my RCPU in D0 to the FX5UC will i get this value in same Device?

How is the mapping in this Case?

once i did it with a weintek HMI and i Read memory devices Ms from 8193= M0 so i Wonder if its the same when modbus is implemented.

[Gambit]

There is a default mapping between Mitsubishi devices and modbus devices. (You can change it if you want but is not needed)

So if you write to holding register 0 (40000) you will write it into D0

 

[Miguel.itlac]

okay thank you all guys for your support