For more information on the user interface, see Nodes.

  1. Select all nodes in the list.
  2. Select a single node.
  3. Menu with the following actions:
    • Start: Start all selected nodes.
    • Restart: Restart all selected nodes. Only started nodes can be restarted.
    • Stop: Stop all selected nodes. Only started nodes can be stopped.
    • Configuration: Opens the node configuration dialog.
    • Delete: Delete all selected nodes. Node deletion will automatically stop the polling for the deleted nodes and remove the nodes from the node list.

Node deletion will not affect the Navigator tree structure. The node will continue to be listed in the Navigator tree structure, but the node’s values will no longer be updated from MSIB.

The following information displays in the node list:

  • Node Name.
  • Current state of the node.
  • Quality: 0& (0/0): Quality in % of the node and number of points.
  • Based on the percentage of the total points for a node compared to the points reporting a value on the previous cycle, this number indicates the quality of data coming from a node. The percentage excludes failed points and unresponsive points. If the node is stopped, the value will be empty.

Node details

Selecting an individual node name provides the following node specific data.

  • The number of point licenses being used by a started node. The node itself is not counted as a point for licensing purposes.
  • Node data about the objects within a started node.
  • Configuration information about the node.
Configured Node Points
  1. Create and download node file.
  2. Refresh the table.
  3. Open the Configuration dialog for the node.
  4. Go Back to the nodes list.
  5. The object Name.
  6. An Alternate Point Name, if provided.
  7. The object Description, if provided.
  8. The most recent Value.
  9. The object’s Unit of measure.
  10. An indication of the object’s Quality, whether reliable (Normal) or in a fault state. The following values are possible:
    • Normal
    • Fault: Hardware Fault
    • Fault: Timeout
    • Initializing
  12. The Priority level of a BACnet point.
  13. The Priority column applies to commandable BACnet points. MSIB uses the priority array to display the current BACnet priority of a point.
  14. A visual representation of the Status.
  15. The current Timestamp displayed in UTC standard. This column is only populated if activated in the settings. For more information, see .
  16. The timestamp of the data can be displayed in either UTC or local time. UTC is the default view.

BACnet IP

MSIB displays the following point details for BACnet IP points.

  • Object Name
  • Description
  • Object Instance
  • Object Type
  • Virtual
  • Current Value
  • Engineering Units
  • Priority Level
  • Data Quality
  • Status - Fault
  • Status - Alarm
  • Status – Out of Service
  • Status - Overridden
  • Device Name
  • Device Instance
  • Device Database Rev
  • Equipment Name
  • IP Address
  • DHCP Enabled
  • BACnet Network
  • RPM Enabled

BACnet MSTP

MSIB displays the following point details for BACnet MSTP points.

  • Object Name
  • Description
  • Object Instance
  • Object Type
  • Virtual
  • Current Value
  • Engineering Units
  • Priority Level
  • Data Quality
  • Status - Fault
  • Status - Alarm
  • Status – Out of Service
  • Status - Overridden
  • Device Name
  • Device Instance
  • Device Database Rev
  • Equipment Name
  • IP Address
  • DHCP Enabled
  • BACnet Network
  • MSTP Address
  • MSTP Network
  • RPM Enabled

APOGEE P2

MSIB displays the following point details for APOGEE P2 points.

  • Point Name
  • Descriptor
  • Point Type
  • Virtual
  • Current Value
  • Engineering Units
  • Priority Level
  • Data Quality
  • Status - Fault
  • Status – Alarm
  • Status – Out of Service
  • Status - Overridden
  • Device Name
  • Equipment Name
  • IP Address
  • DHCP Enabled
  • Network Name

If a point detail is not applicable, a dash (-) displays in the value field.

Polling

For quickest confirmation of communication at start up, Siemens recommends starting the nodes aligned with the top of the hour at 15-minute intervals. This allows MSIB to begin the process of polling data without delay. Otherwise, you may have to wait for the time interval to be aligned before you see data. For example, if you have 1000 points and start the node at 14 minutes after the hour, MSIB will know it cannot poll that many points in one minute, so it will wait one minute, then start polling to align with the next 15-minute increment.

When a node is started, MSIB will list the expected points in the UI, marking them as initializing until data is received to indicate the points are normal.

If a point does not respond in time for a poll, the node will show the last polled value and the status column will indicate a timeout fault.

If all of the points respond to a poll, then the values are updated and the status is normal for each point.

If a point does not respond because of faulty hardware, the node will show the last polled value and the status column will indicate a hardware fault.

MSIB will attempt one retry of polling points under these circumstances:

  • All points on the node have been tried
  • Enough time remains in the polling cycle for a retry.
  • The point being retried had timed out, failing to respond.

If a point already responded with an error or a fault, it will not be retried.

Points that fail to respond do not get sent to Navigator. Only points that respond with a normal or hardware fault status have their data transmitted to Navigator.

Some devices, such as DXRs, require MSIB to discover information about them before polling can begin. For these, you will need to allow extra time before expecting data to flow to MSIB.

See also