<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs.optrix.com.au/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>ARDI Documentation - distribute</title>
        <description></description>
        <link>https://docs.optrix.com.au/</link>
        <lastBuildDate>Fri, 29 May 2026 20:05:51 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://docs.optrix.com.au/_media/wiki:dokuwiki.svg</url>
            <title>ARDI Documentation</title>
            <link>https://docs.optrix.com.au/</link>
        </image>
        <item>
            <title>Configuring Live Data Distribution</title>
            <link>https://docs.optrix.com.au/distribute:configuring_live_data_distribution</link>
            <description>Configuring Live Data Distribution

To distribute live data to other locations, create a replication.json file in your site folder.

The site folder is located in your ARDI installation directory, under /web/sites/.

This file should contain JSON data similar to the example below</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 28 May 2026 04:37:06 +0000</pubDate>
        </item>
        <item>
            <title>Creating Your Own Distributor</title>
            <link>https://docs.optrix.com.au/distribute:creating_your_own_distributor</link>
            <description>Creating Your Own Distributor

Distributor files can be found in your Python library directory, under /ardi/consolidator.

Distribution modules are named &#039;dist_xxx&#039;, where &#039;xxx&#039; is the type name used in the configuration file.

Installations will include a dist_custom</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 03:09:34 +0000</pubDate>
        </item>
        <item>
            <title>InfluxDB</title>
            <link>https://docs.optrix.com.au/distribute:influx</link>
            <description>InfluxDB

This type of distribution sends incoming data to an InfluxDB server to be recorded.

Type Name

The type name to use in your configuration is influx.

Configuration

The following configuration options are accepted...
NameNotesPurposehostnameRequiredThe full path to your</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 01:35:30 +0000</pubDate>
        </item>
        <item>
            <title>Memcache</title>
            <link>https://docs.optrix.com.au/distribute:memcache</link>
            <description>Memcache

This type of distribution sends incoming data to a Memcache server, where it is held in an in-memory data store.

Type Name

The type name to use in your configuration is memcache.

Configuration

The following configuration options are accepted...
Name</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 03:07:18 +0000</pubDate>
        </item>
        <item>
            <title>MQTT Versions</title>
            <link>https://docs.optrix.com.au/distribute:mqtt_versions</link>
            <description>MQTT Versions

The Distribution addon supports two different ways of sending data to MQTT servers.

The point-based method sends a single MQTT message for each individual point of information. Every temperature, pressure, mode and status has it&#039;s own distinct MQTT message.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 03 May 2026 23:33:34 +0000</pubDate>
        </item>
        <item>
            <title>MQTT Per-Point Topics</title>
            <link>https://docs.optrix.com.au/distribute:mqtt</link>
            <description>MQTT Per-Point Topics

This type of distribution sends incoming data to your MQTT server, with one topic per point of live data.

This means that there will be a large number of individual topics in your MQTT hierarchy.

Each message simply contains the raw value of that point of information.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 03:07:28 +0000</pubDate>
        </item>
        <item>
            <title>MQTT Event Notifications</title>
            <link>https://docs.optrix.com.au/distribute:mqttev</link>
            <description>MQTT Event Notifications

This type of distribution sends incoming data to your MQTT server, with one topic per property. 

However, rather than being a live stream of updates, these topics are only sent updates when a significant change happens.

For discrete values (on/off signals, statuses, text values etc.), messages will be sent with any change. This reflects machines turning on/off, doors closing etc.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 28 May 2026 03:46:50 +0000</pubDate>
        </item>
        <item>
            <title>MQTT Per-Asset Topics</title>
            <link>https://docs.optrix.com.au/distribute:mqttob</link>
            <description>MQTT Per-Asset Topics

This type of distribution sends incoming data to your MQTT server, with one topic per ARDI asset that has live data.

This will consolidate all updates about an asset into a single message, reducing the total size of the MQTT namespace and reducing the number of total messages sent.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 03:07:44 +0000</pubDate>
        </item>
        <item>
            <title>Pre-Built Distributors</title>
            <link>https://docs.optrix.com.au/distribute:pre-built_distributors</link>
            <description>Pre-Built Distributors

Below are the list of distributor modules that are included with ARDI 2026 and above.

InfluxDB 

Memcache 

MQTT Per-Point Topics 

MQTT Event Notifications 

MQTT Per-Asset Topics 

Redis 

TimescaleDB 

Webhook</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 28 May 2026 04:49:02 +0000</pubDate>
        </item>
        <item>
            <title>Memcache</title>
            <link>https://docs.optrix.com.au/distribute:redis</link>
            <description>Memcache

This type of distribution sends incoming data to a REDIS server, where it is held in an in-memory data store that can be subscribed to.

Type Name

The type name to use in your configuration is redis.

Configuration

The following configuration options are accepted</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 03:06:55 +0000</pubDate>
        </item>
        <item>
            <title>Live Data Distribution</title>
            <link>https://docs.optrix.com.au/distribute:start</link>
            <description>Live Data Distribution

ARDIs Live Data Distribution functions let you push live data to other platforms as it arrives.

It&#039;s useful for recording data to historians, or pushing data to distribution and messaging systems such as MQTT.

Importantly, it applies ARDIs naming and structure to the incoming data, ensuring that the information is recorded consistently and is easy for users to find.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Mon, 04 May 2026 03:31:47 +0000</pubDate>
        </item>
        <item>
            <title>TimescaleDB</title>
            <link>https://docs.optrix.com.au/distribute:timescaledb</link>
            <description>TimescaleDB

This type of distribution sends incoming data to a TimescaleDB server to be recorded.

TimescaleDB is a modified version of PostGRESQL designed to handle long term, high-speed time-series data without experiencing the major performance issues that arise when storing this sort of data in a traditional database engine.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 28 May 2026 04:53:10 +0000</pubDate>
        </item>
        <item>
            <title>Webhook</title>
            <link>https://docs.optrix.com.au/distribute:webhook</link>
            <description>Webhook

This type of distribution sends incoming data to an HTTP server.

Note that as live data can be very fast, we suggest the webhook server must be able to handle a high rate of incoming calls.

Type Name

The type name to use in your configuration is webhook</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 03 May 2026 23:57:07 +0000</pubDate>
        </item>
    </channel>
</rss>
