Using the µVision Socket Interface: Client Interface (UVSC)

| Using the µVision Socket Interface Application Note 198 Control and monitor µVision via the built-in TCP/IP interface

- Main Page
- Usage and Description
- Reference

All Data Structures Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
Client Interface (UVSC)

The Client Interface (UVSC) simplifies the use of UVSOCK. Developers do not have to care about the TCP/IP interface or deal with the asynchronous nature of UVSOCK. UVSC is implemented as a DLL for 32-bit and 64-bit operating systems (UVSC.dll, UVSC64.dll), providing a C-API for accessing UVSOCK features. The DLL can be loaded into an application using the normal Windows methods and can be programmed in any language that is capable of using a DLL interface. All API element names start with UVSC_ and are described in UVSC Client Interface (UVSC_C.h). The high-level API functions are grouped in Client Functions.

- The starting function for a Client is UVSC_Init to initialize the interface.
- Call UVSC_OpenConnection with the required TCP socket port to establish a connection to uVision. You must Enable UVSOCK in uVision and define a callback function to enable UVSOCK Messaging.
- The #define UVSC_MAX_CLIENTS sets the maximum concurrent client connections.

## Recommended settings:

- Installing the UVSC-DLLs into the folder C:\Keil_v5\UV4 ensures compatibility with future uVision versions. (C:\Keil_v5 is the root folder of your uVision installation. Can differ in older versions or for your installation. UV4 is the installation folder of the uVision executable. Can be UV3 in older versions.)
- The DLL does not have to be included in the distributed application, unless the application should be used with a specific version of the development tools.

The application note provides an example program UVSC-Tester which can be used as a start for your client or for a better understanding of the interface.