09-10-2011 09:49 AM - edited 09-10-2011 09:56 AM
Hello, dear lv'ers:
Recently i am evolved in a project where i want to reuse my developed ac measurement modules (certainly in .vi format) in target computers. The related information has been collected below:
0) Develope machine: win7, lv2010 sp1 development suite bought last year, third-part usb devices (Rigol DG1022 for instance, recognized in MAX as USB0::0x0957::0x0407::MY44012174::INSTR), ac measurement vi's with VISA function calling.
1) Target computer A: MultiVu for squid vsm from QD(quantum design) bought in 2009, allowing third-part extension script written in visual basic .bas format. MAX was installed by QD, but our third-part usb devices could unfortunately not be recognized and assigned a visa resource name.
2) Target computer B: MultiVu for squid-xl from QD bought 2007, allowing third-part extension script writen in Delphi .dpr format. Its MAX has the same problem.
i have got familiar with extending such two MultiVu's for dc measurement based on Keithley 2400 & 2182, successfully using VB and Delphi, respectively. Such dc module has nothing to do with labview and has already installed with GPIB interface in MAX.
i have already overviewed some related posts here for dll building for VB and Delphi, and i could build my hellow-world dll for vb(simply following reversstring one in ni knowledgebase). However, at the moment, my main concerning is how to build dll's installation package for our two target computers, so that they can use the third-part usb devices as in my development machine?
Your answers, direct or indirectly, would be quite appreciated.
Faithfully
Jun Lu
----------
Member of Technical Staff in State Key Laboratory of Magnetism
Beijing National Laboratory for Condensed Matter Physics
Institute of Physics, Chinese Academy of Sciences
100190 Beijing, P.R. China
http://www.instrument.com.cn/ilog/handsomeland/
09-11-2011 03:34 AM - edited 09-11-2011 03:35 AM
Probably, i have just got a solution for this problem.
The way seems quite simple: what i need to do, before importing dll or exe files, is installing a VISA 4.0 (http://download.ni.com/support/softlib/visa/NI-VISA/4.0/win32/visa400full.exe) in target computers, which can communicate fine with our devices.
Afterwards, you know, everthing goes ok as does in the development computer.
When i got further problems, i shall return here. :-).
01-31-2012 11:27 AM
Did you find any solution to this problem. Please let me know. I am in similar situation.
01-31-2012 06:03 PM
please refer the #1 reply by myself.
01-31-2012 06:27 PM
So basically you are creating .dll of whatever you want by using visa? Is that the solution?
We have a MPMS system and the crotrollers 1802 does not reespond to *IDN? query. Is it similar with you?
01-31-2012 07:35 PM
From my knowledge, MPMS system has no driver for visa calling, which is quite not the same case as PPMS.
The only way i know, to operate mpms, is using Delphi to get MpmsExports, MpmsOleDll, MpmsDefinitions etc. resources.
Probably bad news to you: QD engineers told me that they have no interest to develop labview oriented interface for MPMS series.
01-31-2012 08:26 PM
Thanks
I know the delphi story. I was wondering did you try call libtary node function from labview with this .dll library?
The problem is I have labview code for other meter and I was wondering that if I convert the VI to .dll and that will work or not.
Did you use Delphi to solve this?
Let me know.
02-01-2012 06:01 PM
not yet. Nevertheless, it would be a piece of cake for Delphi to call dll created by lv.
02-16-2012 03:22 AM
Probably I have a solution! are you still interested?
Please write me to richya7@yahoo.com
02-16-2012 04:17 AM
Interesting...
ok, already sent, pls chk your mailbox...