Windows IMCEA Driver SIMATIC Industrial PCs. Programming Manual 11/2011 SIMATIC

Transcription

1 Windows IMCEA Driver SIMATIC Industrial PCs Programming Manual 11/2011 SIMATIC

2

3 Introduction 1 2 SIMATIC SIMATIC Industrial PCs Programming Manual Software installation 3 IOCTL functions 4 IMCEA API functions 5 PC IO API functions 6 Application examples 7 A Appendix A 11/2011 J31069-D2131-U001-A3-7618

4 Legal information Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken. CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed. Trademarks All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Industry Sector Postfach NÜRNBERG GERMANY J31069-D2131-U001-A P 01/2012 Technical data subject to change Copyright Siemens AG All rights reserved

5 Table of contents 1 Introduction Software installation Requirements WINDOWS IMCEA (npnp) installation WINDOWS IMCEA (PnP) installation IOCTL functions IMCEA API functions Overview of the function groups Changes from Version Basic driver functions Overview of the basic driver functions ImcEADrvInstallDriver() ImcEADrvUninstallDriver() ImcEADrvStartDriver() ImcEADrvStopDriver() ImcEADrvOpen() ImcEADrvClose() Port access functions Overview of the port access functions ImcEADrvReservePort() ImcEADrvFreePort() ImcEADrvWritePort() ImcEADrvReadPort() Memory access functions Overview of the memory access functions ImcEADrvReserveMem() ImcEADrvFreeMem() Interrupt processing functions Overview of the interrupt processing functions ImcEADrvStartInterruptHandler() ImcEADrvStopInterruptHandler() ImcEADrvResetWaitForInterrupt() ImcEADrvWaitForInterruptEx() PCI address space processing functions ImcEADrvSearchPCI()...52 Programming Manual, 11/2011, J31069-D2131-U001-A

6 Table of contents 6 PC IO API functions Introduction General API functions Overview of the general API functions PcioInit() PcioClose() PcioGetBaseAddress() PcioWaitForIRQ() Analog I/O functions Overview of the analog I/O functions PcioInitAnalogInput() PcioInitAnalogOutput() PcioReadAnalogChannel() PcioWriteAnalogChannel() PcioStartAnalogConversion() PcioSetAnalogOutputConversionChannels() Pt100 functions Overview of the Pt100 functions PcioInitPt100() PcioReadPt100() Digital I/O functions Overview of the digital I/O functions PcioReadDigitalInput() PcioWriteDigitalOutput() Diagnostic functions Overview of the diagnostic functions PcioDiagnosticRequest() Application examples Function of the application examples Generation of an application example A Appendix A A.1 Service and support Index Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

