ICS TRIPLEX T8312-4數字量輸入模塊,T8312-4產(chǎn)品顏色
無(wú)PROFIBUS丟失/添加停止模式下的故障現在記錄了“模塊丟失”和“模塊添加”故障當CPU處于停止模式時(shí)正確。從屬診斷狀態(tài)字從屬診斷狀態(tài)字現在僅提供以下地址：具有要報告的診斷消息的從屬設備。此狀態(tài)字否longer錯誤地報告了具有物理網(wǎng)絡(luò )錯誤。獲取設備診斷COMMREQ命令CPU366 Get Device Diagnostics現在返回標準診斷數據以及擴展診斷數據。這操作與其他PROFIBUS產(chǎn)品一致。COMMREQ響應內存數據類(lèi)型內存類(lèi)型現在可以用于PROFIBUS COMMREQ響應數據。
ICS TRIPLEX T8312-4數字量輸入模塊在以前的版本中，當使用與之相關(guān)聯(lián)的字節偏移段返回數內存類(lèi)型。該問(wèn)題已在1.02版中得到糾正。丟失/添加故障的格式輸入/輸出表設備丟失或設備故障增加的位置現在為在IO故障表中正確報告。此外，從機地址列在故障額外數據的字節5中。IO故障表中指示的參考地址始終顯示與PROFIBUS中最低配置從設備相關(guān)的參考網(wǎng)絡(luò )如果出現以下情況，則故障表中沒(méi)有故障PROFIBUS配置為拒絕如果在下載完成后，CPU366拒絕PROFIBUS配置完成后，自PROFIBUS固件1.02起，將出現以下故障：記錄“由于配置原因，無(wú)法將配置傳遞到模塊不匹配”。從屬狀態(tài)位將不會(huì )設置，LED模式將系統關(guān)閉，COM呈綠色閃爍。這表明PROFIBUS子板未配置。參考表的驗證帶COMMREQ返回的尺寸數據COMMREQ狀態(tài)字現在正確返回值4當在用于讀取的COMMREQ中使用了無(wú)效的內存引用類(lèi)型PROFIBUS信息。在以前的版本中，如果使用了無(wú)效的標識符，則不會(huì )顯示任何數據返回到引用表，但狀態(tài)字將指示OK（1）的值。額外“添加設備”故障在以前的版本中，報告了每個(gè)版本的“添加設備”故障下載后，PROFIBUS網(wǎng)絡(luò )配置中的設備或者在過(guò)渡到運行時(shí)。此問(wèn)題已在中更正版本1.02LED操作失敗中央處理器PROFIBUS Master LED現在正確指示網(wǎng)絡(luò )處于如果CPU主板出現故障，則清除模式。在這種情況下，電源的OK LED將熄滅，表示CPU不工作。ABB GSD文件和西門(mén)子SIMOCODE GSD文件不關(guān)于CPU366的工作在以前的版本中，下載包含一個(gè)或多個(gè)GSD文件的項目ABB從機（型號PDP22-FBP（V1））或西門(mén)子從機（型號SIMCODE）連接到CPU 366將導致COM LED指綠色閃爍，系統LED指示燈熄滅。既不是從位，也不是主位（在從狀態(tài)位陣列中）將被設置為開(kāi)啟，并且沒(méi)有故障記錄在故障表中。該問(wèn)題在版本1.02中得到糾正
PROFIBUS Issues Resolved by Revision 1.02
Subject Description
No PROFIBUS Loss/Add
Faults In stop mode
“Loss of module” and “Addition of module” faults are now logged
correctly when the CPU is in STOP mode.
Slave Diagnostic Status Word
The Slave Diagnostic Status Word now provides only the addresses of
slaves that have a diagnostic message to report. This status word no
longer erroneously reports the addresses of slaves that have a physical
network error.
Get Device Diagnostics
COMMREQ
The CPU366 Get Device Diagnostics now returns the standard
diagnostics data, as well as the extended diagnostic data. This
operation is consistent with other PROFIBUS products.
COMMREQ Response
Memory Data Types
The %I, %Q, %M and %T memory types can now be used for the
PROFIBUS COMMREQ response data.
In previous releases, the CPU366 did not use the offset correctly when
returning data using the BYTE offset segments associated with these
memory types. This problem has been corrected in release 1.02.
Format Of Loss/Add Faults In
the I/O Table
The location of a Loss Of Device or Addition Of Device fault is now
reported correctly in the IO Fault table.
In addition, the slave address is listed in byte 5 of the fault extra data.
The reference address indicated in the IO Fault table always shows the
reference associated with the lowest configured slave in the PROFIBUS
network.
No Fault In Fault Table If
PROFIBUS Configuration Is
Rejected
If the CPU366 rejects a PROFIBUS configuration after a download has
completed, as of PROFIBUS firmware 1.02, the following fault will be
logged “Unable to deliver configuration to module due to configuration
mismatch”. The slave status bits will not be set, and the LED pattern will
be SYS off, and COM blinking green. This indicates that the PROFIBUS
daughterboard is not configured.
Validation Of Reference Table
Sizes With COMMREQ Return
Data
The COMMREQ status word now correctly returns a value of 4
indicating “Command Terminated – invalid command data” when an
invalid memory reference type is used in a COMMREQ is used to read
PROFIBUS information.
In previous releases, if an invalid identifier was used, no data was
returned to the reference table yet the status word would indicate a
value of OK (1).
Extra “Addition of Device”
faults
In previous releases, an “Addition of Device” fault was reported for each
device in the PROFIBUS network configuration either after a download
or on the transition to run. This issue has been corrected in
release 1.02.
LED Operation With Failed
CPU
The PROFIBUS Master LEDs now correctly indicate the network is in
clear mode if the CPU motherboard fails.
In this situation, the power supply’s OK LED will be off, indicating the
CPU is non-operational.
ABB GSD file and SIEMENS
SIMOCODE GSD file do not
work on CPU366
In previous versions, downloading a project with one or more GSD files
for either an ABB slave (model PDP22-FBP (V1)) or Siemens slave
(model SIMCODE) to a CPU 366 would result in COM LED indicator
flashing green & SYS LED indicator off. Neither the slave bit, nor the
master bit (in the slave status bit array) would be set on and no fault was
logged in the fault table. This issue is corrected in version 1.02.
