[精品]Functionalspecificationexternaldriverinterface.doc

Functional Specification Interface for direct calls to external drivers from RealtimePLC-Runtime for Windows NT Which modules are linked ? IO-Drivers are linked by entries in the registry-key \\HKEY_LOCAL_MACHINE\Software\3S Smart Software Solutions\Codesys SP\RTPLC\IO Drivers. Here a value ?DriverXX“ must exist for each driver that should be linked. XX is a continuously incremented number, starting with 0. All function, that may work on hardware, are redirected to the drivers that are linked, from now on. This document describes the interface necessary to manage the linking of external IO-Drivers (by filling some function-pointer-tables) to the realtime extension of WindowsNT, created by Smart Software Solutions GmbH. The basic procedure to retrieve the functionpointers. Each driver running under WindowsNT must fill some entries in the list of his dispatch-functions, for example: pDriverObject-MajorFunction[IRP_MJ_DEVICE_CONTROL]= ntDeviceControl; pDriverObject-MajorFunction[IRP_MJ_CREATE ]= ntCreateFile; Now we add one entry, which tells the operating system the address of a function, dedicated for driver-driver-comunication. pDriverObject-MajorFunction[IRP_MJ_INTERNAL_DEVICE_CONTROL]= yyyyyy; where yyyyyy is the address of a function, defined as follows: typedef struct _tagCallbackInfo { //the security-members are made to check, whether the caller is a legal caller to the driver. unsigned long ulSecurityId1; // this member must be set to 0x436F4465 means CoDe unsigned long ulSecurityId2; // this member must be set to 0means Sysspace unsigned long ulCommand; unsigned long ulSubCommand; unsigned long ulCmdParam; void* pAdditionalCmdData; //may point to a caller-supplied, command-specific structure. }CallbackInfo; unsigned long yyyyyy(CallbackInfo* pcbi, void* pPar); This function is called by the realtimePLC, with the security Ids as parameters, see above. The driver now can determine, whether the call really comes from real