Table Of Contents

XNET Database Export (G Dataflow)

    Last Modified: March 13, 2017

    Exports a cluster from the open database to a file in a specific format.


    cluster in

    The I/O name of the cluster.



    An input that contains the pathname to the file to be created.


    error in

    Error conditions that occur before this node runs. The node responds to this input according to standard error behavior.

    Default: No error


    cluster out

    A copy of the cluster in parameter. You can use this output to wire the node to subsequent nodes.


    error out

    Error information. The node produces this output according to standard error behavior.


    This node exports a cluster from an XNET database to a specific file format. A CAN cluster is exported as CANdb++ database (.dbc). A LIN cluster is exported as a LIN database file (.ldf). A FlexRay cluster cannot be exported and returns an error. If the target file exists, it is overwritten. The filepath parameter is required; you cannot accidentally overwrite the original file by specifying an empty filepath.

    XNET saves to the file only features that XNET sessions use to communicate on the network. If the original file was created using non-XNET software, the target file may be missing details from the original file. For example, NI-XNET supports only linear scaling. If the original FIBEX file used a rational equation that cannot be expressed as a linear scaling, XNET converts this to a linear scaling with factor 1.0 and offset 0.0.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Supported

    Recently Viewed Topics