CFP clock loose synchronization

Hi!
   It seems to me there's a great problem in my 2 cFP-2020. They run an embedded application, in which I manually can set system time. In a timed loop I get cFP system date-time, and I notice that, in comparison to windows system clock, cFP clock looses about 2-3 seconds each 10 minutes: it's really too much!
   In my application I have to log events with timestamps, and I need an accurate clock! Moreover, my final application won't have an ethernet connection, so that I can't provide a time-server! So onboard clock must be accurate! I can only send packets via RS232 to update time, but I whish I could do it once per day, not once per minute!
   Last thing I noticed, is that this lost of synch happens mainly when I cyclically get system time, but it seems absurd to me that system clock looses cycles when "asked" for time!
   Thank so much!
graziano
Attachments:
time.vi ‏89 KB

These two .vis are one way to get and distribute the HW clock.
A 'read' of time_global.vi will return the most recently set time.
We read our I/O about 1/second so the time is plenty accurate
for our applications.
Matt
Message Edited by Matthew Williams on 04-20-2006 10:32 AM
Attachments:
get_raw_values.vi ‏51 KB
time_global.vi ‏19 KB

Similar Messages

Increase sound volume above 150% without loosing synchronization

I would like to increase the sound volume substantially above 150%. There have been some suggestions to this topic (extract sound and work with sound studio or audacity).
When I do this I loose synchronization of audio and video. Does anyone know a way to increase sound substantially without loosing synchronization?
Bertrand Völckers
iMac Mac OS X (10.4.7)

It doesn't necessarily produce any distortion ..it all depends on how loud - or quiet - the sound was to start with.
In Audacity & Sound Studio you can see if there's going to be any distortion as you raise the sound level: if the tops & bottoms of the visible waveform get chopped off ("clipped", in techno-speak) as the waveform grows larger, then you'll hear distortion.
If there's no clipping, and the waveforms keep their original shape - but just become larger - then there'll be no distortion ..bigger doesn't necessarily mean distorted, unmanageable or unbearable.
It's not necessarily VERY LOUD EITHER! ..If the original audio was just the hum of air through a swan's wings as it flew by, that might be almost inaudible on your sound track. By raising the audio level, say, 500% it may become noticeable.
That'd also raise the level of everything else by 500%, too, but if it was a still day, that might be just a slight background hiss. You could filter out the general hiss, and just leave the thrum of the swan flying by..
In this bit of audio..
..raising the levels by 500% would certainly distort (by clipping; chopping off the edges) the loudest regions, but the quietest sections are unlikely to become distorted.
If all the sound is as low as the quiet sections above, then there's unlikely to be any distortion after boosting it.

NI6682H using IEEE1588 Clock to synchronize Boardtime

Hello,
I'm working with NI 6682H. I want to use IEEE 1588 Clock to synchronize the board time.
If I understand correctly I've to configure it for SLAVE.
What I don't understand is how I can do it.
I've seen through the examples and wrote some code, which works but the Clock is running as MASTER.
My second question would be: how/where can I specify the Source for the MASTER-Clock (URL, IP, ...).
My thrist question: where can I find the MAC Adresse of the RJ45 Port on the Module. I didn't finde it MAX or VI/Propertynodes.
best regards
christian

Hi Christian,
yes i think you've understand it correctly but you need an IEEE 1588 Master, if you want to use the NI6682 Module as Slave.
I've attached you a Master VI and a Slave VI. There you can see that the Master is using the "Send Time to UDP" function and the Slave the "Get Time from UDP" Function.
You don't need to specify the Source of the Master Clock, because for the communication the UDP Protocoll is used. The Master and the Slaves only need the same UDP Port to communicate together.
http://www.ni.com/white-paper/4950/en/
I think you can find the MAC-Address of the Module on a Label that is attached to the 6682H Card. And i found an example to programmaticly get the IP & MAC Address: https://decibel.ni.com/content/docs/DOC-15459
Regards,
Stefan
Attachments:
Generate Sync Clock-Slave.vi ‏32 KB
Generate Sync Clock-Master.vi ‏67 KB

How to output the digital clock and synchronization signal from the NI USB-6211

Hello,
I need to connect the NI USB-6211 to control a digital to analog convertor chip (AD5541). However, this chip requires three input signals :1) Clock input, 2) Logic input or a synchronization signal and 3) Signal Serial Data input (CS, SCLK, DIN).
how to output the digital clock and the synchronization signal from the NI USB-6211?

