🌪️ Discover the Turbine Sensor Plugin – Your Solution for Precise Turbine Monitoring

The Turbine Sensor Plugin is a powerful tool for managing and configuring turbine sensors. Using advanced acoustic signal processing and machine learning algorithms, this plugin monitors turbine noises and reliably detects whether they are running or not. It immediately informs flight personnel when turbines are shut down, allowing the passenger cabin to be connected to the aircraft. With intuitive, flow-based programming, you can effortlessly set up workflows to efficiently process detected turbine states.

🌟 Why Choose the Turbine Sensor Plugin?

  • ⚡ Real-Time Turbine Monitoring: Instantly detect the operational status of turbines and respond in real-time.
  • 🎯 Precise Status Detection: Use acoustic signals and machine learning to accurately determine whether turbines are running or stopped.
  • 💾 Data Management & Storage: Securely store all detected turbine states in the database and access them anytime through the provided API.
  • 📢 Automated Notifications: Automatically inform flight personnel when turbines are shut down, allowing safe connection of the passenger cabin.
  • 🤖 Automated Workflow Integration: Seamlessly integrate the Turbine Sensor Plugin into your existing workflows to automate event management.
  • 🎵 Acoustic Signal Processing: Utilize highly precise acoustic signals to reliably monitor turbine operational status.

✨ Your Benefits at a Glance

  • 📈 Improved Efficiency: Optimize airport operations with accurate information about turbine status.
  • 🛡️ Increased Safety: Ensure the passenger cabin is only connected when turbines are safely shut down.
  • ⏳ Time Savings: Automate repetitive tasks and focus on what truly matters.
  • 📞 Reliable Support: Enjoy 24/7 customer service and a 1-year warranty for peace of mind.
  • 🔄 Easy Updates: Stay up-to-date with regular updates, including the latest version 1.0.2.

🚀 Perfect for Your Needs

Whether you want to enhance aircraft monitoring systems, improve turbine status detection accuracy, or automate event management workflows – the Turbine Sensor Plugin provides the flexibility and performance you need.

💼 Use Cases:

  • ✈️ Airport Operators: Monitor and manage the operational status of aircraft turbines for smooth gate operations.
  • 🛫 Airlines: Improve safety and efficiency by keeping ground personnel informed of turbine status.
  • 🛠️ Maintenance Providers: Detect anomalies in turbine operations early for proactive maintenance.
  • 🏭 Aircraft Manufacturers: Integrate the Turbine Sensor Plugin into systems for quality assurance and performance monitoring.

Start today with the Turbine Sensor Plugin and turn acoustic turbine sounds into valuable data for your projects! 🌟

💥 Highlights:

  • 💪 Powerful & Flexible: Ideal for a wide range of applications in turbine monitoring.
  • 🖱️ User-Friendly: Easy setup and integration with flow-based programming.
  • 🔒 Secure & Reliable: Robust data management and continuous support ensure smooth operation.

Take the next step in precise and efficient turbine monitoring with the Turbine Sensor Plugin! 🌪️✨

| Field | Value | |-----------------------|---------------------------------------------------------------------------| | NAME | turbinesensor | | VERSION | 1.0.2 | | ALIAS | Turbine Sensor Plugin | | TAGS | sensor, event, turbine, acoustic, detection, machine learning, workflow integration, event analysis | | SHORTDESCRIPTION | Detects and monitors turbine statuses using acoustic signals and machine learning. | | DESCRIPTION | The Turbine Sensor Plugin is a powerful tool designed to manage and configure turbine sensors. Utilizing advanced acoustic signal processing and machine learning algorithms, this plugin monitors the sounds of turbines to determine whether they are running or not. It provides immediate notifications to flight personnel when turbines have stopped, indicating that the passenger cabin can be connected to the aircraft. With flow-based programming, you can easily set up workflows to process detected turbine statuses efficiently. This plugin is ideal for enhancing aircraft monitoring systems, improving detection accuracy, and automating event management workflows. Turbine events can be filtered based on various criteria, stored securely, and accessed seamlessly via the provided API. |

Module Nodes

the module nodes are the building blocks for the flow-based programming. Each node represents a specific task or operation that can be performed by the module. The following table lists the available nodes for this module.

