abstractMqttDriver-MqttNumericObjectSubscribeExt
This component configures the subscription to numeric data.
This component is in the abstractMqttDriver palette under the AbstractMqttPoints folder.
To access these properties, expand , expand a device, expand the Points folder, expand this point and double-click the Proxy Ext.
In addition to the standard properties (Status, Fault Cause and Enabled) these properties are unique to this component.
| Property | Value | Description |
|---|---|---|
| Device facets | additional properties | Determine how values are formatted
for display depending on the context and the type of data. Examples
include engineering units and decimal precision for numeric types,
and descriptive value (state) text for boolean and enum types. With the exception of proxy points (with possible defined device facets), point facets do not affect how the framework processes the point’s value. Besides control points, various other components have facets too. For example, many kitControl and schedule components have facets. Details about point facets apply to these components too, unless especially noted. You access facets by clicking an Edit button or a chevron >>. Both open an Edit Facets window. |
| Conversion | Drop-down list (defaults to Default) | Defines how the system converts
proxy extension units to parent point units. Default automatically converts similar units (such as Fahrenheit to Celsius) within the proxy point. Note: In most cases, the standard Default conversion is best. Linear applies to voltage input, resistive input and voltage output writable points. Works with linear-acting devices. You use the Scale and Offset properties to convert the output value to a unit other than that defined by device facets. Linear With Unit is an extension to the existing linear conversion property. This specifies whether the unit conversion should occur on “Device Value” or “Proxy Value”. The new linear with unit convertor, will have a property to indicate whether the unit conversion should take place before or after the scale/offset conversion. Reverse Polarity applies only to Boolean input and relay output writable points. Reverses the logic of the hardware binary input or output. 500 Ohm Shunt applies to voltage input points only. It reads a 4-to-20mA sensor, where the Ui input requires a 500 ohm resistor wired across (shunting) the input terminals. Tabular Thermistor applies to only a Thermistor input point and involves a custom resistance-to-temperature value response curve for Type 3 Thermistor temperature sensors. Thermistor Type 3 applies to an Thermistor Input point, where this selection provides a “built-in” input resistance-to-temperature value response curve for Type 3 Thermistor temperature sensors. Generic Tabular applies to non-linear support for devices other than for thermistor temperature sensors with units in temperature. Generic Tabular uses a lookup table method similar to the “Thermistor Tabular” conversion, but without predefined output units. |
| Tuning Policy Name | drop-down | Selects a network tuning policy by name. This policy defines stale time and minimum and maximum update times. During polling, the system uses the tuning policy to evaluate both write requests and the acceptability (freshness) of read requests. |
| Read Value | read-only | Displays the last value read
from the device, expressed in device facets. |
| Write value | read-only | Displays the last value written
using device facets. |
| Topic | text | Defines a string that the broker
uses to filter messages for each client. A topic consists of one or
more topic levels. Each level is separated by a forward slash (topic
level separator). |
| Qos | drop-down | Defines the Qos (Quality of Service)
level, which configures how persistently the broker and client attempt
to ensure that a message is received. Fire And Forget (0) delivers the message once with no confirmation. Atleast Once (1) delivers the message at least once with confirmation required. Exactly Once (2) delivers the message exactly once by using a four-step handshake. Messages may be sent at any Qos level, and clients may attempt to subscribe to topics at any Qos level. |