|
|
|
| R2012a Documentation → Instrument Control Toolbox | |
Learn more about Instrument Control Toolbox |
|
| Contents | Index |
This table summarizes what is new in Version 3.0 (R2011b):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
Yes | Yes | Bug
Reports |
New features and changes introduced in this version are:
The toolbox now supports Bluetooth® devices. Instrument Control Toolbox supports the Bluetooth serial port profile (SPP).
The Instrument Control Toolbox Bluetooth interface lets you connect to devices over the Bluetooth interface and to transmit and receive ASCII and binary data. You can identify any SPP Bluetooth device and establish a two-way connection with that device.
Bluetooth is an open wireless technology standard for exchanging data over short distances using short wavelength radio transmissions from fixed and mobile devices using a packet-based protocol. Bluetooth provides a secure way to connect and exchange information between devices such as Lego Mindstorm NXT robots, USB Bluetooth adaptors (dongles), wireless sensors, mobile phones, faxes, laptops, computers, printers, GPS receivers, etc.
To identify Bluetooth devices in the Instrument Control Toolbox, use the instrhwinfo function on the Bluetooth interface, called Bluetooth.
For information on using the Bluetooth interface, see Controlling Instruments Using Bluetooth.
A new family of instrument support, Quick-Control Instruments, is being introduced. For R2011b, the Quick-Control Oscilloscope is available. You can use this new oscilloscope function for simplified oscilloscope control and waveform acquisition.
Create the Quick-Control Oscilloscope object using the Instrument Control Toolbox oscilloscope function. It provides a simplified way to control oscilloscopes and perform waveform acquisitions without dealing with the underlying drivers. It can be used with scopes using IVI-C or IVI-COM drivers.
For information on prerequisites, functions that work with the Quick-Control Oscilloscope, and a full workflow example of using it, see Using Quick-Control Oscilloscope.
In both the command-line and the Test & Measurement Tool, a generic VISA interface is now supported. In the Test & Measurement Tool, generic devices appear in the More node under the VISA node. In the command-line toolbox, they are available as a type 'generic'.
For example, if you have a generic VISA device that is made by National Instruments®, you could use the instrhwinfo function to see it:
instrhwinfo('visa','ni','generic')You can use this generic support to communicate over open VISA sockets, USB Raw, etc.
For more information, see Working with the Generic Interface.
In the Test & Measurement Tool, instruments that use the VISA interface now appear under the VISA node in the instrument tree. For example, if you are using a TCP/IP instrument with the VISA interface, instead of a TCP/IP - VISA node in the tree, you will see a VISA node, with a TCP/IP node under it. It is easier to see what protocols are using the VISA interface with the VISA node.
Also, the generic VISA interface is now supported. Generic devices appear in a More node under the VISA node in the instrument tree. If your instrument is recognizable as a type such as 'gpib' or 'tcpip', it appears in that type-specific node. For example, a TCP/IP instrument appears in the TCPIP node under the VISA node. But if it is a generic instrument, it appears in the More node.
For R2011b, error and warning message identifiers have changed in the Instrument Control Toolbox software.
If you have scripts or functions that use message identifiers that changed, you must update the code to use the new identifiers. Typically, message identifiers are used to turn off specific warning messages, or in code that uses a try/catch statement and performs an action based on a specific error identifier.
For example, the <'illustrative:old:ID'> identifier has changed to <'new:similar:ID'>. If your code checks for <'illustrative:old:ID'>, you must update it to check for <'new:similar:ID'> instead.
To determine the identifier for a warning, run the following command just after you see the warning:
[MSG,MSGID] = lastwarn;
This command saves the message identifier to the variable MSGID.
To determine the identifier for an error, run the following command just after you see the error:
exception = MException.last; MSGID = exception.identifier;
Note: Warning messages indicate a potential issue with your code. While you can turn off a warning, a suggested alternative is to change your code so it runs warning-free.
 | Version 3.1 (R2012a) Instrument Control Toolbox Software | Version 2.12 (R2011a) Instrument Control Toolbox Software |  |
Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