Hi SaberSaber,
You should be able to use the counters to generate a pulse train that could be used for clock and synch purposes.
Hope this helps. Let us know if you have more questions.
Dave C.
Applications Engineer
National Instruments

How to use the PXI's 10MHz backplane clock to synchronize two or more 6031E boards?

Hi,
I'm trying to use two 6031E boards to acquire multiple channels Analog Inputs, and I'd like to sync them with the PXI backplane clock (not the RTSI bus). I found an example from NI, "Two E-Series Shared ScanClk.vi", and modified it a bit. But I'm wondering if the two boards must have the same acqusition rate? e.g. Can I have 1 board acquiring at 1kHz while the other one at 20Hz? and if yes, how do I do it?
Your input will be very much appreciated. Thanks!
Dan
Attachments:
mod_Two_E-Series_Shared_ScanClk.vi ‏148 KB

Unfortunately, E Series boards cannot synchronize with the 10 MHz PXI backplane clock. They do, however, have access to the PXI trigger lines, which are basically the RTSI lines. Except for line 6 which is the star trigger line. They can only read from this line.
The example program you have selected will definitely be part of your solution. It allows you to share the scan clock timing signal between two boards. If you would like the slave board to acquire at a slower scan rate, you could always route the master's scan clock to one of the slave's on-board counters which can act as a frequency divider. The output of this counter can become the new slower scan clock for the slave board. Use the Generate Pulse Train shipping example VI as your frequency d
ivider. Finally, make sure you route the signals appropriately and you'll be in business.
I hope this helps!
Russell McMurtrey
Applications Engineer
National Instruments
http://www.ni.com/support

Using the X Series interal clock for synchronization

Hi,
I am slowly learning how to use Labview in my work. I have 2 X-series multifunction DAQs that are each linked to a computer. I am reading in the user manual that the DAQ has a built in 10MHz clock that can be used by other DAQs in the system. The idea is that I'd like one of the two DAQs to be a master and all operations should be theoretically unified. I am unclear on how to actually tap into the internal 10MHz clock on DAQ1. I may be misinformed about some fundamentals of Labview, I recognize this. I played around with some DAQmx functions and was confused because the Create virtual channel DAQmx that I assume has to come first in a sequence of DAQmx's still required an external signal source: "lines". This seems counter-intuitive for my purposes!. Can there be an input that is genuinely from within the DAQ? If I create a DAQ assistant to generate counter output, I see how it can be timed using the 10MHz reference clock but somehow I also feel like this is an incorrect strategy.
I am still an amateur but I haven't found very good resourses that actually explain how to generate timing, only that you can do it. Besides, isn't the 'timing' of any signal I generate in the program dependent on how fast the while loop surrounding the whole program cycles? And can this be controlled?
Any starting point or advice you can provide is greatly appreciated.

Hi twitchell,
Are you trying to synchronize analog input? If so, this should be a good starting point: Synchronizing DSA, S Series, and X Series Devices With a Single NI-DAQmx Task
Otherwise, please post more details about what you are trying to do: channel type, sample rate (same on each device or not?), triggering, etc.
Brad
Brad Keryan
NI R&D

CFP signal loose

Hello!
We have installed cFP-2100 controller and cFP-AI-111 for control and logging the data from sensors. cFP controller is connected (via ethernet) to PC with basic LabView application. While application runs in LabView Development System all everything is allright, but if I make executable file and run it, then in few hours (everytime different) network adapter crashes and loose cFP signal. Can you help me with any suggestion or advise?
Looking forward to hear from you,
Dmitri

Dmitri,
Where are the executable and the VI located? Are they on your PC or deployed to the cFP-2100?
Intermittent loss of network communication can be caused by a duplicate IP address. If you disconnect your cFP-2100 and on your host PC ping the IP address that your cFP-2100 was assigned, do you get a response? If you do, then you have a duplicate IP address.
How is your cFP-2100 connected? Is it in an isolated network or exposed?
Isolated Network (static IP):
1. Direct connection between PC and cFP-2100 with crossover Ethernet.
2. Hub/Switch without an external network connected. Ie, no DHCP server. Straight-through Ethernet is used.
Exposed Network (DHCP server):
1. Typically has a router with DHCP.
What is the IP address and subnet mask of your cFP-2100 and your host PC?
Another possibility is that your communication is being crowded out because your executable is gradually consuming all memory if it is deployed on your cFP-2100. To monitor both CPU and Memory usage, navigate to Tools»Real-Time»System Manager in your Project Explorer window in LabVIEW. Be sure to click the Start Monitoring button to begin monitoring.
Trey B
Applications Engineering
National Instruments

