Configuring Mitsubishi Slave Devices in Geo SCADA Expert

On a Geo SCADA Expert system, you configure the Geo SCADA Expert database so that entries in the database correspond to the devices on your system. This section summarizes the database items that you need to configure to represent the Mitsubishi Slave devices on your system.

To function as a Mitsubishi Slave, the Mitsubishi Slave Driver has to be installed and running on the Geo SCADA Expert servers on your system. The Mitsubishi Slave driver allows Geo SCADA Expert to act as a Mitsubishi^TM MELSEC^TM A PLC, and use the Mitsubishi MELSEC A protocol to talk to a Mitsubishi Master (for example, another server).

When you configure Mitsubishi Slave items in the Geo SCADA Expert database, many of the settings for those items need to correspond to the settings of the relevant Mitsubishi Master on your system. Some settings are either fixed (incorporated into the design of the Mitsubishi Master), or are configured by an engineer. You need to have access to, or an understanding of, the settings of the Mitsubishi Master on your system before you can configure the Mitsubishi Slave database items successfully.

For instance, you need to know the type(s) of Mitsubishi device (point) data that Geo SCADA Expert is to report to the Mitsubishi Master, and how the communications to that Master are structured or grouped. You also need to be aware of The Transmission Protocol Supported by Geo SCADA Expert.

You also need to be aware of which optional features are required for each Mitsubishi Slave item. These features include:

• Alarm views
• Alarm redirections
• User methods.

You can also use core Geo SCADA Expert features with Mitsubishi Slave database items, including Lists, Actions, and Mimics. See the core documentation for details.

 

For each Mitsubishi Slave device, you need to configure:

1. Mitsubishi Slave Channel(s) to represent the communication connection(s) between the Slave and its Master (see Configuring a Mitsubishi Slave Channel).
2. Value Maps for mapping ‘point’ properties into memory so that they can be accessed by the Slave’s Master (see Configuring Value Maps in the Geo SCADA Expert Guide to Core Configuration).

   A Mitsubishi Slave Source (see below) maps to BIT Value Maps for Bit Device data and to WORD Value Maps for Word Device data.

3. A Mitsubishi Slave Source to specify which Value Map(s)—blocks of data—are to be scanned by a particular Master device (see Configuring a Mitsubishi Slave Source).

   Configure a separate Source for each block of data that is to be scanned separately to other data by, for example, a different Master scanner.

To save time, we recommend that you configure Mitsubishi Slave items in the order listed above. This is because Source configuration requires you to specify a Channel and the Value Maps that hold the Source’s ‘point’ data.