Filter Turbine Event by Aircraft Presence

Filter turbine events based on the presence of an aircraft at the gate.

Metadata:

  • Name: FilterAircraftPresenceTurbineEvent
  • Tags: filter, aircraft presence, turbine event
  • Category: Filter
  • Subcategory: Aircraftpresence > Turbineevent

Description:

This node filters turbine events by the presence of an aircraft at the gate. The presence is determined by the actual time an aircraft is physically at the gate, and can be configured for each day of the week.

Inputs: (1)

  • TurbineEvent to filter : The TurbineEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeTimeConfig: { 
	
	# The start time of the day in the format HH:mm:ss.
  start: string,
	# The end time of the day in the format HH:mm:ss.
  end: string,
}

Filter Event by Area Name

Filter events by comparing area name.

Metadata:

  • Name: FilterAreaTurbineEvent
  • Tags: filter, area, turbine event
  • Category: Filter
  • Subcategory: Area > Turbineevent

Description:

This node filters turbine events by area name, such as 'Gate-1' or 'Runway-2'. It is case-sensitive and must exactly match the area name to filter. If the area name matches the configured value, the node will output the turbine event. Area names can be configured for each area in the system.

Inputs: (1)

  • TurbineEvent to filter : The TurbineEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeAreaFilterConfig: { 
	
	# The case-sensitive area name to filter.
  value: string,
}

Filter Event by Concurrency

Compare multiple turbine events based on the timestamp to detect concurrency.

Metadata:

  • Name: FilterConcurrencyTurbineEvent
  • Tags: filter, concurrency, turbine event
  • Category: Filter
  • Subcategory: Timediff > Turbineevent

Description:

This node compares multiple turbine events from different sensors based on the timestamp to detect concurrency. It can be configured with a time window in milliseconds. If the time difference between two turbine events is less than the time window, the node will output a concurrency event.

Inputs: (1)

  • TurbineEvent to filter : The TurbineEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

ConcurrencyTurbineConfig: { 
	
	# The concurrency level of the TurbineSensor.
  concurrency: int32,
	# The time window in milliseconds to evaluate concurrency.
  timewindow: int32,
}

Filter Turbine Event by Probability

Filter events by probability value.

Metadata:

  • Name: FilterProbabilityTurbineEvent
  • Tags: filter, probability, turbine event
  • Category: Filter
  • Subcategory: Probability > Turbineevent

Description:

This node filters turbine events by a probability value between 0 and 1. The value represents the likelihood of the turbine event being correctly identified. If the probability of the turbine event is greater than the configured value, the node will output the turbine event. This node is useful for filtering turbine events based on the likelihood of accurate detection.

Inputs: (1)

  • TurbineEvent to filter : The TurbineEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeProbabilityConfig: { 
	
	# The probability threshold
  probability: int32,
}

Filter Event by Turbine Status

Filter events by turbine status such as running or stopped.

Metadata:

  • Name: FilterStatusTurbineEvent
  • Tags: filter, status, turbine event
  • Category: Filter
  • Subcategory: Status > Turbineevent

Description:

This node filters turbine events by turbine status, such as 'running' or 'stopped'. The status to filter can be configured, and if the status of the turbine event matches the configured value, the node will output the turbine event. This node is useful for filtering turbine events based on the operational status of the turbine.

Inputs: (1)

  • TurbineEvent to filter : The TurbineEvent to filter process and filter the data. if the condition is true, the data will be passed to the next node, otherwise it will be filtered.

Outputs: (2)

  • Rejected (Failed) : The condition is false and the data is filtered an labeled as failed without the reason. (value is higger than xy)
  • Accepted (Success) : The condition is true and the data is passed to the next node without modification.

Configuration:

The following configuration parameters can be set for this node:

NodeStatusFilterConfig: { 
	
	# The status to filter. Valid options are running, stopped, idle, or maintenance.
  value: string,
}

Random Turbine Event

Generate a random turbine event for testing purposes.

Metadata:

  • Name: RandomTurbineEvent
  • Tags: producer, random, turbine event, test
  • Category: Producer
  • Subcategory: Random > Turbineevent

Description:

This node generates a random turbine event for testing purposes only. The turbine event contains information such as the timestamp, sensor ID, turbine status, and other relevant data. This node is useful for testing other nodes that require a turbine event as input. The rate of generating random turbine events can be configured by the input trigger.

