Table Of Contents

Repeat Host Driven Synchronization (G Dataflow)

Last Modified: April 2, 2018

Use this flavor of synchronization in conjunction with Host Align on the FPGA. When this node finishes, the FPGAs are synchronized. Use this version of synchronization to return to a known synchronization state from a previous run. It is possible for the FPGAs to not be synchronized if the synchronization data in is incorrect. Synchronization data is also valid only for a given system configuration. If the location of the USRP RIO device, chassis, or slot changes, synchronization data may not be valid.

connector_pane_image
datatype_icon

niusrprio sessions in

Objects created by the Open node and used as the session handles for the USRP RIO nodes.

datatype_icon

synchronization data in valid

A flag to use the values from a previous synchronization run (synchronization data in) to return the FPGAs to that synchronization state.

datatype_icon

synchronize data in

Returns the FPGAs to the previous synchronization state using synchronization data from that synchronization run.

datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

sync.cptr.period

The period (in clocks) of the common periodic time reference (CPTR). The default value automatically sets the CPTR period to 10 MHz. The CPTR period controls the rate at which synchronized signals are realized. When you use FPGA Align, the CPTR period must be the same as the Reference Clock period. The sync.cptr.period must be set to the ratio of the clock-driven loop (CDL) rate that the Align node is in to the common reference rate. For example, the CPTR period must be 12 if using the GPS for the Reference Clock, and the Data Clock for the CDL Clock (120 MHz/10 MHz). When you use Host Align, this value is configurable. The maximum value is 63. The minimum value for the sync.cptr.period must be big enough to ensure transmission across the sync.fpga io line. Refer to the specifications for the FPGA I/O line chosen. For example, if the FPGA I/O line has a maximum propagation delay of 50 ns, then the minimum value would be 6. Because the period of the 120 MHz Data Clock is ~8.333 ns, it would require 6 clocks to exceed 50 ns. NI does not recommend changing the CPTR period while running. Alignment must be re-run if the CPTR period is changed.

datatype_icon

niusrprio sessions out

niUsrpRio sessions used in all subsequent USRP RIO host nodes.

datatype_icon

synchronization data out

Synchronization data from the completed synchronization run that can be used to return the FPGAs to that synchronization state. The data is valid only if the FPGAs were successfully synchronized with no output error.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

Web Server: Not supported in VIs that run in a web application


Recently Viewed Topics