Issue
TAC Xenta I/O modules that are added as LonWorks units in TAC Vista, are converted to Xenta I/O modules belonging to a Xenta Base unit (SlaveSpeak devices) in EcoStruxure Building Operation, after conversion using TAC Vista Conversion Tool.
Product Line
EcoStruxure Building Operation, TAC Vista
Environment
- Vista Server
- TAC Vista Conversion tool
- Xenta
- Xenta I/O-modules
Cause
In TAC Vista, the Xenta I/O modules are normally located on the same subnet as the Xenta Base unit, and belong to the Xenta Base unit, communicating as SlaveSpeak devices.
If a Xenta I/O module is located on another subnet than the Xenta base unit, it could instead be added as a LonWorks Unit in Vista, and therefore communicating via LonWorks bindings to the Xenta base unit using SNVTs.
Vista Conversion Tool does not handle this configuration. In the conversion tool, all Xenta I/O modules are expected to be connected directly to a Xenta base unit, located on the same Subnet, and are therefore always treated as SlaveSpeak devices.
Resolution
After running the Vista Conversion tool, you have to re-build the LonWorks Bindings between the Xenta I/O module and the Xenta Base unit manually in EBO, as the Conversion Tool does not handle the actual configuration setup.
