Signal Generators

cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

NI-TClk reports error -200312 from the AWG. (Specified waveform is invalid.)

Highlighted

NI-TClk reports error -200312 from the AWG. (Specified waveform is invalid.)

Okay, there is no easy way to describe the steps leading up to the this error.

 

I run a system that has a PXIe-5122 and a PXIe5442. I use TClk to allow me to add multiple results together to increase signal to noise.

MODES

Typically, all of the data can be collected in direct mode  (no streaming) and that works fine.

Sometimes the data to be collected from the 5122 does not fit in the memory, and streaming is set up and that works fine.

Sometimes the data to be produced by the 5442 does not fit in memory, and streaming is set up and that works fine.

One can even create a scenario where both are streaming and that works fine.

PROBLEM

However, any time streaming has been activated on the 5442, it is no longer possible to return to the mode where one does not stream on 5442.

 

In fact, the system gets to a point where one must shut down the PC and reboot to bring the cards back online.

 

 

Background

Anytime a new script must be run on the awg I run (this happens each time on streaming since buffers need to initialized each time.)

 

niFgen_AbortGeneration
niFgen_ClearArbMemory

 

before I reload the awg. I have tried reset in NIMAX. I have tried restart under Win10.

 

Something gets broken in a weird way.

REPORTED ERROR

The only reported error occurs not at any NiFgen function call but at

niTClk_Initiate()

 

Here is a sample error stream.

 

    NI-TClk initiated a session, and the instrument driver reported an error.
    Error reported by the instrument driver:
    The specified waveform is invalid.
    Waveform Name: www10003
    Status Code: -200312
    Session index (starts at zero):

 

www10003 is the name of the previous streaming waveform / waveform location (4 by 1MSample for streaming) but it should not be included in the current script. This is a ghost in the system. Do I need to specifically deallocate this waveform memory because niFgen_ClearArbMemory() does not? If so what command to use?

 

Another indication of a memory error is that the returned streaming waveform name from niFgen_WriteBinary16Waveform() changes each time, we run. The first run is www10000, the second www10001, the third www10002...

 

This sequential renaming of the waveform make me suspect that the niFgen_ClearArbMemory() may not be releasing either the memory, namespace, etc.

 

Any help is appreciated.

 

Greg

0 Kudos
Message 1 of 5
(76 Views)

Re: NI-TClk reports error -200312 from the AWG. (Specified waveform is invalid.)

Greg,

 

I see you posted your configuration but would you be able to share your code with us? This isn't something we see a lot, and it would be very helpful to see how you have your code set up.

 

If I had to guess I would say there may be sessions that aren't being closed out of properly.

Patrick O.
Applications Engineering
National Instruments
0 Kudos
Message 2 of 5
(58 Views)

Re: NI-TClk reports error -200312 from the AWG. (Specified waveform is invalid.)

I am working on two fronts.

 

Front 1 is cutting down the code to remove all of the GUI overhead and non pertinent (and some  non NI) hardware etc.

 

Front 2. I am also looking at my management of the thread safe queues to make sure there isn't something there (possible abandoned streaming queues)  that flew under the wire for years and now in my move to CVI2017 or latest drivers rears it head to offend the compiler or drivers in some way. I will get something posted by the end of the week if the gods align and the grad students are held at bay.

0 Kudos
Message 3 of 5
(50 Views)

Re: NI-TClk reports error -200312 from the AWG. (Specified waveform is invalid.)

I appreciate you taking the time to remove all the non pertinent information. Let's hope those gods align and the code comes through quickly. I look forward to going through it.

Patrick O.
Applications Engineering
National Instruments
0 Kudos
Message 4 of 5
(39 Views)

Re: NI-TClk reports error -200312 from the AWG. (Specified waveform is invalid.)

Okay. No joy on code stripping yet but I may know the problem.

 

I am using waveform scripting (niFgen_ConfigureOutputMode (vi, NIFGEN_VAL_OUTPUT_SCRIPT) ) mode with niFgen_WriteNamedWaveformI16 for local waveforms .This allows the user to create mostly arbitrary length waveform and number of waveform loops.

 

When I (aka user) add streamed waveforms, I use niFgen_AllocateWaveform (still with script output mode). Current help documentation states that niFgen_AllocateWaveform requires the output mode to be sequence. Although this generates a usable output, there is no "niFgen_DeallocateWaveform or similar". This seems to leave an issue with on board memory that is not resolved by my faithful memory annihliation tools of niFgen_AbortGeneration and  niFgen_ClearArbMemory.

 

In short for streaming I use

niFgen_AllocateWaveform ();

niFgen_SetAttributeViInt32 (vi, VI_NULL, NIFGEN_ATTR_STREAMING_WAVEFORM_HANDLE, waveform_handle));

niFgen_WriteBinary16Waveform()   //loads first chunk of data to stream

niFgen_GetAttributeViString (vi, "0", NIFGEN_ATTR_STREAMING_WAVEFORM_NAME, 512, streamwfname);

 

This gives me the necessary name to populate the script.

 

As I type this I wonder if I can use niFgen_DeleteNamedWaveform () to fix this mess. Typically this is paired with niFgen_AllocateNamedWaveform () but since I have the went through the trouble to get the name and all.

 

More to follow tomorrow.. 

0 Kudos
Message 5 of 5
(5 Views)