Filter
Top Products
Reference Manual
00809-0100-4696, Rev AA
September 2004
4-3
Rosemount 848L
TROUBLESHOOTING
FOUNDATION Fieldbus
Resource Block
I/O Transducer and Logic Block Troubleshooting
NAMUR Sensors
Symptom Possible Cause Corrective Action
Device does not show
up in the live list
Network configuration parameters
are incorrect
Set the network parameters of the LAS (host system) according to the FF
Communications Profile
ST: 8
MRD: 10
DLPDU PhLO: 4
MID: 7
TSC: 4 (1 ms)
T1: 1920000 (60 s)
T2: 5760000 (180 s)
T3: 480000 (15 s)
Network address is not in polled
range
Set first Unpolled Node and Number of UnPolled Nodes so that the device
address is within range
Power to the device is below the
9 VDC minimum
Increase the power to at least 9V
Noise on the power /
communication is too high
Verify terminators and power conditioners are within specification
Verify that the shield is properly terminated and not grounded at both ends. It is
best to ground the shield at the power conditioner
Device that is acting as
a LAS does not send
out CD
LAS Scheduler was not
downloaded to the Backup LAS
device
Ensure that all of the devices that are intended to be a Backup LAS are
marked to receive the LAS schedule
All devices go off live
list and then return
Live list must be reconstructed by
Backup LAS device
Current link setting and configured links settings are different. Set the current
link setting equal to the configured settings.
Symptom Possible Causes Corrective Action
Mode will not leave
OOS
Target mode not set Set target mode to something other than OOS.
Memory Failure, Communication
Failure, Body Temperature
Failure
BLOCK_ERR will show the lost NV Data or Lost Static Data bit set. Restart the
device by setting RESTART to Processor. If the block error does not clear, call
the factory.
No I/O Power Ensure power at I/O Power Terminals are between 9-32 VDC.
Block Alarms Will not
work
Features FEATURE_SEL does not have Alerts enabled. Enable the report bit.
Notification LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
Symptom Possible Causes Corrective Action
Mode will not leave
OOS
Target mode not set Set target mode to something other than OOS.
Resource block The actual mode of the Resource block is in OOS. See Resource Block
Diagnostics for corrective action.
i/O Transducer Block The actual mode of the Transducer Block is OOS, set it to Auto
Symptom Possible Causes Corrective Action
I/O Failure Open or shorted sensor Check sensor and wiring