Gecko events - DMU801

Device events domain: Gecko

Code prefix: gecko

adc.InternalError

• Message: {componentName}: ADC internal error in port {portId}
• Severity: Error

• Custom data:

  • componentName: Component name in the application
  • portId: Port identifier

• Reason:

  The ADC subsystem encountered an internal error. This may be due to faulty or missing hardware.

• Recovery:

  1. Make sure that the DMA80x plug-in modules are properly installed.
  2. Check that the pins in the baseboard are not bent or damaged.

adc.measurementFailure

• Message: {componentName}: analog measurement failure in port {portId}
• Severity: Error

• Custom data:

  • componentName: Component name in the application
  • portId: Port identifier
  • adcErrors: Errors detected in analog measurement

• Reason:

  The measurement failed due to one or more of the following errors:

  • LOW_PIN_UNDERVOLTAGE: Voltage at LOW input pin is too low to measure (undervoltage)
  • LOW_PIN_OVERVOLTAGE: Voltage at LOW input pin is too high to measure (overvoltage)
  • HIGH_PIN_UNDERVOLTAGE: Voltage at HIGH input pin is too low to measure (undervoltage)
  • HIGH_PIN_OVERVOLTAGE: Voltage at HIGH input pin is too high to measure (overvoltage)
  • ADC_SATURATION: Selected voltage range is too small for the measurement (saturation)
  • ADC_CONVERSION_ERROR: Input voltage is out of range (positive or negative) for the measurement to be reliable (conversion error)
  • ADC_CALIBRATION_ERROR: Periodical offset calibration routine failed (calibration error)

• Recovery:

  • Over- or undervoltage: Check that the connected sensor is correctly powered.
  • Saturation or conversion error: Check that the voltage range is suitable for the measurement.
  • Calibration error: Check for excessive RF interference. Replace the DMA80x plug-in module.

adc.sensorNotDetected

• Message: {componentName}: sensor not detected in port {portId}
• Severity: Error

• Custom data:

  • componentName: Component name in the application
  • portId: Port identifier

• Reason:

  The system does not detect the sensor. This may be due to hardware failure, configuration error, or sensor malfunction.

• Recovery:

  1. Check the sensor connection.
  2. Check the sensor configuration.
  3. Check the sensor for physical damage.

application.scriptStart

• Message: Application script started: fingerprint {scriptHash}
• Severity: Informational

• Custom data:

  • scriptHash: SHA-256 hash of the currently running the application
  • isStandardConfig: (Hidden flag) indicates whether the application is the default (true) or customized (false) application

• Reason:

  The application has been started. This may be due to system startup or an explicit application upload or restart request.

application.start

• Message: Application started: version {version}
• Severity: Informational

• Custom data:

  • version: Version identifier

• Reason:

  The observation processing engine has been started. This may be due to system startup, explicit restart request, or application failure.

application.scriptFailure

• Message: Application script failed, engine halted
• Severity: Critical

• Custom data:

  • reason: Hidden reason (exception string)

• Reason:

  The observation processing engine has detected an error in the application. Typically, this is due to an error in the application, but it can also be caused by a missing or malfunctioning external instrument.

• Recovery:

  1. Make sure that the instruments are connected and configured correctly.
  2. Make sure that the feature groups and station parameters match the available instruments.
  3. Check that the system has the correct version of the application.
  4. Fix or replace any malfunctioning instruments.

component.statusChange

• Message: {componentName}: component status changed to {status}
• Severity: Warning

• Custom data:

  • status: New status (OK, DISABLED, ERROR, MISSING, SERVICE, WARNING)
  • componentName: Component name in the application

• Reason:

  Status of an application component has changed. The component may represent an external instrument or a peripheral (a physical device), a collection of devices, an algorithm, or other purely logical component.

  Most commonly this status event is used with components representing a physical device. Some statuses are only meaningful for physical devices.

  The status values are:

  • OK: The component is functioning normally (this status marks the end of an abnormal state)
  • DISABLED: The component has been intentionally disabled
  • ERROR: The component or device has encountered some kind of malfunction
  • MISSING: The device is not connected to the system or does not communicate
  • SERVICE: The device is intentionally placed into service mode
  • WARNING: The component reports degraded operational state

