Issue
Infinet to MP or RP controller communications
Product Line
EcoStruxure Building Operation
Environment
- Infinet Controller i2 i1
- SmartX IP RPC RP-C, MPC, MP-C, MPV, MP-V Controller
Cause
The power cycle and bandwidth requirements need to be considered when setting the parameters for Infinet to MP/RP communication
Resolution
First ensure a good understanding of "Infinet Under the hood" article.
A direct binding can easily be made between an Infinet controller object like an Analog Value and an MP/RP Controller object like an Analog Value.
The whole communication path is not BACnet so a "Value transfer settings" window can be opened that controls part of the EBO communication process.
This default configuration (Infinet to MP/RP) will usually result in the Infinet Value being collected every 10 seconds, this value will then only only be written to the MP/RP when the value changes. To ensure the value is correct following a power cycle either enable Guaranteed transfer and set to 1 minute, or use the retailed level on the MP/RP object
If there is a listview, graphic or watch window containing the Infinet Object, this causes the value to be collected every 500mS, as seen in the screenshot below
If the Infinet Object is "exported", (see "Infinet under the hood" for details) then the communication can be much more efficient as the values are only sent when there is a change (greater than the object threshold for analog inputs).
If the communication is from the MP/RP Object to the Infinet controller Object, then a BACnet COV subscription will be set up by the EBO server to the MP/RP Controller, this will be renewed if either is reset/power cycled.
It needs to be remembered that the "Value Transfer settings" is an EBO property and in this case the communication is controlled by the EBO Server with Infinet in one direction and BACnet in the other. So the communication to the MP'/RP controllers will either be a write or a COV subscription from the EBO Server.
