Archived: LabVIEW 2012 and 2012 SP1 DSC Module Known Issues

Publish Date: Jul 21, 2018 | 0 Ratings | 0.00 out of 5 | Print

Overview

This document has been archived and is no longer updated by National Instruments.

This document contains the LabVIEW 2012 DSC Module known issues that were discovered before and since the release of LabVIEW 2012 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 2012 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Table of Contents

Document Organization

The Known Issues Document is divided into two separate tables. The following section displays the issues by issue category.

Known Issues by 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 published a section of the known issues table sorted by the date the issue was added to the document.

Known Issues by Date

Contacting NI

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.

Known Issues by Category

The following items are known issues in LabVIEW 2012 and 2012 SP1 DSC Module sorted by Category.

Citadel
287009 Warning 0 on Read Trace VI upon first run of code
Compatibility
356183 The NI DSC OPC UA API and QuickClient are not compatible with the COPA-DATA ZenOPCsvr
Controls and Indicators
255585 Mutiple instances of the same type of navigation control prevents proper alignment of the controls.
Distributed System Manager
252428 U32 bit field listed as Unnamed Type 1 in Distributed System Manager
252430 Cannot set a SV as u32 bit field type from SV dialog in Distributed System Manager
Functions, VIs, and Express VIs
49147 3XPC7K4J Saving a process to a library does not save the Access or Security information for the process
257303 Open Trace VI's terminal "trace name" returns error -1967362033 if unwired.
287009 Warning 0 on Read Trace VI upon first run of code
I/O Servers
280037 The first read of an EPICS Client PV returns 'General communication failure'
297362 EPICS I/O Server client returns incorrect STAT values in an alarm state
Installation and Activation
330447 DSC 2012 installer reports an error when installing on Windows 8
LabVIEW Object Oriented Programming
364404 "Library not found or failed to load" after closing and re-opening VI
LabVIEW Project
252427 Cannot set a SV as u32 bit field type from SV dialog in LabVIEW Project
Miscellaneous
280037 The first read of an EPICS Client PV returns 'General communication failure'
364752 OPC UA Security Fails on CompactRIO Targets That Do Not Support Setting the Target Time in MAX
Performance
229251 Citadel timestamp problems on Intel E7500 processors
314382 Modbus master write requests lost when using fast update rate
Shared Variables
93751 Alarm properties are set to default values when it is disabled and enabled again via property nodes
252427 Cannot set a SV as u32 bit field type from SV dialog in LabVIEW Project
252428 U32 bit field listed as Unnamed Type 1 in Distributed System Manager
252430 Cannot set a SV as u32 bit field type from SV dialog in Distributed System Manager
277919 Periodic I/O Server can Fail with Error -1
370238 LabVIEW crashes if the Alarm Properties windows is open while an alarm is auto acknowledged



ID Known Issue
Citadel
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.

Reported Version: 2010    Resolved Version: N/A    Added: 07/06/2011
Compatibility
356183

Return
The NI DSC OPC UA API and QuickClient are not compatible with the COPA-DATA ZenOPCsvr
When using NI DSC OPC UA to communicate with a COPA-Data ZenOPCsvr, you will get error -356615: LabVIEW: (Hex 0xFFFA8EF9) Encoding halted because of invalid data in the serialized objects

Workaround: Use a compatible OPC UA Server

Reported Version: 2011 SP1    Resolved Version: 2013    Added: 08/06/2012
Controls and Indicators
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 8.2    Resolved Version: N/A    Added: 01/05/2010
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 07/06/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 05/04/2011
Installation and Activation
330447

Return
DSC 2012 installer reports an error when installing on Windows 8
When installing Microsoft SQL Server 2005 through the DSC 2012 installer, various .NET and compatibility errors are displayed.

Workaround: Enable .NET 3.5.1 before installing LabVIEW and LabVIEW DSC. The compatibility warning dialogs still appear but the installation completes correctly.

Reported Version: 2012    Resolved Version: 2013    Added: 12/07/2012
LabVIEW Object Oriented Programming
364404

Return
"Library not found or failed to load" after closing and re-opening VI
If a dynamically loaded LVClass loads a shared library via a Call Library Function Node (CLFN), and the top level VI also loads the same shared library, there can be a conflict as the calling VIs go out of memory.

Workaround: Closing and reopening the project will clear the conflicts from memory

Reported Version: 2012    Resolved Version: 2013    Added: 07/26/2012
LabVIEW Project
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
Miscellaneous
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
364752

Return
OPC UA Security Fails on CompactRIO Targets That Do Not Support Setting the Target Time in MAX
On a CompactRIO that does not support changing the target time in MAX, OPC UA security certificates will appear expired and therefore secure communication will fail.

Workaround: Set the target time using the System Configuration API before generating and using a security certificate.

Reported Version: 2012    Resolved Version: N/A    Added: 12/07/2012
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 08/03/2010
314382

Return
Modbus master write requests lost when using fast update rate
If a Modbus master submits write requests at very fast update rates (for example: 10ms) packets will be lost.

