LDX100 Series – NativeIP configuration using USB files

Overview

Selected models within the LDX100 camera series support the NativeIP feature. This feature, available as a licensed option, provides IP connectivity directly from the camera head without the need for a traditional base station like the XCU UXF.

When using a traditional setup with XCU, the IP connectivity configuration is managed by the XCU and stored in its cradle. When swapping cameras connected to an XCU, this IP configuration remains unaffected. This ensures that the signals to and from a newly installed camera are automatically available on the IP network in the exactly same way as with the original camera it replaced.

With the NativeIP option, cameras are directly connected to an IP network. This can make it challenging to replace cameras in an easy way, because the complete IP configuration is managed by the camera itself. Especially in the unwanted situation that a camera fails just before the start of a production, there is a need to have a replacement camera up and running as quickly as possible. This requires the replacement camera to have exactly the same IP configuration as the camera that was replaced.

To make replacement more convenient, the camera software now offers the possibility to backup and restore all NativeIP related settings using a configuration file on a USB storage device. Restoring a saved configuration is possible immediately when the camera is turned on before the camera accesses the connected IP network with its original settings. This prevents the unwanted situation and risks of network problems due to incorrect IP settings.

In addition, these configuration files can also accommodate other use cases, where (re)configuration of the NativeIP settings is desired.

NATIVEIP CONFIGURATION FILES

NativeIP configuration files contain all settings related to the NativeIP operation for one or more cameras. A single configuration file can host (or contain) multiple separate configurations for each camera used in a production.
Example:

• Config-File: “OB Van 4” contains settings for:

  • Cam 1 – Settings
  • Cam 2 – Settings
  • Cam 3 – Settings
  • …

• Config-File: “Studio 5” contains settings for:

  • Cam 1 – Settings

  • Cam 2 – Settings

  • Cam 3 – Settings

  • …

The configuration settings for each camera include all settings related to IP network, video, audio, intercom, locking and control connectivity.

A brief non-exhaustive overview:

Configuration files are defined as an open JSON-based file format. This enables users to create custom configuration files with only the settings needed for their productions.

Notes:
• The option to save/restore configuration files is only available with an active NativeIP license
• The camera software will search, read and write configuration files in the \LDX\Boot subdirectory of the USB storage device

SAVING CONFIGURATIONS

NativeIP configuration files can be saved to a USB storage device from the Camera menu:

• Ensure a USB storage device is present

• Ensure the camera User Level is set to “Setup”

• Go to Menu | Configuration | Files | Config Files

  

• Select “Store” to get access to the Store options

  

There are 4 different ways to store a config file:

• Quick save: Creates a new file with auto-generated file name, based on the actual camera number, date and time settings.
• New file: Creates a new file with supplied file name and configuration name
• Append: Adds a new configuration with supplied name to an existing file
• Overwrite: Overwrites an existing configuration in an existing file.

All configuration files will be saved in the \LDX\Boot directory of the USB-storage device. This location is the same as where the camera will search for existing configuration files.

QUICK SAVE

The fastest way to save the current NativeIP configuration to file is using the “Quick Save” option.

When using “Quick Save”, automatically a new file will be created with an auto-generated file name, based on the current camera number, date and time.

For example: A file named “Cam01_240927_1327” will be created for Camera 1 on September 27, 2024 at 13:27. This file will contain 1 configuration named “Cam01”.

NEW FILE

The “New File” option will save the current NativeIP configuration to a new file. A new file name must be supplied by the user. The configuration name is filled by default with the current camera number, but can be altered when needed.

• Select “File” to enter a new file name. The menu will show <Edit> as placeholder when no filename has been entered yet.

• When desired, select “Cfg” to change the proposed configuration name based on the current camera number.

• Select “Save config” to save the new file to USB storage

  

When successfully saved, a “Saved” message will be shown as confirmation. In case a file with the chosen name already exists, a “Failed: Already exists” message will be shown.

Note: The “Save config” option will be blocked until a new file name has been entered.

APPEND TO EXISTING FILE

The current NativeIP configuration can added to an existing configuration file with the “Append” option. A chosen configuration file will be extended with an additional camera configuration containing the current camera settings.

• Select “File” to choose an existing file from the USB storage device

• When desired, select “Cfg” to change the default proposed configuration name based on the current camera number

• Select “Save config” to append the configuration to the chosen file

  

When successfully saved, a “Saved” message will be shown as confirmation. In case the chosen file already contains an existing configuration with the same name, a “Failed: Already exists” message will be shown.

Note: The “Save config” option will be blocked until an existing file has been selected.

OVERWRITE

With the “Overwrite” option it is possible to overwrite configuration data stored within an existing file on the USB storage device.

• Select “File” to choose an existing file from the USB storage device

• Select “Cfg” to choose the existing configuration which should be overwritten. In case the selected file contains just a single configuration, it will be automatically selected.

