This is an old revision of the document!

Mitsubishi Q / FX PLC Integration Guide

TransSECS supports direct integration of many PLCs including Mitsubishi Ethernet PLCs. You build the interface by configuring, rather than programming, although you might need a little scripting to validate remote commands.

As with any TransSECS application, almost all GEM messages gem_tool_messages are handled directly by TransSECS. To build a complete application, all that is required is connect VIDs, CEIDs, and ALIDs. Remote commands and recipes (S7 messages) may also be required.

PLC connection

As with any other PLC, you create a connection to the PLC directly within the TransSECS editor.

once you've created the connection to the PLC you can add tags, based on registers, within the PLC node

For simplicity you can also import the tags from an Excel spreadsheet

as described here: Importing VIDs, CEIDs, and ALIDs into TransSECS

Connecting to VIDs, ALIDs and CEIDs

You connect from the tags to the SECS IDs. Just select the Device Name (eg Mitsubishi Q) and the tag name (eg GasFlow)

Whenever the host requests the value of the VID the correct value, as last read from the PLC, will be provided.

Similarly, ALIDs are configured so that any change will cause a SECS Alarm messages (S5F1) to be sent to the host with an indication that the alarm is set or cleared.

CEIDs are triggered by any change from zero to non-zero and can be reset either by TransSECS or the PLC.

Remote Commands