<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: refprop in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/480849#M231069</link>
    <description>&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;LabVIEW missed a couple of wires in the file read code when I backward compiled it from 8.2 to 8.0 to 7.1&lt;BR /&gt;
&lt;BR /&gt;
Try this recompiled version. I verified it works with pure fluids and mixtures.&lt;BR /&gt;
&lt;BR /&gt;
Look in the VI tree at the example (Refprop Example.vi).&lt;BR /&gt;
Using this code, both pure fluids and mixtures are handled the exactly the same way.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;/DIV&gt;&lt;P&gt;Message Edited by gsussman on &lt;SPAN class="date_text"&gt;02-20-2007&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;12:19 PM&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2007 18:19:19 GMT</pubDate>
    <dc:creator>gsussman</dc:creator>
    <dc:date>2007-02-20T18:19:19Z</dc:date>
    <item>
      <title>refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/272079#M144710</link>
      <description>&lt;DIV&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;Hello,&lt;NAMESPACE prefix="o" ns="urn:schemas-microsoft-com:office:office"&gt;&lt;P&gt;&lt;/P&gt;&lt;/NAMESPACE&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;I was wondering if anyone has ever completed an application accessing REFPROP from NIST. &lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;I have used other DLL’s with the CIN tool but can not seem to make this REFPROP DLL work.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;If anyone has a code snippet showing the settings of the CIN tool that is using REFPROP, it would be greatly appreciated.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 28 Sep 2005 17:23:04 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/272079#M144710</guid>
      <dc:creator>jacbenimble</dc:creator>
      <dc:date>2005-09-28T17:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/272741#M144990</link>
      <description>&lt;P class="MsoNormal"&gt;Hello Jackbenimble,&lt;BR /&gt;
&lt;BR /&gt;
It sounds like you are able to call other DLLs properly, so I am assuming that
there is no problem from the LabVIEW end of things.&amp;nbsp; I searched and found
a link to a patch for the software I believe you are trying to call &lt;A href="http://www.nist.gov/srd/nist23.htm" target="_blank"&gt;here&lt;/A&gt;.&amp;nbsp; If you have any
questions on exactly how to call third party DLLs please let us know -- I am
more than happy to provide some documentation and help on that.&lt;BR /&gt;
&lt;BR /&gt;
Hope that link helps.&amp;nbsp; Have a great afternoon!&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;/P&gt;

&lt;BR /&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 29 Sep 2005 20:08:03 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/272741#M144990</guid>
      <dc:creator>Travis_M.</dc:creator>
      <dc:date>2005-09-29T20:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/290706#M152738</link>
      <description>Any new developments on this front?&lt;BR /&gt;&lt;BR /&gt;I also need to access the Refprop DLL and can't seem to get the calling convention down. I have done a bunch of other DLL/labview interfaces before, however this one does not seem to conform to the normal rules of LabVIEW and dll calls.</description>
      <pubDate>Sun, 20 Nov 2005 16:12:43 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/290706#M152738</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2005-11-20T16:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291804#M153266</link>
      <description>&lt;P class="MsoNormal"&gt;Hello,&lt;BR /&gt;
&lt;BR /&gt;
I don’t know about the specific problems with this DLL, but LabVIEW is only
able to call with C or STDCALL (WINAPI) calling convention.&amp;nbsp; The DLL seems
to have a known issue (linked above) with some installation issues.&amp;nbsp; I do
not know if the customer above was able to get the software working, but please
let us know if you have any questions on how to use the Call Library Function
Node VI in LabVIEW with either calling convention.&lt;BR /&gt;
&lt;BR /&gt;
Have a great day!&lt;/P&gt;

&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 22 Nov 2005 22:29:02 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291804#M153266</guid>
      <dc:creator>Travis_M.</dc:creator>
      <dc:date>2005-11-22T22:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291811#M153270</link>
      <description>Yes, I was able to get this to work.
