integrating the kinemetrics obsidian seismic recorded with...

5 Gould Road, PO Box 2155 New London, NH 03257 USA

Voice: (603) 526-9800 [email protected] www.canarysystems.com

Integrating the Kinemetrics Obsidian Seismic Recorder with MultiLogger Suite

1


Sensor Application Note #26

Overview

The Obsidian accelerograph manufactured by Kinemetrics is a 24-bit seismic recorder offering support for up to eight external sensors and one internal sensor. With common network timing provided by external GPS, it is well-matched with Kinemetrics' EpiSensor accelerometers and provides for a built-in web interface for configuring of the sensor inputs and communication parameters.

This Sensor Application Note provides the instructions for integrating the Obsidian accelerograph utilizing the

EpiSensor with Canary Systems MultiLogger Suite. The integration includes the configuration of the following:

Accelerometer and sensor hardware setup

Communication configuration

Automated data import configuration

Database configuration

This integration supports the monitoring and recording of strong motion events. It does not include triggering of alarms or sending alarms status to a datalogger or other hardware device.

Figure 1 shows an example deployment layout:

(Figure 1)

Kinemetrics and Rockhound are Registered Trademarks of Kinemetrics, Inc. Microsoft and Windows are Registered Trademarks of the Microsoft Corporation. MultiLogger, MLWeb and Canary Systems are Registered Trademarks of Canary Systems, Inc.


2

Figure 2 shows an Obsidian Recorder and EpiSensor used for this application:

(Figure 2)

System Requirements

The integration requires certain hardware equipment and software applications in order to support the necessary configuration tasks and communication of data from the field to the database. The following hardware and software items are required for the integration:

Obsidian Rock Series accelerograph

EpiSensor FBA ES-T tri-axial accelerometer

Signal cable for the EpiSensors to the Obsidian

120VAC Power

DC Charge Controller

12VDC battery

TCP/IP connection at the Obsidian

A server or PC with Microsoft Windows 7 or greater and MultiLogger Suite version 2016 SP4 or greater

A web browser (Firefox version 50.0 was used for this integration)

PuttyTel or other Windows based terminal application (for low-level programming of the Obsidian)

Kinemetrics #853607 Serial Cable and serial communication connection to server or PC

Kinemetrics #853608 Ethernet Cable and ethernet connection to server or PC

Kinemetrics #504083 12VDC Power Cable


3

Dataflow

The EpiSensors continuously provide a constant +/- 20mV signal to the Obsidian accelerograph that is relative to acceleration (strong motion). Any time the level of the signal indicates a movement beyond the user-set threshold, the system considers it an "event" and creates a data file of the sensor signal levels of all the sensors during the event. Because the Obsidian is receiving a constant signal from the accelerometers, the event file includes three seconds of pre-event and ten second post-event signals to assure the event is captured (pre and post-event duration is user configurable).

Once the event file is created in the Obsidian, it is stored in memory until MultiLogger requests the file from the Obsidian. When MultiLogger requests the file, it is then downloaded and queued for import into the MultiLogger database. Once the event file is imported into the database, the event data is stored in the database for analysis using the database analysis tools.

Figure 3 shows event files being stored in the Obsidian prior to import:

(Figure 3)

Obsidian Configuration

The Obsidian device must be configured in order for the signal to be detected from the sensors, processed and stored into the Obsidian as an event file prior to downloading to MultiLogger. The configuration requires two levels of configuration. Both a low-level IP Networking configuration via a Linux terminal connection, and then the Obsidian device software configuration must be done in order to detect and record the events via a browser interface program.

The low-level IP Networking configuration involves establishing the device IP address needed to identify the

Obsidian on the network and also to communicate with the Obsidian via the Rockhound software in order to perform the software level configuration.

Use the following steps to accomplish both configurations:


4

Establish the IP address for the Obsidian device

Connect a PC to the Obsidian device using Linux terminal connection console application such as PuTTYtel and a Kinemetrics #853607 serial cable. The Kinemetrics Doc #300821a Quick Start Guide provides step-by-step instructions on the connection. Login to the Obsidian device.

(Figure 4)

Configure the IP Networking Parameters and Test the Network Connection

Execute the netconfig command to establish the IP network parameters to be used for the device. The assigned address must be a static address discoverable by the MultiLogger server. See pages 243-245 in the Kinemetrics Doc #300816a Rock User Guide for the netconfig command syntax.

Once the IP network parameters are configured, connect the Obsidian to the IP network shared by the server and confirm the server is able to ping the IP address of the device.

(Figure 5)


5

Configure the Obsidian Recording Parameters

