DWL@DWL10000064152
| Verze | Jazyk | Operační systém | Datum | Velikost | Typ | Stáhnout |
|---|---|---|---|---|---|---|
| 1.6.2.0 | * | 21.06.2013 | 7 MB | EXE | AS3.0_HW_X20SL8000.exe | |
| Popis |
V3.0 HW Upgrade (X20SL8000) Revision information X20SL8000 Version 1.6.2.0: ID: 340670 Correction of cyclic memory tests Correction of cyclic memory tests Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 2\7616_1.fw(275), 3\7616_1.fw(284), 4\7616_1.fw(296) Version 1.6.0.1: ID: 314765 Safety Release 1.6 Supports Safety Release 1.6 (AS4.0 only) Channel description changed: No Configuration descriptionchanged: Yes Firmware changed: No Firmware: 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(295) Version 1.5.0.1: ID: 304115 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\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(295) Version 1.5.0.0: ID: 180910 revision information for V1.5.0.0 See B&R homepage for correct formatted display of this text:<br/>ID: 249115<br/>no communication to SafeLOGIC with low cycle times<br/>Communication to 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 parameter für the number of SCANs (e.g. at startup)<br/>Channel description changed: No<br/>Configuration description changed: Yes<br/>Firmwarechanged: 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 reset due to ethernet disturbances.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 258685 / SupportID: 400065575<br/>status bit "Scanning"<br/>Thebit "Scanning" in the status response (remote control) toggled although the SafeLOGIC was still scanning.<br/>Channel description changed: No<br/>Configuration description changed: 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 thathas 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 number is 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 willbe generated if sending of asynchronous packets fails (e.g. because of overload in asynchronous EPL channel)<br/>Channel description changed: No<br/>Configuration description changed: 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 an SIO module<br/>When swapping an SIO module between 2 slots (both belonging to the same SL), the SL sometimes did not signal a module 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 datawhen replacing SafeLOGIC<br/>The data on the SafeKEY could getlost when replacing the SafeLOGIC hardware if new new hardware 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 couldnot boot correctly if the SafeDESIGNER application containted special function block diagram constructs with SEL-FUB.<br/>Channel description 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 have happened sporadicallythat the SafeLOGIC couldn't receive SDOs anymore after an AR reboot (and therefore didn't switch to operational).<br/>Channel descriptionchanged: No<br/>Configuration description changed: No<br/>Firmware changed: Yes Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(294) Version 1.4.1.97: ID: 180910 revision information for V1.5.0.0 see history of module X20SL8001 Channel descriptionchanged: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.4.1.1: ID: 272640 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: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.4.0.2: ID: 272675 revision information for V1.4.0.1 ID#176990: SafeKEY-LED was not activated for LED test. SafeKEY-LED was not activated for LED test. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#218995: reset after SafeKEAY format SafeLOGIC will be resetted automatically after a SafeKEY format. Channel description changed: No Configuration description changed: No Firmware changed: Yes Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.4.0.1: ID: 272600 revision informationfor V1.4.0.1 ID#176990: SafeKEY-LED was not activated for LED test. SafeKEY-LED was not activated for LED test. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#218995: reset after SafeKEAY format SafeLOGICwill be resetted automatically after a SafeKEY format. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#219960: external machine options Possiblity to define 512 additional machine options via a file. Channel description changed: No Configuration description changed: No Firmwarechanged: Yes ID#223460: online communication through BR-CPU New parameters in I/O Configuration of SafeLOGIC: "SafeDESIGNER to SafeLOGIC communication" Therefore the SafeLOGIC can be accessed over a TCP port of AR (no IP route required anymore). (requires AR A3.04 or higher !) Channel description changed: No Configuration description changed: Yes Firmware changed: No ID#225445: improvements logger entries - different levels for logger entires: "Info", "Warning" or "Error" (AR B3.05 required) - logger entries with level "Info" or "Warning" are sent by only 1 of the 2safety processors to reduce the number of messages. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#226665: format SafeKEY via operating elements Formatting the SafeKEY can be done via the operating elements of the SafeLOGIC. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#226755: Download application from functional CPU Possibility to download the SafeDESIGNER application from functional CPU toSafeLOGIC. Channel description changed: No Configuration description changed:No Firmware changed: Yes ID#226760: operate SL via EPL and additional logger entries. Possibility to operate the SafeLOGIC (e.g.FWACK) via EPL object dictionary (see manual). Additional logger entrieswhen pressing the SafeLOGIC ENTER button. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#228885: Error "Unexpected FSM event (00) occurred." Error "Unexpected FSM event (00) occurred." (108074/112170) could happen sporadically in case of AR warm restart. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#233580: SL-to-SL connection The parameters of a safe SL-to-SLconnection can be changed. The limit of 8 SAFEBOOL is not given anymore when using AS 3.0.90 and AR V3.08 Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID#239700: Error 108551 / 112647 Error 108551 / 112647 could happen sporadically under certain conditions. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#240700: Failsafe after reset With some projects the SafeLOGIC sporadically didn't boot correctly after an automatic reset (after FW-ACK or application download). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#245315: sporadic reset problems It happened sporadically that the SafeLOGIC didn't response after a reset. It happended sporadically thatthe SafeLOGIC was resetted in case of an AR restart. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID#248160: Problems when using new AR version in application with a lot of powerlink nodes. One could face problems when using actual AR version (e.g. V3.06) in applications with a lot of powerlink nodes. Channel description changed: No Configuration description changed: No Firmware changed: Yes Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.3.0.0: ID: 272615 revision information for V1.3.0.0 ID#198515: provide temperature Temperature is provided atPOWERLINK object 0x2000/0x12 (data type: INT; scale: 0.1°C). Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID#217100: SafeKEY acknowledge after firmware update After a firmware update (from Safety Release 1.1 to Safety Release 1.2) a SafeKEY acknowledgement was requested although the SafeKEY had not been changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.2.0.3: ID: 272585 revision information for V1.2.0.3 ID#177345: 'Authorisation' did not work Parameter 'Authorisation' in I/O Configuration did not work (requires AR Q3.00 or higher!) Channel description changed: No Configuration description changed: Yes Firmware changed: No ID#212694: changes in HWC fixed typos of safety parameters enabled for AR B2.96 Channel description changed: No Configuration description changed: Yes Firmware changed: No Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.2.0.0: ID: 272580 revision information for V1.2.0.0 See B&R homepage for correct formatted display of this text:<br/>ID: 176055<br/>no logger entry if SafeKEY missing<br/>a logger entry will be generated if the SafeKEY is missing<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 176350<br/>improved diagnostics for connection problems<br/>Statistic counters (Objekte 0x2001/0x05..0x07) and logger entries (110434/114530)for improved diagnostic of cyclic safety data communication problems.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 181250<br/>logger entries 122896 and 122895<br/>logger entries 122896 and 122895 had been generated though there was no error<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 181260 / Support ID: 400012016<br/>enhaced boot behaviour of safety application<br/>Boot behaviourof safety application has been enhaced.<br/>Additional functionality for module parameter "Optional".<br/>New datapoint"SafeModuleOk" for each module.<br/>See documentation for details.<br/>Channel description changed: Yes<br/>Configuration description changed: Yes<br/>Firmware changed: Yes<br/><br/>ID: 184795 / Support ID: 400008746<br/>synchronous module startup<br/>It could have happenedthat safety modules where started delayed.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 185125<br/>faster starting of safety modules<br/>starting of safety modules by SL is done faster now<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 186085 / Support ID: 400008745<br/>startup synchronisation SL /AR<br/>Improvements for startup synchronisation SL / AR<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 186245<br/>extended diagnostics<br/>Additional diagnostic datapoint havebeen added to EPL-V2 object dictionary, whichgive information about the actual state of the SL.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 192500 /Support ID: .<br/>error "number of erroneous modules becomes negative"<br/>Internal error "number of erroneous modules becomes negative" could occour by mistake (error numbers 114691 and 118787 )<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 192925 / Support ID: 400013470<br/>additional channels to/from CPU<br/>The max. number of BOOL-Channels to/from CPU has been increased.<br/>Channels of type INT have been added.<br/>Channel description changed: Yes<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 198960 / Support ID: 400017890<br/>operation in cold environment<br/>problems when operating incold environment (0 .. 10°C) solved (logger entries 99850 und 103946)<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 200045 / SupportID: 400019724<br/>no connection to SafeLOGIC<br/>If the SafeKEY contains corrupt data (might be caused by network failure during project download), it can happen that no connection between SafeDESIGNER and SafeLOGIC can be established.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 207500<br/>SL is not resetted anymore<br/>For faster system bootup the SafeLOGIC is not resetted anymore in case of an EPL reset (what alsomeans in case of an AR reboot).<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 207505<br/>increased number of machine options<br/>Number of SafeMachineOptions has been increased to 32.<br/>Channel description changed: Yes<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 207515<br/>flashing of FAIL-LEDs in case of debug mode<br/>Debug mode of the SafeLOGIC is displayed via alternating flashing of FAIL-LEDs.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 212455 / Support ID: 400028396<br/>Problems with SafeMODULE ID > 100<br/>Problems with SafeMODULE ID > 100 fixed.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmware changed: No<br/><br/>ID: 215470 / Support ID: 0<br/>problems with SO modules in projects with a large amount of safety modules<br/>Problems with SO modules couldhappen in some projects (with more than 92 safety modules).<br/>Channeldescription changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 217075 / Support ID: 400032288<br/>logger entry 'Error encountered while access file system on uPC!'<br/>Logger entry 'Errorencountered while access file system on uPC!'(100870) could happen at startupsporadically with certain projects.<br/>Channel descriptionchanged: No<br/>Configuration description changed:No<br/>Firmware changed: Yes<br/>Firmware: 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: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(294) Version 1.1.3.0: ID: 272560 firmware supports hardware Rev. B0 older firmware versions do not work correctly with hardware Rev. B0 or higher! Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\7616_1.fw(262), 2\7616_1.fw(271), 3\7616_1.fw(283), 4\7616_1.fw(105) Version 1.1.2.0: ID: 180900 first official release first official release Channel description changed: No Configuration description changed: No Firmwarechanged: No Firmware: 1\7616_1.fw(261) |
|||||
