Table of Contents

Meinberg LANTIME IMS-MRI API V10

If an application requires the use of external synchronization sources instead of radio/GNSS signals, an MRI card enables the installed clock module to synchronize to 1 PPS, 10 MHz, DCLS, and AM time codes (IRIG B, AFNOR, IEEE 1344, or C37.188).

Each MRI card is dedicated to one clock model. If a redundant solution requires external synchronization input for both clock modules, two MRI cards have to be installed.

The MRI card is available with 4x BNC connectors. Optionally, the MRI input card is also available with fiber optical inputs.

About

Version Info

Range Key Features Based On System Impact
1.0.0.x [SLC Main] Initial version. - Minimum required DataMiner version is 10.0.0.0 - 9118 due to SLManagedScripting C#7 syntax.

Product Info

Range Supported Firmware REST API Version Supported Types
1.0.0.x 7.06.x
7.08.x
10.x.y
16.x.y
MRI

System Info

Range DCF Integration Cassandra Compliant Linked Components
1.0.0.x No Yes DataMiner connector: Meinberg LANTIME Modular API V10

Configuration

Connections

HTTP Main Connection

This connector uses an HTTP connection and requires the following input during element creation:

HTTP CONNECTION:

  • IP address/host: The polling IP or URL of the destination.
  • IP port: The IP port of the destination.
  • Bus address: If the proxy server has to be bypassed, specify bypassproxy.

Initialization

Slot ID

The DataMiner element will not know which slot it needs to represent until the slot ID has been provided.

On the General page, the slot ID must be configured.

REST API

The HTTP communication uses a REST API, which needs to be enabled.

On the device's web interface, make sure the Enable REST API option is selected under the general settings on the System page.

HTTP Credentials

The HTTP communication will not be up and running until the necessary HTTP credentials have been provided.

On the Credentials page of the element, the user name and password must be configured.

Web Interface

The web interface is only accessible when the client machine has network access to the product.

How to Use

REST (Representational State Transfer) calls are used to retrieve the device information.

HTTP Communication

On the HTTP Communication page, you can track the HTTP sessions used for communicating with the device.

This makes it possible to follow the communication flow and provides some useful statistics, e.g. request time, response time, time span (RTT), etc.

  • HTTP Sessions State: If you enable this setting, the active HTTP sessions will be tracked.
  • HTTP Sessions Max Count: This determines the maximum number of HTTP sessions that will be tracked.