cifx Device Driver Driver Manual cifx Device Driver under CeWin V Hilscher Gesellschaft für Systemautomation mbh

Transcription

1 Driver Manual cifx Device Driver cifx Device Driver under CeWin V Hilscher Gesellschaft für Systemautomation mbh DOC110502DRV02EN Revision 2 English Released Public

2 Introduction 2/29 Table of Contents 1 Introduction List of Revisions Terms, Abbreviations and Definitions References to Documents Legal Notes Copyright Important Notes Exclusion of Liability Export Windows CE Driver Overview Requirements Features Limitations Content General Information about Windows CE Driver Getting Started Setting-up the CeWin Platform Install CeWin Hardware Preparation Assigning the Hardware Configure the CeWin Platform OS.config General.config cifxpci_pcie.config / NXSB-PCA-PCI.config Running CeWin CifX CE Drv Compiling the Source Code Driver installation Registry Settings Loading the Driver Demo Application Build Debug an Application Appendix List of Tables List of Figures Contacts...29

3 Introduction 3/29 1 Introduction CeWin is a real-time extension the Microsoft Windows operating system XP, offered by the company ACONTIS. This document describes the integration of the cifx CE Device Driver in CeWin. The document is based on the standard cifx CE Device Driver documentation and is understood as an add-on to the CeWin specific installation procedure. For general information about using drivers under Windows CE and the Hilscher cifx Device Driver for CE please refer to the Microsoft CE documentation and the cifx Device Driver - Windows CE DRV 2 EN.pdf from Hilscher. 1.1 List of Revisions Rev Date Name Chapter Revision SD all Created SD Update reworked (links, driver update) Table 1: List of Revisions 1.2 Terms, Abbreviations and Definitions Term Description CeWin CeWin cifx Communication Interface based on netx PCI Peripheral Component Interconnect DLL Dynamic Link Library DPM Dual-Port Memory Physical interface to all communication board (DPM is also used for PROFIBUS-DP Master). Table 2: Terms, Abbreviations and Definitions 1.3 References to Documents This document refers to the following documents: [1] Hilscher Gesellschaft für Systemautomation mbh: Driver Manual, Windows CE 5.0/6.0, V , Revision 2, english, [2] ACONTIS: CeWin. [3] ACONTIOS: RtosVM-UserManual. Table 3: References to Documents

4 Introduction 4/ Legal Notes Copyright Hilscher Gesellschaft für Systemautomation mbh All rights reserved. The images, photographs and texts in the accompanying material (user manual, accompanying texts, documentation, etc.) are protected by German and international copyright law as well as international trade and protection provisions. You are not authorized to duplicate these in whole or in part using technical or mechanical methods (printing, photocopying or other methods), to manipulate or transfer using electronic systems without prior written consent. You are not permitted to make changes to copyright notices, markings, trademarks or ownership declarations. The included diagrams do not take the patent situation into account. The company names and product descriptions included in this document may be trademarks or brands of the respective owners and may be trademarked or patented. Any form of further use requires the explicit consent of the respective rights owner Important Notes The user manual, accompanying texts and the documentation were created for the use of the products by qualified experts, however, errors cannot be ruled out. For this reason, no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed. Descriptions, accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature. It cannot be ruled out that the user manual, the accompanying texts and the documentation do not correspond exactly to the described features, standards or other data of the delivered product. No warranty or guarantee regarding the correctness or accuracy of the information is assumed. We reserve the right to change our products and their specification as well as related user manuals, accompanying texts and documentation at all times and without advance notice, without obligation to report the change. Changes will be included in future manuals and do not constitute any obligations. There is no entitlement to revisions of delivered documents. The manual delivered with the product applies. Hilscher Gesellschaft für Systemautomation mbh is not liable under any circumstances for direct, indirect, incidental or follow-on damage or loss of earnings resulting from the use of the information contained in this publication.

