Issue
A Xenta 5/7/9xx controller can either be implemented as
- A Xenta Server, where it doubles as the LonTalk adapter and a Xenta device
- A LON node, where it is a part of an LNS database below a different LonTalk adapter
If the Xenta is a LON node, then it will be represented as a LON device in the network, but also utilizes Xenta Group Bindings to communicate to Xenta programmable controllers (280/300/401). If graphic pages in certain Xenta units aren't displaying data, or connection objects aren't passing data as expected, the online status of the Xenta units should be checked not from the Vista Server, but from inside the Xenta 5/7/9xx. This issue will display red x's on the graphics page.
Product Line
TAC Vista
Environment
- Xenta 511, 527, 701, 711, 721, 731, 913
- LNS Database
Cause
A Xenta 5/7/9xx LON node pulls "double duty" as both a LON device and a Xenta Lacnet device. It requires one Xenta Group Binding on message tag 0 to facilitate communication with Xenta programmable controllers.
Resolution
- Log into the web interface for the 5/7/9xx.
- Navigate to Utilities > LacNet > LacNet List Xenta. "LacNet" refers to proprietary Xenta communication.
- View the online status of each Xenta programmable controller in the network. It is displayed as below:
===============================================
Node: RTU7
Xenta group: XG_RTUS GroupMaster:No
FTP state alarmstack, app:finished OnOff:N/A
Latest FTP : 05/13/2011 11:25:59
State: online (since 05/13/2011 11:23:05)
Xenta??? Software version: 3.84-01
NID: 04:6B:84:9F:01:00 Subnet/Node: 253/122
Module: SUMMARY
Module: CALIBRATE
Module: CONFIGURE
Module: ALARMS
Module: SETPOINTS
Module: ERRORS
Module: $LOG
Module: $SYSTEM
Module: $SYS
Number of alarm objects: 25
Number of public signals: 7
Number of handles allocated: 8, where 1 is with notification
===============================================
