fclose

Disconnect interface object from instrument

Syntax

fclose(obj)


Arguments

obj	An interface object or an array of interface objects.

Description

fclose(obj) disconnects obj from the instrument.

Examples

This example creates the GPIB object g, connects g to the instrument, writes and reads text data, and then disconnects g from the instrument using fclose.

g = gpib('ni',0,1);
fopen(g)
fprintf(g,'*IDN?')
idn = fscanf(g);
fclose(g)

At this point, you can once again connect an interface object to the instrument. If you no longer need g, you should remove it from memory with the delete function, and remove it from the workspace with the clear command.

Tips

If obj was successfully disconnected, then the Status property is configured to closed and the RecordStatus property is configured to off. You can reconnect obj to the instrument using the fopen function.

An error is returned if you issue fclose while data is being written asynchronously. In this case, you should abort the write operation with the stopasync function, or wait for the write operation to complete.

Version History

Introduced before R2006a

R2024a: i2c object interface warns

Use of this function with an i2c object issues a warning that i2c will be removed in a future release. To connect to a peripheral device on an I2C controller, use the device function with an aardvark or ni845x object, its functions, and its properties instead.

The recommended functionality has additional capabilities and improved performance. See Transition Your Code to aardvark or ni845x Interface for more information about using the recommended functionality.

R2023a: i2c object interface will be removed

Use of this function with an i2c object will be removed in a future release.

R2021b: gpib object interface will be removed

Use of this function with a gpib object will be removed. To access a GPIB instrument, use the VISA-GPIB interface with a visadev object, its functions, and its properties instead.

The recommended functionality has additional capabilities and improved performance. See Transition Your Code to VISA-GPIB Interface for more information about using the recommended functionality.

R2021a: tcpip, visa, and serial object interfaces will be removed

Use of this function with the tcpip (with NetworkRole set to server), visa, and serial interfaces will be removed. Use the following interfaces and their functions instead. The recommended interfaces have additional capabilities and improved performance.

Functionality	Use This Instead	Additional Information
tcpip	tcpserver	Transition Your Code to tcpserver Interface
visa	visadev	Transition Your Code to visadev Interface
serial	serialport	Transition Your Code to serialport Interface

R2020b: Bluetooth, tcpip, and udp object interfaces will be removed

Use of this function with the Bluetooth, tcpip (with NetworkRole set to client), and udp interfaces will be removed. Use the following interfaces and their functions instead. The recommended interfaces have additional capabilities and improved performance.

Functionality	Use This Instead	Additional Information
Bluetooth	bluetooth (case-sensitive)	Transition Your Code to bluetooth Interface
tcpip	tcpclient	Transition Your Code to tcpclient Interface
udp	udpport	Transition Your Code to udpport Interface

R2019b: serial object interface is not recommended

Use of this function with a serial object is not recommended. To access a serial port, use a serialport object instead.

The recommended functionality has additional capabilities and improved performance. See Transition Your Code to serialport Interface for more information about using the recommended functionality.