header for fortran dll to be called from matlab
in [Matlab]
|
From: Hu on 17 Jun 2010 19:17 Dear all, I am trying to call a DLL file from Matlab. I guess the DLL was created by FORTRAN and I don't have header file for this DLL file. Does anybody know how to write a header file for it? In the help document of the program, there are ways calling it from VB6 and Fortan90. The information is followed: VB Declaration Statement: Private Declare Sub ProcessWeather Lib "EPlusWth" (ByVal strInType As String, ByVal InTypeLen As Long, ByVal strOutType As String, ByVal OutTypeLen As Long, ByVal strInFileName As String, ByVal InFileNameLen As Long, ByVal strOutFileName As String, ByVal OutFileNameLen As Long, ErrorFlag As Boolean) Calling it from VB: Call ProcessWeather(InputFileDataType, Len(InputFileDataType), OutputFileDataType, Len(OutputFileDataType), InputFileName, Len(InputFileName), OutputFileName, Len(OutputFileName), ErrorFlag) ************************************************************** Fortran 90/95 Declaration: INTERFACE SUBROUTINE ProcessWeather(InType,OutType,InFileName,OutFileName,ErrFlag) CHARACTER(len=*), INTENT(IN) :: InType ! InputFile Type CHARACTER(len=*), INTENT(IN) :: OutType ! OutputFile Type CHARACTER(len=*), INTENT(IN) :: InFileName ! InputFile Name (Full path) CHARACTER(len=*), INTENT(IN) :: OutFileName ! OutputFileName (Full path) LOGICAL(Byte2), INTENT(OUT) :: ErrFlag ! If errors are found, ! set to true and put ! description put in file. END SUBROUTINE END INTERFACE And calling it from Fortran: call processweather(trim(intype),trim(outtype), & trim(infilename),trim(outfilename),errflag) ************************************************************* Hope anybody could help me write a header according to the declaration in VB and fortran. Thank you very much! Hu Du
From: James Tursa on 17 Jun 2010 20:47 "Hu " <amber.du(a)gmail.com> wrote in message <hveadg$31c$1(a)fred.mathworks.com>... > Dear all, > > I am trying to call a DLL file from Matlab. I guess the DLL was created by FORTRAN and I don't have header file for this DLL file. Does anybody know how to write a header file for it? In the help document of the program, there are ways calling it from VB6 and Fortan90. The information is followed: > > VB Declaration Statement: > Private Declare Sub ProcessWeather Lib "EPlusWth" (ByVal strInType As String, > ByVal InTypeLen As Long, ByVal strOutType As String, ByVal OutTypeLen As > Long, ByVal strInFileName As String, ByVal InFileNameLen As Long, ByVal > strOutFileName As String, ByVal OutFileNameLen As Long, ErrorFlag As Boolean) > > Calling it from VB: > Call ProcessWeather(InputFileDataType, Len(InputFileDataType), > OutputFileDataType, Len(OutputFileDataType), > InputFileName, Len(InputFileName), > OutputFileName, Len(OutputFileName), > ErrorFlag) > ************************************************************** > Fortran 90/95 Declaration: > INTERFACE > SUBROUTINE ProcessWeather(InType,OutType,InFileName,OutFileName,ErrFlag) > CHARACTER(len=*), INTENT(IN) :: InType ! InputFile Type > CHARACTER(len=*), INTENT(IN) :: OutType ! OutputFile Type > CHARACTER(len=*), INTENT(IN) :: InFileName ! InputFile Name (Full path) > CHARACTER(len=*), INTENT(IN) :: OutFileName ! OutputFileName (Full path) > LOGICAL(Byte2), INTENT(OUT) :: ErrFlag ! If errors are found, > ! set to true and put > ! description put in file. > END SUBROUTINE > END INTERFACE > > And calling it from Fortran: > call processweather(trim(intype),trim(outtype), & > trim(infilename),trim(outfilename),errflag) > ************************************************************* > > Hope anybody could help me write a header according to the declaration in VB and fortran. Thank you very much! > > Hu Du Character strings are notorious for causing headaches with the string lengths being passed. Maybe they are next to each string pointer, or maybe they are all bunched up at the end. But based on the VB description it looks like they are next to the pointers and not bunched at the end. You might try this: void PROCESSWEATHER(char *, int, char *, int, char *, int, char *, int, short *) James Tursa
From: Hu on 18 Jun 2010 06:18 Thank you very much! James, Your header file is great! I can load the dll into Matlab now, and I also can use the ProcessWeather function. The problem is that when Matlab finish executing the function, it will be shut down incorrectly. However the output results are correct. Is it the problem of DLL or header file? May I ask what does * mean in header file? Best regards, Hu "James Tursa" <aclassyguy_with_a_k_not_a_c(a)hotmail.com> wrote in message <hvefm7$ogi$1(a)fred.mathworks.com>... > "Hu " <amber.du(a)gmail.com> wrote in message <hveadg$31c$1(a)fred.mathworks.com>... > > > > Hu Du > > Character strings are notorious for causing headaches with the string lengths being passed. Maybe they are next to each string pointer, or maybe they are all bunched up at the end. But based on the VB description it looks like they are next to the pointers and not bunched at the end. You might try this: > > void PROCESSWEATHER(char *, int, char *, int, char *, int, char *, int, short *) > > James Tursa
From: James Tursa on 18 Jun 2010 10:21 "Hu " <amber.du(a)gmail.com> wrote in message <hvfh4t$87k$1(a)fred.mathworks.com>... > Thank you very much! James, > > Your header file is great! I can load the dll into Matlab now, and I also can use the ProcessWeather function. The problem is that when Matlab finish executing the function, it will be shut down incorrectly. However the output results are correct. > > Is it the problem of DLL or header file? I am not sure what the BYTE2 is in the last argument. I had assumed that it was a 2-byte integer, but now I think maybe it is just a 1-byte unsigned integer. So try this instead: void PROCESSWEATHER(char *, int, char *, int, char *, int, char *, int, unsigned char *) > May I ask what does * mean in header file? * means pointer. So char * is a pointer to char. Basically it means the argument is passed by reference (address to the variable itself is put on the calling stack) rather than by value (the value itself is put on the calling stack). James Tursa
From: Hu on 21 Jun 2010 09:36 Thank you again James, I tried the new header file, it still have the same problem. Is it because the function need return a value for ErrorFlag and I didn't define the variable in Matlab before I call the function? Actually, there are three other functions in the DLL file. SetupPWInternalDataPath SetFixOutOfRangeData SetDefaultChgLimit The declaration of them are followed: VB declaration statement: Private Declare Sub SetupPWInternalDataPath Lib "EPlusWth" (ByVal strPath As String, ByVal InPathLen As Long) And a call from a VB program: Call SetupPWInternalDataPath(AppPath, Len(AppPath)) -------------------------------------------------------------------------- Likewise for Fortran 90/95: INTERFACE SUBROUTINE SetupPWInternalDataPath (Path) CHARACTER(len=*), INTENT(IN) :: Path ! Path where data files reside END SUBROUTINE END INTERFACE And then calling it from Fortran: Character(len=255) DataPath CALL SetupPWInternalDataPath(trim(DataPath)) ************************************************* VB Declaration statement: Private Declare Sub SetFixOutOfRangeData Lib "EPlusWth" (ByVal strValue As String, ByVal strValueLen As Long) And calling it from VB: Global FixOutOfRangeData As String FixOutOfRangeData = “Yes” Call SetFixOutOfRangeData(FixOutOfRangeData, Len(FixOutOfRangeData)) ------------------------------------------------------------------------------------ For Fortran 90/95: INTERFACE SUBROUTINE SetFixOutOfRangeData (YesNo) CHARACTER(len=*),INTENT(IN) :: YesNo ! ‘yes’ to set fixing option; ! ‘no’ to not END SUBROUTINE END INTERFACE And then calling it: CALL SetFixOutOfRangeData(‘no’) ********************************************************* VB Declaration Statement: Private Declare Sub SetDefaultChgLimit Lib "EPlusWth" (ByVal strValue As String, ByVal strValueLen As Long, ByVal strValue As String, ByVal strValueLen As Long) And a call from VB: Call SetDefaultChgLimit(TriggerLimit, Len(TriggerLimit), IgnoreCalcTrigger, Len(IgnoreCalcTrigger)) ***************************************************** The information in header file I used are: void SetupPWInternalDataPath (char *,int); void SetFixOutOfRangeData(char *,int); void SetDefaultChgLimit(char *,int,char *,int); Are they right? Do I need call these functions firstly then call ProcessWeather? Regards, Hu "James Tursa" <aclassyguy_with_a_k_not_a_c(a)hotmail.com> wrote in message > I am not sure what the BYTE2 is in the last argument. I had assumed that it was a 2-byte integer, but now I think maybe it is just a 1-byte unsigned integer. So try this instead: > > void PROCESSWEATHER(char *, int, char *, int, char *, int, char *, int, unsigned char *) > > > May I ask what does * mean in header file? > > * means pointer. So char * is a pointer to char. Basically it means the argument is passed by reference (address to the variable itself is put on the calling stack) rather than by value (the value itself is put on the calling stack). > > James Tursa
|
Next
|
Last
Pages: 1 2 Prev: discrete trasnfer function calculations discrepance Next: Issue with Accessor methods |
