0 |
Invalid frequency output |
1 |
Uncorrected Volume Flow Rate |
2 |
|
3 |
Pressure |
4 |
Temperature |
5 |
Zero Flow Velocity |
6 |
Flow Velocity |
7 |
Velocity |
8 |
Sound Velocity |
9 |
Path |
10 |
A1 |
11 |
A2 |
12 |
B1 |
13 |
B2 |
14 |
C1 |
15 |
C2 |
16 |
D1 |
17 |
D2 |
18 |
Performance (%) |
19 |
Gain (dB) |
20 |
SNR (dB) |
21 |
Signal (mV) |
22 |
Noise (mV) |
23 |
Acknowledge |
24 |
No Longer Active |
25 |
Not Currently Active - Requires Acknowledge |
26 |
Display Meter K-Factors |
27 |
AO1 Content Changed |
28 |
AO2 Content Changed |
29 |
Freq1 Content Changed |
30 |
Freq2 Content Changed |
31 |
Units Changed |
32 |
Start |
33 |
Abort |
34 |
End |
35 |
Disable |
36 |
Enable |
37 |
Setup Units |
38 |
Setup Outputs |
39 |
Setup HART |
40 |
Analog Output 1 Trim |
41 |
Analog Output 2 Trim |
42 |
Refresh Alerts |
43 |
Variable Summary |
44 |
F: Configuration Lost, Latched Until Acknowledged - Acknowledge |
45 |
F: Configuration Lost, Latched Until Acknowledged - Not Currently Active - Requires Acknowledge |
46 |
F: Acquisition Mode - Acknowledge |
47 |
F: Acquisition Mode - Not Currently Active - Requires Acknowledge |
48 |
F: Acquisition Module Error - Acknowledge |
49 |
F: Acquisition Module Error - Not Currently Active - Requires Acknowledge |
50 |
F: Too Few Operating Chords - Acknowledge |
51 |
F: Too Few Operating Chords - Not Currently Active - Requires Acknowledge |
52 |
F: Diagnostic Core File Generated, Latched Until Acknowledged - Acknowledge |
53 |
F: Diagnostic Core File Generated, Latched Until Acknowledged - No Longer Active |
54 |
F: Electronics Voltage Out Of Range |
55 |
F: Acquisition Module is Not Compatible with Firmware |
56 |
F: Watchdog Reset, Latched Until Acknowledged - Acknowledge |
57 |
F: Watchdog Reset, Latched Until Acknowledged - No Longer Active |
58 |
M: Chord A Hard Failed |
59 |
M: Chord B Hard Failed |
60 |
M: Chord C Hard Failed |
61 |
M: Chord D Hard Failed |
62 |
M: Flow Pressure Invalid - Acknowledge |
63 |
M: Flow Pressure Invalid - Not Currently Active - Requires Acknowledge |
64 |
M: Flow Temperature Invalid - Acknowledge |
65 |
M: Flow Temperature Invalid - Not Currently Active - Requires Acknowledge |
66 |
M: Clock Invalid |
67 |
M: Reset Required |
68 |
A: Reverse Flow Detected - Acknowledge |
69 |
A: Reverse Flow Detected - Not Currently Active - Requires Acknowledge |
70 |
A: Meter Velocity Above Maximum Limit - Acknowledge |
71 |
A: Meter Velocity Above Maximum Limit - Not Currently Active - Requires Acknowledge |
72 |
A: Flow-Condition Volumetric Flow Rate Validity |
73 |
A: Analog Output 1 Validity |
74 |
A: Analog Output 2 Validity |
75 |
A: Frequency Output 1 Data is Invalid |
76 |
A: Frequency Output 2 Data is Invalid |
77 |
A: HART Fourth Variable Validity |
78 |
A: HART Command 33 Slot 0 Validity |
79 |
A: HART Command 33 Slot 1 Validity |
80 |
A: HART Command 33 Slot 2 Validity |
81 |
A: HART Command 33 Slot 3 Validity |
82 |
A: HART Third Variable Validity |
83 |
A: Analog Output 1 (HART PV) is Saturated |
84 |
A: Analog Output 2 (HART SV) is Saturated |
85 |
A: Analog Output 1 (HART PV) is Fixed |
86 |
A: Analog Output 2 (HART SV) is Fixed |
87 |
A: Average Sound Velocity Out-Of-Limits |
88 |
A: Configuration Changed, Latched Until Acknowledged - Acknowledge |
89 |
A: Configuration Changed, Latched Until Acknowledged - No Longer Active |
90 |
A: Power Failure, Latched Until Acknowledged - Acknowledge |
91 |
A: Power Failure, Latched Until Acknowledged - No Longer Active |
92 |
A: Flow-Condition Pressure Out-Of-Limits |
93 |
A: Flow-Condition Temperature Out-Of-Limits |
94 |
A: Alarm Archive Log is Full |
95 |
A: Analog Output 1 Test Enable |
96 |
A: Analog Output 2 Test Enable |
97 |
A: Audit Archive Log is Full |
98 |
A: Daily Archive Log is Full |
99 |
A: Electronics Temperature is Out Of Nominal Range |
100 |
A: Frequency Output 1 Pair Test Enable |
101 |
A: Frequency Output 2 Pair Test Enable |
102 |
A: Hourly Log Full Indicator |
103 |
A: System Archive Log is Full |
104 |
Comm Status: Polled |
105 |
Overview |
106 |
Configure |
107 |
Service Tools |
108 |
Device Status: Good |
109 |
No Active Alerts |
110 |
Device Status: Failed |
111 |
Device Status: Maintenance |
112 |
Device Status: Advisory |
113 |
Zero Calibration |
114 |
Device Information |
115 |
Manual Setup |
116 |
Alert Setup |
117 |
Alerts |
118 |
Variables |
119 |
Trends |
120 |
Maintenance |
121 |
Identification |
122 |
Revisions |
123 |
Alarm Type and Security |
124 |
Device Variables Mapping |
125 |
Units |
126 |
Analog Output 1 (HART) |
127 |
HART Parameters |
128 |
Analog Output 2 |
129 |
Frequency/Digital Outputs |
130 |
Frequency/Digital Output 1 |
131 |
Frequency/Digital Output 2 |
132 |
Frequency/Digital Output 3 |
133 |
Frequency and Digital Output 1 |
134 |
Frequency Output 1 |
135 |
Digital Output 1 |
136 |
Frequency and Digital Output 2 |
137 |
Frequency Output 2 |
138 |
Digital Output 2 |
139 |
Temperature |
140 |
Pressure |
141 |
Digital Input |
142 |
Flow Analysis Alerts |
143 |
Detect Reverse Flow |
144 |
Set Flow Range Limits |
145 |
Flow Data |
146 |
Flow Values |
147 |
Flow Analysis |
148 |
Path Information |
149 |
Performance |
150 |
Gain |
151 |
SNR |
152 |
Signal |
153 |
Noise |
154 |
Flow Totals |
155 |
Volume Totals |
156 |
All Variables |
157 |
Primary Variable |
158 |
Status: Good |
159 |
Status: Bad |
160 |
Secondary Variable |
161 |
Third Variable |
162 |
Fourth Variable |
163 |
Routine Maintenance |
164 |
Voltage Units |
165 |
HART Voltage Units |
166 |
Decibel Units |
167 |
HART Decibel Units |
168 |
Firmware |
169 |
Meter CPU Firmware Revision |
170 |
HART Device Variable 0 (uncorrected volumetric flow rate) value. The units are specified by the 'HARTVolFlowRateUnit' data point. |
171 |
.2f |
172 |
Upper Range |
173 |
Lower Range |
174 |
HART Device Variable 6 (flow pressure) value. The units are specified by the 'HARTPressureUnit' data point. |
175 |
Device Variable 6 |
176 |
HART Device Variable 7 (flow temperature) value. The units are specified by the 'HARTTemperatureUnit' data point. |
177 |
Device Variable 7 |
178 |
.0f |
179 |
Pressure Source |
180 |
Not Used |
181 |
Live Analog |
182 |
Fixed |
183 |
Temperature Source |
184 |
Alarm Selection |
185 |
The pressure and/or temperature source when the corresponding input is in alarm. Either the last good, i.e. non-alarm, value or a fixed value is used. |
186 |
Hold Last Output Value |
187 |
Used Fixed Value |
188 |
Velocity Units |
189 |
HART velocity unit. |
190 |
Failed Detail Status Byte 0 |
191 |
Reserved |
192 |
Acquisition Module is Not Compatible with Firmware |
193 |
Watchdog Reset, Latched Until Acknowledged |
194 |
Electronics Voltage Out Of Range |
195 |
Acquisition Module Error |
196 |
Diagnostic Core File Generated, Latched Until Acknowledged |
197 |
Maintenance Detail Status Byte 0 |
198 |
Advisory Detail Status Byte 0 |
199 |
Base-Condition Volumetric Flow Rate Validity |
200 |
Flow-Condition Volumetric Flow Rate Validity |
201 |
Advisory Detail Status Byte 1 |
202 |
Analog Output 1 (HART PV) is Fixed |
203 |
Analog Output 2 (HART SV) is Fixed |
204 |
Analog Output 1 Validity |
205 |
Analog Output 2 Validity |
206 |
Frequency Output 1 Data is Invalid |
207 |
Frequency Output 2 Data is Invalid |
208 |
Analog Output 1 Test Enable |
209 |
Analog Output 2 Test Enable |
210 |
Advisory Detail Status Byte 2 |
211 |
HART Fourth Variable Validity |
212 |
HART Third Variable Validity |
213 |
System Archive Log is Full |
214 |
Alarm Archive Log is Full |
215 |
Audit Archive Log is Full |
216 |
Daily Archive Log is Full |
217 |
Hourly Log Full Indicator |
218 |
Advisory Detail Status Byte 3 |
219 |
HART Command 33 Slot 3 Validity |
220 |
HART Command 33 Slot 2 Validity |
221 |
HART Command 33 Slot 1 Validity |
222 |
HART Command 33 Slot 0 Validity |
223 |
Flow-Condition Temperature Out-Of-Limits |
224 |
Flow-Condition Pressure Out-Of-Limits |
225 |
Average Sound Velocity Out-Of-Limits |
226 |
Meter Velocity Above Maximum Limit |
227 |
.3f |
228 |
8.3f |
229 |
Device Description |
230 |
Device Description Build |
231 |
Volume Units |
232 |
HART volume unit. The volumetric flow rate unit, HARTVolFlowRateUnit is derived from this unit data point and the rate time unit data point HARTRateTimeUnit. |
233 |
Flow Rate Time Units |
234 |
HART flow rate time unit. This data point is used to derive the volumetric flow rate unit. |
235 |
HARTVolFlowRateUnit |
236 |
HART volumetric flow rate unit. This unit is derived from the volume unit HARTVolUnit and the flow rate time unit HARTRateTimeUnit data points. |
237 |
Content (Primary Variable) |
238 |
Selects the data to be represented by Analog Output 1. Is used for HART (slave) communication as the Primary Variable content. |
239 |
Content (Secondary Variable) |
240 |
Selects the data to be represented by Analog Output 2.Is used for HART (slave) communication as the Secondary Variable content. |
241 |
Content |
242 |
Selects the data to be represented by the frequency output 1 pair (1A and 1B). Frequency output 1 and digital output 1 share a common ground. |
243 |
Direction |
244 |
Selects the flow direction represented by the Frequency Output 1 pair,. When set to "Reverse" or "Forward", both channels A and B represent the specified content when the flow is in selected direction. When set to "Absolute", both channels A and B represent the specified content regardless of the flow direction. When set to "Bidirectional", channel A represents the specified content when the flow is in the forward direction and channel B represents the specified content when flow is in the reverse direction (See Liquid Ultrasonic Installation, Operations and Maintenance Manual: Frequency Outputs). |
245 |
Reverse |
246 |
Forward |
247 |
Absolute |
248 |
Bidirectional |
249 |
Selects the data to be represented by the frequency output 2 pair (2A and 2B). Frequency output 2 and digital output 2 share common ground. |
250 |
Selects the flow direction represented by the Frequency Output 2 pair Freq1A, Freq1B,. When set to "Reverse" or "Forward", both channels A and B represent the specified content when the flow is in selected direction. When set to "Absolute", both channels A and B represent the specified content regardless of the flow direction. When set to "Bidirectional", channel A represents the specified content when the flow is in the forward direction and channel B represents the specified content when flow is in the reverse direction (See Liquid Ultrasonic Installation, Operations and Maintenance Manual: Frequency Outputs). |
251 |
ZeroFlowCalReqControl |
252 |
Specifies the desired zero-flow calibration action. A zero-flow calibration process must be inactive in order to be started. The "Accept Result and Exit" selection is only valid when the status indicates "Completed Successfully." |
253 |
Exit/Abort |
254 |
Accept Result and Exit |
255 |
Status |
256 |
Current zero-flow calibration status indicator. |
257 |
Inactive |
258 |
In Progress |
259 |
Completed Successfully |
260 |
Failed - Chord Failure |
261 |
Failed - Too Large Offset |
262 |
Failed - Too Large Estimated Maximum Deviation |
263 |
Zero Calib Duration |
264 |
Specifies the zero-flow calibration duration. |
265 |
Factory-calibrated flow velocity (customer calibration not applied). This is the result of applying the factory calibration coefficients to the average weighted flow velocity, AvgWtdFlowVel. |
266 |
.4f |
267 |
Proposed Offset |
268 |
Zero-flow calibration result. This value is only valid and can only be accepted when the ZeroFlowCalStatus is "Completed Successfully." When accepted, this value is used to update the FwdA0 and RevA0 data points. This value is not retained through a power cycle. |
269 |
.5f |
270 |
Progress |
271 |
Zero-flow calibration progress (percent complete). |
272 |
Turbulence A |
273 |
Meter turbulence A is an estimate of the standard deviation of delta time as a percentage of delta time for chord A. for chord A. A value of 0% indicates no appreciable turbulence. |
274 |
#.2f |
275 |
Turbulence B |
276 |
Meter turbulence B is an estimate of the standard deviation of delta time as a percentage of delta time for chord B. A value of 0% indicates no appreciable turbulence. |
277 |
Turbulence C |
278 |
Meter turbulence C is an estimate of the standard deviation of delta time as a percentage of delta time for chord C. A value of 0% indicates no appreciable turbulence. |
279 |
Turbulence D |
280 |
Meter turbulence D is an estimate of the standard deviation of delta time as a percentage of delta time for chord D. A value of 0% indicates no appreciable turbulence. |
281 |
Symmetry |
282 |
Symmetry measurement. This compares the upper chord velocities FlowVelA + FlowVelB to the lower chord velocities FlowVelC+ FlowVelD. For perfectly symmetrical flow, this value equals 1.0. See also CrossFlow and ProfileFactor. This is only applicable to 4-path meters. |
283 |
#.3f |
284 |
Cross-Flow |
285 |
Measure of cross flow. This compares the flow velocities from one side of the meter FlowVelA + FlowVelC to the other side FlowVelB + FlowVelD. This value is equal to 1.0 when there is no cross-flow. See also Symmetry and ProfileFactor This is only applicable to 4-path meters. |
286 |
Profile Factor |
287 |
The ratio of the sum of the velocities of the inner chords, FlowVelB and FlowVelC, to the sum of the velocities of the outer chords, FlowVelA and FlowVelD. This ratio is a numerical representation of the velocities taken in cross section in the direction of flow. This is only applicable to 4-path meters. |
288 |
Swirl Angle |
289 |
The arctangent of the ratio of the tangential velocity, computed from the individual chordal velocities FlowVelA, FlowVelB, FlowVelC, and FlowVelD, to the average flow velocity. See also CrossFlow, Symmetry, and ProfileFactor. This is only applicable to 4-path meters. |
290 |
Average Flow Velocity |
291 |
Average flow velocity (per batch). This is the weighted sum of the chord flow velocities with the dry-calibration coefficients (A coefficients or meter factor FwdA0, FwdA1, FwdA2, FwdA3, RevA0, RevA1, RevA2, and RevA3 applied and any selected wet-calibration method applied. |
292 |
Flow Analysis Lower Velocity Range Limit |
293 |
The lower flow velocity limit for gating "flow analysis gated" values in daily and hourly logs. |
294 |
.1f |
295 |
Flow Analysis Upper Velocity Range Limit |
296 |
The upper flow velocity limit for gating "flow analysis gated" values in daily and hourly logs. |
297 |
Any Baseline Available |
298 |
Indicates whether or not the baselines are supported for this meter type. If the meter is an allocation type, DeviceNumber =3812, then the value is FALSE (0) and the baselines are not used. |
299 |
Available |
300 |
Not Available |
301 |
Model Number |
302 |
Changing this value requires warm-starting the meter. This value should only be changed at the factory or when replacing a CPU Module in the field. |
303 |
Forward Uncorrected Volume |
304 |
Accumulation of flow-condition volume (integer portion) in the forward direction. The total is computed using this integer portion (digits to the left of the decimal) with the fractional portion PosVolFlowFrac (digits to the right of the decimal) Note that internally this value rolls over at the units-converted equivalent of an unsigned 64 bit integer (18446744073709551615). However, when read via Modbus, the value rolls from 999,999,999 to 0. |
305 |
Reverse Uncorrected Volume |
306 |
Accumulation of flow-condition volume (integer portion) in the reverse direction. The total is computed using this integer portion (digits to the left of the decimal) with the fractional portion NegVolFlowFrac (digits to the right of the decimal) Note that internally this value rolls over at the units-converted equivalent of an unsigned 64 bit integer (18446744073709551615). However, when read via Modbus, the value rolls from 999,999,999 to 0. |
307 |
Forward Base Condition Volume |
308 |
Accumulation of base-condition volume (integer portion) in the forward direction. The total is computed using this integer portion (digits to the left of the decimal) with the fractional portion PosVolBaseFrac (digits to the right of the decimal) Note that internally this value rolls over at the units-converted equivalent of an unsigned 64 bit integer (18446744073709551615). However, when read via Modbus, the value rolls from 999,999,999 to 0. |
309 |
Reverse Base Condition Volume |
310 |
Accumulation of base-condition volume (integer portion) in the reverse direction. The total is computed using this integer portion (digits to the left of the decimal) with the fractional portion NegVolBaseFrac (digits to the right of the decimal) Note that internally this value rolls over at the units-converted equivalent of an unsigned 64 bit integer (18446744073709551615). However, when read via Modbus, the value rolls from 999,999,999 to 0. |
311 |
Pressure Units |
312 |
HART pressure unit. |
313 |
Temperature Units |
314 |
HART temperature unit. |
315 |
Selects the flow direction represented by Analog Output 1. When set to "Reverse" or "Forward", the analog output represents the specified content when the flow is in selected direction. When set to "Absolute", the analog output represents the specified content regardless of the flow direction. |
316 |
Alarm Action |
317 |
Specifies the action for Analog Output 1 current when the content is invalid. No special action is taken when set to None. |
318 |
High - 20 mA |
319 |
Low - 4 mA |
320 |
Hold Last Value |
321 |
Very Low - 3.5 mA |
322 |
Very High - 20.5 mA |
323 |
None |
324 |
Selects the flow direction represented by Analog Output 2. When set to "Reverse" or "Forward", the analog output represents the specified content when the flow is in selected direction. When set to "Absolute", the analog output represents the specified content regardless of the flow direction. |
325 |
Alarm Action |
326 |
Specifies the action for Analog Output 2 current when the content is invalid. No special action is taken when set to None. |
327 |
Maximum Frequency |
328 |
Selects the Frequency Output 1 pair maximum (full-scale) frequency used in determining the K-factor and inverse K-factor. |
329 |
1000 |
330 |
5000 |
331 |
B Phase Zeroed on Error |
332 |
When TRUE (1), forces the Frequency Output 1 channel B frequency to zero when the frequency pair's data is invalid. |
333 |
Not Forced to Zero on Error |
334 |
Forced to Zero on Error |
335 |
B Phase |
336 |
Selects the Frequency Output 1 pair channel B phase relative to the channel A phase based on the flow direction. |
337 |
Lag Forward, Lead Reverse |
338 |
Lead Forward, Lag Reverse |
339 |
Freq1FeedbackCorrectionPcnt |
340 |
Specifies the Frequency Output 1 pair percentage of error (determined by frequency feedback) to adjust for per batch. This only applies when the frequency pair content is selected to be a rate. |
341 |
Channel A Polarity |
342 |
Selects the Digital Output 1A polarity as "Normal" or "Inverted". For "Normal" polarity, a high output indicates either valid frequency data or forward flow (depending upon the content selected via the DO1AContent data point). For "Inverted" polarity, a low output indicates either valid frequency data or forward flow. |
343 |
Normal |
344 |
Inverted |
345 |
Channel A Content |
346 |
Selects the content (Freq1 Validity (0) or Flow Direction (2)) for Digital Output 1A to be directed to FODO1Source, FODO2Source or FODO3Source. |
347 |
Frequency Output 1 Validity |
348 |
Flow Direction |
349 |
Channel B Polarity |
350 |
Selects the Digital Output 1B polarity as "Normal" or "Inverted". For "Normal" polarity, a high output indicates either valid frequency data or forward flow (depending upon the content selected via the DO1BContent data point). For "Inverted" polarity, a low output indicates either valid frequency data or forward flow. |
351 |
Channel B Content |
352 |
Selects the content (Freq1 Validity (0) or Flow Direction (2)) for Digital Output 1B to be directed to FODO1Source, FODO2Source or FODO3Source. |
353 |
Selects the Frequency Output 2 pair maximum (full-scale) frequency used in determining the K-factor and inverse K-factor. |
354 |
When TRUE (1), forces the Frequency Output 2 channel B frequency to zero when the frequency pair's data is invalid. |
355 |
Selects the Frequency Output 2 pair channel B phase relative to the channel A phase based on the flow direction. |
356 |
Freq2FeedbackCorrectionPcnt |
357 |
Specifies the Frequency Output 2 pair percentage of error (determined by frequency feedback) to adjust for per batch. This only applies when the frequency pair content is selected to be a rate. |
358 |
Selects the Digital Output 2A polarity as "Normal" or "Inverted". For "Normal" polarity, a high output indicates either valid frequency data or forward flow (depending upon the content DO2AContent). For "Inverted" polarity, a low output indicates either valid frequency data or forward flow. |
359 |
Selects the content (Freq2 Validity (0) or Flow Direction (2)) for Digital Output 2A to be directed to FODO2Source or FODO3Source. |
360 |
Frequency Output 2 Validity |
361 |
Selects the Digital Output 2B polarity as "Normal" or "Inverted". For "Normal" polarity, a high output indicates either valid frequency data or forward flow (depending upon the content selected via the Digital Output 2B content data point). For "Inverted" polarity, a low output indicates either valid frequency data or forward flow. |
362 |
Selects the content (Freq2 Validity (0) or Flow Direction (2)) for Digital Output 2B to be directed to FODO2Source or FODO3Source. |
363 |
Analog output 1 zero scale volume flow rate. Used for scaling charts. |
364 |
Analog output 1 full scale volume flow rate. Used for scaling charts. |
365 |
Minimum input pressure. Used for scaling charts. |
366 |
Maximum input pressure. Used for scaling charts. |
367 |
Minimum input temperature. Used for scaling charts. |
368 |
Maximum input temperature. Used for scaling charts. |
369 |
General Polarity |
370 |
This value sets the polarity of digital input 1. A TRUE (1) value is normal polarity (default). A FALSE (0) value is inverted polarity. |
371 |
Calibration Polarity |
372 |
This point specifies the polarity for digital input 1 (DI1) when it is configured via IsDI1UsedForCal for use in synchronizing a calibration. See also IsDI1ForCalStateGated. |
373 |
Digital Input 1 Calibrate Active High |
374 |
Digital Input 1 Calibrate Active Low |
375 |
Calibration Gating |
376 |
This point specifies the calibration gating for digital input 1 when it is configured via IsDI1UsedForCal) for use in synchronizing a calibration. When FALSE (0), the calibration is started/stopped via an inactive->active edge; when TRUE (1), the calibration is started via an inactive->active state change and stopped via an active->inactive state change. The active edge/state is specified via the IsDI1ForCalActiveLow data point. |
377 |
Digital Input 1 Calibrate Edge Gated |
378 |
Digital Input 1 Calibrate State Gated |
379 |
Low Limit |
380 |
Pressure alert low limit. The pressure is invalid when the input flow pressure SpecFlowPressure, LiveFlowPressure is at or below this limit. |
381 |
High Limit |
382 |
Pressure alert high limit. The pressure is invalid when the input flow pressure SpecFlowPressure, LiveFlowPressure is at or above this limit. |
383 |
Fixed Pressure |
384 |
Specifies the flow-condition pressure used in calculations when the enable pressure input data point is set to "Fixed". |
385 |
Gage or Absolute |
386 |
Specifies whether the input pressure is absolute, TRUE (1), or gage FALSE (0). If the input pressure is gage, then the absolute pressure is calculated as the sum of the input gage pressure and the atmospheric pressure specified via the AtmosphericPress data point. |
387 |
Gage |
388 |
Atmospheric Pressure |
389 |
Specifies the atmospheric pressure. This value is required when the flow pressure input is "Fixed" and the input pressure unit is "Gage". |
390 |
Temperature alert low limit. The temperature is invalid when the input flow temperature is at or below this limit. |
391 |
Temperature alert high limit. The temperature is invalid when the input flow temperature is at or above this limit. |
392 |
Fixed Temperature |
393 |
Specifies the flow-condition temperature used in calculations when the enable temperature input data point is set to "Fixed". |
394 |
DampingValue |
395 |
Specifies the damping value for all outputs and measurement data points. The damping value is the (worst case) time for the outputs and measurement data points to reach 63% of the steady-state value in response to a step input. This is a function of the BatchUpdatePeriod. |
396 |
An average of FlowTemperature over one minute used for baselines |
397 |
An average of FlowPressure over one minute used for baselines |
398 |
#.1f |
399 |
Running Average Turbulence A |
400 |
An average of chord A turbulence over one minute used for baselines |
401 |
Running Average Turbulence B |
402 |
An average of chord B turbulence over one minute used for baselines |
403 |
Running Average Turbulence C |
404 |
An average of chord C turbulence over one minute used for baselines |
405 |
Running Average Turbulence D |
406 |
An average of chord D turbulence over one minute used for baselines |
407 |
Average Flow Velocity |
408 |
An average of AvgFlow over one minute used for baselines |
409 |
An average of CrossFlow over one minute used for baselines |
410 |
An average of ProfileFactor over one minute used for baselines |
411 |
An average of SwirlAngle over one minute used for baselines |
412 |
An average of Symmetry over one minute used for baselines |
413 |
Running Average Standard Deviation of Cross-Flow |
414 |
Running standard deviation of cross-flow over a minute. |
415 |
Running Average Standard Deviation of Profile Factor |
416 |
Running standard deviation of the profile factor over a minute. |
417 |
Running Average Standard Deviation of Symmetry |
418 |
Running standard deviation of Symmetry over a minute. |
419 |
Running Average Validity |
420 |
Are the values in the one minute averages valid for use with the baseline |
421 |
Not Valid |
422 |
Valid |
423 |
Flow direction indicator. |
424 |
Chord A |
425 |
Chord A flow velocity. |
426 |
Chord B |
427 |
Chord B flow velocity. |
428 |
Chord C |
429 |
Chord C flow velocity. |
430 |
Chord D |
431 |
Chord D flow velocity. |
432 |
Chord A sound velocity. |
433 |
Chord B sound velocity. |
434 |
Chord C sound velocity. |
435 |
Chord D sound velocity. |
436 |
Average Sound Velocity |
437 |
Average sound velocity (per batch) of all active chords |
438 |
Reverse Flow Volume |
439 |
Volume flowed from continuous flow in reverse direction. This volume is compared to the reverse flow limit to determine the reverse flow alert. It is only accumulated when the flow velocity is below the reverse flow velocity threshold. |
440 |
Signal A1 |
441 |
Batch average of the signal amplitude when transducer A1 receives a signal |
442 |
Signal A2 |
443 |
Batch average of the signal amplitude when transducer A2 receives a signal |
444 |
Signal B1 |
445 |
Batch average of the signal amplitude when transducer B1 receives a signal |
446 |
Signal B2 |
447 |
Batch average of the signal amplitude when transducer B2 receives a signal |
448 |
Signal C1 |
449 |
Batch average of the signal amplitude when transducer C1 receives a signal |
450 |
Signal C2 |
451 |
Batch average of the signal amplitude when transducer C2 receives a signal |
452 |
Signal D1 |
453 |
Batch average of the signal amplitude when transducer D1 receives a signal |
454 |
Signal D2 |
455 |
Batch average of the signal amplitude when transducer D2 receives a signal |
456 |
Noise A1 |
457 |
Batch average of the noise amplitude when transducer A1 receives a signal |
458 |
Noise A2 |
459 |
Batch average of the noise amplitude when transducer A2 receives a signal |
460 |
Noise B1 |
461 |
Batch average of the noise amplitude when transducer B1 receives a signal |
462 |
Noise B2 |
463 |
Batch average of the noise amplitude when transducer B2 receives a signal |
464 |
Noise C1 |
465 |
Batch average of the noise amplitude when transducer C1 receives a signal |
466 |
Noise C2 |
467 |
Batch average of the noise amplitude when transducer C2 receives a signal |
468 |
Noise D1 |
469 |
Batch average of the noise amplitude when transducer D1 receives a signal |
470 |
Noise D2 |
471 |
Batch average of the noise amplitude when transducer D2 receives a signal |
472 |
SNR A1 |
473 |
Average signal-to-noise ratio (A1). |
474 |
SNR A2 |
475 |
Average signal-to-noise ratio (A2). |
476 |
SNR B1 |
477 |
Average signal-to-noise ratio (B1). |
478 |
SNR B2 |
479 |
Average signal-to-noise ratio (B2). |
480 |
SNR C1 |
481 |
Average signal-to-noise ratio (C1). |
482 |
SNR C2 |
483 |
Average signal-to-noise ratio (C2). |
484 |
SNR D1 |
485 |
Average signal-to-noise ratio (D1). |
486 |
SNR D2 |
487 |
Average signal-to-noise ratio (D2). |
488 |
Performance A1 |
489 |
Percentage of good batch firings (path A1). |
490 |
Performance A2 |
491 |
Percentage of good batch firings (path A2). |
492 |
Performance B1 |
493 |
Percentage of good batch firings (path B1). |
494 |
Performance B2 |
495 |
Percentage of good batch firings (path B2). |
496 |
Performance C1 |
497 |
Percentage of good batch firings (path C1). |
498 |
Performance C2 |
499 |
Percentage of good batch firings (path C2). |
500 |
Performance D1 |
501 |
Percentage of good batch firings (path D1). |
502 |
Performance D2 |
503 |
Percentage of good batch firings (path D2). |
504 |
Gain A1 |
505 |
Gain when transducer A1 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
506 |
Gain A2 |
507 |
Gain when transducer A2 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
508 |
Gain B1 |
509 |
Gain when transducer B1 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
510 |
Gain B2 |
511 |
Gain when transducer B2 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
512 |
Gain C1 |
513 |
Gain when transducer C1 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
514 |
Gain C2 |
515 |
Gain when transducer C2 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
516 |
Gain D1 |
517 |
Gain when transducer D1 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
518 |
Gain D2 |
519 |
Gain when transducer D2 is receiving a signal. Gain is applied to the received signal in hardware in volts/volt (hardware gain units). Conversion from hardware gain to decibels is gain (db) = 20 * log10(gain(hw)). Alarm limits for gain alarms are GainLowLmt and GainHighLmt. |
520 |
Reverse Flow Volume Limit |
521 |
This is the limit for the reverse flow alert. If the volume for reverse flow exceeds this value with continuous reverse flow, the reverse flow alert will be set. |
522 |
Reverse Flow Zero Cutoff |
523 |
Velocity threshold below which the flow velocity is considered reversed (and thus the reverse flow volume is accumulated). |
524 |
Detect Reverse Flow |
525 |
Disables reverse flow detection , when set FALSE (0) Setting this to TRUE (1) will enable reverse flow detection if the flow analysis feature enable isTRUE (1) and the device number is 3414. |
526 |
Disabled |
527 |
Enabled |
528 |
Meter Serial Number |
529 |
The serial number for the ultrasonic meter. The meter serial number is located on the tag attached to the ultrasonic meter body and is included in the maintenance log and reports file. |
530 |
IsFODO1Avail |
531 |
Frequency Output/Digital Output 1 available indicator based on the CPU Module's I/O board and the optional I/O Module configuration. The content is selected by the FODO1 source selector and the output levels by the FODO1 mode selector. |
532 |
Source |
533 |
Selects the source for Frequency/Digital Output 1 if IsFODO1Avail is TRUE (1). The sources may be:
Frequency Output 1A based on Freq1Content
Frequency Output 1B based on Freq1Content and Freq1BPhase
Digital Output 1A based on DO1AContent
Digital Output 1B based on DO1BContent
The output levels are selected by FODO1Mode |
534 |
Frequency Output 1A |
535 |
Frequency Output 1B |
536 |
Digital Output 1A |
537 |
Digital Output 1B |
538 |
Mode |
539 |
Selects the output levels for Frequency/Digital Output 1 FODO1Source when IsFODO1Avail is TRUE (1) |
540 |
TTL |
541 |
Open Collector |
542 |
IsFODO2Avail |
543 |
Frequency Output/Digital Output 2 available indicator based on the CPU Module's I/O board and the optional I/O Module configuration. The content is selected by the FODO2 source selector and the output levels by the FODO2 mode selector. |
544 |
Selects the source for Frequency/Digital Output 2 if IsFODO2Avail is TRUE (1). The sources may be:
Frequency Output 1A based on Freq1Content
Frequency Output 1B based on Freq1Content and Freq1BPhase
Frequency Output 2A based on Freq2Content
Frequency Output 2B based on Freq2Content and Freq2BPhase
Digital Output 1A based on DO1AContent
Digital Output 1B based on DO1BContent
Digital Output 2A based on DO2AContent
Digital Output 2B based on DO2BContent
The output levels are selected by FODO2Mode |
545 |
Frequency Output 2A |
546 |
Frequency Output 2B |
547 |
Digital Output 2A |
548 |
Digital Output 2B |
549 |
Selects the output levels for Frequency/ Digital Output 2 FODO2Source when IsFODO2Avail is TRUE (1) |
550 |
IsFODO3Avail |
551 |
Frequency Output/Digital Output 3 available indicator based on the CPU Module's I/O board and the optional I/O Module configuration. The content is selected by the FODO3 source selector and the output levels by the FODO3 mode selector. |
552 |
Selects the source for Frequency/Digital Output 3 if IsFODO3Avail is TRUE (1). The sources may be:
Frequency Output 1A based on Freq1Content
Frequency Output 1B based on Freq1Content and Freq1BPhase
Frequency Output 2A based on Freq2Content
Frequency Output 2B based on Freq2Content and Freq2BPhase
Digital Output 1A based on DO1AContent
Digital Output 1B based on DO1BContent
Digital Output 2A based on DO2AContent
Digital Output 2B based on DO2BContent
The output levels are selected by FODO3Mode |
553 |
Selects the output levels for Frequency/Digital Output 3 FODO3Source when IsFODO3Avail is TRUE (1) |
554 |
General |
555 |
Primary Purpose Variable |
556 |
Shortcuts |
557 |
Device Identification |
558 |
Revision Numbers |
559 |
Configuration |
560 |
Analog Output 1 |
561 |
Security |
562 |
Write protect status represents the position of the PROTECT switch on the CPU module. |
563 |
Guided Setup |
564 |
Initial Setup |
565 |
After installation, run this wizard to configure units in which to display parameters when using HART interface. |
566 |
After installation, run this wizard to configure meter outputs.
|
567 |
After installation, run this wizard to setup the basic HART specific parameters. |
568 |
Refresh Note:
If changes are made to any Source variable on this page, apply changes and navigate off to Guided Setup and back to Manual Setup for the changes to be reflected in other Manual Setup pages. |
569 |
Live Temperature |
570 |
Temperature Alarm |
571 |
Live Pressure |
572 |
Pressure Alarm |
573 |
Pressure Type |
574 |
Flow Range Limits |
575 |
Configure Reverse Flow Detection |
576 |
Reverse Flow Detection |
577 |
Perform digital to analog trim of the first milliamp output. |
578 |
Perform digital to analog trim of the second milliamp output. |
579 |
This is a snapshot of the current alerts. To refresh, close and reopen this dialog.
|
580 |
This is a snapshot of the current alerts. To refresh, navigate off and back on to this page.
|
581 |
Failed - Fix Now |
582 |
Maintenance - Fix Soon |
583 |
Advisory |
584 |
HART Units |
585 |
The meter contains output(s) that can be configured as either a frequency output or a digital status. The Frequency outputs 1 and Digital outputs 1 are paired together meaning the Digital outputs 1 will report the status for the parameter for Frequency output 1. Similarly, Frequency outputs 2 and Digital outputs 2 are paired together. In addition, each Frequency output has an A and B output phase. |
586 |
Configure the available frequency and digital outputs. |
587 |
Analog Outputs |
588 |
The meter's measured average sound velocity is outside the defined limits.
Recommended Actions:
1. Verify that all chords are measuring the same Speed of Sound within about 0.15%. Look for alerts that indicate transducer problems and resolve any of these issues. This could include failing transducers, debris buildup on transducers, or incorrectly entered path lengths in the configuration.
2. If the chords agree well, it is recommended that the SSMin or SSMax be adjusted so the meter's average speed of sound falls within these limits.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
589 |
|
590 |
Acquisition Mode |
591 |
The meter is not measuring and is trying to acquire measurement data. Possible causes include empty pipe, transducer failures, miswired transducers, invalid geometry configuration, malfunctioning Acquisition Module and fluid type not supported by meter.
Recommended Actions:
1. Verify the process fluid rate has not exceeded the maximum rate indicated on the meter nameplate. Lower the flow rate if necessary.
2. If a new meter or upgraded meter, verify geometry configuration distance between transducers (for four-path meters LA, LB, LC, and LD and for dual-path meters LA and LB) and correct if needed. If these parameters are incorrect, check all meter parameters against the meter Zero Flow Calibration report. This report can be requested from your local area Daniel service representative.
3. Check transducers wiring. Verify all connections are secure and that wires are connected to the correct terminals on the Acquisition Module.
4. Replace Acquisition Module with a spare to see if this corrects the issue. If it does and the meter is still under warranty, you may request a replacement module from your local area Daniel service representative.
5. Collect a Maintenance log with Daniel MeterLink if the issue is unresolved and contact your local area Daniel service representative.
|
592 |
Chord A Hard Failed |
593 |
The meter is unable to obtain measurement data from this pair of transducers.
Recommended Actions:
1. If no other transducers are failed or are reporting status alerts, the issue is most likely isolated to this pair of transducers or its cabling. Check the transducer wiring for this pair of transducers to make sure connections are secure and wired correctly.
2. Verify that the meter run is not partially full where this top transducer pair is not submerged in the process fluid.
3. Verify the Gain A1 and Gain A2 of this transducer pair is not above 90dB. The gain values can be read on the Path Performance tab under Service Tools . If so, remove the transducers, clean, and reapply the coupling fluid to the front face of the transducers. If this does not correct the issue, at least one of the transducers in the pair should be replaced.
4. If transducer cabling allows, swap cabling of failed transducer pair with a pair with equal path lengths. If the alert remains active for this chord, then the transducers are working properly. If this alert clears but the chord that was swapped now fails, the issue is with the transducer.
5. If this issue is unresolved, collect a Maintenance Log, Configuration file and Waveform stream file with Daniel MeterLink and contact your local area Daniel service representative. |
594 |
Chord B Hard Failed |
595 |
The meter is unable to obtain measurement data from this pair of transducers.
Recommended Actions:
1. If no other transducers are failed or are reporting status alerts, the issue is most likely isolated to this pair of transducers or its cabling. Check the transducer wiring for this pair of transducers to make sure connections are secure and wired correctly.
2. Verify the Gain A1 and Gain A2 of this transducer pair is not above 90dB. The gain values can be read on the Path Performance tab under Service Tools . If so, remove the transducers, clean, and reapply the coupling fluid to the front face of the transducers. If this does not correct the issue, at least one of the transducers in the pair should be replaced.
3. If transducer cabling allows, swap cabling of failed transducer pair with a pair with equal path lengths. If the alert remains active for this chord, then the transducers are working properly. If this alert clears but the chord that was swapped now fails, the issue is with the transducer.
4. If this issue is unresolved, collect a Maintenance Log, Configuration file and Waveform stream file with Daniel MeterLink and contact your local area Daniel service representative. |
596 |
Chord C Hard Failed |
597 |
Chord D Hard Failed |
598 |
Analog Output 1 (HART PV) is Saturated |
599 |
Analog Output 1 is saturated (i.e. the loop current has reached its upper or lower endpoint and cannot increase or decrease any further).
Recommended Actions:
1. The analog output may need to be rescaled to prevent it from saturating. Use the Field Setup Wizard in Daniel MeterLink to configure Analog Output 1. |
600 |
Analog Output 2 (HART SV) is Saturated |
601 |
Analog Output 2 is saturated (i.e. the loop current has reached its upper or lower endpoint and cannot increase or decrease any further).
Recommended Actions:
1. The analog output may need to be rescaled to prevent it from saturating. Use the Setup Outputs wizard under Guided Setup to configure Analog Output 2. |
602 |
Analog Output 1 (AO1) is invalid. The analog output is considered invalid if the analog output is in test mode or the content the analog output is trying to drive is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output on Analog Output 1, resolving that issue should clear this alert.
2. If the content selected for Analog Output 1 is not in alarm, then verify that the output is not fixed or set in test mode.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
603 |
Analog Output 1 current is in test mode and fixed. The current can be fixed via the HART command 66.
Recommended Actions:
1. Once the Analog Output 1 is removed from test mode, this alert will clear. |
604 |
Analog Output 2 (AO2) is invalid. The analog output is considered invalid if the analog output is in test mode or the content the analog output is trying to drive is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output on Analog Output 2, resolving that issue should clear this alert.
2. If the content selected for Analog Output 2 is not in alarm, then verify that the output is not fixed or set in test mode.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
605 |
Analog Output 2 current is in test mode and fixed. The current can be fixed via the HART command 66.
Recommended Actions:
1. Once the Analog Output 2 is removed from test mode, this alert will clear. |
606 |
Configuration Changed, Latched Until Acknowledged |
607 |
The configuration checksum value has changed. This indicates that one or more parameters have been modified in the meter's configuration.
Recommended Actions:
1. Collect an Audit log using Daniel MeterLink in order to see what configuration parameters changed and when they changed.
2. The alert must be acknowledged to clear it from list of alerts. |
608 |
Configuration Lost, Latched Until Acknowledged |
609 |
The meter has performed a cold start. The meter configuration has reset to default values and the meter is not configured correctly to measure flow.
Recommended Actions:
1. Unless the Cold Start occurred after upgrading firmware, it is recommended to have the CPU Module replaced. Contact your local area Daniel service representative.
2. If the cold start occurred after a firmware upgrade, you must fully re-configure the meter from a previously saved configuration using the Edit/Compare Configuration screen in Daniel MeterLink.
3. The alert must be acknowledged to clear it from list of alerts per DidCnfgChksumChg.
4. If the issue is unresolved, contact your local area Daniel service representative. |
610 |
Power Failure, Latched Until Acknowledged |
611 |
The meter has had power removed for a period of time or the meter restarted itself such as after a firmware upgrade. The Audit log in the meter will indicate the power fail time.
Recommended Actions:
1. If this was a known power fail or restart of the meter just acknowledge this alert.
2. If this was an unexpected restart of the meter, verify the integrity of the power to the meter and make sure that the voltage level is in the range of 11-36 VDC at the meter.
3. The alert must be acknowledged to clear it from list of alerts.
4. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
612 |
The flow-condition pressure is outside the limits.
Recommended Actions:
1. If connected to a pressure transducer, verify that the transducer is functioning properly. Verify that the wiring is correctly connected to TB2-B pins 1 & 2 (ANALOG IN PT- and PT+). Verify that the current is between 4 mA and 20 mA.
2. Use the Pressure tab under Configure->Manual Setup to verify the input is properly configured for your pressure input.
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
613 |
The flow-condition temperature is outside the limits.
Recommended Actions:
1. If connected to a temperature transducer, verify that the transducer is functioning properly. Verify that the wiring is correctly connected to TB2-B pins 3 & 4 (ANALOG IN TT- and TT+). Verify that the current is between 4 mA and 20 mA.
2. Use the Temperature tab under Configure->Manual Setup to verify the input is properly configured for your temperature input.
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
614 |
The parameter which the Frequency Output 1 is configured to represent is invalid or the output is currently in test mode.
Recommended Actions:
1. You can determine whether the output is in test mode by using Meter Outputs in Daniel MeterLink.
2. If the parameter for which Frequency Output 1 is configured is invalid, other alerts will be present that will help you resolve the issue.
3. If the issue is unresolved, collect a Maintenance log and Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
615 |
The parameter which the Frequency Output 2 is configured to represent is invalid or the output is currently in test mode.
Recommended Actions:
1. You can determine whether the output is in test mode by using Meter Outputs in Daniel MeterLink.
2. If the parameter for which Frequency Output 2 is configured is invalid, other alerts will be present that will help you resolve the issue.
3. If the issue is unresolved, collect a Maintenance log and Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
616 |
The HART Fourth Variable value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
617 |
The HART Slot 0 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
618 |
The HART Slot 1 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
619 |
The HART Slot 2 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
620 |
The HART Slot 3 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
621 |
The HART Third Variable value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
622 |
An Acquisition Module-related error has been detected. The CPU Module's measurement LED (MEAS) will flash green when proper communications with the Acquisition Module are restored.
Recommended Actions:
1. If the CPU Module's measurement LED (MEAS) is not flashing green, check interconnect cable between Acquisition Module and the CPU Module.
2. If the CPU Module's measurement LED (MEAS) is still not flashing green, check the Acquisition Module error reasons code
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
623 |
The alarm archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect alarm archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadAlarmLog to overwrite old records. |
624 |
Enables the Analog Output Test mode for Analog Output 1. When in the Analog Output Test mode, Analog Output 1 is fixed at the percentage of full scale specified via the Analog Output 1 test mode output percent configuration point (regardless of the actual data content value). If Analog Output 1 remains in Analog Output Test mode for longer than the non-normal mode timeout, Analog Output 1 automatically exits Analog Output Test mode and returns to normal operation. |
625 |
Enables the Analog Output Test mode for Analog Output 2. When in the Analog Output Test mode, Analog Output 2 is fixed at the percentage of full scale specified via the Analog Output 2 test mode output percent configuration point (regardless of the actual data content value). If Analog Output 2 remains in Analog Output Test mode for longer than the non-normal mode timeout, Analog Output 2 automatically exits Analog Output Test mode and returns to normal operation. |
626 |
The audit archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect audit archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadAuditLog to overwrite old records. |
627 |
Clock Invalid |
628 |
The meter's hardware clock has been set to a date prior to Jan. 1, 2003.
Recommended Actions:
1. The real time clock has a power backup of about 2 weeks. If the meter remains unpowered for more than this time, the real time clock will reset back to Jan. 1, 2000. If this is the issue, use either the Field Setup Wizard or the Monitor screen in Daniel MeterLink to set the correct date and time.
2. If the meter has not been unpowered for more than a week, then CPU Module should be replaced as the real time clock or its backup power source may be damaged.
3. Contact your local area Daniel service representative for assistance in getting a replacement CPU board. |
629 |
A diagnostic core file has been generated which may indicate a problem with the meter.
Recommended Actions:
1. The alert must be acknowledged to clear it from list of alerts.
2. Collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative. |
630 |
The daily archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect daily archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadDailyLog to overwrite old records. |
631 |
Electronics Temperature is Out Of Nominal Range |
632 |
The temperature of the electronics is out of nominal operating range (below -40 °C or above 100 °C ). Operating outside the nominal operating range could lead to a system failure.
Recommended Actions:
1. Attempt to warm or cool the meter electronics housing.
2. If the electronics is mounted to the meter and the process fluid in the meter is over 65 °C, you must remote mount the electronics off from the meter body.
3. Collect a Maintenance log using Daniel MeterLink while the meter is experiencing the issue, collect an Archive log (Daily/Hourly/Alarm/Audit/System) using Daniel MeterLink from the meter and contact your local area Daniel service representative. |
633 |
The CPU Board system voltages or Acquisition Module system voltages are out-of-range. Valid CPU Module voltages are 1.0V, 1.2V, 2.5V, 3.3V or valid Acquisition Module System voltages are 1.2V, 2.5V or 3.3V.
Recommended Actions:
1. Replace the CPU Module if one or more of the CPU voltages is out-of-range.
2. Replace Acquisition Module if one or more of the Acquisition Module voltages is out-of-range.
3. If the issue is unresolved, contact your local area Daniel service representative. |
634 |
Frequency Output 1 Pair Test Enable |
635 |
Frequency Output 1 is in test mode which means the pulses output do not reflect the process flow through the meter. Test mode allows the connection from this output to a flow computer to be verified.
Recommended Actions:
1. Use the Meter Outputs screen in Daniel MeterLink to disable the test mode for Frequency Output 1 to clear this alert and return the meter back to its normal mode of operation.
2. Unless Daniel MeterLink or another application through Modbus is reenabling the test mode, the output will revert back to the normal mode of operation in a user configured timeout period which can be up to 30 minutes. |
636 |
Frequency Output 2 Pair Test Enable |
637 |
Frequency Output 2 is in test mode which means the pulses output do not reflect the process flow through the meter. Test mode allows the connection from this output to a flow computer to be verified.
Recommended Actions:
1. Use the Meter Outputs screen in Daniel MeterLink to disable the test mode for Frequency Output 2 to clear this alert and return the meter back to its normal mode of operation.
2. Unless Daniel MeterLink or another application through Modbus is reenabling the test mode, the output will revert back to the normal mode of operation in a user configured timeout period which can be up to 30 minutes. |
638 |
The hourly archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect hourly archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadHourlyLog to overwrite old records. |
639 |
Velocity is above the meter maximum velocity limit.
Recommended Actions:
1. Lower the velocity of the meter as this alert indicates you are running above a safe limit that could damage the meter run or could indicate you are running above your upper calibration limit where meter uncertainty could increase.
2. Use the Edit/Compare configuration screen in Daniel MeterLink to change the value of MeterMaxVel if desired. It is recommended to set this either to the maximum calibrated velocity of the meter or to the maximum safe operating velocity of the meter run. The maximum safe operating velocity typically is to prevent erosion of the pipe internal diameter and prevent damage to protrusions such as thermal wells. |
640 |
Reverse Flow Detected |
641 |
The meter has accumulated a reverse flow volume greater than a user configurable limit. This alert is configured as part of the Flow Analysis Alerts setup under the Alert Setup menu.
Recommended Actions:
1. Check valves for leaks.
2. If metering run is known to have some volume of reverse flow when flow is stopped, reconfigure the reverse flow volume limit to allow a greater volume.
3. If meter regularly flows in the reverse direction, this alert should be disabled. It is only intended to be used for unidirectional applications.
4. If the issue is unresolved, collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative. |
642 |
The system archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect system archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadSystemLog to overwrite old records. |
643 |
Too Few Operating Chords |
644 |
Number of operating chords is less than the minimum number for a valid measurement. Operating chords are those which are not manually set inactive and not marked as failed.
Recommended Actions:
1. Check the other alerts that indicate why a chord is hard failed. Resolving these should resolve this issue.
2. If this issue is unresolved, collect a Maintenance log and Archive log and contact your local area Daniel service representative. |
645 |
The firmware cannot work with the installed Acquisition Module. Either the Acquisition Module is newer than the firmware and the firmware does not recognize it or the Acquisition Module is installed on a meter running firmware for the opposite product (Gas/Liquid).
Recommended Actions:
1. Upgrade the firmware in the meter to the latest version using Daniel MeterLink. Contact your local area Daniel service representative to obtain the latest firmware.
2. If the latest firmware revision did not resolve the issue, replace the Acquisition Module.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
646 |
Reset Required |
647 |
The meter configuration has changed and requires a restart for the change to take effect.
Recommended Actions:
1. If you are unaware of changes made to the meter's configuration, collect the Audit log using the Archive Logs screen in Daniel MeterLink to review configuration changes. If the changes are valid, momentarily remove power from the meter to allow it to restart which will clear this alert.
2. If the Audit log shows no changes, contact your local area Daniel service representative for assistance. |
648 |
Flow Pressure Invalid |
649 |
Pressure is invalid if the flow pressure is outside the limits defined by the low and high pressure alert limits.
Recommended Actions:
First Time Startup Issues:
1. Verify that there is voltage to the pressure sensor, either from the terminal on the meter's power supply board or from an external power supply.
2. If using an analog pressure device, verify that the pressure sensor is properly wired to connector TB2-B pins 1 & 2 (ANALOG IN PT- & PT+) .
3. Use the Pressure tab under Configure->Manual Setup to verify the input is properly configured for your pressure input.
4. If using a flow computer to write pressure to the meter, verify that it is properly writing to fixed flow pressure in the proper units. The current value will be displayed as Fixed pressure in the Pressure tab under Configure->Manual Setup.
5. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
Run Time Issues:
1. Adjust pressure of process fluid to within alarm limits.
2. If using an analog pressure device and input reading is 0, check if IsAI2Avail is equal to 1 in the Meter Information dialog in Daniel MeterLink. If it is not 1, either the I/O Board has been removed or is damaged. Reinstall or replace the board if this value is 0.
3. If using an analog pressure device, verify that the pressure sensor is working properly.
4. If using an analog pressure device, recheck wiring and switch settings as noted above under First Time Setup Issues.
5. If flow computer is writing values to the fixed flow pressure, verify that the flow computer is still writing valid values without Modbus write errors.
6. Reverify the pressure input settings are correct on the Pressure tab under Configure->Manual Setup.
7. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
|
650 |
There is an error with the AGA8 base-condition volumetric flow rate. The base-condition volumetric flow rate becomes invalid if the flow-condition volumetric flow rate validity , pressure validity, temperature validity, or AGA8 flow calculation validity are set to invalid.
Recommended Actions:
1. Other primary cause alerts will be present in the alert list. Resolve those alerts first and this alert will clear.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
651 |
The meter either has not collected enough information from the chords to make an accurate measurement or the pressure and/or temperature are invalid and meter is performing pressure or temperature expansion corrections on the meter internal diameter. This is an alert condition that shows the validity of the flow-condition volumetric flow rate. The flow-condition volumetric flow rate becomes invalid if the uncorrected flow-condition volumetric flow rate validity, temperature expansion correction validity, pressure expansion correction validity, or Flow-profile-effect correction validity is invalid.
Recommended Actions:
1. If a Pressure expansion correction validity alert is present, correcting it may clear this alert.
2. If a Temperature expansion correction validity alert is present, correcting it may clear this alert.
3. If an Uncorrected flow-condition volumetric flow rate validity alert is present, correcting it may clear this alert.
4. If a Flow-profile-effect correction validity alert is present, correcting it may clear this alert.
5. If the issue is unresolved, collect a Maintenance Log with Daniel MeterLink and contact your local area Daniel service representative. |
652 |
Flow Temperature Invalid |
653 |
Temperature is invalid if the flow temperature is outside the limits defined by the low and high temperature alert limits.
Recommended Actions:
First Time Startup Issues:
1. Verify that there is voltage to the temperature sensor, either from the terminal on the meter's power supply board or from an external power supply.
2. If using an analog temperature device, verify that the temperature sensor is properly wired to connector TB2-B pins 3 & 4 (ANALOG IN TT- & TT+) .
3. Use the Temperature tab under Configure->Manual Setup to verify the input is properly configured for your temperature input.
4. If using a flow computer to write temperature to the meter, verify that it is properly writing to fixed flow temperature in the proper units. The current value will be displayed as Fixed temperature in the Temperature tab under Configure->Manual Setup.
5. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
Run Time Issues:
1. Adjust temperature of process fluid to within alarm limits.
2. If using an analog temperature device and input reading is 0, check if IsAI1Avail is equal to 1 in the Meter Information dialog in Daniel MeterLink. If it is not 1, either the I/O Board has been removed or is damaged. Reinstall or replace I/O board if this value is 0.
3. If using an analog temperature device, verify that the temperature sensor is working properly.
4. If using an analog temperature device, recheck wiring and switch settings as noted above under First Time Setup Issues.
5. If flow computer is writing values to the fixed flow temperature, verify that the flow computer is still writing valid values without Modbus write errors.
6. Reverify the temperature input settings are correct on the Temperature tab under Configure->Manual Setup.
7. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
|
654 |
Software watchdog initiated a meter warm-start. The watchdog keeps track of the performance of all metrology processes in the meter to ensure a reliable measurement. When a process stops responding, the watchdog forces the meter to restart.
Recommended Actions:
1. Collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative.
2. The alert must be acknowledged to clear it from list of alerts. |
655 |
3810 Series Liquid USM |
656 |
Daniel Industries |
657 |
MMBtu |
658 |
Million BTU |
659 |
MJ/s |
660 |
Megajoules per second |
661 |
MJ/d |
662 |
Megajoules per day |
663 |
MMBtu/s |
664 |
Million BTU per second |
665 |
MMBtu/h |
666 |
Million BTU per hour |
667 |
MMBtu/d |
668 |
Million BTU per day |
669 |
L/d |
670 |
Liters per day |
671 |
dB |
672 |
Decibels |
673 |
Write Protect Status |
674 |
Analog Output 2 Saturated |
675 |
Analog Output 2 Fixed |
676 |
Primary Variable Out of Limits |
677 |
Non-primary Variable Out of Limits |
678 |
PV Analog Output Saturated |
679 |
PV Analog Output Fixed |
680 |
More Status Available |
681 |
Cold Start |
682 |
Configuration Changed |
683 |
Field Device Malfunction |
684 |
CPU Serial Number |
685 |
Poll Address |
686 |
Number of Response Preambles |
687 |
Final Assembly Number |
688 |
Universal |
689 |
Hardware |
690 |
Software |
691 |
Field Device |
692 |
Acquisition Module Error, Latched Until Acknowledged |
693 |
Too Few Operating Chords, Latched Until Acknowledged |
694 |
Acquisition Mode, Latched Until Acknowledged |
695 |
Flow Temperature Invalid, Latched Until Acknowledged |
696 |
Flow Pressure Invalid, Latched Until Acknowledged |
697 |
Meter Velocity Above Max Limit, Latched Until Acknowledged |
698 |
Measurement and/or Output Data is Invalid |
699 |
One or More Meter Archive Logs are Full |
700 |
Reverse Flow Detected, Latched Until Acknowledged |
701 |
Enable on token-passing data link layer only |
702 |
Enable on TDMA data link layer only |
703 |
Enable on both TDMA and token-passing data link layer |
704 |
Wireless |
705 |
WirelessHART Device |
706 |
IEEE 802.15.4 2.4GHz DSSS with O-QPSK Modulation |
707 |
Primary |
708 |
Primary Analog Channel |
709 |
Secondary |
710 |
Secondary Analog Channel |
711 |
Tertiary |
712 |
Tertiary Analog Channel |
713 |
Quaternary |
714 |
Quaternary Analog Channel |
715 |
Quinary |
716 |
Quinary Analog Channel |
717 |
Critical Power Failure |
718 |
Lock all |
719 |
Trim not supported |
720 |
Configuration cannot be changed |
721 |
Locked by gateway |
722 |
Analog Input Channel |
723 |
Analog Output Channel |
724 |
Secondary Analog Channel Saturated |
725 |
Tertiary Analog Channel Saturated |
726 |
Quaternary Analog Channel Saturated |
727 |
Quinary Analog Channel Saturated |
728 |
Secondary Analog Channel Fixed |
729 |
Tertiary Analog Channel Fixed |
730 |
Quaternary Analog Channel Fixed |
731 |
Quinary Analog Channel Fixed |
732 |
8u |
733 |
Device Variable |
734 |
Analog Channel Number |
735 |
Analog Channel Number- Index into an array of Analog Channels. |
736 |
K-Factor: %[.1f]{kFactor1} pulses/%{0}
Inverse K-Factor: %[.4f]{inverseKFactor1} %{0}/pulse
|
737 |
K-Factor: %[.1f]{kFactor2} pulses/%{2}
Inverse K-Factor: %[.4f]{inverseKFactor2} %{2}/pulse
|
738 |
Invalid upper range - cannot calculate K-factor 1. |
739 |
K-factor 1 content is invalid. |
740 |
Invalid upper range - cannot calculate K-factor 2. |
741 |
K-factor 2 content is invalid. |
742 |
Time units invalid. |
743 |
Frequency Output 1
Content: |
744 |
Frequency Output 2
Content: |
745 |
Frequency Output 1
Not configured to a Frequency/Digital Output.
|
746 |
Frequency Output 2
Not configured to a Frequency/Digital Output.
|
747 |
K-Factor: Not Applicable to Velocity Output
|
748 |
|
749 |
Corrected Volume Flow Rate |
750 |
You must write analog output 1 content (the device variable mapped to PV) to the meter to refresh dependent values. |
751 |
You must write analog output 2 content to the meter to refresh dependent values. |
752 |
You must write frequency output 1 content to the meter to refresh dependent values. |
753 |
You must write frequency output 2 content to the meter to refresh dependent values. |
754 |
You must write units to the meter to refresh dependent values. |
755 |
Warning: Take the device out of process control loop. |
756 |
Enter zero flow calibration duration |
757 |
Wait for zero flow calibration to complete and then select End Zero to process the result.
Select Abort Zero to stop the zero flow calibration early without updating the zero flow velocity offset. |
758 |
Zero flow calibration not inactive |
759 |
Zero flow calibration aborted. The zero flow velocity offset has not been updated. |
760 |
It is now safe to put the device in process control loop. |
761 |
Zero flow calibration not started. |
762 |
Zero flow velocity offset %[.5f]{zeroFlowCalResult} %{0} |
763 |
Zero flow calibration failed due to chord failure. The zero flow velocity offset has not been updated. |
764 |
Zero flow calibration failed due to zero flow velocity offset too large. The zero flow velocity offset has not been updated. |
765 |
Zero flow calibration failed due to estimated maximum deviation too large. The zero flow velocity offset has not been updated. |
766 |
Enter the minimum reverse flow velocity above which to accumulate flow in the reverse direction for this alert. Enter as a positive value.
%[L]{0} |
767 |
Enter the accumulated volume limit above which an alert will be generated.
%[L]{1} |
768 |
Error: Detect Reverse Flow not enabled. The error was Invalid selection. |
769 |
Error: Detect Reverse Flow not enabled. The error was Value was too high. |
770 |
Error: Detect Reverse Flow not enabled. The error was Value was too low. |
771 |
Error: Detect Reverse Flow not enabled. The error was Too few data bytes received. |
772 |
Error: Detect Reverse Flow not enabled. The error was In write protect mode. |
773 |
Error: Detect Reverse Flow not enabled. The error was Invalid unit. |
774 |
Error: Detect Reverse Flow not enabled. The error was Busy. |
775 |
Error: Detect Reverse Flow not disabled. The error was Invalid selection. |
776 |
Error: Detect Reverse Flow not disabled. The error was Value was too high. |
777 |
Error: Detect Reverse Flow not disabled. The error was Value was too low. |
778 |
Error: Detect Reverse Flow not disabled. The error was Too few data bytes received. |
779 |
Error: Detect Reverse Flow not disabled. The error was In write protect mode. |
780 |
Error: Detect Reverse Flow not disabled. The error was Invalid unit. |
781 |
Error: Detect Reverse Flow not disabled. The error was Busy. |
782 |
Detect Reverse Flow enabled. |
783 |
Detect Reverse Flow disabled. |
784 |
Next |
785 |
select |
786 |
Select the output(s) to configure and click Next to continue. |
787 |
Frequency/Digital Outputs;Analog Outputs;Exit |
788 |
Back;Next |
789 |
Connect reference meter. |
790 |
About to set analog output 1 to %0 mA |
791 |
Enter Meter Value |
792 |
Is field device %0 mA output equal to reference meter? |
793 |
Returning field device to original output. |
794 |
About to set analog output 2 to %0 mA |
795 |
Reading Device Status... |
796 |
PV: %{0}
Value: %1 %2
Status: Bad
SV: %{3}
Value: %4 %5
Status: Bad |
797 |
PV: %{0}
Value: %1 %2
Status: Bad
SV: %{3}
Value: %4 %5
Status: Good |
798 |
PV: %{0}
Value: %1 %2
Status: Good
SV: %{3}
Value: %4 %5
Status: Bad |
799 |
PV: %{0}
Value: %1 %2
Status: Good
SV: %{3}
Value: %4 %5
Status: Good |
800 |
TV: %{0}
Value: %1 %2
Status: Bad
QV: %{3}
Value: %4 %5
Status: Bad |
801 |
TV: %{0}
Value: %1 %2
Status: Bad
QV: %{3}
Value: %4 %5
Status: Good |
802 |
TV: %{0}
Value: %1 %2
Status: Good
QV: %{3}
Value: %4 %5
Status: Bad |
803 |
TV: %{0}
Value: %1 %2
Status: Good
QV: %{3}
Value: %4 %5
Status: Good |
804 |
F: Configuration Lost, Latched Until Acknowledged - Acknowledge
Priority: Failed - Fix Now
Description:
The meter has performed a cold start. The meter configuration has reset to default values and the meter is not configured correctly to measure flow.
Recommended Actions:
1. Unless the Cold Start occurred after upgrading firmware, it is recommended to have the CPU Module replaced. Contact your local area Daniel service representative.
2. If the cold start occurred after a firmware upgrade, you must fully re-configure the meter from a previously saved configuration using the Edit/Compare Configuration screen in Daniel MeterLink.
3. The alert must be acknowledged to clear it from list of alerts per DidCnfgChksumChg.
4. If the issue is unresolved, contact your local area Daniel service representative. |
805 |
F: Configuration Lost, Latched Until Acknowledged - Not Currently Active - Requires Acknowledge
Priority: Failed - Fix Now
Description:
The meter has performed a cold start. The meter configuration has reset to default values and the meter is not configured correctly to measure flow.
Recommended Actions:
1. Unless the Cold Start occurred after upgrading firmware, it is recommended to have the CPU Module replaced. Contact your local area Daniel service representative.
2. If the cold start occurred after a firmware upgrade, you must fully re-configure the meter from a previously saved configuration using the Edit/Compare Configuration screen in Daniel MeterLink.
3. The alert must be acknowledged to clear it from list of alerts per DidCnfgChksumChg.
4. If the issue is unresolved, contact your local area Daniel service representative. |
806 |
Do you want to acknowledge the Alert? |
807 |
Yes;No |
808 |
F: Acquisition Mode - Acknowledge
Priority: Failed - Fix Now
Description:
The meter is not measuring and is trying to acquire measurement data. Possible causes include empty pipe, transducer failures, miswired transducers, invalid geometry configuration, malfunctioning Acquisition Module and fluid type not supported by meter.
Recommended Actions:
1. Verify the process fluid rate has not exceeded the maximum rate indicated on the meter nameplate. Lower the flow rate if necessary.
2. If a new meter or upgraded meter, verify geometry configuration distance between transducers (for four-path meters LA, LB, LC, and LD and for dual-path meters LA and LB) and correct if needed. If these parameters are incorrect, check all meter parameters against the meter Zero Flow Calibration report. This report can be requested from your local area Daniel service representative.
3. Check transducers wiring. Verify all connections are secure and that wires are connected to the correct terminals on the Acquisition Module.
4. Replace Acquisition Module with a spare to see if this corrects the issue. If it does and the meter is still under warranty, you may request a replacement module from your local area Daniel service representative.
5. Collect a Maintenance log with Daniel MeterLink if the issue is unresolved and contact your local area Daniel service representative.
|
809 |
F: Acquisition Mode - Not Currently Active - Requires Acknowledge
Priority: Failed - Fix Now
Description:
The meter is not measuring and is trying to acquire measurement data. Possible causes include empty pipe, transducer failures, miswired transducers, invalid geometry configuration, malfunctioning Acquisition Module and fluid type not supported by meter.
Recommended Actions:
1. Verify the process fluid rate has not exceeded the maximum rate indicated on the meter nameplate. Lower the flow rate if necessary.
2. If a new meter or upgraded meter, verify geometry configuration distance between transducers (for four-path meters LA, LB, LC, and LD and for dual-path meters LA and LB) and correct if needed. If these parameters are incorrect, check all meter parameters against the meter Zero Flow Calibration report. This report can be requested from your local area Daniel service representative.
3. Check transducers wiring. Verify all connections are secure and that wires are connected to the correct terminals on the Acquisition Module.
4. Replace Acquisition Module with a spare to see if this corrects the issue. If it does and the meter is still under warranty, you may request a replacement module from your local area Daniel service representative.
5. Collect a Maintenance log with Daniel MeterLink if the issue is unresolved and contact your local area Daniel service representative.
|
810 |
F: Acquisition Module Error - Acknowledge
Priority: Failed - Fix Now
Description:
An Acquisition Module-related error has been detected. The CPU Module's measurement LED (MEAS) will flash green when proper communications with the Acquisition Module are restored.
Recommended Actions:
1. If the CPU Module's measurement LED (MEAS) is not flashing green, check interconnect cable between Acquisition Module and the CPU Module.
2. If the CPU Module's measurement LED (MEAS) is still not flashing green, check the Acquisition Module error reasons code
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
811 |
F: Acquisition Module Error - Not Currently Active - Requires Acknowledge
Priority: Failed - Fix Now
Description:
An Acquisition Module-related error has been detected. The CPU Module's measurement LED (MEAS) will flash green when proper communications with the Acquisition Module are restored.
Recommended Actions:
1. If the CPU Module's measurement LED (MEAS) is not flashing green, check interconnect cable between Acquisition Module and the CPU Module.
2. If the CPU Module's measurement LED (MEAS) is still not flashing green, check the Acquisition Module error reasons code
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
812 |
F: Too Few Operating Chords - Acknowledge
Priority: Failed - Fix Now
Description:
Number of operating chords is less than the minimum number for a valid measurement. Operating chords are those which are not manually set inactive and not marked as failed.
Recommended Actions:
1. Check the other alerts that indicate why a chord is hard failed. Resolving these should resolve this issue.
2. If this issue is unresolved, collect a Maintenance log and Archive log and contact your local area Daniel service representative. |
813 |
F: Too Few Operating Chords - Not Currently Active - Requires Acknowledge
Priority: Failed - Fix Now
Description:
Number of operating chords is less than the minimum number for a valid measurement. Operating chords are those which are not manually set inactive and not marked as failed.
Recommended Actions:
1. Check the other alerts that indicate why a chord is hard failed. Resolving these should resolve this issue.
2. If this issue is unresolved, collect a Maintenance log and Archive log and contact your local area Daniel service representative. |
814 |
F: Diagnostic Core File Generated, Latched Until Acknowledged - Acknowledge
Priority: Failed - Fix Now
Description:
A diagnostic core file has been generated which may indicate a problem with the meter.
Recommended Actions:
1. The alert must be acknowledged to clear it from list of alerts.
2. Collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative. |
815 |
F: Diagnostic Core File Generated, Latched Until Acknowledged - No Longer Active
Priority: Failed - Fix Now
Description:
A diagnostic core file has been generated which may indicate a problem with the meter.
Recommended Actions:
1. The alert must be acknowledged to clear it from list of alerts.
2. Collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative. |
816 |
F: Electronics Voltage Out Of Range
Priority: Failed - Fix Now
Description:
The CPU Board system voltages or Acquisition Module system voltages are out-of-range. Valid CPU Module voltages are 1.0V, 1.2V, 2.5V, 3.3V or valid Acquisition Module System voltages are 1.2V, 2.5V or 3.3V.
Recommended Actions:
1. Replace the CPU Module if one or more of the CPU voltages is out-of-range.
2. Replace Acquisition Module if one or more of the Acquisition Module voltages is out-of-range.
3. If the issue is unresolved, contact your local area Daniel service representative. |
817 |
F: Acquisition Module is Not Compatible with Firmware
Priority: Failed - Fix Now
Description:
The firmware cannot work with the installed Acquisition Module. Either the Acquisition Module is newer than the firmware and the firmware does not recognize it or the Acquisition Module is installed on a meter running firmware for the opposite product (Gas/Liquid).
Recommended Actions:
1. Upgrade the firmware in the meter to the latest version using Daniel MeterLink. Contact your local area Daniel service representative to obtain the latest firmware.
2. If the latest firmware revision did not resolve the issue, replace the Acquisition Module.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
818 |
F: Watchdog Reset, Latched Until Acknowledged - Acknowledge
Priority: Failed - Fix Now
Description:
Software watchdog initiated a meter warm-start. The watchdog keeps track of the performance of all metrology processes in the meter to ensure a reliable measurement. When a process stops responding, the watchdog forces the meter to restart.
Recommended Actions:
1. Collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative.
2. The alert must be acknowledged to clear it from list of alerts. |
819 |
F: Watchdog Reset, Latched Until Acknowledged - No Longer Active
Priority: Failed - Fix Now
Description:
Software watchdog initiated a meter warm-start. The watchdog keeps track of the performance of all metrology processes in the meter to ensure a reliable measurement. When a process stops responding, the watchdog forces the meter to restart.
Recommended Actions:
1. Collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative.
2. The alert must be acknowledged to clear it from list of alerts. |
820 |
M: Chord A Hard Failed
Priority: Maintenence - Fix Soon
Description:
The meter is unable to obtain measurement data from this pair of transducers.
Recommended Actions:
1. If no other transducers are failed or are reporting status alerts, the issue is most likely isolated to this pair of transducers or its cabling. Check the transducer wiring for this pair of transducers to make sure connections are secure and wired correctly.
2. Verify that the meter run is not partially full where this top transducer pair is not submerged in the process fluid.
3. Verify the Gain A1 and Gain A2 of this transducer pair is not above 90dB. The gain values can be read on the Path Performance tab under Service Tools . If so, remove the transducers, clean, and reapply the coupling fluid to the front face of the transducers. If this does not correct the issue, at least one of the transducers in the pair should be replaced.
4. If transducer cabling allows, swap cabling of failed transducer pair with a pair with equal path lengths. If the alert remains active for this chord, then the transducers are working properly. If this alert clears but the chord that was swapped now fails, the issue is with the transducer.
5. If this issue is unresolved, collect a Maintenance Log, Configuration file and Waveform stream file with Daniel MeterLink and contact your local area Daniel service representative. |
821 |
M: Chord B Hard Failed
Priority: Maintenence - Fix Soon
Description:
The meter is unable to obtain measurement data from this pair of transducers.
Recommended Actions:
1. If no other transducers are failed or are reporting status alerts, the issue is most likely isolated to this pair of transducers or its cabling. Check the transducer wiring for this pair of transducers to make sure connections are secure and wired correctly.
2. Verify the Gain A1 and Gain A2 of this transducer pair is not above 90dB. The gain values can be read on the Path Performance tab under Service Tools . If so, remove the transducers, clean, and reapply the coupling fluid to the front face of the transducers. If this does not correct the issue, at least one of the transducers in the pair should be replaced.
3. If transducer cabling allows, swap cabling of failed transducer pair with a pair with equal path lengths. If the alert remains active for this chord, then the transducers are working properly. If this alert clears but the chord that was swapped now fails, the issue is with the transducer.
4. If this issue is unresolved, collect a Maintenance Log, Configuration file and Waveform stream file with Daniel MeterLink and contact your local area Daniel service representative. |
822 |
M: Chord C Hard Failed
Priority: Maintenence - Fix Soon
Description:
The meter is unable to obtain measurement data from this pair of transducers.
Recommended Actions:
1. If no other transducers are failed or are reporting status alerts, the issue is most likely isolated to this pair of transducers or its cabling. Check the transducer wiring for this pair of transducers to make sure connections are secure and wired correctly.
2. Verify the Gain A1 and Gain A2 of this transducer pair is not above 90dB. The gain values can be read on the Path Performance tab under Service Tools . If so, remove the transducers, clean, and reapply the coupling fluid to the front face of the transducers. If this does not correct the issue, at least one of the transducers in the pair should be replaced.
3. If transducer cabling allows, swap cabling of failed transducer pair with a pair with equal path lengths. If the alert remains active for this chord, then the transducers are working properly. If this alert clears but the chord that was swapped now fails, the issue is with the transducer.
4. If this issue is unresolved, collect a Maintenance Log, Configuration file and Waveform stream file with Daniel MeterLink and contact your local area Daniel service representative. |
823 |
M: Chord D Hard Failed
Priority: Maintenence - Fix Soon
Description:
The meter is unable to obtain measurement data from this pair of transducers.
Recommended Actions:
1. If no other transducers are failed or are reporting status alerts, the issue is most likely isolated to this pair of transducers or its cabling. Check the transducer wiring for this pair of transducers to make sure connections are secure and wired correctly.
2. Verify the Gain A1 and Gain A2 of this transducer pair is not above 90dB. The gain values can be read on the Path Performance tab under Service Tools . If so, remove the transducers, clean, and reapply the coupling fluid to the front face of the transducers. If this does not correct the issue, at least one of the transducers in the pair should be replaced.
3. If transducer cabling allows, swap cabling of failed transducer pair with a pair with equal path lengths. If the alert remains active for this chord, then the transducers are working properly. If this alert clears but the chord that was swapped now fails, the issue is with the transducer.
4. If this issue is unresolved, collect a Maintenance Log, Configuration file and Waveform stream file with Daniel MeterLink and contact your local area Daniel service representative. |
824 |
M: Flow Pressure Invalid - Acknowledge
Priority: Maintenence - Fix Soon
Description:
Pressure is invalid if the flow pressure is outside the limits defined by the low and high pressure alert limits.
Recommended Actions:
First Time Startup Issues:
1. Verify that there is voltage to the pressure sensor, either from the terminal on the meter's power supply board or from an external power supply.
2. If using an analog pressure device, verify that the pressure sensor is properly wired to connector TB2-B pins 1 & 2 (ANALOG IN PT- & PT+) .
3. Use the Pressure tab under Configure->Manual Setup to verify the input is properly configured for your pressure input.
4. If using a flow computer to write pressure to the meter, verify that it is properly writing to fixed flow pressure in the proper units. The current value will be displayed as Fixed pressure in the Pressure tab under Configure->Manual Setup.
5. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
Run Time Issues:
1. Adjust pressure of process fluid to within alarm limits.
2. If using an analog pressure device and input reading is 0, check if IsAI2Avail is equal to 1 in the Meter Information dialog in Daniel MeterLink. If it is not 1, either the I/O Board has been removed or is damaged. Reinstall or replace the board if this value is 0.
3. If using an analog pressure device, verify that the pressure sensor is working properly.
4. If using an analog pressure device, recheck wiring and switch settings as noted above under First Time Setup Issues.
5. If flow computer is writing values to the fixed flow pressure, verify that the flow computer is still writing valid values without Modbus write errors.
6. Reverify the pressure input settings are correct on the Pressure tab under Configure->Manual Setup.
7. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
|
825 |
M: Flow Pressure Invalid - Not Currently Active - Requires Acknowledge
Priority: Maintenence - Fix Soon
Description:
Pressure is invalid if the flow pressure is outside the limits defined by the low and high pressure alert limits.
Recommended Actions:
First Time Startup Issues:
1. Verify that there is voltage to the pressure sensor, either from the terminal on the meter's power supply board or from an external power supply.
2. If using an analog pressure device, verify that the pressure sensor is properly wired to connector TB2-B pins 1 & 2 (ANALOG IN PT- & PT+) .
3. Use the Pressure tab under Configure->Manual Setup to verify the input is properly configured for your pressure input.
4. If using a flow computer to write pressure to the meter, verify that it is properly writing to fixed flow pressure in the proper units. The current value will be displayed as Fixed pressure in the Pressure tab under Configure->Manual Setup.
5. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
Run Time Issues:
1. Adjust pressure of process fluid to within alarm limits.
2. If using an analog pressure device and input reading is 0, check if IsAI2Avail is equal to 1 in the Meter Information dialog in Daniel MeterLink. If it is not 1, either the I/O Board has been removed or is damaged. Reinstall or replace the board if this value is 0.
3. If using an analog pressure device, verify that the pressure sensor is working properly.
4. If using an analog pressure device, recheck wiring and switch settings as noted above under First Time Setup Issues.
5. If flow computer is writing values to the fixed flow pressure, verify that the flow computer is still writing valid values without Modbus write errors.
6. Reverify the pressure input settings are correct on the Pressure tab under Configure->Manual Setup.
7. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
|
826 |
M: Flow Temperature Invalid - Acknowledge
Priority: Maintenence - Fix Soon
Description:
Temperature is invalid if the flow temperature is outside the limits defined by the low and high temperature alert limits.
Recommended Actions:
First Time Startup Issues:
1. Verify that there is voltage to the temperature sensor, either from the terminal on the meter's power supply board or from an external power supply.
2. If using an analog temperature device, verify that the temperature sensor is properly wired to connector TB2-B pins 3 & 4 (ANALOG IN TT- & TT+) .
3. Use the Temperature tab under Configure->Manual Setup to verify the input is properly configured for your temperature input.
4. If using a flow computer to write temperature to the meter, verify that it is properly writing to fixed flow temperature in the proper units. The current value will be displayed as Fixed temperature in the Temperature tab under Configure->Manual Setup.
5. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
Run Time Issues:
1. Adjust temperature of process fluid to within alarm limits.
2. If using an analog temperature device and input reading is 0, check if IsAI1Avail is equal to 1 in the Meter Information dialog in Daniel MeterLink. If it is not 1, either the I/O Board has been removed or is damaged. Reinstall or replace I/O board if this value is 0.
3. If using an analog temperature device, verify that the temperature sensor is working properly.
4. If using an analog temperature device, recheck wiring and switch settings as noted above under First Time Setup Issues.
5. If flow computer is writing values to the fixed flow temperature, verify that the flow computer is still writing valid values without Modbus write errors.
6. Reverify the temperature input settings are correct on the Temperature tab under Configure->Manual Setup.
7. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
|
827 |
M: Flow Temperature Invalid - Not Currently Active - Requires Acknowledge
Priority: Maintenence - Fix Soon
Description:
Temperature is invalid if the flow temperature is outside the limits defined by the low and high temperature alert limits.
Recommended Actions:
First Time Startup Issues:
1. Verify that there is voltage to the temperature sensor, either from the terminal on the meter's power supply board or from an external power supply.
2. If using an analog temperature device, verify that the temperature sensor is properly wired to connector TB2-B pins 3 & 4 (ANALOG IN TT- & TT+) .
3. Use the Temperature tab under Configure->Manual Setup to verify the input is properly configured for your temperature input.
4. If using a flow computer to write temperature to the meter, verify that it is properly writing to fixed flow temperature in the proper units. The current value will be displayed as Fixed temperature in the Temperature tab under Configure->Manual Setup.
5. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
Run Time Issues:
1. Adjust temperature of process fluid to within alarm limits.
2. If using an analog temperature device and input reading is 0, check if IsAI1Avail is equal to 1 in the Meter Information dialog in Daniel MeterLink. If it is not 1, either the I/O Board has been removed or is damaged. Reinstall or replace I/O board if this value is 0.
3. If using an analog temperature device, verify that the temperature sensor is working properly.
4. If using an analog temperature device, recheck wiring and switch settings as noted above under First Time Setup Issues.
5. If flow computer is writing values to the fixed flow temperature, verify that the flow computer is still writing valid values without Modbus write errors.
6. Reverify the temperature input settings are correct on the Temperature tab under Configure->Manual Setup.
7. If the issue is unresolved, collect a Maintenance Log using Daniel MeterLink and contact your local area Daniel service representative.
|
828 |
M: Clock Invalid
Priority: Maintenence - Fix Soon
Description:
The meter's hardware clock has been set to a date prior to Jan. 1, 2003.
Recommended Actions:
1. The real time clock has a power backup of about 2 weeks. If the meter remains unpowered for more than this time, the real time clock will reset back to Jan. 1, 2000. If this is the issue, use either the Field Setup Wizard or the Monitor screen in Daniel MeterLink to set the correct date and time.
2. If the meter has not been unpowered for more than a week, then CPU Module should be replaced as the real time clock or its backup power source may be damaged.
3. Contact your local area Daniel service representative for assistance in getting a replacement CPU board. |
829 |
M: Reset Required
Priority: Maintenence - Fix Soon
Description:
The meter configuration has changed and requires a restart for the change to take effect.
Recommended Actions:
1. If you are unaware of changes made to the meter's configuration, collect the Audit log using the Archive Logs screen in Daniel MeterLink to review configuration changes. If the changes are valid, momentarily remove power from the meter to allow it to restart which will clear this alert.
2. If the Audit log shows no changes, contact your local area Daniel service representative for assistance. |
830 |
A: Reverse Flow Detected - Acknowledge
Priority: Advisory
Description:
The meter has accumulated a reverse flow volume greater than a user configurable limit. This alert is configured as part of the Flow Analysis Alerts setup under the Alert Setup menu.
Recommended Actions:
1. Check valves for leaks.
2. If metering run is known to have some volume of reverse flow when flow is stopped, reconfigure the reverse flow volume limit to allow a greater volume.
3. If meter regularly flows in the reverse direction, this alert should be disabled. It is only intended to be used for unidirectional applications.
4. If the issue is unresolved, collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative. |
831 |
A: Reverse Flow Detected - Not Currently Active - Requires Acknowledge
Priority: Advisory
Description:
The meter has accumulated a reverse flow volume greater than a user configurable limit. This alert is configured as part of the Flow Analysis Alerts setup under the Alert Setup menu.
Recommended Actions:
1. Check valves for leaks.
2. If metering run is known to have some volume of reverse flow when flow is stopped, reconfigure the reverse flow volume limit to allow a greater volume.
3. If meter regularly flows in the reverse direction, this alert should be disabled. It is only intended to be used for unidirectional applications.
4. If the issue is unresolved, collect an Archive log using Daniel MeterLink and contact your local area Daniel service representative. |
832 |
A: Meter Velocity Above Maximum Limit - Acknowledge
Priority: Advisory
Description:
Velocity is above the meter maximum velocity limit.
Recommended Actions:
1. Lower the velocity of the meter as this alert indicates you are running above a safe limit that could damage the meter run or could indicate you are running above your upper calibration limit where meter uncertainty could increase.
2. Use the Edit/Compare configuration screen in Daniel MeterLink to change the value of MeterMaxVel if desired. It is recommended to set this either to the maximum calibrated velocity of the meter or to the maximum safe operating velocity of the meter run. The maximum safe operating velocity typically is to prevent erosion of the pipe internal diameter and prevent damage to protrusions such as thermal wells. |
833 |
A: Meter Velocity Above Maximum Limit - Not Currently Active - Requires Acknowledge
Priority: Advisory
Description:
Velocity is above the meter maximum velocity limit.
Recommended Actions:
1. Lower the velocity of the meter as this alert indicates you are running above a safe limit that could damage the meter run or could indicate you are running above your upper calibration limit where meter uncertainty could increase.
2. Use the Edit/Compare configuration screen in Daniel MeterLink to change the value of MeterMaxVel if desired. It is recommended to set this either to the maximum calibrated velocity of the meter or to the maximum safe operating velocity of the meter run. The maximum safe operating velocity typically is to prevent erosion of the pipe internal diameter and prevent damage to protrusions such as thermal wells. |
834 |
A: Flow-Condition Volumetric Flow Rate Validity
Priority: Advisory
Description:
The meter either has not collected enough information from the chords to make an accurate measurement or the pressure and/or temperature are invalid and meter is performing pressure or temperature expansion corrections on the meter internal diameter. This is an alert condition that shows the validity of the flow-condition volumetric flow rate. The flow-condition volumetric flow rate becomes invalid if the uncorrected flow-condition volumetric flow rate validity, temperature expansion correction validity, pressure expansion correction validity, or Flow-profile-effect correction validity is invalid.
Recommended Actions:
1. If a Pressure expansion correction validity alert is present, correcting it may clear this alert.
2. If a Temperature expansion correction validity alert is present, correcting it may clear this alert.
3. If an Uncorrected flow-condition volumetric flow rate validity alert is present, correcting it may clear this alert.
4. If a Flow-profile-effect correction validity alert is present, correcting it may clear this alert.
5. If the issue is unresolved, collect a Maintenance Log with Daniel MeterLink and contact your local area Daniel service representative. |
835 |
A: Analog Output 1 Validity
Priority: Advisory
Description:
Analog Output 1 (AO1) is invalid. The analog output is considered invalid if the analog output is in test mode or the content the analog output is trying to drive is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output on Analog Output 1, resolving that issue should clear this alert.
2. If the content selected for Analog Output 1 is not in alarm, then verify that the output is not fixed or set in test mode.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
836 |
A: Analog Output 2 Validity
Priority: Advisory
Description:
Analog Output 2 (AO2) is invalid. The analog output is considered invalid if the analog output is in test mode or the content the analog output is trying to drive is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output on Analog Output 2, resolving that issue should clear this alert.
2. If the content selected for Analog Output 2 is not in alarm, then verify that the output is not fixed or set in test mode.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
837 |
A: Frequency Output 1 Data is Invalid
Priority: Advisory
Description:
The parameter which the Frequency Output 1 is configured to represent is invalid or the output is currently in test mode.
Recommended Actions:
1. You can determine whether the output is in test mode by using Meter Outputs in Daniel MeterLink.
2. If the parameter for which Frequency Output 1 is configured is invalid, other alerts will be present that will help you resolve the issue.
3. If the issue is unresolved, collect a Maintenance log and Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
838 |
A: Frequency Output 2 Data is Invalid
Priority: Advisory
Description:
The parameter which the Frequency Output 2 is configured to represent is invalid or the output is currently in test mode.
Recommended Actions:
1. You can determine whether the output is in test mode by using Meter Outputs in Daniel MeterLink.
2. If the parameter for which Frequency Output 2 is configured is invalid, other alerts will be present that will help you resolve the issue.
3. If the issue is unresolved, collect a Maintenance log and Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
839 |
A: HART Fourth Variable Validity
Priority: Advisory
Description:
The HART Fourth Variable value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
840 |
A: HART Command 33 Slot 0 Validity
Priority: Advisory
Description:
The HART Slot 0 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
841 |
A: HART Command 33 Slot 1 Validity
Priority: Advisory
Description:
The HART Slot 1 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
842 |
A: HART Command 33 Slot 2 Validity
Priority: Advisory
Description:
The HART Slot 2 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
843 |
A: HART Command 33 Slot 3 Validity
Priority: Advisory
Description:
The HART Slot 3 value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
844 |
A: HART Third Variable Validity
Priority: Advisory
Description:
The HART Third Variable value as defined by the HART device variable selection is invalid.
Recommended Actions:
1. If an alert exists for the content selected to be output , resolving that issue should clear this alert.
2. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
845 |
A: Analog Output 1 (HART PV) is Saturated
Priority: Advisory
Description:
Analog Output 1 is saturated (i.e. the loop current has reached its upper or lower endpoint and cannot increase or decrease any further).
Recommended Actions:
1. The analog output may need to be rescaled to prevent it from saturating. Use the Field Setup Wizard in Daniel MeterLink to configure Analog Output 1. |
846 |
A: Analog Output 2 (HART SV) is Saturated
Priority: Advisory
Description:
Analog Output 2 is saturated (i.e. the loop current has reached its upper or lower endpoint and cannot increase or decrease any further).
Recommended Actions:
1. The analog output may need to be rescaled to prevent it from saturating. Use the Setup Outputs wizard under Guided Setup to configure Analog Output 2. |
847 |
A: Analog Output 1 (HART PV) is Fixed
Priority: Advisory
Description:
Analog Output 1 current is in test mode and fixed. The current can be fixed via the HART command 66.
Recommended Actions:
1. Once the Analog Output 1 is removed from test mode, this alert will clear. |
848 |
A: Analog Output 2 (HART SV) is Fixed
Priority: Advisory
Description:
Analog Output 2 current is in test mode and fixed. The current can be fixed via the HART command 66.
Recommended Actions:
1. Once the Analog Output 2 is removed from test mode, this alert will clear. |
849 |
A: Average Sound Velocity Out-Of-Limits
Priority: Advisory
Description:
The meter's measured average sound velocity is outside the defined limits.
Recommended Actions:
1. Verify that all chords are measuring the same Speed of Sound within about 0.15%. Look for alerts that indicate transducer problems and resolve any of these issues. This could include failing transducers, debris buildup on transducers, or incorrectly entered path lengths in the configuration.
2. If the chords agree well, it is recommended that the SSMin or SSMax be adjusted so the meter's average speed of sound falls within these limits.
3. If the issue is unresolved, collect a Maintenance log using Daniel MeterLink and contact your local area Daniel service representative. |
850 |
A: Configuration Changed, Latched Until Acknowledged - Acknowledge
Priority: Advisory
Description:
The configuration checksum value has changed. This indicates that one or more parameters have been modified in the meter's configuration.
Recommended Actions:
1. Collect an Audit log using Daniel MeterLink in order to see what configuration parameters changed and when they changed.
2. The alert must be acknowledged to clear it from list of alerts. |
851 |
A: Configuration Changed, Latched Until Acknowledged - No Longer Active
Priority: Advisory
Description:
The configuration checksum value has changed. This indicates that one or more parameters have been modified in the meter's configuration.
Recommended Actions:
1. Collect an Audit log using Daniel MeterLink in order to see what configuration parameters changed and when they changed.
2. The alert must be acknowledged to clear it from list of alerts. |
852 |
A: Power Failure, Latched Until Acknowledged - Acknowledge
Priority: Advisory
Description:
The meter has had power removed for a period of time or the meter restarted itself such as after a firmware upgrade. The Audit log in the meter will indicate the power fail time.
Recommended Actions:
1. If this was a known power fail or restart of the meter just acknowledge this alert.
2. If this was an unexpected restart of the meter, verify the integrity of the power to the meter and make sure that the voltage level is in the range of 11-36 VDC at the meter.
3. The alert must be acknowledged to clear it from list of alerts.
4. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
853 |
A: Power Failure, Latched Until Acknowledged - No Longer Active
Priority: Advisory
Description:
The meter has had power removed for a period of time or the meter restarted itself such as after a firmware upgrade. The Audit log in the meter will indicate the power fail time.
Recommended Actions:
1. If this was a known power fail or restart of the meter just acknowledge this alert.
2. If this was an unexpected restart of the meter, verify the integrity of the power to the meter and make sure that the voltage level is in the range of 11-36 VDC at the meter.
3. The alert must be acknowledged to clear it from list of alerts.
4. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
854 |
A: Flow-Condition Pressure Out-Of-Limits
Priority: Advisory
Description:
The flow-condition pressure is outside the limits.
Recommended Actions:
1. If connected to a pressure transducer, verify that the transducer is functioning properly. Verify that the wiring is correctly connected to TB2-B pins 1 & 2 (ANALOG IN PT- and PT+). Verify that the current is between 4 mA and 20 mA.
2. Use the Pressure tab under Configure->Manual Setup to verify the input is properly configured for your pressure input.
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
855 |
A: Flow-Condition Temperature Out-Of-Limits
Priority: Advisory
Description:
The flow-condition temperature is outside the limits.
Recommended Actions:
1. If connected to a temperature transducer, verify that the transducer is functioning properly. Verify that the wiring is correctly connected to TB2-B pins 3 & 4 (ANALOG IN TT- and TT+). Verify that the current is between 4 mA and 20 mA.
2. Use the Temperature tab under Configure->Manual Setup to verify the input is properly configured for your temperature input.
3. If the issue is unresolved, collect a complete Archive log from the meter using Daniel MeterLink and contact your local area Daniel service representative. |
856 |
A: Alarm Archive Log is Full
Priority: Advisory
Description:
The alarm archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect alarm archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadAlarmLog to overwrite old records. |
857 |
A: Analog Output 1 Test Enable
Priority: Advisory
Description:
Enables the Analog Output Test mode for Analog Output 1. When in the Analog Output Test mode, Analog Output 1 is fixed at the percentage of full scale specified via the Analog Output 1 test mode output percent configuration point (regardless of the actual data content value). If Analog Output 1 remains in Analog Output Test mode for longer than the non-normal mode timeout, Analog Output 1 automatically exits Analog Output Test mode and returns to normal operation. |
858 |
A: Analog Output 2 Test Enable
Priority: Advisory
Description:
Enables the Analog Output Test mode for Analog Output 2. When in the Analog Output Test mode, Analog Output 2 is fixed at the percentage of full scale specified via the Analog Output 2 test mode output percent configuration point (regardless of the actual data content value). If Analog Output 2 remains in Analog Output Test mode for longer than the non-normal mode timeout, Analog Output 2 automatically exits Analog Output Test mode and returns to normal operation. |
859 |
A: Audit Archive Log is Full
Priority: Advisory
Description:
The audit archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect audit archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadAuditLog to overwrite old records. |
860 |
A: Daily Archive Log is Full
Priority: Advisory
Description:
The daily archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect daily archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadDailyLog to overwrite old records. |
861 |
A: Electronics Temperature is Out Of Nominal Range
Priority: Advisory
Description:
The temperature of the electronics is out of nominal operating range (below -40 °C or above 100 °C ). Operating outside the nominal operating range could lead to a system failure.
Recommended Actions:
1. Attempt to warm or cool the meter electronics housing.
2. If the electronics is mounted to the meter and the process fluid in the meter is over 65 °C, you must remote mount the electronics off from the meter body.
3. Collect a Maintenance log using Daniel MeterLink while the meter is experiencing the issue, collect an Archive log (Daily/Hourly/Alarm/Audit/System) using Daniel MeterLink from the meter and contact your local area Daniel service representative. |
862 |
A: Frequency Output 1 Pair Test Enable
Priority: Advisory
Description:
Frequency Output 1 is in test mode which means the pulses output do not reflect the process flow through the meter. Test mode allows the connection from this output to a flow computer to be verified.
Recommended Actions:
1. Use the Meter Outputs screen in Daniel MeterLink to disable the test mode for Frequency Output 1 to clear this alert and return the meter back to its normal mode of operation.
2. Unless Daniel MeterLink or another application through Modbus is reenabling the test mode, the output will revert back to the normal mode of operation in a user configured timeout period which can be up to 30 minutes. |
863 |
A: Frequency Output 2 Pair Test Enable
Priority: Advisory
Description:
Frequency Output 2 is in test mode which means the pulses output do not reflect the process flow through the meter. Test mode allows the connection from this output to a flow computer to be verified.
Recommended Actions:
1. Use the Meter Outputs screen in Daniel MeterLink to disable the test mode for Frequency Output 2 to clear this alert and return the meter back to its normal mode of operation.
2. Unless Daniel MeterLink or another application through Modbus is reenabling the test mode, the output will revert back to the normal mode of operation in a user configured timeout period which can be up to 30 minutes. |
864 |
A: Hourly Log Full Indicator
Priority: Advisory
Description:
The hourly archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect hourly archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadHourlyLog to overwrite old records. |
865 |
A: System Archive Log is Full
Priority: Advisory
Description:
The system archive log is full and the log is not configured to be overwritten automatically.
Recommended Actions:
1. Collect system archive log records using Daniel MeterLink and allow Daniel MeterLink to mark them as read which will allow them to be overwritten.
2. If it is desirable to let the meter automatically overwrite the oldest log record once the log is full, use the Edit/Compare configuration screen in Daniel MeterLink to change DoOverwriteUnreadSystemLog to overwrite old records. |