Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

HART driver for Brooks MFC

Hi Albert,

we're looking for a HART labview driver and I've found a thread on this forum in which you've provided some labview VIs to support the HART protocol, can you tell me what the status is of this driver (tested and found working, is there an update available maybe?) and whether or not I can use it freely?

Thanks,

Egon.

0 Kudos
Message 11 of 34
(9,576 Views)
Hi

I did not work on this llb since then.
You can use it freely.
If you have extensions or made it better, you always can post it here or in the NI driver section
greetings from the Netherlands
0 Kudos
Message 12 of 34
(9,555 Views)

Hello,

 

Apparently, I am following the same steps as you - I am trying to communicate to the Brooks 5800 series MFC and 0154 2ndary electronics via LabView.  Does anyone have any luck since?  How do you get the Tag ID out without their software?

 

Thanks

wkc

0 Kudos
Message 13 of 34
(9,000 Views)

Hi

 

I'm speaking out of my head, but the demo software runs for 5 minutes and shows the tag.

Give it a try and fill this tag in the send vi.

greetings from the Netherlands
0 Kudos
Message 14 of 34
(8,973 Views)

Brooks models 0154 have fixed tag ID's for the 4 channels (channel1, till channel4)

For Labview applications Brooks has software (Smart DDE)acting as a driver between the LabView application and the 58xxS Mass Flow Controllers (MFC's) and can be purchased via Brooks.

Another way is to directly program in LabView (without the Smart DDE) by programming in the HART protocol (a HART communication Manual is available from the Brooks website).

 

Adrie

0 Kudos
Message 15 of 34
(8,787 Views)

Here is an improved version of the Brooks MFC LabVIEW control software. (I orginally started of with the software posted here, so many thanks for this!).

The LVOOP approach is used.

Use the Constructor.vi to initialise your MFC and use Destructor.vi to release resources.

The low level HART protocol is programmed in the Communication folder within the Brooks MFC.lvclass and does not have to be used.

Some commonly used functions to control the MFC are found in the root folder of the class, such as "write setpoint" e.g.

 

Good luck with it!

Message 16 of 34
(8,523 Views)

Thanks Pieter

once in a while such a gift bounces back in a positive way

greetings from the Netherlands
0 Kudos
Message 17 of 34
(8,514 Views)
Hi Pieter, Could you please post an example on how to use the class with two or more mass flow controllers? Thanks in advance Rob
0 Kudos
Message 18 of 34
(8,125 Views)

Hi Rob,

The driver is written using LVOOP, meaning LabVIEW Object Oriented Programming. The idea is that you create "instances" of the class, in this case the brooks MFC driver. So in order to use multiple instruments you have to create multiple instances. Please find out a bit more about LVOOP and everything will become clear. You can place your instances in an array and then control an arbitrary number of MFC's.

Pieter

0 Kudos
Message 19 of 34
(8,058 Views)

Hello Pieter,

 

I try to use your example to read Brooks MFM 5861S.

 

Could you help me to configure all parameters to do work the communication, I have an error when I try to do this.

 

I had configure my port com1, in contructor.vi, and I run Brooks MFC read response but it don't work

Thanks

 

0 Kudos
Message 20 of 34
(7,864 Views)