Skip to main content

All Configurable Parameters

Introduction​

Measurement Point Parameters are configuration values that can be assigned to measurement points in the Statotest monitoring system. These parameters enable customization of measurement functionality, data processing, and chart visualization.

The primary purposes of these parameters are:

  • Data Processing: Define coefficients, multipliers, dividers, and offsets for calculating measured values
  • Chart Configuration: Set names, units, and display settings for data series in charts
  • Data Filtering: Control which data should be hidden or filtered out
  • Temperature Compensation: Configure temperature-based corrections for measurements
  • Custom Calculations: Enable specialized calculations for specific measurement types

Parameter Structure​

Each parameter consists of several attributes that determine when and how it should be applied:

Required Attributes​

  • Name: The identifier of the parameter (e.g., "multiplier", "name", "toFixed")
  • Value: The parameter value (can be a number or text depending on the parameter type)

Optional Attributes​

  • Channel: The measurement channel number to which this parameter applies. If not specified, the parameter may apply globally or to all channels.
  • Valid From: A timestamp (epoch) indicating when this parameter becomes active. This allows parameters to change over time.

Advanced Attributes (Filtering)​

These attributes narrow down when a parameter should be applied to specific data:

  • Data Type: The type of measurement data (e.g., acceleration, raw, voltage, environment, inclination, strain, etc.)
  • Unit ID: Apply parameter only to data with a specific unit (e.g., temperature, humidity, voltage)
  • Sensor ID: Apply parameter only to data from a specific sensor type
  • Measurement ID: Apply parameter to specific measurement identifiers
  • Event ID: Apply parameter to specific event types (implemented fully in the future)
  • Application: Restrict parameter to specific applications:
    • web - Web portal
    • portal - Internal portal
    • mobile - Mobile app
    • r-ext-charts - External charts (public access without account)

Generic Parameters​

Generic parameters are available across all measurement types and provide fundamental configuration capabilities.

hideData​

Hides data from specific channels, sensors, or time periods.

Description: When set to "true", this parameter prevents data matching the specified criteria (channel, sensor ID, unit ID, valid from date) from being displayed in charts and exports.

Typical Values:

  • true - Hide the data
  • false - Show the data (default)

Example Use Cases:

  • Hide data from a malfunctioning sensor
  • Hide data from a specific channel during calibration periods
  • Remove invalid data from display

name​

Customizes the display name of a data series in charts.

Description: Overrides the default name for a data series. This is especially useful for providing meaningful labels for different channels or sensors.

Typical Values:

  • Temperature - Sensor 1
  • North Wall Displacement
  • Main Support Beam

Example Use Cases:

  • Provide descriptive names for measurement locations
  • Differentiate between multiple sensors measuring the same quantity
  • Use localized names for different languages

quantity​

Specifies the physical quantity being measured.

Description: Defines what physical property is being measured (e.g., displacement, force, pressure). This helps with data organization and interpretation.

Typical Values:

  • Displacement
  • Force
  • Pressure

Example Use Cases:

  • Document the measurement type for reports
  • Group similar measurements together
  • Provide context for data interpretation

unit​

Defines the unit of measurement for display.

Description: Sets the unit label that appears in charts and data exports. This overrides the default unit.

Typical Values:

  • mm (millimeters)
  • °C (degrees Celsius)
  • kN (kilonewtons)
  • MPa (megapascals)
  • % (percentage)

Example Use Cases:

  • Display values in preferred units
  • Show custom units for calculated values
  • Standardize units across different sensors

toFixed​

Controls the number of decimal places displayed for values.

Description: Specifies how many decimal places should be shown for the measured values. This affects both chart display and data exports.

Typical Values:

  • 0 - Show whole numbers only
  • 2 - Show two decimal places (e.g., 12.34)
  • 3 - Show three decimal places (e.g., 12.345)

Example Use Cases:

  • Reduce noise in displayed data by limiting decimals
  • Match precision to sensor capabilities
  • Improve readability of charts

toFixedTemp​

Sets decimal places specifically for temperature values.

Description: Similar to toFixed, but applies specifically to temperature measurements. This allows different precision for temperature versus the main measured quantity.

Typical Values:

  • 1 - Show one decimal place (e.g., 23.5°C)
  • 2 - Show two decimal places (e.g., 23.45°C)

Example Use Cases:

  • Set appropriate precision for temperature sensors
  • Differentiate temperature precision from main measurement precision

tempSensor​

Specifies the temperature source for temperature compensation.

Description: Defines which temperature sensor's data should be used for temperature-based calculations or compensation. This is critical for measurements that need temperature correction.

Typical Values:

  • disabled or false - Don't use temperature compensation
  • device - Use the device's internal temperature sensor
  • sensor - Use the measurement sensor's temperature
  • single - Use a single temperature source
  • [channel number] - Use temperature from a specific channel (e.g., 1, 2, 3)

