LonWorks Communications
UM353-1
March
2003
5-2
SERVICING CONSIDERATIONS
The functioning of a LonWorks network can be affected by:
•
Upgrading the MPU Controller board firmware
•
Replacing a controller’s MPU Controller board with a board having a different firmware version
•
Moving a LonWorks board to a controller with a different MPU Controller board firmware version
Background
A LonWorks option board contains a Program ID for the controller node. A Controller MPU board will store a
Program ID in the EEPROM on the LonWorks board when the combination is first powered up. When the Network
Manager software installs a controller node as part of a network, it reads the Program ID when a controller is
installed for the first time. The Program ID of the controller, as with all other installed nodes, is then retained by the
Network Manager.
The version 1.30 Program ID was changed since new function blocks DIS and DOS contained a new network
variable type: SNVT_state. When controller firmware is upgraded to 1.30 or higher, the controller will store a new
Program ID in the EEPROM on the LonWorks board so that a Network Manager will recognize it as a different
type of node.
Considerations
1. When a controller in an installed network is upgraded to 1.30 or higher, the Network Manager will not
recognize the network variables added by the new version. The Network Manager will be able to bind
variables present in the earlier version.
2. A LonWorks board that has been used in a controller with 1.30 or higher firmware should not be used in a
controller with firmware 1.21 or lower. The LonWorks board EEPROM will contain the Program ID stored in
it by the 1.30 firmware.
•
If the LonWorks board is mounted in a controller with 1.21 firmware and the controller is installed by a
Network Manager that had
not previously installed
a controller with 1.30 firmware, a problem will occur.
The Network Manager will read out the list of network variables available but the variables will be only
those that were available in 1.21. In subsequent installations of controllers with 1.30 firmware, the
Network Manger will not read, and therefore will not have access to, the new 1.30 variables.
•
If the LonWorks board is mounted in a controller with 1.21 firmware and the controller is installed by a
Network Manger that
had previously installed
a controller with 1.30 firmware, the Network Manager
variable list will include the new 1.30 variables. The controller, however, will reject an attempt to bind
them.
StockCheck.com
Содержание Moore 353
Страница 2: ...S t o c k C h e c k c o m ...
Страница 14: ...Contents UM353 1 xii March 2003 S t o c k C h e c k c o m ...
Страница 24: ...Introduction UM353 1 March 2003 1 10 S t o c k C h e c k c o m ...
Страница 152: ...LonWorks Communications UM353 1 March 2003 5 4 S t o c k C h e c k c o m ...
Страница 164: ...Network Communications UM353 1 6 12 March 2003 S t o c k C h e c k c o m ...
Страница 246: ...Operation UM353 1 March 2003 9 8 S t o c k C h e c k c o m ...
Страница 254: ...Controller and System Test UM353 1 March 2003 10 8 S t o c k C h e c k c o m ...
Страница 282: ...Circuit Description UM353 1 March 2003 13 4 S t o c k C h e c k c o m ...
Страница 298: ...Model Designation and Specifications UM353 1 March 2003 14 16 S t o c k C h e c k c o m ...
Страница 302: ...Abbreviations And Acronyms UM353 1 15 2 March 2003 S t o c k C h e c k c o m ...
Страница 304: ...Warranty UM353 1 W 2 March 2003 S t o c k C h e c k c o m ...