DWL@DWL10000300336
Verze | Jazyk | Operační systém | Datum | Velikost | Typ | Stáhnout |
---|---|---|---|---|---|---|
1.6.5.0 | * | 27.02.2015 | 7 MB | EXE | AS3.0_HW_X20SL8001.exe | |
Popis |
V3.0 HW Upgrade (X20SL8001) Revision information X20SL8001 Version 1.6.5.0: ID: 388225 SL stuck in POWERLINK status "PreOp2" during bootup It could happen sporadically that SafeLOGIC got stuck in POWERLINK state "PreOp2" during bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 388300 / 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 ID: 399265 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: 399270 SafeI/O modules stuck in PreOp state after AR restart It could happen sporadically that SafeI/O modules where stuck in PreOp after only AutomationRuntime (not SafeLOGIC) had been restarted. Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 399290 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 Firmware: 2\7959_1.fw(275), 3\7959_1.fw(284), 4\7959_1.fw(300) Version 1.6.4.0: ID: 337650/ Support ID: 400108625 SafeLOGIC stuck during bootup It happened rarely that the SafeLOGIC got stuck during bootup without generating any loggermessage. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 347860 / 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: 352820 / 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: 369940 / 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 Firmware: 2\7959_1.fw(275), 3\7959_1.fw(284), 4\7959_1.fw(299) Version 1.6.3.0: ID: 352615 maximum number of supported modules Since AS 4.0.15 the maximum number of supported modules was limited to 99 (instead of 100). Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 364000 SafeLOGIC stuck 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\7959_1.fw(275), 3\7959_1.fw(284), 4\7959_1.fw(297) Version 1.6.2.0: ID: 338004 Correction of cyclic memory tests Correction of cyclic memory tests Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 2\7959_1.fw(275), 3\7959_1.fw(284), 4\7959_1.fw(296) Version 1.6.0.1: ID: 314760 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\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(295) Version 1.5.0.1: ID: 304120 Reestablish connection failed After a connection abort the device was notable to esablishe a connection again. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(295) Version 1.5.0.0: ID: 249115 no communication to SafeLOGIC with low cycle times Communication to SafeLOGIC was sometimes not possible when the cycle time in the SafeDESIGNER was <=1000µs and also EPL cycle time was accordinglylow. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 254995 / Support ID: 400063611 number of SCANs New parameter für the number of SCANs (e.g. at startup) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 256475 delete and re-insert SMC axis The axis id, that was generated when an axis was deleted and re-inserted inthe project, was not accepted by the SafeLOGIC in some cases. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 257985 Improved ethernet disturbance behaviour Sporadic SafeLOGIC reset due to ethernet disturbances. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 258685 / Support ID: 400065575 status bit "Scanning" The bit "Scanning" in the status response (remote control) toggled althoughthe SafeLOGIC was still scanning. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 259370 / Support ID: 400065174 failsafe with active SafeDESIGNER online connection Failsafe state of the SafeLOGIC could happen sporadically upon a SafeDESIGNER online connection that has been active for several minutes. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 259970 EPL V2:PRC and DNA Support of following EPL V2 functionalities: "Poll Response Chaining" and "Dynamic Node Allocation" Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 260735 / Support ID: 400066717 response behaviour of SL remote control Response behaviour of some SL remot control commands has been improved. Channel description changed: No Configuration description changed:No Firmware changed: Yes ID: 261681 firmware version in SDM The firmware version of the SafeLOGIC was not shown in the Module Details window of SDM Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 262190 Check for max. cycle time New parameter do define a maximum limit of the SL cycle time. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 264290 error "(0) instance number is invalid" Error "(0) instance number is invalid" (108548 / 112644) could occour in special configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 264465 Improved diagnosis in case of network problems New logger message (122908) that will be generated if sending of asynchronous packets fails (e.g. because of overload in asynchronous EPL channel) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 265425 logger entry "time/date changed" isgenerated too often. Logger entry 122889 is only generated if the time delta is more than 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 265525 default activate SPROXY The default value of the parameter "Activate SPROXY" changed from "off" to "on". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 267345/ Support ID: 400068135 behaviour when swapping an SIO module When swapping an SIO module between 2 slots (both belonging to the same SL), the SLsometimes did not signal a module exchange or didn't boot correctly. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 268920 / Support ID: 400072619 timeout SDO access remote control Timeouts of SDO accesses could happen when remote controlling the SafeLOGIC. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 269275 HTML formatted help Help files for this module come HTML formatted (instead of PDF). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 276585 / Support ID:400080281 SafeKEY data when replacing SafeLOGIC The data on the SafeKEY could get lost when replacing the SafeLOGIC hardware if new new hardware required a firmware update. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 279470 problems regarding SEL-FUB The SafeLOGIC could not boot correctly if the SafeDESIGNER application containted special function block diagram constructs with SEL-FUB. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 280855 SL doesn't switch to operational after AR reboot It could have happened sporadically that the SafeLOGIC couldn't receive SDOs anymore after an AR reboot (andtherefore didn't switch to operational). Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\7959_1.fw(262), 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(294) Version 1.4.1.92: ID: 262190 Check for max. cycle time New parameter do define a maximum limit of the SL cycle time. Channeldescription changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 1\7959_1.fw(262), 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(99) Version 1.4.1.1: ID: 251380 SL-to-SL connection Is not limited to 8 SAFEBOOL anymore (requires AS V3.0.90and AR V3.08) Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\7959_1.fw(262),2\7959_1.fw(271), 3\7959_1.fw(283) Version 1.4.0.0: 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 / Support ID: 400034396 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 B&R-CPU New parameters in I/O Configuration of SafeLOGIC: "SafeDESIGNER to SafeLOGIC communication"<br/>Therefore the SafeLOGIC can be accessedover a TCP port of AR (no IP route required anymore).<br/>(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)<br/>- logger entries with level "Info" or "Warning" are sent by only 1 of the 2 safety processors to reduce the number of messages. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 226665 / Support ID: 400041388 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).<br/>Additional logger entries when pressing the SafeLOGIC ENTER button. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 228885 / SupportID: 400043442 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. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 239700 / Support ID: 400051567 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.<br/>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 Firmware: 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(294) Version 1.3.0.0: ID: 198515 provide temperature Temperatureis provided at POWERLINK 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 Firmware: 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(294) Version 1.2.0.3: ID: 177345 'Authorisation' did not work Parameter 'Authorisation' in I/OConfiguration did not work (requires AR Q3.00 or higher!) Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\7959_1.fw(262), 2\7959_1.fw(271) Version 1.2.0.0: ID: 176055 no logger entry if SafeKEY missing a logger entry will be generated if the SafeKEY is missing Channel description changed: No Configuration description changed: No Firmware changed: No ID: 176350 improved diagnostics for connection problems Statistic counters (Objekte 0x2001/0x05..0x07) and logger entries (110434/114530) for improved diagnostic of cyclic safety data communication problems. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 181250 logger entries 122896 and 122895 logger entries 122896 and 122895 had been generated though there was no error Channel description changed: No Configuration description changed: No Firmware changed: No ID: 181260 / Support ID: 400012016 enhaced boot behaviour of safety application Boot behaviour of safety application has been enhaced.<br/>Additional functionality for module parameter "Optional".<br/>New datapoint "SafeModuleOk" for each module.<br/>See documentation for details. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 184795 / Support ID: 400008746 synchronous module startup It could have happened that safety modules where started delayed. Channeldescription changed: No Configuration description changed: No Firmware changed: No ID: 185125 faster starting of safety modules starting of safety modules by SL is done faster now Channel descriptionchanged: No Configuration description changed: No Firmware changed:No ID: 186085 / Support ID: 400008745 startup synchronisation SL / AR Improvements for startup synchronisation SL / AR Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 186245 extended diagnostics Additional diagnostic datapoint have been added to EPL-V2 object dictionary, which give information about the actual state of the SL. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 192500 / Support ID: . error "number of erroneous modules becomes negative" Internal error "number of erroneous modules becomes negative" could occour by mistake (error numbers 114691 and 118787 ) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 192925 / Support ID: 400013470 additional channels to/from CPU The max. number of BOOL-Channels to/from CPU has been increased.<br/>Channels of type INT have been added. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 198960 / Support ID: 400017890 operation in cold environment problems when operating in cold environment (0 .. 10°C) solved (loggerentries 99850 und 103946) Channel description changed: No Configuration description changed: No Firmware changed: No ID: 200045 / Support ID: 400019724 no connection to SafeLOGIC 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. Channel description changed: No Configuration descriptionchanged: No Firmware changed: No ID: 207500 SL is not resetted anymore For faster system bootup the SafeLOGIC is not resetted anymore in case of an EPL reset (what also means in case of an AR reboot). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 207505 increased number of machine options Number of SafeMachineOptions has been increased to 32. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 207515 flashing of FAIL-LEDs in case of debug mode Debug mode of the SafeLOGIC is displayed via alternating flashing of FAIL-LEDs. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 212455 / Support ID: 400028396 Problems with SafeMODULE ID > 100 Problems with SafeMODULE ID > 100 fixed. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 215470 / Support ID: 0 problems with SO modules in projects with a large amount of safety modules Problems with SO modules could happen in some projects (with more than 92 safety modules). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 217075 / Support ID: 400032288 logger entry "Error encountered while access file system on uPC!" Logger entry "Error encountered while access file system on uPC!" (100870) could happen at startup sporadically with certain projects. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 2\7959_1.fw(271), 3\7959_1.fw(283), 4\7959_1.fw(294) Version 1.1.3.0: ID: 182530 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: No Firmware: 1\7959_1.fw(262) Version 1.1.2.0: ID: 180905 first official release first official release Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\7959_1.fw(261) |