LabVIEW 8.6 Datalogging and Supervisory Control Module Readme
Primary Software: LabVIEW Modules>>DSC Module
Primary Software Version: 8.6
Primary Software Fixed Version: N/A
Secondary Software: N/A
Problem: I do not have the LabVIEW 8.6 Datalogging and Supervisory Control Module installed. How can I see the readme for this product without installing it?
Solution: The readme for the LabVIEW 8.6 Datalogging and Supervisory Control Module is attached below and also installs with the module. The readme document describes any last-minute installation instructions, known issues, and changes from the previous version.
This file contains important information about the LabVIEW 8.6 Datalogging and Supervisory Control (DSC) Module, including installation and upgrade issues, compatibility issues, and changes from the DSC Module 8.5.1. Refer to the LabVIEW Upgrade Notes and to the LabVIEW Datalogging and Supervisory Control Module Release and Upgrade Notes for more information about upgrade and compatibility issues, a list of new features in LabVIEW 8.6 DSC Module, and installation instructions.
You can access the LabVIEW Upgrade Notes by selecting Help»Search the LabVIEW Help in LabVIEW and navigating to the LabVIEW Documentation Resources book on the Contents tab. You can access the LabVIEW Datalogging and Supervisory Control Module Release and Upgrade Notes by selecting Help»Search the LabVIEW Help in LabVIEW and navigating to the DSC Module»Related Documentation topic on the Contents tab.
Refer to the labview\readme directory for readme files about LabVIEW add-ons, including the DSC Module.
Supported Platforms
Installation Instructions
Installing the LabVIEW Datalogging and Supervisory Control Module Silently
Licensing
DSC Module 8.6 Features and Changes
Documentation Corrections
Known Issues
Fixed Bugs
The DSC Module supports Windows Vista/XP/2000. The DSC Module does not support Windows NT/Me/98/95/Server 2003. Refer to the LabVIEW Datalogging and Supervisory Control Module Release and Upgrade Notes for a complete list of system requirements.
Refer to the LabVIEW Datalogging and Supervisory Control Module Release and Upgrade Notes for installation instructions. The following list describes additional installation considerations.
- (Windows 2000) The computer must have the following components installed:
- Windows 2000 Service Pack 4
- Internet Explorer 6 Service Pack 1 or later
- The DSC Module requires Microsoft Data Access Components (MDAC) 2.8 SP1 or later. If you have Windows XP Service Pack 2 or Windows Vista installed, MDAC is installed by default.
- The DSC Module requires the Microsoft SQL Server 2005 Express Edition (SQL Express). This component is installed by default when you install the DSC Module. During the installation process, the DSC Module installer creates an instance of SQL Express named
CITADEL. To prevent unauthorized access to SQL Express, the installer also generates a password for the default SQL Express administrator sa. The default password is the computer ID. Complete the following steps to find the computer ID using the NI License Manager.
- Launch the NI License Manager by selecting Start»All Programs»National Instruments»NI License Manager.
- Click the Display Computer Information button in the toolbar.
The DSC Module installer enables a mixed security mode on existing SQL Servers. If the target computer does not have an SQL Server installed, the DSC Module installer installs SQL Express in the mixed security mode.
Use the following command line prompt to change the default password for the sa user:
Sqlcmd -S"localhost\CITADEL" -U"sa" -P"COMPUTER_ID" -Q"sp_password 'COMPUTER_ID', 'NEW_PASSWORD', 'sa'"
If the mixed security mode is not acceptable, change both the SQL Express and Citadel login modes. You must set the registry DWORD values HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\LoginMode and HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Citadel\5.0\IntegratedSecurity to 1.
National Instruments recommends that you change the login mode immediately after you install the DSC Module. Otherwise, you must relink all existing Citadel databases. Restart the SQL Express and Citadel services in order for changes to take effect. If you use integrated NT security, you might need to configure the server machine and all clients explicitly.
Note: The DSC Module 8.2 uses Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), not SQL Express. If you upgrade the DSC Module 8.2 to the DSC Module 8.6, any existing databases continue to use MSDE 2000 for alarm logging, but new databases you create use SQL Express. If you detach an existing database from the DSC Module and then reattach the database, the DSC Module migrates the database to SQL Express.
You might want to uninstall MSDE 2000 after installing the DSC Module 8.6. Complete the following steps to uninstall MSDE 2000.
- Stop all running processes in the NI Distributed System Manager.
- Open Measurement & Automation Explorer (MAX) and select My System»Historical Data»Citadel 5 Universe from the Configuration tree.
- On the Databases page, detach all databases from the local computer.
- Open the Windows Control Panel and uninstall MSDE 2000.
- Restart the computer.
- Open MAX and reattach all databases.
- The DSC Module uses the latest version of the NI Publish-Subscribe Protocol (NI-PSP) data transfer protocol. Although the NI-PSP data transfer protocol is backwards-compatible with earlier versions, installing the latest version of the NI-PSP data transfer protocol on earlier versions of the DSC Module provides enhanced performance.
You can control programmatically which features in the DSC Module distribution to enable or disable for installation. You therefore can install a subset of the DSC Module distribution silently. Refer to the silent_install.txt file in the Bin directory on the LabVIEW Datalogging and Supervisory Control Module CD for more information about installing the DSC Module silently and about feature selection automation.
The DSC Module extends the System Manager with additional functionality for monitoring, configuring, and acknowledging alarms, and monitoring and acknowledging events. In LabVIEW, select Tools»Distributed System Manager to launch the System Manager.
The DSC Module 8.6 relies on licensing activation. You have a temporary license for a 30-day evaluation period. If you do not activate the DSC Module license, the DSC Module operates in evaluation mode, by default, for a 30-day evaluation period. When the evaluation period expires, you cannot use the DSC features, and LabVIEW hides the DSC VIs and user interfaces. You must activate a valid DSC Module license to continue using the DSC Module.
Refer to the LabVIEW Release Notes for more information about licensing in LabVIEW.
The NI OPC Servers application installed with the DSC Module provides a temporary license for a two-hour evaluation period. You must activate a valid license to continue using the NI OPC Servers application after the evaluation period expires.
The DSC Module 8.6 provides two new examples and improves some existing examples. The two new examples are the Boiler and HVAC examples. Use the Example Finder, available by selecting Help»Find Examples, to explore and launch these examples.
Refer to the LabVIEW Help for programming concepts, step-by-step instructions, and reference information about the DSC Module 8.6. Access the LabVIEW Help by selecting Help»Search the LabVIEW Help.
- The Getting Started with the LabVIEW Datalogging and Supervisory Control Module manual did not change for LabVIEW 8.6 DSC Module. Therefore, the content might not reflect changes made in LabVIEW 8.6 DSC Module. Refer to the LabVIEW Help for the most updated information.
The following items are known issues in the DSC Module 8.6.
| ID | Known Issue |
|---|
| — | If you have Windows Vista installed, you have restricted access to the system by default even if you log in as an administrator. Windows Vista sets part of the file system to read-only, and the DSC Module might not have sufficient access rights for some files. To ensure that datalogging to the Citadel database is successful, you must specify an appropriate database location to which the DSC Module has full access. By default, the DSC Module configures appropriate access rights for the labview\data folder and stores the database in that folder. If you want to store the database in a different folder, ensure that the folder meets the following requirements:
- The database folder is readable by all members of the USERS group. The Citadel database is a shared resource and must be available to all users of the system. Alarm logging fails if the database folder is not readable to all users.
- The database folder is writable by the user who wants to log data.
- The database folder is readable and writable by the SYSTEM user. The Citadel service runs as a SYSTEM user and must have sufficient access rights to manage the database files.
- The database folder is writable by the NETWORK SERVICE user. By default, the folders under the
C:\Users directory and the top-level folders that the NETWORK SERVICE user creates are writable by that user.
If you do not store the database in the labview\data folder, National Instruments recommends that you place the database under the Windows Public user directory, located at C:\Users\Public. This folder always meets the requirements above. Do not use the following folders to store the database:
- C:\Windows—The system has highly restricted access to this folder.
- C:\Users\Username—This folder is visible only to the owning user, so the system has restricted access to this folder.
|
| — | If you have Windows XP installed, the DSC Module stores the Citadel database in the labview\data folder by default. If you want to store the database in a different folder, ensure that the folder is writable by the NETWORK SERVICE user. |
| — | If you have Windows XP Service Pack 2 installed, DSC Module networking does not function as expected. You must manually configure the Windows firewall Exceptions list and reboot the computer. Refer to the National Instruments Web site at ni.com/info and enter the info code exprc4 for more information about correcting this problem. |
| — | If you uninstall the DSC Module 8.5 and an earlier version of LabVIEW remains on the system, the earlier version of LabVIEW might try to repair itself the next time you open it. The repair process might remove any patches you installed for that version of LabVIEW. Make sure to reinstall any patches you have on the system after the repair finishes. In particular, LabVIEW might prompt you to repair the DSC Common Tools component. |
| — | The following installation and uninstallation procedures might prevent some I/O servers from functioning properly:
- Install LabVIEW 8.2, LabVIEW 8.6, and the DSC Module 8.6. Then uninstall LabVIEW 8.2.
- Install LabVIEW 8.2, the DSC Module 8.2, and LabVIEW 8.6. Then uninstall LabVIEW 8.6.
Repair the installation of the DSC Module to correct this behavior. |
| — | The DSC Module does not support building DLLs with the Application Builder. |
| — | If you programmatically create or modify a LabVIEW library, you must modify the library in the context of a project. |
| — | If you configure a shared variable for data or event logging but the Shared Variable Engine cannot establish a connection to the database, the Shared Variable Engine triggers an alarm and logs the data to the default database. |
| — | When you use a third-party OPC client to connect to the National Instruments Variable Engine OPC server, the server name might appear as National Instruments Variable Engine and National Instruments Variable Engine.1. To ensure forward compatibility, select the National Instruments Variable Engine instance when configuring an OPC connection. |
| — | If you migrate an application from the DSC Module 7.x to the DSC Module 8.6, the application might perform less well than expected in the DSC Module 8.6. Refer to the National Instruments Web site at ni.com/info and enter the info code exzd8c for more information about this problem. |
| — | Enabling the Logging property of a deployed library does not log the current values of any shared variables in that library. The Shared Variable Engine logs all subsequent value changes based on logging deadband settings. |
| — | Browsing the National Instruments Variable Engine OPC server with an OPC 2.x client using the OPC_FLAT flag returns only the first seven levels of hierarchy. |
| — | The LabVIEW Datalogging and Supervisory Control Module Release and Upgrade Notes and the Getting Started with the LabVIEW Datalogging and Supervisory Control Module manual did not change for the DSC Module 8.6. Therefore, the content in the two documents does not reflect changes made in the DSC Module 8.6. |
| — | The default shared variable logging deadband value is 100%. The correct default value is 1%. |
| 38144 | Logging to a remote database might affect system performance. |
| 38686 | The NI HyperTrend ActiveX control might plot horizontal lines for unchanging item values. Scroll or zoom the NI HyperTrend display to remove the horizontal lines. |
| 48349 | Network-published shared variables might not function properly if multiple network adapters are enabled on the same computer. If you have multiple network adapters enabled, you can force the Shared Variable Engine to use a specific adapter by adding the following lines to the C:\Windows\logos.ini file:
[LOGOS]
ServiceBindTo=xx:xx:xx:xx:xx:xx
where xx:xx:xx:xx:xx:xx represents the MAC address of the network adapter. |
| 49147 | When you save an online process to a library file, the security configuration on the process is lost. |
| 50539 | Invalid variable binding does not show a bad status alarm. |
| 51369 | You cannot configure multiple front panel binding options for multi-element controls, such as clusters and charts. |
| 51638 | Importing an EPICS record with a "." in the record name causes LabVIEW to crash. |
| 52260 | The DSC Module OPC Client I/O server does not support non-Western character sets. |
| 52268 | The NI Keyboard Filter Driver does not support Windows x64. |
| 54963 | You cannot log alarms to specific user folders in Windows Vista. |
| 93751 | Alarm properties are reset to default values when they are disabled and enabled using the relevant property nodes. |
| 93918 | Creating a user-defined alarm that starts with "alarm" returns an invalid argument error (-1967362033). |
| 116848 | In the LabVIEW Help, the VI paths in the following topics contain 8.5, which should read 8.6.
- Using On Input Change I/O Servers
- Using Periodic I/O Servers
|
The following items are the IDs and titles of a subset of issues fixed in the LabVIEW 8.6 DSC Module. If you have a Bug ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the DSC Module.
| Bug ID | Fixed Issue |
|---|
| 41906 | Read traces VI needs a database URL when in compiled EXE. |
| 55177 | Add/remove traces will crash MAX if trace's process name is "IO". |
| 56805 | Front Panel Mass Binding Tool does not import tags with ' in the URL. |
| 58007 | Multi-segment pipe behaves oddly when selecting "Add vertical pipe segment". |
| 58624 | Custom IO Server with branching stop condition wires will not build properly. |
| 64898 | Cannot select multiple variables to edit in MVE. |
| 94028 | Network-binding to alarm's Enable property cannot control the Set/Clear status of the alarm. |
| 98991 | NI OPC Servers may crash when switching property pages. |
| 99142 | NI OPC Servers has error pop-ups when creating new project. |
| 100487 | Alarms do not maintain alarm state and default when there are no active subscribers. |
| 104255 | Calling Historical Data View VI in built EXE crashes EXE when closing MAX. |
| 107244 | Historical VIs do not return copies of the input URL. |
Copyright
© 2008 National Instruments Corporation. All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
In regards to components that use Citadel 5, the following copyright applies. Copyright © 1994 Hewlett-Packard Company. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Trademarks
National Instruments, NI, ni.com, LabVIEW, and Citadel are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information about National Instruments trademarks.
Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering the National Instruments products, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or ni.com/patents.
Related Links:
Attachments: 
Report Date: 06/03/2008
Last Updated: 08/01/2008
Document ID: 4M2H4HLC
