Emerson 475 User Manual page 74

5-4
Table 5-2. Troubleshooting Table for the Fieldbus Protocol
Symptom Possible Causes
No communication The Field Communicator
with device. is connected to a
segment with DeltaV and
the device on the same
segment is being
commissioned using
DeltaV.
Connected to a This issue is caused by
segment in a bench the speed at which
configuration and the certain LAS-enabled
Live Device List devices are attempting to
remains blank (even run the segment.
the Field
Communicator does
not appear).
Unable to change the The Field Communicator
address of a device. is unable to change the
address of a device that
is currently the LAS.
The Field A host takes over as the
Communicator does LAS.
not remain the LAS
on a segment.
A backup LAS takes over
as the LAS. The lower the
address and Slot Time of
the device, the more
likely this will occur.
Troubleshooting
Solution
The Field Communicator is unable
to communicate with this device
until you go offline and then back
online.
Establish communication by
putting the Field Communicator on
the segment first and then adding
one or more devices. By putting
the Field Communicator on first, it
will remain the LAS and control the
communication.
Establish communication by
putting the Field Communicator on
the segment first and then adding
one or more devices. By putting
the Field Communicator on first, it
will remain the LAS and allow the
address change.
When a host is established on a
segment, it will take over as the
LAS. No action is required.
See "Changing the Slot Time" on
page 4-16.