Delta Watch: File formats - Tilt sensors

Need to import tilt sensor data?

This article describes the data formats that Delta Watch supports as well as the file format for creating many sensors at once.

Log in or sign up for myTopcon to view this page:

Delta Watch: File formats - Tilt sensors

Introduction

This article details the file formats supported by Delta Watch to import geotechnical tilt meter data. There is native support for some data file formats, but if the required format is not directly supported at the moment, then use this guide to convert the original data into a format Delta Watch can import.

At the moment, the following file formats are supported:

Tilt Meter Data Type Import Formats
Format Type Description
Senceive (*.CSV format) Native support for data files created by a Senceive wireless sensors system
VMT data format (*.CSV) General format for importing tilt sensor data. Preferably convert any non-supported data format to this format.
GeoScope customized Native support for GeoScope generated tilt data files

 

 

Senceive (*.CSV format)

This data format is to directly support data files from the wireless tilt sensors from Senceive.

Filename

The file as generated by a Senceive gateway can directly go to Delta Watch. Simply ensure that this data goes in its own dedicated folder for import in Delta Watch. The diagram below shows the filename construction in detail.

Filename: gw _ 0X _ YYYY-MM-DD _ hh-mm-ss .CSV
Fixed text              
Separator            
Count number of the gateway          
Separator        
Date code where:
  YYYY = year
  MM = month
  DD = day
     
Separator    
Time code where:
  hh = hour
  mm = minutes
  ss = seconds
 
File extension, only .CSV

File format

  • File should not have a header row
  • Uses the comma as column separator
  • Has only one value per data line
  • Uses CRLF as EOL character
  • Order and type of columns is as per the table below:

 

Column Description Unit Format
Node-ID Unique Node ID/MAC address. This is not used by Delta Watch. String char[23]
Point name The name as given to the sensor. This is the name used in Delta Watch and needs to match exactly. String  
DateTime Date + Time code of the reading   YYYY-MM-DD hh:mm:ss
SensorType Denotes the respective channel of the sensor and thus the type of the data.
See below SensorTypeID table
[code] Integer
Value Value for SensorType in units as per SensorTypeID table --- Float

 

SensorType ID codes and units for tilt sensor nodes

SensorType Description Unit
0 Battery voltage Volts
1 Onboard temperature Degrees Celcius
18 Tilt X-axis Decimal degrees
19 Tilt Y-axis Decimal degrees
20 Tilt Z-axis Decimal degrees

 

Example file below:

VMT data format (*.CSV)

This data format could be used when creating your own data files externally. Take care of the required columns.

Filename

The diagram below explains the filename construction.

Filename: Tilt _ YYYYMMDD _ hhmmss .CSV
Fixed text          
Separator        
Date code where:
  YYYY = year
  MM = month
  DD = day
     
Separator    
Time code where:
  hh = hour
  mm = minutes
  ss = seconds
 
File extension, only .CSV

File format

  • Uses the semicolon as column separator
  • Single header row, as specified in the table below
  • Uses CRLF as EOL character

Column

Description Unit Format Optional
Sensorname Sensor name, this one to be used in configuring Delta Watch String char[23]  
Date_Time Date + Time (UTC+00) of measurement    YYYYMMDD_hhmmss  
Valid True/False Flag char[5] (True or False)  
TiltX Tilt in direction of X-axis Radians Float  
TiltY Tilt in direction of Y-axis Radians Float  
TiltZ Tilt in direction of Z-axis Radians Float  
Battery Voltage of power supply Volt Float YES
Temperature Internal sensor temperature Degree Celcius Float YES

 

Example header row:

Sensorname;Date_Time;Valid;TiltX[rad];TiltY[rad];TiltZ[rad];Battery[V];Temperature[DegC]

Example file below:

GeoScope customized

This data format should be used when using the GeoScope sensors and logging system. To be able to import a value to the correct channel, each channel in the Sensor management module needs to be adjusted for this format only. See below for more details.

Filename

The diagram below explains the filename construction.

Filename: Tilt _ YYYY_MM_DD _ hh_mm_ss .txt
Fixed text          
Separator        
Date code where:
  YYYY = year
  MM = month
  DD = day
     
Separator    
Time code where:
  hh = hour
  mm = minutes
  ss = seconds
 
File extension, only .TXT

File format

  • File has no header
  • Uses the [TAB] character as column separator
  • Contains a single value per data line where the channel type name gets appended to the Sensorname
  • Last column value is always 0
  • Uses CRLF as EOL character
Column Description Unit Format
Channel ID sensor name, including channel identifier _x, _y, or _z. This field can only contain one underscore character! String char[25]
Date + Time Date (UTC+00) of measurement. Note the space between the date and time. --- DD/MM/YYYY hh:mm:ss
Value Tilt value for axis as per Sensorname Radians Float
Fixed-field Fixed field containing the value 0 --- Integer

 

Example file below:

Channel ID

To correctly identify for which channel a data value is in the GeoScope data format, a channel identifier is appended at the end of the sensorname to create the Channel ID. This will either be _x, _y, or _z for each respective axis. See the above data file example.

For Delta Watch to process this data correctly, the channel name needs to be adjusted in the Sensor management section. The channel name needs to start with the text Alpha. Therefore, for a tilt sensor with the name Tilt01, the X channel name in the file becomes Tilt01_x, and in Delta Watch the channel name becomes Alpha X.

To do this:

  1. Navigate to Point and limit management > Sensor management.
  2. Select the sensor.
  3. Select the Channel to adjust, either: Tilt x-axis, Tilt y-axis, or Tilt z-axis.
  4. Double-click on the channel, or click on the Edit [Edit] icon.
  5. Adjust the channel name to Alpha ?, where ? is either x, y, or z. Close the dialog box.
  6. Repeat for any other channels and sensors.
  7. Write the changes to the database.