Example Use Cases:

  • Use ambient temperature from a nearby sensor for strain gauge compensation
  • Use device temperature for internal corrections
  • Reference a specific temperature sensor for calculations

timeWindow​

Defines the time window for temperature data averaging.

Description: When using temperature data for calculations, this parameter specifies the time window (in minutes) over which temperature values should be averaged, or enables dynamic window calculation.

Typical Values:

  • dynamic - Calculate time window automatically based on data density
  • 5 - Use 5-minute averaging window
  • 60 - Use 1-hour averaging window

Example Use Cases:

  • Smooth temperature fluctuations for stable compensation
  • Match temperature averaging to measurement intervals
  • Reduce noise in temperature-dependent calculations

useApiCalculation​

Forces the use of server-side calculation instead of local calculation.

Description: When set to "true", values are calculated on the server/API side using stored coefficients rather than applying multipliers/dividers locally. This is useful when the API has access to more sophisticated calculation methods.

Typical Values:

  • true - Use server-calculated values
  • false - Apply local multiplier/divider/offset calculations (default)

Example Use Cases:

  • Use manufacturer-calibrated sensor calculations from the server
  • Leverage centralized calculation updates without changing client code
  • Access complex calculations not available in the chart library

multiplier​

Multiplies measured values by a coefficient.

Description: A numerical coefficient that is multiplied with the measured value. Used for sensor calibration, unit conversion, or applying sensitivity factors.

Typical Values:

  • 1 - No multiplication (default)
  • 0.001 - Convert from smaller to larger units (e.g., micrometers to millimeters)
  • 1.05 - Apply a 5% calibration correction

Example Use Cases:

  • Convert raw sensor output to engineering units
  • Apply calibration coefficients
  • Scale values for different unit systems

coeficient (DEPRECATED)​

⚠️ DEPRECATED: Use multiplier instead.

Legacy parameter that functioned the same as multiplier. Kept for backward compatibility but should not be used in new configurations.

divider​

Divides measured values by a coefficient.

Description: A numerical coefficient by which the measured value is divided. Often used in combination with multiplier for complex unit conversions.

Typical Values:

  • 1 - No division (default)
  • 1000 - Convert from larger to smaller units (e.g., meters to millimeters)
  • 2 - Apply a half-scale factor

Example Use Cases:

  • Convert between unit systems
  • Apply inverse calibration factors
  • Scale down large raw values

offset​

Adds or subtracts a constant value from measurements.

Description: A constant value that is added to the result after multiplier and divider are applied. Used for zero-point adjustment or baseline correction.

Typical Values:

  • 0 - No offset (default)
  • -5.5 - Subtract 5.5 from all values
  • 100 - Add 100 to all values

Example Use Cases:

  • Adjust sensor zero point
  • Apply baseline corrections
  • Shift values to a reference state

filterValues​

Removes specific values from the dataset.

Description: A semicolon-separated list of values that should be excluded from charts and calculations. Useful for filtering out known error values or invalid readings.

Typical Values:

  • 0 - Filter out zero values
  • 999; 9999 - Filter out multiple error codes
  • -273.15 - Filter out sensor error readings

Example Use Cases:

  • Remove sensor error codes from data
  • Filter out obviously invalid readings
  • Clean up data before visualization

removePeak​

Removes sudden spikes in data that exceed a threshold.

Description: Filters out individual data points that differ from neighboring values by more than the specified amount. Helps remove measurement spikes while preserving valid trends.

Typical Values:

  • 10 - Remove spikes greater than 10 units
  • 50 - Remove spikes greater than 50 units

Example Use Cases:

  • Remove electrical interference spikes
  • Filter mechanical shock readings
  • Clean noisy sensor data

aggregateByTimeWindow​

Groups data into time intervals for aggregation.

Description: Specifies the time window (in minutes) for grouping data points. Used in combination with aggregateByFunction to reduce data density and smooth trends.

Typical Values:

  • 5 - Aggregate data every 5 minutes
  • 60 - Aggregate data every hour
  • 1440 - Aggregate data daily (24 hours)

Example Use Cases:

  • Reduce data density for long-term trend analysis
  • Create hourly/daily averages
  • Smooth high-frequency measurement noise

aggregateByFunction​

Defines the mathematical function used for data aggregation.

Description: Specifies how multiple data points within a time window should be combined into a single value.

Typical Values:

  • avg - Calculate average (mean) of values in the window
  • median - Calculate median (middle value) in the window

Example Use Cases:

  • Use average for typical trending
  • Use median to reduce impact of outliers
  • Create smoother long-term trend lines

Developer Section: JSON Format​

For developers and advanced users, parameters are stored and transmitted in JSON format using the MpParam interface.

MpParam Interface Structure​

{
  "name": "string (required)",
  "value": "string (required)",
  "channel": "number (optional)",
  "validFromEpoch": "number (optional)",
  "unitId": "number (optional)",
  "sensorTypeId": "number (optional)",
  "eventTypeId": "number (optional)",
  "measId": "string (optional)",
  "chartType": "string (optional)",
  "application": "string (optional)"
}

