https://docs.optrix.com.au/ Thu, 01 Oct 2026 00:16:02 +0000 FeedCreator 1.8 https://docs.optrix.com.au/_media/wiki:dokuwiki.svg https://docs.optrix.com.au/ https://docs.optrix.com.au/distribute:configuring_live_data_distribution Configuring Live Data Replication To distribute live data to other locations, create a replication.json file in your site folder. You should also install and enable the live data replication addon. The site folder is located in your ARDI installation directory, under /web/sites/ anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:22:36 +0000 https://docs.optrix.com.au/distribute:creating_your_own_distributor Creating Your Own Replicator Replicator files can be found in your Python library directory, under /ardi/consolidator. Replicator modules are named 'dist_xxx', where 'xxx' is the type name used in the configuration file. Note that originally the replication engine was called the anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:30:04 +0000 https://docs.optrix.com.au/distribute:influx InfluxDB This type of replicator 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 anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:23:57 +0000 https://docs.optrix.com.au/distribute:memcache Memcache This type of replicator 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 anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:24:24 +0000 https://docs.optrix.com.au/distribute:mqtt_versions 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's own distinct MQTT message. anonymous@undisclosed.example.com (Anonymous) Sun, 03 May 2026 23:33:34 +0000 https://docs.optrix.com.au/distribute:mqtt MQTT Per-Point Topics This type of replicator 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. anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:24:37 +0000 https://docs.optrix.com.au/distribute:mqttev MQTT Event Notifications This type of replicator 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. anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:24:50 +0000 https://docs.optrix.com.au/distribute:mqttob MQTT Per-Asset Topics This type of replicator 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. anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:25:02 +0000 https://docs.optrix.com.au/distribute:pre-built_distributors Pre-Built Replicators Below are the list of replicator 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 anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:23:43 +0000 https://docs.optrix.com.au/distribute:redis Redis This type of replicator 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 anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:25:49 +0000 https://docs.optrix.com.au/distribute:start Live Data Replication ARDIs Live Data Replication functions let you push live data to other platforms as it arrives. It'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. anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:30:31 +0000 https://docs.optrix.com.au/distribute:timescaledb TimescaleDB This type of replicator 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. anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:26:02 +0000 https://docs.optrix.com.au/distribute:webhook Webhook This type of replicator 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 anonymous@undisclosed.example.com (Anonymous) Wed, 16 Sep 2026 22:26:17 +0000