7 Introduction 1 Purpose of the manual This manual contains all information about the following topics: Installation and configuration of the WINDOWS IMCEA driver of the IOCTL functions of the driver Capabilities of the IMCEA API Capabilities of the PC IO API IMCEA API and PC IO API are based on the IOCTL functions of the driver. Target group The manual is aimed at programmers. Manual - range of validity The manual is valid for all supply versions of the WINDOWS IMCEA driver and describes the as-delivered condition as of Version 2.0. Further information For information on SIMATIC hardware as well as on the Visual Studio development environment, please refer to the respective product manuals. Windows-specific questions can be asked on the Microsoft support page ( Conventions The following abbreviations are used in this manual: For the product designation WINDOWS IMCEA driver, the abbreviation driver is also used. For the product designation "analog I/O module 0", "analog I/O module" is used. For the product designation "digital I/O module 0", "digital I/O module" is used. Programming Manual, 11/2011, J31069-D2131-U001-A

8 Introduction 8 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

9 2 Functionality Under the operating systems Microsoft Windows XP, Windows Embedded Standard 2009 (32-bit), Windows Server 2008 R2 (64-bit), Windows Embedded Standard 7 (32-bit), and Windows 7 Ultimate (32 and 64-bit), the WINDOWS IMCEA driver offers direct access functions (low-level) to physical I/O resources (memory-mapped I/O, port-based I/O and interrupts). With the driver, applications can directly access the hardware. Based on the driver functions, the IMCEA API permits simplified access to the hardware. The PC IO API offers functions which are specifically tailored to the properties of the PC IO basic module and the associated I/O modules. NOTICE The driver is only released for use on SIMATIC IPC hardware platforms. Note The driver also supports multiprocessor platforms. Furthermore, as of Version 2.0, the 64-bit versions of the Windows operating systems are also supported. Operation Several threads can simultaneously send jobs to the WINDOWS IMCEA driver. However, the I/O manager only passes on these jobs to the IMCEA driver if they have differing handles (connections). The handles are created by calling "ImcEADrvOpen()". As processing in the WINDOWS IMCEA driver takes place according to the priority of the thread, processing in the driver can also be interrupted by another thread. Programming Manual, 11/2011, J31069-D2131-U001-A

10 Driver variants The "WINDOWS IMCEA" product contains three driver variants: WINDOWS IMCEA (PnP, 32-bit): PlugAndPlay-capable driver for Windows XP, Windows Embedded Standard 2009, Windows 7 Ultimate, and Windows Embedded Standard 7 (32-bit version of the operating systems) WINDOWS IMCEA (npnp, 32-bit): Non-PlugAndPlay-capable driver for Windows XP, Windows Embedded Standard 2009, Windows 7 Ultimate, and Windows Embedded Standard 7 (32-bit version of the operating systems) WINDOWS IMCEA (npnp, 64-bit): Non-PlugAndPlay-capable driver for Windows Server 2008 R2 and Windows 7 Ultimate (64-bit version of the operating systems) Note The PnP driver and npnp driver can be operated at the same time. Product components The software for the product "WINDOWS IMCEA" is structured as follows: Component Included in IMCEA drivers IMCEA API PC IO API Application examples Installation files, drivers, documentation Source file of the IMCEA API Source files of the PC IO API Source file of the programming examples The IMCEA driver is accessed exclusively by means of the Windows function DeviceIOControl() Shows an example of the use of the IOCTL codes with the Windows function DeviceIOControl() Shows an example of the use of the IMCEA API functions when accessing a PC IO module Programming examples for the PC IO API and IMCEA API functions "WINDOWS IMCEA" comprises of the following individual files: File IMCEA drivers i386\imcea.sys i386\imceapnp.sys amd64\imcea.sys setup.bat Setup.exe Setup64.exe WINDOWS IMCEA (npnp) 32-bit driver WINDOWS IMCEA (PnP) 32-bit driver WINDOWS IMCEA (npnp) 64-bit driver Batch file for starting the 32-bit setup or 64-bit setup Setup program for the WINDOWS IMCEA (npnp) 32-bit driver Setup program for the WINDOWS IMCEA (npnp) 64-bit driver 10 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

11 File i386\imcea.inf inc\imceadrv.h Programmierhandbuch_WINDOWS_ IMCEA-Treiber.pdf Programming_Manual_WINDOWS_ IMCEA_Driver.pdf IMCEA API examples\imcealib.cpp inc\imcealib.h PC IO API inc\pcio.h examples\pcio.cpp inc\pcioport.h inc\pcioportwin32.h examples\pcioportwin32.cpp Installation file for the WINDOWS IMCEA (PnP) driver This header file includes definitions for the IOCTL code for access to the driver, and definitions for the pass structures. The file also allows direct access to the WINDOWS IMCEA driver without API. User documentation for the WINDOWS IMCEA driver (German) User documentation for the WINDOWS IMCEA driver (English) Source file of the IMCEA API with the calls. This file includes the source code of all functions for access to the driver. Header file for WINDOWS IMCEA calls. This file includes definitions for the example functions for access to the driver. All driver functions are accessible via a C interface. Header file for the PC IO API This file contains definitions, data types and prototypes of the use of the PC IO API. The file must be integrated in the user program if the functions of the PC IO API are to be used. Source file for the PC IO API This file contains the operating system-independent source code of the PC IO API functions. The file must be compiled with the user program if the functions of the PC IO API are to be used. Header file for the PC IO API This file contains internal definitions and data types of the PC IO API. It is automatically integrated by the header file pcio.h and must be compiled with the user program if the functions of the PC IO API are to be used. Header file for the PC IO API This file contains internal Windows-specific definitions and data types of the PC IO API. The file is automatically integrated by the header file pcio.h and must be compiled with the user program if the functions of the PC IO API are to be used. Source file for the PC IO API This file contains the Windows-specific source code of the PC IO API functions. The file must be compiled with the user program if the functions of the PC IO API are to be used. Programming Manual, 11/2011, J31069-D2131-U001-A

12 File Application examples examples\pcio_api\main.cpp examples\microbox\microbox.cpp examples\ipc627c\ipc627c.cpp examples\pcio_geber\main.cpp Source file of the programming examples for the PC IO API applications Source file of the programming example with the IMCEA API for the SIMATIC IPC427C Source file of the programming example with the IMCEA API for the SIMATIC IPC627C Source file of the programming example with the IMCEA API for access to the encoder of a PC IO basic module Development environment All the example files included in the product have been tested with Visual Studio 2005, 2008 and Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

13 Software installation Requirements Hardware requirements You need a Windows computer in order to install the WINDOWS IMCEA driver. To use the PlugAndPlay version of the driver, your computer must have a PCI bus. The driver can be used for the PC IO Base 400 module, for example. Software requirements To install the driver you need the "WINDOWS IMCEA" product. Note Administrator rights are required to install the IMCEA driver. Programming Manual, 11/2011, J31069-D2131-U001-A

14 Software installation 3.2 WINDOWS IMCEA (npnp) installation 3.2 WINDOWS IMCEA (npnp) installation IMCEA (npnp) installation procedure To install the driver, proceed as follows: Start the installation program Setup.ba that is included in the product package with administrator rights. The Setup dialog box appears: In the Setup dialog box, select the Install option. The driver is installed and registered in the system. After completing the installation, restart the system. The driver is now started and can be used by an application. After the next power-up of the operating system, the driver is also visible in the device manager of the Windows Control Panel. Alternative method of installation The npnp driver can also be installed from an application program. For more information on this, please refer to the description of the "ImcEADrvInstallDriver()" function. Note As of Version 1.7 of the Windows IMCEA driver, the driver is installed by Setup with the "automatic" mode so that it is started during the power-up of the operating system. This approach avoids the operating system security warnings that occur when a driver is installed and started from within the application. Installing and starting the driver from the application is thus omitted. 14 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

15 Software installation 3.2 WINDOWS IMCEA (npnp) installation Representation of the driver in the Device Manager Start the device manager. In order to show non-plugandplay devices, use the right mouse key to activate the "View" menu on the Device Manager icon and there select "Show hidden devices". Note If the drivers are not displayed in the Device Manager, then either manually start the driver or restart the system. Programming Manual, 11/2011, J31069-D2131-U001-A

16 Software installation 3.2 WINDOWS IMCEA (npnp) installation The driver is indicated by the name "IMCEA". The "automatic" starting mode is selected as the default setting. However, you can change the starting mode by clicking the right mouse key and selecting the "Properties" menu. The following settings are available: If the driver is to be started by the application, select the option "Requirement". Note Some operating systems issue security warnings if a driver is installed and started from within the application. As of Version 1.7 of the Windows IMCEA driver, the driver is therefore installed by Setup with the "automatic" mode so that it is started during the power-up of the operating system. 16 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

17 Software installation 3.3 WINDOWS IMCEA (PnP) installation 3.3 WINDOWS IMCEA (PnP) installation IMCEA (PnP) installation procedure To install the driver, proceed as follows: After installing a module and the subsequent restart of the system, the "Found New Hardware Wizard" is displayed. Now insert the data medium containing the "WINDOWS IMCEA" product into the respective drive of your computer (for example: USB flash drive in H:\) and select the following options: Programming Manual, 11/2011, J31069-D2131-U001-A

18 Software installation 3.3 WINDOWS IMCEA (PnP) installation 18 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

19 Software installation 3.3 WINDOWS IMCEA (PnP) installation Select the "Have Disk" and then your USB flash drive: The system then finds the PnP driver on the USB flash drive. This is then installed once you click on "Next": Note As the driver is not certified by Microsoft, in some operating systems a system message appears during installation stating that the driver has not passed the Windows logo test. Ignore this message and continue with the installation. Programming Manual, 11/2011, J31069-D2131-U001-A

20 Software installation 3.3 WINDOWS IMCEA (PnP) installation The "Finish" option concludes the installation: After installation, the driver is ready for normal operation and is visible in the Device Manager of the Windows Control Panel. 20 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

21 Software installation 3.3 WINDOWS IMCEA (PnP) installation Representation of the driver in the Device Manager The driver is indicated by the name "Siemens PC IO Central Peripheral Extension (CIO)" in the "Multifunction adapters" menu. Programming Manual, 11/2011, J31069-D2131-U001-A

22 Software installation 3.3 WINDOWS IMCEA (PnP) installation 22 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

23 IOCTL functions 4 All access to the driver takes place via IOCTL functions. They are passed to the driver by the "DeviceIoControl()" function. The definitions of possible calls are specified in the header file IMCDRV.H. The following IOCTL functions are available: Function CTRLCD_RESERVE_PORT CTRLCD_READ_PORT CTRLCD_WRITE_PORT CTRLCD_FREE_PORT CTRLCD_RESERVE_MEM CTRLCD_FREE_MEM CTRLCD_START_INTR_HANDLER CTRLCD_FREE_INTR_HANDLER CTRLCD_WAIT_FOR_INTERRUPT CTRLCD_RESET_WAIT_FOR_INTERRUPT CTRLCD_SEARCH_PCI CTRLCD_WAIT_FOR_INTERRUPTEX Reserving I/O port Reading a port Writing to a port Freeing a reserved port Reserving a memory area Freeing a reserved memory area Reserve interrupt and set up handler Free reserved interrupt Waiting for receipt of an interrupt Aborting waiting for an interrupt Configuration Space - search and read Waiting for receipt of an interrupt and read Note A more detailed description of the IOCTL functions is not included in this documentation. Programming Manual, 11/2011, J31069-D2131-U001-A

24 IOCTL functions 24 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

25 IMCEA API functions Overview of the function groups The IMCEA API functions are based on the IOCTL functions. The functions provided in the source file of the IMCEA API can be divided into the following groups: Basic driver functions Port access functions Memory access functions Interrupt processing functions PCI address space processing functions Note All the functions described in the following chapters have been tested with Visual Studio 2005, 2008, and Changes from Version 1.7 The IMCEA API was extended for 64-bit applications. The following data types were changed in the structures RESERVEINT and RESERVEINTEX: RESERVEINT: Component Old data type New data type IntHandle ULONG ULONG_PTR RESERVEINTEX: Component Old data type New data type Address ULONG ULONG_PTR IntHandle ULONG ULONG_PTR Note For 32-bit operating systems, the data type does not change because the previous data type ULONG is included in ULONG_PTR. Existing user applications therefore do not require alteration or recompilation. Programming Manual, 11/2011, J31069-D2131-U001-A

26 IMCEA API functions 5.3 Basic driver functions 5.3 Basic driver functions Overview of the basic driver functions The WINDOWS IMCEA driver offers the following basic functions: Function ImcEADrvInstallDriver() ImcEADrvUninstallDriver() ImcEADrvStartDriver() ImcEADrvStopDriver() ImcEADrvOpen() ImcEADrvClose() Install npnp driver Uninstall npnp driver Start npnp driver Stop npnp driver Open driver Close driver Note As of Version 1.7, the functions "ImcEADrvInstallDriver()", "ImcEADrvUninstallDriver()", "ImcEADrvStartDriver()" and "ImcEADrvStopDriver()" are no longer of significance and merely exist for compatibility reasons with earlier driver versions. 26 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

27 IMCEA API functions 5.3 Basic driver functions ImcEADrvInstallDriver() With the "ImcEADrvInstallDriver()" function, the npnp driver can be installed from an application program. Note As of Version 1.7, the "ImcEADrvInstallDriver" function is no longer of significance and it merely exists for compatibility reasons with earlier driver versions. Note Prior to executing the "ImcEADrvInstallDriver()" function, you must first copy the file imcea.sys to the "<Windows>\system32\drivers" directory. Syntax DWORD ImcEADrvInstallDriver ( char *szdriverpath, char *szdrivername ); szdriverpath szdrivername Path and file name, e.g. "%SystemRoot%\\system32\\drivers\\imcea.sys" Driver name "IMCEA" Programming example dwretcode = ImcEADrvInstallDriver("%SystemRoot%\\system32\\drivers\\imcea.sys", "IMCEA"); if((dwretcode!= ERROR_SUCCESS) && (dwretcode!= ERROR_SERVICE_EXISTS)) { printf("imceadrvinstalldriver: Error 0x%lx\n", dwretcode); } After completing the installation, restart the system. The driver is now ready for normal operation and is visible after start-up by the application program in the Device Manager of the Windows Control Panel. Programming Manual, 11/2011, J31069-D2131-U001-A

28 IMCEA API functions 5.3 Basic driver functions ImcEADrvUninstallDriver() With the "ImcEADrvUninstallDriver()" function, the npnp driver can be uninstalled from an application program. Note As of Version 1.7, the "ImcEADrvUninstallDriver" function is no longer of significance and it merely exists for compatibility reasons with earlier driver versions. Syntax DWORD ImcEADrvUninstallDriver ( char *szdrivername ); szdrivername Driver name "IMCEA" Programming example dwretcode = ImcEADrvUninstallDriver("IMCEA"); if(dwretcode!= ERROR_SUCCESS) { printf("imceadrvuninstalldriver: Error 0x%lx\n", dwretcode); } 28 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

29 IMCEA API functions 5.3 Basic driver functions ImcEADrvStartDriver() The function "ImcEADrvStartDriver()" in the source file for IMCEA API starts the npnp driver at runtime. "IMCEA" is given as the driver name. Note As of Version 1.7, the "ImcEADrvStartDriver" function is no longer of significance and it merely exists for compatibility reasons with earlier driver versions. Note It is only necessary to start the driver via this function if the starting mode "Manual" is selected in the device settings. Syntax DWORD ImcEADrvStartDriver ( char *szdrivername ); szdrivername Driver name "IMCEA" Programming example dwretcode = ImcEADrvStartDriver("IMCEA"); if(dwretcode!= ERROR_SUCCESS) { printf("imceadrvstartdriver: Error 0x%lx\n", dwretcode); } Programming Manual, 11/2011, J31069-D2131-U001-A

30 IMCEA API functions 5.3 Basic driver functions ImcEADrvStopDriver() The function "ImcEADrvStopDriver()" in the source file for IMCEA API stops the npnp driver. "IMCEA" is given as the driver name. When it is stopped, the driver independently performs all the clearing work. As a result, the occupied resources (ports, memory and interrupts) are freed. Note As of Version 1.7, the "ImcEADrvStopDriver" function is no longer of significance and it merely exists for compatibility reasons with earlier driver versions. Note It is usually unnecessary to stop the driver. In the development phase of an application, the explicit starting and stopping of a driver can sometimes be helpful. NOTICE Stopping the driver using this function can cause problems with other applications that are also using the driver. Syntax DWORD ImcEADrvStopDriver ( char *szdrivername ); szdrivername Driver name "IMCEA" Programming example dwretcode = ImcEADrvStopDriver("IMCEA"); if(dwretcode!= ERROR_SUCCESS) { printf("imceadrvstopdriver: Error 0x%lx\n", dwretcode); } 30 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

31 IMCEA API functions 5.3 Basic driver functions ImcEADrvOpen() The function "ImcEADrvOpen()" in the source file for IMCEA API opens the driver. The name "IMCEA" is given for the npnp driver, and "IMCEA0" for the PnP driver (with several modules then "IMCEA1", "IMCEA2" etc.). As a result a handle is returned. Subsequent calls on the driver are only possible using this handle. Syntax DWORD ImcEADrvOpen ( char* szdrivername, HANDLE* hdrvhandle ); szdrivername hdrvhandle Driver name "IMCEA" Driver handle Programming example dwretcode = ImcEADrvOpen("IMCEA", &DrvHandle); if(dwretcode!= ERROR_SUCCESS) { printf("imceadrvopen: Error 0x%lx\n", dwretcode); } Programming Manual, 11/2011, J31069-D2131-U001-A

32 IMCEA API functions 5.3 Basic driver functions ImcEADrvClose() The function "ImcEADrvClose()" in the source file for IMCEA API closes the driver. Syntax DWORD ImcEADrvClose ( HANDLE hdrvhandle ); hdrvhandle Driver handle Programming example ImcEADrvClose (hdrvhandle); 32 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

33 IMCEA API functions 5.4 Port access functions 5.4 Port access functions Overview of the port access functions Available functions The following port access functions can be used with the WINDOWS IMCEA driver: Function ImcEADrvReservePort() ImcEADrvFreePort() ImcEADrvWritePort() ImcEADrvReadPort() Reserve ports Free ports Write ports Read ports Use of the functions Before a program can access ports, you must register the I/O area with the operating system by means of the "ImcEADrvReservePort()" function. After successfully registering the I/O area, ports can be read and written via the "ImcEADrvReadPort()" and "ImcEADrvWritePort()" functions. After concluding the access, you can then again free the registered area by means of the "ImcEADrvFreePort()" function. Note As of Version 1.7, the functions "ImcEADrvReservePort()" and "ImcEADrvFreePort()" are no longer of significance, and merely exist for compatibility reasons with earlier driver versions. Note A direct port access of the application is not possible. Programming Manual, 11/2011, J31069-D2131-U001-A

34 IMCEA API functions 5.4 Port access functions Data structures used The data structures "RESERVEIO" and "PORTIO" are used for the port access functions. typedef struct ReserveIO { PVOID StartAddress; /* start address of the port or the memory */ ULONG Length; /* length of the area in bytes */ } RESERVEIO; typedef RESERVEIO *PRESERVEIO; typedef struct PortIO { PVOID Address; /* address of the port at IMCEA(nPnP) Offset of the port at IMCEA(PnP) */ ULONG Value; /* value to be written */ ULONG Mode; /* 0: PORT_MODE_UCHAR: Byte access 1: PORT_MODE_USHORT: Word access 2: PORT_MODE_ULONG: Dword access */ } PORTIO; typedef PORTIO *PPORTIO; 34 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

35 IMCEA API functions 5.4 Port access functions ImcEADrvReservePort() The "ImcEADrvReservePort()" function checks the passed parameters for completeness and correctness. The function then checks to see if the necessary ports in the system are unoccupied. If the ports are unoccupied they will be exclusively occupied by the driver. Note As of Version 1.7, the "ImcEADrvReservePort()" function is no longer of significance and it merely exists for compatibility reasons with earlier driver versions. Syntax DWORD ImcEADrvReservePort ( HANDLE hdrvhandle, RESERVEIO *ReserveIO ); hdrvhandle ReserveIO Return value of the function "ImcEADrvOpen()" Data structure for the port access function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_NO_SYSTEM_RESOURCES ERROR_NO_MORE_ITEMS ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The requested area could not be reserved (resources are already occupied) The number of reserved I/O areas is too great (max. 50) Handle is invalid Programming Manual, 11/2011, J31069-D2131-U001-A

36 IMCEA API functions 5.4 Port access functions ImcEADrvFreePort() The function "ImcEADrvFreePort()" again frees the I/O areas that were occupied with the function "ImcEADrvReservePort()". Note As of Version 1.7, the "IImcEADrvFreePort()" function is no longer of significance and it merely exists for compatibility reasons with earlier driver versions. Syntax DWORD ImcEADrvFreePort ( HANDLE hdrvhandle, RESERVEIO *ReserveIO ); hdrvhandle ReserveIO Return value of the function "ImcEADrvOpen()" Data structure for the port access function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_ADDRESS ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The area to be freed has not been reserved ("Reserve ports" call missing) Handle is invalid 36 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

37 IMCEA API functions 5.4 Port access functions ImcEADrvWritePort() Syntax The "ImcEADrvWritePort()" function can write a port with a byte, word or dword. To do this, the respective value must be entered in the "Mode" field. With PnP drivers, the parameter Address includes the offset as an input parameter and the actual address (start address of the module + offset) as an output parameter. DWORD ImcEADrvWritePort ( HANDLE hdrvhandle, PORTIO *PortIO ); hdrvhandle PortIO Return value of the function "ImcEADrvOpen()" Data structure for the port access function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_PARAMETER ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The mode does not correspond with the three predefined types Handle is invalid Programming example PORTIO PortIO; PortIO.Address = (void*)0x3f8; PortIO.Value = 0x41; PortIO.Mode = PORT_MODE_UCHAR; /* absolute address for IMCEA(nPnP) relative address for IMCEA(PnP) */ dwretcode = ImcEADrvWritePort(hDrvHandle, &PortIO); if(dwretcode == ERROR_SUCCESS) { printf("value(mode=%d) 0x%x written to Address 0x%x\n", PortIO.mode, PortIO.Value, PortIO.Address); } Programming Manual, 11/2011, J31069-D2131-U001-A

38 IMCEA API functions 5.4 Port access functions ImcEADrvReadPort() The "ImcEADrvReadPort()" function can read a port with a byte, word or dword. To do this, the respective value must be entered in the "Mode" field. With IMCEA(PnP) the parameter Address includes the offset as an input parameter and the actual address (start address of the module + offset) as an output parameter. Syntax DWORD ImcEADrvReadPort ( HANDLE hdrvhandle, PORTIO *PortIO ); hdrvhandle PortIO Return value of the function "ImcEADrvOpen()" Data structure for the port access function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_PARAMETER ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The mode does not correspond with the three predefined types Handle is invalid Programming example PORTIO PortIO; PortIO.Address = (void*)0x21; PortIO.Value = 0x0; PortIO.Mode = PORT_MODE_UCHAR; /* absolute address for IMCEA(nPnP) relative address for IMCEA(PnP) */ dwretcode = ImcEADrvReadPort(hDrvHandle, &PortIO); { printf("value(mode=%d) of Address 0x%x = 0x%x\n", PortIO.mode, PortIO.Address, PortIO.Value); } 38 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

39 IMCEA API functions 5.5 Memory access functions 5.5 Memory access functions Overview of the memory access functions Available functions The following memory access functions can be used with the WINDOWS IMCEA driver: Function ImcEADrvReserveMem() ImcEADrvFreeMem() Reserve memory Free memory Data structures used The data structure "RESERVEIO" is used for the memory access functions. typedef struct _ReserveIO { PVOID StartAddress; /* start address of the port or the memory */ ULONG Length; /* length of the area in bytes */ } RESERVEIO; typedef RESERVEIO *PRESERVEIO; Programming Manual, 11/2011, J31069-D2131-U001-A

40 IMCEA API functions 5.5 Memory access functions ImcEADrvReserveMem() WINDOWS IMCEA (npnp) With the function "ImcEADrvReserveMem()" you can reserve the passed memory addresses. The function is informed of the start address and the number of bytes following. The driver checks the resources in view of the resources already occupied by Windows. If there is no conflict, then the resources are designated as occupied. WINDOWS IMCEA (PnP) Via the PnP mechanism, the driver already knows the address and the length of the memory. Both parameters of the RESERVEIO structure are therefore not evaluated. The function carries out an address mapping with the start address. The resulting virtual address is returned to the caller. All future access to the memory must be conducted via the virtual address. With this address, the application can work directly in User Mode. Syntax DWORD ImcEADrvReserveMem ( HANDLE hdrvhandle, RESERVEIO *ReserveIO ); hdrvhandle ReserveIO Return value of the function "ImcEADrvOpen()" Data structure for the memory access function 40 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

41 IMCEA API functions 5.5 Memory access functions Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_NO_SYSTEM_RESOURCES ERROR_NO_MORE_ITEMS ERROR_ACCESS_DENIED ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The required area could not be reserved as it has already been reserved by another call. The number of reserved areas is too great (max. 50) The address mapping is denied by the operating system Handle is invalid WINDOWS IMCEA (npnp) - programming example RESERVEIO ReserveIO; ReserveIO.StartAddress = (void*)address; /* not used for IMCEA(PnP) */ ReserveIO.Length = length; /* not used for IMCEA(PnP) */ dwretcode = ImcEADrvReserveMem(hDrvHandle, &ReserveIO); if(dwretcode == ERROR_SUCCESS) { printf("imceareservemem(address: 0x%x) was successful\n", ReserveIO.StartAddress); } WINDOWS IMCEA (PnP) - programming example RESERVEIO ReserveIO; dwretcode = ImcEADrvReserveMem(hDrvHandle, &ReserveIO); if(dwretcode == ERROR_SUCCESS) { printf("imceareservemem(address: 0x%x, Length: 0x%x) was successful\n", ReserveIO.StartAddress, ReserveIO.Length); } Programming Manual, 11/2011, J31069-D2131-U001-A

42 IMCEA API functions 5.5 Memory access functions Conduct memory access After reserving the desired memory area, access to the memory can take place directly within the application. Note Please note that all modern compilers carry out a very strong code optimization. This can result in individual memory accesses being optimized away. If you want to avoid this, then you must exclude the respective accesses via Pragmas from optimization, or the pointers must be declared as "volatile". Memory access - programming example volatile ULONG *helpmem; RESERVEIO ReserveIO; dwretcode = ImcEADrvReserveMem(hDrvHandle, &ReserveIO); if(dwretcode == ERROR_SUCCESS) { printf("imceareservemem(address: 0x%x, Length: 0x%x) was successful\n", ReserveIO.StartAddress, ReserveIO.Length); } helpmem = (ULONG*) ReserveIO.StartAddress; helpmem[0] = 0x ; /* out value */ readmem = helpmem[6]; /* read register 6 */ 42 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

43 IMCEA API functions 5.5 Memory access functions ImcEADrvFreeMem() Using the function "ImcEADrvFreeMem()" you can again free the memory areas that were occupied using the function "ImcEADrvReserveMem()". To do this, the virtual address that was provided by the function "ImcEADrvReserveMem()" must be passed. Syntax DWORD ImcEADrvFreeMem ( HANDLE hdrvhandle, RESERVEIO *ReserveIO ); hdrvhandle ReserveIO Return value of the function "ImcEADrvOpen()" Data structure for the memory access function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_ADDRESS ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The area to be freed has not been reserved ("Reserve memory" call missing) Handle is invalid Programming example dwretcode = ImcEADrvFreeMem(hDrvHandle, &ReserveIO); Programming Manual, 11/2011, J31069-D2131-U001-A

44 IMCEA API functions 5.6 Interrupt processing functions 5.6 Interrupt processing functions Overview of the interrupt processing functions Available functions The following interrupt processing functions can be used with the WINDOWS IMCEA driver: Function ImcEADrvStartInterruptHandler() ImcEADrvStopInterruptHandler() ImcEADrvResetWaitForInterrupt() ImcEADrvWaitForInterruptEx() Reserving of interrupts Free interrupts Reset wait for interrupts Wait for interrupts with read Data structures used The data structures "RESERVEINT" and "RESERVEINTEX" (for "ImcEADrvWaitForInterruptEx()") are used for the interrupt processing functions. typedef struct ReserveInt { ULONG IntNr; /* Number of the interrupt for WINDOWS IMCEA (npnp) */ ULONG Mode; /* Shared for WINDOWS IMCEA (npnp): INT_MODE_SHARED Bus type for WINDOWS IMCEA(nPnP): INT_BUS_ISA INT_BUS_PCI Trigger mode for both drivers: INT_LATCHED INT_LEVELSENSITIVE */ ULONG Timeout; /* Timeout in milliseconds or INFINITE */ ULONG_PTR /* Returned handle from the function */ IntHandle; /* "ImcEADrvStartInterruptHandler()" */ ULONG Status; /* Reason for feedback: INT_NORMAL: Interrupt has arrived INT_BREAK: Interrupt was canceled INT_TIMEOUT: Timeout */ } RESERVEINT; typedef RESERVEINT *PRESERVEINT; 44 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

45 IMCEA API functions 5.6 Interrupt processing functions typedef struct ReserveIntEx { ULONG_PTR /* Physical address from which is read for */ Address; /* WINDOWS IMCEA(nPnP) or offset for WINDOWS /* IMCEA(PnP) */ ULONG Mode; /* Read mode: INT_MODE_IO_READ8 INT_MODE_IO_READ16 INT_MODE_IO_READ32 INT_MODE_MEM_READ8 INT_MODE_MEM_READ16 INT_MODE_MEM_READ32 */ ULONG Timeout; /* Timeout in milliseconds or INFINITE */ ULONG_PTR /* Returned handle from the function */ IntHandle; /* "ImcEADrvStartInterruptHandler()" */ ULONG Status; /* Reason for feedback: INT_NORMAL: Interrupt has arrived INT_BREAK: Interrupt was canceled INT_TIMEOUT: Timeout */ ULONG Value; /* Input: Mask for read value Output: read value */ } RESERVEINTEX; typedef RESERVEINTEX *PRESERVEINTEX; Programming Manual, 11/2011, J31069-D2131-U001-A

46 IMCEA API functions 5.6 Interrupt processing functions ImcEADrvStartInterruptHandler() The function "ImcEADrvStartInterruptHandler()" installs an Interrupt Service Routine (ISR) for the passed interrupt number. Note Interrupts that occur directly after a function call can be lost. Only after calling the function "ImcEADrvWaitForInterruptEx()" is the driver able to pass on the information to the application without losing an interrupt. Note With the Mode parameter in the RESERVEINT structure, the WINDOWS IMCEA (npnp) driver does not evaluate whether the interrupt should be shared or reserved exclusively. Note The driver WINDOWS IMCEA (PnP) already knows the interrupt number via the PnP mechanism. The parameters IntNr and Mode from the RESERVEINT structure are therefore not evaluated. Syntax DWORD ImcEADrvStartInterruptHandler ( HANDLE hdrvhandle, RESERVEINT *IntData ); hdrvhandle IntData Return value of the function "ImcEADrvOpen()" Data structure for the interrupt processing function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_NO_SYSTEM_RESOURCES ERROR_NO_MORE_ITEMS ERROR_INVALID_HANDLE No error The data structures to/from the driver are incorrect No system resources available The number of occupied interrupts is too great (max. 15) Handle is invalid 46 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

47 IMCEA API functions 5.6 Interrupt processing functions WINDOWS IMCEA (npnp) - programming example RESERVEINT IntData; IntData.IntNr = 5; /* IRQ */ IntData.IntHandle = 0; /* Don`t care */ IntData.Mode = INT_MODE_SHARED INT_BUS_ISA INT_LEVELSENSITIVE; /* Shared */ dwretcode = ImcEADrvStartInterruptHandler(hDrvHandle, &IntData); WINDOWS IMCEA (PnP) - programming example RESERVEINT IntData; IntData.IntHandle = 0; /* Don`t care */ IntData.Mode = INT_LATCHED; /* latched */ dwretcode = ImcEADrvStartInterruptHandler(hDrvHandle, &IntData); if(dwretcode == ERROR_SUCCESS) { printf("startinterrupthandler(intno: 0x%x) was successful\n", IntData.IntNo); } Programming Manual, 11/2011, J31069-D2131-U001-A

48 IMCEA API functions 5.6 Interrupt processing functions ImcEADrvStopInterruptHandler() The function "ImcEADrvStopInterruptHandler()" again frees the resources that have been reserved by means of the function "ImcEADrvStartInterruptHandler()". Syntax DWORD ImcEADrvStopInterruptHandler ( HANDLE hdrvhandle, RESERVEINT *IntData ); hdrvhandle IntData Return value of the function "ImcEADrvOpen()" Data structure for the interrupt processing function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_ADDRESS ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect The interrupt was not occupied ("Reserve interrupt" call missing) Handle is invalid Programming example ImcEADrvStopInterruptHandler(hDrvHandle, &IntData); 48 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

49 IMCEA API functions 5.6 Interrupt processing functions ImcEADrvResetWaitForInterrupt() The function "ImcEADrvResetWaitForInterrupt()" acknowledges the wait function "ImcEADrvWaitForInterruptEx()". You must use this function in order to cancel the wait function. Syntax DWORD ImcEADrvResetWaitForInterrupt ( HANDLE hdrvhandle, RESERVEINT *IntData ); hdrvhandle IntData Return value of the function "ImcEADrvOpen()" Data structure for the interrupt processing function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect Handle is invalid Programming example ImcEADrvResetWaitForInterrupt(hDrvHandle, &IntData); Programming Manual, 11/2011, J31069-D2131-U001-A

50 IMCEA API functions 5.6 Interrupt processing functions ImcEADrvWaitForInterruptEx() The function "ImcEADrvWaitForInterruptEx()" waits for the interrupt to arrive. With an interrupt, the address (I/O or memory) given in the parameter block is read and masked with the passed mask. If, after masking, a bit is still set, the interrupt from this module is triggered and the read value (without masking) is returned. Within the Interrupt Service Routine (ISR) this waiting function is informed of the event. The function can now return to the application and therefore report the interrupt event. In order to be able to execute the function "ImcEADrvWaitForInterruptEx()", a special thread is required within the application and this is executed asynchronously to the normal sequence. This thread needs a special handle to call in order to be able to access the driver. The "INT_BREAK" flag of the "Status" component" within the structure "RESERVEINTEX" indicates if the interrupt was cancelled by means of the function "ImcEADrvResetWaitForInterrupt()". Syntax DWORD ImcEADrvWaitForInterruptEx ( HANDLE hdrvhandle, RESERVEINTEX *IntDataX ); hdrvhandle IntDataX Return value of the function "ImcEADrvOpen()" Data structure for the interrupt processing function Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_PARAMETER ERROR_INVALID_HANDLE Meaning No errors The data structures to/from the driver are incorrect The mode is invalid Handle is invalid Programming example RESERVEINTEX IntDataX; 50 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

51 IMCEA API functions 5.6 Interrupt processing functions IntDataX.Address = 0x0; /* relative address */ IntDataX.IntHandle = IntData.IntHandle; IntDataX.Mode = INT_MODE_MEM_READ32; IntDataX.Value = 0xffffffff; /* check all bits */ IntDataX.Timeout = INFINITE; /* wait till interrupt has occurred */ dwretcode = ImcEADrvWaitForInterruptEx(hDrvHandle, &IntDataX); if(dwretcode == ERROR_SUCCESS) { printf("interrupt status register = 0x%x,status = 0x%x\n", IntDataX.Value, IntData.Status); } Programming Manual, 11/2011, J31069-D2131-U001-A

52 IMCEA API functions 5.7 PCI address space processing functions 5.7 PCI address space processing functions The following PCI address space processing functions can be used with the WINDOWS IMCEA driver: Function ImcEADrvSearchPCI() Configuration space search ImcEADrvSearchPCI() The function "ImcEADrvSearchPCI()" searches the entire PCI bus for all functions that correspond with the selected parameters VendorID, DeviceID, Subsystem VendorID and Subsystem ID. In order to search all devices on the bus, VendorID = 0xFFFFFFFF can be passed. Note Please refer to the manufacturer s information concerning configuration space for precise details regarding the parameters DeviceID and VendorID. The contents of the devices found are entered in the passed Config-Space field. The function cancels the search when the Config-Space field is full. If the function finds no device on the bus for the selected parameters VendorID and DeviceID, then NumOfFunctions = 0 is set. Syntax DWORD ImcEADrvSearchPCI ( HANDLE hdrvhandle, ULONG VendorID, ULONG DeviceID, ULONG SubVendorID, ULONG SubDeviceID, PCI_CONFIG_SPACE *ConfigSpace, ULONG MaxNumOfFunctions, ULONG *NumOfFunctions ); 52 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

53 IMCEA API functions 5.7 PCI address space processing functions Structure of the PCI_CONFIG_SPACE field typedef struct { UCHAR PciBusNum; /* Bus number */ UCHAR PciDeviceNum; /* Device number */ UCHAR PciFunctionNum; /* Function number */ USHORT VendorId; USHORT DeviceId; USHORT Cmdreg; USHORT StatReg; UCHAR RevisionId; UCHAR ClassCode[3]; UCHAR CacheLineSize; UCHAR LatencyTime; UCHAR HeaderType; UCHAR BIST; UINT BaseAdr0; UINT BaseAdr1; UINT BaseAdr2; UINT BaseAdr3; UINT BaseAdr4; UINT BaseAdr5; UINT CardbusCisPtr; USHORT SubsysVendorId; USHORT SubsysId; UINT ExpRomBaseAdr; UINT reserved[2]; UCHAR IntLine; /* Interrupt */ UCHAR IntPin; UCHAR Min_Gnt; UCHAR Max_Lat; } PCI_CONFIG_SPACE; hdrvhandle VendorID DeviceID SubVendorID SubDeviceID ConfigSpace MaxNumOfFunctions NumOfFunctions Return value of the function "ImcEADrvOpen()" Vendor ID Device ID Subsystem Vendor ID Subsystem ID Array of Config-Space Maximum number of entries in Config-Space Number of functions found [out ] Programming Manual, 11/2011, J31069-D2131-U001-A

54 IMCEA API functions 5.7 PCI address space processing functions Return value Value ERROR_SUCCESS ERROR_INSUFFICIENT_BUFFER ERROR_INVALID_HANDLE No errors The data structures to/from the driver are incorrect Handle is invalid Programming example /* all PCI devices shall be looked for */ dwretcode = ImcEADrvSearchPCI(hDrvHandle, 0xffffffff, 0xffffffff, 0, 0, ConfigSpace, sizeof(configspace)/sizeof(pci_config_space), &NumOfFunctions); if(dwretcode!= ERROR_SUCCESS) { printf("imceadrvsearchpci: Error 0x%lx\n", dwretcode); } 54 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

55 PC IO API functions Introduction The PC IO API is based on the IMCEA API. It provides functions for access to PC IO basic modules with analog or digital I/O modules. The provided PC IO API functions can be broken down into the following groups: General functions Analog I/O functions Pt100 functions Digital I/O functions Diagnostic functions Note The PC IO API is only available as a 32-bit version. Note All the functions described in the following chapters have been tested with Visual Studio 2005, 2008, and NOTICE The functions of the PC IO API on the PC IO basic module require the FPGA firmware version V1.3 and the microcontroller firmware version V1.4. If your module has an older firmware version, contact Support if necessary. See also Service and support (Page 97) Programming Manual, 11/2011, J31069-D2131-U001-A

56 PC IO API functions 6.2 General API functions 6.2 General API functions Overview of the general API functions Available functions The PC IO API offers the following general functions: Function PcioInit() PcioClose() PcioGetBaseAddress() PcioWaitForIRQ() Initialize PC IO API Free resources of an initialized PC IO API again Request the start address of a PC IO basic module Wait for an interrupt from a PC IO basic module Use of the functions Before a program can access a PC IO basic module, the PC IO API must be initialized by means of the call "PcioInit()". It searches in the system for plugged-in modules and requests resources from the operating system. They must be freed again by means of the call "PcioClose()" at the end of the program. Note If the PC IO API is to be used in multitasking operation, then the initiating call "PcioInit()" can only be invoked once at the beginning of the application. If the API has already been initialized, then certain resources in the system are exclusively reserved and subsequent calls of "PcioInit()" of other tasks return with an error message. With the API correctly initialized once, one or more PC IO modules can then be accessed in multitasking mode. Data types used The general functions use the following data types: typedef PcioResult int; /* Type of return values of all functions of the PC IO API. The meanings of the individual values are defined in the file pcio.h and can be found in the description of the respective function. */ 56 Programming Manual, 11/2011, J31069-D2131-U001-A3-7618

57 PC IO API functions 6.2 General API functions Data structures used The general functions use the following data structures: typedef struct tagpcioboardlist { unsigned int Count; /* Number of elements in the field Boards */ PcioBoard *Boards; /* Each element in the field represents a PC IO basic module. */ } PcioBoardList; typedef struct tagpcioboard { unsigned int BaseAddress; unsigned char IntLine; HANDLE DriverHandle; unsigned char FPGAVersion; unsigned char MCVersion; PcioModuleList ModuleList; } PcioBoard; /* Start address of the PC IO basic module */ /* Interrupt line which the PC IO basic module received from the Interrupt Controller */ /* IMCEA driver handle with which the PC IO API accesses the PC IO basic module */ /* Version ID of the FPGA of the PC IO basic module */ /* Version ID of the microcontroller of the PC IO basic module */ /* List of the plugged-in modules detected during power-up */ typedef struct tagpciomodulelist { unsigned int Count; /* Number of elements in the field Modules */ PcioModule *Modules; /* Pointer to the field with PcioModules. Each element in the field represents a module inserted in the PC IO basic module and detected during power-up */ } PcioModuleList; typedef struct tagpciomodule { PcioSlot Slot; /* Slot of the PC IO basic module where the module is inserted */ PcioModuleType Type; /* Module type */ PcioModuleDiagnostics DiagnosticInfo; /* Diagnostic information via the module */ } PcioModule; Programming Manual, 11/2011, J31069-D2131-U001-A