Measurement Studio Support for Visual Studio 6.0 Readme

Measurement Studio Support for Visual Studio 6.0 provides ActiveX controls for use in Visual Basic 6.0 and Visual C++ class libraries for use in Visual C++ 6.0. Refer to Measurement Studio 7.1 Visual Studio 6.0 Support New Features for information about the features introduced in Measurement Studio 7.1 that are available for use in Visual Basic 6.0 and Visual C++ 6.0.

Note   For information about Measurement Studio 7.1 for Visual Studio .NET 2003, refer to Start»All Programs»National Instruments»Measurement Studio for VS .NET 2003»Measurement Studio Readme.

Measurement Studio Support for Visual Studio 6.0 is Measurement Studio 6.0 with the addition of an installer that includes updates to the following components:

• Traditional NI-DAQ ActiveX controls
• User Interface ActiveX controls
• IVI ActiveX controls
• Visual C++ User Interface class library
• Visual C++ NI-488.2 class library

The installer updater includes updates made in Measurement Studio 7.0 and updates made in Measurement Studio 7.1.

Note   LabWindows/CVI is not included with Measurement Studio Support for Visual Studio 6.0. LabWindows/CVI is included as a separate installer with Measurement Studio 7.0 Enterprise Edition.

This file contains the following sections:

• System Requirements
• Installing Measurement Studio Support for Visual Studio 6.0
• Updates to ActiveX Controls and Visual C++ Class Libraries
• Known Issues in Measurement Studio Support for Visual Studio 6.0

Refer to the Measurement Studio for Visual Basic Version 6.0 readme and the Measurement Studio for Visual C++ Version 6.0 readme for more information on features, distribution, upgrading, and known issues. These readmes are installed to Start»Programs»National Instruments»Measurement Studio»Readme Files.

System Requirements

Visual Basic

To use the Measurement Studio ActiveX controls, your computer must have the following:

• Microsoft Windows 2000/NT/Me/98 operating system (Windows NT users need NT 4.0 with Service Pack 3 or later)
• ActiveX control container such as Microsoft Visual Basic (32-bit version)
• Appropriate hardware and driver software if you are going to use a Measurement Studio I/O hardware control
• Pentium-class microprocessor (Pentium 90 MHz or higher microprocessor recommended)
• VGA resolution (or higher) video adapter (16-bit color recommended for the user interface and 3D graph controls)
• Memory requirements:
• 32 MB for Microsoft Windows 98 or later (48 MB recommended)
• 32 MB for Microsoft Windows NT (48 MB recommended)
• 64 MB of memory for Microsoft Windows Me and Microsoft Windows 2000
• Minimum of 85 MB of free hard disk space for the Measurement Studio for Visual Basic Full Development System
• Microsoft-compatible mouse

Visual C++

To use the Measurement Studio Visual C++ class libraries, your computer must have the following:

• Windows 2000/NT/Me/98 (Windows NT users need Windows NT Service Pack 3 or later)
• Pentium 133 MHz (Pentium 266 MHz or higher recommended)
• 32 MB RAM (62 MB recommended)
• 132 MB free disk space
• Microsoft Visual C++ 6.0 and Service Pack 3 or later

Installing Measurement Studio Support for Visual Studio 6.0

Note   If you have a version of ComponentWorks installed on your computer, uninstall that version before installing Measurement Studio. To uninstall ComponentWorks, select Start»Settings»Control Panel»Add/Remove Programs. Select NI ComponentWorks from the list of programs and press the Add/Remove button.

Note to Windows 2000/NT Users   You must be logged in to your computer with administrator privileges to install Measurement Studio. Otherwise, the setup program might produce a blank dialog error or an error stating "You must have system administrator privileges to install or modify this product."

Note to LabVIEW Users   If you install any component of Measurement Studio and NI-DAQ 6.7 or earlier on your machine and you then install LabVIEW 6i, the LabVIEW 6i installer will remove the NI-DAQ support for Measurement Studio. If the LabVIEW 6i installer removes the NI-DAQ support for Measurement Studio, you must download and install NI-DAQ 6.8 or later to restore the NI-DAQ support for Measurement Studio. To download NI-DAQ, go to http://digital.ni.com/softlib.nsf/current, select Multifunction DAQ, and then select NI-DAQ 6.8 or later.