5 Introduction 5/ Exclusion of Liability The software was produced and tested with utmost care by Hilscher Gesellschaft für Systemautomation mbh and is made available as is. No warranty can be assumed for the performance and flawlessness of the software for all usage conditions and cases and for the results produced when utilized by the user. Liability for any damages that may result from the use of the hardware or software or related documents, is limited to cases of intent or grossly negligent violation of significant contractual obligations. Indemnity claims for the violation of significant contractual obligations are limited to damages that are foreseeable and typical for this type of contract. It is strictly prohibited to use the software in the following areas:! for military purposes or in weapon systems;! for the design, construction, maintenance or operation of nuclear facilities;! in air traffic control systems, air traffic or air traffic communication systems;! in life support systems;! in systems in which failures in the software could lead to personal injury or injuries leading to death. We inform you that the software was not developed for use in dangerous environments requiring fail-proof control mechanisms. Use of the software in such an environment occurs at your own risk. No liability is assumed for damages or losses due to unauthorized use Export The delivered product (including the technical data) is subject to export or import laws as well as the associated regulations of different counters, in particular those of Germany and the USA. The software may not be exported to countries where this is prohibited by the United States Export Administration Act and its additional provisions. You are obligated to comply with the regulations at your personal responsibility. We wish to inform you that you may require permission from state authorities to export, re-export or import the product.

6 Windows CE Driver 6/29 2 Windows CE Driver ATTENTION: The Windows CE driver comes as source code with a demo project. Because of the hardware options of Windows CE, the driver will not be delivered as a pre-compiled run-able driver module. The driver source must be compiled for the specific platform it is used on. 2.1 Overview! The cifx Device Driver for Windows CE is a stream driver, running in the kernel of the operating system.! Access to the driver functions is offered by a driver API DLL (cifxcedll). The DLL covers the device IO control calls used to communicate with the driver and offers the same CIFX API like on the Windows desktop operating systems. Figure 1: CifX CE Driver - Architecture

7 Windows CE Driver 7/ Requirements! Hilscher NXDRV-CE for Windows CE 6 V or later! CeWin Either CeWin 4.1 SDK for Windows CE6.0 and / or CeWin 4.1 display based SDK for Windows CE6.0! Development environment: Microsoft Visual Studio 2005 (Platformbuilder Add-On for Windows CE Remote Tools) + Service Pack Features! see Hilscher NXDRV-CE for Windows CE 6 V or later 2.4 Limitations! see Hilscher NXDRV-CE for Windows CE 6 V or later! Tested and developed for CeWin (WinCE6.0)! When DMA is enabled the extended memory might not be available.

8 Windows CE Driver 8/ Content The following table shows the CeWin folder structure located in /Driver/CE6/. The folder contains all required configuration files and also a demo application. Folder CeWin Documentation Application CifXTest_Console Configuration Config INF LoadCifXdrv Table 4: CeWin Content Content CeWin Add-On (required configuration files and examples) This document Example application Example application (especially for CeWin) CeWin platform configuration files CeWin platform configuration files (integrating cifx device) required installation files for cifx hardware Helper Application (Loading the driver at system startup) The driver itself is placed in /Driver/CE6/VS2005/. The contained solution file (/Driver/CE6/VS2005/cifXCEDriver.sln) provides projects for the CeWin platforms (headless/display based). Further demo applications are located in /Driver/CE6/Applications/. The corresponding solution file contains also projects for the CeWin platform. Before building the applications please consult the appropriate documentation (section Demo Application on page 25).

9 Windows CE Driver 9/ General Information about Windows CE Driver The Windows CE driver comes as source code with a demo project. Because of the hardware options of Windows CE, the driver will not be delivered as a pre-compiled run-able driver module. The driver source must be compiled for the specific platform it is used on. There is no difference between the cifx driver source used for the CeWin platform and other CE systems. For further CE specific information refer to the standard cifx Device Driver -Windows CE DRV 02.pdf document. This contains general information about the cifx CE Driver and also detailed information about the CE registry settings. This description contains only information how integrate the cifx CE Driver in an already build image of CE 6.0. Therefore it only focuses the specific installation and configuration. For a complete description of all aspects of CeWin consult the original ACONTIS manuals (References [2], [3]).

