Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 69269

TCLK Synchronisation error requires computer restart

$
0
0

Hello

I am using a PXI chassis with an MXI card, and synchronising a PXI-5122 digitiser with a PXI-5412 FGEN using NI-TClk.

I configure the TClk session in the conventional way (I think!) as so:TClk question 3.png(Apologies for the broken wires - I tried to take a snippet of a bit of my VI rather than the whole lot, which I unfortunately can't release.  However, it works fine so no need to worry too much about it!)

Then the program runs, and works fine, and then at the end I release the devices as follows:TCLK question2.png

And this also works fine.

The bit that doesn't work is if a user sets a combination of settings that aren't allowed, for example capturing more samples than is possible with the onboard memory.  Then, despite the fact the snippet above still runs on exit, I am unable to use the cards again without shutting down the computer and re-booting it.

The error I get then comes from the "niTClk Sychronise.vi" and says:NI TClk problem.png

I can, of course, check for all possible permutations of options for the cards and prevent incompatible options.  These are strictly in-house applications, though, and I would like to give my users as much flexibility as possible, so that would be quite a task.  I'm not complaining though - I know it's the right thing to do but I don't write perfect code first time every time so there will still be some testing and the occasional time when something slips through.

It seems wrong that even during my testing there will be times when I have to shut down the whole rig just to get up and running again, and quite a waste of time - so my question is:

 

Is there something I can add to the 'standard' combination of niFgen Abort Generation.vi, niFgen Close.vi and niScope Close.vi, which will force the cards and TClk session to be released regardless of their state (i.e. if they have hung)?

Thank you!

P.S. This is for a built application - running the code from LabVIEW itself I don't have the same problem.

 

 


Viewing all articles
Browse latest Browse all 69269

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>