Table of Contents
Advertisement
Troubleshooting
Table 5-2. Troubleshooting table for the fieldbus protocol
Symptom
Possible causes
No
The Field
communication
Communicator is
with device.
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
segment in a
by the speed at
bench
which certain
configuration and
LAS-enabled
the Live Device
devices are
List remains
attempting to run the
blank (even the
segment.
Field
Communicator
does not appear).
Unable to change
The Field
the address of a
Communicator is
device.
unable to change the
address of a device
that is currently the
LAS.
The Field
A host takes over as
Communicator
the LAS.
does 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.
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 76.
83
Advertisement
Table of Contents