1. Install driver software and hardware if you need to acquire data or control instruments in your program. Driver software performs the low-level calls to your hardware. You must install and configure the corresponding driver software and hardware before you can use any of the Measurement Studio hardware I/O controls or class libraries, including the DAQ, GPIB, Serial, VISA, IVI, and IMAQ controls.

   Some Measurement Studio ActiveX controls and class libraries require features provided only in the newest versions of the driver. You can download the most current driver from the National Instruments Web site at ni.com.

2. Install your hardware device. Refer to your hardware installation guide for information.
3. Configure your device with National Instruments Measurement & Automation Explorer (MAX). After configuring your hardware, MAX contains information about the hardware that you might need to use the Measurement Studio I/O controls and class libraries. For example, use the device number from MAX to specify a device with an I/O control.
4. Insert the Measurement Studio Support for Visual Studio 6.0 CD in the CD drive of your computer. If the CD startup screen does not appear, use Windows Explorer to run the SETUP.EXE program from your CD.
5. If you do not already have Measurement Studio 6.0 installed, click Install NI Measurement Studio 6.0 and follow the instructions on the screen. If you do have Measurement Studio 6.0 installed, go to step 6 of this list.
6. Click Update NI Measurement Studio 6.0 and follow the instructions on the screen.

Updates to ActiveX Controls and Visual C++ Class Libraries

Measurement Studio Support for Visual Studio 6.0 has an installer that includes updates to Traditional NI-DAQ ActiveX controls, user interface ActiveX controls, IVI ActiveX controls, the Visual C++ User Interface class library, and the Visual C++ NI-488.2 class library.

The following sections list previous issues that are fixed in Measurement Studio 7.0 and Measurement Studio 7.1.

Note   Changes made to user interface ActiveX controls also apply to Measurement Studio Visual C++ applications.

Updates for Traditional NI-DAQ ActiveX Controls

The following list describes issues with traditional NI-DAQ ActiveX controls that are fixed in Measurement Studio 7.0:

• 2XJH9EYV: No way to synchronize multiple PXI-4472 DAQ devices with Data Acquisition controls.
• 2XJHUUYV: Cannot use DSA IEPE current excitation with Data Acquisition controls.
• 2IHDI79V: Data Acquisition controls do not support correlated DIO.
• 2T6CFI00: CWCounter OutputMode property not available.
• 1RP9BQWV: Data Acquisition controls do not provide Filter and Prescale properties in property pages.
• 216EH5TB: CWPulse property pages do not recognize decimal separator symbols other than ".".
• 318GPK36: Pulse train on 6602 with external source does not work using CWPulse.
• 29AECIC2: CWDI error when doing continuous input.
• 2OT9MU3P: Data Acquisition controls digital change detection does not work properly.
• 2ID7RUWW: Data Acquisition controls do not support buffered event counting with initial count.
• 2DOALM78: CWCounter is missing ReadBacklog method.
• 2ZBEMR90: Right-click help does not work for Data Acquisition controls.
• 2X1FRS56: The cwdaq.ocx file is missing digital signature.
• 2CNC7ECQ: Error using CWDaqTools AIParameter.
• 1QCH4VWV: CWCounter Pulse and OutputMode not programmatically accessible.
• 2WS8DLO6: Run time error configuring CWCounter gate parameters in some circumstances.

Updates for User Interface ActiveX Controls

The following lists describe issues with user interface ActiveX controls that are fixed in Measurement Studio 7.0 and Measurement Studio 7.1.

Measurement Studio 7.0 Updates