Inputs: (1)

  • Get TurbineEvent : Trigger to get TurbineEvent data

Outputs: (1)

  • TurbineEvent : Output for TurbineEvent data

Configuration:

The following configuration parameters can be set for this node:

RandomTurbineEventConfig: { 
	
	# The status of the turbine event, such as running, stopped, idle, or maintenance.
  turbine_status: string,
	# The unique identifier of the sensor.
  sensor_identifier: string,
	# The version of the sensor.
  sensor_version: string,
	# The probability or confidence level of the event being correctly identified.
  confidence: int32,
	# The type of the turbine, such as jet engine, turboprop, or turbofan.
  turbine_type: string,
	# The area where the turbine event took place.
  area: string,
}

Save Turbine Event

Save a turbine event in the database and output a success message.

Metadata:

  • Name: SaveTurbineEvent
  • Tags: save, database, event, sql
  • Category: Consumer
  • Subcategory: Database > Turbineevent

Description:

This node saves a turbine event in the database, containing details like timestamp, sensor ID, turbine status, and other relevant data. It's useful for event tracking, analysis, or auditing. The data is validated and stored in a SQLite database without any required configuration. On successful save, a success message is output. If the turbine event isn't in the correct TurbineEvent format, an error message will be output. The database used is SQLite, and no additional setup is needed.

Inputs: (1)

  • TurbineEvent to save : The TurbineEvent to save in the database or file.

Outputs: (1)

  • Is Success : Success

Configuration:

No configuration required for this node.

AI-based Turbine Detection

Detect turbine events using AI algorithms.

Metadata:

  • Name: TurbineDetection
  • Tags: producer, sensor, turbine event
  • Category: Producer
  • Subcategory: Hardware > Turbineevent

Description:

This node monitors turbines acoustically based on their sound using AI algorithms. It can be configured with a version, name, and path. The node will start the turbine detection process and output the turbine event.

Inputs: (1)

  • Get TurbineEvent : Trigger to get TurbineEvent data

Outputs: (1)

  • TurbineEvent : Output for TurbineEvent data

Configuration:

The following configuration parameters can be set for this node:

TurbineModelConfig: { 
	
	# The version of the turbine detection model.
  version: string,
	# The name of the turbine detection model.
  model: string,
	# The minimum confidence level required for turbine status identification.
  confidence: double,
	# The size of the model: small, medium, or large.
  size: string,
}

Report Turbine Event

Provide a pre-configured notification for a turbine event.

Metadata:

  • Name: TurbineEventNotification
  • Tags: notification, turbine event, frontend
  • Category: Notification
  • Subcategory: Frontend > Turbineevent

Description:

This node provides a pre-configured notification for a turbine event. You can configure the title, message, and level of the notification to be sent. This node is useful for sending notifications when a turbine event is detected to the User Interface or other systems.

Inputs: (1)

  • Trigger : The trigger of the notification.

Outputs: (1)

  • Notification : Output for Notification data

Configuration:

The following configuration parameters can be set for this node:

NotificationTurbineEventConfig: { 
	
	# The title of the notification.
  title: string,
	# The message content of the notification.
  message: string,
	# The severity level of the notification.
  level: string,
}

Turbine Sensor

Sensor that monitors turbines and creates turbine events.

Metadata:

  • Name: TurbineSensor
  • Tags: producer, sensor, turbine event
  • Category: Producer
  • Subcategory: Hardware > Turbineevent

Description:

This node monitors turbines acoustically based on their sound. It can be configured with a version, name, and path, and sends the turbine event to the next node. This node is useful in scenarios where detecting turbine operational status through sound is required, such as monitoring whether turbines are running or stopped. The TurbineSensor can be configured with a unique identifier, version, name, and path.

Inputs: (0)

Outputs: (1)

  • TurbineEvent : Output for TurbineEvent data

Configuration:

The following configuration parameters can be set for this node:

SensorConfig: { 
	
	# The unique identifier of the Sensor.
  sensor_serial: string,
	# The version of the Sensor.
  version: string,
	# The name of the Sensor.
  name: string,
	# The path of the Sensor.
  path: string,
}
Appendices