(Help) PLC to PLC communication (FX3U) over module FX3U-ENET-ADP

[sangph 0]

Hi All,

I want to ask some questions regarding Ethernet Communication with FX3U PLC series. I have 2 PLCs of FX3U series (FX3U-48M and FX3U-48M) and I use module FX3U-ENET-ADP  . My questions are:

1. Can I use module FX3U-ENET-ADP to share data between 2 PLC's over ethernet ???

2. If possible, How can i do it ???.

thanks a lot.

[Crossbow 295]

No.  The ENET-ADP is meant as a programming connection only.

[AndreasW 21]

hi,

i'am not sure if it works with two ENET-ADP-Moduls, as Crossbow said the ADP-Version is meant for a programming connection, that means
you can't access it from within the PLC code (no open socket, send/receive data, ....). Maybe it will work only using the DEVICE-Data Transfer
Function using an N:N- network (see Data Communication manual)
https://www.atronika.com/Mitsubishi/PLC/MITSUBISHI_FX3GFX3UFX3UC-Users-Manual-%E2%80%93-Data-Communications-Networking.pdf

but i'm not sure that it will work.

If you have at least one ENET-module you can use the N:N-Network Data Transfer function. If you
don't want to (or can't) use the data transfer function you have to to the data transfer from within the PLC program
using the MC-Protocoll. you should have a look at the differences between the ENET and the ENET-ADP Version
see Appendix in the ENET-ADP manual https://si3a.mitsubishielectric.com/fa/sl/dl/9939/JY997D45801-F.pdf

 

 

 

 

[sangph 0]

7 hours ago, AndreasW said:

hi,

i'am not sure if it works with two ENET-ADP-Moduls, as Crossbow said the ADP-Version is meant for a programming connection, that means
you can't access it from within the PLC code (no open socket, send/receive data, ....). Maybe it will work only using the DEVICE-Data Transfer
Function using an N:N- network (see Data Communication manual)
https://www.atronika.com/Mitsubishi/PLC/MITSUBISHI_FX3GFX3UFX3UC-Users-Manual-%E2%80%93-Data-Communications-Networking.pdf

but i'm not sure that it will work.

If you have at least one ENET-module you can use the N:N-Network Data Transfer function. If you
don't want to (or can't) use the data transfer function you have to to the data transfer from within the PLC program
using the MC-Protocoll. you should have a look at the differences between the ENET and the ENET-ADP Version
see Appendix in the ENET-ADP manual https://si3a.mitsubishielectric.com/fa/sl/dl/9939/JY997D45801-F.pdf

 

 

 

 

hi,

I got it. I will try it.

thanks a lot

[Crossbow 295]

PLC to PLC requires FX3U-ENET, not FX3U-ENET-ADP.

[Inntele 60]

39 minutes ago, Crossbow said:

PLC to PLC requires FX3U-ENET, not FX3U-ENET-ADP.

Dear Crossbow,

Sorry, but in this case you're not right. I'm sure, AndreasW are right, i.e. N:N network communicaton over TCP/IP protocol, because the ENET-ADP module is just a translator to TCP/IP of a serial data, coming from additional serial port of PLC. 

[Crossbow 295]

23 hours ago, Inntele said:

Dear Crossbow,

Sorry, but in this case you're not right. I'm sure, AndreasW are right, i.e. N:N network communicaton over TCP/IP protocol, because the ENET-ADP module is just a translator to TCP/IP of a serial data, coming from additional serial port of PLC. 

I'm not so sure on that.  I worked at Mitsu when that product was launched, and we were told it was for programming connection only, not for peer to peer networking.  As AndreasW mentioned, you need at least one ENET (not ADP) to do N:N communication.  So unless they changed the product after launch, ENET-ADP to ENET-ADP is not possible.  

[Inntele 60]

42 minutes ago, Crossbow said:

I'm not so sure on that.  I worked at Mitsu when that product was launched, and we were told it was for programming connection only, not for peer to peer networking.  As AndreasW mentioned, you need at least one ENET (not ADP) to do N:N communication.  So unless they changed the product after launch, ENET-ADP to ENET-ADP is not possible.  

42 minutes ago, Crossbow said:

I'm not so sure on that.  I worked at Mitsu when that product was launched, and we were told it was for programming connection only, not for peer to peer networking.  As AndreasW mentioned, you need at least one ENET (not ADP) to do N:N communication.  So unless they changed the product after launch, ENET-ADP to ENET-ADP is not possible.  

On 15.12.2020 at 7:30 PM, Crossbow said:

PLC to PLC requires FX3U-ENET, not FX3U-ENET-ADP.

I\m understanding, that you are big specialist in Mitusbishi PLC line. While I'm know, how it works, because we are connected SCADA thru the mentioned modules. This is just a gate between serial data transition and TCP/IP transition.

[Crossbow 295]

SCADA can talk to it.  Never said it couldn't.  SCADA is asking for the data. 

PLC to PLC is not supported.  There's no communication functions you can write in the program to talk via that port.

Or it wasn't the last time I dealt with one of these years ago.  I got out of that product line around 2013.

Grab the FX3U Communication Manual and show me a function that can talk via the ENET-ADP.

[Crossbow 295]

From the manual JY997D45801:

The Ethernet adapter has the following features.

1) Users can read and write data and programs from/to the PLC using MELSOFT products such as GX Works2 within the company LAN, etc.

2) Users can develop custom software to communicate with the PLC by using MC (MELSEC Communication) protocol (A-compatible 1E frame subset, for details, refer to user's manual). (TCP/IP or UDP/IP)

3) The FX3U-ENET-ADP can be connected directly (simple connection) to GX Works2 with only one Ethernet cable without using the hub.

4) Users can search "FX3U-ENET-ADP + Main unit" connected in the network using the find CPU function of GX Works2.

5) The FX3U-ENET-ADP can automatically set the time of the main unit using the time setting function.

6) The FX3U-ENET-ADP parameters can be set easily using GX Works2.

7) The diagnostic functions of GX Works2 enables easy diagnostics and troubleshooting of the FX3U-ENETADP.

8) Users can monitor the information and device values stored in the main unit and FX3U-ENET-ADP from the browser in the personal computer using the data monitoring function.

[Inntele 60]

I said that my logic do not based on the manual, but on the logic of module connection and its working. The module is connected to the connector of serial port, and the module is not difference what it will translate to network, moreover it work independenly of the program scan... Thus it should provide N:N network protocol. Hope, the topicstarter checked it already.

[Inntele 60]

I said that my logic do not based on the manual, but on the logic of module connection and its working. The module is connected to the connector of serial port, and the module is not difference what it will translate to network, moreover it work independenly of the program scan... Thus it should provide N:N network protocol. Hope, the topicstarter checked it already.

[Crossbow 295]

How do you plan to tell the PLC the IP address of the target device?  You can't.

This is what the FX3U-ENET is intended for.  Buy the right hardware for the task.