Manufacturer-specific Objects

Index Parameter Name

2000h GB_aby_ActConfg Actual configuration of the node

2001h GB_aby_DesConfg Desired configuration of the node

2002h Number_of_digital_inputs

2003h Number_of_digital_output_modules 2004h Number_of_analog_inputs

2005h Number_of_analog_out

The configuration of the node is defined and checked using the transCON-specific objects 2000h and 2001h. Object 2000h represents the modules that are recognised on the node and is used for diagnostic purposes. If the desired and actual configurations do not match, the node transmits a device-specific emergency message with the following input (also refer to the structure of the emergency telegram on page 3.9).

Emergency error code: FF01h

•

Manufacturer specific error feld: Bit felds of bytes 4 and 5 form the deviating

•

I/O modules

3.5.2 Actual Configuration of the Node

Index S-Idx Type Default Meaning

2000 h 0h u8 (read only) 10h Number of subindices/maximum number of modules

1h u8 Identifer of module with index 0

2h u8 Identifer of module with index 1

… … …

10h u8 Identifer of module with index 15

▼

Object 2000 contains the identifers found.

The following table specifies the identifers for the module types:

Module type Identifer

No module found 00h

Digital input module 15h

Digital output module 11h Analog input/output module 62h

PT 100 module 36h

3.5.3 Desired Configuration of the Node

Index S-Idx Type Content Meaning

2001 h 0h u8 (read only) 10h Number of subindices = maximum number of modules

1h u8 Desired identifer of module with ID 0

2h u8 Desired identifer of module with ID 1

… … …

10h u8 Desired identifer of module with ID Fh

▼

The desired configuration determines which module type is expected for each ID (0 - 15).

The following table lists the inputs that are valid for the desired identifers:

Module type Desired identifer in object 2001

No module 00h

Digital input module 15h

Digital output module 11h Analog input/output module 62h

PT 100 module 36h

Any module (wild card) FFh

3.5.4 Wild Cards

A "wild card" is defined for the desired identifer, which can be accepted for any module in this index (including no module). The wild card is strictly intended for setting up a labora-tory installation quickly and easily. It must not be used for configuration in a feld installa-tion, as is explained in detail in the example below.

The variable part of the object directory is constructed on the basis of the desired identifers in object 2001h. For this purpose, the number of modules involved must be determined. Each module entered as a desired module must be taken into account for the structure of the object directory. Furthermore, those modules that are connected to the node and entered in object 2001h as wild cards are also taken into account.

Modules whose IDs have been entered in object 2001 as "No module" are not taken into account. The example below should clarify this.

3.5.5 Example of Actual/Desired Configuration

Object 2001h is configured for the desired arrangement of three DIs, two DOs and two non-specific modules. In reality, four DI modules and four DO modules are connected.

Desired configuration of the modules

Modules with which the node is equipped (actual configuration) Index S-Idx value ID Module

type

effect on the object directory

Comment

2001h 0h 16h

1h 00h 0 00h No effect Standard case

2h FFh 1 00h No effect Only permitted

for laboratory

3h 15h 2 15h First DI module Standard case

4h 11h 3 11h First DO module Standard case

5h 11h 4 11h Second DO module Standard case

6h 00h 5 00h No effect Standard case

7h FFh 6 15h Second DI module Only permitted

for laboratory

8h 15h 7 15h Third DI module Standard case

9h 00h 8 00h No effect Standard case

Ah 00h 9 00h No effect Standard case

Bh 15h A 11h Fourth DI module Incorrect con

-figuration

Ch 15h B 00h Fifth DI module Incorrect con

-figuration

Dh 00h C 00h No effect Standard case

Eh 00h D 00h No effect Standard case

Fh 00h E 11h No effect Incorrect con

-figuration

10h 00h F 15h No effect Incorrect con

-figuration Detailed Analysis of the Example Settings

Subindex0 of object 2001h specifies the index of the highest subindex for the object.

Since a maximum of 16 modules can be connected to a transCON node, the content of the subindex is always 16 (10h).

Subindex1 specifies the expected module type for the module whose ID rotary switch is set to 0. This value is set to "no module". There is also no module with ID 0 connected to the node. This represents a standard case for a non-existent module.

NOTICE

The "wild card" value is not permitted in feld installations. The setting "No module" must be used for non-existent modules.

Subindex2 is responsible for the module with ID 1 and is set to "wild card". Since no module with ID = 1 is connected to the node, the variable part of the object directory is not affected.

Subindex3 specifies the value "DI" for the module with ID 2, and a digital input module with ID 2 is connected to the node. This is the standard case for a module installed on the node; the prescribed value matches the existing module type. This digital input module is the first DI module that is relevant for calculating the object directory.

Subindex 4 and 5 request digital output modules for IDs 3 and 4; these modules are also actually present. They are considered to be the first and second digital output modules when calculating the object directory.

Subindex 6 is the standard case for a non-existent module.

Subindex 7 is a "wild card" for ID 6. Since the module with ID 6 is a digital input module, it is considered to be another (in this case, therefore, a second) digital input when creating the object directory.

Subindex 8 also represents a standard case for a module. The digital input module with ID 7 is considered to be the third digital input module when creating the object directory.