System - go to homepage
System logo

System

Basics

Trimble Precision SDK for Windows exists in different flavors:

  • TPSDK [version number], like TPSDK v3.6
  • TPSDK [year], like TPSDK 2018

TPSDK packages with the version number in the name are based on the legacy core component. TPSDK packages with the year in the name are based on the current core component.

The main difference is that the legacy version supports Windows CE/ Windows Mobile while the new version supports Windows Desktop only. Otherwise legacy uses more Microsoft technology compared to the current core component.



Using and updating TPSDK

Implementing and distributing the SDK typically consists of two steps:

  • Add references to your project or solution; these references contain the interfaces used in the project
  • Add the drivers which will be supported to the application installer

There is a 1:1 relationship between interface (references) and implementation (drivers). Therefore a developer must do both - update the references in a solution AND upldate the dynically loaded drivers.

An update always consists of both reference and driver updates.

Also note that within the Drivers folder two folder x86 and x64 with native files exists. Please do NOT relocate these folders; this contain native files and are expected relative to the main driver counterpart.



Microsoft Visual Studio and .NET versions

TPSDK can be used with any Microsoft Visual Studio starting with version 2008.

  • TPSDK legacy target .NET v3.5
  • TPSDK current targets .NET v4.0

If a developer wishes to develop for Windows CE/ Windows Mobile he must use Visual Studio 2008 SP1 as this is the last version supporting Microsoft’s Mobile compilers.

  • TPSDK legacy gets build with Visual Studio 2008 SP1 and its corresponding compilers.
  • TPSDK current gets build with Visual Studio 2017 and its corresponding compilers.


VCRedist packages

TPSDK uses a mix of languages - mainly C++ and C#.

While C# requires the .NET runtime the C++ components need the corresponding system dlls (known as VCRedist).

For that purpose the TIM installer also copies a set of vcredist installers to the development machine. Those installers must be installed on the target machine in order to run TPSDK. Missing a VCRedist packages typically results in weird errors while loading the driver.



More sample applications

Each component within TPSDK has its own sample application. Those sample apps - like the SSI sample app - are typically exercising the interface 1:1. Interface samples are great for finding functionality in a component. On the other side they are in some cases hard to follow while implementing workflows.

For that reason Trimble offers a set of sample applications which mimic the workflow of an application. Those samples are shared on request as they would otherwise be an overkill for any developer. If you are looking for a sample application specific to a domain please reach out to Trimble via the known channels.

An exception to the list above is the main sample - which combines SSI, CSI and SIL in a single application focusing on Vision control.