Litmus Customer Support

Each of our technical support technicians has extensive experience in edge computing and IIoT. We are prepared to assist OT or IT departments with expertise in legacy equipment, PLCs, dockers, databases, IT networking, integrations, and more.

Our customer support surveys prove an extremely high level of customer satisfaction in our industry. Litmus customers report 95% satisfaction with our technical support response time, problem-solving, and ability to help them bring projects to completion.

Instead of waiting for a call, we monitor our infrastructure continuously to catch any potential threats to uptime or performance. Part of our team is dedicated to proactively responding to any issues that may arise with Litmus Edge or Litmus Edge Manager.

Litmus Edge has a component called Integrations consisting of northbound connectors. Users can use Flows to parse the data as per their required format and then publish it to our internal message broker which can then be used to send data to Microsoft Azure. Users can also send the data directly to Azure in Litmus Edge raw format with a single click.

Currently templates exist for PLC configuration and flows. Users can select a mix and match of both, and create as many templates as they choose. These templates can then be uploaded at an admin level in Litmus Edge Manager so that they are available to deploy at all facilities, or at a company level.

First select `Applications` from the sidebar. Next select `Marketplace` from the applications menu. Select the appropriate container.

Flows by default does not save historical data. If you would like to save historical data, please create a database container within the Marketplace that will save the data.

The most likely cause of this issue is due to the use of custom nodes. If a custom node was used in your flow, you will need to download and reinstall the custom nodes. Custom nodes will not be included in backups.

We rely on the security offered by the docker. For deployment, you can use certificate-based authentication to add a private registry and then use images on the registry to launch containers.