WebHMI Docs

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Connecting to Mitsubishi PLC with MELSEC protocol ======

----

{{ network:fx5u_pic.jpg?nolink&200|}}
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:

{{ network:melsec_shot1.png?direct&800 |}}

 In addition to Melsec, you need to add SLMP protocol handlers, because Melsec uses SLMP services, it is also necessary to remember the selected IP address and Port No. for exchange. 

You also need to check that the Melsec exchange is allowed in the Application Settings:
{{ network:melsec_shot2.png?direct&800 |}}

In connection properties in WebHMI, you must specify the IP address and port from the above properties in the controller project:
{{ network:melsec_shot_3.png?direct |}}

  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. The driver supports ONLY 3E/4E frame types. 
  
===== Notes on connecting to Melsec PLC via WebHMI virtual IP =====

There 2 things you have to adjust in your Melsec PLC programming tool:

  - State that you are connecting via HUB (not direct Ethernet connection)
  - Reserve more Melsoft connections in the PLC's configuration 

{{ :conn:conn-examples:melsec:connection_via_hub_melsec.jpg?direct&800 |}}

{{ :conn:conn-examples:melsec:extra_melsoft_socket_for_vpn_connection.jpg?direct&800 |}}

Please refer more to the [[remote_service_access | remote service access ]] article.