Differences

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

--- mitsubishi_q_fx_plc_integration_guide [2021/03/29 13:27] – created wikiadmin
+++ mitsubishi_q_fx_plc_integration_guide [2021/03/29 13:53] (current) – wikiadmin
@@ Line 1: / Line 1: @@
-**Mitsubishi Q / FX PLC Integration Guide**
+**SECS/GEM for 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.
+[[https://ergotech.com/contact?edit[cid]=6&edit[subject]=SECS/GEM for Mitsubishi PLC"|Contact us for more details.]]
+TransSECS supports full GEM300 integration - E39, E40, E87, E94 as well as SECS (E4, E5, E37) and GEM (E30). It supports applications that do not use GEM and SECSI (serial) connections - very useful for older tools.
 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.
@@ Line 35: / Line 39: @@
 **Remote Commands**
+Handling Remote/Host Commands is described here: [[scripting_to_handle_host_messages_in_transsecs_devices|How to Handle Host Messages in TransSECS Devices]]
+**Recipe Management**
+TransSECS can support a wide range of recipe management options.  The simplest is to use the CSV file support that is easily enabled in TransSECS [[recipe_management|TransSECS Recipe Management]].  There's really no limit to the sophistication of the solution, including using databases for recipe management [[devices_databases|TransSECS Devices Application Examples with Databases]]