User Manual

Appendix G - Field Upgrade to DCW 1.16F
Landis+Gyr
Network Concentrator User and Installation Guide 98-1013 Rev AF 118
the neighborhood will be associated with the same System Controller as the Collector next door. If a
utility is large enough to have a lot of System Controllers in use, then it is likely the change to a
different Collector will result in a change to the System Controller. However, if the DCW completes
the neighbor-query process in a timely-manner, the host will straighten the reassignment once it sees
the Concentrator Registration Message.
The Concentrator discovery process time can be between 15 - 30
minutes
If the host sends the Concentrator CPU a message before the new default destination is assigned, it
will use the Collector within the database. The DCW automatically accepts the Collector WAN
address as the default destination as long as the message is received before the default destination is
assigned.
Self-Assigned Destination
The best way to prevent unprocessed messages from interfering with data reads, is to shut down the
host registration processing code during scheduled reads. The DCW will continue to send
Concentrator Registration Messages once every 15 minutes until the host responds. If the DCW
successfully self assigns a destination, a query from the host to the Concentrator CPU is received to
not automatically change the destination. To change the destination, you must manually change it. If
the destination change fails while on a different System Controller, the meter read data that is going
to an incorrect System Controller is still processed, and then put into the database. The meter
discovery events from that Concentrator will not work.
To avoid non-working meter discovery events, L+G recommends using
the normal Concentrator repoint process to address the Conc en tr ator
to the correct System Con t r o lle r.