• Recovery:

  When the component represents a device:

  1. If the status is ERROR or MISSING, the device may be malfunctioning.
  2. If the status is WARNING, check other events or the device documentation for further recovery guidance.
  3. Check the cabling and function of the instrument.

  There may be other events that more accurately describe the root cause of the status change.

custom.observation.alarm

• Message: Observation value alarm: {componentName}.{observationName}: "{message}"
• Severity: Alarm

• Custom data:

  • componentName: Originating component name in the application
  • observationName: Name of the observation
  • message: Textual alarm message
  • observationValue: Observation value
  • observationQuality: Observation quality
  • state: In alarm state

• Reason:

  The application is reporting an alarm-level issue related to an observation value.

custom.observation.informational

• Message: Observation value information: {componentName}.{observationName}: "{message}"
• Severity: Informational

• Custom data:

  • componentName: Originating component name in the application
  • observationName: Name of the observation
  • message: Textual information message
  • observationValue: Observation value
  • observationQuality: Observation quality

• Reason:

  The application is reporting information related to an observation value.

custom.observation.warning

• Message: Observation value warning: {componentName}.{observationName}: "{message}"
• Severity: Warning

• Custom data:

  • componentName: Originating component name in the application
  • observationName: Name of the observation
  • message: Textual information message
  • observationValue: Observation value
  • observationQuality: Observation quality
  • state: In warning state

• Reason:

  The application is reporting a warning-level issue related to an observation value.

custom.script.error

• Message: {componentName}: "{message}"
• Severity: Error

• Custom data:

  • componentName: Originating component name in the application
  • message: Textual error message
  • code: Application-specific code
  • state: In error state

• Reason:

  The application is reporting a critical technical issue.

custom.script.informational

• Message: {componentName}: "{message}"
• Severity: Informational

• Custom data:

  • componentName: Originating component name in the application
  • message: Textual information message

• Reason:

  The application informs about a significant technical event.

custom.script.warning

• Message: {componentName}: "{message}"
• Severity: Warning

• Custom data:

  • componentName: Originating component name in the application
  • message: Textual warning message
  • code: Application-specific code
  • state: In warning state

• Reason:

  The application informs about a non-critical technical issue.

feature.activation

• Message: Feature {featureName} activated
• Severity: Informational

• Custom data:

  • featureName: Name of the activated feature (for example, MODBUS_TCP, FTP)

• Reason:

  The user activated a feature.

feature.allowUnencryptedProtocols

• Message: Unencrypted protocols allowed
• Severity: Warning

• Reason:

  The ability to activate unsecured communication protocols with security risk has been enabled. This is a security-relevant action that allows subsequent activation of protocols like MODBUS_TCP.

feature.deactivation

• Message: Feature {featureName} deactivated
• Severity: Informational

• Custom data:

  • featureName: Name of the deactivated feature

• Reason:

  The user deactivated a feature.

feature.disabledByPolicyCheck

• Message: Feature {featureName} disabled by policy: {reason}
• Severity: Warning

• Custom data:

  • featureName: Name of the feature that was disabled

• Reason:

  Policy violation reason (for example, Unencrypted communication is not allowed)

feature.disallowUnencryptedProtocols

• Message: Unencrypted protocols disallowed
• Severity: Informational

• Reason:

  The ability to use unencrypted communication protocols has been disabled. Any active unencrypted protocols have been automatically deactivated.

io.doorSwitch

• Message: "{switchId}" door state is "{state}"
• Severity: Alarm

• Custom data:

  • state: Door switch state (open, closed, unknown)
  • switchId: Door switch identifier (for example, Enclosure, Cabin, Inner, or similar)

• Reason:

  The door switch has detected a change in the door state. This event is typically used to monitor the state of the enclosure door or other doors in the system.

web.scriptUpdate

• Message: Application script updated by user "{username}"
• Severity: Informational

• Custom data:

  • username: User who performed the action
  • filename: Application filename

• Reason:

  The application has been updated through the Web UI or API.

web.stationParameterUpdate

• Message: Station parameters updated by user "{username}"
• Severity: Informational

• Custom data:

  • username: User who performed the action
  • updatedStationParameters: Station parameters that have been updated

• Reason:

  Application station parameters have been updated through the Web UI or API.