Open a browser window and direct it the IP address of the Obsidian device. This will open the Rockhound software. See page 124 of the Rock User Guide for help logging into the system.

(Figure 6)

Under the Tools menu, select Advanced Toggles and then select Show Advanced Parameters.

(Figure 7)

Under Tools menu, select Module Add. Add the following modules to the configuration and then save:

Altus Telemetry via TCP/IP

Altus EVT Format Data Archiver


6

Figure 8 shows a summary screen of the Channel configuration:

(Figure 8)

Under the Layout menu, select Hardware and fill in the following parameters:

Unit ID

Network ID

Site ID

'dig1' name: ex "Crest" or "Abutment"

Fill in all "dig_Vch_ID" parameters: ex CZ would indicate Crest axis Z

Enter the value of 20 for all dig_Ch_Sensitivity (Physical) parameters to indicate a 1-20 VDC range of the sensor.

Enter the value of 32 for all dig_Ch_Sensor Type (Physical) to indicate the EpiSensor is being used.

Under the Layout menu, select Configuration and fill in the following parameters:

Under Altus EVT Format Data Archiver:

Data Directory = \data

Output Directory - \data\events\

Under Altus Telemetry via TCP/IP:

TCP Port = 9801

Under Command Console:

TCP Port number 9900

For all of the dig_, Ch_, (z_z_CZ_z) Threshold Triggers:

Enter 5 or 10 for Trigger and Detrigger levels. 5 = 0.05 g and 10 = 0.1 trigger levels

Save all changes and let the system reboot. Go back into Rockhound interface and confirm that all settings have been saved.


7

Figure 9 shows an example of the configuration:

(Figure 9)

Confirm the correct configuration by performing a shake test of the sensor. To accomplish this, carefully pick up the sensor and move the sensor to a different axis. While the sensor is sensitive to sudden drops or impacts, it is acceptable to move or tilt the sensor in the three axis directions. Once complete, confirm the shake test event is detected and recorded by selecting Recorded Files from the files menu. A shake test should present the strong motion movement in all three axis. See Figure 10 for an example:


8

(Figure 10)

Be sure to confirm the three axis labels in the upper right of each chart series correlate to the correct axis directional movement performed during the shake test. Ex: CX, CY and CZ.


9

MultiLogger Configuration

TCP/IP connectivity is supported for communication to the Obsidian recorder. The steps below are used to connect the recorder to the MultiLogger network, confirm communication, configure the event file collection interval, and automate the database import function:

Open MultiLogger

Select Add a Gateway or select an existing Gateway

Select Add a TCP/IP Socket and give it a name as necessary

Right click on the TCP/IP socket, select Add a Seismic Recorder, then select Kinemetrics Obsidian from the Add Device pop-up.

Figure 11 presents an example of the MultiLogger tree and the selection of the Kinemetrics Obsidian device:

(Figure 11)


10

Once the Obsidian recorder has been added to the tree, select the device and then select the Settings tab to enter the IP address and TCP port number of the device. Then select the Active box, and then finally, select Save to save the configuration.

(Figure 12)

Once the device is configured, confirm the Obsidian recorder is communicating with the network by selecting the Logger icon at the top of the MultiLogger Network Manager screen to enter the Obsidian device screen.


11

(Figure 13)

Once the Obsidian Datalogger screen is open, select the Monitor tab and confirm the dynamic fields such as the connection icon and other real time fields containing new values. If current values are not present then the Obsidian recorder is not communicating with MultiLogger and troubleshooting is required.

(Figure 14)

To configure the system to automatically collect the event files from the Obsidian recorder and import them into the MultiLogger database, select the Obsidian device from the MultiLogger Network Manager and then select the Data Collection tab. Enter the desired collection interval to indicate how often the system will check for new event files and then select Enable Schedule and Automatic Database Import. Lastly, select Save to save the settings.


12

(Figure 15)


13

Database Considerations

The Obsidian records strong motion data in VDC units with a full-scale range of +20VDC to -20VDC where +20VDC = 1.0 g and -20VDC = -1.0 g. MultiLogger stores the raw readings into dynamic elements within the database in VDC.

The SI derived unit for acceleration is the meter/square second. 1 meter/square second is equal to 100 gal. The conversion to g units is 980.665 gal = 1 g.

Various chart types are available in the database for viewing the event data. Currently the database utilizes the SI unit for acceleration. Future releases will include support for data presentation in g units.

As event data is imported into the database, each measurement channel is stored in an individual data element series which enables support for multiple axis presentation and analysis. Figures 16 and 17 are examples of charts produced in the database:

(Top: Figure 16, Bottom: Figure 17)

integrating the kinemetrics obsidian seismic recorded with...

Documents