MCF and MFS Files

MCF Files

When you save your applet configuration, the configuration data are saved to file. The configuration file has the file extension *.mcf. (MCF = microEnable Configuration File)

The MCF file is saved in text format, so that you can change the settings of individual parameters not only via microDisplay X or API, but also directly in this file.

The MCF file contains:

Camera Configuration in Separate XML File

 

MCF files do not contain the camera configuration. You can save the camera configuration in a separate *.xml file. The MCF file only contains the applet configuration.

   

MFS Files

The configuration of an applet may contain field parameters, for example, LUTs. These field parameters are not directly stored in the MCF file, but in a separate file with file extension *.mfs. (MFS = microEnable Field Storage)

You never need to handle the MFS file directly:

Standard Acquisition Applets

 

All Standard Acquisition Applets contain field parameters. Thus, each time you save the configuration of a Standard Acquisition Applet, two files are created, the *.mcf file and the *.mfs file. However, you do not need to handle the *.mfs file separately, as it is always automatically created/loaded when you save/load the *.mfs file.

The following arrays (field parameters) are part of all or some Standard Acquisition Applets:

  • LUTs
  • KneeLUTs
  • ChannelCurrent (ironman CXP boards only)
  • ChannelVoltage (ironman CXP boards only)
  • PoCXPStatePort_x (marathon CXP boards only)
  • PoCXPCurrentPort_x (marathon CXP boards only)
  • PoCXPVoltagePort_x (marathon CXP boards only)
   

 

Why MFS Files?

 

Saving all field data into a separate file keeps the applet configuration file MCF clear and allows for downward compatibility.