10 Getting Started 10/29 3 Getting Started 3.1 Setting-up the CeWin Platform Install CeWin In case of already installed system this section can be skipped. After running the setup of the CeWin platform the installation wizard will guide you through the installation. The delivered configuration files (/Cewin/Configuration/Config/) are specified for a Single PC development. This means the target system CeWin and the development system running concurrently on one CPU core. During installation a wizard will ask for the preferred setup type. In case of using other installation types the delivered config files need to be adapted Figure 2 shows which type of setup needs to be chosen. Figure 2: CeWin Setup The remaining installation process is self explaining and not described in this document.

11 Getting Started 11/ Hardware Preparation The hardware preparation is explained using a cifx PCI device. Required hardware components:! cifx PCI Device After installation of CeWin the cifx PCI card needs to be assigned to the CeWin system. Intending to use the cifx device in interrupt mode it is important to make sure that the interrupt of the PCI hardware is not shared with other devices. Thus it is necessary to examine the hardware connections before setting up the hardware Interrupt handling of PCI hardware under CeWin expects to use none shared interrupts This can be checked by using the Windows device manager, clicking on View > Resources by Connection. Figure 3: Device Manager

12 Getting Started 12/29 After this step the expanded view of the category IRQ, shows all devices and which interrupt line they are assigned to. Figure 4: Device Manager Connections Figure 4 shows that the cifx PCI card is connected to a single interrupt line (18), therefore it is possible to install the cifx PCI card with interrupt support (no interrupt sharing available). The PCI devices chosen to be assigned to CeWin can not share interrupts with devices installed under Windows XP. One solution is to disable all unused devices on Windows XP to get a free, unshared interrupt or to disable interrupt support of the RTOS (CeWin) device. For further information see reference [3]. In case the PCI device uses a shared interrupt, the PCI hardware needs to be installed as a device using polling mode. The following section explains how to install the cifx PCI card for polling or interrupt mode.

13 Getting Started 13/ Assigning the Hardware Assigning the cifx PCI hardware device to the CeWin platform, can be done by reinstalling the device and choosing a special RTOS INF file. The needed RTOS INF files are located in /CeWin/Configuration/INF/. All files in this directory need to be placed in the Rtos-Infs folder located under the CeWin installation path (C:\Programme\CeWin\Rtos-Infs). To avoid automatic installation of the cifx PCI device by Windows XP, it is necessary to rename the origin INF files in the windows INF directory (c:/windows/inf/). The origin INF file of a cifx PCI device can be located by searching for the name of the device which needs to be installed. Figure 5: INF - File Search Figure 5 shows the INF file search of a cifx PCI device ("cifx PCI/PCIe Device"). The name of a device can be found in the Windows Device Manager. It is recommended to rename INF file, found by this search, by appending ".sav" to the file name. Renaming the original INF file will prevent an automatic installation of the hardware under Windows XP.

14 Getting Started 14/29 Remember to rename the found INF file and its corresponding PNF file! Figure 6: Renaming INF - File Restoring the INF file name to its original name re-enables the automatic hardware installation under Windows XP. After renaming the INF file, the device must be uninstalled (Windows Device Manager > Right Click on the device which to uninstall > Deinstall). Do not use the Windows Device Manager Update Driver functionality! It is recommended to reinstall the device by first uninstalling the driver and than, manually installing it again with "Searching for new Hardware" from the Windows Device Manager.

