I am trying to use NI-Sync to create a clock to then send triggers to an output. From looking at the example Here , it should work. However, I am getting the error of "Property Node (arg 1) in niSync Create Clock (Frequency).vi:6780001->triggerMultiplySandbox.vi <ERR>This operation requires a feature that is not supported." So it looks like its erroring at the create Clock.vi. I believe I am following all the rules, so it should work? See attached for my vi.I've set the frequency from 10 KHz to 1 MHz to see if its maybe a frequency issue. The coerced freq is always inf

Hi, The onboard clock gen of the PXIe-6674T is a DDS and which does not support niSync Create Clock.vi to generate clocks. To generate a clock with the PXIe-6674T, use the DDS Properties>>DDS Frequency property node then route the DDS to the designed terminal. You can route the DDS directly to some terminals like ClkOut, PXI_LVDS#, and PXIe-DStarA#. For other terminals, you'll need to set the synchronization clock to the DDS and then route the synchronization clock as the source. For example to generate a specific frequency on PXI_Trig0 with the PXIe-6674T, you would take the following steps: Set property DDS Properties>>DDS Frequency to the frequency Set property Synchronization Clock Properties>>Synchronization Clock Source (PXI_Trig, PXI_Star, PXIe_DStarB) to DDS Route Synchronization Clock (Full Speed)/SyncClkFullSpeed to PXI_Trig0 In the PXIe-6674T User Manual, you can find a summary of all the possible routes in Figure 7. Sources and Destinations for PXIe-6674T Signal Routing Operations. Also, I'd recommend leaving the PXIe-6674T in the system timing slot of your chassis which is slot 4 for the PXIe-1082. For PXI-1 chassis, the system timing slot was often slot 2, but for PXI Express chassis the system timing slot can vary based on chassis model. I hope this helps,-Tyler

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

NI Sync Create Clock Issue

Solved!

I believe, that I have seen in the manual, that 50 MHz is the threshold between fast and slow clock speeds. I guess it is hard to maintain shape of the multi frequency signal (rectangle) at high speeds and they switch to mono frequency (sine).

Message 11 of 11

(466 Views)

LabVIEW

NI Sync Create Clock Issue

Re: NI Sync Create Clock Issue