Detailed Parameter Attribute Explanations​

Required Attributes​

name (string, required)

  • The parameter identifier that determines what functionality this parameter controls
  • Must match one of the documented parameter names (e.g., "multiplier", "name", "toFixed", "hideData")
  • Case-sensitive

value (string, required)

  • The parameter value, always stored as a string regardless of the actual data type
  • For numeric values: "1.5", "0.001", "100"
  • For boolean values: "true" or "false"
  • For text values: "Main Beam - North", "mm", "Temperature Sensor 1"
  • For JSON arrays: "[\"basic\", \"length\"]" or "[\"X\", \"Y\"]"

Optional Attributes (Filtering)​

channel (number, optional)

  • The measurement channel number to which this parameter applies
  • If omitted, the parameter may apply globally or to all channels (behavior depends on parameter type)
  • Example: 1, 2, 15

validFromEpoch (number, optional)

  • Unix timestamp (seconds since January 1, 1970) indicating when this parameter becomes active
  • Allows parameters to change over time
  • If multiple parameters with the same name/channel exist, the one with the latest validFromEpoch ≤ current time is used
  • Example: 1698163200 (October 24, 2023, 12:00:00 UTC)

unitId (number, optional)

  • Filters parameter application to data with a specific unit type
  • Used to apply different parameters to different units from the same channel
  • Common values: Temperature (various IDs), Humidity, Voltage, Distance, etc.
  • Only data matching this unit ID will be affected by the parameter

sensorTypeId (number, optional)

  • Filters parameter application to data from a specific sensor type
  • Used when multiple sensor types are used on the same channel
  • Example: 10 for LIS2DH12 internal accelerometer
  • Only data from sensors with this type ID will be affected

eventTypeId (number, optional)

  • Filters parameter application to specific event types
  • Future functionality - currently implemented for basic event filtering
  • Example: 1 for low-priority device events

measId (string, optional)

  • Filters parameter application to specific measurement identifiers
  • Advanced filtering for complex measurement scenarios
  • Rarely used in typical configurations

chartType (string, optional)

  • Restricts parameter to specific data types
  • Possible values: "accelero", "coordinateJTSK", "coordinateLocal", "device", "dilato", "environment", "inclino", "meteo", "onlyTemps", "raw", "strain", "unit", "voltage"
  • If omitted, parameter applies to all data types (when name matches)
  • Use this to create data-type-specific configurations

application (string, optional)

  • Restricts parameter to specific applications/platforms
  • Possible values: "web", "portal", "mobile", "r-ext-charts"
  • Allows different parameter sets for different user interfaces
  • If omitted, parameter applies to all applications

Detailed Examples​

Example 1: Multiplier Parameter​

{
  "name": "multiplier",
  "value": "0.001",
  "channel": 1,
  "validFromEpoch": 1698163200,
  "chartType": "strain",
  "application": "web"
}

Explanation:

  • name: "multiplier" - This parameter will multiply measured values
  • value: "0.001" - Multiply by 0.001 (convert from smaller to larger units)
  • channel: 1 - Apply only to channel 1 data
  • validFromEpoch: 1698163200 - Active from October 24, 2023, 12:00:00 UTC onwards
  • chartType: "strain" - Apply only to strain measurement data
  • application: "web" - Apply only in the web portal application

Use Case: Convert strain readings on channel 1 to different units starting from a specific date, but only in the web interface and only for strain data type.

Example 2: Name Parameter​

{
  "name": "name",
  "value": "Main Beam - North Side",
  "channel": 1
}

Explanation:

  • name: "name" - This parameter sets the display name for a data series
  • value: "Main Beam - North Side" - The custom name that will appear in charts
  • channel: 1 - Apply to channel 1
  • No chartType: applies to all data types from channel 1
  • No validFromEpoch: applies to all time periods
  • No application: applies to all applications

Use Case: Give channel 1 a descriptive, user-friendly name across all applications and time periods.

Example 3: Temperature Compensation Coefficient​

{
  "name": "tempCompensationCoefA",
  "value": "-0.0005",
  "channel": 3,
  "sensorTypeId": 25,
  "chartType": "raw",
  "validFromEpoch": 1709251200
}

Explanation:

  • name: "tempCompensationCoefA" - Quadratic coefficient for temperature compensation
  • value: "-0.0005" - Negative quadratic term value
  • channel: 3 - Apply to channel 3
  • sensorTypeId: 25 - Apply only to sensor type 25 on this channel
  • chartType: "raw" - Apply only to raw data type
  • validFromEpoch: 1709251200 - Active from March 1, 2024 onwards

Use Case: Apply specific temperature compensation to a particular sensor type on channel 3, starting from when new calibration was performed.

Example 4: Hide Data Parameter​

