One-click Integrations with Flinks

Introduction to Flinks

‍

Flinks, short for FlytBase Links, are connectors that enable one-click integrations between FlytBase and external apps, devices, or modules. This section provides an overview of various Flinks and their roles in enhancing drone operations.

‍

Flinks (FlytBase Links): Connectors for easy integration between FlytBase and external systems.

‍

Critical Components for Drone Autonomy

‍

1. Drones and Docking Stations: Enable continuous, unsupervised operations with automatic battery refueling.
2. Flight Operations Software: Essential for automating tasks like site security, asset inspection, and emergency response.
3. Specialized Payloads: Include mapping sensors, gas detection equipment, and more.
4. Detect and Avoid Technology: Ensures safety and regulatory compliance in airspace.
5. UTMs (Unmanned Traffic Management Systems): Provide real-time airspace awareness for BVLOS operations.
6. Parachutes: Enhance safety for flights over people and BVLOS.
7. Data: Data Processing: Converts vast amounts of drone-captured data into actionable insights.

‍

Platform vs. Application

This section explains the difference between a platform and an application, emphasizing the importance of a platform approach in integrating docked drones into enterprise systems for enhanced operational efficiency.

‍

1. Platform: Comprehensive infrastructure supporting various hardware and software applications (e.g., Android, AWS, FlytBase).
2. Application: Software performing specific tasks for end-users (e.g., Microsoft Word, DJI Flight Hub 2).

‍

Why a Platform Approach is better: 

1. Integrates docked drones into enterprise systems.
2. Enables real-time data sharing and automated workflows.
3. Facilitates seamless integration into IT and communication frameworks.

‍

Use Case: Security and Surveillance

This section explores how Flinks can enable autonomous drone operations in security and surveillance, addressing key questions and requirements enterprises may have.

‍

Key Questions for Automating Security Operations:

• How to integrate alarm systems for immediate drone response?
• How to get real-time video feeds into VMS?
• How to automate patrols and detect/report vehicles and people using AI?
• How to ensure drones avoid other aircraft?
• How to generate detailed mission reports and manage resources?

‍

Flinks Solutions:

1. Alarms Flink: Immediate drone response to incidents.
2. Live Streaming Flink: Real-time monitoring and AI detection.
3. Detect and Avoid Flink: Ensures safety in airspace.
4. Mission & Logs Flink: Generates reports and manages data.

‍

Benefits of Flinks

This section highlights the advantages of using Flinks, emphasizing how they streamline and automate drone operations, making integration easier and reducing manual errors.

‍

1. Centralized Hub: Connects FlytBase with various tools, automating workflows.
2. Ease of Integration: Simplifies processes, reducing manual errors and enhancing efficiency.

‍

Introduction

In this lesson, we'll cover the following key topics:

• Adding a Flink: How to create and customize Flinks on the Flightbase platform.
• Integrating Your Alarm System Using Webhooks: Securing and setting up your alarm systems to work seamlessly with Flightbase.
• Testing the Alarm Source: Verifying that your alarm sources are functioning correctly.

Developer Settings

1. Understanding Flinks
   • Flinks (Flightbase Links) enable the connection and automation of workflows between Flightbase and third-party applications/sensors using webhooks.
2. Alarm System Basics
   • Example: Sensor detects a fire, triggering an alert on Flightbase via webhooks.
   • Response Options: Handle manually or create an automation (details in the next video).
3. Securing Your Webhooks
   • Use a client ID, client secret, and access token for security.
   • Generating an Access Token:
     • Go to the settings panel (top right) and click on "Developer Settings."
     • Credentials are organization-specific.
     • Token Validity: Choose between lifetime or 15 minutes (recommended for security).
     • Steps:
       • Integrate the client ID and client secret using Base64 encoding.
       • Set token validity to 15 minutes.
       • Click "Fetch Token" to generate the access token.
     • Use the access token as an authorization header in every REST API call.
   • Need Help? Contact support at support.flightbase.com.

Adding a Flink and Alarm Sources

