Create and Manage Remote Connections

In remote scenarios, the communication partners – for example the application and the VCI on the vehicle – must be able to recognize each other and establish a connection. It is also essential that the software and data records are up to date. Both can be easily provided by Softing as a server or cloud-based application.


  • Responsible for development fleets
  • Managers of distributed test setups
  • Production planning managers
  • Developers of remote-capable diagnostic and flash applications
  • Developers of test applications in development and production
  • Developers of after-sales solutions


  • Configuration: Registration of users (user/tools)
  • Configuration: Registration of user rights (in planning)
  • Configuration: Registration of vehicle interfaces (devices) 
  • Device API: Login to the broker and status message
  • Tool API: Query of possible vehicle interfaces
  • Tool API: Connection to vehicle interface


Finding authorized communication partners

Previous diagnostics were simple: one tool connects to one VCI. In remote use cases, however, various users have to find the right communication partner (the device) with their tool, for example a Softing VCI via D-PDU API or a Softing SDE, which can be installed on a VCI, a test computer or in the vehicle. Only devices that are in a state that allows communication may be accessed.

User rights

Access to devices is usually restricted. For example, not every user of a development tester is allowed to access every device under test from different series. It is therefore necessary to regulate who has access to which device. This function is currently under development. On request, Softing provides an application with a list of the devices it is allowed to access. Status information also shows whether the device is in a connectable state or is currently busy elsewhere - for example, because diagnostics are not permitted due to the driving status or because another application has blocked the device.

Types of connection

The broker informs an application about accessible devices and their status. Recognition can then take place e.g., via the IP address, the name of the device or the VIN (Vehicle Identification Number). The connection is possible in several ways: via the broker itself, which manages the connections of the communication partners in gateway mode, or in independent mode, in which a direct connection is established between tools and device based on the connection information.

Possible Applications

Remote use cases exist throughout the entire product life cycle. From 1:1 connections via the connection of one tool with many devices, to connections of many tools with one test object may be necessary. Generalization with m tools that need to communicate with n devices is also a common use case. All of these can be covered with the help of Softing

Test appliction in production 

In the production line, the vehicles currently available in the assembly line are regularly checked at dedicated points, taking into account their production status, or software is programmed into the vehicle. To perform this, the tool requests the IP address of the device from the broker and can then execute the corresponding routines on the vehicle known via the vehicle identification. The combination of vehicle identification and IP address is usually stored in the logistics system when the device is connected to the vehicle. 

Diagnostic developer with prototype vehicles

Only a limited number of prototype vehicles are available, but all ECU managers must still be able to carry out their tests. The Softing makes this possible right from the office, as tests can be carried out on an available vehicle at any time. The status is always available so that the tester can easily recognize whether a vehicle is in a diagnosable state and whether it is currently occupied by another tester.