{
  "name": "hideData",
  "value": "true",
  "channel": 2,
  "validFromEpoch": 1698163200,
  "sensorTypeId": 10,
  "unitId": 5
}

Explanation:

  • name: "hideData" - This parameter hides data from display
  • value: "true" - Enable hiding (must be "true" to activate)
  • channel: 2 - Hide data from channel 2
  • validFromEpoch: 1698163200 - Hide data from this timestamp onwards
  • sensorTypeId: 10 - Only hide data from sensor type 10
  • unitId: 5 - Only hide data with unit ID 5

Use Case: Hide specific temperature readings (unit ID 5) from the internal sensor (type 10) on channel 2 after a certain date when the sensor was known to be malfunctioning.

Example 5: Multiple Parameters Array​

[
  {
    "name": "multiplier",
    "value": "0.001",
    "channel": 1,
    "chartType": "strain"
  },
  {
    "name": "offset",
    "value": "-50",
    "channel": 1,
    "chartType": "strain"
  },
  {
    "name": "name",
    "value": "Strain Gauge - Column A1",
    "channel": 1
  },
  {
    "name": "toFixed",
    "value": "3",
    "channel": 1
  }
]

Explanation: This array configures channel 1 with:

  1. A multiplier of 0.001 for strain data
  2. An offset of -50 (applied after multiplication) for strain data
  3. A custom display name for all data from channel 1
  4. Display precision of 3 decimal places

Calculation: ((raw_value × 0.001) + (-50)).toFixed(3)

Complete Example​

[
  {
    "name": "multiplier",
    "value": "0.001",
    "channel": 1,
    "validFromEpoch": 1698163200,
    "chartType": "strain",
    "application": "web"
  },
  {
    "name": "name",
    "value": "Main Beam - North",
    "channel": 1
  },
  {
    "name": "toFixed",
    "value": "3",
    "channel": 1,
    "unitId": 15
  },
  {
    "name": "hideData",
    "value": "true",
    "channel": 2,
    "validFromEpoch": 1698163200,
    "sensorTypeId": 10
  }
]

Data Type Specific Parameters​

The following sections document parameters that are specific to particular measurement types.

Acceleration (Accelero)​

viewSensor10​

Shows data from the internal LIS2DH12 accelerometer sensor.

Description: By default, data from the internal sensor (ID 10 - LIS2DH12) is hidden. Set this to "true" to display it.

Typical Values:

  • true - Show internal sensor data
  • false - Hide internal sensor data (default)

Example Use Cases:

  • Compare internal and external accelerometer readings
  • Debug sensor issues
  • Validate measurement setup

viewEvent1​

Shows data from low-priority device events.

Description: Controls whether data associated with low-priority device events (Event Type 1) should be displayed.

Typical Values:

  • true - Show event data
  • false - Hide event data (default)

Example Use Cases:

  • Include routine device status in analysis
  • Show all available data for troubleshooting

sensorACCType​

Filters acceleration data to show only specific sensor types.

Description: Restricts displayed data to a specific accelerometer sensor type ID.

Typical Values:

  • -200 - Show all sensor types (default)
  • 10 - Show only LIS2DH12 internal sensor
  • [sensor ID] - Show only specified sensor type

Example Use Cases:

  • Focus on data from a specific accelerometer model
  • Compare different sensor types separately
  • Filter by sensor capability

filterXParamL / filterYParamL / filterZParamL​

Sets the lower threshold for filtering X/Y/Z axis acceleration data.

Description: Data points with acceleration below this threshold on the respective axis will be excluded.

Typical Values:

  • -2.0 - Filter values below -2g
  • -0.5 - Filter values below -0.5g

Example Use Cases:

  • Remove negative acceleration artifacts
  • Filter out sensor drift
  • Define acceptable measurement range

filterXParamH / filterYParamH / filterZParamH​

Sets the upper threshold for filtering X/Y/Z axis acceleration data.

Description: Data points with acceleration above this threshold on the respective axis will be excluded.

Typical Values:

  • 2.0 - Filter values above 2g
  • 5.0 - Filter values above 5g

Example Use Cases:

  • Remove shock/impact spikes
  • Define maximum expected acceleration
  • Filter electrical noise

taraX / taraY / taraZ​

Tare (zero-point) values for X/Y/Z axis calibration.

Description: The zero-point reference value for each axis, used in sensor calibration calculations.

Typical Values:

  • 0 - No tare offset
  • 0.05 - Small tare correction

Example Use Cases:

  • Zero out sensor at installation position
  • Apply factory calibration values
  • Correct for mounting orientation

gainX / gainY / gainZ​

Gain (sensitivity) coefficients for X/Y/Z axis.

Description: Sensitivity factor applied to each axis for calibration and scaling.

Typical Values:

  • 1.0 - Unity gain (default)
  • 0.98 - 2% sensitivity reduction
  • 1.05 - 5% sensitivity increase