1. Adding a Flink
   • Navigate to the "Flinks" drawer from the hamburger menu on the left.
   • Click on "Add Custom Flink" and then "Next."
   • Provide a suitable name (e.g., "downtown south") and description (e.g., "accident prone area inspection").
   • Optionally, add a customized icon by clicking "Browse" and selecting your icon.
   • Click "Add" to complete the process.
2. Adding Alarm Sources
   • Select your Flink card and go to the "Alarm Sources" tab.
   • Click on "Add Source" and provide a name and description for the alarm source.
   • Click "Generate URL" to create a URL for your webhook and alarm payload JSON.
   • Use the generated URL to integrate your alarm source and trigger alarms on the Flightbase dashboard.
   • Ensure the source is active by triggering the webhook at least once every 30 seconds (found in the "Heartbeat" tab).

Testing the Alarm Source

• Testing Functionality
  • On the dashboard, press the "Test" button to trigger an alarm in the right panel.
  • This confirms the alarm source is functioning correctly.
  • Note: This test will not initiate any linked automation; it's solely for verification.

Conclusion

• Recap: You've learned how to add, integrate, and test your workflows on Flightbase.
• Next Steps: Check out the next video to learn about automating your workflows.

‍

Introduction

In this video, we have focused on creating and managing automated workflows for alarm responses.

1. Pre-requisite
   • Ensure you have already created an alarm source.
2. Accessing Automations
   • Navigate to the automations drawer in the top left corner of your dashboard.
   • Click on "Create" and then "Next."
3. Naming Your Automation
   • Provide a suitable name for your automation flow (e.g., "Downsouth Fire Inspection").
4. Selecting Alarm Source and Action
   • Choose your alarm source.
   • Select the action for the drone to perform in response to the trigger:
     • Go to Location: The drone navigates to a specified location.
     • Perform Mission: The drone executes a predefined mission.
5. Choosing the Response Mode
   • Manual Response: Operator takes control of the alarm response, no automatic launch.
   • Automated Response: The drone is automatically launched without operator intervention.
6. Assigning a Site
   • Assign the site where this automation will be active.
7. Selecting the Device
   • Choose the device at the moment the alarm is raised or select it now from your list of devices.
8. Setting Flight Parameters (for Go to Location)
   • Define flight parameters such as altitude and speed.
9. Selecting a Mission (for Perform Mission)
   • Pick a mission from your list, noting that only missions part of the assigned site can be selected.
10. Finalizing Automation
    • Click on the "Create" button to complete the setup of your automation flow.

Review and Management

• Automation Logs: All actions triggered by an alarm are logged in the panel for future review and analysis.

‍

• Prerequisites:
  • Completed lessons on creating, testing, and integrating Flinks.
  • Lessons on creating automations using alarm sources.
  • Access to Postman or any HTTP request application.

Getting Started

• Developer Settings:
  • Navigate to the developer settings to get the Client ID and Client Secret.
  • Only Admins and the Organization Owner can access these settings.
• Security Protocols:
  • FlytBase uses token-based authentication for security.
  • Token-based authentication is secure, encrypted, signed, and can be revoked.

Generating Credentials

• Steps:
  • Click on Generate Credentials.
  • Receive your Client ID and Client Secret.
  • Store them securely and optionally regenerate your Client Secret.
• Token Validity:
  • Fetch an access token with a chosen validity (recommended 15 mins for security).
  • Fetch the token via the FlytBase dashboard or an API call.
• Using Postman to Generate Token:
  • Create a new collection and add a request.
  • Use the URL in Developer Settings for generating the token with a GET call.
  • Under Params, enter the token expiry (long or short validity).
  • Under Authorization, select Basic Auth and enter Client ID as Username and Client Secret as Password.
  • Click Send to receive your token.

Setting Up Heartbeat and Trigger APIs

• Heartbeat API:
  • Create a new request for Heartbeat API.
  • Use the Webhook URL for Heartbeat and set the API call type to POST.
  • Under Body, select RAW and set the body type to JSON.
  • Under Authorization, input the bearer token.
  • Click Send and verify the response.
