Articles in this section

Setting up Kepware

Kepware IoT Gateway is a common way of sending data to Factbird. Many of our customers already have Kepware installed and only need to add the IoT gateway module. Kepware is to be installed and maintained on your end. This page shows how to get Kepware to work with Factbird.

 

For detailed information, see the technical guide: Kepware Technical Guide 

Installing

The following software is needed:

  • KEPServerEX setup program
  • Java runtime (32-bit)

Kepware IoT Gateway

Start the KEPServerEX setup program. Use the version already installed on the server, alternatively, upgrade to a newer version.

Untitled (5).png

Modify the installation:

Untitled (6).png

Add IoT gateway:

Untitled (7).png

Press Next and complete the installation.

Java runtime

The Kepware IoT component requires Java. As Kepware is a 32-bit program, the Java version must also be 32-bit. Download the Windows Offline version from:

https://www.java.com/en/download/manual.jsp

Install or update Java

Untitled (8).png

Adding a connection to Factbird Cloud

Needed information:

  • Information from this guide
  • unique id provided by Factbird
  • certificate provided by Factbird

Start the KEPServer 6 Configuration

Add a new Iot Gateway agent:

Untitled (9).png

Name the agent with a unique name and set type to “MQTT Client”.

Untitled (10).png

Set the URL to: ssl://a3f8k0ccx04zas-ats.iot.eu-west-1.amazonaws.com:8883

 

💡If your company is using a private cloud solution, the URL will differ. Please submit a support request for the correct URL.

 

Set the topic to: plc/input/<uuid>, where <uuid> is the unique ID for the agent provided by Factbird.

Untitled (11).png

Set the Client ID to: <uuid>, where <uuid> is the unique ID for the agent provided by Factbird.

Untitled (11).png

Select Properties for the MQTT agent, and select the security tab.

Change the TLS version to 1.2.

Change Client Certificate to: Enabled.

Untitled (13).png

Adding tags to be published to Factbird

Add the items the agent should publish.

 

Here, a simulation tag is selected for testing.

Untitled (14).png

Note: For tags where you want to detect stops, select to publish on every scan and set the scan rate to 5000mS or below.

Untitled (15).png

Adding a security certificate to the connection

On the Kepware tray menu, select Settings…

Untitled (16).png

Under MQTT agent, select Manage certificates.

Untitled (17).png

HImport New Certificate.

Untitled (18).png

Select the certificate <certid>-certificate.pem.crt file provided by Factbird:

Untitled (19).png

Select the private key <certid>-private.pem.key file provided by Factbird:

Untitled (20).png

A password is not needed.

Untitled (21).png

Confirmation.

Untitled (22).png

 

 

Adding Amazon root certificate

Note: this is only for older Windows servers that do not have the Amazon certificate included:  Amazon root certificate It can normally be skipped.

 

 

Testing

Reinitialize the Kepware runtime to activate the configuration.

Untitled (23).png

Confirm the IoT Gateway starts without any errors:

Untitled (24).png

 

Was this article helpful?
0 out of 0 found this helpful