15 Getting Started 15/29 After replacement of the corresponding INF files and de-installation, the hardware installation can be executed as usual (Windows Device Manager > Right Click > Searching for new Hardware). Figure 7 shows a snapshot. Figure 7: Device Manager Connections In the following installation dialog it is necessary to select the delivered INF file manually instead of choosing the automatic installation option of Windows XP. As already noted above, depending on the application or the custom needs, if the should be used in interrupt mode, the correct INF file for the device needs to be chosen (see /CeWin/Configuration/INF/). INF files are chosen by their name. Files without an extension are used for interrupt driven hardware and files with the extension "_nirq" (polling) are used for non interrupt driven hardware. For example if the cifx card is used in interrupt mode, the INF file cifxpci_pcie.inf must be used.! Search manually

16 Getting Started 16/29! Choose the INF file. This example uses the INF file with interrupt support for a NXSB PCA adapter.

17 Getting Started 17/29! This step will install the driver After a successful installation of the cifx card, the device will now appear in the Device Manager under Realtime OS Devices. Figure 8 shows an example system with an additional RTOS network adapter. In this case the Intel PRO/100 network adapter is working in polling mode and the cifx hardware is driven in interrupt mode. Figure 8: Device Manager RTOS Devices For detailed information or in case of further custom settings refer to the ACONTIOS: RtosVM-UserManual.

18 Getting Started 18/ Configure the CeWin Platform After the CeWin run-time environment installation, a few settings need to be done for the cifx hardware integration. The folder /CeWin/Configuration/Config/ contains example configuration files of a CeWin standard platform with integrated cifx PCI card. The corresponding settings need to be added in the equivalent configuration files under the installation path (c:/programs/cewin/). The folder /CeWin/Configuration/Config/ contains example files of a CeWin platform.! Os.config Includes all necessary configuration files.! General.config Configuration of Windows WinCE and RTOS.! cifxpci_pcie.config Configuration settings for the cifx PCI card.! NXSB-PCA-PCI.config Configuration settings for the NXSB-PCA PCI adapter. Note that these files are only example files. In case of an already running system please add only the missing lines of configuration. In case of creating/altering the configuration files, note that every configuration file is starting with the keyword 'RtosConfig' OS.config To include the necessary settings for the cifx PCI card the corresponding configuration file cifxpci_pcie.config (e.g. NXSB-PCA-PCI.config for cifx evaluation hardware) needs to be included. The following line is required:! #include "cifxpci_pcie.config" ;configuration of the cifx PCI/PCIe card Make sure cifxpci_pcie.config is placed in the same folder where OS.config is placed. According to the device the corresponding configuration file needs to be included. Device Configuration Files Name cifxpci_pcie.config Description generic configuration for cifx PCI/PCIe device NXSB-PCA-PCI.config Table 5: Configuration Files configuration for NXSB-PCA-PCI adapter (netx evaluation boards) Note that these files are only example files. For more information see section cifxpci_pcie.config / NXSB-PCA-PCI.config on page 20.

19 Getting Started 19/ General.config General.config contains general information about the platforms and the common registry settings of the WinCE. The following table shows some useful entries out of the WinCE registry section. General.config Registry Entry for WinCE [HKEY_LOCAL_MACHINE\Loader] "SystemPath" [HKEY_LOCAL_MACHINE\Init] LaunchXX [HKEY_LOCAL_MACHINE\Init] DependXX Description The SystemPath variable determines the standard search path of WinCE. Starts an application after system startup Dependency entry for an application specified in a LaunchXX entry. Table 6: Configuration Files - Windows CE Registry! SystemPath Declares the standard search path (SystemPath) of CeWin for libraries or executables. Libraries or executables which must be known by Windows CE needs to be listed in the SystemPath variable. Example: ; ; Windows CE registry ; [HKEY_LOCAL_MACHINE\Loader] "SystemPath" = multi_sz:"\\windows\\","\\network\\cewin\\","\\my_path\"

