DWL@DWL10000300334
| Verze | Jazyk | Operační systém | Datum | Velikost | Typ | Stáhnout |
|---|---|---|---|---|---|---|
| 1.6.5.0 | * | 27.02.2015 | 7 MB | EXE | AS3.0_HW_X20SL8000.exe | |
| Popis |
V3.0 HW Upgrade (X20SL8000) Revision information X20SL8000 Version 1.6.5.0: ID: 403855 enhaced behaviour in case of CPU redundancy switch enhaced behaviour in case of CPU redundancy switch Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 403860 SL stuck in POWERLINK status "PreOp2" during bootup It could happen sporadically that SafeLOGIC got stuck inPOWERLINK state "PreOp2" during bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 403865 SafeI/O modules stuck in PreOp state after AR restart Itcould happen sporadically that SafeI/O modules where stuck in PreOp afteronly AutomationRuntime (not SafeLOGIC) had been restarted. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 403870 logger message 122908 shall be generated only once for modules that are missing in AS configuration Logger message 122908 ("error asynchronous communication") is generated only once after startup for modules that are missing in the hardware configuration of AutomationStudio. This only applies for projects where hardware configurations of AutomationStudio and SafeDESIGNER do not match exactly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 403875 / Support ID: 400135568 problems after trying to access a not existing EPL object In rare cases the SafeLOGIC got stuck during bootup without logger message if the functional CPU calls EplSDORead for a not existing object. 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(300) Version 1.6.4.0: ID: 381720/ Support ID: 400101708 acknowledge SafeMC encoder via remote control Acknowledgement of a SafeMC encoder exchange was not possible via remote control Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 381725 / Support ID: 400101639 rarely failsafe during bootup It could happen very rarely that the SafeLOGIC entered failsafe state during bootup (entering logger numbers 98566 / 98565 / 99340) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 381735 / Support ID: 400117779 Logger message 122889 "time/date changed" SafeLOGIC generated 122889 "time/date changed" continuously under rare conditions. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 381740 / Support ID: 400108625 SafeLOGICstuck during bootup It happened rarely that the SafeLOGIC got stuck during bootup without generating any logger message. 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(299) Version 1.6.3.0: ID: 355530 maximum number of supported modules Since AS 4.0.15 the maximum number of supported modules was limited to 19 (instead of 20). Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 369915 SafeLOGICstuck during boot It could happen sporadically that the SafeLOGIC got stuck in POWERLINK state "PreOp 2" during boot. 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(297) 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 (AS 4.0 only) Channel description changed: No Configuration description changed: 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 axisid, 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 disturbancebehaviour<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 / 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 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 caseof 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 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 theSafeLOGIC.<br/>Channel description changed: No<br/>Configuration description changed: No<br/>Firmwarechanged: 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 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 could not 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 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 Channeldescription 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 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.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 wasnot 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 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 ID#219960: external machine options Possiblity to define 512 additional machine options via a file. Channel description changed: No Configuration description changed: No Firmware changed: 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 entries when 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-SL connection 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 that the 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 at POWERLINK object 0x2000/0x12 (data type: INT; scale: 0.1°C). Channeldescription 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.1.0: ID: 341995 Correction of cyclic memory tests Correction of cyclic memory tests Channel descriptionchanged: No Configuration description changed: No Firmware changed:Yes Firmware: 1\7616_1.fw(263), 2\7616_1.fw(275) 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/>Channeldescription changed: No<br/>Configuration description changed: No<br/>Firmware changed: Yes<br/><br/>ID: 181250<br/>loggerentries 122896 and 122895<br/>logger entries 122896 and 122895 had been generated though there was no error<br/>Channeldescription 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 behaviour of safety applicationhas been enhaced.<br/>Additional functionality for module parameter "Optional".<br/>New datapoint "SafeModuleOk" for each module.<br/>Seedocumentation 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 happened that 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 safetymodules 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 have been added to EPL-V2 object dictionary, which give 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 typeINT 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 in cold 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 / Support ID: 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 resettedanymore in case of an EPL reset (whatalso means 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/>Channeldescription 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 could happen in some projects (with morethan 92 safety modules).<br/>Channel description 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 'Error encountered 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.4.0: ID: 341990 Correction of cyclic memory tests Correction of cyclic memory tests Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\7616_1.fw(263) Version 1.1.3.0: ID: 272560 firmware supports hardware Rev. B0 olderfirmware 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 Firmware changed: No Firmware: 1\7616_1.fw(261) |
|||||
