DS200RTBAG3AEB燃機(jī)電氣模塊
LonWorks選項(xiàng)板包含控制器節(jié)點(diǎn)的程序ID。控制器MPU板將存儲(chǔ)組合首次通電時(shí),LonWorks板上EEPROM中的程序ID。當(dāng)網(wǎng)絡(luò)Manager軟件將控制器節(jié)點(diǎn)安裝為網(wǎng)絡(luò)的一部分,當(dāng)控制器處于首次安裝。與所有其他已安裝節(jié)點(diǎn)一樣,控制器的程序ID由網(wǎng)絡(luò)管理器。
版本1.30程序ID已更改,因?yàn)樾鹿δ軌KDIS和DOS包含新網(wǎng)絡(luò)變量類型:SNVT_state。當(dāng)控制器固件升級(jí)到1.30或更高版本時(shí),控制器將存儲(chǔ)新的LonWorks板上EEPROM中的程序ID,以便網(wǎng)絡(luò)管理員將其識(shí)別為不同的節(jié)點(diǎn)類型。
考慮
1.當(dāng)已安裝網(wǎng)絡(luò)中的控制器升級(jí)到1.30或更高版本時(shí),網(wǎng)絡(luò)管理器將不會(huì)識(shí)別新版本添加的網(wǎng)絡(luò)變量。網(wǎng)絡(luò)管理器將能夠綁定早期版本中存在的變量。
2.在固件為1.30或更高版本的控制器中使用的LonWorks板不應(yīng)用于固件為1.21或更低版本的控制器。LonWorks板EEPROM將包含存儲(chǔ)在中的程序ID它由1.30固件。
?如果LonWorks板安裝在具有1.21固件的控制器中,并且控制器由如果網(wǎng)絡(luò)管理器以前未安裝固件為1.30的控制器,則會(huì)出現(xiàn)問(wèn)題。
網(wǎng)絡(luò)管理器將讀出可用的網(wǎng)絡(luò)變量列表,但變量?jī)H為在1.21中可用的那些。在后續(xù)安裝1.30固件的控制器中網(wǎng)絡(luò)管理器不會(huì)讀取,因此無(wú)法訪問(wèn)新的1.30變量。
?如果LonWorks板安裝在具有1.21固件的控制器中,并且控制器由之前安裝了固件為1.30的控制器的網(wǎng)絡(luò)管理器,即網(wǎng)絡(luò)管理器變量列表將包括新的1.30變量。但是,控制器將拒絕綁定嘗試他們建議的行動(dòng)
升級(jí)MPU控制器固件時(shí):
1) 生成所有網(wǎng)絡(luò)綁定的報(bào)告。
2) 從網(wǎng)絡(luò)中卸載控制器節(jié)點(diǎn)。
3) 升級(jí)控制器固件
4) 安裝控制器節(jié)點(diǎn)。
5) 參考上述報(bào)告并綁定所有網(wǎng)絡(luò)變量。筆記如果控制器已升級(jí),仍可使用當(dāng)前MetaVision 3.0x網(wǎng)絡(luò)管理器的版本,但在升級(jí)之前卸載為推薦。其他網(wǎng)絡(luò)管理器可能不允許這樣做。
5.一旦LonWorks選項(xiàng)板用于1.30或更高版本的控制器,并從服務(wù),將板標(biāo)記為“僅1.30固件”。
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. Suggested Actions
4. When upgrading MPU Controller firmware:
1) Generate a report of all network bindings.
2) Uninstall the controller node from a network.
3) Upgrade the controller firmware
4) Install the controller node.
5) Refer to the above report and bind all network variables.
Note
If the controller has already been upgraded, it can still be uninstalled with the current
version of the MetaVision 3.0x Network Manager but uninstalling prior to upgrading is
recommended. Other Network Managers may not allow this.
5. Once a LonWorks option board is used in a 1.30 or higher controller and is uninstalled and removed from
service, mark the board as “1.30 firmware only”.