Workaround: Update values at a slower rate to reduce the amount of lost packets.

Reported Version: 2011    Resolved Version: N/A    Added: 12/07/2012
Shared Variables
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.

Reported Version: 8.5    Resolved Version: 2013    Added: 08/03/2009
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
370238

Return
LabVIEW crashes if the Alarm Properties windows is open while an alarm is auto acknowledged
If an alarm is set to "Auto" acknowledge, LabVIEW will crash if the Alarm Properties windows is open while an alarm is auto acknowledged.

Workaround: 1. Do not have the "Alarm Properties" window open for automatically acknowledged alarms or 2. Use "Manual" acknowledgement for alarms

Reported Version: 2012    Resolved Version: 2013    Added: 12/07/2012


Known Issues by Date

The following items are known issues in LabVIEW 2012 and 2012 SP1 DSC Module sorted by Date.

93751 Alarm properties are set to default values when it is disabled and enabled again via property nodes
49147 3XPC7K4J Saving a process to a library does not save the Access or Security information for the process
229251 Citadel timestamp problems on Intel E7500 processors
252427 Cannot set a SV as u32 bit field type from SV dialog in LabVIEW Project
252428 U32 bit field listed as Unnamed Type 1 in Distributed System Manager
252430 Cannot set a SV as u32 bit field type from SV dialog in Distributed System Manager
255585 Mutiple instances of the same type of navigation control prevents proper alignment of the controls.
257303 Open Trace VI's terminal "trace name" returns error -1967362033 if unwired.
277919 Periodic I/O Server can Fail with Error -1
280037 The first read of an EPICS Client PV returns 'General communication failure'
297362 EPICS I/O Server client returns incorrect STAT values in an alarm state
287009 Warning 0 on Read Trace VI upon first run of code
364404 "Library not found or failed to load" after closing and re-opening VI
356183 The NI DSC OPC UA API and QuickClient are not compatible with the COPA-DATA ZenOPCsvr
314382 Modbus master write requests lost when using fast update rate
330447 DSC 2012 installer reports an error when installing on Windows 8
364752 OPC UA Security Fails on CompactRIO Targets That Do Not Support Setting the Target Time in MAX
370238 LabVIEW crashes if the Alarm Properties windows is open while an alarm is auto acknowledged



ID Known Issue
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.

Reported Version: 8.5    Resolved Version: 2013    Added: 08/03/2009
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

Reported Version: 8.2    Resolved Version: N/A    Added: 01/05/2010
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 08/03/2010
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 05/04/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 07/06/2011
364404

Return
"Library not found or failed to load" after closing and re-opening VI
If a dynamically loaded LVClass loads a shared library via a Call Library Function Node (CLFN), and the top level VI also loads the same shared library, there can be a conflict as the calling VIs go out of memory.

Workaround: Closing and reopening the project will clear the conflicts from memory

Reported Version: 2012    Resolved Version: 2013    Added: 07/26/2012
356183

Return
The NI DSC OPC UA API and QuickClient are not compatible with the COPA-DATA ZenOPCsvr
When using NI DSC OPC UA to communicate with a COPA-Data ZenOPCsvr, you will get error -356615: LabVIEW: (Hex 0xFFFA8EF9) Encoding halted because of invalid data in the serialized objects

Workaround: Use a compatible OPC UA Server

Reported Version: 2011 SP1    Resolved Version: 2013    Added: 08/06/2012
314382

Return
Modbus master write requests lost when using fast update rate
If a Modbus master submits write requests at very fast update rates (for example: 10ms) packets will be lost.

Workaround: Update values at a slower rate to reduce the amount of lost packets.

Reported Version: 2011    Resolved Version: N/A    Added: 12/07/2012
330447

Return
DSC 2012 installer reports an error when installing on Windows 8
When installing Microsoft SQL Server 2005 through the DSC 2012 installer, various .NET and compatibility errors are displayed.

Workaround: Enable .NET 3.5.1 before installing LabVIEW and LabVIEW DSC. The compatibility warning dialogs still appear but the installation completes correctly.

Reported Version: 2012    Resolved Version: 2013    Added: 12/07/2012
364752

Return
OPC UA Security Fails on CompactRIO Targets That Do Not Support Setting the Target Time in MAX
On a CompactRIO that does not support changing the target time in MAX, OPC UA security certificates will appear expired and therefore secure communication will fail.

Workaround: Set the target time using the System Configuration API before generating and using a security certificate.

Reported Version: 2012    Resolved Version: N/A    Added: 12/07/2012
370238

Return
LabVIEW crashes if the Alarm Properties windows is open while an alarm is auto acknowledged
If an alarm is set to "Auto" acknowledge, LabVIEW will crash if the Alarm Properties windows is open while an alarm is auto acknowledged.

Workaround: 1. Do not have the "Alarm Properties" window open for automatically acknowledged alarms or 2. Use "Manual" acknowledgement for alarms

Reported Version: 2012    Resolved Version: 2013    Added: 12/07/2012

Document last updated on 2/7/2013

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit