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 2010 DSC Module known issues that were discovered before and since the release of LabVIEW 2010 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 2010 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The Known Issues Document is divided into two separate tables. The following section displays the issues by issue category.
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 have published a section of the known issues table sorted by the 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 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Building and Distributing LabVIEW Applications | ||||||
| 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.
| |||||
| 247513 Return | Error 1003 Building EXE With DSC Historical VIs When Top Level VI is Open When building a VI that contains VIs from NI_DSC.lvlib, and the top level VI is open you get error 1003 "The VI is broken. Open the VI in LabVIEW and fix the errors." Workaround: Close the top level VI, and build again.
| |||||
| Citadel | ||||||
| 293727 Return | Values over 999 in Citadel export incorrectly to text/CSV files Because tag values of 1,000 or greater in an comma separated value (CSV) file exported trace include the comma, the values leading and following the comma will be in separate rows. This is due to the comma in the tag value being interpreted as a row separator. Workaround: Export to tab delimited instead of CSV
| |||||
| 287009 Return | Warning 0 on Read Trace VI upon first run of code Using the Read Trace VI, Read Traces VI, or Get Trace Info VI results in a Warning 0 upon first run. Subsequent runs do not have the problem. Workaround: Replace Read Traces VI with the Historical Trend Express VI or clear this particular warning.
| |||||
| 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.
| |||||
| 255585 Return | Mutiple instances of the same type of navigation control prevents proper alignment of the controls. If you have multiple VIs that have more than one instance of any type of Navigation Control, you cannot align these navigation controls to one another in the "Manage Navigation Controls" dialog window. Workaround: Use only one type of Navigation Control per VI.
| |||||
| Distributed System Manager | ||||||
| 252428 Return | U32 bit field listed as Unnamed Type 1 in Distributed System Manager When you deploy a Shared Variable with the U32 bit field data type it is listed in Distributed System Manager as Unnamed Type 1. Workaround: N/A
| |||||
| 252430 Return | Cannot set a SV as u32 bit field type from SV dialog in Distributed System Manager If you set a SV to use the U32 Bit Field datatype in the DSM Shared Variable dialog window, the type will be changed to a U32 once you close the dialog window. Workaround: N/A
| |||||
| Functions, VIs, and Express VIs | ||||||
| 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
| |||||
| 252383 Return | Configure Alarming - Bad Status VI always produces an error if "enable?" is set to false. When using the Bad Status instance of the Configure Alarming VI the VI will always through an error if the "enabled?" Boolean in the "bad status alarm settings" cluster is set to false. Workaround: Do not execute this VI if you aren't enabling this type of alarm.
| |||||
| 252420 Return | Configure Alarming - Bit Array VI always produces an error if enable? is set to false When using the Bit Array instance of the Configure Alarming VI the VI will always through an error if the "enabled?" Boolean in the "bad status alarm settings" cluster is set to false. Workaround: Do not execute this VI if you aren't enabling this type of alarm.
| |||||
| 252521 Return | Configure Alarming - Boolean VI always produces an error if enable? is set to false When using the Boolean instance of the Configure Alarming VI the VI will always through an error if the "enabled?" Boolean in the "bad status alarm settings" cluster is set to false. Workaround: Do not execute this VI if you aren't enabling this type of alarm.
| |||||
| 257303 Return | Open Trace VI's terminal "trace name" returns error -1967362033 if unwired. Detailed help for DSC Module » Database Writing VIs » Open Trace VI says, "trace name is the name of the Citadel trace. If a trace with this name does not exist in the target database, the DSC Module creates a new trace. Otherwise, Citadel appends data to the end of the existing trace." The VI returns an error if this terminal is not wired. Workaround: Always specify a trace name.
| |||||
| 287009 Return | Warning 0 on Read Trace VI upon first run of code Using the Read Trace VI, Read Traces VI, or Get Trace Info VI results in a Warning 0 upon first run. Subsequent runs do not have the problem. Workaround: Replace Read Traces VI with the Historical Trend Express VI or clear this particular warning.
| |||||
| 306205 Return | Error 1003 when building an executable with OpenTrace.vi within a LabVIEW Class If you are building a stand alone LabVIEW executable that has the polymorphic OpenTrace.vi within a LabVIEW class error 1003 will occur during the build. Workaround: Call the individual instance of the OpenTrace VI (Open Trace (Numeric), Open Trace (Logical), etc) instead of the polymorphic VI. These VIs can be found at C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\lvdsc\historical.
| |||||
| I/O Servers | ||||||
| 280037 Return | The first read of an EPICS Client PV returns 'General communication failure' The first read of a PV triggers the creation of the PV item through LogosXT. Due to this, first read will fail. There are similar issues with the first read of EPICS Server. Workaround: Use Programmatic Shared Variable API to open the Shared Variable bound to the EPICS Client PV, and wait a sufficient amount of time (>0.1 seconds). You can then read the value successfully through Programmatic Shared Variable API.
| |||||
| 297362 Return | EPICS I/O Server client returns incorrect STAT values in an alarm state When an EPICS I/O Server client is created in DSC, it populates with a STAT field, which is the alarm state as defined by EPICS. When running a client, however, the STAT field goes through the states of LOLO, LOW, NO_ALARM, COMM, and COS. Workaround: Bind the client VI to the EPICS server STAT value, if possible. Otherwise, convert the STAT value to its correct string in the user's code when reading STAT from the client.
| |||||
| Installation and Activation | ||||||
| 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.
| |||||
| 252427 Return | Cannot set a SV as u32 bit field type from SV dialog in LabVIEW Project If you set a SV to use the U32 Bit Field datatype in the LabVIEW project Shared Variable dialog window, the type will be changed to a U32 once you close the dialog window. Workaround: N/A
| |||||
| Miscellaneous | ||||||
| 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.
| |||||
| 248412 Return | OPC Client IO Server cannot browse FactoryTalk Gateway OPC Server An OPC I/O server will not show any OPC tags within containers on a FactoryTalk Gateway OPC Server. Workaround: Don't browse the OPC Server. Instead manually input the URL of a tag to bind to the Shared Variable.
| |||||
| 250605 Return | Ending NI OPC Server process from task manager will cause connected processes to hang. If you end the NI OPC Servers process (ServerMain.exe) from task manager any process containing an OPC I/O Server client connected to the OPC server will hang. This hang is characterized by the user's inability to stop or remove the process from DSM. Workaround: N/A
| |||||
| 280037 Return | The first read of an EPICS Client PV returns 'General communication failure' The first read of a PV triggers the creation of the PV item through LogosXT. Due to this, first read will fail. There are similar issues with the first read of EPICS Server. Workaround: Use Programmatic Shared Variable API to open the Shared Variable bound to the EPICS Client PV, and wait a sufficient amount of time (>0.1 seconds). You can then read the value successfully through Programmatic Shared Variable API.
| |||||
| 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 | ||||||
| 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
| |||||
| 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.
| |||||
| 250605 Return | Ending NI OPC Server process from task manager will cause connected processes to hang. If you end the NI OPC Servers process (ServerMain.exe) from task manager any process containing an OPC I/O Server client connected to the OPC server will hang. This hang is characterized by the user's inability to stop or remove the process from DSM. Workaround: N/A
| |||||
| 252427 Return | Cannot set a SV as u32 bit field type from SV dialog in LabVIEW Project If you set a SV to use the U32 Bit Field datatype in the LabVIEW project Shared Variable dialog window, the type will be changed to a U32 once you close the dialog window. Workaround: N/A
| |||||
| 252428 Return | U32 bit field listed as Unnamed Type 1 in Distributed System Manager When you deploy a Shared Variable with the U32 bit field data type it is listed in Distributed System Manager as Unnamed Type 1. Workaround: N/A
| |||||
| 252430 Return | Cannot set a SV as u32 bit field type from SV dialog in Distributed System Manager If you set a SV to use the U32 Bit Field datatype in the DSM Shared Variable dialog window, the type will be changed to a U32 once you close the dialog window. Workaround: N/A
| |||||
| 277919 Return | Periodic I/O Server can Fail with Error -1 When deploying a periodic I/O server on some systems, the I/O server fails with error -1, "Unable to Load Configuration." All Shared Variables bound to data items within the Periodic I/O server have the value of "Server Failure." Workaround: Add a string reg key "mndVer" under "HKEY_LOCAL_MACHINE\SOFTWARE\NATIONAL INSTRUMENTS\Tagger", and set its value to "10.0
| |||||
| 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 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 247513 Return | Error 1003 Building EXE With DSC Historical VIs When Top Level VI is Open When building a VI that contains VIs from NI_DSC.lvlib, and the top level VI is open you get error 1003 "The VI is broken. Open the VI in LabVIEW and fix the errors." Workaround: Close the top level VI, and build again.
| |||||
| 248412 Return | OPC Client IO Server cannot browse FactoryTalk Gateway OPC Server An OPC I/O server will not show any OPC tags within containers on a FactoryTalk Gateway OPC Server. Workaround: Don't browse the OPC Server. Instead manually input the URL of a tag to bind to the Shared Variable.
| |||||
| 250605 Return | Ending NI OPC Server process from task manager will cause connected processes to hang. If you end the NI OPC Servers process (ServerMain.exe) from task manager any process containing an OPC I/O Server client connected to the OPC server will hang. This hang is characterized by the user's inability to stop or remove the process from DSM. Workaround: N/A
| |||||
| 252383 Return | Configure Alarming - Bad Status VI always produces an error if "enable?" is set to false. When using the Bad Status instance of the Configure Alarming VI the VI will always through an error if the "enabled?" Boolean in the "bad status alarm settings" cluster is set to false. Workaround: Do not execute this VI if you aren't enabling this type of alarm.
| |||||
| 252420 Return | Configure Alarming - Bit Array VI always produces an error if enable? is set to false When using the Bit Array instance of the Configure Alarming VI the VI will always through an error if the "enabled?" Boolean in the "bad status alarm settings" cluster is set to false. Workaround: Do not execute this VI if you aren't enabling this type of alarm.
| |||||
| 252427 Return | Cannot set a SV as u32 bit field type from SV dialog in LabVIEW Project If you set a SV to use the U32 Bit Field datatype in the LabVIEW project Shared Variable dialog window, the type will be changed to a U32 once you close the dialog window. Workaround: N/A
| |||||
| 252428 Return | U32 bit field listed as Unnamed Type 1 in Distributed System Manager When you deploy a Shared Variable with the U32 bit field data type it is listed in Distributed System Manager as Unnamed Type 1. Workaround: N/A
| |||||
| 252430 Return | Cannot set a SV as u32 bit field type from SV dialog in Distributed System Manager If you set a SV to use the U32 Bit Field datatype in the DSM Shared Variable dialog window, the type will be changed to a U32 once you close the dialog window. Workaround: N/A
| |||||
| 252521 Return | Configure Alarming - Boolean VI always produces an error if enable? is set to false When using the Boolean instance of the Configure Alarming VI the VI will always through an error if the "enabled?" Boolean in the "bad status alarm settings" cluster is set to false. Workaround: Do not execute this VI if you aren't enabling this type of alarm.
| |||||
| 255585 Return | Mutiple instances of the same type of navigation control prevents proper alignment of the controls. If you have multiple VIs that have more than one instance of any type of Navigation Control, you cannot align these navigation controls to one another in the "Manage Navigation Controls" dialog window. Workaround: Use only one type of Navigation Control per VI.
| |||||
| 257303 Return | Open Trace VI's terminal "trace name" returns error -1967362033 if unwired. Detailed help for DSC Module » Database Writing VIs » Open Trace VI says, "trace name is the name of the Citadel trace. If a trace with this name does not exist in the target database, the DSC Module creates a new trace. Otherwise, Citadel appends data to the end of the existing trace." The VI returns an error if this terminal is not wired. Workaround: Always specify a trace name.
| |||||
| 277919 Return | Periodic I/O Server can Fail with Error -1 When deploying a periodic I/O server on some systems, the I/O server fails with error -1, "Unable to Load Configuration." All Shared Variables bound to data items within the Periodic I/O server have the value of "Server Failure." Workaround: Add a string reg key "mndVer" under "HKEY_LOCAL_MACHINE\SOFTWARE\NATIONAL INSTRUMENTS\Tagger", and set its value to "10.0
| |||||
| 280037 Return | The first read of an EPICS Client PV returns 'General communication failure' The first read of a PV triggers the creation of the PV item through LogosXT. Due to this, first read will fail. There are similar issues with the first read of EPICS Server. Workaround: Use Programmatic Shared Variable API to open the Shared Variable bound to the EPICS Client PV, and wait a sufficient amount of time (>0.1 seconds). You can then read the value successfully through Programmatic Shared Variable API.
| |||||
| 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.
| |||||
| 297362 Return | EPICS I/O Server client returns incorrect STAT values in an alarm state When an EPICS I/O Server client is created in DSC, it populates with a STAT field, which is the alarm state as defined by EPICS. When running a client, however, the STAT field goes through the states of LOLO, LOW, NO_ALARM, COMM, and COS. Workaround: Bind the client VI to the EPICS server STAT value, if possible. Otherwise, convert the STAT value to its correct string in the user's code when reading STAT from the client.
| |||||
| 293727 Return | Values over 999 in Citadel export incorrectly to text/CSV files Because tag values of 1,000 or greater in an comma separated value (CSV) file exported trace include the comma, the values leading and following the comma will be in separate rows. This is due to the comma in the tag value being interpreted as a row separator. Workaround: Export to tab delimited instead of CSV
| |||||
| 287009 Return | Warning 0 on Read Trace VI upon first run of code Using the Read Trace VI, Read Traces VI, or Get Trace Info VI results in a Warning 0 upon first run. Subsequent runs do not have the problem. Workaround: Replace Read Traces VI with the Historical Trend Express VI or clear this particular warning.
| |||||
| 306205 Return | Error 1003 when building an executable with OpenTrace.vi within a LabVIEW Class If you are building a stand alone LabVIEW executable that has the polymorphic OpenTrace.vi within a LabVIEW class error 1003 will occur during the build. Workaround: Call the individual instance of the OpenTrace VI (Open Trace (Numeric), Open Trace (Logical), etc) instead of the polymorphic VI. These VIs can be found at C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\lvdsc\historical.
|
Document last updated on 7/6/2012