MVME2700-3461機(jī)器人模塊卡件
特殊的處理方式解釋了為什么在控制驅(qū)動器時，您經(jīng)?？吹巾椖恐碉@示的質(zhì)量不確定。8.配置DDCS通信有時DDCS網(wǎng)絡(luò)的物理結(jié)構(gòu)需要更改通信板設(shè)置。配置必須在本地完成。無法遠(yuǎn)程配置。DriveOPC的通信庫中包含了設(shè)置及其用戶界面的更改。但是，如果DriveOPC配置為充當(dāng)遠(yuǎn)程OPC服務(wù)器，則會禁用其中的所有用戶界面。請注意，盡管DriveWindow被用作調(diào)用通信設(shè)置的客戶端，但它可以使用任何OPC客戶端（例如，DriveOPC發(fā)行版中包含的WriteOPC）來完成，該客戶端能夠?qū)懭隣PC項。要配置DDCS通信，請關(guān)閉所有使用DriveOPC的應(yīng)用程序。如果您正在配置（遠(yuǎn)程端）PC，該P(yáng)C被配置為服務(wù)遠(yuǎn)程客戶端，您還必須：?在配置DDCS通信時，確保沒有客戶端將使用DriveOPC。如果無法以其他方式執(zhí)行，則可以使用DCOMCNFG.EXE禁用DCOM。?編輯DWC_DEF。INI，并在[OPC]部分將Remote=1更改為Remote=0。在所有情況下，都應(yīng)檢查DWC_DEF.INI。如果根本沒有[OPC]部分，下面沒有Remote鍵，或者Remote的值為零，則正常。如果DriveOPC版本早于2.03（DriveWindow 2.01或更高版本），并且PC已通過寄存器更改配置為使用本地服務(wù)器（EXE）版本的DriveOPC，而不是進(jìn)程中（DLL）版本，則應(yīng)撤銷寄存器更改，從而使用進(jìn)程內(nèi)（DLL）版本。完成這些準(zhǔn)備后，啟動DriveWindow并連接到本地DriveOPC。使驅(qū)動器狀態(tài)刷新脫機(jī)。高級信息10-26 DriveWindow 2添加具有OPC地址通信的項目。ConfigureDialog導(dǎo)入瀏覽的項目集?；?qū)⒁渲玫念l道號（0，1，..）寫入添加的項目。DriveOPC通信庫顯示DDCS對話框。筆記如果DriveOPC版本早于2.03（DriveWindow 2.01或更早），則DriveWindow（或任何其他客戶端）的用戶界面可能處于活動狀態(tài)。請在關(guān)閉對話框之前不要使用它。如果這樣做，您可能會使客戶端程序崩潰。高級信息驅(qū)動窗口2 10-27現(xiàn)在您可以更改鏈接速率、光束強(qiáng)度和繁忙超時。請不要更改任何其他設(shè)置。單擊保存按鈕保存更改，然后單擊確定按鈕關(guān)閉對話框。單擊保存按鈕時，DriveOPC通信庫始終將更改寫入DWC_DEF。ProgramData的DriveWare文件夾中的INI文件。當(dāng)DriveOPC重新啟動時，它還會重新啟動通信庫，從DWC_DEF讀取新設(shè)置。
The special handling explains, why you often see quality uncertain shown with the item value, when control of the drive is taken. 8. Configuring DDCS Communication Sometimes the physical construction of a DDCS network is such that you need to change the communication board settings. Configuring must be done locally. Configuring remotely is not possible. Change of the settings and its user interface is included the communication library of DriveOPC. However, if DriveOPC is configured to act as a remote OPC Server, all user interfaces within it are disabled. Note that although DriveWindow is used as the client to invoke the communication settings, it can be done with any OPC client (WriteOPC included in DriveOPC distribution, for example), which is capable of writing to an OPC item. To configure the DDCS communication, close all applications, which use DriveOPC. If you are configuring a (remote end) PC, which is configured to serve remote clients, you also have to: ? Make sure that no client will use DriveOPC, while you are configuring the DDCS communication. If you cannot do it otherwise, you can disable DCOM by using DCOMCNFG.EXE. ? Edit DWC_DEF.INI in the DriveWare folder of ProgramData and change Remote=1 to Remote=0 in the [OPC] section. In all cases, you should check DWC_DEF.INI. If it does not have [OPC] section at all, there is no Remote key under it, or the value of Remote is zero, it is OK. If DriveOPC version is older than 2.03 (DriveWindow 2.01 or older), and the PC has been configured by a register change to use the local server (EXE) version of DriveOPC instead of the in-process (DLL) version in all cases, you should revoke the register changes, so that the in-process (DLL) version is used. After these preparations, start DriveWindow and connect to the local DriveOPC. Put drive status refresh off-line. Advanced Information 10-26 DriveWindow 2 Add an item with OPC address Communication.ConfigureDialog into the browsed item set. or Write the channel number (0, 1, ..), which you want to configure, into the added item. A DDCS dialog box is presented by the DriveOPC communication library. Note! If DriveOPC version is older than 2.03 (DriveWindow 2.01 or older), the user interface of DriveWindow (or any other client) may be active. Please do not use it until you have closed the dialog box. If you do, you will probably crash the client program. Advanced Information DriveWindow 2 10-27 Now you can change link rate, beam intensity, and busy time-out. Please do not change any other settings. Click the Save button to save the changes and then the OK button to close the dialog box. When you click the Save button, DriveOPC communication library always writes the changes into the DWC_DEF.INI file in the DriveWare folder of ProgramData. When DriveOPC is restarted, it also restarts the communication library, which reads the new settings from DWC_DEF.
