Shortcut types

A shortcut is a name that stands for the device you want to connect to, and the data that device contains. The communication path associated with the shortcut tells the application where to find that data. Shortcuts are added, deleted, or modified using the
Shortcut Properties
table in the
Device Shortcuts
area of the
Communication Setup
editor.
The following table shows the available shortcut types. Select one shortcut type for each shortcut.
Shortcut type
Description
Processor
Used for the processor type devices, such as 1756-L53, 1756-L61S, 1756-L64, 1756-L75, and
CompactLogix
L32E Processor.
EDS Parameter
Used for devices in which the EDS parameter is defined, such as 1734-and DeviceNet Adaptor, 1734-ADNX, 1747-AENTR, 1756-DNB, and 1783-MS10T Stratix 8300.
Symbolic
Used for devices that have tags or symbols defined, such as the 1426
PowerMonitor™
5000,
Micro800
series (Micro820, Micro830, and Micro850) controllers, and 193 E1 Plus Solid-State Overload Relays.
Unsolicited Message
Used for the
ControlLogix
,
PLC-2
, PLC-5, and SLC 500 controllers via EtherNet/IP. Additional options show when this shortcut type is selected. Starting from version 6.10.00, FactoryTalk Linx supports PLC-2 communication via the unsolicited message shortcut type. Starting from version 6.31.00, FactoryTalk Linx supports PLC-5 and SLC 500 communication via unsolicited message shortcut type.
CIP Object
Supports accessing devices' CIP Object instance attributes as tags.
You must select a suboption of the CIP Object. Currently,
FactoryTalk Linx
supports the
Energy
and
Class/Instance/Attribute Message
suboption.
Redundant Controller Path
Used for a single
ControlLogix
controller with redundant communication paths. The default path names are
Path1
and
Path2
.
Redundant
ControlLogix
Controller
Used for two
ControlLogix
controllers in a single
ControlLogix
redundancy configuration connected to redundancy modules with different communication paths. The default path names are
Primary Controller
and
Secondary Controller
.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal