1. Home
  2. Docs
  3. Documentation
  4. Integrations
  5. Crimson 3.1 & 3.2

Crimson 3.1 & 3.2

In this article we are connecting the Crimson 3.1 / 3.2 programming software to Nimbus808 solution platform using MQTT.


crimson 3.1 / 3.2 main_pic

Crimson 3.1 / 3.2 is Red Lion’s powerful next-generation programming software for CR1000, CR3000 HMIs, Graphite® HMIs & Graphite Controllers, and E3 I/O™ modules

The objective of this guide is to explain how to set up Crimson 3.1 devices to stream data to Nimbus808 over MQTT.


Requirements:

  1. Nimbus808 Account
  2. Crimson 3.2 or 3.1 programming software

Crimson 3.1 / 3.2 – Configuration

This guide assumes your device utilizing Crimson 3.2 or 3.1 programming software has been configured and is already connected to the internet.

Click the “Communications” tab in the Navigation Pane section.

crimson 3.1 / 3.2 navigation pane

Click “Generic MQTT”

Enable the Generic MQTT Agent, and adjust the MQTT Servers’ Host Name 1 to be the Nimbus808 instance.

crimson 3.1 / 3.2 generic mqtt

Note: You may have up to 4 different Generic MQTT connections set to the same broke with different various publication / subscription topics.


Sending and Receiving Data to Nimbus808

Crimson 3.1 / 3.2 utilizes Tag Sets to program which tags will be sent over to nimbus at the MQTT Servers Publication or Subscription topics.

Tag Set 1

tag set 1

Tag Set 2

tag set 2

Download the project file to your Crimson device utilizing Crimson 3.1 / 3.2 programming software.


Verify results on your Nimbus808 dashboard

Data is transmitted and received under the respective topics. For example, outbound data is published through dev1, while inbound updates are delivered through dev2. In this way, distinctions are made between communication directions, and tag data is made manageable and interpretable.

Publish
dev1 = {“Tag1”:123}

Subscription
dev2 = {“Tag1”:123}


Have questions? Contact us for help