Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

interface with Mettler-Toledo FP90?

Hi-
I'm new to LV yet, I'm trying to write an application that interfaces with an HP multimeter and a Mettler-Toledo FP90 temperature controller. Each device has a serial port dedicated to it. The interface driver to the HP multimeter I found was already included as an example in LV5.1, however I could not find any intrument drivers or code to interface with the Mettler FP90 (if anyone knows where I can get it, I'd greatly appreciate it) However, I do have a document from Mettler detailing how to control remotely and the commands.

I've managed to interface with both machines at the same time. However, there is no query function for the M-T FP90 so I have to continually read the serial port for a trigger code. The
trigger code that I thought appropriate would be the change of status code that would correspond to "beginning temperature program"

According to the Mettler-Toledo document on remote control of the FP90 the change of state report is in the form of U\s#####\s#####\r\n
The following is their definition:

" The first value represents the curren state of the FP90's internal state machine. It is a decimal unsigned integer, composed of two byte values representing the current state of the two state machines in the FP90 firmware, (the second value has not been defined yet)."

They continue to say:

"The high order byte represents the user interface state machine, the low order byte represents the cell control state machine."

They also list numbers that represent different states. The high order bytes has 0 to 43 and the low order byte has 0 to 16 entries.

As you probably guessed, I'm new to this, so I was wondering if someone could help me understand what the above quotes me
an, specifically what could they mean by high and low order bytes?

Much appreciated,
F. Asfour
0 Kudos
Message 1 of 2
(3,630 Views)
Hello-

I found some Mettler drivers at http://zone.ni.com/idnet Maybe these drivers can be modified to work for you.

There are also other options. First, I would like you to submit a request for this driver at:
http://zone.ni.com/idnet/other.htm
We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.

If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://zone.ni.com/idnet/development.htm

We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize i
n driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance

See http://zone.ni.com/idnet/other.htm for more options.

Randy Solomonson
Applications Engineer
National Instruments
0 Kudos
Message 2 of 2
(3,630 Views)