Unexpected schedule contents or results

This topic lists some issues when unexpected schedule contents or results occur.

A schedule no longer appears on the Schedules tab.

Any user with

Delete a schedule

permission can delete any schedule from FactoryTalk AssetCentre. You do not have to create a schedule to be able to delete that schedule. If you or another FactoryTalk AssetCentre user has permission and deletes an asset from the asset tree, the schedule will be deleted. This occurs if an asset is the starting point (the top-level asset) of a schedule. The schedule cannot be retrieved. You must add the device to the asset tree again and then recreate the asset's schedule.

An asset is missing from a schedule.

If you or another FactoryTalk AssetCentre user deletes an asset from the asset tree, that asset will be removed from any schedules in which it was included. To restore that asset to the schedule, you would have to add the asset back into the container in the asset tree that is the starting point of the schedule. When you add the asset back to the container, it will appear in the schedule again, but it will have the default operation properties set under

Tools > Options

. If these are not the desired properties, you can change the properties for that asset in that schedule.

For Device Monitor schedules, open the Logix 5000 asset's properties and browse for Addressing Info. This should set the

Change Detect Capable

field to

True

so that the asset will be included in the schedule. Device Monitor is only available for Logix 5000 version 20 or higher controllers.

An asset's operation properties have reverted to defaults.

All assets added to a schedule use the default operation properties set through

Tools > Options

. If you move or copy an asset in the asset tree to another scheduled container in the tree, you must set the desired operation properties again.

My schedule contains extra devices that I don't want in the schedule.

Devices that support the scheduled operation will automatically be added to an existing schedule for a container as soon as the device is added to the container in the asset tree. To exclude assets from a schedule, disable the assets you do not want included in the schedule.

A device in a scheduled container does not appear as an asset in the schedule.

You will be unable to create a schedule for an asset that is to be the starting point of a schedule if the asset is not supported by the scheduled operation. Also, a schedule will not include an asset that is not supported by the selected operation. For example, if you have Disaster Recovery for Rockwell devices, but did not purchase Disaster Recovery for Motoman Robots, you won't be able to create a schedule for a Motoman robot, nor will a Motoman robot appear in a schedule for its parent container.

Differences were detected for an excluded block (Siemens S7 Controller (STEP7))

If differences are detected during a compare operation for a data block that you excluded and you have set

Compare Data Blocks by Length and Structure

to

True

, it means the length or structure changed (for example, a DB block was added or a data type changed).

Also, if you manually change an initial value for a parameter in a data block using your editing software for the Siemens S7 Controller (STEP7), it will register as a change in length and structure. Even if you exclude the data block, a change in length and structure is detected during a comparison (if Compare Data Blocks by Length and Structure is set to

True

).

Additionally, if you manually change an initial value for a parameter in a data block, the connection between the address and the symbolic name is lost. Only the address can be shown and a backup and compare operation will report differences. The symbolic names are still available in the project in the Configuration Data binder.

Cannot retrieve the MAC address and hardware serial number of the Allen-Bradley PLC-5 or SLC 500 controllers using a CIP scan

The Asset Inventory Agent uses RSLinx Classic when scanning a CIP network for devices. When performing a CIP scan using the Ethernet driver for the PLC-5 or SLC 500 controller, the device’s IP addressing in RSLinx Classic must follow this format: IP address :EIP, for example, 10.224.108.186 :EIP. This format ensures that the scan can retrieve the controller MAC address and hardware serial number.

To resolve this problem, do one of the following:

Before you begin, make sure that you have created an Ethernet IP driver.

To create an Ethernet IP driver:

To change the Asset Inventory driver from Ethernet to Ethernet IP:

Or