Clock looses time

My clock wont keep time. I have it set to check from the internet and have set it to the correct time zone. I have also trashed the pref file multiple times and it has not helped. When I click on the clock prefs it will fix itself but this is only because it checks from the internet but it may later loose time again. This also happens sometimes when I boot up. I was told before that this is because of the clock battery however, this does not apply because I have a MBP not a desktop. I do have bootcamp v.1.4 running xp pro sp2 if that means anything. This problem is not specific to OS X because it happens with windows as well.
Thanks,
MacGuy3000
P.S. this is unrelated but does anyone know the release of leopard? I know that it is sometime this month (october) but not the exact date.

My brother told me this happened to him as well, and is caused by using Boot Camp. You might check in the Boot Camp forum:
http://discussions.apple.com/forum.jspa?forumID=1165
See if anyone has found a solution (my brother simply uninstalled Boot Camp, as he has several other Windows machines around the house, he just wanted to try it out).
Francine
Francine
Schwieder

Clock looses time and date, Clock looses time and date

Clock losses time & date when battery dies whats my problem?

Well, probably the reason that would happen is that when the iPod is asleep, a tiny bit of the battery keeps the clock alive. If it is completely deprived of all power, that it wouldn't be able to keep that small process going. Just make sure to not let the battery die entirely, and it should be fine. I usually keep my iPod plugged in, but if I can't, I stop using it when I get the 20% battery warning. If you put it to sleep when you get this alert, there is plenty of juice to keep the clock alive in the background for quite a while.

Error while exporting the clock to CLK OUT of 5922

Hi
I am using a PXI-5922 for my application. I need to export the internal clock to the CLK OUT pin in the front pannel of the board. I tried almost all the possible VIs and properties in NIScope functions. Everywhere it gives an error saying "Your device does not support this routing" though in 5922 manuals reads as its possible.
Please suggest any solution.

Hi Vsh,
I'm sorry but the 5922 does not support exporting the internal sample clock to the CLK OUT connector.
The manual [1] has a routing diagram which shows what signals can be routed to the connector, I've placed it here
for reference as Figure 1 below.
Fig 1. Clock Routing Diagram
You can route the CLK IN external connector to the CLK OUT external connector, as the diagram shows.
Figure 2 shows how to do this, these are all niSCOPE palette vi's.
Fig. 2 CLK IN to CLK OUT
And finally, here is what will throw an error with the NI 5922, as seen in Figure 3 below.
Fig 3. Error 89136
What options do you have?
#1. Assuming this is to synchronize the digitizer with something else, then use a external
device's sample clock.
#2. Route the PXI CLK to the CLK Out terminal and use this for sample clock source/synchronization
#3.
[1] NI High Speed Digitizers Help
Message Edited by Matthew W on 09-05-2007 09:39 AM
Attachments:
5922_clocking_options.JPG ‏43 KB
vi_used.JPG ‏16 KB
vi_throwserror.JPG ‏19 KB

How to synchronize two USB webcams (each at 30fps) for a combined 60fps video? Three for 90fps?

Hello All,
Multiple-Camera Lab Application: How-To?
Exploring a loose-synchronization for cameras, low resolution, B&W=gray video capture, that may require up to 200fps, laboratory application.
Frames would be recorded serially, from 1_frame/10msec at 100fps to 1_frame/5msec at 200fps.
Consecutive frame-to-frame intervals do not need to be fixed at 10msec, they may vary a lot +/-50%, are non-critical.
Video recording may last up to 1_minute maximum real time (no sound recording needed at any time).
Specs say a generic USB2.0 webcam can record up to 30fps.
And USB2.0 is a half-duplex serial protocol.
Using two or more webcams in parallel, focused on the same scene, may yield a composite video capture at multiples of 30fps.And much lower price than a single dedicated high speed camera.
Ultimately all frames have to be assembled -in sequence- into one big video recording.
Any comments, any ideas? Did anyone try this?
Thank you,
Dan

Hi,
Sorry I am not much help about this. Creative webcams aren't built to work that way.

Please help with C code to synchronize counter output to analog input

