DWL@DWL10000567893
| Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
|---|---|---|---|---|---|---|
| 1.10.13.0 | * | 20/03/2024 | 6 Mo | EXE | AS4_HW_X20cSLX410.exe | |
| Description |
V4.1 HW Upgrade (X20cSLX410) Revision information X20cSLX410 Version 1.10.13.0: ID: 780205 Correction of the input filter with set "Filter off". Correction of the input filter, if a "Filter off" is set and a channel error is detected. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(340) Version 1.10.12.1: ID: 694335 Improvement of the internal voltage monitoring. Improvement of the internal voltage monitoring. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 694340 Loss of safety connection Loss of safety connection, even though the parametrized "safe data duration" is longer than the network failure Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(338) Version 1.10.10.5: ID: 670720 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.10.4: ID: 651425 new AR targets support new AR targets X20CPx68x and xPC22xx Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.10.3: ID: 626170 data sheet V1.141 See chapture "Version history" in the data sheet. i.a. calculation of Safety response time has been updated. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 637425 fix logger entry 123622 SLX didn't enter RUN state and logger number 123622 was entered when using 10 other safety modules. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.9.0: ID: 618245 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with large projects. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.5.0: ID: 582825 logger message 106773 Fix for logger message 106773 "Parameter checksum sizes do not match". Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(326) Version 1.10.4.1: ID: 585670 channel error when wired to +24V Temporary channel errors (logger entry 115011) are reported if If channels are wired to +24V during module bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589970 additional parameters Support additonal parameters (AsSafety FBK safeDownloadData_V2.Type=safeDATA_TYPE_ADDPARA); requires AR >= A04.41 ! Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589975 fix CLEAR DATA Not all relevant data has been deleted upon command "CLEAR DATA" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589980 logger entry 123432 fixed logger entry 123432 when using setup mode in combination with machine options Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589985 bootup time increase of bootup time with Upgrade V1.10.2.9 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589990 increased tolerance against asynchronous communication problems Problems in asynchronous communication to safety modules now cause the modules to be rated as "missing" not until the "Node Guarding Timeout" has expired (instead of after a few seconds) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589995 extended operating temperature range Firmware preparation for hardware revisions that allow operating temperature range down to -40°C. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(326) Version 1.10.3.2: ID: 549110 / Support ID: 400225917 Correction of SLX download frame Correction of SLX download frame Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.3.1: ID: 537600 logger message 110367 with external maschine options SLX did not boot correctly when using external machine options with upgrade V1.10.2.9 (logger message 110367 and others). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 537605 logger message 123416 when aknowledging a firmware mismatch The command for firmware acknowledgement was accepted although there was still a SCAN in progress. This could lead to a failure with logger message 123416. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.2.9: ID: 381670 / Support ID: 400132230 X20(c)SLX910: warn about invalid two channel processing mode X20(c)SLX910: SafeDESIGNER generates a warning during compile if a two-channel evaluation channel is used but the according parameter "Two Channel Processing Mode" is "none". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 481780 / Support ID: 400199480 error message about incompatible AR version Error message during AutomationStudio compile when trying to use Safety Release 1.10 with an AR version that is too old. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 494085 Improve SLX cycle time Performance optimization for improvement of internal SLX cycle time. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 494095 online help V1.103 Update online help to V1.103 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 502230 support Acopos P3 (X20SLX210 and X20SLX410 only) X20SLX210 and X20SLX410 support all variants of Acopos P3 (X20SLX910 supports 1 axis only) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 513925 / Support ID: 400193973, 400206803 SLXbootState 54 SLXbootState never reached value 54 "SafeRUN" although SLX booted correctly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 516045 fixes for parameters in SafeDESIGNER Minor text corrections. Remove obsolete parameter "Cycle time". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 521125 Adapt filter algorithm to eliminate dependencies between TON and TOF-filter Filter algorithm was adapted to eliminate dependencies between TON and TOF-filter which existed since FW V301. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522940 Error while downloading big SafeDESIGNER applications to the SLX. Download was aborted and the message "File Unlock Status: Error while writing unlock status!" was shown. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522945 Setup Mode and automated acknowledgements - Setup Mode is supported (requires SafeDESIGNER 4.3 and AutomationRuntime B4.26 or higher) - new parameters for automated acknowledgement of SafeKEY and firmware exchange. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 528960 SafeOS Status in SafeDESIGNER Remote Control It is a known issue that the SafeOS status in SafeDESIGNER remote control is not shown correctly when using certain versions. SafeDESIGNER SafePLC window or AsSafety can be used instead. This affects a set of following versions: SLX Upgrade >=V1.10.2.x, Safety Release 1.10, SafeDESIGNER >=V4.2.3 and AR B4.26 to C4.26 or C4.33 to E4.33 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.0.0: ID: 374990 / Support ID: 400129134 SafeDESIGNER communication Variable status Frequent activating/deactivating of SafeDESIGNER variable status could lead to failure of SLX communication. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 390095 / Support ID: 400137073 informations about actual application CRC and timestamp of the SafeDESIGNER application that is actually stored on the SLX can be read via asynchronous data points. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 411790 Support of release 1.10 including openSAFETY 1.5 Support of release 1.10 including openSAFETY 1.5 with easier parametrization of timing parameters Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 426855 / Support ID: 400151377 Optional modules no longer reported missing via SLX LEDs Channel description changed: No Configuration description changed: No Firmware changed: No ID: 440400 / Support ID: 400147709, 400160605, 400165854, 400175456 Input checksum data error In rare cases it could happen sporadically that the SLX entered failsafe state with "Input checksum data error" (logger messages 69648, 73744, 69655 und 73751) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448715 application download Performance optimization of application download to SLX. Some sequences have been changes for this which omitted some of the values of SLXbootState. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448980 / Support ID: 400162839, 400168358 limit of max 1 SLX per CPU / line integration If there are more then one SLX in the AS hardware tree, only one of them may be enabled. On the other hand now it is allowed to download a SafeDESIGNER application that doesn't match the SafeLOGIC-ID of the AS hardware tree. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(320) Version 1.9.2.0: ID: 446100 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 450770 / Support ID: 400137924 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313) Version 1.9.1.0: ID: 425280 change of input filter The behaviour of the input filter has changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 425285 Update Online Help Update Online Help V1.91 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 425290 fw valid from SafetyRelease 1.7 on The firmware is used for all SafetyReleases from 1.7 on. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 425300 Default values changed Default values of Cycle_Time_typical_us and Default_Max_X2X_CycleTime_us changed Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 4\57992_1.fw(313) Version 1.9.0.0: ID: 419175 The module also supports SafetyRelease 1.9 Starting with this version, the module also supports SafetyRelease 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 419185 Update Online Help Update Online Help V1.90 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\57992_1.fw(300), 2\57992_1.fw(311) Version 1.8.0.2: ID: 383120 / Support ID: 400129134 SafeDESIGNER communication minor enhacements for SafeDESIGNER <-> SLX communication Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383150 logger entry 114722 Logger entry 114722 could happen. SLX did not boot after this. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383155 logger entry if SLX remains in mode NoEXECUTION (SE double flash) SLX generates a new logger entry if it remains in mode NoEXECUTION during bootup, due to missing SafeModuleOk of a module. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383160 Limits SafeDESIGNER application The maximum number of markers as well as the maximum number of FB instances has both been increased from 128 to 256. The size of available marker memory has been decreased from 6k to 5k. Recompilation of SafeDESIGNER application is required. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 383165 logger entry 115011 "input error state has changed" logger entry 115011 "input error state has changed" was generated by mistake during bootup Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383170 logger entry 117269 "excessive X2X input data errors" Logger entry 117269 was generated by mistake upon each bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383175 / Support ID: 400125793 synchronization of cyclic communication does not work correctly for each bootup Synchronization of cyclic communication did not work correctly for each bootup if one of the cycle times in AS (X2X, EPL or cross link task) was higher than the internel SLX cycle time (800-1600µs). SLX got stuck in NoEXECUTION. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383180 failsafe mode and logger entries upon downloading a different project If a different project was downloaded to the SLX it could have happened that the SLX entered failsafe mode with diverse logger entries (e.g. 108571, 112694, 110405 oder 114502). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383185 / Support ID: 400129401 max. number of variables in variable status / logger message 77996 The maximum number of variables for SafeDESIGNER variable status has been increased from 64 to 128. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383190 data point "SLXioCycle" New data point "SLXioCycle" that holds the actual cycle time of data exchange SLX <-> CPU (requires AR H4.06 or higher) Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383195 SafeKEY format SafeKEY format command now also erases data from SLX (requires AR I4.06 or higher) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383200 Reset SafeLOGIC Command "Reset SafeLOGIC" didn't reset SLX immediately if it hadn't been in failsafe mode before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383205 / Support ID: 400130422 SL <-> SLX - communication enabled SL <-> SLX - communication Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383210 / Support ID: 400128242 logger message 117253 / 121349 logger messages 117253 / 121349 ("initial parameter check failed") with Info0=1 ("invalid UDID of SCMar") could occour with certain SLX hardware modules. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383215 / Support ID: 400131774 new password A new password request was shown by mistake if SLX had been in failsafe. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383220 SLX not available during startup If SLX was not responding during startup (e.g. missing 24V supply or failsafe state), the system wouldn't recover from this state except via restart. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383225 / Support ID: 400125030 state "Scanning" when using NotPresent flags State "Scanning" was never left when using SAGECOT_FLAGS_V1_TYP.NotPresent (FBK safeDownloadData() of AsSafety-Library) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383230 Problems with FW-ACKN Acknowledgement of firmware revision sometimes failed out. After that SK-XCHG and FW-ACKN had to be acknowledged again. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383235 SK-XCHG after exchange of SLX After exchange of SLX module acknowledgement of SK-XCHG was requested twice. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383240 / Support ID: 400132796 problems acknowledging UDIDs Acknowledgement of UDIDs was not possible (resulting in logger messages 99337 and 114701) if AR (respectively Windows in case of ARwin) had been running more than half an hour before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383245 wrong logger numbers of "SCM SW:" The system component "SCM SW:" generated following logger entries with wrong error numbers: 114721 instead of 114833 "internal error revision number", 114722 instead of 114834 "interner error SLX command channel", 114723 instead of 114835 "SLX in inaccessible state" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 389550 Update Online Help Update Online Help Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\57992_1.fw(300), 2\57992_1.fw(311) Version 1.7.0.2: ID: 351205 Known issues - activate option "Ignore data objects that are on target only" in AutomationStudio to avoid unintended deletion of internal safety data! - SafeDESIGNER "Variable status" supports a maximum of 64 variables (sum of variables in all open worksheets!). SLX will switch to error state if exceeding this amount. - after exchange of SLX hardware module the "SK-XCHG" must be acknowledged before a safety project download is possible (will abort with error "invalid UDID" otherwise). Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.1: ID: 347700 english help Help files where only available in german Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.0: ID: 347275 first official release first official release Safety Release 1.7 required Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\57992_1.fw(300) |
|||||
| Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
| 1.10.12.1 | * | 11/12/2020 | 6 Mo | EXE | AS4_HW_X20cSLX410.exe | |
| Description |
V4.1 HW Upgrade (X20cSLX410) Revision information X20SLXx1x Version 1.10.12.1: ID: 694335 Improvement of the internal voltage monitoring. Improvement of the internal voltage monitoring. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 694340 Loss of safety connection Loss of safety connection, even though the parametrized "safe data duration" is longer than the network failure Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(338) Version 1.10.10.5: ID: 670720 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.10.4: ID: 651425 new AR targets support new AR targets X20CPx68x and xPC22xx Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.10.3: ID: 626170 data sheet V1.141 See chapture "Version history" in the data sheet. i.a. calculation of Safety response time has been updated. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 637425 fix logger entry 123622 SLX didn't enter RUN state and logger number 123622 was entered when using 10 other safety modules. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.9.0: ID: 618245 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with large projects. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.5.0: ID: 582825 logger message 106773 Fix for logger message 106773 "Parameter checksum sizes do not match". Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(326) Version 1.10.4.1: ID: 585670 channel error when wired to +24V Temporary channel errors (logger entry 115011) are reported if If channels are wired to +24V during module bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589970 additional parameters Support additonal parameters (AsSafety FBK safeDownloadData_V2.Type=safeDATA_TYPE_ADDPARA); requires AR >= A04.41 ! Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589975 fix CLEAR DATA Not all relevant data has been deleted upon command "CLEAR DATA" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589980 logger entry 123432 fixed logger entry 123432 when using setup mode in combination with machine options Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589985 bootup time increase of bootup time with Upgrade V1.10.2.9 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589990 increased tolerance against asynchronous communication problems Problems in asynchronous communication to safety modules now cause the modules to be rated as "missing" not until the "Node Guarding Timeout" has expired (instead of after a few seconds) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589995 extended operating temperature range Firmware preparation for hardware revisions that allow operating temperature range down to -40°C. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(326) Version 1.10.3.2: ID: 549110 / Support ID: 400225917 Correction of SLX download frame Correction of SLX download frame Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.3.1: ID: 537600 logger message 110367 with external maschine options SLX did not boot correctly when using external machine options with upgrade V1.10.2.9 (logger message 110367 and others). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 537605 logger message 123416 when aknowledging a firmware mismatch The command for firmware acknowledgement was accepted although there was still a SCAN in progress. This could lead to a failure with logger message 123416. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.2.9: ID: 381670 / Support ID: 400132230 X20(c)SLX910: warn about invalid two channel processing mode X20(c)SLX910: SafeDESIGNER generates a warning during compile if a two-channel evaluation channel is used but the according parameter "Two Channel Processing Mode" is "none". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 481780 / Support ID: 400199480 error message about incompatible AR version Error message during AutomationStudio compile when trying to use Safety Release 1.10 with an AR version that is too old. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 494085 Improve SLX cycle time Performance optimization for improvement of internal SLX cycle time. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 494095 online help V1.103 Update online help to V1.103 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 502230 support Acopos P3 (X20SLX210 and X20SLX410 only) X20SLX210 and X20SLX410 support all variants of Acopos P3 (X20SLX910 supports 1 axis only) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 513925 / Support ID: 400193973, 400206803 SLXbootState 54 SLXbootState never reached value 54 "SafeRUN" although SLX booted correctly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 516045 fixes for parameters in SafeDESIGNER Minor text corrections. Remove obsolete parameter "Cycle time". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 521125 Adapt filter algorithm to eliminate dependencies between TON and TOF-filter Filter algorithm was adapted to eliminate dependencies between TON and TOF-filter which existed since FW V301. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522940 Error while downloading big SafeDESIGNER applications to the SLX. Download was aborted and the message "File Unlock Status: Error while writing unlock status!" was shown. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522945 Setup Mode and automated acknowledgements - Setup Mode is supported (requires SafeDESIGNER 4.3 and AutomationRuntime B4.26 or higher) - new parameters for automated acknowledgement of SafeKEY and firmware exchange. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 528960 SafeOS Status in SafeDESIGNER Remote Control It is a known issue that the SafeOS status in SafeDESIGNER remote control is not shown correctly when using certain versions. SafeDESIGNER SafePLC window or AsSafety can be used instead. This affects a set of following versions: SLX Upgrade >=V1.10.2.x, Safety Release 1.10, SafeDESIGNER >=V4.2.3 and AR B4.26 to C4.26 or C4.33 to E4.33 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.0.0: ID: 374990 / Support ID: 400129134 SafeDESIGNER communication Variable status Frequent activating/deactivating of SafeDESIGNER variable status could lead to failure of SLX communication. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 390095 / Support ID: 400137073 informations about actual application CRC and timestamp of the SafeDESIGNER application that is actually stored on the SLX can be read via asynchronous data points. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 411790 Support of release 1.10 including openSAFETY 1.5 Support of release 1.10 including openSAFETY 1.5 with easier parametrization of timing parameters Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 426855 / Support ID: 400151377 Optional modules no longer reported missing via SLX LEDs Channel description changed: No Configuration description changed: No Firmware changed: No ID: 440400 / Support ID: 400147709, 400160605, 400165854, 400175456 Input checksum data error In rare cases it could happen sporadically that the SLX entered failsafe state with "Input checksum data error" (logger messages 69648, 73744, 69655 und 73751) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448715 application download Performance optimization of application download to SLX. Some sequences have been changes for this which omitted some of the values of SLXbootState. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448980 / Support ID: 400162839, 400168358 limit of max 1 SLX per CPU / line integration If there are more then one SLX in the AS hardware tree, only one of them may be enabled. On the other hand now it is allowed to download a SafeDESIGNER application that doesn't match the SafeLOGIC-ID of the AS hardware tree. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(320) Version 1.9.2.0: ID: 446100 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 450770 / Support ID: 400137924 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313) Version 1.9.1.0: ID: 425280 change of input filter The behaviour of the input filter has changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 425285 Update Online Help Update Online Help V1.91 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 425290 fw valid from SafetyRelease 1.7 on The firmware is used for all SafetyReleases from 1.7 on. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 425300 Default values changed Default values of Cycle_Time_typical_us and Default_Max_X2X_CycleTime_us changed Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313) Version 1.9.0.0: ID: 419175 The module also supports SafetyRelease 1.9 Starting with this version, the module also supports SafetyRelease 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 419185 Update Online Help Update Online Help V1.90 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50608_1.fw(300), 2\50608_1.fw(311) Version 1.8.0.2: ID: 383120 / Support ID: 400129134 SafeDESIGNER communication minor enhacements for SafeDESIGNER <-> SLX communication Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383150 logger entry 114722 Logger entry 114722 could happen. SLX did not boot after this. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383155 logger entry if SLX remains in mode NoEXECUTION (SE double flash) SLX generates a new logger entry if it remains in mode NoEXECUTION during bootup, due to missing SafeModuleOk of a module. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383160 Limits SafeDESIGNER application The maximum number of markers as well as the maximum number of FB instances has both been increased from 128 to 256. The size of available marker memory has been decreased from 6k to 5k. Recompilation of SafeDESIGNER application is required. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 383165 logger entry 115011 "input error state has changed" logger entry 115011 "input error state has changed" was generated by mistake during bootup Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383170 logger entry 117269 "excessive X2X input data errors" Logger entry 117269 was generated by mistake upon each bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383175 / Support ID: 400125793 synchronization of cyclic communication does not work correctly for each bootup Synchronization of cyclic communication did not work correctly for each bootup if one of the cycle times in AS (X2X, EPL or cross link task) was higher than the internel SLX cycle time (800-1600µs). SLX got stuck in NoEXECUTION. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383180 failsafe mode and logger entries upon downloading a different project If a different project was downloaded to the SLX it could have happened that the SLX entered failsafe mode with diverse logger entries (e.g. 108571, 112694, 110405 oder 114502). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383185 / Support ID: 400129401 max. number of variables in variable status / logger message 77996 The maximum number of variables for SafeDESIGNER variable status has been increased from 64 to 128. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383190 data point "SLXioCycle" New data point "SLXioCycle" that holds the actual cycle time of data exchange SLX <-> CPU (requires AR H4.06 or higher) Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383195 SafeKEY format SafeKEY format command now also erases data from SLX (requires AR I4.06 or higher) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383200 Reset SafeLOGIC Command "Reset SafeLOGIC" didn't reset SLX immediately if it hadn't been in failsafe mode before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383205 / Support ID: 400130422 SL <-> SLX - communication enabled SL <-> SLX - communication Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383210 / Support ID: 400128242 logger message 117253 / 121349 logger messages 117253 / 121349 ("initial parameter check failed") with Info0=1 ("invalid UDID of SCMar") could occour with certain SLX hardware modules. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383215 / Support ID: 400131774 new password A new password request was shown by mistake if SLX had been in failsafe. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383220 SLX not available during startup If SLX was not responding during startup (e.g. missing 24V supply or failsafe state), the system wouldn't recover from this state except via restart. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383225 / Support ID: 400125030 state "Scanning" when using NotPresent flags State "Scanning" was never left when using SAGECOT_FLAGS_V1_TYP.NotPresent (FBK safeDownloadData() of AsSafety-Library) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383230 Problems with FW-ACKN Acknowledgement of firmware revision sometimes failed out. After that SK-XCHG and FW-ACKN had to be acknowledged again. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383235 SK-XCHG after exchange of SLX After exchange of SLX module acknowledgement of SK-XCHG was requested twice. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383240 / Support ID: 400132796 problems acknowledging UDIDs Acknowledgement of UDIDs was not possible (resulting in logger messages 99337 and 114701) if AR (respectively Windows in case of ARwin) had been running more than half an hour before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383245 wrong logger numbers of "SCM SW:" The system component "SCM SW:" generated following logger entries with wrong error numbers: 114721 instead of 114833 "internal error revision number", 114722 instead of 114834 "interner error SLX command channel", 114723 instead of 114835 "SLX in inaccessible state" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 389550 Update Online Help Update Online Help Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50608_1.fw(300), 2\50608_1.fw(311) Version 1.7.0.2: ID: 351205 Known issues - activate option "Ignore data objects that are on target only" in AutomationStudio to avoid unintended deletion of internal safety data! - SafeDESIGNER "Variable status" supports a maximum of 64 variables (sum of variables in all open worksheets!). SLX will switch to error state if exceeding this amount. - after exchange of SLX hardware module the "SK-XCHG" must be acknowledged before a safety project download is possible (will abort with error "invalid UDID" otherwise). Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.1: ID: 347700 english help Help files where only available in german Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.0: ID: 347275 first official release first official release Safety Release 1.7 required Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\50608_1.fw(300) |
|||||
| Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
| 1.10.10.5 | * | 25/03/2020 | 6 Mo | EXE | AS4_HW_X20cSLX410.exe | |
| Description |
V4.1 HW Upgrade (X20cSLX410) Revision information X20SLXx1x Version 1.10.10.5: ID: 670720 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.10.4: ID: 651425 new AR targets support new AR targets X20CPx68x and xPC22xx Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.10.3: ID: 626170 data sheet V1.141 See chapture "Version history" in the data sheet. i.a. calculation of Safety response time has been updated. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 637425 fix logger entry 123622 SLX didn't enter RUN state and logger number 123622 was entered when using 10 other safety modules. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.9.0: ID: 618245 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with large projects. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.5.0: ID: 582825 logger message 106773 Fix for logger message 106773 "Parameter checksum sizes do not match". Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(326) Version 1.10.4.1: ID: 585670 channel error when wired to +24V Temporary channel errors (logger entry 115011) are reported if If channels are wired to +24V during module bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589970 additional parameters Support additonal parameters (AsSafety FBK safeDownloadData_V2.Type=safeDATA_TYPE_ADDPARA); requires AR >= A04.41 ! Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589975 fix CLEAR DATA Not all relevant data has been deleted upon command "CLEAR DATA" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589980 logger entry 123432 fixed logger entry 123432 when using setup mode in combination with machine options Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589985 bootup time increase of bootup time with Upgrade V1.10.2.9 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589990 increased tolerance against asynchronous communication problems Problems in asynchronous communication to safety modules now cause the modules to be rated as "missing" not until the "Node Guarding Timeout" has expired (instead of after a few seconds) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589995 extended operating temperature range Firmware preparation for hardware revisions that allow operating temperature range down to -40°C. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(326) Version 1.10.3.2: ID: 549110 / Support ID: 400225917 Correction of SLX download frame Correction of SLX download frame Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.3.1: ID: 537600 logger message 110367 with external maschine options SLX did not boot correctly when using external machine options with upgrade V1.10.2.9 (logger message 110367 and others). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 537605 logger message 123416 when aknowledging a firmware mismatch The command for firmware acknowledgement was accepted although there was still a SCAN in progress. This could lead to a failure with logger message 123416. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.2.9: ID: 381670 / Support ID: 400132230 X20(c)SLX910: warn about invalid two channel processing mode X20(c)SLX910: SafeDESIGNER generates a warning during compile if a two-channel evaluation channel is used but the according parameter "Two Channel Processing Mode" is "none". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 481780 / Support ID: 400199480 error message about incompatible AR version Error message during AutomationStudio compile when trying to use Safety Release 1.10 with an AR version that is too old. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 494085 Improve SLX cycle time Performance optimization for improvement of internal SLX cycle time. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 494095 online help V1.103 Update online help to V1.103 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 502230 support Acopos P3 (X20SLX210 and X20SLX410 only) X20SLX210 and X20SLX410 support all variants of Acopos P3 (X20SLX910 supports 1 axis only) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 513925 / Support ID: 400193973, 400206803 SLXbootState 54 SLXbootState never reached value 54 "SafeRUN" although SLX booted correctly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 516045 fixes for parameters in SafeDESIGNER Minor text corrections. Remove obsolete parameter "Cycle time". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 521125 Adapt filter algorithm to eliminate dependencies between TON and TOF-filter Filter algorithm was adapted to eliminate dependencies between TON and TOF-filter which existed since FW V301. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522940 Error while downloading big SafeDESIGNER applications to the SLX. Download was aborted and the message "File Unlock Status: Error while writing unlock status!" was shown. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522945 Setup Mode and automated acknowledgements - Setup Mode is supported (requires SafeDESIGNER 4.3 and AutomationRuntime B4.26 or higher) - new parameters for automated acknowledgement of SafeKEY and firmware exchange. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 528960 SafeOS Status in SafeDESIGNER Remote Control It is a known issue that the SafeOS status in SafeDESIGNER remote control is not shown correctly when using certain versions. SafeDESIGNER SafePLC window or AsSafety can be used instead. This affects a set of following versions: SLX Upgrade >=V1.10.2.x, Safety Release 1.10, SafeDESIGNER >=V4.2.3 and AR B4.26 to C4.26 or C4.33 to E4.33 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.0.0: ID: 374990 / Support ID: 400129134 SafeDESIGNER communication Variable status Frequent activating/deactivating of SafeDESIGNER variable status could lead to failure of SLX communication. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 390095 / Support ID: 400137073 informations about actual application CRC and timestamp of the SafeDESIGNER application that is actually stored on the SLX can be read via asynchronous data points. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 411790 Support of release 1.10 including openSAFETY 1.5 Support of release 1.10 including openSAFETY 1.5 with easier parametrization of timing parameters Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 426855 / Support ID: 400151377 Optional modules no longer reported missing via SLX LEDs Channel description changed: No Configuration description changed: No Firmware changed: No ID: 440400 / Support ID: 400147709, 400160605, 400165854, 400175456 Input checksum data error In rare cases it could happen sporadically that the SLX entered failsafe state with "Input checksum data error" (logger messages 69648, 73744, 69655 und 73751) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448715 application download Performance optimization of application download to SLX. Some sequences have been changes for this which omitted some of the values of SLXbootState. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448980 / Support ID: 400162839, 400168358 limit of max 1 SLX per CPU / line integration If there are more then one SLX in the AS hardware tree, only one of them may be enabled. On the other hand now it is allowed to download a SafeDESIGNER application that doesn't match the SafeLOGIC-ID of the AS hardware tree. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(320) Version 1.9.2.0: ID: 446100 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 450770 / Support ID: 400137924 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313) Version 1.9.1.0: ID: 425280 change of input filter The behaviour of the input filter has changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 425285 Update Online Help Update Online Help V1.91 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 425290 fw valid from SafetyRelease 1.7 on The firmware is used for all SafetyReleases from 1.7 on. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 425300 Default values changed Default values of Cycle_Time_typical_us and Default_Max_X2X_CycleTime_us changed Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313) Version 1.9.0.0: ID: 419175 The module also supports SafetyRelease 1.9 Starting with this version, the module also supports SafetyRelease 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 419185 Update Online Help Update Online Help V1.90 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50608_1.fw(300), 2\50608_1.fw(311) Version 1.8.0.2: ID: 383120 / Support ID: 400129134 SafeDESIGNER communication minor enhacements for SafeDESIGNER <-> SLX communication Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383150 logger entry 114722 Logger entry 114722 could happen. SLX did not boot after this. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383155 logger entry if SLX remains in mode NoEXECUTION (SE double flash) SLX generates a new logger entry if it remains in mode NoEXECUTION during bootup, due to missing SafeModuleOk of a module. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383160 Limits SafeDESIGNER application The maximum number of markers as well as the maximum number of FB instances has both been increased from 128 to 256. The size of available marker memory has been decreased from 6k to 5k. Recompilation of SafeDESIGNER application is required. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 383165 logger entry 115011 "input error state has changed" logger entry 115011 "input error state has changed" was generated by mistake during bootup Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383170 logger entry 117269 "excessive X2X input data errors" Logger entry 117269 was generated by mistake upon each bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383175 / Support ID: 400125793 synchronization of cyclic communication does not work correctly for each bootup Synchronization of cyclic communication did not work correctly for each bootup if one of the cycle times in AS (X2X, EPL or cross link task) was higher than the internel SLX cycle time (800-1600µs). SLX got stuck in NoEXECUTION. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383180 failsafe mode and logger entries upon downloading a different project If a different project was downloaded to the SLX it could have happened that the SLX entered failsafe mode with diverse logger entries (e.g. 108571, 112694, 110405 oder 114502). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383185 / Support ID: 400129401 max. number of variables in variable status / logger message 77996 The maximum number of variables for SafeDESIGNER variable status has been increased from 64 to 128. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383190 data point "SLXioCycle" New data point "SLXioCycle" that holds the actual cycle time of data exchange SLX <-> CPU (requires AR H4.06 or higher) Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383195 SafeKEY format SafeKEY format command now also erases data from SLX (requires AR I4.06 or higher) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383200 Reset SafeLOGIC Command "Reset SafeLOGIC" didn't reset SLX immediately if it hadn't been in failsafe mode before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383205 / Support ID: 400130422 SL <-> SLX - communication enabled SL <-> SLX - communication Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383210 / Support ID: 400128242 logger message 117253 / 121349 logger messages 117253 / 121349 ("initial parameter check failed") with Info0=1 ("invalid UDID of SCMar") could occour with certain SLX hardware modules. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383215 / Support ID: 400131774 new password A new password request was shown by mistake if SLX had been in failsafe. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383220 SLX not available during startup If SLX was not responding during startup (e.g. missing 24V supply or failsafe state), the system wouldn't recover from this state except via restart. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383225 / Support ID: 400125030 state "Scanning" when using NotPresent flags State "Scanning" was never left when using SAGECOT_FLAGS_V1_TYP.NotPresent (FBK safeDownloadData() of AsSafety-Library) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383230 Problems with FW-ACKN Acknowledgement of firmware revision sometimes failed out. After that SK-XCHG and FW-ACKN had to be acknowledged again. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383235 SK-XCHG after exchange of SLX After exchange of SLX module acknowledgement of SK-XCHG was requested twice. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383240 / Support ID: 400132796 problems acknowledging UDIDs Acknowledgement of UDIDs was not possible (resulting in logger messages 99337 and 114701) if AR (respectively Windows in case of ARwin) had been running more than half an hour before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383245 wrong logger numbers of "SCM SW:" The system component "SCM SW:" generated following logger entries with wrong error numbers: 114721 instead of 114833 "internal error revision number", 114722 instead of 114834 "interner error SLX command channel", 114723 instead of 114835 "SLX in inaccessible state" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 389550 Update Online Help Update Online Help Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50608_1.fw(300), 2\50608_1.fw(311) Version 1.7.0.2: ID: 351205 Known issues - activate option "Ignore data objects that are on target only" in AutomationStudio to avoid unintended deletion of internal safety data! - SafeDESIGNER "Variable status" supports a maximum of 64 variables (sum of variables in all open worksheets!). SLX will switch to error state if exceeding this amount. - after exchange of SLX hardware module the "SK-XCHG" must be acknowledged before a safety project download is possible (will abort with error "invalid UDID" otherwise). Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.1: ID: 347700 english help Help files where only available in german Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.0: ID: 347275 first official release first official release Safety Release 1.7 required Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\50608_1.fw(300) |
|||||
| Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
| 1.10.10.4 | * | 30/09/2019 | 6 Mo | EXE | AS4_HW_X20cSLX410.exe | |
| Description |
V4.1 HW Upgrade (X20cSLX410) Revision information X20SLXx1x Version 1.10.10.4: ID: 651425 new AR targets support new AR targets X20CPx68x and xPC22xx Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.10.3: ID: 626170 data sheet V1.141 See chapture "Version history" in the data sheet. i.a. calculation of Safety response time has been updated. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 637425 fix logger entry 123622 SLX didn't enter RUN state and logger number 123622 was entered when using 10 other safety modules. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.9.0: ID: 618245 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with large projects. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(330) Version 1.10.5.0: ID: 582825 logger message 106773 Fix for logger message 106773 "Parameter checksum sizes do not match". Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(326) Version 1.10.4.1: ID: 585670 channel error when wired to +24V Temporary channel errors (logger entry 115011) are reported if If channels are wired to +24V during module bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589970 additional parameters Support additonal parameters (AsSafety FBK safeDownloadData_V2.Type=safeDATA_TYPE_ADDPARA); requires AR >= A04.41 ! Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589975 fix CLEAR DATA Not all relevant data has been deleted upon command "CLEAR DATA" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589980 logger entry 123432 fixed logger entry 123432 when using setup mode in combination with machine options Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589985 bootup time increase of bootup time with Upgrade V1.10.2.9 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589990 increased tolerance against asynchronous communication problems Problems in asynchronous communication to safety modules now cause the modules to be rated as "missing" not until the "Node Guarding Timeout" has expired (instead of after a few seconds) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589995 extended operating temperature range Firmware preparation for hardware revisions that allow operating temperature range down to -40°C. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(326) Version 1.10.3.2: ID: 549110 / Support ID: 400225917 Correction of SLX download frame Correction of SLX download frame Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.3.1: ID: 537600 logger message 110367 with external maschine options SLX did not boot correctly when using external machine options with upgrade V1.10.2.9 (logger message 110367 and others). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 537605 logger message 123416 when aknowledging a firmware mismatch The command for firmware acknowledgement was accepted although there was still a SCAN in progress. This could lead to a failure with logger message 123416. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.2.9: ID: 381670 / Support ID: 400132230 X20(c)SLX910: warn about invalid two channel processing mode X20(c)SLX910: SafeDESIGNER generates a warning during compile if a two-channel evaluation channel is used but the according parameter "Two Channel Processing Mode" is "none". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 481780 / Support ID: 400199480 error message about incompatible AR version Error message during AutomationStudio compile when trying to use Safety Release 1.10 with an AR version that is too old. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 494085 Improve SLX cycle time Performance optimization for improvement of internal SLX cycle time. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 494095 online help V1.103 Update online help to V1.103 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 502230 support Acopos P3 (X20SLX210 and X20SLX410 only) X20SLX210 and X20SLX410 support all variants of Acopos P3 (X20SLX910 supports 1 axis only) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 513925 / Support ID: 400193973, 400206803 SLXbootState 54 SLXbootState never reached value 54 "SafeRUN" although SLX booted correctly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 516045 fixes for parameters in SafeDESIGNER Minor text corrections. Remove obsolete parameter "Cycle time". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 521125 Adapt filter algorithm to eliminate dependencies between TON and TOF-filter Filter algorithm was adapted to eliminate dependencies between TON and TOF-filter which existed since FW V301. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522940 Error while downloading big SafeDESIGNER applications to the SLX. Download was aborted and the message "File Unlock Status: Error while writing unlock status!" was shown. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522945 Setup Mode and automated acknowledgements - Setup Mode is supported (requires SafeDESIGNER 4.3 and AutomationRuntime B4.26 or higher) - new parameters for automated acknowledgement of SafeKEY and firmware exchange. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 528960 SafeOS Status in SafeDESIGNER Remote Control It is a known issue that the SafeOS status in SafeDESIGNER remote control is not shown correctly when using certain versions. SafeDESIGNER SafePLC window or AsSafety can be used instead. This affects a set of following versions: SLX Upgrade >=V1.10.2.x, Safety Release 1.10, SafeDESIGNER >=V4.2.3 and AR B4.26 to C4.26 or C4.33 to E4.33 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(324) Version 1.10.0.0: ID: 374990 / Support ID: 400129134 SafeDESIGNER communication Variable status Frequent activating/deactivating of SafeDESIGNER variable status could lead to failure of SLX communication. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 390095 / Support ID: 400137073 informations about actual application CRC and timestamp of the SafeDESIGNER application that is actually stored on the SLX can be read via asynchronous data points. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 411790 Support of release 1.10 including openSAFETY 1.5 Support of release 1.10 including openSAFETY 1.5 with easier parametrization of timing parameters Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 426855 / Support ID: 400151377 Optional modules no longer reported missing via SLX LEDs Channel description changed: No Configuration description changed: No Firmware changed: No ID: 440400 / Support ID: 400147709, 400160605, 400165854, 400175456 Input checksum data error In rare cases it could happen sporadically that the SLX entered failsafe state with "Input checksum data error" (logger messages 69648, 73744, 69655 und 73751) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448715 application download Performance optimization of application download to SLX. Some sequences have been changes for this which omitted some of the values of SLXbootState. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448980 / Support ID: 400162839, 400168358 limit of max 1 SLX per CPU / line integration If there are more then one SLX in the AS hardware tree, only one of them may be enabled. On the other hand now it is allowed to download a SafeDESIGNER application that doesn't match the SafeLOGIC-ID of the AS hardware tree. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313), 5\50608_1.fw(320) Version 1.9.2.0: ID: 446100 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 450770 / Support ID: 400137924 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313) Version 1.9.1.0: ID: 425280 change of input filter The behaviour of the input filter has changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 425285 Update Online Help Update Online Help V1.91 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 425290 fw valid from SafetyRelease 1.7 on The firmware is used for all SafetyReleases from 1.7 on. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 425300 Default values changed Default values of Cycle_Time_typical_us and Default_Max_X2X_CycleTime_us changed Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 3\50608_1.fw(302), 4\50608_1.fw(313) Version 1.9.0.0: ID: 419175 The module also supports SafetyRelease 1.9 Starting with this version, the module also supports SafetyRelease 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 419185 Update Online Help Update Online Help V1.90 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50608_1.fw(300), 2\50608_1.fw(311) Version 1.8.0.2: ID: 383120 / Support ID: 400129134 SafeDESIGNER communication minor enhacements for SafeDESIGNER <-> SLX communication Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383150 logger entry 114722 Logger entry 114722 could happen. SLX did not boot after this. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383155 logger entry if SLX remains in mode NoEXECUTION (SE double flash) SLX generates a new logger entry if it remains in mode NoEXECUTION during bootup, due to missing SafeModuleOk of a module. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383160 Limits SafeDESIGNER application The maximum number of markers as well as the maximum number of FB instances has both been increased from 128 to 256. The size of available marker memory has been decreased from 6k to 5k. Recompilation of SafeDESIGNER application is required. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 383165 logger entry 115011 "input error state has changed" logger entry 115011 "input error state has changed" was generated by mistake during bootup Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383170 logger entry 117269 "excessive X2X input data errors" Logger entry 117269 was generated by mistake upon each bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383175 / Support ID: 400125793 synchronization of cyclic communication does not work correctly for each bootup Synchronization of cyclic communication did not work correctly for each bootup if one of the cycle times in AS (X2X, EPL or cross link task) was higher than the internel SLX cycle time (800-1600µs). SLX got stuck in NoEXECUTION. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383180 failsafe mode and logger entries upon downloading a different project If a different project was downloaded to the SLX it could have happened that the SLX entered failsafe mode with diverse logger entries (e.g. 108571, 112694, 110405 oder 114502). Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383185 / Support ID: 400129401 max. number of variables in variable status / logger message 77996 The maximum number of variables for SafeDESIGNER variable status has been increased from 64 to 128. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383190 data point "SLXioCycle" New data point "SLXioCycle" that holds the actual cycle time of data exchange SLX <-> CPU (requires AR H4.06 or higher) Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383195 SafeKEY format SafeKEY format command now also erases data from SLX (requires AR I4.06 or higher) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383200 Reset SafeLOGIC Command "Reset SafeLOGIC" didn't reset SLX immediately if it hadn't been in failsafe mode before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383205 / Support ID: 400130422 SL <-> SLX - communication enabled SL <-> SLX - communication Channel description changed: Yes Configuration description changed: No Firmware changed: No ID: 383210 / Support ID: 400128242 logger message 117253 / 121349 logger messages 117253 / 121349 ("initial parameter check failed") with Info0=1 ("invalid UDID of SCMar") could occour with certain SLX hardware modules. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383215 / Support ID: 400131774 new password A new password request was shown by mistake if SLX had been in failsafe. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383220 SLX not available during startup If SLX was not responding during startup (e.g. missing 24V supply or failsafe state), the system wouldn't recover from this state except via restart. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383225 / Support ID: 400125030 state "Scanning" when using NotPresent flags State "Scanning" was never left when using SAGECOT_FLAGS_V1_TYP.NotPresent (FBK safeDownloadData() of AsSafety-Library) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383230 Problems with FW-ACKN Acknowledgement of firmware revision sometimes failed out. After that SK-XCHG and FW-ACKN had to be acknowledged again. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383235 SK-XCHG after exchange of SLX After exchange of SLX module acknowledgement of SK-XCHG was requested twice. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383240 / Support ID: 400132796 problems acknowledging UDIDs Acknowledgement of UDIDs was not possible (resulting in logger messages 99337 and 114701) if AR (respectively Windows in case of ARwin) had been running more than half an hour before. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 383245 wrong logger numbers of "SCM SW:" The system component "SCM SW:" generated following logger entries with wrong error numbers: 114721 instead of 114833 "internal error revision number", 114722 instead of 114834 "interner error SLX command channel", 114723 instead of 114835 "SLX in inaccessible state" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 389550 Update Online Help Update Online Help Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50608_1.fw(300), 2\50608_1.fw(311) Version 1.7.0.2: ID: 351205 Known issues - activate option "Ignore data objects that are on target only" in AutomationStudio to avoid unintended deletion of internal safety data! - SafeDESIGNER "Variable status" supports a maximum of 64 variables (sum of variables in all open worksheets!). SLX will switch to error state if exceeding this amount. - after exchange of SLX hardware module the "SK-XCHG" must be acknowledged before a safety project download is possible (will abort with error "invalid UDID" otherwise). Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.1: ID: 347700 english help Help files where only available in german Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\50610_1.fw(300), 2\50610_1.fw(311) Version 1.7.0.0: ID: 347275 first official release first official release Safety Release 1.7 required Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\50608_1.fw(300) |
|||||
| Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
| 1.10.10.3 | * | 31/07/2019 | 6 Mo | EXE | AS4_HW_X20cSLX410.exe | |
| Description |
V4.1 HW Upgrade (X20cSLX410) Revision information X20cSLX410 Version 1.10.10.3: ID: 626170 data sheet V1.141 See chapture "Version history" in the data sheet. i.a. calculation of Safety response time has been updated. Channel description changed: No Configuration description changed: No Firmware changed: No ID: 637425 fix logger entry 123622 SLX didn't enter RUN state and logger number 123622 was entered when using 10 other safety modules. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.10.1: ID: 637415 new AR targets support new AR targets X20CPx68x andxPC22xx Channel description changed: No Configuration description changed: No Firmware changed: No ID: 637425 fix logger entry123622 SLX didn't enter RUN state and logger number 123622 was entered when using 10 other safety modules. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.10.0: ID: 626170 safety response time The check of the network transmission timeof cyclic data tolerated values up to 12ms higher than configured by the parameters "safe data duration"/"additional tolerated packet loss". This could lead to an increased safety response time. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.9.0: ID: 618245 logger entry 112174, 108078 Logger entry 112174, 108078could happen sporadically with large projects. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(330) Version 1.10.5.0: ID: 582825 logger message 106773 Fix for logger message 106773 "Parameter checksum sizes do not match". Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(326) Version 1.10.4.1: ID: 585670 channel error when wired to +24V Temporary channel errors (logger entry 115011) are reported if If channels are wired to +24V during module bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589970 additional parameters Support additonal parameters (AsSafety FBK safeDownloadData_V2.Type=safeDATA_TYPE_ADDPARA); requires AR >= A04.41 ! Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589975 fix CLEAR DATA Not all relevant data has been deleted upon command "CLEAR DATA" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589980 logger entry 123432 fixed logger entry 123432 when using setup mode in combination with machineoptions Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589985 bootup time increase of bootup time with UpgradeV1.10.2.9 Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 589990 increased tolerance against asynchronous communication problems Problems in asynchronous communication to safety modules now cause the modules to be rated as "missing" not until the "Node Guarding Timeout" has expired(instead of after a few seconds) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589995 extended operating temperature range Firmware preparation for hardware revisions that allow operating temperature range down to -40°C. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(326) Version 1.10.3.2: ID: 549110 / Support ID: 400225917 Correction of SLX download frame Correction of SLX download frame Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.3.1: ID:537600 logger message 110367 with external maschine options SLX didnot boot correctly when using external machine options with upgrade V1.10.2.9(logger message 110367 and others). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 537605 logger message 123416 when aknowledging a firmware mismatch The command for firmware acknowledgement was accepted although there was still a SCAN in progress. This could lead to a failure with logger message 123416. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.2.9: ID: 381670 / Support ID: 400132230 X20(c)SLX910: warn about invalid two channel processing mode X20(c)SLX910: SafeDESIGNER generates a warning during compile if a two-channel evaluation channel is used but the according parameter "Two Channel Processing Mode" is "none". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 481780 / Support ID: 400199480 error message about incompatible AR version Error message during AutomationStudio compile when trying to use Safety Release 1.10 with an AR versionthat is too old. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 494085 Improve SLX cycle time Performance optimization for improvement of internal SLXcycle time. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 494095 online helpV1.103 Update online help to V1.103 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 502230 support Acopos P3 (X20SLX210 and X20SLX410 only) X20SLX210 and X20SLX410 support all variants of Acopos P3 (X20SLX910 supports 1 axis only) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 513925 / Support ID: 400193973, 400206803 SLXbootState 54 SLXbootState never reached value 54 "SafeRUN" although SLX booted correctly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 516045 fixes for parameters in SafeDESIGNER Minor text corrections. Remove obsolete parameter "Cycle time". Channel description changed:No Configuration description changed: Yes Firmware changed: No ID: 521125 Adapt filter algorithm to eliminate dependencies between TON and TOF-filter Filter algorithm was adapted to eliminate dependenciesbetween TON and TOF-filter which existed since FW V301. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522940 Error while downloading big SafeDESIGNER applications to the SLX. Download was aborted and the message "File Unlock Status: Error while writing unlock status!" was shown. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522945 Setup Mode and automated acknowledgements - Setup Mode is supported (requires SafeDESIGNER 4.3 and AutomationRuntime B4.26or higher) - new parameters for automated acknowledgement of SafeKEY and firmware exchange. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 528960 SafeOS Status in SafeDESIGNER Remote Control It is a known issue that the SafeOS status in SafeDESIGNER remote control is not shown correctly when using certain versions. SafeDESIGNER SafePLC window or AsSafety can be used instead. This affects a set of following versions: SLX Upgrade >=V1.10.2.x, Safety Release 1.10, SafeDESIGNER >=V4.2.3 and AR B4.26 to C4.26 or C4.33to E4.33 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.0.0: ID: 374990 / Support ID: 400129134 SafeDESIGNER communication Variable status Frequent activating/deactivating of SafeDESIGNER variable status could leadto failure of SLX communication. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 390095 / Support ID: 400137073 informations about actual application CRC and timestamp of the SafeDESIGNER application that is actually stored on the SLX can be read via asynchronous data points. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 411790 Support of release 1.10 including openSAFETY 1.5 Support of release 1.10 including openSAFETY 1.5 with easier parametrization of timing parameters Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 426855 / Support ID: 400151377 Optional modules no longer reported missing via SLX LEDs Channel description changed: No Configuration description changed: No Firmware changed: No ID: 440400 / Support ID: 400147709, 400160605, 400165854, 400175456 Input checksum data error In rare cases it could happen sporadically that the SLX entered failsafe state with "Input checksum data error" (logger messages 69648, 73744, 69655 und 73751) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448715 application download Performance optimization of application download to SLX. Some sequences have been changes for this which omitted some of the values ofSLXbootState. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448980 / Support ID: 400162839, 400168358 limit of max 1 SLX per CPU / line integration If there are more then one SLX in the AS hardware tree, only one of them may be enabled. On the other hand now it is allowed todownload a SafeDESIGNER application that doesn't match the SafeLOGIC-ID of the AS hardware tree. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(320) Version 1.9.2.0: ID: 450785 / Support ID: 400137924 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work withsome Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313) Version 1.9.1.0: ID: 425385 change of input filter The behaviour of the input filter has changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 425390 Update Online Help Update Online Help V1.91 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 425395 fw valid from SafetyRelease 1.8 on The firmware is used for all SafetyReleasesfrom 1.8 on. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 425400 Default values changed Default values of Cycle_Time_typical_us and Default_Max_X2X_CycleTime_us changed Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 4\57992_1.fw(313) Version 1.9.0.0: ID: 419950 The module also supportsSafetyRelease 1.9 Starting with this version, the module also supports SafetyRelease 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 419955 Update Online Help Update Online Help V1.90 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 2\57992_1.fw(311) Version 1.8.0.3: ID: 393855 firstofficial release first official release Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\57992_1.fw(311) |
|||||
| Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
| 1.10.5.0 | * | 19/10/2018 | 6 Mo | EXE | AS4_HW_X20cSLX410.exe | |
| Description |
V4.1 HW Upgrade (X20cSLX410) Revision information X20cSLX410 Version 1.10.5.0: ID: 582825 logger message 106773 Fix for logger message 106773 "Parameter checksum sizes do not match". Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(326) Version1.10.4.1: ID: 585670 channel error when wired to +24V Temporary channel errors (logger entry 115011) are reported if If channels are wired to +24V during module bootup. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589970 additional parameters Support additonal parameters (AsSafety FBKsafeDownloadData_V2.Type=safeDATA_TYPE_ADDPARA); requires AR >= A04.41 ! Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589975 fix CLEAR DATA Not all relevant data has been deleted upon command "CLEAR DATA" Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589980 logger entry 123432 fixed logger entry 123432 when using setup mode in combination with machineoptions Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589985 bootup time increase of bootuptime with Upgrade V1.10.2.9 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589990 increased tolerance against asynchronous communication problems Problems in asynchronous communication to safety modules now cause the modules to be rated as "missing" not until the "Node Guarding Timeout" has expired(instead of after a few seconds) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 589995 extended operating temperature range Firmware preparation for hardwarerevisions that allow operating temperaturerange down to -40°C. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(326) Version 1.10.3.2: ID: 549110 / Support ID: 400225917 Correction of SLX download frame Correction of SLX download frame Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.3.1: ID: 537600 logger message 110367 with external maschine options SLX did not boot correctly when using external machine options withupgrade V1.10.2.9 (logger message 110367 and others). Channel description changed: No Configuration description changed: No Firmware changed: No ID: 537605 logger message 123416 when aknowledging a firmware mismatch The command for firmware acknowledgement was accepted although there was still a SCAN in progress. This could lead to a failure with loggermessage 123416. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313),5\57992_1.fw(324) Version 1.10.2.9: ID: 381670 / Support ID: 400132230 X20(c)SLX910: warn about invalid two channel processing mode X20(c)SLX910: SafeDESIGNER generates a warning during compile if a two-channel evaluation channel is used but the according parameter "Two Channel Processing Mode" is "none". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 481780 / Support ID: 400199480 error message about incompatible AR version Error message during AutomationStudio compile when trying to use Safety Release 1.10 with an AR version that is too old. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 494085 Improve SLX cycle time Performance optimization for improvement of internal SLX cycle time. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 494095 online help V1.103 Update online help to V1.103 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 502230 support Acopos P3 (X20SLX210 and X20SLX410 only) X20SLX210 and X20SLX410 support all variants of Acopos P3 (X20SLX910 supports 1 axis only) Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 513925 / Support ID: 400193973, 400206803 SLXbootState 54 SLXbootState never reached value 54 "SafeRUN" although SLX booted correctly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 516045 fixes for parameters in SafeDESIGNER Minor text corrections. Remove obsolete parameter "Cycle time". Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 521125 Adapt filter algorithm to eliminate dependencies between TON and TOF-filter Filter algorithm was adapted to eliminate dependencies between TON and TOF-filter which existed since FW V301. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522940 Error while downloading bigSafeDESIGNER applications to the SLX. Download was aborted and the message "File Unlock Status: Error while writing unlock status!" was shown. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 522945 Setup Mode and automated acknowledgements - Setup Mode is supported (requires SafeDESIGNER 4.3 and AutomationRuntime B4.26 or higher) - new parameters for automated acknowledgement of SafeKEY and firmware exchange. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID:528960 SafeOS Status in SafeDESIGNER Remote Control It is a known issue that the SafeOS status in SafeDESIGNER remote control is not shown correctly when using certain versions. SafeDESIGNER SafePLC window or AsSafety can be used instead. This affects a set of following versions: SLX Upgrade>=V1.10.2.x, Safety Release 1.10, SafeDESIGNER >=V4.2.3 and AR B4.26to C4.26 or C4.33 to E4.33 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 4\57992_1.fw(313), 5\57992_1.fw(324) Version 1.10.0.0: ID: 374990 / Support ID: 400129134 SafeDESIGNER communication Variable status Frequent activating/deactivating of SafeDESIGNER variable status could leadto failure of SLX communication. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 390095 / Support ID: 400137073 informations about actual application CRC and timestamp of the SafeDESIGNER application that is actually stored on the SLX can be read via asynchronous data points. Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 411790 Support of release 1.10 including openSAFETY 1.5 Support of release 1.10 including openSAFETY 1.5 with easier parametrization of timing parameters Channel description changed: No Configuration description changed: Yes Firmware changed: Yes ID: 426855 / Support ID: 400151377 Optional modules no longer reported missing via SLX LEDs Channel description changed: No Configuration description changed: No Firmware changed: No ID: 440400 / Support ID: 400147709, 400160605,400165854, 400175456 Input checksum data error In rare cases it could happen sporadically that the SLX entered failsafe state with "Input checksum data error" (logger messages 69648, 73744, 69655 und 73751) Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448715 application download Performance optimization of application download to SLX. Some sequences have been changesfor this which omitted some of the values of SLXbootState. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 448980 / Support ID: 400162839, 400168358 limit of max 1 SLX per CPU / line integration If there are more then one SLX in the AS hardware tree, only one of them may be enabled. On the other hand now it is allowed to download a SafeDESIGNER application that doesn't match the SafeLOGIC-ID of the AS hardware tree. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 4\57992_1.fw(313), 5\57992_1.fw(320) Version 1.9.2.0: ID:450785 / Support ID: 400137924 SafeLOGIC-X with Panal PC SafeLOGIC-X didn't work with some Panal PCs (e.g. 5PC901 and 5PPC2100) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\57992_1.fw(313) Version 1.9.1.0: ID: 425385 change of input filter The behaviour of the input filter has changed. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 425390 Update Online Help Update Online Help V1.91 Channel description changed: No Configuration description changed: No Firmware changed: No ID:425395 fw valid from SafetyRelease 1.8 on The firmware is used for all SafetyReleases from 1.8 on. Channel description changed: No Configuration description changed: Yes Firmware changed: No ID: 425400 Default values changed Default values of Cycle_Time_typical_us and Default_Max_X2X_CycleTime_us changed Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 4\57992_1.fw(313) Version 1.9.0.0: ID: 419950 The module also supports SafetyRelease 1.9 Starting with this version, the module also supports SafetyRelease 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 419955 Update Online Help Update Online Help V1.90 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 2\57992_1.fw(311) Version 1.8.0.3: ID:393855 first official release first official release Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 2\57992_1.fw(311) |
|||||