I e-mailed Dr. Lemmon and he was more than happy to provide examples of his code being called by LabView.
I am passing them on just as received.
If you make more VIs, would you  please forward them, or post them. We would all find some benifit in the shared work.
Thanks
John</description>
      <pubDate>Tue, 22 Nov 2005 22:39:01 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291811#M153270</guid>
      <dc:creator>jacbenimble</dc:creator>
      <dc:date>2005-11-22T22:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291812#M153271</link>
      <description>I spoke to a guy at NIST yesterday. He was able to send me a copy of a couple of VIs that somebody cobbled together to initialize and make one function call. Hopefully within the next couple of weeks (time permitting) I will have time to clean up those calls as well as implement some of the other calls in a more standard driver format.&lt;BR /&gt;&lt;BR /&gt;The problem with Refprop is not with the dll, per se, but more due to the somewhat cryptic way the parameters are entered.&lt;BR /&gt;&lt;BR /&gt;I plan on submitting my finished VIs back to NIST for inclusion with the next version of Refprop that will be releasing sometime early next year.</description>
      <pubDate>Tue, 22 Nov 2005 22:39:38 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291812#M153271</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2005-11-22T22:39:38Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291814#M153272</link>
      <description>Jack.....it looks like you got the same VIs I did, and from the same guy by the way.&lt;BR /&gt;&lt;BR /&gt;When I get my code together I will post it with NIST as possibly on my FTP site.</description>
      <pubDate>Tue, 22 Nov 2005 22:41:33 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/291814#M153272</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2005-11-22T22:41:33Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/477550#M229637</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;I was able to get Labview to call on Refprop for properties of a single pure fluid, but haven't been able to do this for a mixture. There seems to be a discrepency between the calls documented in the help file, and those in the Labview DLL call.&lt;/P&gt;
&lt;P&gt;Has anyone been able to call on properties of a mixture from Labview?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2007 16:37:14 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/477550#M229637</guid>
      <dc:creator>Will_Crowe</dc:creator>
      <dc:date>2007-02-13T16:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/478198#M229897</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;The attached zip file contains VIs in LV 7.1 format that shoud give you a leg up on getting going with Refprop.&lt;BR /&gt;
&lt;BR /&gt;
The code supports pure fluids as well as mixtures, but only a couple of
the calculations functions (SATP, SATT, TPFLSH), however it should give
you a good baseline for working out any of the other Refprop functions.&lt;BR /&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 14 Feb 2007 15:55:22 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/478198#M229897</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2007-02-14T15:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/480785#M231048</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Thank you&amp;nbsp;for those VI's.&lt;/P&gt;
&lt;P&gt;However, I still seem to have the same problem, namely how to get properties of a mixture back from the Refprop DLL. The "refrigerant file" input in your VI&amp;nbsp;is&amp;nbsp;a single string which can take a single refrigerant (pure fluid) name. When I try to enter a mixture name into this string control, nothing is returned.&lt;/P&gt;
&lt;P&gt;In the DLL descriptions that come with Refprop (for theSETUP subroutine) it names one of the inputs as "hfiles" and refers to this as an "array of file names specifying fluid/mixture components for each of the nc components". However, the control is a string control, not an array, so I can't figure out how you enter in several fluid names, to make up a mixture. I also don't know where you specify which mixture (the name, eg. R404A) that you want.&lt;/P&gt;
&lt;P&gt;If I could just get these calls right, I think everything else would be OK. Certainly I can get&amp;nbsp;labview to call in properties for a single fluid very easily, but I can't work it for a mixture.&lt;/P&gt;
&lt;P&gt;I really appreciate your help,&lt;/P&gt;
&lt;P&gt;Will&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2007 17:05:16 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/480785#M231048</guid>
      <dc:creator>Will_Crowe</dc:creator>
      <dc:date>2007-02-20T17:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/480849#M231069</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;LabVIEW missed a couple of wires in the file read code when I backward compiled it from 8.2 to 8.0 to 7.1&lt;BR /&gt;
&lt;BR /&gt;
Try this recompiled version. I verified it works with pure fluids and mixtures.&lt;BR /&gt;
&lt;BR /&gt;
Look in the VI tree at the example (Refprop Example.vi).&lt;BR /&gt;
Using this code, both pure fluids and mixtures are handled the exactly the same way.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;/DIV&gt;&lt;P&gt;Message Edited by gsussman on &lt;SPAN class="date_text"&gt;02-20-2007&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;12:19 PM&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2007 18:19:19 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/480849#M231069</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2007-02-20T18:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481428#M231315</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;I tried these VI's and managed to get properties for mixtures to read, which is major progress for me. However, I'm now getting a lot of errors (the type that require Labview to shut down). These don't happen all of the time. I use the part of the code that you sent me to initialise, and then I use the "Call_TPFLSHdll+Indicators" which I got some months ago (on this thread) to read properties when values of P and T are input. Maybe you have an updated version of the routine to do this. If not, can you suggest any possible reasons for the errors?&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Will&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2007 17:32:32 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481428#M231315</guid>
      <dc:creator>Will_Crowe</dc:creator>
      <dc:date>2007-02-21T17:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481433#M231318</link>
      <description>Unfortunately I don't have any functions other than the ones that are included in the zip file I sent you.&lt;BR /&gt;
