LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how to rewrite the dll file

EpromW(TCHART Efile[],HWND,hWnd)
Efile is the file name to test, hWnd is used to graphic the progress Bar,
For the first TCHART Efile[],I want to open a file that I want to write it into my instrument, hWnd is a progress Bar that can indicate my process,but when I use the Call dll function node, it can't write it correctly.please give me the best resolution.
maincool
0 Kudos
Message 1 of 16
(3,791 Views)
maybe you need the terminator "\n" at the end of the test file string. Just a thought.
0 Kudos
Message 2 of 16
(3,778 Views)


Joe Guo 写:
maybe you need the terminator "\n" at the end of the test file string. Just a thought.



It can't write it correctly,please give me other advice!thanks a lot!
maincool
0 Kudos
Message 3 of 16
(3,764 Views)
Please provide us with the prototype of a call to the DLL in a text based language, including type descriptors. That would make it easier to determine how to call it from LabVIEW.
- Philip Courtois, Thinkbot Solutions

Thinkbot Solutions
0 Kudos
Message 4 of 16
(3,751 Views)
Also, take a look at the excellent shipping example called "Call DLL.vi". It shows the ways to call almost any data type.
- Philip Courtois, Thinkbot Solutions

Thinkbot Solutions
0 Kudos
Message 5 of 16
(3,746 Views)
Hi Philip:
Philip C. write "Also, take a look at the excellent shipping example called "Call DLL.vi". It shows the ways to call almost any data type.



Please provide us with the prototype of a call to the DLL in a text based language, including type descriptors. That would make it easier to determine how to call it from LabVIEW. "

The based language is the VC++6.0,the description as below:
EepromW(TCHAR Efile[], HWND hWnd)
Select EepromW to programme at the start/end of the test (after I2cCommOpen)
Efile[] is the name of the file ,
the hWnd is the process bar ,
Also there is another to check it status

The method SInfo to check the status of write Eeprom:
struct SInfo {

BYTE status; status of the process (Eeprom Dawnload Status)
BYTE perc; percentage of the process (0 - 100)
BYTE err; error code (see ERR_CODE in Sbit100.h.)
BYTE nRetry; n. attempt (1 - 3)
}
how to call them?

Thanks a lot
maincool
maincool
0 Kudos
Message 6 of 16
(3,742 Views)
Use the following types when specifying the parameters of the DLL in the Call By Reference Node:

Efile: String >> C String Pointer
hWnd: Numeric >> Unsigned 32-bit Integer

See the attached DefineDLL.JPG.
- Philip Courtois, Thinkbot Solutions

Thinkbot Solutions
0 Kudos
Message 7 of 16
(3,719 Views)


Philip C. 写:
Use the following types when specifying the parameters of the DLL in the Call By Reference Node:

Efile: String >> C String Pointer
hWnd: Numeric >> Unsigned 32-bit Integer

See the attached DefineDLL.JPG.



Thanks a lot!
Yes,first I invoke this dll, I use the specifying the paraemters like you said, but I want to see the progress bar during my program running,how to do it?
Best regards,
maincool
0 Kudos
Message 8 of 16
(3,716 Views)


maincool 写:


Philip C. 写:
Use the following types when specifying the parameters of the DLL in the Call By Reference Node:

Efile: String >> C String Pointer
hWnd: Numeric >> Unsigned 32-bit Integer

See the attached DefineDLL.JPG.



Thanks a lot!
Yes,first I invoke this dll, I use the specifying the paraemters like you said, but I want to see the progress bar during my program running,how to do it?
Best regards,




need I use CIN tool to configure the DLL configration?thanks a lot!
maincool
0 Kudos
Message 9 of 16
(3,688 Views)
Hi Maincool!

It sounds to me like you're not necessarily having any troubles calling the function (in the DLL) from LabVIEW. It sounds like you are having troubles getting the functions in the DLL to do what you want them to do. It is hard for us to tell you how to get it to work because none of us know what functions reside in your DLL and how they all work together. However, I'll take a stab at it.

It sounds like you may be loading the progress bar into memory and configuring it just fine. It also sounds like there should be a function to *display* the progress bar. Could this be the case?

Hope this helps!

Travis H.
National Instruments
Travis H.
LabVIEW R&D
National Instruments
Message 10 of 16
(3,669 Views)