ModbusSerial 2.0 Patch 01 DIObjects ReadMe

# Wonderware ModbusSerial 2.0 Patch 01 DIObjects ReadMe

Last revision: 5/31/2006

This ReadMe file describes the WonderwareÒ ModbusSerial DeviceIntegration (DI) Objects and how to install them. Also, known issues are documented.

DIObject Package: DiModbusSerial_2.0.001.aaPkg

Objects in the Package:

ModbusSerial 2.2 | ModbusSerialPLC 1.1
ModbusSerialDataMODEM 1.1 | ModbusSerialQuantum 2.1
ModbusSerialLine 1.1 | ModbusSerialRadioMODEM 1.1
ModbusSerialMicro 2.1 | ModbusSerialStation 1.1
ModbusSerialMomentum 2.1 |

Encapsulated DAServer: MBSerial 2.0.001

Supported IAS: IAS 2.1

About DIObjects

Resolved Issues

Known Issues

Installation Information

# About DIObjects

DIObjects are representations, or models, of the network and devices associated with a particular application to which the Industrial Application Server is connected. The hierarchy of the actual devices is the same as the hierarchy of the DIObjects.

< top of document >

# Resolved Issues

The following issues are resolved in this patch.

### L00037399:

When an OPC client subscribes to item 400050:16, the server shows data type VT_BOOL in the Canonical column and VT_UI2 in the Type column. The server should show VT_BOOL data type in both columns.

### L00037890:

The DCOM Config utility should show the application name DASMBSerial instead of GUID.

### L00039422:

When an offline PLC is polled, the server waits 10 seconds for a reply. When the reply timer times out, the slow poll timer starts. This allows the other PLCs on the RS485 network to get regular updates for 10 seconds and not go into slow poll mode before the offline PLC is polled again.

Important Note: For a multi-drop (RS485) network, if a request message is sent to an offline PLC, the communications port is blocked for the amount of time set in the Reply Timeout parameter. One request message is sent after every slow poll time interval to each PLC that is offline.

For example:

Four PLCs are connected to COM 1.
Reply Timeout: 5 seconds
Slow Poll Interval: 30 seconds

If one of the PLCs goes offline and the expected reply message times out, the PLC is put into a slow poll mode and the next request message is scheduled in about 25 seconds (30 seconds minus 5 seconds). Because of the blocking nature of the Modbus Serial protocol, the time slice available to communicate with the remaining three online PLCs is 25 seconds out of the 30-second interval period.
If three out of the four PLCs are offline, the time slice to communicate with the remaining online PLC is 15 seconds out of the 30-second interval period (30 – 3 * 5).

Use the following formula to set the slow poll interval parameter in a multi-drop network. In the formula, the n variable represents equivalent slave PLCs.

Slow Poll Interval >= n * Reply Timeout

### L00040586:

If one node in a multi-drop network (RS485) is offline, $SYS$Status must reflect the communications status per topic/node and not switch between 0 and 1 for all the nodes/topics.

### L00049103:

The DAServer cannot continuously connect to a PLC via a radio modem. Problems occur when setting up communications via a radio modem. The RSSI signal level is too high and it results in transmission errors. After a connection is made, the connection to a PLC via the radio modem also drops out and the DAServer cannot come out of a Slow Poll mode without operator intervention. To resolve these problems and to have the Modbus Serial DAServer operate properly, perform the following:

- Adjust the radio antennas to have the gain level in the recommended range of 70-90 dBm (dB milliWatt).
- Set up the radio modems according to the manufacturer’s operating specifications.

### L00050207:

The problem with the system timer is fixed. The timer does not wrap around to zero after the server runs continuously for 49.7 days.

### L00050295:

The DAServer does not reconnect to the modem after the serial cable between the PC and the modem is disconnected. After the serial cable between the PC and the modem is disconnected, perform the following steps to reconnect the DAServer to the modem:

- Connect the serial cable.
- Power the modem down and up.
- Configure the DAServer and the ELPRO U905 D radio modem to support DTR (Data Terminal Ready).

- On the RadioMODEM_000_Parameters configuration view of the DAServer hierarchy, select the Enable DSR/DTR support check box.
- On the 905U-D Configuration dialog box, select the Command Mode, Disconnect option in the Data Terminal Ready (DTR) Control group box to configure the ELPRO U905 D radio modem serial connection.

### L00051572:

Modulo-10000 functionality is not working. When you use Modulo-10000, the results are the same as when reading a long integer.

< top of document >

# Known Issues

The following are known issues in this patch.

### Configuration:

You can configure the ModbusSerial DIObjects to connect a large network of Modbus PLCs across different serial ports. System resources such as CPU cycles, physical memory, and system threads are consumed with each PLC that is configured into the ModbusSerial DIObject.

The DIObjects performance may be reduced if a high number of PLCs are configured for a serial port.

### L00019525:

ArchestrATM does not limit the number of device objects that can be assigned to a parent object.

### L00028210:

A warning message is shown in the logger when an object having multiple “Required Host Feature” is imported and an instance of it is created. You can ignore this warning.

< top of document >

# Installation Information

To install a DIObject, you must understand the ArchestrA Integrated Development Environment (IDE). For detailed instructions on installing and using DIObjects within the IDE, see the IDE User's Guide. This information is also included in the individual DIObject help files, which are available after you import the DIObject into the IDE.

Detailed installation instructions are included in the IDE User’s Guide. You can find instructions on how to use the DIObjects in the IDE User's Guide, as well as in the individual DIObject help files, which are accessible after the DIObject has been imported into the IDE.

## Importing Objects

To use an object, you must first import it into your Galaxy. Objects are shipped as "package" files with a .aaPKG extension. More than one object can be contained in a package file.

Note: You can also import object instances that were exported from another Galaxy. All previous associations are retained, such as assignment, containment, derivation, and area.

The Galaxy database does not allow two objects with the same name or more than one copy of the same version of an object. When you import an object, you must specify how to handle version and naming conflicts.

### To import an object

1. Start the ArchestrA IDE.
2. On the Galaxy menu, point to Import and click Automation Object(s). The Import AutomationObject(s) dialog box appears.
3. Browse for an object file (.aaPKG extension) and click Open. The Import Preferences dialog box appears.
4. In the Object version mismatch area, configure the behavior of the import process.

· Click Skip to import new objects and leave the existing object unchanged.

· Click Overwrite to replace the existing object with the minor version or configuration version upgrade of that object.

· Click Migrate to import the selected object(s) that have gone through a major version upgrade.

5. Click OK. A progress dialog box appears.
6. Click Close when the import process is done. Imported templates are shown in the proper toolset in the Template Toolset. Imported instances are shown in the Application Views. The following post-import rules apply:

· If the toolset does not exist, it is created.

· If the object belongs to a security group that does not exist, it is associated with the Default security group.

· If the object belongs to an area that does not exist, it is associated with the Unassigned Area.

· If the host to which the object is assigned does not exist, it is assigned to the Unassigned Host.

Note: If you import a new version of an existing instance, the new version is marked as requiring deployment if the existing object is already deployed.

< top of document >

© 2006 Invensys Systems, Inc. All Rights Reserved.