&lt;BR /&gt;
LabVIEW errors (the type that require a shutdown) when calling a DLL
are normally indicative of passing the DLL the wrong data type(s) or
passing arguments that don't have the correct preinitialized size.
LabVIEW does not allow allocation of memory by the DLL, LV must pass
all parameters to the dll padded to specific lengths. The same holds
true for any data retruned from the DLL.&lt;BR /&gt;
&lt;BR /&gt;
The best advise I can give you is to use the code I sent you as a
baseline for extending the functionality to other Refprop function
calls.&lt;BR /&gt;
Use the calling convention detailed in my code. DO NOT use the calling
conventions used in the code you originally received from NIST. The
NIST calling conventions are not formatted 100% correctly. They will
work for pure fluids but will fail when attempting to work with
mixtures.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Feb 2007 17:40:31 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481433#M231318</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2007-02-21T17:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481452#M231325</link>
      <description>&lt;DIV&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;I believe that most of these calculations have limits on the ranges. If a calculation attempt is made and the data input is not a reasonable number you will get this error. Maybe you could use some sort of valid range check before attempting the call. You could use the example Excel program supplied on with the NIST CD to check the response with the given data. I believe that if you attempt to give it data that is out of range it will respond with an error and allowable ranges. (In the excel example) &lt;/FONT&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/P&gt;&lt;FONT face="Helv" size="2"&gt;
&lt;P&gt;- There are 10 kinds of people in the world, those that know binary, and those that don't &lt;/P&gt;&lt;/FONT&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 21 Feb 2007 18:01:29 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481452#M231325</guid>
      <dc:creator>jacbenimble</dc:creator>
      <dc:date>2007-02-21T18:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481566#M231365</link>
      <description>You are correct about the allowable ranges, however that should only
generate an error in the error cluster, and appropriate error source
text.&lt;BR /&gt;
Range checking would be a pretty difficult operation in that in many
cases you have multi variable dependence. My recomendation would be to
simply perform the calculation and pick up any errors returned by
Refprop.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&amp;nbsp;That being said, I believe the error that he described (LV crashes) is the result of an improper DLL call.&lt;BR /&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 21 Feb 2007 22:04:45 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/481566#M231365</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2007-02-21T22:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/482145#M231628</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#000000"&gt;&lt;FONT face="Times New Roman"&gt;As you say, I don’t think that it’s due to out of range values because sometimes it doesn’t give the error for several runs of the program, and then it appears even though the input values (and therefore the returned values) haven’t changed.&lt;NAMESPACE prefix="o" ns="urn:schemas-microsoft-com:office:office"&gt;&lt;P&gt;&lt;/P&gt;&lt;/NAMESPACE&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;P&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#000000"&gt;&lt;FONT face="Times New Roman"&gt;I tried to see if the error correlated with anything (time intervals between runs etc.) and the behaviour is pretty eratic – sometimes the program runs and sometimes it crashes.&lt;P&gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;P&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#000000"&gt;&lt;FONT face="Times New Roman"&gt;One strange thing that happens if I’m editting the program that calls TPFLSHdll, is that &lt;P&gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#000000"&gt;&lt;FONT face="Times New Roman"&gt;&lt;SPAN style="mso-spacerun: yes"&gt;&amp;nbsp;&lt;/SPAN&gt;when I go to save or close the changed program, I occasionally get a report of an “insane” object and then a message saying there has been a Fatal Internal Error. So, even when I don’t run the VI that links to the DLL, but simply edit the program that contains this VI, unusual errors can arise.&lt;P&gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;P&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#000000"&gt;&lt;FONT face="Times New Roman"&gt;I will try to check the calls to the DLL, but they seem to be what’s documented by NIST. Also, would the fact that it works fine for pure substances not suggest that the calls are OK?&lt;P&gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;P&gt;&lt;FONT face="Times New Roman" color="#000000" size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;SPAN lang="EN-GB" style="mso-ansi-language: EN-GB"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#000000"&gt;&lt;FONT face="Times New Roman"&gt;Regards, Will.&lt;P&gt;&lt;/P&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2007 23:13:08 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/482145#M231628</guid>
      <dc:creator>Will_Crowe</dc:creator>
      <dc:date>2007-02-22T23:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/504702#M240708</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Dear gsussman,&lt;/P&gt;
