internetbion.blogg.se - Fmc micromate

#Fmc micromate manual#

Disclaimer FMC Technologies Measurement Solutions, Inc. Each metering system is unique and each program parameter must be reviewed and programmed for that specific metering system application.

#Fmc micromate manual#

If required, return the sensor to an Authorized Instantel Representative for further testing.1 Electronic Preset Delivery System Smith Meter Installation Manual Bulletin MN06150 Issue/Rev 0.6 (8/15)Ģ Caution The default or operating values used in this manual and in the program of the Smith Meter are for factory testing only and should not be construed as default or operating values for your metering system.

Check cables and connectors for wear, bent pins, or foreign debris.

Refer to the section in this manual, Geophone Direct Hard Surface Mount Installation Instruction.

Ensure that the orientation of the Geophone is correct, as per the given application, such as a ceiling installation.

Was the sensor moved during the Sensor Check? This will result in a failed reading.

When a Sensor Check error occurs, check the following for possible causes: The sensor check is NOT a calibration check and cannot replace the annual calibration process as it does not compare the measured result against an external traceable reference. If a geophone sensor was not level or was upside down, the monitor would indicate a failed sensor check on one or more channels. The Sensor Check feature on Instantel vibration monitors is to help ensure that the sensors have been connected and installed correctly. Please refer to Chapter 14 of the Micromate Operator Manual, page 121, for more information.

NOTE: The auxiliary trigger is automatically disabled in this mode.

The waveform event is saved as a separate file, while the Histogram Event file remains continuous, limited only by the amount of available memory. (This happens when an event exceeds the waveform trigger level, Ex: Pile driving) Records data on peak events and Histogram events.

This will create a waveform record while Histogram recording.

It also calculates the largest peak vector sum over the entire event, displaying the peak of each interval in a bar chart. For each channel, the unit calculates the maximum peak and its frequency. (This reduces the recorded data and increases storage capacity.) For each interval, the unit calculates the maximum peaks, the largest peak frequency, and the peak vector sum. The unit gathers continuous data based on the sample rate but only registers relevant peaks for the interval. (Ex: Pile driving) The unit stores summary information in intervals. Used also to record background noise levels near a site. Used when automatic triggers are unreliable due to high wind or nearby vehicle activity.(Ex: Blasting) The unit records an event, displays the results, and continues to monitor for events exceeding the trigger level to record. To record multiple events automatically with no lag time between events.Please refer to Chapter 3.7.2 of the THOR Operator Manual, page 66, for more information. In the confirmation dialog box, click OK.WARNING: Deleted events cannot be restored. Click a project’s arrow that contains the unit’s event data to delete.Please refer to Chapter 5.5.2 of the THOR Operator Manual, page 100, for more information. WARNING: Deleting an event, will delete all associated reports with it. Tip: To select multiple events, hold down CTRL on the keyboard and select the events. Select one or more events then right-click and select Delete Event(s).Please refer to Chapter 5.5.1 of the THOR Operator Manual, page 99, for more information.

(Events with the Location Type Local are already copied onto the computer.)

Select one or more events with the Location Type Unit, then right-click and select Create Local Copy of Event(s) and Log(s).

Click a project’s arrow that contains the unit’s event data to copy.

Local: A copy of the event file has been downloaded to the local computer and can be Unit: The event file is stored on the unit and is being viewed temporarily in THOR. The Location attribute indicates where the event file resides. Use this function to store a copy of the event file(s) onto your local computer. Please refer to Chapter 5.4 of the THOR Operator Manual, page 98, for more information.