Functional Safety Known Issues

Aperçu

This document contains the known issues with NI Functional Safety Editor. New issues appear at the top of this document. This list includes only severe or the most common issues, and does not include every issue known to NI.

The workarounds described in this 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. The brief description given does not necessarily describe the problem in full detail. If you would like more information on an issue, visit ni.com/contact and reference the issue ID. If you identify a workaround for an issue that is not listed in this document, please contact NI so that the workaround may be published.

ID Known Issue Affected Versions
726500 Functional Safety Editor loses transition condition when editing in the right rail May 2018
690073 Compound states do not correctly resize for long transition conditions. May 2018
690101 Transition logic that is semantically equivalent to FALSE before compilation does not function correctly. September 2017
622824 Transition conditions can change locations when loaded from file. September 2017 - Current
593853 If you save the User Program while editing a text box, the changes to the text box are not committed. September 2017 - Current
627068 Cannot open files of the same name. September 2017 - Current
650011 Creating a compound state over an existing state pushes the transition conditions to the outside of the compound state, breaking the transitions. September 2017 - Current
659712 For digital inputs with a discrepancy time specified, the actual discrepancy time allowed by the module could differ. September 2017 - Current

 

Known Issues with NI Functional Safety

ID Known Issues
726500

Functional Safety Editor loses transition condition when editing in the right rail

If a user places two states on the block diagram and connects them with a transition then clicks on the transition label and adds text, the transition label text can disappear if the user clicks anywhere else on the block diagram.

Workaround: Right-click the transition wire and choose "create transition condition" to enter text instead of clicking on the wire itself. See KB "Unable to Add Transition Conditions to Functional Safety Editor" for more details

Back to Top

690073

Compound states do not correctly resize for long transition conditions.

Compound states do not expand to fit large transition conditions, which can result in some text being hidden. When the compound state is manually expanded to fit the wire transition condition, the right side expands oddly. Once expanded correctly, the compound state cannot be made smaller than wire transition condition manually.

Workaround: Manually expand the compound state. Alternatively, use multiple lines on the transition.  

Back to top

690101

Transition logic that is semantically equivalent to FALSE before compilation does not function correctly.

If the transition logic between two states that can be simplified by inspection to FALSE (for example, A && !A), then the transition will always execute. Such logic should fail the required safety logic validation requirements in the C Series Functional Safety Manual prior to reaching a deployed state. However, setting a transition logic to FALSE can be useful while debugging a User Program. Do not rely on this technique when developing and testing User Programs with the Functional Safety Editor September 2017.

Workaround: If debugging a User Program, use a Boolean variable to isolate code instead of FALSE.  

Back to top

622824

Transition conditions can change locations when loaded from file.

With a state machine containing transitions:  Save it, close it, then re-open it.  One or more transition wires may have moved and no longer looks "clean". This can also appear as issue #656340: when moving multiple items simultaneously (mass select), occasionally one or more of the transition conditions does not move concurrently.

Workaround: N/A  

Back to top

593853

If you save the User Program while editing a text box, the changes to the text box are not committed.

If you try to save the document while editing a text box in the right rail or on the diagram, the changes to the text box are not reflected in the saved file.

Workaround: Deselect the text box by clicking out of it prior to saving.  

Back to top

627068

Cannot open files of the same name.

If you have opened a given .FSP file, that name is now 'reserved' by the Functional Safety Editor for that particular copy of the file.  If you try to open a file of the same name from a different directory you will get an error. This is also embodied in issue #644840: if you try to 'Save As' a .FSP file with the same name but in a different directory, the subsequent compilation will fail.

Workaround: To open the other file, close the Functional Safety Editor to reset its session memory. Then, open the second file with a fresh instance of the Functional Safety Editor.  

Back to top

650011

Creating a compound state over an existing state pushes the transition conditions to the outside of the compound state, breaking the transitions.

Start with two or more states and a transition between them with some logic. Drop (or "ring") one of the destination states with a new compound state. You will see the transition condition get pushed to outside the compound state. This is an invalid location that results in a broken wire.

Workaround: Delete the internal wire segment and rewire. This will move the transition condition inside. Or, copy the transition condition to the existing segment inside the compound state and delete the external transition condition. 

Back to top

659712

For digital inputs with a discrepancy time specified, the actual discrepancy time allowed by the module could differ.

The actual discrepancy time allowed between dual channels is slightly shorter from the time configured in the Functional Safety Editor due to signal routing and counter timebases.  This results in the slightly more conservative behavior with the assertion of the discrepancy fault sooner than specified discrepancy time. The time will be shorter by the Minimum Discrepancy Timer. This time can be found in the C Series Functional Safety Manual under "Minimum Discrepancy Timer."

For example, for a Dual Input configured with 500 us discrepancy in the Functional Safety, the discrepancy at the board could be staggered as much as 500 us - MinimumDiscrepancyTimer (100 us) = 400 us.

Workaround: N/A  

Back to top

 

 

Note: 

In addition to the above Known Issues for the Functional Safety Editor, there are Known Issues that could impact Functional Safety users which are distributed by other drivers, and therefore are listed elsewhere. For example:

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).