&lt;P&gt;I have been using the VI's that you posted to this forum to extract properties for R404A from refprop, and I am delighted to say that they are working well. The files that I earlier got from NIST were giving intermittent errors, on which subject you commented previously in this thread. I am currently using the TPFLSH routine to extract enthalpy values when P and T values are input. I would like, now,&amp;nbsp;to do a similar routine for for PHFLSH (as I cannot find entropy with&amp;nbsp;a PT input pair for one of the points) and I was hoping to look at the code of your TPSLSH routine. All that I wish to check is what is different about your call to the DLL and the call in the&amp;nbsp;VI posted by NIST, that makes your one stable, and the other one crash. Would it be possible to get a non-passworded version of TPFLSHdll.VI to check this? I know this is a bit cheeky, but many of the other VI's that you posted are not passworded, and it would probably unlock the reason for the errors and allow me to develop other similar VI's.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Will&lt;/P&gt;</description>
      <pubDate>Tue, 10 Apr 2007 16:55:19 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/504702#M240708</guid>
      <dc:creator>Will_Crowe</dc:creator>
      <dc:date>2007-04-10T16:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/691168#M316839</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Hi guys,&lt;/P&gt;
&lt;P&gt;I see you have already come accross my problem before!&lt;/P&gt;
&lt;P&gt;I am looking to get hold of the converter of refprop for use with simply converting nominal&amp;nbsp; density values into pressure. I have used all the SubVI measurements that you have sent me already but none of them see to have the function that i actually need. Was just wandering if I was going about this the wrong way or there was something else that might be helpful out there.&lt;/P&gt;
&lt;P&gt;Basically&amp;nbsp;I just want to use the pressure and density functions. of the dll. I have some VB code which seems to be doing it ok. Any ideas. Would be great to get in contact about this. Best regards Pete Davies&lt;/P&gt;
&lt;P&gt;&lt;A href="mailto:davies.pg@gmail.com" target="_blank"&gt;davies.pg@gmail.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Apr 2008 10:52:42 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/691168#M316839</guid>
      <dc:creator>AustinPeter</dc:creator>
      <dc:date>2008-04-17T10:52:42Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/692209#M317293</link>
      <description>Pete

Just because the actual DLL call to the specific REFPROP function you need is not included in the supplied VIs, does not necessarily mean that it is not available in the REFPROP dll. The code developed was only those functions that I required when I built my original app. There was quite a number of functions that have not been included.

If you can perform the function using the actual REFPROP exe file then there is a way to do it using the LabVIEW calls (some included, some you will have to build yourself).

The key to doing it is to use the functions I posted earlier in this thread as a baseline for creating your own functions. Be very aware of the data sizes of the inputs to the DLL. Most of my code checks and formats it properly so don't strip that out by accident.

Regards,
Greg</description>
      <pubDate>Fri, 18 Apr 2008 15:48:42 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/692209#M317293</guid>
      <dc:creator>gsussman</dc:creator>
      <dc:date>2008-04-18T15:48:42Z</dc:date>
    </item>
    <item>
      <title>Re: refprop</title>
      <link>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/852432#M386513</link>
      <description>Hello, I have downloaded your Refprop zipped file for LV 7, thak you very much for your time and effort here.&amp;nbsp; I am missing the Refprop.dll, I guessing that it is not included in your zipped folder but I wanted to be sure.&amp;nbsp; Where would I find the Refprop.dll?&amp;nbsp; Thanks.</description>
      <pubDate>Thu, 12 Feb 2009 23:47:34 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/refprop/m-p/852432#M386513</guid>
      <dc:creator>jon_mcbee</dc:creator>
      <dc:date>2009-02-12T23:47:34Z</dc:date>
    </item>
  </channel>
</rss>

