=====PLC Addressing for MIStudio and TransSECS=====

====PLC Device Drivers====

Both TransSECS (Devices) and MIStudio use the same mechanism to obtain data from PLCs. For TransSECS Devices you add PLC drivers to the Devices node, then either import the device addresses and configurations using [[importing device servers with a spreadsheet|Import Excel]], or add individual addresses one by one to the driver node. In MIStudio you have the choice of using the Devices node to add a PLC Device Server or you can drag and drop a PLC Device Server bean into the Diagram Window of MIStudio to configure the connection to the PLC. Either way the underlying device driver is the same for each PLC and therefore the configuration of the specific PLC device driver is the same for all products. 

The available PLC Device drivers are:

  * Modbus TCP
  * Modbus RTU
  * Modbus ASCII
  * Modbus RTU over TCP
  * EtherNet/IP (used by Allen-Bradley ControlLogix and Siemens NJ Series)
  * Mitsubishi Q/FX
  * Omron FINS
  * Allen-Bradley MicroLogix
  * Siemens S7 (S7 300,S7 200,S7 1200,S7 1500)

We also offer OPC DA, OPC UA, Simulators, Database, and other protocols and servers in the Devices node of TransSECS and MIStudio. See individual wiki pages for these drivers and more information.

====Driver Configuration====

PLC Drivers have some properties in common. Other properties are unique to the specific PLC and are covered in the documentation for that PLC. For the most part you will not need to change anything in the PLC driver except the IP address of the PLC (hostname property), when applicable.

====PLC Address Configuration====

The addressing of PLC registers is different for each PLC type and is covered in a separate topic, links below:

[[ethernetip plc addressing for all products|EtherNet/IP Addressing]]

[[modbusplcaddressing|Modbus Registers/Addresssing]]