Example Use Cases:

  • Apply manufacturer calibration
  • Compensate for temperature effects
  • Normalize sensor response

offsetX / offsetY / offsetZ​

Offset values applied after gain for X/Y/Z axis.

Description: Final offset added to each axis after tare and gain calculations.

Typical Values:

  • 0 - No offset
  • 0.1 - Add 0.1g offset

Example Use Cases:

  • Fine-tune zero position
  • Apply post-calibration corrections
  • Adjust for known biases

Environment​

SHT​

Applies corrections for SHT30 humidity sensor.

Description: When set to "true", applies specific calculation corrections for SHT30 series humidity sensors, even if the sensor type ID doesn't match exactly.

Typical Values:

  • true - Apply SHT corrections
  • false - Use standard calculations (default)

Example Use Cases:

  • Fix humidity reading issues with SHT sensors
  • Apply manufacturer-specific corrections
  • Handle legacy sensor configurations

Inclination (Inclino)​

inclinoCharts​

Specifies which types of inclination charts to generate.

Description: A JSON array defining which chart types should be created from inclination data.

Typical Values:

  • ["basic"] - Show only basic inclination angles (default)
  • ["basic", "length"] - Show angles and calculated lengths
  • ["basic", "length", "settlement", "deviation"] - Show all chart types

Chart Types:

  • basic - Inclination angles in degrees (X, Y, Z)
  • length - Calculated displacements in meters
  • settlement - Vertical settlement calculations
  • deviation - Deviation from reference position

Example Use Cases:

  • Customize chart display for specific monitoring needs
  • Show only relevant calculations
  • Reduce chart clutter

hideAxis​

Hides specific axes from basic inclination charts.

Description: A JSON array of axis labels to hide from the basic inclination angle charts.

Typical Values:

  • [] - Show all axes (default)
  • ["Z"] - Hide Z axis
  • ["X", "Y"] - Show only Z axis

Example Use Cases:

  • Focus on relevant measurement axes
  • Simplify charts for single-axis monitoring
  • Remove axes with no meaningful data

viewSensor10​

Shows data from internal inclinometer sensor.

Description: Controls whether data from the internal inclinometer sensor (LIS2DH12, ID 10) should be displayed.

Typical Values:

  • true - Show internal sensor data
  • false - Hide internal sensor data (default)

Example Use Cases:

  • Compare internal vs external sensors
  • Use internal sensor for backup monitoring

event​

Filters out low-priority device events.

Description: When set to "true", hides data from low-priority device events (Event Type 1).

Typical Values:

  • true - Hide low-priority event data
  • false - Show all data (default)

Example Use Cases:

  • Focus on measurement data only
  • Remove device status readings

sensorACCType​

Filters inclination data by sensor type.

Description: Shows only data from a specific inclinometer sensor type.

Typical Values:

  • -200 - Show all sensor types (default)
  • [sensor ID] - Show only specified sensor type

Example Use Cases:

  • Compare different inclinometer models
  • Focus on calibrated sensor data

length​

The reference length for inclination-to-displacement calculations.

Description: The physical length (in meters) of the monitored element, used to calculate displacements from inclination angles.

Typical Values:

  • 1.0 - 1 meter reference length
  • 2.5 - 2.5 meter reference length
  • 10.0 - 10 meter reference length

Example Use Cases:

  • Calculate beam deflection from angle
  • Convert angle to linear displacement
  • Monitor column tilt as horizontal displacement

x0 / y0 / z0​

Reference (zero) angles for X/Y/Z axes.

Description: The initial reference angle for each axis, representing the "zero" position from which changes are measured.

Typical Values:

  • 0 - Perfectly level reference
  • 2.5 - 2.5° initial angle
  • -1.2 - -1.2° initial angle

Example Use Cases:

  • Set installed position as reference
  • Account for intentional slope
  • Define baseline for change detection

offsetX / offsetY / offsetZ​

Offset values for length calculation on X/Y/Z axes.

Description: Constant offset (in meters) added to the calculated displacement for each axis.

Typical Values:

  • 0 - No offset
  • 0.05 - Add 50mm offset

Example Use Cases:

  • Adjust for reference point location
  • Apply known initial displacement
  • Correct for mounting position

diameter​

Diameter for Z-axis length calculation.

Description: The diameter (in meters) used instead of length for Z-axis displacement calculations. This is useful for rotation-based calculations.

Typical Values:

  • 0.5 - 0.5 meter diameter
  • 1.0 - 1 meter diameter

Example Use Cases:

  • Calculate displacement at the edge of a rotating element
  • Monitor circular cross-section elements
  • Convert rotation to linear displacement

startAngle​

Initial angle for settlement calculations.

Description: The reference angle for settlement calculations, typically the Y-axis angle at the start of monitoring.

Typical Values:

  • 0 - Level initial position
  • 1.5 - 1.5° initial slope

Example Use Cases:

  • Set baseline for settlement monitoring
  • Account for initial construction slope
  • Define reference state

