MVME332XTP庫存備件
查看驅動(dòng)器狀態(tài)查看參數和信號瀏覽樹(shù)窗格項目集窗格3.備件處理我們建議您為驅動(dòng)器控制板備件保留每個(gè)DDCS通信通道中的一個(gè)節點(diǎn)地址。原因是：?用作備件的控制板在裝運時(shí)通常有一個(gè)預先編程的節點(diǎn)地址。?如果控制板完全沒(méi)有編程，它將在節點(diǎn)地址1處啟動(dòng)。?如果節點(diǎn)地址1處有驅動(dòng)器，則DriveWindow中需要或能夠重新啟動(dòng)驅動(dòng)器的功能無(wú)法在其他節點(diǎn)重新啟動(dòng)驅動(dòng)器。原因是，任何重新啟動(dòng)的驅動(dòng)器都會(huì )使用一個(gè)節點(diǎn)地址，并且在此期間會(huì )有兩個(gè)驅動(dòng)器在同一節點(diǎn)地址處響應。如果不遵循這些建議，則無(wú)法：?下載其他驅動(dòng)器的參數后重新啟動(dòng)。?將系統軟件還原或下載到其他驅動(dòng)器。如果您遵循建議并將節點(diǎn)地址保留為一個(gè)備用地址，例如，用備用地址替換控制板是很容易的。調試完成后，對所有驅動(dòng)器進(jìn)行完全備份。您可以將它們全部保存在一個(gè)備份包文件中。如果驅動(dòng)器的控制板出現故障，需要用備件更換：?用備件更換控制板。您不需要關(guān)閉其他驅動(dòng)器的電源。?如果DriveWindow正在運行，請斷開(kāi)OPC服務(wù)器或退出。?給驅動(dòng)器通電。?啟動(dòng)DriveWindow和/或連接OPC服務(wù)器。修復的驅動(dòng)器應出現在節點(diǎn)地址1。?打開(kāi)備份包文件。?選擇要恢復的節點(diǎn)地址1處的已修復驅動(dòng)器。?從備份包中選擇要用于恢復的原始節點(diǎn)。?執行還原。如果一切正常，修復后的驅動(dòng)器將顯示在其原始節點(diǎn)地址。?通過(guò)關(guān)閉備份包進(jìn)行清理。請注意，如果使用這種處理備件的方法，則無(wú)需在光學(xué)DDCS網(wǎng)絡(luò )中進(jìn)行任何連接更改。其他DriveWindow 2 9-31另請參閱：什么是備份包如何備份如何恢復如何恢復參數4.限制4.1.1最大板數DriveWindow本身不使用通信板本身。因此，限制由DriveOPC設置，DriveWindow使用DriveOPC與驅動(dòng)器通信。從2.03版（包括在DriveWindow 2.02版中）開(kāi)始，DriveOPC可以處理多個(gè)DDCS通信板。支持的板的數量取決于操作系統。自2.08版（包括在DriveWindow 2.22版中）起，DriveOPC還可以在Windows 2000/XP/Vista下處理RUSB-02 USB/DDS適配器。盡管DriveOPC 2.09版（包括在DriveWindow 2.30版中）支持，但DriveWindow 2.33（或更高版本）安裝不支持NISA-03板和Windows NT。
See Also: Viewing Status of Drives Viewing Parameters and Signals Browse Tree Pane Item Sets Pane 3. Handling of Spare Parts We recommend that you reserve the node address one of each DDCS communication channel for drive control board spare parts. The reasons are: ? Control boards made to be used as spare parts have usually node address one preprogrammed, when they are shipped. ? If a control board has not been programmed at all, it boots at node address one. ? Functions within DriveWindow, which require or are able to restart a drive, cannot do restarting of drives at other nodes, if there is a drive at node address one. The reason is that any restarting drive uses node address one for while, and there would be two drives responding at the same node address during that time. If you do not follow these recommendations, you are not able to: ? Restart other drives after downloading their parameters. ? Restore or download system software to other drives. If you follow the recommendations and leave the node address one free for spare parts, replacing a control board, for example, with a spare is easy. After commissioning is done, take full backup of all drives. You can have them all in a single backup package file. If a control board of a drive fails and needs to be replaced by a spare: ? Replace the control board with a spare. You do not need power off other drives. ? If you have DriveWindow running, either disconnect the OPC Server or exit. ? Power up the drive. ? Start DriveWindow and/or connect the OPC Server. The repaired drive should appear at node address one. ? Open the backup package file. ? Select the repaired drive at node address one to be restored. ? Select the original node from the backup package to be used in restoring. ? Execute restoring. If all went well, the repaired drive will be shown at its original node address. ? Clean up by closing the backup package. Note that you do not need to do any connection changes in the optical DDCS network, if using this method of handling spare parts. Miscellaneous DriveWindow 2 9-31 See Also: What is a Backup Package How to Backup How to Restore How to Restore Parameters 4. Limitations 4.1.1 Maximum Number of Boards DriveWindow itself does not use the communication boards itself. So, the limits are set by the DriveOPC, which DriveWindow uses in communication with the drives. Since version 2.03 (included in DriveWindow version 2.02), DriveOPC can handle several DDCS communication boards. Number of supported boards depends on the operating system. Since version 2.08 (included in DriveWindow version 2.22), DriveOPC can handle also RUSB-02 USB/DDCS adapters under Windows 2000/XP/Vista. Although supported by DriveOPC version 2.09 (included in DriveWindow version 2.30), DriveWindow 2.30 (or newer) installation does not support NISA-03 boards and Windows NT.
