Issue
- AMT has stopped receiving data
- AMT is not receiving data
- A new link added to a system, is not sending messages or transactions
Product Line
TAC INET
Environment
I/NET
Cause
AMT can stop receiving data for several reasons.
- Connection between Remote Client with I/O and SQL is broken
- AMT is Paused
- Communication to the device is not functioning
- AMT Masking is not set correctly
- Host Masking is not set correctly
- Point Masking is not set correctly
- Door Editor Masking is not Set
- The software has frozen
- I/NET has reached its maximum online event size and FIFO is not working (very rare)
- Other
Resolution
Connection between Remote Client with I/O and SQL PC is broken.
- Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC
- Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server
- Wait several minutes for data to update.
- If this fails, ensure that there are no firewalls or communication failures between the 2 PCs.
- If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server. This is fixed in v2.43 or greater.
AMT is paused
- Right-click anywhere in an open Alarm/Transaction/Message window
- The bottom choice is either "Pause" or "Resume"
- If it is "Resume" click on that and AMT function will be restored
Communication to the device is not functioning
- Minimize AMT and open I/NET
- Connect to the controller
- Select Summary>Controller
- If you see values and get no error messages this is not the issue
- If you cannot see values or get a "No Entries in Database" error, determine why communication is down
AMT Masking is not set correctly
- In AMT Select Edit>Configuration
- Note the current settings, take a screen shot and save it if possible
- For troubleshooting purposes, select all of the check boxes under "Messages/Alarm"
- Restart the I/O server
- In I/NET trigger a point to go into alarm or send a message
- Check AMT for successful delivery
Host Masking is not set correctly (TCP/IP only)
- Right-click on the I/O server and select Configure
- Modify the Active Profile
- On the bottom of the screen click on "Host Masks"
- Select any NPR or 527
- Note the current settings
- Check all boxes
- Click okay
- Repeat 4-7 for all NPR or 527 devices
- Restart the I/O server
- In I/NET trigger a point to go into alarm or send a message
- Check AMT for successful delivery
Point Masking not set correctly
- Connect to a controller that you expect to receive messages from
- Select Edit>Controller>Resident I/O
- Modify a point you expect to receive messages from
- Ensure that the appropriate Mask bits are set
- Ensure that there is a priority set for both Messages and Alarms
- Click okay
- Go to the controller summary and attempt to trigger a message or alarm
Door Editor Masking is not Set
- Connect to a controller that you expect to receive messages from
- Select Edit>Controller>Doors
- Modify a door you expect to receive messages from
- Ensure that the appropriate Mask bits are set
- Ensure that there is a priority set for both Transactions and Alarms
- Click okay
- Attempt to trigger a message or alarm
The software has frozen
- Restart the I/O server
- If this does not work restart the computer
I/NET has reached its maximum online event size and FIFO is not working (very rare)
- Right Click on the I/O server and select Archive Configuration
- Enable Archiving if it is not enabled
- Increase the size of the maximum online events
- Restart the I/O server
- Trigger an Alarm or Event in I/NET
- Verify AMT
Other troubleshooting steps
- Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back
If AMT still will not function Repeat the above processes using an Event window with no filter. It is possible messages are being received, just not to the open Window
- Close all open AMT windows
- Select System>New>Event Window
- Click Okay
- This opens an Event Window which will display all data coming into AMT
- Repeat the above troubleshooting processes
The Controller LAN is having communication issues
- Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure
Other solutions for this issue have been documented in these articles:
- No door transactions coming into AMT: Quick Poll is not enabled. Typically applies to older sites.
- Transactions not Updating AMT Window using direct connect: For Direct Connect systems
- No Transactions or controller Events in AMT: Reliable Tap
- AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.