settlementOffset​

Offset applied to settlement calculations.

Description: Constant offset (in meters) added to calculated settlement values.

Typical Values:

  • 0 - No offset
  • -0.02 - Subtract 20mm from settlement

Example Use Cases:

  • Adjust for initial survey elevation
  • Correct for reference benchmark
  • Apply known starting settlement

calculateSettlement​

Enables settlement calculation for a channel.

Description: When set to "true", settlement calculations are performed for this channel using the Y-axis inclination and length parameter.

Typical Values:

  • true - Calculate settlement
  • false - Don't calculate settlement (default)

Example Use Cases:

  • Monitor foundation settlement
  • Track vertical movement
  • Calculate subsidence

deviationOffsetX / deviationOffsetY / deviationOffsetZ​

Reference angles for deviation calculations.

Description: The reference angle for each axis against which current angles are compared to calculate deviation.

Typical Values:

  • 0 - No deviation from level
  • 1.5 - 1.5° reference angle

Example Use Cases:

  • Set design position as reference
  • Monitor deviation from as-built state
  • Track angle changes from baseline

Raw Data​

newView​

Controls which version of raw data processing to use.

Description: Legacy parameter to switch between old and new data processing methods. New view is now required.

Typical Values:

  • false - ⚠️ Old view (no longer supported - will cause error)
  • Default (not set) - Use new view

enableTempCompensation​

Enables temperature compensation for raw measurements.

Description: When set to "true", applies polynomial temperature compensation to raw values using configured coefficients.

Typical Values:

  • true - Enable temperature compensation
  • false - No compensation (default)

Example Use Cases:

  • Compensate strain gauges for temperature effects
  • Remove thermal drift from measurements
  • Apply sensor temperature corrections

tempCompensationCoefA​

Quadratic coefficient for temperature compensation.

Description: The 'A' coefficient in the temperature compensation polynomial: A×T² + B×T + C

Typical Values:

  • 0 - No quadratic term
  • 0.0001 - Small quadratic correction
  • -0.0005 - Negative quadratic correction

Example Use Cases:

  • Apply non-linear temperature effects
  • Use manufacturer calibration coefficients
  • Model complex temperature response

tempCompensationCoefB​

Linear coefficient for temperature compensation.

Description: The 'B' coefficient in the temperature compensation polynomial: A×T² + B×T + C

Typical Values:

  • 0 - No linear term
  • -0.5 - Moderate linear correction
  • 1.2 - Positive linear correction

Example Use Cases:

  • Apply primary temperature sensitivity
  • Use sensor datasheet coefficients
  • Correct linear thermal expansion

tempCompensationCoefC​

Constant coefficient for temperature compensation.

Description: The 'C' coefficient (constant term) in the temperature compensation polynomial: A×T² + B×T + C

Typical Values:

  • 0 - No constant term
  • 10 - Constant offset of 10

Example Use Cases:

  • Apply zero-temperature offset
  • Add constant correction factor

tempCompensationReference​

Reference temperature for compensation calculations.

Description: The temperature (in °C) at which the compensation calculation is referenced. The compensation formula result is subtracted from this reference value.

Typical Values:

  • 20 - 20°C reference
  • 0 - 0°C reference
  • 25 - 25°C reference (common calibration temperature)

Example Use Cases:

  • Set calibration temperature as reference
  • Define zero-compensation point
  • Match manufacturer specifications

tempCompensationOffset​

Additional offset after temperature compensation.

Description: A constant value added after temperature compensation and other calculations are complete.

Typical Values:

  • 0 - No additional offset
  • 5.5 - Add 5.5 units after compensation

Example Use Cases:

  • Fine-tune compensated values
  • Apply post-compensation baseline
  • Correct for residual drift

showBeforeCompensated​

Shows both compensated and uncompensated values.

Description: When set to "true", displays both the original raw values and the temperature-compensated values in separate data series.

Typical Values:

  • true - Show both original and compensated (default when compensation is enabled)
  • false - Show only compensated values

Example Use Cases:

  • Compare before/after compensation
  • Validate compensation effectiveness
  • Debug compensation formulas

negativeRawValue​

Inverts the sign of raw values.

Description: When set to "true", multiplies raw values by -1 before any other processing.

Typical Values:

  • true - Invert raw values
  • false - Use raw values as-is (default)

Example Use Cases:

  • Correct sensor polarity
  • Match sign convention
  • Fix inverted installation

displayNewtons​

Converts raw strain values to Newtons.

Description: When set to "true", creates an additional data series showing values converted to Newtons (force unit). This is a specialized calculation for specific strain applications.

Typical Values:

  • true - Calculate and show force in Newtons
  • false - Don't calculate Newtons (default)

Example Use Cases:

  • Display load measurements
  • Convert strain to force for specific sensors
  • Show engineering units instead of raw strain

dataType​

Specifies special data type processing for raw data.

Description: Defines how raw data should be processed for specific sensor types.

Typical Values:

  • thermocouple - Apply thermocouple voltage-to-temperature conversion
  • pyranometr - Apply pyranometer processing (negative values set to zero)
  • (empty) - Standard raw processing (default)

Example Use Cases:

  • Process thermocouple voltage readings
  • Handle solar radiation sensors
  • Apply sensor-specific algorithms

Strain​

strainView​

Specifies the strain sensor type and calculation method.

Description: Defines which strain calculation formula should be used based on the sensor manufacturer or model.

Typical Values:

  • new - Modern vibrating wire sensors (default)
  • geokon - Geokon vibrating wire sensors
  • smejkalka - Smejkalka-specific calculation
  • pontex - Pontex vibrating wire sensors
  • true - Legacy calculation (old formula)

Example Use Cases:

  • Match sensor manufacturer specifications
  • Use correct calculation for sensor type
  • Support different sensor brands

K​

K coefficient for legacy strain calculation.

Description: Used in the older strain calculation formula: ((f² - f0²) × K). Only used when strainView is set to "true".

Typical Values:

  • 1.0 - Unity coefficient
  • 0.8 - Typical K value

Example Use Cases:

  • Support legacy sensor installations
  • Use historical calibration data

f0​

Reference frequency (f0) for legacy strain calculation.

Description: The reference frequency value in Hz, used in older strain calculation: ((f² - f0²) × K). Only used when strainView is set to "true".

Typical Values:

  • 1000 - 1000 Hz reference
  • 1200 - 1200 Hz reference

Example Use Cases:

  • Set sensor's initial frequency
  • Use factory calibration value

L0 (or Dig_0)​

Reference digit value for strain calculation.

Description: The zero-strain digit value (f²/1000) used in modern strain calculations. Represents the sensor reading at zero strain.

Typical Values:

  • 1000 - 1000 digit reference
  • 1250 - 1250 digit reference

Example Use Cases:

  • Set installation reading as zero point
  • Use manufacturer's zero strain value
  • Establish baseline for measurements

G​

Gauge factor for strain sensors.

Description: The sensor's gauge factor (sensitivity coefficient) that converts digit changes to microstrain.

Typical Values:

  • 1.0 - Unity gauge factor
  • 3.2 - Common gauge factor for vibrating wire sensors
  • 0.8 - Lower sensitivity gauge

Example Use Cases:

  • Apply sensor-specific sensitivity
  • Use manufacturer calibration
  • Convert raw readings to engineering units

gaugeLength​

Physical gauge length of the strain sensor.

Description: The active measurement length of the strain sensor in millimeters. Used for converting strain to deformation (displacement).

Typical Values:

  • 150 - 150mm gauge length
  • 100 - 100mm gauge length
  • 200 - 200mm gauge length

Example Use Cases:

  • Calculate absolute deformation
  • Convert strain to linear displacement
  • Match sensor physical specifications

filterData​

Enables value filtering for strain data.

Description: When set to "true" for a channel, enables filtering based on filterParamL and filterParamH thresholds.

Typical Values:

  • true - Enable filtering
  • false - Disable filtering (default)

Example Use Cases:

  • Remove outliers from strain data
  • Filter sensor noise
  • Define valid measurement range

filterParamL​

Lower threshold for strain filtering.

Description: When filterData is enabled, strain values below this threshold are excluded.

Typical Values:

  • -500 - Filter strains below -500 με
  • -1000 - Filter strains below -1000 με

Example Use Cases:

  • Remove unrealistic compression readings
  • Define minimum expected strain
  • Filter sensor errors

filterParamH​

Upper threshold for strain filtering.

Description: When filterData is enabled, strain values above this threshold are excluded.

Typical Values:

  • 500 - Filter strains above 500 με
  • 2000 - Filter strains above 2000 με

Example Use Cases:

  • Remove unrealistic tension readings
  • Define maximum expected strain
  • Filter measurement spikes

tempMultiplier​

Temperature multiplier for strain sensor temperature.

Description: Multiplies the raw temperature reading from the strain sensor.

Typical Values:

  • 1 - No multiplication (default)
  • 0.1 - Scale down by factor of 10

Example Use Cases:

  • Convert temperature units
  • Apply temperature sensor calibration

tempDivider​

Temperature divider for strain sensor temperature.

Description: Divides the temperature reading (after multiplier).

Typical Values:

  • 1 - No division (default)
  • 10 - Divide by 10

Example Use Cases:

  • Convert temperature scales
  • Apply inverse calibration

tempOffset​

Temperature offset for strain sensor temperature.

Description: Value added to temperature after multiplier and divider.

Typical Values:

  • 0 - No offset (default)
  • -5 - Subtract 5°C
  • 20 - Add 20°C

Example Use Cases:

  • Correct temperature sensor bias
  • Convert to different temperature reference

digitView​

