Home

CIF WinAC Driver

1. 15 3t WinAC Basis WinAC RTX Ces 15 4 STEP 7 Project Creation and Configuration 20urr000nnn00n0n0nnnnnannnnnnnnnnnnnnnnnnnnnnannnnnnnnnannnnnannnnnn 16 4 1 Install the CIF Hardware and its Device Drivers 16 4 2 Create a Fieldbus Configuration with SyCon sse 17 4 3 Create a new STEP7 Project 17 4 4 Configure the CIF Devices used in the STEP7 Project 19 4 5 Setup O Data Update Halte ird e tnter b cete e MEC EE ERE MERGE 21 4 6 Asynchronous Message Transfer c cccecccececeeeeeceeeeneneeeeeeeneeeeeseeeeeeaneeeeenensecesseneeeesnenaeeeenenees 22 4 7 Ertor CReCklngy intet eb e fiie been cit ete ren ctetu la etii cvi ogg 24 5 Fieldbus GonfigUuratiOn 22 i core een a and 25 54 Fieldbus Startup BelaviOUE io eut cene eec e cte endl elie dale odin ee eg 26 5 2 Auto Addressing suere edet u en enden 26 5 3 Handshake of the Process Data 27 5 4 User Program Monitoring rn ee ee erre ee Deed ned nee a era 27 6 CIF Win AG DTEIVer E 28 6 1 Driver Loading Initialization and Hemovimg eren 29 Gril WIDAG Basis iiie etude eu IRE 29 6 1 2 WINAC RTX c E 29 6 2 Driver FUnctloris eer tt eo t x ert a a a retire Eege AE RU Ina de E E De ew quts 30 0 3 Initialization Greter 31 6 4 WO Data Transfer between CIF Cards and Process Image sse 31 7 STEP 7 Prog rau see eec deett fed Ee 32 Jjt P
2. Transfer slave state information to the slave state map FB4 CIFACWriteOutput 4 Write OUTPUT data to CIF devices Transfer slave state information to the slave state map FB5 CIFACReadSlaveConfig 2 Read a slave configuration information into a given DB FB6 CIFACReadDevicelnfo 12 Reads global information about a device into a given DB FB7 CIFACWriteMsg 7 Write a messages to the CIF device FB8 CIFACReadMsg 8 Read a messages from the CIF device Table 16 Function Blocks 7 3 1 FB2 CIFACDriverlnit Description Initialize all devices configured in DB CONFIG Direction out Type WORD Parameter Description ERROR Error return Table 17 FB2 CIFACDriverlnit 7 3 2 FB3 CIFACReadlnput Description Read the input process data from the CIF hardware and store the data into the input image map DB_I_MAP_DEVICEx of the device Direction Type Parameter Description in BLOCK_DB DB_CONFIG Global configuration data block in INT DEV Device number 0 process all devices 1 4 process specific device out WORD ERROR Error return Table 18 FB3 CIFACReadinput CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Program 36 48 7 3 3 FB4 CIFACWriteOutput Description Write the output process data to the CIF hardware used the data from the output image map DB Q MAP DEVICEX of
3. eviceumer s STRINGIS Lk Device number of the device 0 not checked SerialNumber Temamerei Ir k Serial number of the device 0 not checked t configurationFileName sTRING 100 k Configuration data base path and file e g C test TEST DBM FirmvareDomload sm je Lk Initiate automatic firmware download e g C YtestiFirnvareY perm Im jo fe Haber ef che corresponding INPUT MAP DB pe omar m bo e uber of the corresponding OUTPUT MAP DB IDB_SLAVE sTaTe Map Im o Lk Number of the corresponding SLAVE STATE MAP DB Eu UM 1290 0 stat PROGID STRING 254 CIFACDriver ProgID of Device Driver DO NOT CHANGE p De THIN Fehler 2 nto EE Dr cken Sie F1 um Hilfe zu erhalten offline Abs Einfg Ui Figure 3 STEP7 Declaration View of DB_CONFIG Data description Error Error return value for FB2 INIT_OK Local initialization state must be cleared on beginning of OB100 SFB_CREA_COM SFB_EXEC_COM WinAC interface to access third party software Accessed via multi instance DEVICE ARRAY 1 4 Device structure allows up to four CIF devices at the same time DeviceType Name of the CIF device like defined in the Supported Devices Table e g CIFS50CAN BoardNumber Can be obtained from the CIF device driver if WinAC Basis is used On WinAC RTX the CIF WinAC Driver automatically enumerates the devices In this case board numbers are c
4. ERROR INTERNAL An internal error occurred 0x8001 E EXCEPTION An exception occurred 0x8002 E NO VALID INPUT Input the ANY pointer is invalid 0x8003 E_INPUT_RANGE_INVALID Input the ANY pointer range is invalid 0x8004 E NO VALID OUTPUT Output the ANY pointer is invalid 0x8005 E OUTPUT RANGE INVALID Output the ANY pointer range is invalid 0x8006 E OUTPUT OVERFLOW More bytes were written into the output buffer by the extension object than were allocated 0x8007 E_ NOT INITIALIZED ODK system has not been initialized no previous call to SFB65001 CREA COM 0x8008 E HANDLE OUT OF RANGE The supplied handle value does not correspond to a valid extension object 0x8009 VE INPUT OVERFLOW More bytes were written into the input buffer by the extension object than were allocated Table 25 Error Numbers WinAC RTX Error List CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Error Numbers 8 3 CIF WinAC Driver Error List 41 48 Value Name Description 0 NO ERROR Success 1 GLOBAL ERROR Check device error values Errors from underlying hardware driver CIF Device Driver C IF RTX driver 1000 DRIVER ALREADY OPENED 1001 DRIVER DLL NAME INVALID 1002 DRIVER DLL NOT FOUND 1003 DRIVER FUNCTION MISSING 1004 DRIVER FUNCTION FAILED 1005 DRIVER DEVICE NAME INVALID 100
5. This enables the application to be fully initialized before starting the fieldbus communication Fieldbus Startup Behaviour Automatic release of the communication by the device The fieldbus system will start up as soon as the card has finished it S power on sequence Controlled release of the communication by the The start of the fieldbus system can be controlled by an application program recommended default application NOTE The WinAC driver always starts without starting the fieldbus system Therefore an explicit start function must be executed within the application 5 2 Auto Addressing SyCon allows to setup the way how the slave process data are sorted into the process data image of the master device Auto addressing enabled forces SyCon to place the slave process data in an increasing order starting at offset 0 into the process data image of the master device The slaves are processed in the order like they are inserted into the fieldbus configuration Auto addressing disabled allows the user to manually assign the process data position for each slave in the process data image of the master device SyCon provides the possibility to review the created address table Auto Addressing Auto addressing ENABLED default SyCon automatically places the slave process data into the master process data image starting at offset 0 Auto addressing DISABLED User manually place
6. USER file read failed 104 DRV USR INVALID FILETYPE USER file type invalid 105 DRV USR FILENAME INVALID USER file name not valid 110 DRV FW FILE OPEN FAILED USER firmware file not opened 111 DRV FW FILE SIZE ZERO USER firmware file size zero 112 DRV FW FILE NO MEMORY 113 DRV EW FILE READ FAILED 114 DRV FW INVALID FILETYPE 115 DRV_FW_FILENAME_INVALID USER not enough memory to load firmware file USER firmware file read failed USER firmware file type invalid USER firmware file name not valid 116 DRV_FW_DOWNLOAD_ERROR USER firmware file download error 117 DRV_FW_FILENAME_NOT_FOUND USER firmware file not found in the internal table 118 DRV_FW_BOOTLOADER_ACTIVE 119 DRV FW NO FILE PATH USER firmware file BOOTLOADER active USER firmware file not file path 120 DRV CF FILE OPEN FAILED USER configuration file not opened 121 DRV CF FILE SIZE ZERO USER configuration file size zero 122 DRV CF FILE NO MEMORY USER not enough memory to load configuration file 123 DRV CF FILE READ FAILED USER configuration file read failed 124 DRV CF INVALID FILETYPE USER configuration file type invalid 125 DRV CF FILENAME INVALID USER configuration file name not valid 126 DRV CF DOWNLOAD ERROR USER configuration file download error 127 DRV_CF_FILE_NO_SEGMENT USER no flash segment in the configuration file 128 DR
7. Message enaere ar eeoa aaaeeeaeo enora N aa Eea haear aeaio aeea Eaa ieaie naa aar tis 22 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020 701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 Appendix 9 3 Contacts Headquarters Germany Hilscher Gesellschaft f r Systemautomation mbH Rheinstrasse 15 65795 Hattersheim Phone 49 0 6190 9907 0 Fax 49 0 6190 9907 50 E Mail info hilscher com Support Phone 49 0 6190 9907 99 E Mail de support hilscher com Subsidiaries China Hilscher Ges f Systemaut mbH Shanghai Representative Office 200010 Shanghai Phone 86 0 21 6355 5161 E Mail info hilscher cn Support Phone 86 0 21 6355 5161 E Mail cn support hilscher com France Hilscher France S a r l 69500 Bron Phone 33 0 4 72 37 98 40 E Mail info hilscher fr Support Phone 33 0 4 72 37 98 40 E Mail fr support hilscher com India Hilscher India Pvt Ltd New Delhi 110 025 Phone 91 9810269248 E Mail info hilscher in Italy Hilscher Italia srl 20090 Vimodrone MI Phone 39 02 25007068 E Mail info hilscher it Support Phone 39 02 25007068 E Mail it support hilscher com CIF WinAC Driver WinAC Basis and WinAC RTX 48 48 Japan Hilscher Japan KK Tokyo 160 0022 Phone 81 0 3 5362 0521 E Mail info hilscher jp Support Phone 81 0 3 5362 0521 E Mail jp support hilscher com Switzerland Hilscher Swiss GmbH 4500
8. Monitoring SyCon allows to setup the device watchdog time This time is used to shout down the fieldbus system in case of an abnormal program behaviour User Program Monitoring Watchdog time Timeout until the fieldbus will be stopped in case of an abnormal program behaviour 1000 ms Default 0 ms Function disabled CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 CIF WinAC Driver 28 48 6 CIF WinAC Driver The following section describes the internal driver functions The WinAC Basis driver is based on the CIF Device Driver interface Cif32DLL DLL The WinAC RTX driver is based on the CIF RTX Driver CIFRTXDriver rtdll WinAC Basis and WinAC RTX are using a different way to call the driver The basis version uses a COM interface and the RTX version uses a calling interface The connection between the STEP7 part of the program and the CIF WinAC Driver is done by two SFBs SFB65001 CREA COM creates loads the CIF WinAC Driver CREA COM uses the parameter PROGID INSTANCEID to define the used program On WinAC Basis the parameter must be defined as CIFACDriver CIFACDriver and WinAC RTX needs the entry RTSS CifACRTXDriver rtall SFB65002 EXEC_COM is used to access the driver functions It uses a handle to the driver created by CREA_COM CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2
9. Solothurn Phone 41 0 32 623 6633 E Mail info hilscher ch Support Phone 49 0 6190 9907 99 E Mail ch support hilscher com USA Hilscher North America Inc Lisle IL 60532 Phone 1 630 505 5301 E Mail info hilscher us Support Phone 1 630 505 5301 E Mail us support hilscher com DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009
10. Wrong or no interrupt selected Check interrupt on the device and in driver registration They have to be the same Interrupt already used by an other PC component The used protocol on the device needs longer than the timeout period given in the DevGetMessage function Error 20 The device needs longer than the timeout period given in the DevReset function Using device interrupts This error occurs when for example interrupt 9 is set in the driver registration but no or a wrong interrupt is jumpered on the device device in pollmode Interrupt already used by an other PC component The timeout period can differ between fieldbus protocols Error 21 The device can not reach communication state Device not connected to the fieldbus No station found on the fieldbus Wrong configuration on the device Error 23 The device needs longer than the timeout period given in the DevExchangel o function Using device interrupts Wrong or no interrupt selected Check interrupt on the device and in driver registration They have to be the same Interrupt already used by an other PC component Error 30 The device driver could not be opened Device driver not installed Wrong parameters in the driver configuration If the driver finds invalid parameters for a communication board and no other boards with valid parameters are available the driver will not be loaded Error 33 A driver function could not be
11. called This is an internal error between the device driver and the DLL Make sure to use a device driver and a DLL with the same version An incompatible old driver DLL is used CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Appendix 47 48 9 Appendix 9 1 List of Tables Table 15 Listo Revisions oui e ERU REDEEM REUS ADU E ere it eai tisse 5 Table 2 References to Additional Information 2 ccccccceceeeeeeenceeeeeeeeeeeeeaaeeeeeeeseeaaaeeeeeeeeeeccaaeeeeeeeeeceaaeeeseeeseecnnieeeeeeess 5 IE KHeBESII UC 8 Table 4 Requirements WinAC Basis V3 x SP1 IA 10 Table 5 Requirements WinAC RTX V3 x 4 0 V4 1 iisssssssssssssssssssssseeee eene eene en nenne nnne n enne nennen rennen nnn 10 Table 6 Requirements WinAC RTX 200p eene nnne nennen snnt nntn sn etr enne rene nnn nnne nnn neni 10 Table 7 Requirements WinAC RTX 2008 11 Table 8 Requirements WinAC HIN 2000 11 Table 9 Supported CIF Cards and Fieldbus Systems Part 71 13 Table 10 Supported CIF Cards and Fieldbus Systems Part 2 seen 14 Table 11 Driver Loading Initialization and Removing WinAC Basis mens 29 Table 12 Driver Loading Initialization and Removing WinAC HIN 29 Fable 13 Driver F nctons ierit ree t eee an ER Reto Eleg eres soot eser Baie EE eebe eege Eh 30 Table 14 P
12. data type mismatch 164 DEN CF MODULE DEF MISSING NO SI CONFIG Module definition is missing no Slot Idx gt 1000 RCS ERROR Board operation system errors will be passed with this offset e g error 1234 means RCS error 234 Only if a ready fault occurred during board initialization Table 27 Error Numbers CIF Device Driver Error List CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Error Numbers 45 48 8 4 1 Additional Error Information This section contains more information about possible reasons to certain error numbers Error 1 The communication board is not initialized by the driver No or wrong configuration found for the given board Check the driver configuration Driver function used without calling DevOpenDriver first Error 6 The device driver version does not corresponds to the driver DLL version From version V1 200 the internal command structure between DLL and driver has changed Make sure to use the same version of the device driver and the driver DLL Error 10 Dual ported RAM DPM not accessible no hardware found This error occurs when the driver is not able to read or write to the DPM Check the BIOS setting of the PC Memory address conflict with other PC components try another memory address Check the driver configuration for this board Check the jumper setting of t
13. detailed information about RCS messages please consult the manual CIF Toolkit tke pdf and for the protocol specific message commands the corresponding protocol interface manual e g DPM_pie pdf gt PROFIBUS DP Master protocol interface manual CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 24 48 4 7 Error Checking CIFAC_Status_Word MW 60 is a global word which will receive error values If the value is 0 after returning from a FB call no error occurred Value 1 indicates device specific errors These errors are inserted into the value DeviceError located in the device array in DB_CONFIG Error numbers 1 are defined as global errors NOTE OB100 always stops on all errors from FB2 Also if two fieldbus systems are installed and one of them can t be started The user is responsible to change the error handling in OB100 to allow a system to start if one of the defined master devices or fieldbus systems does not work CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Fieldbus Configuration 25 48 5 Fieldbus Configuration This section describes how to configure a CIF master device NOTE Please consult the SyCon user manual for a detailed description how to create a valid fieldbus configuration and how to change t
14. 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 1 3 2 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
15. the slave process data into the masters process data image NOTE Consult the SyCon manual about a closer description CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 Fieldbus Configuration 27 48 5 3 Handshake of the Process Data Handshake modes are used to control the access to the I O process data image between the PC Host and the CIF card Device The setting of the transfer mode is very important because it will influence the consistency of the process data and the fieldbus behaviour Transfer modes are only available on master cards The modes are configured via SyCon which offers up to six modes depending on the used CIF hardware and fieldbus system Handshake Mode Supported Bus synchronous device controlled NO Only possible on dedicated systems because the system must respond during a bus data cycle which can be less than 350 micro seconds Buffered device controlled YES No consistence uncontrolled YES Not recommended process data which are not of the type byte can be transferred inconsistent Buffered host controlled recommended default YES Bus synchronous host controlled YES Not on all fieldbus systems and CIF cards available System is responsible to drive the bus Buffered extended host controlled NO 5 4 User Program Monitoring Under User Program
16. wide range of SIMATIC WinAC versions The minimum software requirements are listed below Please notice that you need a valid Hilscher hardware license code to use a CIF Device 2 3 1 WinAC Basis V3 x SP1 V4 1 Sofware Wem S SS SyCon Fieldbus System Configurator CIF WinAC Driver for WinAC Basis V3 x SP1 V4 1 V1 200 Hardware driver for ISA PCMCIA PCI cards CIF Device Driver V3 015 for Windows NT or V3 015 CIF Device Driver for Windows 2000 XP V3 120 or higher Table 4 Requirements WinAC Basis V3 x SP1 4 1 2 3 2 WinAC RTX V3 x V4 0 V4 1 Sofware Wem SyCon Fieldbus System Configurator Hardware driver for ISA and PCI cards Table 5 Requirements WinAC RTX V3 x 4 0 V4 1 2 3 8 WinAC RTX 2005 Sofware Wem S SS Siemens SIMATIC WinAC RTX 2005 Siemens SIMATIC Step 7 V5 3 SP 3 or higher SyCon Fieldbus System Configurator V2 814 or higher CIF WinAC Driver for WinAC RTX 2005 V2 004 Hardware driver for ISA PCMCIA PCI cards CIFRTXDriver for Ardence RTX 6 5 V1 110 Table 6 Requirements WinAC RTX 2005 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 11 48 2 3 4 WinAC RTX 2008 Gebuer 777 yS Siemens SIMATIC WinAC RTX 2008 Siemens SIMATIC Step 7 V5 4 SP 3 or higher Hilscher SyCon Fieldbus System Configurator V2 814 or higher CIF WinAC Driver for WinAC RTX 2008 2009 V
17. 009 09 Released Public Hilscher 2009 CIF WinAC Driver 6 1 29 48 Driver Loading Initialization and Removing The CIF WinAC Driver will be called during different WinAC states to carry out its functions 6 1 1 WinAC State WinAC Basis Description Loading of WinLC During the start of WinLC Logic Controller the COM interface to the driver will be instanciated At this time the driver object is generated and the APIs of the underlying hardware drivers are loaded by LoadLibrary Unloading of WinLC Unloading of the Logic Controller will remove the COM interface which also closes the hardware drivers frees API DLLs and destroys the driver object Activate DevOpenDriver of the loaded hardware drivers will be called Deactivate DevCloseDriver of the loaded hardware drivers will be called Execute Calls the driver functions described in the section Driver Functions Table 11 Driver Loading Initialization and Removing WinAC Basis 6 1 2 WinAC RTX WinAC State Description ODKCreate During the start of WinLC Logic Controller the COM interface to the driver will be instanciated At this time the driver object is generated and the APIs of the underlying hardware drivers are loaded by LoadLibrary ODKRelease Unloading of the Logic Controller will remove the COM interface which also closes the hardware drivers frees API DLLs and destroys the driver object Ac
18. 3 000 Hardware driver for ISA PCMCIA PCI cards CIFRTXDriver for IntervalZero RTX 8 1 V1 110 Table 7 Requirements WinAC RTX 2008 2 3 5 WinAC RTX 2009 Software Version Siemens SIMATIC WinAC RTX 2009 Siemens SIMATIC Step 7 V5 4 SP 4 or higher Hilscher SyCon Fieldbus System Configurator V2 814 or higher CIF WinAC Driver for WinAC RTX 2008 2009 V3 000 Hardware driver for ISA PCMCIA PCI cards CIFRTXDriver for IntervalZero RTX 8 1 V1 110 Table 8 Requirements WinAC RTX 2009 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 12 48 2 4 Features WinAC Basis V3 x 4 0 4 1 Hardware detection and setup for ISA PCMCIA PCI by standard driver functions WinAC RTX all versions Automatic hardware detection for ISA and PCI hardware by the CIF RTX driver Asynchronous fieldbus protocol services CIF WinAC Driver V2 004 and higher General Device selection by name and board number All supported devices can be used simultaneously Up to four devices possible Automatic firmware comparison and download during startup possible Automatic configuration comparison and download during startup possible Unique device selection of the hardware by serial and device number possible including automatic card replacement detection Fieldbus configuration by SyCon no fieldbus configuration in STEP7 needed Slave I O data are m
19. 4 0 4 1 CIF Device Driver and its components CIF RTX Driver V1 106 for VenturCom RTX V4 3 2 1 5 x CIF WinAC Driver V2 004 for WinAC RTX 2005 CIF RTX Driver V1 110 for Ardence RTX 6 5 CIF WinAC Driver V3 000 for WinAC RTX 2008 2009 CIF RTX Driver V1 110 for IntervalZero RTX 8 1 NOTE The Hilscher product CD does not include any Siemens components Please contact Siemens how to obtain their products and how to install them We suggest to first install the Siemens software The Hilscher installation procedure at first runs the SyCon installation Afterwards it starts the installation of the WinAC driver and the CIF device drivers Each installation provides product specific options like a standard destination directory which can be changed All components will be copied to the selected destination directories and their necessary registration procedures are processed 3 1 WinAC Basis Win AC RTX Step1 Install STEP7 like described by Siemens Step2 Install WinAC Basis or RTX like described by Siemens Step3 Start the setup program from the Hilscher product CD CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 16 48 4 STEP 7 Project Creation and Configuration This chapter describes how to create anew STEP 7 project including Hilscher fieldbus support Step1 Install and configure the CIF hardware and the nece
20. 43 DRV_USR_SIZE_TOO_LONG USER Parameter Size too long Hilscher 2009 Error Numbers 43 48 Value Name Description Hint 44 DRV_USR_DEV_PTR_NULL USER Device address null pointer 45 DRV_USR_BUF_PTR_NULL USER Pointer to buffer is a null pointer 46 DRV_USR_SENDSIZE_TOO_LONG USER Parameter SendSize too long 47 DRV_USR_RECVSIZE_TOO_LONG USER Parameter ReceiveSize too long 48 DRV USR SENDBUF PTR NULL USER Pointer to send buffer is a null pointer 49 DRV USR RECVBUF PTR NULL USER Pointer to receive buffer is a null pointer 50 DRV DMA TIMEOUT CH4 DMA read IO timeout 51 DRV_DMA_TIMEOUT_CH5 DMA write IO timeout 52 DRV DMA TIMEOUT CH6 DMA PCI transfer timeout 53 DRV DMA TIMEOUT CH7 DMA download timeout 54 DRV_DMA_INSUFF_RES_MEM DMA Memory allocation error 70 DRV_ERR_ERROR DRIVER General error 71 DRV_DMA_ERROR DRIVER General DMA error 72 DRV_BATT_ERROR DRIVER Battery error 73 DRV_PWF_ERROR DRIVER Power failed error 80 DRV_USR_DRIVER_UNKNOWN USER driver unknown 81 DRV USR DEVICE NAME INVALID USER device name invalid 82 DRV USR DEVICE NAME UKNOWN USER device name unknown 83 DRV USR DEVICE FUNC NOTIMPL USER device function not implemented 100 DRV USR FILE OPEN FAILED USER file not opened 101 DRV USR FILE SIZE ZERO USER file size zero 102 DV USR FILE NO MEMORY 103 DRV USR FILE READ FAILED USER not enough memory to load file
21. 6 DRIVER DEVICE TYPE UNKNOWN 1007 DRIVER FW FILENAME NOT FOUND 1008 DRIVER DEVICE NUMBER INVALID 1009 DRIVER SERIAL NUMBER INVALID Errors from the CIFWinAC driver 0x8510 E COMMAND NOT IMPLEMENTED Invalid subcommand number 0x8520 E COMMAND UNKNOWN DRIVER Driver unknown 0x8521 E COMMAND UNKNOWN DEVICE Device unknown 0x8522 E COMMAND MEMORY NOT AVAILABLE Internal memory not available 0x8523 E COMMAND UNKNOWN MODE Mode parameter unknown 0x9030 E COMMAND DEVICE ERROR Global device error 0x9031 E COMMAND INVALID INPUT SIZE Input size of defined DB invalid 0x9032 E COMMAND INVALID OUTPUT SIZE Output size of defined DB invalid 0x9033 E COMMAND INVALID DEVICE NUMBER Invalid device number given 0x9034 E COMMAND INVALID DEVICE HANDLE Invalid device handle found 0x9035 E COMMAND DEVICE ALREADY ACTIVE Device already active 0x9040 E COMMAND CFG INP DIRECTION ERROR Device configuration input direction error 0x9041 E COMMAND CFG INP DATATYPE ERROR Device configuration input data type error 0x9042 E COMMAND CFG OUT DIRECTION ERROR Device configuration output direction error 0x9043 E COMMAND CFG OUT DATATYPE ERROR Device configuration output data type error Table 26 Error Numbers WinAC Driver Error List CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Error Numbers 8 4 CIF Device Dri
22. CIF WinAC Driver V1 002 2 2005 11 29 V2 000 All CIF WinAC Basis RTX Driver V1 200 for WinAC 3 x 4 1 CIF WinAC RTX Driver V2 000 for WinAC RTX 2005 Information about background UO data processing included Supported hardware and fieldbus table extended Support for CIF100 cards removed 3 2009 09 02 V2 004 2 2 3 4 3 CIF WinAC RTX Driver V2 004 for WinAC RTX 2005 v3 000 6 27 CIF WinAC RTX Driver V3 000 for WinAC RTX 2008 2009 Requirements and installation instructions for WinAC RTX 2008 and WinAC RTX 2009 included CIFRTX driver version updated to V1 110 Driver functions for asynchronous message transfer added Table 1 List of Revisions 1 2 References to Additional Information Please use the listed manuals if you are searching additional information Manual name Content CIF Device Driver General driver description functions and API Protocol Manual General protocol information and definition Protocol Interface Manual Protocol specific definitions and functions CIF Toolkit Manual General message definitions for asynchronous commands SDOs Table 2 References to Additional Information CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 Introduction 6 48 1 3 Legal Notes 1 3 1 Copyright 2002 2009 Hilscher Gesellschaft f r Systemautomation mbH All rights reserved The images
23. DB CONFIG DB CONFIG DEV 0 process all devices ERROR CIFAC Status Word Network2 Stop PLC on read input error CIFAC Status Word lt gt 0 USER PROGRAMM Network n Write outputs to bus CALL CIFACWriteOutput DB CIFACWriteOutput DB CONFIG DB CONFIG DEV 0 process all devices ERROR CIFAC Status Word Network n 1 Stop PLC on write output error CIFAC Status Word lt gt 0 Table 14 Program Structure CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Program 34 48 7 2 Data Organization DB_CONFIG is the global configuration data block and the only one which has to be changed CIFAC_Status_Word is the global error value for all FBs Each device uses at least three data blocks DB MAP DB Q MAP DB SLAVE STATE MAP Other data blocks like DB SLAVE CFG DB DEVICE INFO DB MSG WRITE and DB MSG READ are predefined for specific functions NOTE Do not change the structure and length of any data block except the DB 1 MAP and DB Q MAP blocks Global Data Definition Description MW 60 CIFAC Status Word Global state error word for all FBs Data Block Definition Description DB2 DB_CONFIG Global configuration data block DB3 DB4 DB5 DB6 Instance DB Instance DBs for function blocks FB3 FB4 FB5 FB6 DB1000 DB SLAVE CFG Standard data block to read a slave conf
24. EM AC hilsc 7 COMPETENCE IN COMMUNICATION Driver Manual CIF WinAC Driver WinAC Basis and WinAC RTX WinAC Basis 3 x 4 1 WinAC RTX 3 x 4 0 4 1 2005 2008 2009 Hilscher Gesllschaft f r Systemautomation mbH www hilscher com DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Table of Contents 1 IntroductiOn 2 2 rc 5 Tel List Of Revisions eisien lH NEID 5 1 2 References to Additional Information 5 1 3 EN e Ee 6 TIt Copyright oie te urn cde Dae ed eu Ee oT keins 6 1 3 2 Important NOIBS nien nmm pietre cce iri CU uci Rec wie T ERE eene 6 13 S Exclusion ot Liability an ee ea enden ehren 7 1 9 4 EXON niece dice cu es EE RON DE eto EE nt biete teeth 7 2 About the Driver sia eege EES co ceca zz cd ante acc zc reo Eve de SE EES 8 2A CDi COntemts viscccsixsessd EET 8 272 Implementation t dae Pp Se t NE Ed ee ieu ie i APR e RM tpa tex Sene dia 9 E Mie 9 2 2 2 WINAC RTX 2 ae anna nn NIE eeu seuss Rn AED ER On 9 PAR WE e UE 10 2 3 4 WinAC Basis V3 9P 17 V4 iiiter mee nM 10 2 3 2 WinAG REX V3 4 VAN MA eicere cte htec ete nie iege rra ec des 10 2 33 WIDnAG RTX 2005 eoi ebbe EE 10 23 4 VW n D 00S E tere E OIM nen te D ene e 11 2 3 5 WinAC RTX 2009 scie ener nete nennen nn an rinnen da teer oda erint 11 p EN 51 7 1611 1 RM 12 PERS BICI EPIIT TES 12 2 6 Supported CIF Cards and Fieldbus Gvstems sse 13 3 IEEE E
25. FACBasisProg WinAC RTX gt CIFACRtxProg WinAC RTX 2005 gt CIFACRtx2005Prog WinAC RTX 2008 gt CIFACRtx2008Prog WinAC RTX 2009 gt CIFACRtx2009Prog otherwise SFB65001 and SFB65002 are not working correctly After creating a STEP7 project the CIF WinAC Driver must be configured The configuration takes place in the DB CONFIG DB2 and has to match the installed CIF hardware CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 19 48 4 4 Configure the CIF Devices used in the STEP7 Project The configuration of the CIF WinAC Driver and the used CIF hardware takes place in DB CONFIG All other FBs are based on this data block DB CONFIG is the instance data block of FB2 ii KOP AWL FUP DB2 Of x Datei Bearbeiten Einf gen Zielsystem Test Ansicht Extras Fenster Hilfe ojala ai el 1 edil s Lis m DB2 CIFACBasisProg SIMATIC PC Station 1 w inLC V3 0 fitresse peuape fe Tantangswrt ect let pem oo ben error mes 4 0istet SFB CREA con Je cREA CON ua instance for SFB CREA CON 262z D stat Je oer com srp pxec com Multi instance for SFD EXEC COM 290 olstas pvict ra ENG a y S DeviceType emmersi t k gt Hilscher Device Type e g CIFSOCAN Border mr Lk Number of the board plugged into the PC Board number 0 3
26. Hilscher CIF WinAC driver requires a license code on the CIF hardware An Error 14 will be reported if there is no license code on the hardware found General Limitations The Hilscher CIF WinAC driver only supports Modular I O Slave Devices with not more than 60 defined modules New Feature The Hilscher CIF WinAC driver now supports asynchronous fieldbus protocol services like SDOs Please notice that this feature is restricted to the CIF WinAC Driver for WinAC 2005 2008 and 2009 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Introduction 5 48 1 Introduction WinAC Windows Automation Center is a product line from the Siemens AG and designed as an integrated solution for Control HMI Networking and Data Processing WinAC is able to use a standard PC as the hardware platform to run all of it s functionality s One of the modules is WinLC Windows Logic Controller which turns the PC into a SoftPLC Since offering an Open Development Kit WinAC ODK WinAC RTX ODK it is possible to extend WinAC by custom functionality s It is also possible to directly interact with the program scan cycle of WinLC These functionality s have been used to implement the Hilscher Communication InterFaces CIF into WinAC Basis and WinAC RTX systems 1 1 List of Revisions Rev Date Version Chapter Revision 1 2002 06 24 V1 000 All Created
27. IFACRTX2009Prog CIFACRtx The program allows to run up to four master devices with the same or different fieldbus systems simultaneously All necessary configuration data and runtime states are placed into one single data block named DB_CONFIG DB2 This data block contains the instances for SFB65001 and SFB56002 all necessary device configuration data to select the master devices CIF cards and the information about device specific data blocks which are used during runtime The program design allows an easy integration of the CIF WinAC driver into an existing STEP7 project SFB65001 and SFB65002 are accessed via multi instances so other program parts are also able to uses these SFBs All driver data blocks are configured in DB_CONFIG so they can be renamed and only the information about the used data blocks in DB_CONFIG must be changed CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Program 7 1 Program Structure 33 48 Organization Function Block OB100 Network Reset INIT_OK flag located in DB_CONFIG U DB CONFIG INIT OK H DB CONFIG INIT OK Network2 Start CIF driver and initialize all devices CALL CIFACDriverlnit UB CONFIG ERROR CIFAC Status Word Network3 Stop on initialization errors CIFAC Status Word lt gt 0 OB1 Network1 Read inputs CALL CIFACReadlnput DB CIFACReadlnput
28. US DP SIMATIC 300 SIMATIC 400 H SIMATIC PC Based Control 300 400 amp SIMATIC PC Station fg Controller gl winLc v3 0 CP G HMI Lg User Application u 0 PC p 9 9 8 BES 511 1 PYOO OYB inLC V3 0 Windows Logic Controller f r indows NT DP Anschlu DP Master Einf gen m glich And 7 Figure 1 STEP7 Hardware Configuration NOTE You will see WinLC RTX when working in a WinAC environment CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 18 48 Step4 Change to the program folder in the STEP7 project and insert OB1 OB100 SFB65001 and SFB65002 and all FBs and DBs from the example project Insert also the symbols from the example project RJ SIMATIC Manager CIFACBasisProg CE x Datei Bearbeiten Einf gen Zielsystem Ansicht Extras Fenster Hilfe plela x ele val e was CIFACBasisProg ig 06100 E S SIMATIC PC Station 1 ij FB3 ER wince v3 0 i FB5 Fez 57 Programm 1 ig DB2 g Quellen ia DB4 n F Bausteine iz DBE iz D81001 ig D81102 Si lt Kein Filter 3 DB1201 3 DB1203 3 DB1302 DB1401 3 DB1403 CA SFB65001 3 SFC46 Dr cken Sie F1 um Hilfe zu erhalten Figure 2 STEP7 Project View NOTE Make sure to use the example program which corresponds to the WinAC system WinAC Basis CI
29. V_CF_DIFFERS_FROM_DBM USER configuration file differs from database 131 DRV_DBM_SIZE_ZERO 132 DRV_DBM_NO_MEMORY USER database size zero USER not enough memory to upload database 133 DRV_DBM_READ_FAILED USER database read failed CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Error Numbers 44 48 Value Name Description Hint 136 DRV DBM NO FLASH SEGMENT USER database segment unknown 150 DEV CF INVALID DESCRIPT VERSION CONFIG version of the Descript table invalid 151 DEV CF INVALID INPUT OFFSET CONFIG input offset is invalid 152 DEV CF NO INPUT SIZE CONFIG input size is 0 153 DEV_CF_MISMATCH_INPUT_SIZE CONFIG input size does not match configuration 154 DEV_CF_INVALID_OUTPUT_OFFSET CONFIG invalid output offset 155 DEV_CF_NO_OUTPUT_SIZE CONFIG output size is 0 156 DEV_CF_MISMATCH_OUTPUT_SIZE CONFIG output size does not match configuration 157 DEV_CF_STN_NOT_CONFIGURED CONFIG Station not configured 158 DEV_CF_CANNOT_GET_STN_CONFIG CONFIG cannot get the Station configuration 159 DEV CF MODULE DEF MISSING CONFIG Module definition is missing 160 DEV CF MISMATCH EMPTY SLOT CONFIG empty slot mismatch 161 DEV CF MISMATCH INPUT OFFSET CONFIG input offset mismatch 162 DEV CF MISMATCH OUTPUT OFFSET CONFIG output offset mismatch 163 DEV CF MISMATCH DATA TYPE CONFIG
30. apped 1 1 into STEP7 data blocks I O data update with hardware processed in back round thread 2 5 Limitations WinAC Basis V3 x 4 0 4 1 Only master cards are supported yet Only one PCMCIA card at a time supported under Windows NT 4 WinAC RTX all versions Only master cards are supported yet PCMCIA cards are not supported CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 13 48 2 6 Supported CIF Cards and Fieldbus Systems The following table shows the currently supported CIF cards and fieldbus systems CIF60CAN CANopen CIF60CAN CIF80COM CANopen CIF80COM COM E02 DeviceNet CIF Device Driver Table 9 Supported CIF Cards and Fieldbus Systems Part 1 Continued on next page CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 14 48 PB COMBICIF30PB Table 10 Supported CIF Cards and Fieldbus Systems Part 2 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Installation 15 48 3 Installation All Hilscher software components including their documentation are provided on a single product CD Following components are located on this CD SyCon System Configurator CIF WinAC Driver V1 200 for WinAC Basis WinAC RTX 3 x
31. ated 0x8007 E NOT INITILIZED COM system has not been initialized no previous call to SFB65001 CREA COM 0x8008 E HANDLE OUT OF RANGE The supplied handle value does not correspond to a valid COM Table 24 Error Numbers WinAC Basis Error List CIF WinAC DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Driver WinAC Basis and WinAC RTX object Hilscher 2009 Error Numbers 82 WinAC RTX Error List 40 48 WinAC RTX Value Name Description SFB65001 0 NO_ERRORS Success 0x807F ERROR_INTERNAL An internal error occurred 0x8001 E EXCEPTION An exception occurred 0x8002 E NO VALID INPUT Input the ANY pointer is invalid 0x8003 E INPUT RANGE INVALID Input the ANY pointer range is invalid 0x8004 E NO VALID OUTPUT Output the ANY pointer is invalid 0x8005 E OUTPUT RANGE INVALID Output the ANY pointer range is invalid 0x8006 E OUTPUT OVERFLOW More bytes were written into the output buffer by the extension object than were allocated 0x8007 E NOT INITIALIZED ODK system has not been initialized no previous call to SFB65001 CREA COM 0x8008 E HANDLE OUT OF RANGE The supplied handle value does not correspond to a valid extension object 0x8009 E INPUT OVERFLOW More bytes were written into the input buffer by the extension object than were allocated SFB65002 0 NO ERRORS Success 0x807F
32. 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 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Introduction 7 48 1 3 3 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 neglig
33. device initialization in FB2 the global error can hold all error values Later during runtime CIFAC Status Word only signals device specific errors with the value 1 and the error can be found in DB CONFIG DEVICE x DeviceError Possible error values Name Values CIFAC Status Word 0 No error 1 Device specific error Check the DeviceError entry of all devices gt 1 Global error see error table CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Error Numbers 8 Error Numbers 39 48 8 1 WinAC Basis Error List WinAC Basis Value Name Description SFB65001 0 NO ERRORS Success 0x807F ERROR INTERNAL An Internal error occurred 0x8001 E EXCEPTION An exception occurred 0x8102 E CLSID FAILED The call CLSIDFromProgID failed 0x8103 E COINITIALIZE FAILED The call to ColnitializeEx failed WinAC Basis SFB65002 0 NO ERRORS Success 0x807F ERROR INTERNAL An Internal error occurred 0x8001 E EXCEPTION An exception occurred 0x8002 E NO VALID INPUT Input the ANY pointer is invalid 0x8003 E INPUT RANGE INVALID Input the ANY pointer range is invalid 0x8004 E NO VALID OUTPUT Output the ANY pointer is invalid 0x8005 E OUTPUT RANGE INVALID Output the ANY pointer range is invalid 0x8006 E OUTPUT OVERFLOW More bytes are written into the buffer by the COM object than alloc
34. ent 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 1 3 4 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 CIF WinAC Driver WinAC Basi
35. format A description of the message data block is given below NOTE CIF cards are working with Little Endian data representation while STEP7 uses a Big Endian data representation I O data are converted by the WinAC driver to the STEP 7 data representation Message data are not converted because the data content depends on the message command Converting the message data into the correct data representation is part of the user application VRKOP AWL FUP UDT1 RCS MSG CIFACRtx SIMATIC PC Station 1 WinLC RTX UDT1 E loj x Datei Bearbeiten Einf gen Zielsystem Test Ansicht Extras Fenster Hilfe 18 x Da 2 Hlal Bro o t ilo nA kass e Jm Retescibessteg dd jeec m Een eer engen p orre beer aber Ke Fus commana Data ammavt0 275 O4 255 data bytes 25 bytes for compatibility with older definitions oem E Caisse P Dr cken Sie F1 um Hilfe zu erhalten offline labs 5 2 infg Figure 4 STEP7 Structure of a RCS Message CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 23 48 Data description rx Token of the receiver task tx Token of the transmitter task In Length of the user data nr Sequential number of the message a Answer message code f Error code b Command message code e Message extension Data User data For
36. he board Error 11 Board is not ready This is a general error the board has a hardware malfunction Error 12 At least one task is not initialized The board is ready but not all tasks are running No data base is loaded into the device Wrong parameter that causes that a task can t initialize Use ComPro menu Online task version Error 14 No license code found on the communication board Device has no license for the used operating system or customer software No firmware or no data base on the device loaded Error 17 No message could be send during the timeout period given in the DevPutMessage function Using device interrupts Wrong or no interrupt selected Check interrupt on the device and in driver registration They have to be the same Interrupt already used by an other PC component Device internal segment buffer full PutMessage function not possible because all segments on the device are in use This error occurs when only PutMessage is used but not GetMessage HOST flag not set for the device No messages are taken by the device Use DevSetHostState to signal a board an application is available Error 18 No message received during the timeout period given in the DevGetMessage function Using device interrupts CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Error Numbers 46 48
37. he fieldbus settings A fieldbus configuration must be created by SyCon System Configurator After creating a valid configuration SyCon is able to either download the configuration directly to the CIF hardware or export the configuration into a database file DBM This exported file can be later used to run the automatic database checking and download SyCon also provides a wide range of options and fieldbus specific settings But not all of the settings are useful in a PLC environment Because of this the SyCon installation provides some preset values which are important Preset values Addressing mode Auto addressing enabled Startup behaviour Controlled Release of the Communication Handshake of the Process Data Buffered host controlled User program monitoring 1000 milliseconds CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Fieldbus Configuration 26 48 5 1 Fieldbus Startup Behaviour SyCon allows to configure the start up behaviour of a fieldbus system It can be Automatic release of the communication by the device which means the master starts the fieldbus system as soon as the card has finished it s power on sequence The fieldbus becomes active and slaves are able to driver there outputs The option Controlled release of the communication by the application program can be used to prevent an automatic startup of the field bus system
38. iguration DB1001 DB DEVICE INFO Standard data block to a device information DB1002 DB MSG WRITE Data block to write a message to the CIF Device DB1003 DB MSG READ Data block to read a message from the CIF Device Device 1 DB1101 DB IMAP DEV 1 Process data image for INPUT data DB1102 DB QMAP DEV 1 Process data image for OUTPUT data DB1103 DB STATEMAP DEV 1 Device 1 slave state map Device 2 DB1201 DB IMAP DEV 2 Process data image for INPUT data DB1202 DB QMAP DEV 2 Process data image for OUTPUT data DB1203 DB STATEMAP DEV 2 Device 2 slave state map Device 3 DB1301 DB IMAP DEV 3 Process data image for INPUT data DB1302 DB_QMAP_DEV_3 Process data image for OUTPUT data DB1303 DB_STATEMAP_DEV_3 gt Device 3 slave state map Device 4 DB1401 DB IMAP DEV 4 Process data image for INPUT data DB1402 DB QMAP DEV 4 Process data image for OUTPUT data DB1403 DB STATEMAP DEV 4 Device 4 slave state map Table 15 Data Organization CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 35 48 STEP 7 Program 7 3 Function Blocks Overview Function Definition Cmd Description Block FB2 CIFACDriverlnit 1 CIFACDriver initialization and initialization of the specified CIF devices Start communication of the fieldbus system if the device successfully initialized FB3 CIFACReadlnput 3 Read INPUT data from CIF devices
39. ldbus communication DevSetHostState CIF CMD STOP COM 10 Stop fieldbus communication DevSetHostState CIF CMD DEVICE INFO 12 Read global information about a CIF DevGetlnfo Table 13 Driver Functions CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public 30 48 Hilscher 2009 CIF WinAC Driver 6 3 Initialization Process 31 48 The following work will be carried out by the driver during initialization Hardware searching and setup Hardware reset Firmware download Configuration download Serial Device number checking License code checking Fieldbus Communication Done by the CIF Device Driver and its tools for the basis version Automatically by the CIF RTX Driver for the RTX version Each CIF card will be restarted by processing a cold reboot This will be done to get boards working which have been previously stopped by a watchdog hit If the application provides a firmware file directory the driver will check the firmware file version against the version currently running on the CIF card If the they are different the driver carries out an automatic firmware download If the application provides a configuration database file directory and name the driver will check the configuration database against the database currently located on the CIF card If the databases are different the driver carries out an automatic database dow
40. led background thread for each device The standard update rate is 2 milliseconds Default I O Data Update Rate is 2 milliseconds The update rate for each device can be changed via the DeviceError value in the global configuration block DB CONFIG If DeviceError is 0 during the startup of the Step 7 program the default update rate is is used A value unequal to 0 is used as a new update rate given in milliseconds UO Update Rate Settings DeviceError 0 Default update rate 2 ms DeviceError gt 0 New update rate in milliseconds e g DeviceError 10 gt Update Rate 10 ms ATTENTION Depending of the fieldbus system the configuration and the number of connected slave devices this update rate can be too fast In such a case the Read Write function of the CIF WinAC driver returns an error 22 DEVICE IO data exchange failed CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVO3EN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 22 48 4 6 Asynchronous Message Transfer With release of the CIF WinAC driver version V2 004 the Hilscher CIF WinAC driver supports asynchronous fieldbus protocol services like SDOs Writing a asynchronous message to the CIF hardware is done via the data block DB MSG WRITE Incoming messages are stored in the data block DB MSG READ The declaration of both data blocks correspond to the structure of the RCS message
41. lscher 2009 STEP 7 Program 37 48 7 3 6 FB7 CIFACWriteMsg Description Writes a message to the CIF hardware for asynchronous fieldbus protocol services Use the data block DB_MSG_WRITE to store the data Direction Type Parameter Description in BLOCK DB DB CONFIG Global data block in INT DEV Device number 1 4 in BLOCK DB MSG WRITE DB Data block for message writing Pass the data block number of the predefined data block DB MSG WhITE out WORD ERROR Error return Table 22 FB7 CIFACWriteMsg 7 39 7 FB8 CIFACReadMsg Description Reads a message from the CIF hardware for asynchronous fieldbus protocol services Use the data block DB MSG READ to store the data Direction Type Parameter Description in BLOCK DB DB_CONFIG Global data block in INT DEV Device number 1 4 in BLOCK DB MSG READ DB Data block for message reading Pass the data block number of the predefined data block DB MSG READ out WORD ERROR Error return Table 23 FB8 CIFACReadMsg CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Program 38 48 7 4 Error Handling The error handling is done by the global error word CIFAC_Status_Word MW 60 and an error value DeviceError for each devices located in DB_CONFIG All FBs expecting an error word where the global word CIFAC Status Word is used During
42. nload If a device and serial number is provided by application the driver will check these against the information on the CIF card The driver will return error 14 if a CIF card does not have a license code The fieldbus communication will be always stopped before leaving the driver After the initialization procedure the CIF card is ready to start 6 4 NO Data Transfer between CIF Cards and Process Image During the initialization process the driver automatically reads the slave configuration from the master device It uses the slave information to calculate the maximum amount of input and output data which must be transferred between the hardware and the program buffers The amount of data are always calculated starting at input and output offset O CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Program 32 48 7 STEP 7 Program This section describes the STEP 7 program which is part of the WinAC implementation Two versions of the program are existing One for the WinAC Basis and one for WinAC RTX system The only differences between the two programs are SFB65001 and SFB 65002 and their initialization which depends on the target system Program Name WinAC Basis CIFACBasisProg CIFACBas WinAC RTX CIFACRTXProg CIFACRtx WinAC RTX 2005 CIFACRTX2005Prog CIFACRtx WinAC RTX 2008 CIFACRTX2008Prog CIFACRtx WinAC RTX 2009 C
43. or in dual port flags 16 DRV DEV MAILBOX FULL DEVICE Send mailbox is full 17 DRV DEV PUT TIMEOUT DEVICE PutMessage timeout yes 18 DRV DEV GET TIMEOUT DEVICE GetMessage timeout yes 19 DRV DEV GET NO MESSAGE DEVICE No message available 20 DRV DEV RESET TIMEOUT DEVICE RESET command timeout yes 21 DRV DEV NO COM FLAG DEVICE COM flag not set yes 22 DRV DEV EXCHANGE FAILED DEVICE IO data exchange failed 23 DRV DEV EXCHANGE TIMEOUT DEVICE IO data exchange timeout yes 24 DRV DEV COM MODE UNKNOWN DEVICE IO data mode unknown 25 DRV DEV FUNCTION FAILED DEVICE Function call failed 26 DRV DEV DPMSIZE MISMATCH DEVICE DPM size differs from configuration 27 DRV DEV STATE MODE UNKNOWN DEVICE State mode unknown 30 DRV_USR_OPEN_ERROR USER Driver not opened device driver not loaded yes 81 DRV USR INIT DRV ERROR USER Can t connect with device 32 DRV USR NOT INITIALIZED USER Board not initialized DevinitBoard not called 33 DRV_USR_COMM_ERR USER IOCTRL function failed 34 DRV_USR_DEV_NUMBER_INVALID USER Parameter DeviceNumber invalid 35 DRV_USR_INFO_AREA_INVALID USER Parameter InfoArea unknown 36 DRV_USR_NUMBER_INVALID USER Parameter Number invalid 37 DRV USR MODE INVALID USER Parameter Mode invalid 38 DRV_USR_MSG_BUF_NULL_PTR USER NULL pointer assignment 39 DRV_USR_MSG_BUF_TOO_SHORT USER Message buffer too short 40 DRV_USR_SIZE_INVALID USER Parameter Size invalid 42 DRV_USR_SIZE_ZERO USER Parameter Size with zero length
44. ounted independent from 0 to 3 for ISA and PCI cards CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 20 48 DeviceNumber SerialNumber Are used to unambiguous identify a specific CIF card This could be necessary if more than one CIF card of the same fieldbus type is used Both values must be defined The values can be found on the CIF card label ConfigurationFileName If not and empty string it defines the SyCon configuration file DBM file which should be used on the device If configured the CIF WinAC Driver will check the configuration against an existing configuration on the hardware and download it if they are not equal The give name must include the file path file name and file extension e g C TestFiles Test dbm FirmwareDownload If not an empty string it defines the file path where the driver will find the firmware file for the given CIF card The CIF WinAC driver already knows the file name which is suitable for the hardware Only the path to the file must be defined e g C TestFiles Firmware The file path must include the trailing character DB 1 MAP Defines the data block number to store the INPUT process data image of this device The example program defines a size of 3584 byte This can be reduced to the real used size The CIF WinAC driver will checked the defined si
45. rogram Structure ueteri ete ee rr e a OE ERE RM Seen et ed eive a egets 33 7 2 RER le TUE le 34 7 3 Functiom Blocks EE 35 73344 FB2 CIFAGCDriverlnit nete Lee lAl ERTL rectos 35 73 27 EBS CGIFAGReadlnpul 5 ete LSU IU ee tute ese ei eke rene Age 35 73 9 FBA CIFAGWELiteOUtDUL EE 36 7 3 4 FB5 CIFACReadSlaveConfig AAA 36 7 3 5 FB6 CIFACReadbDevicelnfo cedere epe eoe le tradere aeree reae gegen e venden 36 1 3 6 FBZzGIEAGWhEteMSg uiis canem icai yi 37 7 37 FB8 CIFAGReadMSg aceite crc e cie e cn eee rcr Ie dela erre eee ree TRE SR 37 7 4 vErrorFHandlirig zi ees eden EPA 38 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 8 Error Numbers nuni re Dee geed 39 831 WinAC Basis Error set 39 8 2 WinAC RTX EmorUset tetun an nannt Ernan enun EEEE an AAEE Ennan an nanne nenna ne ne 40 8 3 CIF WinAC Driver Error Ust 41 8 4 CIF Device Driver Error Ust ritinn tn untu tn nannan nannan annn nE nanan na nnna nnnn nnne 42 8 4 1 Additional Error Information 45 9 Appendiks eaan MI uu eMe icem 47 9 1 Eistot table SA en ee a Ber 47 CR ET Wo IT 47 90 3 3GOhlacl8s cines ieiuno Ere E Kio E ack EE 48 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 Introduction 4 48 Important Notes Autorization The
46. rogram Structure i 23 esci decret eedem etre aces edo eere E ee Deere tene Efe ce 33 Table 15 Data Organization i ee e e DRE ER GP AG IUUD Ris 34 Table 16 Function Blocks uitae ee dee nere Reti ae erbe enter doe Edere eee e de et de 35 Table 17 FB2 GIEAGDriverlriit 2 ttn eue E Eeer Mee ee EE 35 Table 18 FB3 GIFAGReadlnput m coded hehe ee Po Deae EE 35 RL WE Mel Se nk IEN 36 Table 20 EB5 CIFAGReadSlaveGohfig cii ete oe b e REG Er ORE EO Ee oie it 36 Table 21 FB6 CIFACheadievicelto e nnn eE s nnne en nenr iren nnn n nnne 36 Table 22 ER GIEAGWhHfIte MSO crc HERR er o Erie Pe td Le Dec RU RO PRAEC e SIL TR ee Dex DOCERE regen 37 Table 23 E el e m 37 Table 24 Error Numbers WinAC Basis Error List cccccsccccesseeeeeeenceeeeenaeeecenneeeseaeeesseaaeeesecneeseseaeessenaeeessneeeeseieeeeess 39 Table 25 Error Numbers WinAC RTX Error List esses eene enne nennen nennen ennt rennen nennen nnn 40 Table 26 Error Numbers WinAC Driver Error Ust nme nennen nnne nennen nnn 41 Table 27 Error Numbers CIF Device Driver Error Ust enne nnne nnne nennen nn 44 9 2 Figure 1 Figure 2 Figure 3 Figure 4 List of Figures STEP7 Hardware Confgouraton enne enne enne nnne nnne nnne nnne nnns entere resin nennen nennen 17 STEP Project EE 18 STEP7 Declaration View of DB CONFIG ssssssssssssssseeseeeeene enne enne nnne nnn ennt enn nere nennen nnn rennes 19 STEP7 Structure of a RCS
47. s and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 2 About the Driver 2 1 CD Contents 8 48 Folder Content Manuals CIF WinAC Driver Documentation Sycon Sycon Protocol Manuals WinAC Driver CIF WinAC Driver Manual Driver CIF Driver Setup for Windows 9x 2000 XP EDS Electronic Datasheets for Hilscher Devices FAQ Frequently Asked Questions Firmware Firmware Files SyCon SyCon System Configurator UTIL CIF Device Utilities COMPRO ComPro configuration and diagnostic program DEVVIEW Device Viewer to indicate information about DPM PCI PLX Monitor to configure the PCI card TCPIPSrv TCP IP Server WinAC CIF WinAC Driver and Step 7 Example Projects CIFAC Driver CIF WinAC Driver Setup STEP7 Step 7 Example Projects WinAC 3x 41 Step 7 Example Project for WinAC Base RTX 3 x 4 1 WinAC RTX 2005 Step 7 Example Project for WinAC RTX 2005 WinAC RTX 2008 Step 7 Example Project for WinAC RTX 2008 WinAC RTX 2009 Step 7 Example Project for WinAC RTX 2009 ACROREAD Windows Adobe Acrobat Reader Setup German English French Table 3 CD Contents CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 9 48 2 2 Implementation 2 2 1 WinAC Basis The implementation is based on the Siemens WinAC ODK by creating a COM objec
48. ssary device drivers Step2 Create a fieldbus configuration with SyCon Step3 Create a new STEP7 project and use the FBs and DBs from the example program Or change the existing example program CIFACBasisProg CIFACRtxProg CIFACRtx2005Prog CIFACRtx2008Prog CIFACRtx2009Prog depending to the runtime environment Step4 Configure the CIF devices used by the STEP7 project 4 1 Install the CIF Hardware and its Device Drivers Please consult the Hilscher product CD inlet and the device driver manual DRVDEV PDF how to correctly install and configure the CIF hardware and its device drivers WinAC Basis Install the CIF hardware into the PC and the Windows NT Windows 2000 or Windows XP device driver which are necessary for the WinAC Basis system Both SyCon and the CIF WinAC Driver requires the hardware drivers to access the CIF hardware WinAC RTX In a WinAC RTX system the Windows device drivers are only used by SyCon to directly download a configuration to the CIF hardware and to run SyCon debug functionality s The CIF WinAC Driver uses only the CIFRTXDriver to access the hardware ATTENTION The Windows NT Windows 2000 Windows XP device driver must be deactivated as soon as the WinAC runtime system is activated Otherwise it is possible that Win32 programs are also able to access the CIF hardware which results in unexpected system and fieldbus behaviour On Windows NT based systems check the Windows NT Control Panel Devices entr
49. t which is called from the WinLC scan cycle The COM object is located in the file CIFACDriver DLL Hardware access to the Hilscher CIF cards based on the CIF Device Driver for Windows NT 4 Windows 2000 and Windows XP The CIF WinAC driver offers transparent access to the different devices Therefore it hides the functionality s for ISA PCMCIA and PCI cards The cards can be selected by the original Device Type string and a board number between 0 to 3 The board numbers can be obtained from the device driver setup program Overview WinLC CIFWinACDriver CIFACDriver DLL CIF Device Driver 2 2 2 WinAC RTX The implementation is based on the Siemens WinAC RTX ODK The driver is located in the CIFACDriver RTDLL which is called from the WinLC scan cycle via a calling interface Hardware access to the Hilscher CIF cards is based on the CIF RTX Driver CIFRTXDriver rtdll The CIF WinAC driver offers transparent access to the different devices Therefore it hides the functionality s for ISA and PCI cards The cards can be selected by the original Device Type string and a board number between 0 to 3 Overview WinLC CIFWinACDriver CIFACDriver RTDLL CIF RTX Driver CIFRTXDriver RTDLL CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 About the Driver 10 48 2 3 Requirements The CIF WinAC driver is available for a
50. the device Direction Type Parameter Description in BLOCK DB DB CONFIG Global configuration data block in INT DEV Device number 0 process all devices 1 4 process specific device out WORD ERROR Error return Table 19 FB4 ClFACWriteOutput 7 3 4 FB5 CIFACReadSlaveConfig Description Read the configuration data of a specific slave device Use the data block DB SLAVE CFG to store the data Direction Type Parameter Description in BLOCK DB DB_CONFIG Global data block in INT DEV Device number 1 4 in INT SLAVE ADDRESS Slave address to read the configuration 0 127 in BLOCK DB SLAVE CONFIG DB Data block for slave data Pass the data block number of the predefined data block DB SLAVE CFG out WORD ERROR Error return Table 20 FB5 CIFACReadSlaveConfig 7 3 5 FB6 CIFACReadDevicelnfo Description Read various information from a specific CIF device Use the data block DB DEVICE INFO to store the data Direction Type Parameter Description in BLOCK DB DB_CONFIG Global data block in INT DEV Device number 1 4 in BLOCK DB DEVICE INFO DB Data block for device information Pass the data block number of the predefined data block DB DEVICE INFO out WORD ERROR Error return Table 21 FB6 CIFACReadDevicelnfo CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Hi
51. tivate DevOpenDriver of the loaded hardware drivers will be called Deactivate DevCloseDriver of the loaded hardware drivers will be called Execute Calls the driver functions described in the section Driver Functions Table 12 Driver Loading Initialization and Removing WinAC RTX CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 CIF WinAC Driver 6 2 Driver Functions Currently implemented driver functions device Command Code Description Underlying Device Driver Functions CIF CMD INIT 1 Initialization of the specified CIF DevinitBoard devices DevGetBoardlnfoEx Creation of the I O data exchange DevExtendedData background process DevDownload DevReset DevSetHostState CIF CMD CONFIG 2 Read the configuration of one slave Reads the station description device of a specific slave device CIF CMD WRITE IO 3 Write OUTPUT data to a CIF device DevTriggerWatchDog DevExchangelOErr CIF CMD READ IO 4 Read INPUT data from a CIF device DevTriggerWatchDog DevExchangelOErr CIF CMD READ STATE 6 Read task state information Returns the information from COMSTATE structure read by DevExchangelOErr CIF CMD WRITE MSG 7 Write a message to a CIF device DevPutMessage CIF CMD READ MSG 8 Read a message from a CIF device DevGetMessage CIF CMD START COM 9 Start fie
52. ver Error List The column Hint shows if there is additional error information available If Yes then see section Aaditional Error Information which is the next section 42 48 CIF WinAC Driver WinAC Basis and WinAC RTX DOCO020701DRVOSEN Revision 3 English 2009 09 Released Public Value Name Description Hint 0 DRV NO ERROR no error 1 DRV BOARD NOT INITIALIZED DRIVER Board not initialized yes 2 DRV INIT STATE ERROR DRIVER Error in internal init state 3 DRV_READ_STATE_ERROR DRIVER Error in internal read state 4 DRV_CMD_ACTIVE DRIVER Command on this channel is active 5 DRV_PARAMETER_UNKNOWN DRIVER Unknown parameter in function occurred 6 DRV_WRONG_DRIVER_VERSION DRIVER Version is incompatible with DLL 7 DRV_PCI_SET_CONFIG_MODE DRIVER Error during PCI set run mode 8 DRV_PCI_READ_DPM_LENGTH DRIVER Could not read PCI dual port memory length 9 DRV PCI SET RUN MODE DRIVER Error during PCI set run mode 10 DRV DEV DPM ACCESS ERROR DEVICE Dual port ram not accessible yes board not found 11 DRV DEV NOT READY DEVICE Not ready ready flag failed yes 12 DRV DEV NOT RUNNING DEVICE Not running running flag failed yes 13 DRV DEV WATCHDOG FAILED DEVICE Watchdog test failed yes 14 DRV DEV OS VERSION ERROR DEVICE Signals wrong OS version yes 15 DRV DEV SYSERR DEVICE Err
53. y CIFDEV and deactivate the driver On Windows 2000 Windows XP based systems you have to use a RTX Tool to assign the hardware to RTX Please consult the WinAC RTX documentation how this is done 5 CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 17 48 4 2 Create a Fieldbus Configuration with SyCon Contact the SyCon manual how to create a valid fieldbus configuration NOTE SyCon allows to export the configuration into a DBM file which can be later used in a STEP7 program to be checked against an already on the hardware existing configuration and to download it if they are not equal 4 3 Create a new STEP7 Project Please consult the STEP7 documentation how to use STEP7 Step1 Create a new STEP7 project Step 2 Include a SIMATIC PC Station Step 3 Change to the hardware configuration open the hardware catalog select SIMATIC PC Station and insert from the entry Controller the WinLC or WinLC RTX entry into the configuration The driver does not need any information from the STEP7 hardware configuration therefore answer all following questions with NO DG Hw Konfig SIMATIC PC Station 1 Station Bearbeiten Einf gen Zielsystem Ansicht Extras Fenster Hilfe Dee ai Sl En ie RI SIMATIC PC Station 1 Konfiguration Example Iof x Profit Standard PROFIB
54. ze an returns with an error if it is not sufficient DB Q MAP Defines the data block number which holds OUTPUT process data image of this device The example program defines a size of 3584 byte This can be reduced to the real used size The CIF WinAC driver will checked the defined size an returns with an error if it is not sufficient DB SLAVE STATE MAP Defines the data block number to store the slave state information of this device DeviceHandle Generated by the CIF WinAC Driver during device initialization Do not change this value DeviceError Used to store device errors and to setup It is also used during startup to change the cycle time of the backround UO data thread If this value is not 0 during startup the Value is used as the I O data update rate in milliseconds PROGID INSTANCEID This parameter is necessary for WinAC and tells the system which driver to start for SFB65001 SFB CREA COM The value is different for WinAC Basis CIFACDriver CIFACDriver and WinAC RTX RTSS CIFRTXDriver rtdll CIF WinAC Driver WinAC Basis and WinAC RTX DOC020701DRVOSEN Revision 3 English 2009 09 Released Public Hilscher 2009 STEP 7 Project Creation and Configuration 21 48 4 5 Setup I O Data Update Rate The CIF WinAC driver does not directly access the I O image from the hardware The I O data are buffered in an internal UO buffer area For the UO data update with the hardware the driver generates a so cal

CIF WinAC Driver

Contents

Download Pdf Manuals

Related Search

Related Contents