V3.0 HW Upgrade (X20SL8010)

DWL@DWL10000103457

版本	语言	操作系统	日期	尺寸	类型	下载
1.6.2.0	*		06/21/2013	7 MB	EXE	AS3.0_HW_X20SL8010.exe
描述	V3.0 HW Upgrade (X20SL8010) Revision information X20SL8010 Version 1.6.2.0: ID: 340675 Correction of cyclic memory tests Correction of cyclic memory tests Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 2\43193_1.fw(274), 3\43193_1.fw(284), 4\43193_1.fw(296) Version 1.6.0.1: ID: 314770 Safety Release 1.6 Supports Safety Release 1.6 (AS 4.0 only) Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(295) Version 1.5.0.1: ID: 304125 Reestablish connection failed After a connection abort the device was not able to esablishe a connection again. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(295) Version 1.5.0.0: ID: 292640 revision information for V1.5.0.0 See B&R homepage for correct formatted display of this text:<br/><br/>ID: 249115<br/>no communication to SafeLOGIC with low cycle times<br/>Communicationto SafeLOGIC was sometimes not possible when the cycle time in the SafeDESIGNER was <=1000µs and also EPL cycle time was accordingly low.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 254995 / Support ID: 400063611<br/>number of SCANs<br/>New parameterfür the number of SCANs (e.g. at startup)<br/>Channel description changed: No<br/>Configuration description changed: Yes<br/>Firmware changed: Yes<br/><br/>ID: 256475<br/>delete and re-insert SMC axis<br/>The axis id, that was generated when an axis was deleted and re-inserted in the project, was not accepted by the SafeLOGIC in some cases.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 257985<br/>Improved ethernet disturbance behaviour<br/>Sporadic SafeLOGIC resetdue to ethernet disturbances.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 258685 / Support ID: 400065575<br/>status bit "Scanning"<br/>The bit "Scanning" in the status response (remote control) toggled although the SafeLOGIC was still scanning.<br/>Channel descriptionchanged: No<br/>Configuration descriptionchanged: No<br/>Firmware changed: Yes<br/><br/>ID: 259370 / Support ID: 400065174<br/>failsafe with active SafeDESIGNER online connection<br/>Failsafe state of the SafeLOGIC could happen sporadically upon a SafeDESIGNER online connection that has been active for several minutes.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 259970<br/>EPL V2: PRC and DNA<br/>Support of following EPL V2 functionalities: "Poll Response Chaining" and "Dynamic Node Allocation"<br/>Channel description changed: No<br/>Configuration description changed: Yes<br/>Firmware changed: Yes<br/><br/>ID: 260735 / Support ID: 400066717<br/>response behaviour of SL remote control<br/>Response behaviour of some SL remot control commands has been improved.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 261681<br/>firmware version in SDM<br/>The firmware version of the SafeLOGIC was not shown in the Module Details window of SDM<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 262190<br/>Check for max. cycle time<br/>New parameter do define a maximum limit of the SL cycle time.<br/>Channel description changed: No<br/>Configuration description changed: Yes<br/>Firmware changed: Yes<br/><br/>ID: 264290<br/>error "(0) instance number is invalid"<br/>Error "(0) instance numberis invalid" (108548 / 112644) could occour in special configurations.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 264465<br/>Improved diagnosis in case of network problems<br/>New logger message (122908) that will be generated if sending of asynchronous packets fails (e.g. because of overload in asynchronous EPL channel)<br/>Channel description changed: No<br/>Configuration descriptionchanged: No<br/>Firmware changed: Yes<br/><br/>ID: 265425<br/>logger entry "time/date changed" is generated too often.<br/>Logger entry 122889 is only generated if the time delta is more than 5s.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 265525<br/>default activate SPROXY<br/>The default value of the parameter "Activate SPROXY" changed from "off" to "on".<br/>Channel description changed: No<br/>Configuration description changed: Yes<br/>Firmware changed: No<br/><br/>ID: 267345 / Support ID: 400068135<br/>behaviour when swapping anSIO module<br/>When swapping an SIO module between 2 slots (both belonging to the same SL), the SL sometimes did not signal amodule exchange or didn't boot correctly.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 268920 / Support ID: 400072619<br/>timeout SDO access remote control<br/>Timeouts of SDO accesses could happen when remote controlling the SafeLOGIC.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed:Yes<br/><br/>ID: 269275<br/>HTML formatted help<br/>Help files for this module come HTML formatted (instead of PDF).<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 276585 / Support ID: 400080281<br/>SafeKEY data when replacing SafeLOGIC<br/>The data on the SafeKEY could get lost when replacing the SafeLOGIC hardware if new newhardware required a firmware update.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 279470<br/>problems regarding SEL-FUB<br/>The SafeLOGIC could not boot correctly if the SafeDESIGNER application containted special function block diagram constructs with SEL-FUB.<br/>Channeldescription changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 280855<br/>SL doesn't switch to operational after AR reboot<br/>It could havehappened sporadically that the SafeLOGIC couldn't receive SDOs anymore after an AR reboot (and therefore didn't switch to operational).<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/>Firmware: 1\7959_1.fw(262), 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(294) Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(294) Version 1.4.1.1: ID: 272625 Support SafeMC R1.4 Support SafeMC (8BVSVSAFE1-1) upgrade V1.4.0.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 272645 SL-to-SL connection Is not limited to 8 SAFEBOOL anymore (requires AS V3.0.90 and AR V3.08) Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(294) Version 1.4.0.0: ID: 272605 revision information for V1.4.0.0 See B&R homepage for correct formatted display of this text:<br/><br/>ID#176990: SafeKEY-LED was not activated for LED test.<br/>SafeKEY-LED was not activated for LED test.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#218995: reset after SafeKEAY format<br/>SafeLOGIC will be resetted automatically aftera SafeKEY format.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#219960: external machine options<br/>Possiblity to define 512additional machine options via a file.<br/>Channel description changed:No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#223460: online communication through BR-CPU<br/>New parameters in I/O Configuration of SafeLOGIC: "SafeDESIGNER to SafeLOGIC communication"<br/>Therefore the SafeLOGIC can be accessed over a TCP port of AR (no IP route required anymore).<br/>(requires AR A3.04 or higher !)<br/>Channel description changed: No<br/>Configuration description changed: Yes<br/>Firmware changed: No<br/><br/>ID#225445: improvements logger entries<br/>- different levels for logger entires: "Info", "Warning" or "Error" (AR B3.05 required)<br/>- logger entries with level "Info" or "Warning" are sent by only 1 of the 2 safety processors to reduce the number of messages.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#226665: format SafeKEY via operating elements<br/>Formatting the SafeKEY can be done via the operating elements ofthe SafeLOGIC.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#226755: Download application from functional CPU<br/>Possibility to download the SafeDESIGNER application from functional CPU to SafeLOGIC.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#226760: operate SL viaEPL and additional logger entries.<br/>Possibility to operate the SafeLOGIC (e.g. FWACK) via EPL object dictionary (see manual).<br/>Additionallogger entries when pressing the SafeLOGIC ENTER button.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#228885: Error "Unexpected FSM event (00) occurred."<br/>Error "Unexpected FSM event (00) occurred." (108074/112170) could happen sporadically in case of AR warm restart.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#233580: SL-to-SL connection<br/>The parameters of a safe SL-to-SL connection can be changed.<br/>The limit of 8 SAFEBOOL is not given anymore when using AS 3.0.90 and AR V3.08<br/>Channel description changed: Yes<br/>Configurationdescription changed: Yes<br/>Firmware changed: Yes<br/><br/>ID#239700: Error 108551 / 112647<br/>Error 108551 / 112647 could happensporadically under certain conditions.<br/>Channel description changed:No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#240700: Failsafe after reset<br/>With someprojects the SafeLOGIC sporadically didn't boot correctly after an automatic reset (after FW-ACK or application download).<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID#245315: sporadic reset problems<br/>It happened sporadically that the SafeLOGIC didn't response after a reset.<br/>It happended sporadically that the SafeLOGIC was resetted in case of anAR restart.<br/>Channel description changed: No<br/>Configurationdescription changed: No<br/>Firmware changed: Yes<br/><br/>ID#248160: Problems whenusing new AR version in application with a lot of powerlink nodes.<br/>One could face problems when using actual AR version (e.g. V3.06) in applications with a lot of powerlink nodes.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(294) Version 1.3.0.0: ID: 272590 Support SafeMC SafeMC is supported since Safety Release 1.3 .<br/>Requires SafeDESIGNER V2.71! Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(294) Version 1.2.0.0: ID: 212880 first official release first official release - identical to X20SL8000 (motion functions not yet supported) Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 2\43193_1.fw(273), 3\43193_1.fw(283), 4\43193_1.fw(294)