Shows digit values (f²/1000) in charts.

Description: When set to "true", displays the intermediate digit value calculation in addition to strain.

Typical Values:

  • true - Show digit values
  • false - Don't show digits (default)

Example Use Cases:

  • Debug strain calculations
  • Monitor raw frequency-based values
  • Compare with sensor manufacturer tools

deformationView​

Shows deformation (displacement) values in charts.

Description: When set to "true", displays the calculated deformation in millimeters based on strain and gauge length.

Typical Values:

  • true - Show deformation
  • false - Don't show deformation (default)

Example Use Cases:

  • Display absolute displacement
  • Show physical movement instead of strain
  • Provide intuitive measurement units

frequencyView​

Shows raw frequency values in charts.

Description: When set to "true", displays the raw vibrating wire frequency readings in Hz.

Typical Values:

  • true - Show frequency
  • false - Don't show frequency (default)

Example Use Cases:

  • Monitor sensor health
  • Debug frequency stability
  • Compare with manual readings

pascalView​

Shows values converted to stress (Pascals).

Description: When set to "true", converts strain to stress using elastic modulus (E).

Typical Values:

  • true - Show stress values
  • false - Don't show stress (default)

Example Use Cases:

  • Display stress instead of strain
  • Calculate material stress from strain
  • Monitor structural stress levels

Unit Data​

viewTension​

Shows voltage/tension values for unit data.

Description: When set to "true" for a channel, displays voltage/tension readings in addition to or instead of calculated values.

Typical Values:

  • true - Show tension values
  • false - Don't show tension (default)

Example Use Cases:

  • Monitor sensor voltage
  • Debug sensor power issues
  • Show electrical measurements

E[GPa]​

Elastic modulus for stress calculation.

Description: The elastic modulus (Young's modulus) in GPa, used to convert strain-type unit measurements to stress (force).

Typical Values:

  • 210 - Steel (~210 GPa)
  • 200 - Structural steel
  • 70 - Aluminum

Example Use Cases:

  • Calculate stress from strain measurements
  • Convert microstrain to MPa
  • Apply material properties

unitDataType​

Specifies the data type for unit measurements.

Description: Categorizes the unit data for appropriate processing and display.

Typical Values:

  • (varies based on measurement type)

Example Use Cases:

  • Classify measurement types
  • Enable type-specific processing

Only Temps (Temperature-Only Charts)​

onlyTemp​

Enables temperature-only chart mode.

Description: When set to "true", creates charts showing only temperature-related calculations like dew point and delta-T.

Typical Values:

  • true - Enable temperature-only charts
  • false - Standard charts (default)

Example Use Cases:

  • Create dedicated temperature monitoring charts
  • Focus on thermal analysis
  • Monitor environmental conditions

dewpoint​

Calculates and displays dew point temperature.

Description: When set to "true", calculates dew point from temperature and humidity measurements.

Typical Values:

  • true - Calculate dew point
  • false - Don't calculate (default)

Example Use Cases:

  • Monitor condensation risk
  • Track humidity conditions
  • Predict moisture problems

deltaT​

Calculates temperature difference from dew point.

Description: When set to "true", calculates and displays the difference between temperature and dew point (delta-T), which indicates condensation risk.

Typical Values:

  • true - Calculate delta-T
  • false - Don't calculate (default)

Example Use Cases:

  • Monitor condensation risk
  • Assess moisture conditions
  • Prevent frost/condensation

Voltage​

No voltage-specific parameters beyond the generic parameters (multiplier, divider, offset, etc.).

Dilato (Dilatometer)​

Uses generic parameters (multiplier, divider, offset, toFixed, useApiCalculation, hideData) for processing voltage measurements into displacement values. No dilato-specific parameters.

Device​

Uses generic parameters, primarily toFixedTemp for temperature display precision from device sensors.

Coordinate (JTSK and Local)​

Coordinate measurements use no specific parameters beyond the generic ones. Processes GPS/surveying position data in both JTSK (national coordinate system) and local coordinate systems.

Meteo (Meteorological)​

Currently not implemented with specific parameters. Future meteorological data support planned.

Wood Monitor​

Currently not implemented with specific parameters. Future wood moisture monitoring support planned.

Summary​

This documentation covers all available measurement point parameters in the Statotest charts library. Parameters are organized into:

  • Generic parameters: Available for all measurement types
  • Type-specific parameters: Available only for specific measurement types (acceleration, inclination, strain, etc.)

Each parameter includes:

  • Name and description
  • Typical values and examples
  • Practical use cases
  • Technical context

For developers, the JSON format section provides the complete technical specification of the parameter structure.

When configuring parameters:

  1. Start with required fields (name, value)
  2. Add channel if parameter applies to specific channels
  3. Use validFromEpoch for time-based parameter changes
  4. Apply advanced filters (unitId, sensorTypeId, etc.) to narrow parameter scope
  5. Test parameters with representative data before production deployment