Conversion tables, Oem parameters, No change’ when changes have been made – Rockwell Automation T8xxx Application Note Trusted Intelligent Online Updates User Manual

Page 22: Attribute changes, Forced i/o, Don’t delete the appli.mdf and appli.mdh files, Trusted, Intelligent online updates

Advertising
background image

Trusted

TM

AN-T80009 Trusted

TM

Intelligent Online Updates

Issue 4 Nov 08

AN-T80009

22

1.13.6.

Conversion tables

In releases prior to 3.5, changes to conversion tables do not trigger an Intelligent Online Update, but
then do not get activated in a 'normal' online update - the update will download and run, but the
changes to the conversion tables are not in effect. If there is another change that triggers an Intelligent
Online Update (and Intelligent Updates are enabled), then the changes to conversion tables WILL go
into effect after the update. The simplest way to trigger an Intelligent Online Update is to add a new
variable. At release 3.5, changes to conversion tables (and changes to the allocation of conversion
tables to I/O variables) trigger an Intelligent Update.

1.13.7.

OEM parameters

If an OEM parameter on an I/O module complex equipment definition (or peer to peer board) is
changed and then downloaded with an online update, the OEM parameter change will not take effect
until the application is stopped and restarted (or the system is re-powered).

An OEM parameter on a complex equipment definition appears as below on a board, next to a binary
switch icon. These parameters will affect the operation of the peer board or module. This largely
affects changing the I/O module position or changing the peer to peer IP address (or other peer to peer
board parameters). This is the same with the normal online update or intelligent online update, and
changes to OEM parameters will not affect the choice of update type.

1.13.8.

‘NO CHANGE’ when changes have been made

If a change is made that does not require an IOU, this change will not be detailed in the IOU report (file
APPLI.MSX). The report only details changes that require an IOU. This means that if a change is made
and the report says ‘NO CHANGE’, then the change may be made using a normal update.

1.13.9.

Attribute changes

The IOU reports variables as ADDED or DELETED in its post-compile report - not whether any variable
attributes were changed. When NO CHANGE is reported, it simply means that there were no
additions/deletions to the symbol table itself. There may be changes to the attributes.

1.13.10.

Forced I/O

Prior to release 3.5, input variable locks are removed on an intelligent online update. Actual output
variables from the application may indicate the wrong value for forced points. Refer to technical note
TN20040.

1.13.11.

Don’t delete the APPLI.MDF and APPLI.MDH files

The APPLI.MDH and APPLI.MDF files are the databases used by the IOU manager to store details of
each compilation used in an intelligent online update, as described in section 1.5.1. Deleting these files

Advertising