Meinberg LANTIME IMS-LNO
The LNO is a 10 MHz generator card. It provides sinewave signals with low phase noise at four outputs. It has a microprocessor system that monitors the output signals and generates status signals for the management system. It is intended for use with modular IMS systems, the M900 time server platform and GPS-based 3U housing.
A high-quality oscillator is synchronized by the 10 MHz signal of the external reference clock and thus provides the high-precision clock for the IMS-LNO. The microprocessor monitors the state of the PLL synchronization circuit and the warm-up phase of the oscillator and only enables the outputs after a successful phase synchronization. This state is also indicated by the four status LEDs (transition from red to green). In the phase synchronous state, the output level of the four outputs is monitored and any errors are signaled by the assigned red LED.
The LNO module is compatible with all systems of the IMS family. It can also be used in any slot (MRI, ESI, I/O).
About
Version Info
| Range | Key Features | Based On | System Impact |
|---|---|---|---|
| 1.0.0.x | Initial version | - | Minimum required DataMiner version is 10.0.0.0 - 9118 due to SLManagedScripting C#7 syntax. |
| 1.0.1.x [SLC Main] | Compatible with mbgNMS 1.1.x. | 1.0.0.1 | - |
Product Info
| Range | Supported Firmware | REST API Version | Supported Types |
|---|---|---|---|
| 1.0.0.x | 7.04.x | 8.x.y | LNO180 |
| 1.0.1.x | 7.04.x | 8.x.y | LNO180 |
System Info
| Range | DCF Integration | Cassandra Compliant | Linked Components |
|---|---|---|---|
| 1.0.0.x | No | Yes | DataMiner connector: Meinberg LANTIME Modular |
| 1.0.1.x | No | Yes | DataMiner connector: Meinberg LANTIME Modular |
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.