LogoLogo
  • Solution Overview
    • PLC Management and Code Versioning platform
    • Basic terminology
    • Supported automation vendors
  • Project versioning
    • How to upload and manage projects
    • How to use the Windows local client
    • How to view projects incl. changes
  • AI Generated Code Documentation
    • Overview
    • How to generate a documentation
  • Connectivity Service
    • Overview
    • Requirements
    • How to set up a Gateway
    • Configuring Proxy
    • Configuring networks
    • FAQ
  • Browser Based Engineering
    • Working with Browser Based Engineering
    • Up- and download of TIA licenses for Browser Based Engineering
    • Troubleshooting
  • Automated backup
    • Configuring automated PLC backups
  • Automated deployment
    • Directly deploying your projects
    • Deployment Requests (preview)
      • Actions with 2 Factor Authentication (preview)
  • Console administration
    • Creating an account
    • SSO via Azure Active Directory
    • Deleting an account
    • Inviting console users
    • Receiving a console invite
    • Understanding permissions
    • Managing permissions
    • Choosing a subscription plan
    • Viewing bills, downloading invoices, and managing payment methods
  • Examples
    • Quick Start Guide
    • Preparing a Raspberry Pi to be used as a Gateway
  • FAQ
    • Deployment
    • IDEaaS
Powered by GitBook
On this page
  • Solution architecture
  • How it works
  1. Connectivity Service

Overview

PreviousHow to generate a documentationNextRequirements

Last updated 4 months ago

Version 2 of the connectivity service was published to expand the capabilities of SDA's remote services. For instance, it enables remote connectivity to Beckhoff PLCs and enables to use the latest encryption features when remotely connecting to Siemens PLCs.

Version 2 of the connectivity service is currently in private preview. Please get in touch with SDA if you want access to this service.

Solution architecture

The SDA connectivity service is based on a local edge device on which the SDA connectivity client is installed. This device needs to be placed in the on premise customer network and it needs to be able to communicate with the automation devices (e.g., PLCs) which the customer wants to access via the SDA platform. The device can be an existing device that fulfils the .

How it works

Version 2 of the connectivity service uses MQTT for base communication between the gateways and the SDA cloud. To access the OT devices on request a customised Wireguard VPN tunnel running on TCP port 443 (https) is opened temporarily. Wireguard uses the state-of-the-art ChaCha20 encryption method (see also ).

https://www.wireguard.com/protocol/
hardware and software requirements
Connectivity v2 Overview