VI Logger 1.1.1 Readme March 2004 This file contains important last-minute information about VI Logger 1.1.1. Refer to the National Instruments Web site at ni.com for the latest information about VI Logger. ***************************** ** Software Requirements ** ***************************** The computer on which you are running VI Logger 1.1.1 must meet the following software requirements: * Measurement & Automation Explorer (MAX) version 3.0 or later * NI-DAQ 7.0 or later and/or FieldPoint version 4.0 or later * If you are running the VI Logger LabVIEW addon, LabVIEW version 7.0 or later To install VI Logger 1.1.1, run setup.exe. ******************************* ** New for VI Logger 1.1.1 ** ******************************* VI Logger 1.1.1 fixes the following problems: * VI Logger 1.1 installed a prerelease version of the LabVIEW Run-Time Engine. VI Logger 1.1.1 ships with the correct version of LabVIEW. However, if you upgrade from VI Logger 1.1 to VI Logger 1.1.1, VI Logger still uses the prerelease version. This setup presents no known problems, but you might want to install the released version. Complete the following steps to install the released version of the LabVIEW Run-Time Engine: 1. Select National Instruments in the Add or Remove Programs applet in the Control Panel. 2. Click the Change button. The National Instruments Software dialog box appears. 3. Select the LabVIEW Run-Time Engine entry from the list of NI products. 4. Click the Repair button. 5. Navigate to the VI Logger 1.1.1 CD or installer. * If you run a VI Logger program in a version of LabVIEW later than 7.0, the program crashes when you close LabVIEW. VI Logger 1.1.1 fixes this problem. To run VI Logger programs in a version of LabVIEW later than 7.0, mass compile the VI Logger examples and vi.lib VIs. *************************** ** VI Logger 1.1 Notes ** *************************** VI LOGGER AND CVI SUPPORT VI Logger 1.1 does not include support for NI CVI. USING VI LOGGER WITH FIELDPOINT SERIAL BANKS VI Logger support for FieldPoint Serial is the same as FieldPoint Ethernet. However, only one program at a time can access and control the serial port. Therefore, you cannot configure or monitor a Serial bank in MAX while logging VI Logger tasks from it. Doing so might result in internal errors. VI LOGGER AND NI-DAQ ERRORS If error 4523 occurs when you run a VI Logger NI-DAQ task, refer to the KnowledgeBase entry "Unusual Error Messages Loading, Executing, or Debugging Applications When Using NI-DAQ 6.x" at ni.com for a workaround solution. DATASOCKET SERVER You must launch the DataSocket server on a slow computer before running a task that publishes to DataSocket. REAL-TIME DATA AND HISTORICAL DATA VIEW The traffic light-shaped LED indicator for viewing current or historical data has moved from the upper-right side of the data view to the upper-left side. EXPORTING TASKS WITH DOUBLE-BYTE CHARACTERS You might be unable to export and import VI Logger tasks in MAX if the text in the tasks contains double-byte characters, such as Japanese characters. WEB PUBLISHING ON WINDOWS 98 If you enable web publishing on Windows ME/98, VI Logger tasks might stop and a "Fatal Internal Error in drawmgr.cpp" might display after an extended period of time. This error occurs because of a memory leak in Windows 98. SLOW EXPORTING OF LARGE AMOUNTS OF DATA If you log a large amount of data at high speed, exporting this data to a text file is slow. RESIZING THE MAX WINDOW AND THE START/STOP LOGGING BUTTON If you set the MAX window size so the Start/Stop Logging button no longer displays, the associated button text always appears as the default, Start Logging, even though the task already is logging. The Stop icon appears correct. RUNNING TWO TASKS THAT USE THE SAME NI-DAQ HARDWARE Running a second VI Logger task that uses the same NI-DAQ hardware as the task already running can cause the first task to stop with a NI-DAQ error. REGIONAL AND LANGUAGE OPTIONS (LOCATION) VI Logger applies four main regional settings: English, German, French and Japanese. If the localization settings that you use differ from these four settings, VI Logger does not apply localization settings. This affects displayed time and numeric formats in the user interface as well as logged data you export. Refer to KnowledgeBase entry "Why Do I See Other Decimal Symbols In MAX When I've Installed VI Logger 1.1?" at ni.com for more information about this issue.