Differences

This shows you the differences between two versions of the page.

--- connecting_to_melsec [2020/04/21 09:58] – emozolyak
+++ connecting_to_melsec [2020/05/28 09:39] – emozolyak
@@ Line 1: / Line 1: @@
 ====== Connecting to Mitsubishi PLC with MELSEC protocol ======
-To work with Mitsubishi PLCs supporting the MELSEC protocol, it must be first configured the network configuration and explicitly indicated that there will be a host (in our case WebHMI) in the network that will poll the PLC with this protocol. This is done in the visual design environment of GX Works3. You need to go to the Parameter / FX5U CPU / Module parameter / Ethernet port and 'drag' the required communication modules from the 'Ethernet Device' window:
+To work with Mitsubishi PLCs supporting the MELSEC protocol (the generation which is programmed in __GX Works3__ eng. tool), it must be first configured the network configuration and explicitly indicated that there will be a host (in our case WebHMI) in the network that will poll the PLC with this protocol. This is done in the visual design environment of GX Works3. You need to go to the Parameter / FX5U CPU / Module parameter / Ethernet port and 'drag' the required communication modules from the 'Ethernet Device' window:
 {{::melsec_shot1.png?direct|}}
@@ Line 14: / Line 14: @@
   Please test first the PLC you're going to use with WebHMI, e.g. with virtual machine demo image,
-  some firmware vestions of the  Q/L series have been reported as not supported with WebHMI protocol implementation.
+  some firmware vestions of the  Q/L series have been reported as not supported with WebHMI protocol
+  implementation. The driver supports ONLY 3E/4E frame types.