05-03-2013 03:09 PM
05-03-2013 03:58 PM
Hi YBilgin,
Do you get a crash while SPE is loading? Assuming the issue is similar to the previous customer, I may be able to provide a solution. Essentially, this could be related to a sequence file recursively calling itself leading to the exception you see while loading SPE.
- Let's try the following to confirm this is indeed the cause:
1. Move everything in the folders to the Desktop.
2. Relaunch SPE. Does it continue to crash?
If the crash no longer occurs, then the recursive call is in one of the sequences files saved in these folders. Unfortunately, the only way to fix this issue is to open each nivseq file in a text editor modiy the file such that there is no sequence calling itself. The section of interest in the XML files is <References>. In the <References> section you will find zero or more <Reference> sections. Confirm that no <Reference> is calling itself. You must also consider the scenario where the reference indirectly links to itself; for example, SeqA calls SeqB and SeqB calls SeqC, but SeqC calls SeqA - this will lead to a recursive call to SeqA.
This issue has been addressed in NIVS 2012.
05-03-2013 04:11 PM - edited 05-03-2013 04:11 PM
05-03-2013 04:14 PM
05-04-2013 05:05 PM
Many thanks for your patience and cooperation in helping us narrow down the cause Harris. The editor does indeed validate sequences in know paths during the launch; those paths include <NI VeriStand Program Files>\nivs.lib\Sequence Library and <NIVS PublicDocs>\Stimulus Profiles. If the sequence is invalid we show a corresponding icon in the Sequences palette. In NIVS 2012, we manage items differently and therefore this issue doesn't appear there.
05-06-2013 12:26 AM - edited 05-06-2013 12:27 AM
Glad we got to the bottom of this. Was it the process dumper files that helped in the end? Can you tell me about any other significant changes or improvements for 2012's Stimulus Profile Editor? Thanks.
P.S. Would this issue get posted to the known issues for 2011?
05-06-2013 10:37 AM
There are a number of changes,
Usability changes(pulled from What's New in VeriStand 2012 help doc):
New Profile steps (pulled from What's New in VeriStand 2012 help doc):
Bug Fixes (VeriStand 2012 Help: Bug Fixes😞
There are a few bug fixes in 2012 relating to the workspace as well. I would look through the Bug Fixes list for detail and their Issue ID numbers.
05-06-2013 04:38 PM
Yes, the crash dump was the item that lead me to finding the issue - very helpful. Tim posted a great list of SPE 2012 improvements. The issue is actually documented in the 2011/2011 SP1 known issues list as "Recursive call of nivsseq can cause Stimulus Prifle Editor to crash". Unfortunately, the crash dialog doesn't necessarily imply the issue is related to a recursive call; however, statistically this appears to be the issue in most cases.
05-06-2013 05:14 PM
I want to thank to comunity and Nestor.
Finally (after deleting sequence library and simulus profiles folders) SPE GUI poped up. It was really happy moments for me.
But when I try to open previosly created stimulus profile, it crashes again. I guessed the reason of crash is missing libraries. I have copied libraries (Seqence Library and Stimulus Profiles Folders) from a working PC to my PC.
But nothing changed. SPE started to crash again.
Is there any solution or walk aroud trick for that issue.
05-06-2013 06:00 PM
Hi Hreidmar,
- Is the crash occuring when opening the stimulus profile file or when SPE is loading?
- If you are able to load SPE, can you create, save and reopen a new stimulus profile in a different folder to the crashing stimulus profile file? Or does this new file also cause SPE to crash?
- Is this is a crash or does an error dialog (with Exception information) appear? If you get an error dialog with exception information - what is that exception information?
- Your nivsstimprof file may be located in the same folder with a nivsseq which resucrsively calls itself. SPE has a third tree in the Sequences palette named, <Current Document Folder>. Items here are dynamically populate with sequences relative to the currently opened file. Therefore, when you load your nivsstimprof file, SPE will locate all nivsseq files in this folder (and subfolders). I suggest confirming that no sequence files are recursively calling themselves in this folder.