NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the LabVIEW 2009 DSC Module known issues that were discovered before and since the release of LabVIEW 2009 DSC Module. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The LabVIEW 2009 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. However, NI has become aware of a number of issues of potential significance regarding Microsoft Windows 7. To learn how Windows 7 affects your use of NI products, visit ni.com/info and enter the Info Code windows7.
Each Issue appears as a row in the table and includes these fields:
Issue ID—Contains the number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
Legacy ID (optional)—Contains the legacy CAR ID, if an issue has a legacy ID from NI's legacy/deprecated bug reporting database. This ID appears on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
Issue Title (in italics)—Describes the issue in one sentence or less.
Problem Description—Describes the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
Workaround—Provides possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
Reported Version—Contains the earliest version of the NI SoftMotion Module the issue was reported in. If you discover the issue appears in an earlier version of the NI SoftMotion Module than is reported in this field, you can report that to NI (contact information below) to have the field updated.
Resolved Version—Contains the version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
Date Added—Contains the date the issue was added to the document (not the reported date).
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.
The known issues in this document are organized by the category of issue. Please refer to Developer Zone Article "LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in LabVIEW 2010 and 2010 SP1 DSC Module Known Issues sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Building and Distributing LabVIEW Applications | ||||||
| 176613 Return | Library deployment fails if it includes the startup VI of built application or running VI If users specify a VI belonging to a library as the startup VI, then the library will fail to be deployed by the runtime deployment feature or DSC engine control VIs. Workaround: Make startup VIs outside the library which is to be deployed.
| |||||
| 189456 Return | Shared Variable Control Needs DSC to Browse for Variable When using the Shared Variable Control in an executable, the Browse... option is grayed out. The option is not grayed out when run in a LabVIEW development environment. If the executable is built with Enable Enhanced DSC Run-Time Support, it works fine. However since the control is a LabVIEW Core control, it is available without DSC, so it cannot be used as seen in the development environment in an executable without DSC. Workaround: Must install DSC and Enable Enhanced DSC Run-Time Support when building the executable.
| |||||
| Controls and Indicators | ||||||
| 152163 Return | Align shortcut menu option doesn't appear if the control is selected If a Navigation Control is selected with the positioning tool the align shortcut menu option doesn't appear. Workaround: Don't select the Navigation Controls with the positioning tool before right clicking them to pop up the shortcut menu.
| |||||
| Functions, VIs, and Express VIs | ||||||
| 172946 Return | Comparison Express VI does not work in a Custom VI - Periodic I/O server If the Comparison Express VI is used in a Custom VI - periodic I/O server, the indicators and controls you specify will not be deployed to the shared variable engine. The server is deployed, but no shared variables are visible. Workaround: Instead of the express VI use the primitive comparisons.
| |||||
| 49147 3XPC7K4J Return | Saving a process to a library does not save the Access or Security information for the process Saving an online process to a project library (*.lvlib) using the Save to Library (Process) VI does not save the Access or Security configuration for the process. Workaround: N/A
| |||||
| Installation and Activation | ||||||
| 182372 Return | When upgrading from LabVIEW DSC 8.6.x to 2009 some EPICS Server dependency libraries may not be installed. When upgrading from LabVIEW DSC 8.6.x to LabVIEW DSC and RT 2009 the EPICS server may not function due to missing dependency libraries. Installing LabVIEW DSC and RT 2009 without upgrading does not cause any problems. Workaround: N/A
| |||||
| 195367 Return | Warning for "MSXML6" shows when installing SQL server 2005 on localized XP SP3. When installing LabVIEW DSC 2009 on a localized version of Windows XP a warning dialog appears stating "msxml6r.dll" cannot be updated." Workaround: Ignore this dialog and continue the install process.
| |||||
| LabVIEW Project | ||||||
| 126082 Return | Shared Variables in nested virtual folders cannot be edited with the Multiple Variable Editor When there are variables inside nested virtual folders within a Library, the multiple variable editor does not work. If you select several variables in a virtual folder and right-click and select Multiple variable editor, the editor opens but you cannot change anything. Workaround: Convert folders to libraries or move variables under a single folder.
| |||||
| Miscellaneous | ||||||
| 158126 Return | Cannot select database path in Library DSC Setting A user is unable to set the Database Path in the Libary Properties >> DSC Settings: Database section because the browse dialog does not have a "Current Folder" selection. Workaround: Select the "Database Name" instead and it will autopopulate the database path.
| |||||
| 178750 Return | Modbus I/O Server data items inconsistent with help file When creating a Modbus I/O Server, you will see that I/O Item 400001.1-465535.16 has an "Item access type" of Read only, whereas the help file Using Modbus I/O Servers lists it as being both read and write. Workaround: Instead of writing the bits (eg. 400001.1) write the indiviual registers (eg. 400001) as a bit array.
| |||||
| 178809 Return | The hypertrend sometimes draws backwards horizontal lines while in live mode. This issue occurs when the hypertrend is running in live mode. When this issue is occurring, the hypertrend will shoot horizontal lines backwards from the right edge of the trend to the left edge. The lines last for a few updates and then disappear. These lines are simply a drawing artificact of the trend and do not correspond to any actual data. If you take the trend out of live mode and try to examine the horizontal lines, they will disappear. Workaround: Force Hypertrend to redraw by zooming in or out. Read property "IsPlotting" and write it to property "IsPlotting" in the same loop.
| |||||
| 170863 Return | Creating new configurations of custom I/O servers in Distribyted System Manager causes DSM to crash Workaround: N/A
| |||||
| 199905 Return | Alias address is incorrect when adding a range of Modbus digital arrays When adding a range of Modbus DIO registers such as A000001L1-A065535L1, the alias address is incorrect. It appears as "A00000001." This value should appear with the last two digits after the L for the array size. Workaround: Manually edit the bound URL to use the array format: AL
| |||||
| 194885 Return | Error 1967353908 With Modbus Master IO Server When Reading Valid Registers A Modbus Master IO Server will return error 1967353908 with certain modbus slave devices indicating that the master is reading from addresses that do not exist on the slave. This problem is actually caused because the IO Server is building a querry for a range of values behind the scenes, some of which do not exist on the slave. The slave device then returns an exception that causes an error in the server. Workaround: To resolve this issue, reduce the number of Holding Registers in the Advanced Settings of the IO Server to 1.
| |||||
| 222562 Return | Exporting a Trace View to a text file from MAX 4.6.2 gives inaccurate time information When exporting a Trace View from MAX inaccurate time information can be generated. This will occur when using natural or linear interpolation and 0.1s interval for the trace. In this situation data can be incorrectly show as logged back in time. Workaround: Use .01 seconds and discard unused data.
| |||||
| 195296 Return | HyperTrend Max and Min Cusors do not return correct Max or Min values When using the Max and Min curors on a trend in HyperTrend the Max and Min values returned are not the actual max and min values Workaround: N/A
| |||||
| Performance | ||||||
| 229251 Return | Citadel timestamp problems on Intel E7500 processors Computers with Intel E7500 processor can display periodic gaps in Citadel data. The Citadel database stops updating for a short time before updating again. This cycle repeats indefinitely. This will appear in Hypertrend as periodic flat lines between datapoints. Workaround: N/A
| |||||
| Shared Variables | ||||||
| 132994 Return | Multiple Variable Editor cannot set alarming levels for anything other than double-typed variables When editing a variable that has a numeric data type using the Multiple Variable Editor that is not a double you cannot set the alarming levels. This includes variables of single, as well as signed and unsigned Int 8, 16, 32, and 64. Workaround: Use the shared variable properties window to set the alarm levels. Alarm levels can also be set programmatically.
| |||||
| 158511 Return | Value change event registration on remotely deployed shared variables produces runtime error When value change events are registered for remotely deployed shared variables and the network cable is disconnected a run time error is produced. Workaround: Deploy shared variables locally that are bound to the network variables and register value change events for the locally deployed variables.
| |||||
| 173604 Return | Shared Variable Engine crash when writing to Omron plc via NI OPC and LabVIEW when using multi-core only Shared variable engine crash when writing to the tags on an Omron PLC using NI OPC and LabVIEW DSC. This also only happens when the machine is setup as multi-core. Workaround: Disable multicore support in the BIOS of the PC or disable the OPC diagnostics.
| |||||
| 177723 Return | All variables are listed directly under "*.lvproj" when you config the "Network Published: Project Path". When using the Multiple Variable Editor to config the PSP binding for a shared varaible, in the "Network Published: Project Path" column, click the "Browse", you will find all variables are listed directly under the *.lvproj. The information of which target and which process in the hierarchy is missing. Workaround: N/A
| |||||
| 181952 Return | EPICS Server can't publish IOVs If you try to publish IOVs that are selected from the project tree, a pop-up window shows to say "Following items can not be added because they are either single-process or time-triggered variables". Workaround: You can deploy the IOVs first, then publish them as network items.
| |||||
| 50539 454GITH7 Return | Variable bad status alarm does not fire for invalid binding When a variable with an invalid binding is deployed a bad status alarm will not be fired for that variable. Workaround: N/A
| |||||
| 93751 Return | Alarm properties are set to default values when it is disabled and enabled again via property nodes If a user configures an alarm to a value other than the default and then disables that alarm with a property node (Alarming.HI_HI.Enabled for example), reenabling that alarm will reset that value to default. Workaround: If alarming needs to be changed in one program read the alarm properties before setting the enabled property to false and write those values back when setting the property back to true.
| |||||
| 98000 Return | Disabling alarms using network binding and the property node behave differently When disabling an alarm using the property node the alarm is cleared and acknowledged if auto acknowledgement is set. If an alarm is disabled using network binding to the enabled property then the alarm is not cleared. Workaround: N/A
| |||||
| 93918 Return | User defined alarm that starts with "alarm" does not work When creating a user-defined alarm that has a name that starts with "alarm" gives a Invalid argument error (-1967362033) when run even if all parameters are correct. Changing the name to anything else (ie TestAlarm instead of AlarmTest) works. Workaround: Do not use "alarm" as the beginning text in an user defined alarm.
| |||||
| 212581 Return | OPC Bound Variables URL only include Channel when the owning lvlib is included in an EXE When a lvlib containing variables bound to an OPC I/O server is included in the build for an EXE the PSP binding URL becomes incorrect. The resulting URL after the build does not include the full path to the OPC data item. Instead the URL only comprises on the machine name, OPC Prog ID, and the OPC channel. Workaround: When configuring the alias option for the Shared Variable use a PSP URL instead of a Project Path and change your machine name to localhost.
| |||||
| 126082 Return | Shared Variables in nested virtual folders cannot be edited with the Multiple Variable Editor When there are variables inside nested virtual folders within a Library, the multiple variable editor does not work. If you select several variables in a virtual folder and right-click and select Multiple variable editor, the editor opens but you cannot change anything. Workaround: Convert folders to libraries or move variables under a single folder.
| |||||
| 189456 Return | Shared Variable Control Needs DSC to Browse for Variable When using the Shared Variable Control in an executable, the Browse... option is grayed out. The option is not grayed out when run in a LabVIEW development environment. If the executable is built with Enable Enhanced DSC Run-Time Support, it works fine. However since the control is a LabVIEW Core control, it is available without DSC, so it cannot be used as seen in the development environment in an executable without DSC. Workaround: Must install DSC and Enable Enhanced DSC Run-Time Support when building the executable.
| |||||
| 208075 Return | DSC Save State Periodically Option Does not Function Enabling the Save State Periodically option in the DSC Settings:Process Category of the Library Properties does not save the state of the process or Shared Variables within the process. Workaround: N/A
| |||||
| 280588 Return | Values of Shared variables with alarming enabled do not appear in some OPC client browsers If "Enable Alarming" is enabled on a network published Shared Variable, the Shared Variable does not appear as a selectable tag in the browse view of an OPC client. This is because the client thinks the Shared Variable is a container with no value. Workaround: In OPC Quick Client you can select the option to "Browse flat address space on selected branch." Alternatively you can manually enter the path of the Shared Variable.
| |||||
The following items are known issues in LabVIEW 2010 and 2010 SP1 DSC Module Known Issues sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 132994 Return | Multiple Variable Editor cannot set alarming levels for anything other than double-typed variables When editing a variable that has a numeric data type using the Multiple Variable Editor that is not a double you cannot set the alarming levels. This includes variables of single, as well as signed and unsigned Int 8, 16, 32, and 64. Workaround: Use the shared variable properties window to set the alarm levels. Alarm levels can also be set programmatically.
| |||||
| 152163 Return | Align shortcut menu option doesn't appear if the control is selected If a Navigation Control is selected with the positioning tool the align shortcut menu option doesn't appear. Workaround: Don't select the Navigation Controls with the positioning tool before right clicking them to pop up the shortcut menu.
| |||||
| 158126 Return | Cannot select database path in Library DSC Setting A user is unable to set the Database Path in the Libary Properties >> DSC Settings: Database section because the browse dialog does not have a "Current Folder" selection. Workaround: Select the "Database Name" instead and it will autopopulate the database path.
| |||||
| 158511 Return | Value change event registration on remotely deployed shared variables produces runtime error When value change events are registered for remotely deployed shared variables and the network cable is disconnected a run time error is produced. Workaround: Deploy shared variables locally that are bound to the network variables and register value change events for the locally deployed variables.
| |||||
| 172946 Return | Comparison Express VI does not work in a Custom VI - Periodic I/O server If the Comparison Express VI is used in a Custom VI - periodic I/O server, the indicators and controls you specify will not be deployed to the shared variable engine. The server is deployed, but no shared variables are visible. Workaround: Instead of the express VI use the primitive comparisons.
| |||||
| 173604 Return | Shared Variable Engine crash when writing to Omron plc via NI OPC and LabVIEW when using multi-core only Shared variable engine crash when writing to the tags on an Omron PLC using NI OPC and LabVIEW DSC. This also only happens when the machine is setup as multi-core. Workaround: Disable multicore support in the BIOS of the PC or disable the OPC diagnostics.
| |||||
| 176613 Return | Library deployment fails if it includes the startup VI of built application or running VI If users specify a VI belonging to a library as the startup VI, then the library will fail to be deployed by the runtime deployment feature or DSC engine control VIs. Workaround: Make startup VIs outside the library which is to be deployed.
| |||||
| 177723 Return | All variables are listed directly under "*.lvproj" when you config the "Network Published: Project Path". When using the Multiple Variable Editor to config the PSP binding for a shared varaible, in the "Network Published: Project Path" column, click the "Browse", you will find all variables are listed directly under the *.lvproj. The information of which target and which process in the hierarchy is missing. Workaround: N/A
| |||||
| 178750 Return | Modbus I/O Server data items inconsistent with help file When creating a Modbus I/O Server, you will see that I/O Item 400001.1-465535.16 has an "Item access type" of Read only, whereas the help file Using Modbus I/O Servers lists it as being both read and write. Workaround: Instead of writing the bits (eg. 400001.1) write the indiviual registers (eg. 400001) as a bit array.
| |||||
| 178809 Return | The hypertrend sometimes draws backwards horizontal lines while in live mode. This issue occurs when the hypertrend is running in live mode. When this issue is occurring, the hypertrend will shoot horizontal lines backwards from the right edge of the trend to the left edge. The lines last for a few updates and then disappear. These lines are simply a drawing artificact of the trend and do not correspond to any actual data. If you take the trend out of live mode and try to examine the horizontal lines, they will disappear. Workaround: Force Hypertrend to redraw by zooming in or out. Read property "IsPlotting" and write it to property "IsPlotting" in the same loop.
| |||||
| 181952 Return | EPICS Server can't publish IOVs If you try to publish IOVs that are selected from the project tree, a pop-up window shows to say "Following items can not be added because they are either single-process or time-triggered variables". Workaround: You can deploy the IOVs first, then publish them as network items.
| |||||
| 182372 Return | When upgrading from LabVIEW DSC 8.6.x to 2009 some EPICS Server dependency libraries may not be installed. When upgrading from LabVIEW DSC 8.6.x to LabVIEW DSC and RT 2009 the EPICS server may not function due to missing dependency libraries. Installing LabVIEW DSC and RT 2009 without upgrading does not cause any problems. Workaround: N/A
| |||||
| 50539 454GITH7 Return | Variable bad status alarm does not fire for invalid binding When a variable with an invalid binding is deployed a bad status alarm will not be fired for that variable. Workaround: N/A
| |||||
| 93751 Return | Alarm properties are set to default values when it is disabled and enabled again via property nodes If a user configures an alarm to a value other than the default and then disables that alarm with a property node (Alarming.HI_HI.Enabled for example), reenabling that alarm will reset that value to default. Workaround: If alarming needs to be changed in one program read the alarm properties before setting the enabled property to false and write those values back when setting the property back to true.
| |||||
| 98000 Return | Disabling alarms using network binding and the property node behave differently When disabling an alarm using the property node the alarm is cleared and acknowledged if auto acknowledgement is set. If an alarm is disabled using network binding to the enabled property then the alarm is not cleared. Workaround: N/A
| |||||
| 170863 Return | Creating new configurations of custom I/O servers in Distribyted System Manager causes DSM to crash Workaround: N/A
| |||||
| 195367 Return | Warning for "MSXML6" shows when installing SQL server 2005 on localized XP SP3. When installing LabVIEW DSC 2009 on a localized version of Windows XP a warning dialog appears stating "msxml6r.dll" cannot be updated." Workaround: Ignore this dialog and continue the install process.
| |||||
| 199905 Return | Alias address is incorrect when adding a range of Modbus digital arrays When adding a range of Modbus DIO registers such as A000001L1-A065535L1, the alias address is incorrect. It appears as "A00000001." This value should appear with the last two digits after the L for the array size. Workaround: Manually edit the bound URL to use the array format: AL
| |||||
| 49147 3XPC7K4J Return | Saving a process to a library does not save the Access or Security information for the process Saving an online process to a project library (*.lvlib) using the Save to Library (Process) VI does not save the Access or Security configuration for the process. Workaround: N/A
| |||||
| 93918 Return | User defined alarm that starts with "alarm" does not work When creating a user-defined alarm that has a name that starts with "alarm" gives a Invalid argument error (-1967362033) when run even if all parameters are correct. Changing the name to anything else (ie TestAlarm instead of AlarmTest) works. Workaround: Do not use "alarm" as the beginning text in an user defined alarm.
| |||||
| 194885 Return | Error 1967353908 With Modbus Master IO Server When Reading Valid Registers A Modbus Master IO Server will return error 1967353908 with certain modbus slave devices indicating that the master is reading from addresses that do not exist on the slave. This problem is actually caused because the IO Server is building a querry for a range of values behind the scenes, some of which do not exist on the slave. The slave device then returns an exception that causes an error in the server. Workaround: To resolve this issue, reduce the number of Holding Registers in the Advanced Settings of the IO Server to 1.
| |||||
| 229251 Return | Citadel timestamp problems on Intel E7500 processors Computers with Intel E7500 processor can display periodic gaps in Citadel data. The Citadel database stops updating for a short time before updating again. This cycle repeats indefinitely. This will appear in Hypertrend as periodic flat lines between datapoints. Workaround: N/A
| |||||
| 212581 Return | OPC Bound Variables URL only include Channel when the owning lvlib is included in an EXE When a lvlib containing variables bound to an OPC I/O server is included in the build for an EXE the PSP binding URL becomes incorrect. The resulting URL after the build does not include the full path to the OPC data item. Instead the URL only comprises on the machine name, OPC Prog ID, and the OPC channel. Workaround: When configuring the alias option for the Shared Variable use a PSP URL instead of a Project Path and change your machine name to localhost.
| |||||
| 222562 Return | Exporting a Trace View to a text file from MAX 4.6.2 gives inaccurate time information When exporting a Trace View from MAX inaccurate time information can be generated. This will occur when using natural or linear interpolation and 0.1s interval for the trace. In this situation data can be incorrectly show as logged back in time. Workaround: Use .01 seconds and discard unused data.
| |||||
| 126082 Return | Shared Variables in nested virtual folders cannot be edited with the Multiple Variable Editor When there are variables inside nested virtual folders within a Library, the multiple variable editor does not work. If you select several variables in a virtual folder and right-click and select Multiple variable editor, the editor opens but you cannot change anything. Workaround: Convert folders to libraries or move variables under a single folder.
| |||||
| 189456 Return | Shared Variable Control Needs DSC to Browse for Variable When using the Shared Variable Control in an executable, the Browse... option is grayed out. The option is not grayed out when run in a LabVIEW development environment. If the executable is built with Enable Enhanced DSC Run-Time Support, it works fine. However since the control is a LabVIEW Core control, it is available without DSC, so it cannot be used as seen in the development environment in an executable without DSC. Workaround: Must install DSC and Enable Enhanced DSC Run-Time Support when building the executable.
| |||||
| 195296 Return | HyperTrend Max and Min Cusors do not return correct Max or Min values When using the Max and Min curors on a trend in HyperTrend the Max and Min values returned are not the actual max and min values Workaround: N/A
| |||||
| 208075 Return | DSC Save State Periodically Option Does not Function Enabling the Save State Periodically option in the DSC Settings:Process Category of the Library Properties does not save the state of the process or Shared Variables within the process. Workaround: N/A
| |||||
| 280588 Return | Values of Shared variables with alarming enabled do not appear in some OPC client browsers If "Enable Alarming" is enabled on a network published Shared Variable, the Shared Variable does not appear as a selectable tag in the browse view of an OPC client. This is because the client thinks the Shared Variable is a container with no value. Workaround: In OPC Quick Client you can select the option to "Browse flat address space on selected branch." Alternatively you can manually enter the path of the Shared Variable.
|
Document last updated on 07/06/2012