labview code for MKS 146 device-missing files

[blue_sky]

Hi,

I copied a labview program for controlling a MKS 146.  The original device was another model from MKS.  However,  when I  tried to open it, it asked me to find the following files during the loading process which I couldn't find in my computer or NI and MKS web. Is there anyone what is wrong with the program or where I can get these files from?

Thanks,
Emily 


The files missing:
<userlib>:\mks\146.llb\146init.vi
<userlib>:\mks\146.llb\146close.vi
<userlib>:\mks\146.llb\146rdcfg.vi
<userlib>:\mks\146.llb\146trans.vi
<userlib>:\mks\146xtra.llb\146s2prm.vi

<userlib>:\mks\mks.llb\comref.vi
<userlib>:\mks\mks.llb\mks error handler.vi
<userlib>:\mks\mks.llb\taskopen.vi
<userlib>:\mks\mks.llb\taskclos.vi
<userlib>:\mks\mks.llb\taskref.vi
<userlib>:\mks\mks.llb\mkstrans.vi


After ignoring all the above messages, the file was opened with a waring:

FC_016_v2.0.vi
    - The VI expected to be at "C:\Documents and Settings\lsong8.ASUAD\Desktop\subvi\open_file.vi" was loaded from "C:\Documents and Settings\lsong8.ASUAD\Desktop\open_file.vi".
    - The VI expected to be at "C:\Documents and Settings\lsong8.ASUAD\Desktop\subvi\save.vi" was loaded from "C:\Documents and Settings\lsong8.ASUAD\Desktop\save.vi".
    - The File Dialog function no longer supports the datalog type input.
    - The File Dialog function now outputs an er

[gwd]

The missing vis seem to be MKS vis. They were probably in a library file. If you have access to another computer running this vi you should be able to find them.

In addition you seem to have a Labview version mismatch. This may or may not  matter but you won't be able to tell unless you can get the sub-vis.

[blue_sky]

Hi,

Thank you for your reply. However, the original computer is not accessible right now due to some reasons. Is there anywhere else I can get to the MKS files? And the files related to the MKS 146 device?

The questions are probabaly dumb, but I am new to this area, please bear with me. Thank you,

[gwd]

You can 1) do a search on the NI instrument driver network 2) try keywords in google 3) look on the MKS website or 4) call MKS and beg.

Also the manual has enough info for a determined person to write a custom driver.

[amazed]

I work at MKS. Did a search for the missing vi's you mentioned but did find them.   Anything from here would simply be a front panel vi to the 146 .

Are you looking to integrate it into something larger?   

Here's something in 7.0 I send just to get people started. Someone who was really proficient

at Labview could do a much better job at this.  In the diagram, you can change the com port and settings on the left.

The 232 cable is 2-2 3-3 5-5 female 9 pin d's both ends.  Response time from command out to recieved approx 40ms at 9600

Best Regaqrds

j 

[blue_sky]

Thank you very much for the sample. Actually, we are working on something bigger than that, changing flow rate at different time. We got some of the missing files. However, there is  still one file missing "DNLAB32.dll".  Do you have  it  by any chance? 

[amazed]

Sorry.  I meant to say I did not find the file in the previous message.  The only vi's from here would be simple front panels though from what you sent, it looks like a simple task to read a time and then send out the setpoints to the mfc's.   I assume you are simply pressing a start button and the program time sequences thru a list of 3 variables and ends on the last set of data?

Best Regards

john

[mikeporter]

Do you have access to the source code? It looks like you might have to rebuild the missing VIs yourself, but given the instrument manual, an example from the vendor and the context that the VI's are in it shouldn't be too hard to piece things together. Other good hints are the names of the missing VIs. Hopefully whoever wrote them originally had them do just what their names say - and nothing more...

Mike...

[blue_sky]

Thanks a lot. You guys are very helpful.  🙂