Diagnosys Test Result Server helps drive workshop efficiencies through automatic test data logging and the transfer and storing of test result data so that it can be analyzed and interrogated independent of hardware platforms.

Diagnosys Test Result Server

The Test Result Server (TRS) is a self-contained software package that is created and supported by Diagnosys.

It provides an ‘open’ interface on which Diagnosys and third party systems can communicate such that test data information can be made available and transferred bi-directionally between test systems, re-work stations and analysis stations.

FaLang translation system by Faboba

Test Result Server consists of

1 TRS software and license

2 Dedicated Test data Server

Note: TRS requires a networked environment within the workshops in order to be fully implemented.

Need some information?

Please contact us for a no obligation discussion on Diagnosys Products:

Need some information?

Please contact us for a no obligation discussion on Diagnosys Products:

Technical Information

Transferring & Store

It provides a way of transferring and storing test result data between systems that is platform independent e.g. S500 – PinPoint – 3rd party. The diagram shows a typical implementation.

Third party systems

The Test Result Server (TRS) provides an interface that third party systems can communicate such that test data and diagnostic information can be freely available and transferred bi-directionally between systems.

Two main software blocks

TRS is implemented with two main software blocks. The TRS itself is a 32 bit windows service that can be installed on any Windows™ computer. Clients communicate with TRS via the supplied 32-bit Windows™ Dynamic Link Library (TRLClient.DLL), Static library (TRLClient.LIB) and header file (TRLClient.H). These files allow integration into your, or 3rd party, test executive software.

Repository for client-generated Result Data Blocks


TRS is effectively a repository for client-generated Result Data Blocks (RDB). TRLClient manages all communication to the TRS, compilation of the RDB and handles Tag records created by the Test Executive during a test run. Functions are provided for 3rd party software to interact with RDB for recording and extraction of data.

Each record, called a Tag, consists of two parts. The first part is the header that contains a unique Tag ID code and payload size data. The second part consists of the payload zone that can contain user-supplied data up to 2Gb in length.

TRS comes with some predefined Tag ID codes (Operator name, Test Time, Serial number, etc.) which can be extended by creating your own codes so that the RDB can be used to store literally any data needed, for example process tracking information.