Hi All,
I am using NI DAQ USB-6353 with text-based C code to control it. I would like to send a continuous pulse train from the DAQ to pulse a power supply, which then activates an electron beam producing current to be read by the analog input port of the same DAQ. I would like to keep only the analog samples during the pulse peak and samples of a couple pulse widths right after. I am successfully to generate a pulse train using the sampled clock from a counter output channel, but fail to use the same clock to synchronize the pulse train with the analog input. DAQmxReadAnalogF64 is not called by the static function EveryNCallback set for the analog input task. Am I doing something wrong with the following codes? It would be great if it turns out only I am using the wrong sampled clock name of the counter ("dev1/PFI8") for the analog input. Or is something more fundamental that a counter cannot be sync. with an analog input?
Would someone be able to send me a link to an example in C or C++ or visual basic showing how to synchronize a buffered sample clocked digital pulse train from a counter output channel to an analog input? To simplify the post, the below codes do not include the static functions EveryNCallback and DoneCallBack, but I can send them if needed.
Many thanks in advance for your help,
Thuc Bui
//setting operation parameters
double initDelay = 0.0, freq = 10;
double dutyCycle = 0.0001;           //thus pulse width is 10 microsec
unsigned highTicks = 4;   //per period
unsigned numSamplesPerPeriod = highTicks / dutyCycle; //40000 samples/period
unsigned lowTicks = numSamplesPerPeriod - highTicks;      //per period
unsigned sampleRate = 2*numSamplesPerPeriod*freq;       //800000 samples/s
//create counter
TaskHandle counterTask;
int errCode = DAQmxCreateTask("", & counterTask);
errCode = DAQmxCreateCOPulseChanFreq(counterTask, "dev1/ctr0", "",
                                 DAQmx_Val_Hz, DAQmx_Val_Low,
                                 initDelay, freq, dutyCycle);
errCode = DAQmxCfgSampClkTiming(counterTask, "dev1/PFI8", sampleRate, DAQmx_Val_Rising,
                           DAQmx_Val_ContSamp, numSamplesPerPeriod);
//create analog input
TaskHandle aiTask;
double minVolt = 0.0, maxVolt = 1.0;
errCode = DAQmxCreateAIVoltageChan(aiTask, "dev1/ai0", "", DAQmx_Val_Diff,
                                 minVolt, maxVolt, DAQmx_Val_Volts, "");
unsigned bufferSize = 10* numSamplesPerPeriod;
errCode = DAQmxSetBufInputBufSize(aiTask, bufferSize);
errCode = DAQmxCfgSampClkTiming(aiTask, "dev1/PFI8", sampleRate, DAQmx_Val_Rising, DAQmx_Val_ContSamp, numSamplesPerPeriod);
errCode = DAQmxRegisterEveryNSamplesEvent(aiTask, DAQmx_Val_Acquired_Into_Buffer,
                                        numSamplesPerPeriod, 0, EveryNCallback, 0);
errCode = DAQmxRegisterDoneEvent(aiTask, 0, DoneCallBack, 0)
//start aiTask first
errCode = DAQmxStartTask(aiTask);
//then counterTask
errCode = DAQmxStartTask(counterTask);

