Issue
When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications.
Product Line
TAC INET, TAC Vista
Environment
- I/NET
- XBuilder
- I/NET Host Tool
Cause
When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications.
Resolution
This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913.
Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged.
- Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO)
- Create an internal AO point to function as a translator (logic AO)
- Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80
- Perform a Station save
- In XBuilder, create a project for the 527 Web Server
- Insert or re-insert the I/NET network
- Add a connection object
- Drag the Flags attribute of the Doors DO point to the "from" part of the connection object
- Drag the Value attribute of the logic AO point to the "to part of the connection object
- Generate the Project and Send to Target.
The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO. The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test. The Buzzer will not activate if the point is in Manual or Test
The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc). Turn off the other possible alarms, or create an addition internal point labeled Door Forced. The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2)) C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal
