MbusDevice

This component configures and Mbus device.

Figure 3. MbusDevice Property Sheet

To access this view, right-click the device component in the Nav tree and click Views > Property Sheet.

Property	Value	Description
Status	read-only	Indicates the condition of the component at the last check. `{ok}` indicates that the component is licensed and polling successfully. `{down}` indicates that the last check was unsuccessful, perhaps because of an incorrect property, or possibly loss of network connection. `{disabled}` indicates that the `Enable` property is set to `false`. `{fault}` indicates another problem. Refer to `Fault Cause` for more information.
Enabled	`true` or `false`	Activates and deactivates use of the component.
Fault Cause	read-only	Indicates the reason why a system object (network, device, component, extension, etc.) is in fault. This property is empty unless a fault exists.
Health	read-only	Indicates the status of a system object (network, device or component) in the station. Includes a timestamp.
Alarm Source Info	additional properties	Contains a set of properties for configuring and routing alarms when this component is the alarm source.
Mbus Config	additional properties	See Mbus Config properties.
Model Name	text	Identifies the model of the meter.
Poll Frequency	drop-down list, defaults to `Normal`	Specifies which of the three poll tables to use. `Fast` interrogates each device frequently. `Normal` interrogates each device at a standard rate. `Slow` interrogates each device infrequently.
Baud Rate	drop-down list, defaults to `300 Baud`	Configures the device’s communication speed.
Primary Address	0 to 250	Defines a unique number for each device.
Secondary Address	number	Defines an alternate number to identify each device.
Address Mode	drop-down list	Indicates which address to use: `Primary`, `Secondary` or `Secondary Extended`.
Cycle Quantity	number	Identifies the number of message commands required to obtain all messages from a device.
Reset Required (optional)	`true` or `false` (default)	Defines if the device requires a reset to be output prior to requesting messages.
Search Fc Bit State	`true` (default) or `false`	Refers to data transmitted from the slave device to the master, and functions with the `Search Fc Bit in Use` property. `true` indicates that a follow-on message contains the next set of data. In other words, the slave has more data to communicate to the master than fits into a single message. FC stands for Frame Count.
Search Fc Bit in Use	`true` (default) or `false`	Refers to data transmitted from the slave device to the master, and functions with the `Search Fc Bit State` property. `true` indicates that the `Search Fc Bit State` should be evaluated for additional data. Not all devices need to implement this, and those that do declare within the message if the mechanism is active or not.
Req Ske Capable	`true` or `false` (default)	Defines as a capability in the protocol, which the driver can use if the device supports the feature. Not all devices support this functionality.
Ident Number	read-only	Reports the number contained in each communication message received from the device.
Manufacturer	read-only	Identifies the device manufacturer. This code is contained in the communication messages from this device.
Device Type ID	drop-down list	Defines the device type. This information is found in the communication messages from this device.
Application Reset Type (hidden slot)	defaults to `All`	Defines which data within the remote device can be reset if the device supports it.
Sub Telegram Number (hidden slot)	number	Identifies the message (sub-telegram) to display when carrying out an Application Reset action.
Max Inputs Per Cycle Count (hidden slot)	number	Configures the additional number of data requests issued to retrieve data for one cycle. This applies when the initial data message input to the JACE or PC contains a continuation flag, which causes the device to make another request for more data. If subsequent inputs contain continuation flags, the request repeats.
History	additional properties	See History.

Mbus Config properties

Property	Value	Description
Override Network	`true` or `false` (default)	Configures the network to use alternative configuration properties. `false` configures the network to use the standard network-level properties. `true` configures the network to use the properties below.
Retry Count	number (defaults to 2)	Configures how many times to repeat a network read request, if no response is received before the response timeout interval.
Response Timeout	hours, minutes, seconds, milliseconds (defaults to 2 seconds)	Configures the length of time before the system times out when interrogating an Mbus device. You should start by setting this value to a large number, such as 40 seconds. Then, reduce it depending on the number of meters and discovery performance. During testing, a value of 12.5 seconds was used. NOTE: The baud rate also impacts performance. Each device may have a different baud rate.
Inter Message Delay	hours, minutes, seconds (defaults to 0.3 seconds)	Defines the amount of time between messages.
Initialization Delay	hours, minutes, seconds, milliseconds (defaults to 1 seconds)	Defines the period before the system sends next command following an initialization request to the network (SND_NKE). This period should be adjusted to suit the hardware installed on the network. Please consult the device documentation for a suitable value.

History

These properties define what automatically happens when the station regularly connects with a device. Retries occur with the frequency defined by the Interval property (every 15 minutes in the screen capture). Retries continue until the station successfully retrieves the history.

Figure 4. Mbus History Device Ext properties

Property	Value	Description
Retry Trigger	schedule	Adjusts the retry trigger in the event that the History Device Extension could not contact the device.
Trigger mode	drop-down list	Configures when the extension contacts the device.
Last Trigger	read-only	Reports the last time the extension contacted the device.
Next Trigger	read-only	Reports when the extension will contact the device next.

Actions