• Trigger Alarm API:
  • Create a new request and input the Trigger Webhook URL.
  • Under Authorization, enter the bearer token.
  • Input the JSON Body with alert details (timestamp, severity, description, latitude, longitude, altitude, metadata).
  • Click Send to trigger the alarm and verify on the FlytBase dashboard.

Conclusion

• Verification:
  • Check the FlytBase dashboard for the alert and respond to it.

‍

Workflow

‍

1: Plan and Execute a Grid Mission

Tool: FlytBase dashboard.

Task: Conduct a mapping mission using the Grid Mission.

Ref:https://docs.flytbase.com/pre-flight-modules/planning/mission-planning/grid-mission

‍

2: Post-Flight Data Handling

After Landing: Aerial data uploads to private cloud storage if set up.

‍

3: Monitor Image Uploads

Location: Flight logs on FlytBase dashboard.

Process: Images upload to the cloud after the drone lands.

‍

4: Sync Data with DroneDeploy

Action: Go to the "Media" section.

Button: Click "Sync to DroneDeploy".

Outcome: Upload and process images to create an orthomosaic and 3D map.

‍

5: Processing Time

Variable- The time varies based on the quality of images and the area covered.

‍

6: Access Processed Data

Status: Media section will show "Synced".

Button: Click "Go to DroneDeploy" to view outputs.

Alternative: Use DroneDeploy Flink on the dashboard to log in and view outputs.

‍

Summary

FlytBase Data processing Flinks streamline data processing.

Efficient Workflow: Easy monitoring and syncing post-flight.

Output Creation: Generate orthomosaics and 3D maps directly through FlytBase.

Additional Resources

https://docs.flytbase.com/flinks-and-automation/flinks

‍

Introduction to Live Streaming Flink

‍

The Live Streaming Flink connects drone and dock video feeds to your Video Management System (VMS), enhancing site security and threat detection by integrating aerial and dock surveillance with existing CCTV systems.

‍

• Purpose: Expands security coverage by integrating drone and dock feeds with existing CCTV cameras.
• Benefits:some text
  • Real-time aerial surveillance for a broader view.
  • Improved situational awareness.
  • Enhanced threat detection and rapid response times.
  • Addressing surveillance blind spots.

‍

Prerequisites for Integration

‍

Before integrating live video feeds into the VMS, certain hardware and software requirements must be met.

‍

Hardware Requirements:

‍

1. DJI Matrice 30, Matrice 30T, Matrice 3D, Matrice 3TD
2. DJI Dock 1 or DJI Dock 2

‍

Software Requirements:

‍

1. Enable Live Streaming Flink via FlytBase support.
2. Necessary credentials and access rights for Milestone VMS.
3. Topic: RTSP Video Stream Integration

‍

RTSP Video Stream Integration

‍

RTSP streams provide high-quality, real-time video capabilities essential for security and surveillance.

‍

• RTSP URL Format for DJI Dock 1:some text
  • Specific formats for M30 and M30T models.
  • Replace <device_id> with the drone's unique device ID, found under the maintenance tab of the FlytBase dashboard.
• RTSP URL Format for DJI Matrice 3D and Matrice 3TD:

Use the correct URL format based on the drone model.

Locate the device ID on the device management page of the FlytBase dashboard.

‍

Video Feed Behavior and VMS Integration

Understanding the behavior of the video feed and ensuring seamless integration into the VMS.

‍

1. Feed Activation:some text
   1. Ensure drones are online, operational, and connected to the network.
   2. Live video feed becomes visible in the VMS when drones are active.

‍

2. Real-Time Video Changes:some text
   1. Instant reflection of video mode changes (e.g., RGB to thermal imaging) from the FlytBase dashboard to the VMS.
   2. Operators and security personnel view the same detailed visual information.
3. Dynamic Adaptability:some text
   1. Enhances situational awareness and operational efficiency by providing immediate updates to the monitoring team.

Summary

‍

Live Streaming Flink: Enhances security operations by integrating drone and dock video feeds with Milestone VMS.

Integration Process: Requires specific hardware, software, and RTSP URL configurations.

Operational Benefits: Real-time monitoring, rapid threat detection, and improved situational awareness.

‍