Hi Xavier,
Thank you very much for getting back to me. I really appreciate it. I followed your advice with the option 2 and simplified my code by using one of the NI C example templates to generate the below codes (also attached). I was able to see the pulses generated with an oscilloscope, and on the same oscilloscope I could see the ouput pulses of the electron beam probe. Unfortunately, the below code via DAQmxReadAnalogF64 reports of no data read from the probe and finally times out. Below is the error message given by this function. I did check the connection of the analog input wires to make sure they were connected to pin 1 (A0+) and 2 (A0-) because I was using the terminal configuration DAQmx_Val_Diff. Do you see any obvious errors I have made in my codes?
Thanks a lot for your help,
Thuc Bui
Task started, waiting for trigger...
Acquired 0 analog samples DAQmx Error: Some or all of the samples requested have not yet been acquired.
To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It is also possible that you configured the task for external timing, and no clock was supplied. If this is the case, supply an external clock.
Property: DAQmx_Read_RelativeTo
Corresponding Value: DAQmx_Val_CurrReadPos
Property: DAQmx_Read_Offset
Corresponding Value: 0
Task Name: _unnamedTask<1>
Status Code: -200284
End of program, press Enter key to quit
********************** C Code **************************************************
#include <stdio.h>
#include "NIDAQmx.h"
#include <math.h>
#define DAQmxErrChk(functionCall) { if( DAQmxFailed(error=(functionCall)) ) { goto Error; } }
int main(void) {
int32 error = 0;
char errBuff[2048]={'\0'};
TaskHandle taskHandleDig=0;
TaskHandle taskHandleAna=0;
double  timeout=10;
double minVol = -1.0, maxVol = 1.0;
double initDelay = 0.0;
double freq = 10.0;
double pulseWidth = 1.0e-5; //10us
double dutyCycle = pulseWidth * freq;
unsigned hiTicks = 4;
double sampleRate = hiTicks/pulseWidth; //samples/s
unsigned lowTicks = ceil(sampleRate/freq) - hiTicks;
unsigned nSpPeriod = hiTicks + lowTicks;
unsigned numPulses = 1;
unsigned nSpCh = numPulses*nSpPeriod;
double sampleRate2 = ceil(2.0*sampleRate);
unsigned sampleMode = DAQmx_Val_FiniteSamps;
/*********************************************/ /*/ DAQmx Configure Code /*********************************************/
DAQmxErrChk(DAQmxCreateTask("", &taskHandleDig)); DAQmxErrChk(DAQmxCreateTask("", &taskHandleAna));
DAQmxErrChk(DAQmxCreateAIVoltageChan(taskHandleAna, "Dev2/ai0", "", DAQmx_Val_Diff, minVol, maxVol, DAQmx_Val_Volts, ""));
DAQmxErrChk(DAQmxCfgSampClkTiming(taskHandleAna, "/Dev2/Ctr0InternalOutput", sampleRate2, DAQmx_Val_Rising, sampleMode, nSpCh));
DAQmxErrChk(DAQmxCreateCOPulseChanFreq(taskHandleDig, "Dev2/ctr0", "", DAQmx_Val_Hz, DAQmx_Val_Low, initDelay, freq, dutyCycle));
DAQmxErrChk(DAQmxCfgSampClkTiming(taskHandleDig, "/Dev2/PFI12", sampleRate2, DAQmx_Val_Rising, sampleMode, nSpCh));
unsigned bufferSize = nSpCh;
DAQmxErrChk(DAQmxSetBufInputBufSize(taskHandleAna, bufferSize));
DAQmxErrChk(DAQmxSetBufOutputBufSize(taskHandleDig, bufferSize));
/*********************************************/ /*/ DAQmx Write Code /*********************************************/
DAQmxErrChk(DAQmxWriteCtrTicksScalar(taskHandleDig, 0, timeout, hiTicks, lowTicks, NULL));
/*********************************************/ /*/ DAQmx Start Code /*********************************************/
DAQmxErrChk(DAQmxStartTask(taskHandleAna)); DAQmxErrChk(DAQmxStartTask(taskHandleDig));
printf("Task started, waiting for trigger...\n");
/*********************************************/ /*/ DAQmx Read Code /*********************************************/
double* dataAna = new double[nSpCh];
int32 numReadAna = 0;
int errCode = DAQmxReadAnalogF64(taskHandleAna, -1, timeout, DAQmx_Val_GroupByChannel, dataAna, nSpCh, &numReadAna, NULL);
printf("Acquired %d analog samples\n",numReadAna);
if (numReadAna) {
    unsigned nPts = (numReadAna < hiTicks)? numReadAna : hiTicks;
   for (unsigned n = 0; n < nPts; ++n) {
         printf("%6.3f ", dataAna[n]);
    printf("\n");
delete [] dataAna;
DAQmxErrChk(errCode);
Error:
if( DAQmxFailed(error) )   DAQmxGetExtendedErrorInfo(errBuff,2048);
if( taskHandleDig!=0 && taskHandleAna!=0 ) {
/*********************************************/   /*/ DAQmx Stop Code   /*********************************************/
    DAQmxStopTask(taskHandleDig);
    DAQmxClearTask(taskHandleDig);
    DAQmxStopTask(taskHandleAna);
    DAQmxClearTask(taskHandleAna);
if( DAQmxFailed(error) )   printf("DAQmx Error: %s\n",errBuff);
printf("End of program, press Enter key to quit\n");
getchar();
return 0;
Attachments:
Correlated DIO AI_Sample_Clock Dig Start.c ‏6 KB

Best way to synchronize multiple FPGAs

I have multiple PXI-7833R FPGAs and I need all of the AIs to be sampled at the same times (across all FPGAs). As I sample all of the individual AI channels, I buffer the data (write to DMA), scan it and check for a user defined trigger in a different loop. Once I discover this in one channel, I save the data from all FPGAs. In terms of synchronizing the sampling, I had begun, from one FPGA, to send a signal over the PXI trigger line to tell the others to sample, but I assume this does not guarantee synchronization. If I base all of the separate FPGA VIs off of the PXI clock, how do I synchronize the loops to sample at the same clock times?
Thanks
Solved!
Go to Solution.

Hi,
Well, if it's not very timecritical you could pass messages through the host, thats right.
Another way, which is quite hard to implement though, would be to use the other available pxi trigger lines to send messages directly from one FPGA to the other. You would need something like a handshaking, a kind of master who directs which slave is allowed to send, a kind of clock for synchronization and so on.
I cannot give you detailed information, since I never did that by myself, but I know other projects where this works quite good.
Maybe another forums user can give you some better advice.
Thanks,
Christian

Script for synchronizing the clock with Domain Controller

Hi Everyone,
In our environment, we have Mac machines which are joined to window's domain. Once in while machine will not log on to domain because the OS clock had a different time than the domain controller and sooner you fix the clock, machine will start communicating with domain controller.
I was wondering if there is an easier way to do this using script which can run every few hours to force the OS clock to synchronize with the domain controller.
Thanks,

You don't need an Applescript to do that.
Enable the NTP server on the Windows Domain Controller (perhaps start here: http://technet.microsoft.com/en-us/library/cc773013.aspx).
Then setup the Macs to use NTP (Network Time) to sync to the domain controller.

Timebase synchronization issue with PXI 6713

As indicated in another post, I need to use a common timebase to all cards within my PXI chassis to synchronize my acquisition/generation DAQmx tasks.
I performed that successfully by setting timebases of all boards from the 20MHz timebase of a E-series DAQ board.
I have another system setup where I do not have E-series DAQ boards but only M-series. In this case, I tried to synchronize all the cards with the 10MhzRefClock of a PXI 6254 board. It seemed to work correctly, until I looked at the analog output signal of one PXI 6713 board.
This device has 8 analog outputs, I performed as for DAQ boards : I set its timebase to a 10Mhz clock. When I have at least two outputs with hardware timing I observe on scope really weird signal : nothing is visible when all outputs are left to zero volt, but when another voltage is set, the output toggles at very high frequency between 0V and the setting voltage. When two outputs are set to values different from zero, the output also toggles but between these two settings...
I thought it was a board failure, but I checked with another PXI 6713 and the behavior is the same.
When synchronizing with a 20MHz timebase, everything is fine, but 10MHz clearly shows this issue. I checked the 6713 documentation, and it seems possible to use a timebase different than 20MHz.
I attached a VI that illustrates the problem : I create a DAQmx task containing 2 AOs, where 10MHz timebase is taken from a M-series DAQ board. A hardware timed single point timing is configured and outputs are updated in a while loop. If you connect a scope to the first analog output, you will see the phenomenon.
Everyting is fine when you select a 20MHz clock as a timebase. 10MHz leads to this issue. I also tried to synchronize through PXI backplane clock (i.e. /6259_1/PXI_Clk10) but it leads to the same problem.
Please note that using the same 10MHz synchronization on DAQ cards (PXI 6040E, 6071E, 6254, 6259...) for AO works perfectly. I only encountered this problem with PXI 6713 board.
Message Edité par Inpriser le 08-18-2006 02:54 AM
Attachments:
Synchro 10 MHz PXI AO.vi ‏34 KB

Inpriser,
You wanted to use the PXI 10MHz clock to synchronize to 6713s using the PXI capabilities. I’m afraid that since the AO series doesn't have a PLL, you won't be able to use the PXI 10 clock.
I made a few search and found this:
“Neither the 6713 nor any of the AO series support PLL synchronization. However, the M-Series does, though in that case you are limited to a smaller number of analog outputs. Regardless, the best option is using an Arb or other card that can use the Star Trigger, or an m-series device with PLL synchronization capabilities.”
For more info’s about how to deal with PXI and PLL, please check this forum:
http://forums.ni.com/ni/board/message?board.id=170&message.id=11986&requireLogin=False
I’m sorry to disappoint you, hoping you’ll manage to deal with that,
Regards,
BRAUD Jean-Philippe
Field Sales Engineer - Nord et Centre France
LabVIEW Certified Developper

CFP clock loose synchronization

Similar Messages

Maybe you are looking for