Instructions for the use of Brooks DLL with LabVIEW and Windows Operating Systems

Date: Oct 29, 2009 Version: 164J027_AA.zip Dear Brooks LabVIEW DLL User, After unzipping the zip file, you now have the DLL file BrooksDLL.dll and 11 LabVIEW example files. Theses LabVIEW example files were written in version 6.1. To start communication with Brooks S-Series (58xxS), SLA (SLA58xxS) or 4800 (48xxS) digital mass flow devices with LabVIEW, you first have to run the GetDeviceID Example which extracts the device address information. Please look at the LabVIEW diagram on the left of the CallLibraryFunctionNode: the COM port number is set as an integer only (there is no COM involved) and at present a COM port number <= 9 should be used; the BaudRate is also set as an integer value; please select the Drop Type, which can be single drop when only 1 device is connected or multi drop when multiple devices are connected; in case of multi drop you also have to provide the TAG number, in single drop mode this is not required; please enter the TAG number in case of multi drop mode (the TAG# is displayed on a sticker on the side of the device, if this sticker is not present the TAG# can be determined from the serial number e.g. T56761/007, where the TAG# is 56761007. The boxes labeled IDH, IDM, IDL and IDS are the device ID bytes and when you run the program you should get these four numbers appearing on the LabVIEW front panel and also a value of 1 in the Output Param and an OK in the Function Output Comment box; if the number in the Output Param is not 1 there is an error and the S1 and S2 hex and string fields will indicate the error. When this is working please move on to the other DLL functions which should be straightforward to implement. When you then go on to call the other DLL functions ReadSetPoint, WriteSetPoint, ReadFlow, ReadFlowMultipleDevices, ReadAdditionalStatus, ReadTotalizer, ReadTotalizerState, WriteTotalizerState, ReadValveOverRide and WriteValveOverRide you need to supply the function call with the device ID bytes you obtained above; this is shown in the examples (the device ID bytes are in Hex notation). If you have any problems please contact us, contact information can be found on our website, http://www.brooksinstrument.com/. Kind Regards, Brooks Instrument Known issues: None.

Brooks Instrument www.brooksinstrument.com