20 Getting Started 20/29! LaunchXX / DependXX The Launch entry allows starting applications after System Startup. The XX (replaced by a decimal number) defines the order they will be launched. The Depend entry allows starting an application depending on another application. Example: ; ; Windows CE registry ; [HKEY_LOCAL_MACHINE\init]... "Launch80"="AddNetShare.exe" ; this application will connect to the \network\cewin "Launch81"="ConnectConman.exe" ; this application will start the debugging host conn.... "Launch85"="LoadCifXDrv.exe" "Depend85"=hex:50,00... ; The example start order is, first AddNetShare then ConnectConman and LoadCifXDrv. The CEWin uses a default network path (/network/cewin/) for additional drivers (e.g, LoadCifXDrv). Therefore the network connection must be up and running before the cifx driver can be loaded. This makes an additional Depend entry necessary to make sure the network path is available before launching an application (LoadCifXDrv ) from it. 85 (decimal value) at the end of the Depend entry specifies the launch order, while the value 50 (given as a hexadecimal number) specifies the launch order entry (Launch80) this application depends on and must be started before. In this case AddNetShare must be executed before LoadCifXDrv is started cifxpci_pcie.config / NXSB-PCA-PCI.config Both configuration files (cifxpci_pcie.config / NXSB-PCA-PCI.config) contain information about the necessary registry settings of the corresponding devices. The cifxpci_pcie.config is a more generic configuration file. In case of other hardware or further registry options, the missing parameter needs to be added. For more information refer to the cifx CE Driver documentation chapter Driver Registry Settings. The configuration files placed in /CeWin/Configuration/Config/ are only examples. A detailed documentation about the registry settings for the cifx device can be found in the CifX CE Drv documentation chapter Driver Registry Settings.

21 Getting Started 21/ Running CeWin After installing and configuring CeWin, the platform can be started by clicking on Start > Programs > KUKA CeWin > Start CeWin in the Windows Start Menu. Figure 9: Starting CeWin The platform offers also a Debug Console and a Telnet connection. The Telnet connection is automatically established when using the icon "Telnet Target". It could be helpful to start the "Debug Console" before starting CeWin to be able to detect start-up problems. The amount of the debug output of the cifx driver can be adjusted in the registry setting TraceLevel (cifxpci_pcie.config / NXSB-PCA- PCI.config).

22 Getting Started 22/ CifX CE Drv Compiling the Source Code Building CifXCEDriver using Microsoft Visual Studio 2005 Build Procedure:! Copy the directory path, starting with 'VS2005' and all sub-directories to your development system.! Use the included solution file (cifxcedriver.sln) to open the projects with VS2005.! Choose the SDK for which the driver needs to be built for.! Using the drop down menu (CeWin 4.1 [display based] (WCE600) (x86))! Alternatively open the configuration manager and choose the SDK.! Now the driver can be build. First of all compile the cifx driver and the API-DLL. If you load the included solution file the following dialog message may pop up: "The project consists entirely of configurations that require support for platforms which are not installed on this machine. The project cannot be loaded." In this case install the corresponding Software Development Kit (headless or display based CeWin SDK).

