Skip to content

SigGenRP Tech Notes

SigGen Variables Must be Unique

TN0949

Product: SigGenRP, BioSigRZ
Version: All
Date Added: 2014-11-07

Issue

When you generate multiple segments in the same SigGen signal file (.sig), you can only use each variable once.

Symptoms: If you generate a multi-segment stimulus with duplicate variable names, the output displayed in the SigGen multi-purpose plot (stimulus view) will be flat, not showing any stimulus.

Workaround

If you need a signal with multiple segments that each use an identical variable, you can create them to be identical EXCEPT for the name. Each name can only be used once in a given .sig file.

With unique variable names for each segment, SigGenRP and SigGenRZ will generate the stimuli correctly.

Note

When editing these variables in the future, be sure to edit all variables in the same way.

Running SigGenRP or BioSigRP causes AP2 Driver Failure error

TN0832

Product: SigGenRP, BioSigRP
Version: All
Date Added: 2008-07-11

Issue

When BioSigRP and SigGenRP are installed on the PC, uninstalling one will cause the remaining application to fail. The following error is displayed:

Solution

Reinstall the affected application to fix this issue.

'Please enter no more than 50 characters.' error message displayed when designing components of a signal segment in SigGenRP

TN0180

Product: SigGenRP
Version: All
Date Added: 2005-05-13

Issue

When designing components of a signal segment in SigGenRP, for Call: File16, you will get a "Please enter no more than 50 characters." error message if you attempt to enter a filename that is more than 50 characters long. In addition, any filenames between 34 and 50 characters long (including file extension) will be truncated to 34 characters without warning and will not work properly.

Similarly, for Call: File*, when browsing for a file, if the resulting path is longer than 50 characters you will get the error message mentioned earlier. In addition, any paths between 34 and 50 characters long (including file extension) will be truncated to 34 characters without warning and will not work properly.

Workaround

Make sure, depending on the call above, that the filename with extension or the path with extension is shorter than 34 characters.

SigGenRP Play All does not work

TN0127

Product: SigGenRP
Version: All
Date Added: 2004-05-05

Issue

Stimulus plays only once or twice after clicking "Play All" in SigGenRP

Solution

Reload the Stimulus RCO file.

'LoadNorm AP2 Error >>_allof' error when loading RCO files in SigGenRP files that use a normalization file

TN0107

Product: SigGenRP
Version: All
Date Added: 2004-02-05

Issue

If a normalization file has been specified in the Signal Parameters dialog box, a "LoadNorm AP2 Error >>_allof" error will be generated when an RCO file is specified in the Setup RP Device dialog box.

Workaround

Always select the RCO file before specifying a normalization file. If the normalization file has already been specified and device setup option must be changed, clear the Use Norm File check box in the Signal Parameters box before modifying the device setup. After the device setup is complete, return to the signal parameters and select the Use Norm File check box again.

Segment delay

TN0031

Product: SigGenRP
Version: All
Date Added: 2002-08-12

Issue

Segments require a 0.1 millisecond delay relative to the start of the Signal.

AP2 _allotf errors generated when sample rate is changed or variables are initialized

TN0028

Product: SigGenRP
Version: All
Date Added: 2002-08-22

Issue

Normalization files cause problems when changing sample rate or initializing variables. When the sample rate is changed or the variables are initialized AP2 errors with _allotf are generated.

Workaround

Do not change sample rate or initialize variables.