User's Manual
Table Of Contents
- Table of Contents
- Figures and Tables
- 1 - Introduction
- 2 - Functional Description
- 3 - Troubleshooting
- 4 - Specifications
- Acronyms
- Glossary
- Index
36 Universal Metering Transponder for kV2c™ Meter User Guide
Performing Remote Analysis (TNS)
2. Determine if any error messages have occurred during AMR by checking
the SCE Notification log for any associated hardware issues for the meters
that are not communicating.
N
OTE
The Notification log contains important information about the status of
equipment and is automatically updated by TNS and the SCE. For detailed
information about the Notification log and error messages, see the
Notification Log section of the SCE Logs chapter in the TNS Operational
Process Guide and the Notification Log section in the SCE Maintenance chapter
of the TNS End User Guide.
3. Check for TNS errors that may have occurred because of commands
time-out, or any software related issues in TNS that may have prevented
AMR commands processing.
For more information on time-out issues, see the Encode Command
Parameters section in the TNS System Maintenance chapter of the TNS End
User Guide.
4. Perform an On-Request AMR command to determine if the unit
communicates. (This command communicates to the unit by serial number
to eliminate a two-way addressing issue.)
For more information about On-Request meter reads, refer to the
appropriate sections in the TNS End User Guide and the TNS Operational
Process Guide.
A site visit is not required, and you may stop this procedure if the meter
communicates. If the meter communicates, check two-way addressing.
(For more information on two-way addressing, see the Function-Group
Addressing chapter of the TNS Operational Process Guide and the
Two-Way Addressing section in the TNS Generic Applications chapter of
the TNS End User Guide.)
5. Check for other TWACS meters that are reading on the same distribution
transformer, or a nearby meter to narrow the communication problem area.
6. Check the Customer Information System for a disconnected status that may
not have updated in the TNS database. If the meter was disconnected, no
action in TNS is required, but you may want to change the cycle number.
The TNS Operator must have some process for dealing with a meter that no
longer provides a read. The TNS Operator might consider setting up a
special cycle (e.g. cycle 99) for disconnects and continue reading the
meters. Having the disconnected meters in a special cycle allows the TNS
Operator to isolate meters to scan for usage. If a Customer Service
Representative re-activates the service and the notification fails to reach the
TNS Operator, or if a customer tampers with the meter and reconnects the
service, the TNS Operator can quickly identify a successful read in a group
of meters where reads should normally fail. Using this configuration, the
TNS Operator can quickly investigate the reason for the successful read of a
supposedly disconnected meter.