• 2OQ85K9Q: CWGraph annotation shape sometimes filled when FillVisible property set to false.
• 2GABILDD: CWGraph FillToBase does not fill the last segment for some sizes of input data.
• 2M6CJ69Q: Intermittent crash when using CWGraph FillToBase feature.
• 2EEEBPR7: Error when setting CWGraph annotations visible property.
• 2OD3ST7N: Memory leaks when using CWGraph annotations.
• 2C4GQTQK: CWGraph cuts off data when ChartHistory is exceeded.
• 1YSBM7K5: CWGraph does not properly handle values of positive infinity, negative infinity, and NaN.
• 2U9GNPQ6: Maximum number of annotation shape vertices too small. Increase to 1000.
• 2O7GJVQF: Cannot set 3D graph view center properties before the graph is displayed.
• 2V9F90QF: Memory leaks when using CWGraph3D with cursors.
• 1XILP0OP: CWNumEdit gives Type Mismatch error if you leave the value blank.
• 1IRD2I4S: CWNumEdit disappears when Esc key pressed on Visual C++ (MFC) dialog.
• 1XBCLUNG: CWNumEdit does not honor acceleration delay time when set from property page.
• 2B8E749Q: CWButton responds to keyboard input when in indicator mode.
• 32U8LTSP: Control help links and commands stop working after installing LabVIEW to a machine with Measurement Studio.
• 2HRHFOX0: Controls with Windowless true paint incorrectly in Visual C++ .NET 2003 dialog (MFC).
• 2ZDBNFA7: What's This help does not work from sub property pages.
• 2WS99J00: Controls missing font-related properties.
• 2C5HNRQK: The cwui.ocx and cw3dgrph.ocx files are missing digital signatures.
• 299FCITE: CWGraph does not autoscale to data that is plotted when the containing form is loaded.
• 282EM33P: CWGraph3D cursor label background does not repaint correctly in some circumstances.
• 201E78TE: Cannot programmatically set axis to value pairs only mode.
• 11O7GRI7: CWButton gives no indication that it is disabled.
• 2EFC9T56: CWGraph3D ImportStyles and ExportStyles do not work correctly.
• 2JJGFHK0: CWNumEdit does not correctly parse values using symbolic engineering format.
• 2QGFBN1F: CWGraph3D hangs LabVIEW if you select a large value for an axis maximum.
• 2RIA9HQF: Unable to use NiMesaDLL.msm to build an installer.
• 2XCDP2Q6: CWGraph property pages cause Visual Basic to crash in some circumstances.

Measurement Studio 7.1 Updates

• 104DKF44: CWNumEdit flickers when set to same value.
• 2VICJRQ6: CWNumEdit in indicator mode changes displayed value when the user clicks on the control.
• 37L57LAQ: CWNumEdit does not work properly when decimal separator symbol is anything other than ".".
• 35JEACY0: Cannot tab past a CWNumEdit on a Visual C++ .NET 2003 (MFC) dialog.
• 31KKGJ00: Member not found error attempting to access CWGraph annotation shape image.
• 30BFPFHW: CWGraph does not clip plots correctly in some scenarios.
• 2VD32QCM: CWGraph plot, annotation, and cursor events not disabled when the object Enabled property is false.
• 2OIC4S9Q: CWGraph annotation arrow properties do not show up in the bindable properties list in the property page.
• 0HACJ144: No way to undo zoom operations in CWGraph.
• 37BGRLZ8: CWGraph floating cursors incorrectly snap to data when plotting continuously.
• 372B6L45: CWGraph charting with inverted x axis and autoscaling stops working after approximately 3000 points.
• 36H7RVA7: Points are drawn outside of the CWGraph plot area for large point styles.
• 2XC9FMQF: Image returned by CWGraph ControlImage has fonts squeezed upon resizing. Use ControlImageEx instead of ControlImage.
• 2OJ7RR7W: CWGraph plots sometimes render small ticks next to data points.
• 2HKI5HOP: CWGraph does not notify of cursor mouse up/down events when the cursor is over an annotation.
• 2ZGDJ5RS: CWGraph3D does not autoscale color map colors when plot data changes.
• 2G3D19JB: CWGraph3D cursor dragging does not function correctly when the x axis is inverted.
• 2HR6R0JB: Changes made to colors of CWSlide increment and decrement buttons in property pages are not committed.
• 364MLB00: Cannot specify CWButton as the default button or cancel button of a form.
• 38RD7E00: Editing value pairs does not work properly when decimal separator symbol is anything other than ".".
• 35RABO9Q: Controls do not always persist property page changes in Visual C++ .NET 2003 (MFC) resource editor.
• 29T9FK5G: Non-solid line styles render as solid in stretched metafile. Use ControlImageEx instead of ControlImage.
• 25BF85C2 - CWGraph3D ViewXCenter, ViewYCenter, and ViewZCenter properties do not correctly adjust to new axis ranges under some circumstances.
• 39FJ26WQ - CWGraph3D fails to translate system color properly encoded within an OLE_COLOR into the correct RGB color.

Updates for IVI ActiveX Controls

The following list describes issues with IVI ActiveX controls that are fixed in Measurement Studio 7.0:

• 2Y9DCCDD: CWIVIScope Fetch method behaves the same as the Read method.
• 2XE9L9IA: CWIVIFgen does not change the duty cycle as expected.
• 265D0A3P: CWIviDCpower run continuously button does not behave correctly after removing channels.

Updates for Visual C++ User Interface Class Library

The following issue with the Visual C++ User Interface class library is fixed in Measurement Studio 7.0:

• 2YR9K800: Memory leaks in the User Interface and 3D Graph class libraries when calling methods with input string parameters and when setting string properties.
• 209C6RYV: CNiGraph ChartXvsY plots data instead of charts data.
• 2P5BK59Q: Exception accessing CNiShape Image from an annotation.

The following issue with the Visual C++ User Interface class library is fixed in Measurement Studio 7.1:

• 3489FC00: Adding Measurement Studio instrsup.lib prevents some ANSI C library functions from being linked into a C++ project.

Updates for Visual C++ NI-488.2 Class Library

The following issue with the Visual C++ NI-488.2 class library is fixed in Measurement Studio 7.0:

• 2YQHPP00: Memory leaks when destroying CNi4882Board and CNi4882Device objects.

Known Issues in Measurement Studio Support for Visual Studio 6.0

• If you install newer, unlicensed versions of Measurement Studio ActiveX controls on a machine that has previously licensed versions of the Measurement Studio controls, the controls might exhibit one of the following behaviors:
  • The licensed controls become evaluation software for 30 days.
  • The licensed controls do not let you use functionality that was present in the licensed version.
  Fix these states by using the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder.
• If you install older, licensed versions of Measurement Studio ActiveX controls on a machine that has newer, unlicensed versions of the Measurement Studio controls, the controls might exhibit evaluation software behavior for 30 days. Fix this state by using the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder.
• If you have installed Measurement Studio 7.0 on a machine that has prior versions of the Measurement Studio user interface and 3D graph controls and then uninstall Measurement Studio 7.0, the controls might exhibit evaluation software behavior for 30 days. Fix this problem by using the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder.

  (Applications that install prior versions of the Measurement Studio user interface and 3D graph controls include ComponentWorks 2.0, Measurement Studio 1.0, Measurement Studio 6.0, and LabVIEW 6i).

• When you use NI-DAQ 6.x or Traditional DAQ 7.x, error messages might appear while loading, executing, or debugging an application. Refer to the Unusual Error Messages Loading, Executing, or Debugging an Application When Using NI-DAQ 6.x for Windows article in the KnowledgeBase for information on how to resolve this issue.
• When using the Measurement Studio Visual C++ User Interface or 3D Graph class libraries on Windows 98 or ME, your application might hang while accessing a method or property of a control class many times, as in a loop, for example. To work around this problem, you must initialize each control for access only from a single thread. For example, if you have a graph named m_graph as a member variable of a dialog box named CMyDialog, the CMyDialog constructor would appear as the following:

  CMyDialog::CMyDialog :
       CDialog(CMyDialog::IDD, pParent),
       m_graph(CNiInterface::SingleThread)
  

  This workaround prevents you from accessing the control from a thread other than the one that created it. If you do need to access the control this way, you must marshal the interfaces manually or upgrade the OS to Windows 2000 or XP.