Sometimes a user wants to distribute an application, which has been written using one of the I2C APIs, to other users. Therefore it is necessary to redistribute the infrastructure to these users, which is needed to communicate with the I2C boards from telos.
The easiest way is to simply redistribute the complete I2C Studio package. telos offers a Merge Module, which allows to integrate the complete I2C Studio installation into the user’s own setup package. As disk space is no longer an issue these days, this is the recommended way. It makes support for all parties a lot easier.
If the redistribution of the complete I2C Studio is not the desired solution, it is possible to include only the really needed files into the user’s own setup package. telos does not offer any support for such setups.
Normally three components are needed: the driver, the I2C scheduler, and the API itself.
The driver can be found in the installation directory:
If the tools, which are used to create the setup package, do not support the installation of drivers by themselves, telos recommends to use the Driver Install Frameworks (DIFx) from Microsoft, which is part of the WDK.
The I2C Scheduler is located in the following executable:
<install dir>\bin\tracii scheduler.exe
This executable must be registered as Windows Service during the installation of the setup package. Before a setup package gets deinstalled the Windows Service must be deregistered.
The I2C scheduler offers some command line options to register and deregister itself:
tracii_scheduler.exe <option> /install_2000 register the I2C scheduler (>= Win2k) /remove_2000 deregister the I2C scheduler (>= Win2k)
After a successful registration the I2C Scheduler can be found in the Services dialog of the Administrative Tools.
Depending on the used API different files must be included into the user?s own setup package.
The I2C.C API is located in the following file:
<windows dir>\i2capi c.dll
As the I2C.C++ API gets linked statically to the user?s application, no additional files must be included into the setup package.
The I2C.NET API can be found in the following directory:
There are two subdirectories, which contain the 32-bit and the 64-bit versions of the I2C.NET assembly. The interface of both assemblies is compatible.
For the I2C.Labview API some more files are needed. At first two .NET assemblies are needed: the I2C.NET API and i2capi dotnet labview.dll. The second assembly can be found in the Assembly Cache of Windows, which can be accessed using the following virtual directory:
In addition to these assemblies it is necessary to add all used I2C VIs to the setup package. These VIs can be found in the following directory:
The VIs support Labview starting with version 8.2.