InterBus-S Device

InterBus-S boxes which are not recognised by the TwinCAT System Manager can be inserted by inputting InterBus-S-specific length and identity codes. The length and identity codes for each device are given in the corresponding manual and are frequently marked on the device itself.

When adding an InterBus-S box you will see the following dialogue:

Context menu

InterBus-S Device 1:

Append Box... <Insert>

Adds, in the case of InterBus-S Bus Terminals, a box to the local or remote bus.

InterBus-S Device 2:

Actuate the ”List...” button to display a list of current InterBus-S boxes, whose length and identity codes are known.

InterBus-S Device 3:

When adding another InterBus-S box you will see the following dialogue:

InterBus-S Device 4:

Insert Box Before...

Adds another box above the marked box.

Delete Box... <Del>

Deletes the marked box and its sub-elements from the I/O configuration.

Import Box Before...

Adds another box above the marked box. The description of the new box and its sub-elements are read from a file with the suffix "*.tce". This file is created with the following menu option.

Export Box...

Exports the information from the selected box and the information about its sub-elements into a file with the suffix "*.tce".

"InterBus-S" tab

InterBus-S Device 5:

Identity Code: Displays the identity code for the Bus Coupler. It is calculated dynamically - according to the connected terminals.

Length Code: Displays the length code for the Bus Coupler. It is calculated dynamically - according to the connected terminals.

Installation depth: Displays the installation depth of the Bus Coupler. It is calculated dynamically - according to the hierarchical structure of the InterBus-S.

The following settings are only possible in the case of the Phoenix IBS ISA ST-I/T.

Group: Allows the assignment of the device to a group (see Interbus user manual).

Alternative: Allows the assignment of the device to an alternative (see Interbus user manual).

Data consistency: Allows you to increase the data consistency for this device

StartUp: Allows the execution of a Control_Active_Configuration command at the system StartUp for this device.

"CAC/CDF" tab

InterBus-S Device 6:

Allows the execution of some firmware services of the Phoenix IBS ISA ST-I/T when an ADS port is active for the master card. See Interbus user manual. Note that a Control_Active_Configuration command will affect subsidiary devices!

Input Diagnosis

InterBus-S Device 7:

Each InterBus-S fieldbus box contains one diagnostic input byte which signals the status of the current slave during the running time and can be linked, for example with the PLC.

Variable

Value

Description

BoxState

0x01

Rec: Reconfiguration

0x02

Mod: Module error

0x04

W2Err: Error at the W2 interface

0x08

W1Err: Error at the W1 interface

0x10

W2: W2 interface inactive

0x20

W1: W1 interface inactive

PCP Communication

Some InterBus-S devices can carry out non-cyclical communication with the master card as well as cyclical process data exchange (not CIF40-IBSM). The communication in the case of InterBus-S is called PCP communication (Peripherals Communication Protocol).

The devices are recognized by their identity code and have an additional tab.

InterBus-S Device 8:

Enable” PCP communication assigns an AMS port to the device, via which the PCP communication is processed via ADS.

On the InterBus side, the communication connection between this device and the master card receives a communication number (CR = Communication Reference). A password and an access group number can also be specified (see description of PCP communication).

PCP services

The following services are currently supported:

  1. Read (0x0081)
  2. Write (0x0082)
  3. Start (0x0083)
  4. Stop (0x0084)
  5. Resume (0x0089)
  6. Reset (0x008A)

The required service is specified by entering the service code (mentioned above) in the ADS IndexGroup HIWORD (see ADS documentation).

You can simplify the process by using the code 0 for the read service in the case of an AdaReadReq and the write service in the case of an AdsWriteReq.

Index: The required PCP Index is entered in the LOWORD of the IndexGroup.

Sub-index: The required PCP sub-index is entered in the IndexOffset.