MVME300備件模塊
忽略冒號、逗號和連字符周圍的空格。所有參數(shù)必須可讀，CheckGroup參數(shù)以外的其他參數(shù)也必須可寫。請注意，讀取還原列表時沒有錯誤檢查，因此編輯列表時必須格外小心，并且應(yīng)仔細測試更改。4.1.3 LockParameter除非為空，否則這是（布爾）參數(shù)，恢復(fù)參數(shù)時必須包含F(xiàn)ALSE（0）。高級信息10-14 DriveWindow 2 4.1.4 CheckGroup包含恢復(fù)期間檢查階段使用的參數(shù)。除了始終檢查的屬性外，這些參數(shù)的值在驅(qū)動器和要下載的參數(shù)文件中都應(yīng)該相同。4.1.5用戶組包含其他參數(shù)，當(dāng)用戶選擇恢復(fù)用戶參數(shù)時，這些參數(shù)將被恢復(fù)。除類型字符串之外的參數(shù)（屬于組10…98，不受密碼保護）無需在此列出，因為它們會自動包含在內(nèi)。4.1.6 IdRunGroup包含參數(shù)，當(dāng)用戶選擇恢復(fù)Id運行結(jié)果參數(shù)時，這些參數(shù)將被恢復(fù)。4.1.7排序在還原過程中，Groupn值按順序1…n處理。它們在文件中的順序無關(guān)緊要。在保存過程中，任何參數(shù)只會被放入保存文件一次，即使它不受密碼保護并且在還原列表中出現(xiàn)多次。4.1.8覆蓋默認值如果只需要少量修改，并且可以確定默認值，則無需將已定義為默認值的值放入DW2.INI。例如，通過在DW2.INI文件中輸入以下內(nèi)容，可以將101.3從用戶參數(shù)移動到ACW600的Id運行結(jié)果參數(shù)。[ACW600]UserGroupCount=0 IdRunGroupCount=5 IdRunrGroup5=101:3另請參閱：什么是參數(shù)和信號如何保存參數(shù)如何恢復(fù)參數(shù)瀏覽密碼更改文件夾位置5.快速監(jiān)控有兩種監(jiān)控模式：?正常模式?快速模式在正常模式下，原則上，您可以監(jiān)控任何類型的項目。此模式的最小間隔為10毫秒。正常模式是您幾乎應(yīng)該始終使用的模式。在快速模式下，您只能監(jiān)控驅(qū)動參數(shù)和實數(shù)或整數(shù)類型的信號。此模式的最小間隔為1毫秒。您應(yīng)該避免使用此模式，因為它可能會掛斷您的電腦和/或?qū)е买?qū)動器中的面板丟失。高級信息驅(qū)動窗口2 10-15注意！Windows不是實時操作系統(tǒng)。這意味著，在實踐中，即使測量周期性地進行，也不會以相等的時間間隔進行。Windows內(nèi)核中的驅(qū)動器導(dǎo)致的負載可能會導(dǎo)致數(shù)百毫秒量級的測量中斷。這些中斷可以隱藏您試圖監(jiān)視的現(xiàn)象，特別是當(dāng)您的監(jiān)視間隔很小時。在快速模式下，DriveOPC使用較低級別的通信協(xié)議，在等待驅(qū)動器響應(yīng)時可能會在循環(huán)中運行，這會導(dǎo)致處理器負載過高。此外，較低級別通信中的通信吞吐量約為1測量/毫秒。因此，如果您以1ms的間隔監(jiān)測多個信道，則間隔是繪制趨勢時使用的分辨率，而不是測量周期之間的實際間隔。
Spaces surrounding colon, comma, and hyphen are ignored. All parameters must be readable and other than CheckGroup parameters also writeable. Note that there is no error checking when reading the restore lists, so editing the lists must be done with extra care and the changes should be tested carefully. 4.1.3 LockParameter Unless empty, this is the (Boolean) parameter, which must contain FALSE (0) when restoring parameters. Advanced Information 10-14 DriveWindow 2 4.1.4 CheckGroup Contains parameters that are used in checking phase during restoration. In addition to the properties always checked, the values of these parameters should be the same both in the drive and the parameter file to be downloaded. 4.1.5 UserGroup Contains additional parameters, which are restored when user has selected restoration of User Parameters. Parameters other than type string, which are in groups 10...98 and are not pass code protected, need not to be listed here, because they are automatically included. 4.1.6 IdRunGroup Contains parameters, which are restored when user has selected restoration of Id Run Result Parameters. 4.1.7 Ordering During restore, the Groupn values are handled in order 1...n. Their order in the file does not matter. During save, any parameter is put into the save file only once, even if it is not pass code protected and appears several times in restore lists. 4.1.8 Overriding Defaults It is not necessary to put into DW2.INI the values already defined as defaults, if only small modifications are needed, and you can be sure about the defaults. For example, moving 101.3 from User Parameters to Id Run Result Parameters of ACW600 can be done by entering the following in the DW2.INI-file. [ACW600] UserGroupCount=0 IdRunGroupCount=5 IdRunrGroup5=101:3 See Also: What are Parameters and Signals How to Save Parameters How to Restore Parameters Browsing with Pass Code Changes Folder Locations 5. Fast Monitoring There are two modes of monitoring: ? Normal mode ? Fast mode In normal mode you are able, in principle, to monitor any kind of item. The minimum interval in this mode is 10 ms. Normal mode is the mode you should almost always use. In fast mode you can monitor only drive parameters and signals of type real or integer. The minimum interval in this mode is 1 ms. You should avoid using this mode, because it may hang-up you PC and/or cause panel losses in drives. Advanced Information DriveWindow 2 10-15 Note! Windows is not a real-time operating system. It means that, in practice, even if the measurements are done cyclically, they are not done with equal time intervals. Load caused by drives in Windows kernel may cause interrupts in measurements in order of hundreds of milliseconds. These interrupts can hide the phenomena you are trying to monitor, especially when your monitoring interval is small. In fast mode DriveOPC uses a lower level communication protocol and may run in a loop while waiting responses from a drive, which causes high processor load. Also, the communication throughput in the lower level communication is about 1 measurement/millisecond. Thus, if you are monitoring more than one channel with interval of 1 ms, for example, the interval is the resolution used in drawing the trends, not the actual interval between measurement cycles.