23 Getting Started 23/ Driver installation Remember this documentation focuses a platform where the CE image is already build, thus the cifx driver needs to be load dynamically during system start. The CeWin platform offers a network path which is available after system start The network mapping offers the possibility to share files between Windows XP and Windows CE. Therefore files needed to be shared or published for CE must be placed in the network folder of CeWin. All required driver libraries needs to be placed there. It is recommended to choose a meaningful path where to place the driver libraries. When running CeWin, the whole installation path (c:/program/cewin/) is mapped to /network/cewin/. When adding files it is recommended to choose a meaningful path (e.g. the cifx driver: c:/program/cewin/cifxdrv/ results in /network/cewin/cifxdrv/). The following table shows the required files: File Description Location cifxcedrv.dll cifxcedll.dll Stream driver DLL API DLL User Defined File Location: The path must be within the network directory (/network/cewin/my_path) Additionally the path must be included in the Windows CE system search path. [HKEY_LOCAL_MACHINE\Loader] "SystemPath"=multi_sz:\\network\\cewin\\PATH_TO_DRIVER_LIB\\ NETX100-BSL.bin bootloader User Defined File Location: The path must be within the network directory (/network/cewin/my_path) Table 7: cifx Device Driver Libraries Add the network path to the bootloader file registry entry "BootloaderFile"="//network//cewin//MY_PATH". Remember to add the path where the libraries are located to the Windows CE search path (see section General.config on page 19) Registry Settings Under CeWin the registry settings are located in "*.config" files. During system start, CeWin loads the registry settings specified in the various ".config" files. Every configuration file must contain "RtosConfig" in its first line. The syntax of such a configuration file is equal to normal registry syntax. Examples of registry settings can be found under /CeWin/Configuration/Config/ (see section cifxpci_pcie.config on page 20). Therefore any registry setting for the cifx device can be done in the cifxpci_pcie.config file. General information of the cifx CE Driver registry entries can be found in the standard cifx CE Drv documentation.

24 Getting Started 24/ Loading the Driver Loading the cifx driver can be done manually, every time starting an application or automatically when starting the CE system. This expects a previous call of the CE system function ActivateDeviceEx before calling xdriveropen to ensure the driver is loaded. Prerequisite for both loading procedures is the correct driver installation (see section Driver installation on page 23) and the necessary settings and handling is described below. The PCI hardware information in the registry can be found under /HKEY_LOCAL_MACHINE/Drivers/BuiltIn/PCI/Instance/cifX[N]. N is a decimal number counting the allocated devices. Loading the driver after system start:! Manually In the user application ActivateDeviceEx(...) must be called before calling xdriveropen(). An example can be found in LoadCifXDrv (located under /CeWin/LoadCifXDrv/). The driver is loaded until calling DeactivateDevice(...). Loading the driver must be done particular for every device.! Automatically Helper application LoadCifXDrv can also be placed into the CE registry autostart entry, which makes it unnecessary to call ActivateDeviceEx(...) by the user application but therefore the following registry settings are necessary. In this case the driver is loaded until the system shuts down. To add LoadCifXDrv to the startup processes add the following lines (starting at "+++" and ending at "+++") to registry section WindowsCe in the Gerneral.config file (see section General.config on page 19): [HKEY_LOCAL_MACHINE\init] "LaunchYY"="AddNetShare.exe" "LaunchXX"="LoadCifXDrv.exe" "DependXX"=hex:YY, Remember to replace the XX with a decimal number higher than the launch order of AddNetShare (application which maps network path) and replace YY (hex) with the launch number of AddNetShare. Example: "Launch80"="AddNetShare.exe" "Launch81"="LoadCifXDrv.exe" "Depend81"=hex:50,00

25 Getting Started 25/ Demo Application Build! To build the application make sure that the required libraries and include directories are available and set up (section CifX CE Drv on page 22).! Remember to publish all required libraries to the CE image before starting to debug. Table 8 shows the delivered CeWin demo applications and where they are located. Demo Platform Location cifxcesetup display based /Driver/CE6/Application/cifXCESetup/ cifxtcpserver display based /Driver/CE6/Application/cifXTCPServer/ CifXTest display based /Driver/CE6//Application/cifXTest/ CifXTest_console display based /Driver/CE6/CeWin/Application/CifXTest_Console/ PFCheck_console LoadCifXDrv headless display based headless display based headless Do not use CifXTest_Console located under /Application/CifXTestConsole/. It will freeze Windows XP because of the execution priority of CeWin. /Driver/CE6/Application/PFCheck/ /Driver/CE6/CeWin/LoadCifXDrv/ Table 8: Demo Applications To build the application it is recommend to copy the whole folder "Application" in the same directory like folder VS2005 (see section CifX CE Drv on page 22). This secures an easy build process. In case of choosing an alternative directory all include paths for headers and libraries need to be adapted. After choosing the appropriate SDK (see section CifX CE Drv on page 22) the applications can be built. Every application noted in Table 8, requires executing once LoadCifXDrv before starting the application (see section Loading the Driver on page 24).

