Saves the database to a FIBEX file.


icon

Inputs/Outputs

  • cgenclassrntag.png database in —

    database in is the I/O name of the database.

  • cpath.png filepath (empty) —

    filepath contains the pathname to the FIBEX file or is empty (saves to the original filepath).

  • cerrcodeclst.png error in (no error) —

    The error in cluster can accept error information wired from VIs previously called. Use this information to decide if any functionality should be bypassed in the event of errors from other VIs. The pop-up option Explain Error (or Explain Warning) gives more information about the error displayed.

  • igenclassrntag.png database out —

    database out is a copy of the database in parameter. You can use this parameter to wire the VI to subsequent VIs.

  • ierrcodeclst.png error out —

    The error out cluster passes error or warning information out of a VI to be used by other VIs. The pop-up option Explain Error (or Explain Warning) gives more information about the error displayed.

    • Description

    This VI saves the XNET database current state to a FIBEX 3.1.1 file. The file extension must be .xml. If the target file exists, it is overwritten.

    XNET saves to the FIBEX 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.

    If filepath is empty, the file is saved to the same FIBEX file specified when opened. If opened as a file path, it uses that file path. If opened as an alias, it uses the file path registered for that alias.

    Saving a database is not supported in LabVIEW Real-Time, but you can deploy and use a database saved on Windows in LabVIEW Real-Time (refer to the XNET Database Deploy VI).