• Select “Save config” to overwrite the configuration within the selected file.

  

When successfully saved, a “Saved” message will be shown as confirmation. In case of any failure, a “Failed” message will be shown.

Note: The “Save config” option will be blocked until both the existing file and configuration have been selected.

RESTORING A CONFIGURATION UPON STARTUP

Saved NativeIP configurations are useful to reconfigure any random NativeIP capable camera to become part of a production setup or when a swap of an existing camera is needed.

To prevent the new camera accessing the IP network with its previous (unknown) configuration settings, it is possible to restore a saved configuration directly upon camera start-up.
When the camera during the boot up detects an USB storage device with configuration files present, the start-up will be interrupted and the SFP network interface will be kept disabled. The camera automatically shows the “Boot Config” menu, enabling the user to restore a previously saved NativeIP configuration from the actual present USB storage device. When the user exits this “Boot config” menu, the camera will continue its normal operation using the restored configuration settings.

Required steps:

• Ensure the desired configuration file is stored on a USB storage device. The file must be located within the \LDX\Boot subdirectory.

• Ensure a viewfinder is connected to access the camera menu (or an SDI/HDMI monitor showing the viewfinder video with camera menu text)

• Ensure the new camera is switched off

• Insert the USB storage device into the camera USB port

• Power-on the camera

• Wait until the camera is started and the “Boot Config” menu is shown

Note: While this “Boot Config” menu is shown, the SFP network interfaces are disabled

• Select “Config Files”

  

  

• Select “File” to choose the desired configuration file available on the USB storage device
  Select “Cfg” to choose the desired configuration for this camera. When the file only contains a single configuration, it will automatically be selected upon file selection.

• Select “Load Config” to restore the selected configuration settings

  

• When successfully restored, a “Config: Done” message will be shown

• Go back to the “Boot Config” page and select “Exit”

• The camera will continue with its normal operation using the restored configuration settings

Note:

• The RJ45 “C2IP” connector on the back of the camera will remain active while the “Boot config” menu is shown. It will use the C2IP settings as configured when the camera was previously powered off, until new settings are restored from a selected configuration file.
• When exiting the “Boot Config” menu without restoring a configuration from file, the camera will use the configuration as it was active when the camera was previously powered off.

RESTORING AFTER STARTUP

It is also possible to restore a NativeIP configuration while the camera is already operational:

• Ensure a USB storage device is present

• Ensure the camera User Level is set to “Setup”

• Go to Menu | Configuration | Files | Config Files

• Select “Recall” to get access to the Recall menu

• Select “File” to choose the desired configuration file available on the USB storage device

  Select “Cfg” to choose the desired configuration for this camera. When the file only contains a single configuration, it will automatically be selected upon file selection.

• Select “Load Config” to restore the selected configuration settings

• When successfully restored, a “Config: Done” message will be shown

The restored configuration will be instantly active.

CONFIGURATION FILE FORMAT

The NativeIP configuration files are using an open JSON-based format, enabling users to create their own custom configuration files. A JSON schema file is available defining the file structure and all possible options and values of the NativeIP configuration settings.

• NativeIP configuration files will use the .ldxcfg file extension.

• The camera software will save and restore configuration files from the \LDX\Boot subdirectory on a USB storage device.

• Like with any other JSON object definition, the order in which JSON object fields are defined is not relevant.

• Unless indicated as required within the JSON schema, custom configuration files may contain a limited subset of the available NativeIP configuration settings.

• When a limited configuration subset is restored, all missing configuration settings will retain their values as currently configured.

• A single configuration file can contain multiple NativeIP configurations for different cameras.

• Configuration names MUST be unique within the same file.

• Although kept to a minimum, there are several logical dependencies between individual configuration settings which can cause settings to be ignored when restoring a manually created/modified configuration file. These dependencies are identical to availability of corresponding camera menu items.
  Some examples:

  • Manually set IP addresses are ignored when the interface is configured to “DHCP”
  • ST2110-22 protocol selections are not accepted when JPEG XS mode is “Off”
  • High-speed phase video streams can only be enabled when the system videomode is set accordingly.

When interested in defining your own custom configuration files, contact your Grass Valley Cameras support representative to retrieve the JSON schema and example files.

USE CASES

Below several example use cases where the use of the NativeIP configuration files might be convenient:

• Camera exchange: As mentioned within the introduction, saving the NativeIP configuration from one camera and restoring it in another camera makes it easy to swap cameras when needed.

• Camera preparation: When further camera configuration is done from external applications or orchestration tools, a (minimal) custom NativeIP configuration file containing for example only the camera mode, SFP and C2IP settings can be used as a common preparation for each camera to be used within that environment.

• Temporary use within another network environment: When the camera needs to be examined/tested/upgraded in a separate (test) environment, it is now possible to save the original camera configuration and restore it when the camera returns to its origin. In the meantime, configuration can be changed or restored from another saved configuration which matches the temporary (test) environment.