Automotive

Category: Blog Automotive

Diagnostics and Security: Brave new world

Diagnostics and Security: Gateways for hackers and how to close them – As long as diagnostics takes place locally, in other words using a cable connection between the diagnostic tester and the diagnostic interface or the vehicle, it is safe to assume that the diagnostic system is basically secure as far as unauthorized access is concerned. But the picture changes as soon as there is a remote data connection over the Internet.

NEW: Softing TDX Release 2.2 Enables the Dynamic Loading & Supplementing of Diagnostic Projects

Softing TDX Release 2.2 Enables the Dynamic Loading & Supplementing of Diagnostic Projects

A frequent challenge for diagnostics in the field, particularly in the machine environment, is that the ECU configuration of the machine is not known in advance and that a diagnostic project may have to be adapted or supplemented dynamically during runtime. With the new version 2.2. of the repair shop tool Softing TDX, it is possible to load and even supplement diagnostic projects dynamically, depending on the machine configuration.

Biggest Possible Development Efficiency with Remote Engineering

Article in ATZelectronics 10/2019: Biggest Possible Development Efficiency with Remote Engineering

Development projects are increasingly being handled by teams whose members are spread all over the world. Remote Engineering allows efficient networking of global work capacities. However, there are a number of aspects that need to be considered during implementation to ensure a smooth process.

Cybersecurity: Protecting a cyber-physical remote diganostic communication system against cyberattacks

Article on Cybersecurity

The wireless and remote connection between a diagnostic tester and a fleet of vehicles can be considered a technical masterpiece, but only if new challenges such as closing security gaps are mastered. The article analyzes the components of the cyber-physical system (CPS) for remote diagnostic communication and provides measures to improve the resilience against cyberattacks.

Moving Forward into the Future - Diagnostics in Global Engineering Teams

Diagnostics in Global Engineering Teams

The automoive industry is facing major challenges due to the complexity of electric and autonomous vehicles of the future. As a result, work is taking place on global teams, resulting in turn in massive changes in both engineering and the tool landscape used.

Tracking Down Errors: The Perfect Diagnostic Tool in Vehicle Engineering – Whatever the Application Case

Article in "OEM&Lieferant": Tracking Down Errors - The Perfect Diagnostic Tool in Vehicle Engineering

Vehicle engineering is facing a range of challenges. This is why today manufacturers and their suppliers work together at a global level at which they need to be able to exchange data safely all over the world. The range of vehicles is constantly diversifying while the engineering cycles are becoming ever shorter. Vehicles must be maintained over the entire product life cycle which means that more and more tasks have to be completed in an ever shorter time.

SAVE THE DATE – ELIV Congress 2019

Visit Softing at the ELIV Congress 2019!

Meet us at the international congress for automotive electronics ELIV on October 16-17, 2019 in Bonn, Germany. In the fast-paced automotive market, it is of greater importance than ever before for OEMs and suppliers to have transparency when it comes to quality and reliability in all their often globally distributed process sequences. At ELIV (electronics in vehicles) congress in Bonn, Germany we will show you the support we can provide with our innovative and flexible diagnostic and test solutions.

ECU Quicktest – Identfying and testing errors with documentation with Softing DTS.monaco

Softing DTS.monaco: Identifing and testing errors with documentation

The identification of a test unit as well as the reading out of the error memory are activities which are repeated throughout the product life cycle. Regardless of whether HiL, test bench or vehicle – the versions as well as any error memory entries which might occur must be acquired and documented in every test sequence.

«