Overview
For devices that are configured by using a device type manager (DTM), data becomes available only after you have opened and closed the DTM once. Typically, for Modbus TCP and EtherNet/IP devices, a request/connection is created by using the default data of the DTM. For certain devices (for example, TeSys T), a request is created only once you have selected a device reference and saved the change while closing the DTM.
For details about the relation between DTM and I/O profile data, refer to the topic describing how to configure I/O profiles.
Description of Attributes
Attribute |
Description |
---|---|
|
Name and category of the I/O scanner service of the device Read-only. |
|
Name of the server that is used to communicate by using the respective protocol. Read-only. |
(1) |
Part number and version of the module. Click DTM version that corresponds to the version of the module that you are using. to select from the list theOnce a DTM is selected, you can create and configure local slaves. The box is empty by default. NOTE: Selecting a different value while local slaves
exist deletes these local slaves.
|
(1) The attribute appears only for M580 CPU and BMENOC03•1 modules. |
Subcategory
The DTM. It shows the local slaves that exist for the module.
subcategory is created once you have selected aClicking DTM to let you configure the local slave.
(+) creates an empty and opens the selectedClosing the DTM renames the local slave and adds its connection type according to the configuration that you have made in the DTM and creates the subcategory. You can then configure the profile, the connections in its memory registers, and the item mapping if needed. Refer to the tables further in this topic for details.
Each local slave has only one I/O profile, which you can add to a scanner.
Clicking DTM, which lets you perform changes (for example, removing the connection and replacing it by another local slave connection).
reopens theSubcategory
A communication profile is the definition of the data exchanged by a device, which can contain one or more requests or connections. Creating several profiles for a device lets you, for example, preconfigure requests for various scanners by adjusting certain attributes to each one. The profile that is used for communication between the device and the scanner is the active profile.
When a device has an active communication profile, it is added to the device list of the master DTM of the scanner, which creates a device DDT type and variable in the associated control project. The structure of the device DDT takes into account the I/O mapping.
For each device, you can create up to 6 profiles. Minimum is 1.
Each profile features the following attributes.
Attribute |
Default value |
Description |
---|---|---|
|
The name of the device when it is created followed by ProfileX_Device_Status. |
Name of the I/O profile, which is used as default value for the active I/O profile. Optional. NOTE: For certain modules, the default
value is the device name (DHCP identifier) and is read-only (for example, CRA adapter
modules).
|
|
The name of the device when it is created followed by ProfileX. |
The name is used as default value for the active I/O profile. The value of this attribute in the active I/O profile becomes the name of the device DDT variable that is used in the control project to manage the device data. When the attribute is editable, the value cannot be null and must satisfy the following rules:
The software accepts only unique names for a given control project. NOTE: For certain modules, the default value
is the name of the associated device DDT variable and is in read-only
(for example, CRA adapter modules).
|
|
The value of T_. preceded by |
The name is used as default value for the active I/O profile. It becomes the name of the device DDT type that is used in the control project to manage the device data. Read-only. |
|
First available number in the range that corresponds to the scanner. |
Indicates the relative position of the device in the device list of the master DTM of the scanner. The list contains all the numbers that can be assigned to the device when it scanned by a given scanner. This includes numbers that may already be assigned to other devices, which are scanned by the same scanner independently of the communication protocol used by the device. The attribute is shown only when you select the I/O profile in a Communication Mapping View (active I/O profile). NOTE: For some devices,
the attribute is read-only.
NOTE: For local slaves,
the attribute is not shown. A device number is assigned to each local
slave by the master DTM of the scanner.
|
|
– |
Mapping mode that is used to perform and manage the I/O mapping for the profile. Possible values:
Click to open the for the device.NOTE: For a CRA adapter module, automatic mode is selected
by default and is read-only.
|
For each active I/O profile, the following additional attributes are available when you select the profile in a Communication Mapping View.
Attribute |
Description |
---|---|
|
Name of the scanning device. Read-only. |
|
You can enter a comment for the active I/O profile by using free-form text. |
Section for
For each profile, you can create up to 64 requests. Minimum is 1.
Subsection |
Attribute |
Default value(1) |
Description |
---|---|---|---|
|
(2) |
255 |
Number that is used to identify the target of the connection. Typically, a device behind a gateway. Range: 0 to 255 |
(2) |
1500 |
Maximum allowed interval between device responses before a timeout is detected. Range: 5 to 65535 in 5 ms intervals. |
|
(2) |
60 |
Data scan rate. Range: 5 to 60000 in 5 ms intervals. |
|
(3) |
0 |
Range: 0 to 65535 |
|
(3) |
1 |
Number of words that are allocated to read from the server when you create a communication channel.The corresponding memory size is reserved in both the client and server memory heap. Range: 0 to 125 |
|
(2) |
|
Input value that is retained when a communication interruption occurs. Possible values: |
|
|
(3) |
0 |
Range: 0 to 65535 |
(3) |
0 |
Number of words that are allocated to write to the server when you create a communication channel.The corresponding memory size is reserved in both the client and server memory heap. Range: 0 to 120 |
|
|
False |
When selected (true), lets slower TCP/IP devices communicate with the I/O scanner of BMENOC0301/11.4 communication modules. The modules double the timeout setting by increasing the number of retransmissions to 6 instead of the typical 3. |
|
(1) Values for devices without DTM and for additional requests created in manual mapping mode. Otherwise, default values of the first request are those of the device DTM. (2) The value of the attribute can be modified independently in the active I/O profile where the name appears without the term Default. Switching to automatic mapping mode resets the value of the attribute in the active and device I/O profiles. (3) For devices that are configured by using a DTM, in the first request, the value is read-only and provided by the DTM. In requests added manually, you can change the value when the mapping mode is set to manual. |
Section for
For each profile, you can create up to 2 connections.
For certain devices, the following may apply:
Additional connections can only be created in the DTM.
Connection data is managed in Control Expert Editor and does not appear in the tab (for example, for CRA adapter and BMECXM0100 modules).
Subsection |
Attribute |
Default value(1) |
Description |
---|---|---|---|
|
(2) |
30 |
Request packet interval. The data refresh period (ms) of the input connection. Range: 2 to 65535 |
|
– |
This value multiplied by the RPI produces a value that triggers an inactivity timeout. Use the recommended value depending on the RPI value. Range: 4 (default) to 512 in multiples of 4. NOTE: You can change the
value of the attribute independently in the active I/O profile where the name
appears without the Default prefix.
NOTE: Switching to automatic mapping mode resets the
value of the attribute in the active and device I/O profiles.
|
|
|
|
Behavior of inputs when the communication is interrupted. Read-only. |
|
(2)(3) |
1 |
Number of words configured in the device. Range: 1 to 509. |
|
(2) |
|
Transmission type. |
|
(2) |
|
Ethernet packet type (fixed or variable length) to be transmitted. Possible value: |
|
(2) |
|
The transmission priority depends on the DTM. Possible value: |
|
(2) |
|
Transmission trigger. Possible values: |
|
|
(2) |
30 |
Request packet interval. The data refresh period (ms) of the output connection. Range: 2 to 65535 |
(2)(3) |
1 |
Number of words configured in the device. Range: 1 to 505. |
|
(2) |
|
Transmission type. Possible values: |
|
(2) |
|
Ethernet packet type (fixed or variable length) to be transmitted. Possible value: |
|
(2) |
|
The transmission priority depends on the DTM. Possible value: |
|
(1) Values for devices without DTM and for additional connections created in manual mapping mode. Otherwise, default values of the first connection are those of the device DTM. (2) For devices that are configured by using a DTM, the value is read-only and provided by the DTM. (3) In connections added manually, you can change the value of the attribute from the . |