SignalExpress

cancel
Showing results for 
Search instead for 
Did you mean: 

Warning msg "Signal is not contiguous"

Hi,
 
I used NI FGen to generate a sine wave to pump into a circuit (under test) and use NI Hi-speed Digitizer to capture the output of the circuit.
 
The captured signal goes through a low pass filter.  This warning message appear at the filter when it is Run continuously.
 
'Run Once' does not have problem.
 
Has this got to do with synchronizing  the 2 modules in the PXI system or is it a matter of wrong sample rates.
I have searched Help and it mentioned using TClk to synchronize the 2 modules. 
 
How do you use TClk in Signal Express?
How to solve this warning msg?
 
Someone please help.....thanks.
 
Regards,
SeeMist
0 Kudos
Message 1 of 5
(7,111 Views)
Hi SeeMist,

Please post the text of the warning message you are receiving.  If it is coming from the Filter section of the project, it is probably not related to the synchronization.  There is currently not TClk support in SignalExpress, but you could file a suggestion for some TClk support to be added here:

Contact NI
http://sine.ni.com/apps/utf8/nicc.call_me

We take those suggestions very seriously and are always looking for input from customers about what features would be helpful.

Again, if you post the warning message, we'll have a lot better idea of what might be causing the problem.  I'm looking forward to your reply.



Message Edited by NI-Bongo on 05-12-2008 03:40 PM
Regards,
John Bongaarts
0 Kudos
Message 2 of 5
(7,102 Views)

Thank you for your reply, NI-Bongo.

While trying to get the detail warning message, I managed to solve the warning.

The message: " Warning occurred in Filter Step.  The current and previous '5122{1}' signals are not contiguous".

The warning disappeared after I changed the Scope Horizontal setting to Acquire Continuously instead of Acquire N samples. 

I do not seems to understand the NI-Scope in Signal Express very well.

Currently (another project) I use the NI-FEN step to generate a signal from a .hws file (a 25khz burst signal).

It works fine by itself and the "Scope Soft Front Panel" (SFP) is always good at capturing the generated signal.

(The output of generator is externally connected to the input of the Scope).

However, after I closed the SFP and inserted NI-Scope Acquire step in Signal Express, I was not always successful in capturing the signal generated.  Sometimes okay, sometimes not.

The error occurred at the FGen step : "Finite Generation timeout"

Do I have to initialise or there is a problem with my setting?  Trigger or synchronization problem?

The setting of the FGen remains the same in both tests.

The NI-Scope: Trigger = Edge ; Sample rate =100MS/s; Record Length =5000

Please advise.  Thank you.

..SeeMist

0 Kudos
Message 3 of 5
(7,095 Views)

Hello,

I am glad to hear that you resolved the warning issue.  In regard to the other project, are you just interesting in generating the signal once?  What is the lay out of the steps in the project for both the FGEN and SCOPE?  Is the FGEN set to finite or continous generation mode?  How is the SCOPE step setup in the Execution Control tab? 

 


SeeMist wrote:

Currently (another project) I use the NI-FEN step to generate a signal from a .hws file (a 25khz burst signal).

It works fine by itself and the "Scope Soft Front Panel" (SFP) is always good at capturing the generated signal.

(The output of generator is externally connected to the input of the Scope).

However, after I closed the SFP and inserted NI-Scope Acquire step in Signal Express, I was not always successful in capturing the signal generated.  Sometimes okay, sometimes not.

The error occurred at the FGen step : "Finite Generation timeout"

Do I have to initialise or there is a problem with my setting?  Trigger or synchronization problem?

The setting of the FGen remains the same in both tests.

The NI-Scope: Trigger = Edge ; Sample rate =100MS/s; Record Length =5000



Samantha
National Instruments
Applications Engineer
0 Kudos
Message 4 of 5
(7,071 Views)

Hi Samantha,

Yes, the problem is solved again.

You have asked for my setting in the Execution Control.  The small check box "start this step after" was ticked.

I unchecked it and the scope works fine.  I could capture the generated signal now.

Thank you.

Regards,

SeeMist

0 Kudos
Message 5 of 5
(7,066 Views)