26 Getting Started 26/ Debug an Application This explanation expects the development environment and the CeWin platform on the same PC. For remote debugging it is necessary to integrate an additional network adapter or to setup a network bridge. For further information refer to [2]. To be able to run or debug any delivered application requires activating the driver. This can be done by running once LoadcifXDrv before starting a demo application. See section Loading the Driver on page 24.! Starting Debug Session with Visual Studio 2005: Choose Tools > Options click, Device Tools > Devices on the left window, select the appropriate platform (e.g., "CeWin 4.1") and select "Properties" Figure 10: Options! Configure the target IP address by clicking on Configure and insert the IP address like shown in Figure 11. Figure 11: Device Properties The IP address is the default specified in CeWin configuration files. In case of modifications type the corresponding here.

27 Getting Started 27/29! After this step Visual Studio will connect you to the target by clicking on Connect to..., (red marked icon in figure 11) Figure 12: Connecting to device The connection will only be established if the CeWin is already running. If the Connecting... dialog appears and results in Connection succeeded a normal debug session is available. To run the demo without Visual Studio, the application needs to be placed in the network folder of CeWin. For a better application overview under CeWin, create a separate folder under the installation path, for each of your user application (e.g. c:/program/cewin/project/pfcheck results in /network/cewin/project/pfcheck/). Starting the demo can be done via the Telnet Connection (noted in section Running CeWin on page 21). In case of using the display based image it is also possible to start the demo via the remote display (see CeWinRdisp.exe).

28 Appendix 28/29 4 Appendix 4.1 List of Tables Table 1: List of Revisions... 3 Table 2: Terms, Abbreviations and Definitions... 3 Table 3: References to Documents... 3 Table 4: CeWin Content... 8 Table 5: Configuration Files Table 6: Configuration Files - Windows CE Registry Table 7: cifx Device Driver Libraries Table 8: Demo Applications List of Figures Figure 1: CifX CE Driver - Architecture... 6 Figure 2: CeWin Setup Figure 3: Device Manager Figure 4: Device Manager Connections Figure 5: INF - File Search Figure 6: Renaming INF - File Figure 7: Device Manager Connections Figure 8: Device Manager RTOS Devices Figure 9: Starting CeWin Figure 10: Options Figure 11: Device Properties Figure 12: Connecting to device... 27

29 Appendix 29/ Contacts Headquarters Germany Hilscher Gesellschaft für Systemautomation mbh Rheinstrasse Hattersheim Phone: +49 (0) Fax: +49 (0) Support Phone: +49 (0) Subsidiaries China Hilscher Systemautomation (Shanghai) Co. Ltd Shanghai Phone: +86 (0) Support Phone: +86 (0) France Hilscher France S.a.r.l Bron Phone: +33 (0) info@hilscher.fr Support Phone: +33 (0) fr.support@hilscher.com India Hilscher India Pvt. Ltd. New Delhi Phone: info@hilscher.in Italy Hilscher Italia S.r.l Vimodrone (MI) Phone: info@hilscher.it Support Phone: it.support@hilscher.com Japan Hilscher Japan KK Tokyo, Phone: +81 (0) info@hilscher.jp Support Phone: +81 (0) jp.support@hilscher.com Korea Hilscher Korea Inc. Suwon, Gyeonggi, Phone: +82 (0) info@hilscher.kr Switzerland Hilscher Swiss GmbH 4500 Solothurn Phone: +41 (0) info@hilscher.ch Support Phone: +49 (0) ch.support@hilscher.com USA Hilscher North America, Inc. Lisle, IL Phone: info@hilscher.us Support Phone: us.support@hilscher.com