DWL@DWL10000575840
| 版本 | 语言 | 操作系统 | 日期 | 尺寸 | 类型 | 下载 |
|---|---|---|---|---|---|---|
| 1.10.4.1 | * | 10/30/2025 | 1 MB | EXE | AS4_HW_8BVSV2SAFE1-1.exe | |
| 描述 |
V4.0 HW Upgrade (8BVSV2SAFE1-1) Revision information 8BVSV2SAFE1-1 Version 1.10.4.1: ID: SFXA-7054 CVE-2025-43715: Installer is vulnerable to local privilege escalation The installation system NSIS used by B&R can allow local attackers to escalate their privileges. CVE-2025-43715,CVSS: 8.1 (High) CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H Channel description changed: no Configuration description changed: no Firmware changed: no ID: SFXA-6329 HW-Upgrade 1.10.4.1 FW Version 351 - Replacement product for discontinued ACOPOSmulti SafeMotion EnDat 2.2 (8BVSV2SAFE1-1) with new hardware variant 4 - ACOPOSmulti SafeMotion EnDat 2.2 Gen2 (8BSMC9173) Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.10.4.0: (V351) ID: 741835 Propagation delay statistics The Propagation delay statisticscan now be read out. Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 741880 / Support ID: 400299371 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 ID: 741935 / Support ID: 400307322 Improved encoder error handling When an alarm bit occurs, the alarm register is read out explicitly before changing to the error state and the error information is entered in the Safety Logger. EnDat communication is kept active for a few milliseconds so that the ACP firmware can still read out and report the operating state error sources. Alarm bit errors during initialization are reportedby a defined Logger entry and not by debugging information. A separate Logger entry is generated if the encoder is not connected or an encoder timeout occurs. Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 741985 / Support ID: 400298548 Improved encoder error handling Alarm bit errors during initialization are reported by a defined Logger entryand not by debugging information. Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 742085 / Support ID: 400348100, 400341635, 400358931 Errors 7074, 7062, 7022, 7038, 7048, 35244 were sporadically reported when switching on (power on). The following errors were sporadically reported during EnDat initialization triggered by switching on, a warm restart of the CPU orproject download to the CPU or SafeLOGIC controller. NCT: 7074: Encoder: SafeMOTION error 7062: Encoder: SafeMOTION module not ready 7022: Encoder: Initialization is active 7038: Encoder: Position value not synchronouswith absolute value 7048: Error during the reading of encoder memory 35244: Encoder - Received position not valid Safety Logger: 115956, -2147302156: SMC: Encoder - Received position not valid: Info0=0x000X, Info1=0x00000010 or 115956, -2147302156: SMC: Encoder - Received position not valid: Info0=0x000X, Info1=0x00000200 Channel description changed: no Configuration description changed: no Firmware changed: yes Version 1.10.3.1: (V342) ID: 729645 / Support ID: 400351082 Bug fix: Homing status can be lost if a SLT violation occurs The homing status respectively the safe position valid bit can be lost when the SLT torque limit is exceeded and therefore the SLT safety functions are triggered. Automation Studio version: AS 4.0.11.0 Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 729655 / Support ID: 400339046 Solved problem: SafeMOTION error 35016 can occur rarely at the transition from PreOp to Operational Solved problem: SafeMOTION error 35016: SMC FS: internal error, cross communication of check points can occur rarely due toa timeout of the processor at the transition from PreOp to Operational. Channel description changed: no Configuration description changed: no Firmware changed: yes Version 1.10.3.0: (V340) ID: 652960 New feature: Blackout mode (BM) Channel description changed: no Configuration description changed: yes Firmware changed: yes ID: 653220 New function: Checking safe encoder mounting The information whether the encoder issafely mounted is read from the motor data stored in the encoder. If safety functions are used which require safe encoder evaluation and safe encoder mounting is not confirmed in the motor data (or the information is not available), it is automatically checked whether safeencoder monitoring is activated. If the configuration is wrong, the module changes into error state. When using third-party motors or motors without a stored motor data record, the automatic check can be deactivated by setting the parameter "General settings - Encoder monitoring - Safe Encoder Mounting" to "Approved by user". Channel description changed: no Configuration description changed: yes Firmware changed: yes Version 1.10.1.5: (V326) ID: 616845 / Support ID: 400250882 Error 115958 und 115959 after ACOPOS startup When using an EnDat encoder, the following errors could be erroneously reported in rare cases during startup or encoder error acknowledgment: - 115958: SMC: Encoder - Initialization error, Info1=0x000000FF - 115959: SMC: Debug Information, Info1=0x23000000 - 115959: SMC: Debug Information, Info1=0x80400000 Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 616890 / Support ID: 400229368, 400248609 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 ID: 616995 / Support ID: 400224079 Error 7014 or 7015 after ACOPOS startup If the encoder was used before the state "NotErrENC = TRUE" (see I/O Mapping of the SafeMOTION module), one of the following errors could have been reported: - 7014: Encoder: CRC errorduring parameter transfer - 7015: Encoder: Timeout error during parameter transfer In addition, at least version 5.05.0 of ACP10 must be used to solve this problem. Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 619620 / Support ID: 400251128 Network initialization accelerated Network initialization was accelerated for the following cases: - Encoder not connected - Encoder defective For this new function at least version V5.05.0 of ACP10 must be used. Channel description changed: no Configuration description changed: no Firmware changed: yes Version 1.10.1.4: (V271)(V325) ID: 601200 Display of the SafeModuleOK in Automation Studio The status "SafeModuleOK" is displayed in the IO mapping of the SafeMOTION module in AutomationStudio. Channel description changed: yes Configuration description changed: no Firmware changed: no Version 1.10.1.3: (V271)(V325) ID: 597565 / Support ID: 400254396, 400254333, 400254913 Update of the timestamp of the firmware file When updating from version 1.10.1.1 to version 1.10.1.2, the firmware file was not replaced in some cases. The reason is an incorrect timestamp in the firmware file. In upgrade 1.10.1.3, the timestamp has been updated. Thus the issue is resolved. Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.10.1.2: (V271)(V325) ID: 588140 / Support ID: 400249653, 400250602 Not released FW version The HW upgrades 1.10.1.0 and 1.10.1.1 incorrectly contain an unreleased FW version V324. This FW version is not part of the module list and must be replaced with version V325! Channel description changed: no Configuration description changed: no Firmware changed: yes Version 1.10.1.1: (V271)(V324) ID: 580155 Provide the internal cycle time for calculating the Safe Data Duration The hardware description has been adjusted so that the correct internal cycletime is used to calculate the "Safe Data Duration" using the Network Analyzer. Channel description changed: no Configuration description changed: yes Firmware changed:no Version 1.10.1.0: (V271)(V324) ID: 513645 / Support ID: 400198909, 400193000 Some EnDat encoders have reported error 115958 erroneously. Channel description changed: no Configuration description changed:no Firmware changed: yes ID: 562315 Firmware valid for Safety Release V1.4 and later Channel description changed: no Configuration description changed: no Firmware changed: yes ID: 562930 Disabling of encoder error response FFS if no safety function active "FUNCTIONAL FAIL SAFE" in response to an encoder error can be disabled by setting parameter "FFS - Caused by encoder error" to "Only if safety functions requiring an encoder are enabled". In the event of encoder error, bit "NotErrorEnc" is always setto FALSE regardless of the configuration. Channel description changed: no Configuration description changed: yes Firmware changed: yes Version 1.10.0.3: (V271)(V280)(V321) ID: 549255 Support of motion systemmapp Motion HWX file extended for usage with motion system mapp Motion. Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.10.0.2: (V271)(V280)(V321) ID: 495970 Checking of application rules in SafeDESIGNER The rules for the application of SafeMOTION modules are checked as far as possible in SafeDESIGNER in Safety Release 1.10 and later. If the safety application is compiled and a rule violation detected, an erroris output in SafeDESIGNER. The check for the parameters actually transferred continues to take place on the SafeMOTION module. Channel description changed: yes Configuration description changed: yes Firmware changed: yes ID: 496005 / Support ID: 400195703 Dependencies between AR and Safety Release not correct The dependencies between the AR version and Safety Release 1.9 have been corrected for SafeMOTION. If subsequently SafeMachine options are used and therefore also library AsSafety, then the minimum AR version specified in the library must be taken into account. Channel description changed: no Configuration description changed: yes Firmware changed: no Version 1.10.0.0: (V271)(V280)(V321) ID: 467470 8BVSV2SAFE1-1 support in Safety Release 1.10 To support Safety Release 1.10, openSAFETY stack 1.5 has been integrated intothe module firmware. There have been no functional changes. An OSDD file is generated, and the parameters were regrouped and renamed according to the groupings. The new firmware V321 is compatible with both Safety Release 1.9 and Safety Release 1.10. Channel description changed: yes Configuration description changed: yes Firmware changed: yes Version 1.9.0.2: (V271)(V280)(V302) ID: 447805 / Support ID: 400163519 Error correction (not safety relevant): SafeMOTION module boots in FAILSAFE after warm restart of the CPU After a warm restart of the CPU or an error in the PLK connection thesafety FPGA was reconfigured. In some cases the reconfiguration lead to invalid recognition of an CRAM-CRC error and a FAILSAFE reaction. The firmware of the communication processor of the SafeMOTION module has beencorrected. The changes are not safety relevant. After updating the SafeMOTION module no FW exchange has to be acknowledged, becaus the safety relevant FW parts have not been exchanged. Channel description changed: no Configuration description changed: no Firmware changed: yes Version 1.9.0.1: (V271)(V280)(V301) ID: 446060 HW upgrade for 8BVSV2SAFE1-1 Reductionof memory requirements of ACOPOSmulti Safety modules at the SafeLOGIC by zeroising not used configurationparameters (TypicalInputSize and TypicalOutputSize). This change only takes effect if the axis is re-inserted in the project or the project is remade. Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.9.0.0: (V271)(V280)(V301) ID: 391060 SafeMOTION Release 1.9 for SafeMC EnDat2.2 Upgrade for SafeMOTION EnDat2.2 - supported Safety Releases: SR 1.3 to SR 1.9 - New functionts: * Safe Maschine Options (Additional Safety Parameters) * Remanente Safe Position (RSP) * Safety Function Safe Limited Acceleration (SLA) * Parametrization of encoder type * Support of external temperature sensors / support of B&R one-cable-motors *Incremental position is used in safety functions to improve the availability * Improvement of the diagnosis of safety errors Channel description changed: yes Configuration description changed: yes Firmware changed: yes ID: 391070 Support of 8BVSV2SAFE1-1 for Safety Release 1.9 Channel description changed: no Configuration description changed: no Firmware changed: no ID: 422125 Error response if plug-in module is selected Due to a wrong value (valuerange of ShutDownTime) within the HWX file error 7021 was displayed when 8BVSV2SAFE1-1 was selected in Physical View or System Designer Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.6.0.0: ID: 284170 /Support ID: 400082966 Description "Maximum Speed to norm. t. speed range" The actual version of the usermanual contains the description of the parameter "Maximum Speed to norm. t. speed range" . Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.4.0.4: (V271)(V280)(V321)(V325) ID: 441005 / Support ID: 400158456 HW upgrade for 8BVSV2SAFE1-1 Correction of HWX file - illegal character 'è' removed Channel description changed: no Configuration descriptionchanged: no Firmware changed: no Version 1.4.0.3: ID: 324415 Support of 8BVSV2SAFE1-1 Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.4.0.2: (V271)(V280) ID: 271840 / Support ID: 400075818, 400075887, 400075982 Red questionmark next to 8BVSV2SAFE1-1 in the HW-tree The HWC file of the SafeMC module was adapted in such a way that the red question mark in the HW-tree is not indicated any more. The adaption is not safety relevant, the FWand the module-paramters have notbeen changed! Channel description changed: no Configuration description changed: no Firmware changed: no Version 1.4.0.0: (V271)(V280) ID: 226485 Changes/ Features in MotionSafety Release 1.4 - New Safety Functions: * Safely Limited Position (SLP), * Safe Maximum Position(SMP) and * Safe Homing - Support of EnDat22 Functional Safety linear encoders - If SMP and/or SMS are used and "SetPos Alive testing" is activiated, the alive test must be done within 15min; othere the SafeMC Modul will change to Functional Fail Safe State! - Warnings are only sent by µP1 - Logging entries got defined Levels Channel description changed: yes Configuration description changed: yes Firmware changed: yes ID: 237625 Shutdowndelay in case of PLK network error The SafeMC Module is kept in "Operational" state for the time configuerd in the parameter "Shut Down delay in us" in case of a PLK connection error. This allows the functional application to implement a defines shut down of the axis! Channel description changed: yes Configuration description changed: yes Firmware changed: yes |
|||||
| 版本 | 语言 | 操作系统 | 日期 | 尺寸 | 类型 | 下载 |
| 1.10.4.0 | * | 12/21/2022 | 902 KB | EXE | AS4_HW_8BVSV2SAFE1-1.exe | |
| 描述 |
V4.0 HW Upgrade (8BVSV2SAFE1-1) Revision information 8BVSV2SAFE1-1 Version 1.10.4.0: ID: 742085 Errors 7074, 7062, 7022, 7038, 7048, 35244 were sporadically reported when switching on (power on). The following errors were sporadically reported during EnDat initialization triggered by switching on, a warm restart of the CPU or project download to the CPU or SafeLOGIC controller. NCT: 7074: Encoder: SafeMOTION error 7062: Encoder: SafeMOTION module not ready 7022: Encoder: Initialization is active 7038: Encoder: Position value not synchronous with absolute value 7048: Error during the reading of encoder memory 35244: Encoder - Received position not valid Safety Logger: 115956, -2147302156: SMC: Encoder - Received position not valid: Info0=0x000X, Info1=0x00000010 or 115956, -2147302156: SMC: Encoder - Received position not valid: Info0=0x000X, Info1=0x00000200 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 741985 Improved encoder error handling Alarm bit errors during initialization are reported by a defined Logger entry and not by debugging information. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 741935 Improved encoder error handling When an alarm bit occurs, the alarm register is read out explicitly before changing to the error state and the error information is entered in the Safety Logger. EnDat communication is kept active for a few milliseconds so that the ACP firmware can still read out and report the operating state error sources. Alarm bit errors during initialization are reported by a defined Logger entry and not by debugging information. A separate Logger entry is generated if the encoder is not connected or an encoder timeout occurs. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 741880 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 ID: 741835 Propagation delay statistics The Propagation delay statistics can now be read out. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326), 5\42798_3.fw(351) Version 1.10.3.1: ID: 729645 / Support ID: 400351082 Bug fix: Homing status can be lost if a SLT violation occurs The homing status respectively the safe position valid bit can be lost when the SLT torque limit is exceeded and therefore the SLT safety functions are triggered. Automation Studio version: AS 4.0.11.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 729655 / Support ID: 400339046 Solved problem: SafeMOTION error 35016 can occur rarely at the transition from PreOp to Operational Solved problem: SafeMOTION error 35016: SMC FS: internal error, cross communication of check points can occur rarely due to a timeout of the processor at the transition from PreOp to Operational. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326), 5\42798_3.fw(342) Version 1.10.3.0: ID: 652960 New feature: Blackout mode (BM) Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 653220 New function: Checking safe encoder mounting The information whether the encoder is safely mounted is read from the motor data stored in the encoder. If safety functions are used which require safe encoder evaluation and safe encoder mounting is not confirmed in the motor data (or the information is not available), it is automatically checked whether safe encoder monitoring is activated. If the configuration is wrong, the module changes into error state. When using third-party motors or motors without a stored motor data record, the automatic check can be deactivated by setting the parameter "General settings - Encoder monitoring - Safe Encoder Mounting" to "Approved by user". Channel description changed: Yes Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326), 5\42798_3.fw(340) Version 1.10.1.5: ID: 616845 / Support ID: 400250882 Error 115958 und 115959 after ACOPOS startup When using an EnDat encoder, the following errors could be erroneously reported in rare cases during startup or encoder error acknowledgment: - 115958: SMC: Encoder - Initialization error,Info1=0x000000FF - 115959: SMC: Debug Information, Info1=0x23000000 - 115959: SMC: Debug Information, Info1=0x80400000 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 616890 / Support ID: 400229368, 400248609 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with largeprojects. Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 616995 / Support ID: 400224079 Error 7014 or 7015 after ACOPOS startup If the encoder was used before the state "NotErrENC = TRUE" (see I/O Mapping of the SafeMOTION module), one of the following errors could have been reported: - 7014: Encoder: CRC error during parameter transfer - 7015: Encoder: Timeout error during parameter transfer In addition, at least version 5.05.0 of ACP10 must beused to solve this problem. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619620 / Support ID: 400251128 Network initialization accelerated Network initialization was accelerated for the following cases: - Encoder not connected - Encoder defective For this new function at least version V5.05.0 of ACP10 must be used. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326) Version 1.10.1.4: ID: 601200 Display of the SafeModuleOK in Automation Studio The status "SafeModuleOK" is displayed in the IO mapping of the SafeMOTION module in Automation Studio. Channel description changed: Yes Configuration description changed: No Firmwarechanged: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.3: ID: 597565 / Support ID: 400254396, 400254333, 400254913 Update of the timestamp of the firmware file When updating from version 1.10.1.1 to version 1.10.1.2, the firmware file was not replaced in some cases. The reason is an incorrect timestamp in the firmware file. In upgrade 1.10.1.3, the timestamp has been updated. Thus the issueis resolved. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.2: ID: 588140 Not released FW version The HW upgrades 1.10.1.0 and 1.10.1.1 incorrectly contain an unreleased FW version V324. This FW version is not part of the module list and must be replaced with version V325! Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.1: ID: 580155 Provide the internal cycle time for calculating the Safe Data Duration The hardware description has been adjusted so that the correct internal cycle time is used to calculate the"Safe Data Duration" using the Network Analyzer. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.1.0: ID: 513645 / Support ID: 400198909, 400193000 Some EnDat encoders have reported error 115958 erroneously. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562315 Firmware valid for Safety Release V1.4 andlater Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562930 Disabling of encoder error response FFS if no safety function active "FUNCTIONAL FAIL SAFE" in response to an encoder error can be disabled by setting parameter "FFS - Caused by encoder error" to "Only if safety functions requiring an encoder areenabled". In the event of encoder error, bit "NotErrorEnc" is always set to FALSE regardless of the configuration. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.0.3: ID: 549255 Support of motion system mapp Motion HWX file extended for usage with motion system mapp Motion. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23),2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.2: ID: 495970 Checking of application rules in SafeDESIGNER The rules for the application of SafeMOTION modules are checked as far as possible in SafeDESIGNER in Safety Release 1.10 and later. If the safety application is compiled and a rule violation detected, an erroris output in SafeDESIGNER. The check for the parameters actually transferred continues to takeplace on the SafeMOTION module. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 496005 / Support ID: 400195703 Dependencies between AR and Safety Release not correct The dependencies between the AR version and Safety Release 1.9 have been corrected for SafeMOTION. If subsequently SafeMachine options are used and therefore also library AsSafety, then the minimum AR version specified in the library must be taken into account. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.0: ID: 467470 8BVSV2SAFE1-1 support in Safety Release 1.10 To supportSafety Release 1.10, openSAFETY stack 1.5 has been integrated into the modulefirmware. There have been no functional changes. An OSDD file is generated, and the parameters were regrouped and renamed according to the groupings. The new firmware V321 is compatible with both Safety Release 1.9 and Safety Release 1.10. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.9.0.2: ID: 447805 / Support ID: 400163519 Error correction (not safety relevant): SafeMOTION module boots in FAILSAFEafter warm restart of the CPU After a warm restart of the CPU or an error in the PLK connection the safety FPGA was reconfigured. In somecases the reconfiguration lead to invalid recognition of an CRAM-CRC error and a FAILSAFE reaction. The firmware of the communication processor of the SafeMOTION module has beencorrected. The changes are not safety relevant. After updating the SafeMOTION module no FW exchange has to be acknowledged, becaus the safety relevant FW parts have not been exchanged. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(302) Version 1.9.0.1: ID: 446060 HW upgrade for 8BVSV2SAFE1-1 Reduction of memory requirements of ACOPOSmulti Safety modules at the SafeLOGIC by zeroising not used configurationparameters (TypicalInputSize and TypicalOutputSize). This change only takes effect if the axis is re-inserted in the project or the project is remade. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(301) Version 1.9.0.0: ID: 391060 SafeMOTION Release 1.9 for SafeMC EnDat2.2 Upgrade for SafeMOTION EnDat2.2 - supported Safety Releases: SR 1.3 to SR 1.9 - New functionts: *Safe Maschine Options (Additional Safety Parameters) * Remanente Safe Position (RSP) * Safety Function Safe Limited Acceleration (SLA) * Parametrization of encoder type * Support of external temperature sensors /support of B&R one-cable-motors * Incremental position is used in safetyfunctions to improve the availability * Improvement of the diagnosis ofsafety errors Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 391070 Supportof 8BVSV2SAFE1-1 for Safety Release 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 422125 Error response if plug-in module is selected Due to a wrong value (valuerange of ShutDownTime) within the HWX file error7021 was displayed when 8BVSV2SAFE1-1 was selected in Physical View or SystemDesigner Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_3.fw(301), 3\42798_2.fw(23) Version 1.4.0.4: ID: 441005 / Support ID: 400158456 HW upgrade for 8BVSV2SAFE1-1 Correction of HWX file - illegal character 'è' removed Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271),2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321), 4\42798_3.fw(325) Version 1.4.0.2: ID: 271840 / Support ID: 400075818 Red questionmark next to 8BVSV2SAFE1-1 in the HW-tree The HWC file of the SafeMC module was adapted in such a way that the red question mark in the HW-tree is not indicated any more. The adaption is not safety relevant, the FW and the module-paramters have not been changed! Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) Version 1.4.0.0: ID: 226485 Changes/ Features in Motion Safety Release 1.4 - New Safety Functions: * Safely Limited Position (SLP), * Safe Maximum Position(SMP) and * Safe Homing - Support of EnDat22 Functional Safety linear encoders - If SMP and/or SMS are used and "SetPos Alive testing" is activiated, thealive test must be done within 15min; otherethe SafeMC Modul will change to Functional Fail Safe State! - Warnings are only sent by µP1 - Logging entries got defined Levels Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) |
|||||
| 版本 | 语言 | 操作系统 | 日期 | 尺寸 | 类型 | 下载 |
| 1.10.3.1 | * | 06/30/2021 | 904 KB | EXE | AS4_HW_8BVSV2SAFE1-1.exe | |
| 描述 |
V4.0 HW Upgrade (8BVSV2SAFE1-1) Revision information 8BVSV2SAFE1-1 Version 1.10.3.1: ID: 729645 / Support ID: 400351082 Bug fix: Homing status can be lost if a SLT violation occurs The homing status respectively the safe position valid bit can be lost when the SLT torque limit is exceeded and therefore the SLT safety functions are triggered. Automation Studio version: AS 4.0.11.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 729655 / Support ID: 400339046 Solved problem: SafeMOTION error 35016 can occur rarely at the transition from PreOp to Operational Solved problem: SafeMOTION error 35016: SMC FS: internal error, cross communication of check points can occur rarely due to a timeout of the processor at the transition from PreOp to Operational. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326), 5\42798_3.fw(342) Version 1.10.3.0: ID: 652960 New feature: Blackout mode (BM) Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 653220 New function: Checking safe encoder mounting The information whether the encoder is safely mounted is read from the motor data stored in the encoder. If safety functions are used which require safe encoder evaluation and safe encoder mounting is not confirmed in the motor data (or the information is not available), it is automatically checked whether safe encoder monitoring is activated. If the configuration is wrong, the module changes into error state. When using third-party motors or motors without a stored motor data record, the automatic check can be deactivated by setting the parameter "General settings - Encoder monitoring - Safe Encoder Mounting" to "Approved by user". Channel description changed: Yes Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326), 5\42798_3.fw(340) Version 1.10.1.5: ID: 616845 / Support ID: 400250882 Error 115958 und 115959 after ACOPOS startup When using an EnDat encoder, the following errors could be erroneously reported in rare cases during startup or encoder error acknowledgment: - 115958: SMC: Encoder - Initialization error,Info1=0x000000FF - 115959: SMC: Debug Information, Info1=0x23000000 - 115959: SMC: Debug Information, Info1=0x80400000 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 616890 / Support ID: 400229368, 400248609 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with largeprojects. Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 616995 / Support ID: 400224079 Error 7014 or 7015 after ACOPOS startup If the encoder was used before the state "NotErrENC = TRUE" (see I/O Mapping of the SafeMOTION module), one of the following errors could have been reported: - 7014: Encoder: CRC error during parameter transfer - 7015: Encoder: Timeout error during parameter transfer In addition, at least version 5.05.0 of ACP10 must beused to solve this problem. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619620 / Support ID: 400251128 Network initialization accelerated Network initialization was accelerated for the following cases: - Encoder not connected - Encoder defective For this new function at least version V5.05.0 of ACP10 must be used. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326) Version 1.10.1.4: ID: 601200 Display of the SafeModuleOK in Automation Studio The status "SafeModuleOK" is displayed in the IO mapping of the SafeMOTION module in Automation Studio. Channel description changed: Yes Configuration description changed: No Firmwarechanged: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.3: ID: 597565 / Support ID: 400254396, 400254333, 400254913 Update of the timestamp of the firmware file When updating from version 1.10.1.1 to version 1.10.1.2, the firmware file was not replaced in some cases. The reason is an incorrect timestamp in the firmware file. In upgrade 1.10.1.3, the timestamp has been updated. Thus the issueis resolved. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.2: ID: 588140 Not released FW version The HW upgrades 1.10.1.0 and 1.10.1.1 incorrectly contain an unreleased FW version V324. This FW version is not part of the module list and must be replaced with version V325! Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.1: ID: 580155 Provide the internal cycle time for calculating the Safe Data Duration The hardware description has been adjusted so that the correct internal cycle time is used to calculate the"Safe Data Duration" using the Network Analyzer. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.1.0: ID: 513645 / Support ID: 400198909, 400193000 Some EnDat encoders have reported error 115958 erroneously. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562315 Firmware valid for Safety Release V1.4 andlater Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562930 Disabling of encoder error response FFS if no safety function active "FUNCTIONAL FAIL SAFE" in response to an encoder error can be disabled by setting parameter "FFS - Caused by encoder error" to "Only if safety functions requiring an encoder areenabled". In the event of encoder error, bit "NotErrorEnc" is always set to FALSE regardless of the configuration. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.0.3: ID: 549255 Support of motion system mapp Motion HWX file extended for usage with motion system mapp Motion. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23),2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.2: ID: 495970 Checking of application rules in SafeDESIGNER The rules for the application of SafeMOTION modules are checked as far as possible in SafeDESIGNER in Safety Release 1.10 and later. If the safety application is compiled and a rule violation detected, an erroris output in SafeDESIGNER. The check for the parameters actually transferred continues to takeplace on the SafeMOTION module. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 496005 / Support ID: 400195703 Dependencies between AR and Safety Release not correct The dependencies between the AR version and Safety Release 1.9 have been corrected for SafeMOTION. If subsequently SafeMachine options are used and therefore also library AsSafety, then the minimum AR version specified in the library must be taken into account. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.0: ID: 467470 8BVSV2SAFE1-1 support in Safety Release 1.10 To supportSafety Release 1.10, openSAFETY stack 1.5 has been integrated into the modulefirmware. There have been no functional changes. An OSDD file is generated, and the parameters were regrouped and renamed according to the groupings. The new firmware V321 is compatible with both Safety Release 1.9 and Safety Release 1.10. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.9.0.2: ID: 447805 / Support ID: 400163519 Error correction (not safety relevant): SafeMOTION module boots in FAILSAFEafter warm restart of the CPU After a warm restart of the CPU or an error in the PLK connection the safety FPGA was reconfigured. In somecases the reconfiguration lead to invalid recognition of an CRAM-CRC error and a FAILSAFE reaction. The firmware of the communication processor of the SafeMOTION module has beencorrected. The changes are not safety relevant. After updating the SafeMOTION module no FW exchange has to be acknowledged, becaus the safety relevant FW parts have not been exchanged. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(302) Version 1.9.0.1: ID: 446060 HW upgrade for 8BVSV2SAFE1-1 Reduction of memory requirements of ACOPOSmulti Safety modules at the SafeLOGIC by zeroising not used configurationparameters (TypicalInputSize and TypicalOutputSize). This change only takes effect if the axis is re-inserted in the project or the project is remade. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(301) Version 1.9.0.0: ID: 391060 SafeMOTION Release 1.9 for SafeMC EnDat2.2 Upgrade for SafeMOTION EnDat2.2 - supported Safety Releases: SR 1.3 to SR 1.9 - New functionts: *Safe Maschine Options (Additional Safety Parameters) * Remanente Safe Position (RSP) * Safety Function Safe Limited Acceleration (SLA) * Parametrization of encoder type * Support of external temperature sensors /support of B&R one-cable-motors * Incremental position is used in safetyfunctions to improve the availability * Improvement of the diagnosis ofsafety errors Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 391070 Supportof 8BVSV2SAFE1-1 for Safety Release 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 422125 Error response if plug-in module is selected Due to a wrong value (valuerange of ShutDownTime) within the HWX file error7021 was displayed when 8BVSV2SAFE1-1 was selected in Physical View or SystemDesigner Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_3.fw(301), 3\42798_2.fw(23) Version 1.4.0.4: ID: 441005 / Support ID: 400158456 HW upgrade for 8BVSV2SAFE1-1 Correction of HWX file - illegal character 'è' removed Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271),2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321), 4\42798_3.fw(325) Version 1.4.0.2: ID: 271840 / Support ID: 400075818 Red questionmark next to 8BVSV2SAFE1-1 in the HW-tree The HWC file of the SafeMC module was adapted in such a way that the red question mark in the HW-tree is not indicated any more. The adaption is not safety relevant, the FW and the module-paramters have not been changed! Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) Version 1.4.0.0: ID: 226485 Changes/ Features in Motion Safety Release 1.4 - New Safety Functions: * Safely Limited Position (SLP), * Safe Maximum Position(SMP) and * Safe Homing - Support of EnDat22 Functional Safety linear encoders - If SMP and/or SMS are used and "SetPos Alive testing" is activiated, thealive test must be done within 15min; otherethe SafeMC Modul will change to Functional Fail Safe State! - Warnings are only sent by µP1 - Logging entries got defined Levels Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) |
|||||
| 版本 | 语言 | 操作系统 | 日期 | 尺寸 | 类型 | 下载 |
| 1.10.3.0 | * | 12/05/2019 | 893 KB | EXE | AS4_HW_8BVSV2SAFE1-1.exe | |
| 描述 |
V4.0 HW Upgrade (8BVSV2SAFE1-1) Revision information 8BVSV2SAFE1-1 Version 1.10.3.0: ID: 652960 New feature: Blackout mode (BM) Channel description changed: Yes Configuration description changed: No Firmware changed: Yes ID: 653220 New function: Checking safe encoder mounting The information whether the encoder is safely mounted is read from the motor data stored in the encoder. If safety functions are used which require safe encoder evaluation and safe encoder mounting is not confirmed in the motor data (or the information is not available), it is automatically checked whether safe encoder monitoring is activated. If the configuration is wrong, the module changes into error state. When using third-party motors or motors without a stored motor data record, the automatic check can be deactivated by setting the parameter "General settings - Encoder monitoring - Safe Encoder Mounting" to "Approved by user". Channel description changed: Yes Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326), 5\42798_3.fw(340) Version 1.10.1.5: ID: 616845 / Support ID: 400250882 Error 115958 und 115959 after ACOPOS startup When using an EnDat encoder, the following errors could be erroneously reported in rare cases during startup or encoder error acknowledgment: - 115958: SMC: Encoder - Initialization error,Info1=0x000000FF - 115959: SMC: Debug Information, Info1=0x23000000 - 115959: SMC: Debug Information, Info1=0x80400000 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 616890 / Support ID: 400229368, 400248609 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with largeprojects. Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 616995 / Support ID: 400224079 Error 7014 or 7015 after ACOPOS startup If the encoder was used before the state "NotErrENC = TRUE" (see I/O Mapping of the SafeMOTION module), one of the following errors could have been reported: - 7014: Encoder: CRC error during parameter transfer - 7015: Encoder: Timeout error during parameter transfer In addition, at least version 5.05.0 of ACP10 must beused to solve this problem. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619620 / Support ID: 400251128 Network initialization accelerated Network initialization was accelerated for the following cases: - Encoder not connected - Encoder defective For this new function at least version V5.05.0 of ACP10 must be used. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326) Version 1.10.1.4: ID: 601200 Display of the SafeModuleOK in Automation Studio The status "SafeModuleOK" is displayed in the IO mapping of the SafeMOTION module in Automation Studio. Channel description changed: Yes Configuration description changed: No Firmwarechanged: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.3: ID: 597565 / Support ID: 400254396, 400254333, 400254913 Update of the timestamp of the firmware file When updating from version 1.10.1.1 to version 1.10.1.2, the firmware file was not replaced in some cases. The reason is an incorrect timestamp in the firmware file. In upgrade 1.10.1.3, the timestamp has been updated. Thus the issueis resolved. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.2: ID: 588140 Not released FW version The HW upgrades 1.10.1.0 and 1.10.1.1 incorrectly contain an unreleased FW version V324. This FW version is not part of the module list and must be replaced with version V325! Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.1: ID: 580155 Provide the internal cycle time for calculating the Safe Data Duration The hardware description has been adjusted so that the correct internal cycle time is used to calculate the"Safe Data Duration" using the Network Analyzer. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.1.0: ID: 513645 / Support ID: 400198909, 400193000 Some EnDat encoders have reported error 115958 erroneously. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562315 Firmware valid for Safety Release V1.4 andlater Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562930 Disabling of encoder error response FFS if no safety function active "FUNCTIONAL FAIL SAFE" in response to an encoder error can be disabled by setting parameter "FFS - Caused by encoder error" to "Only if safety functions requiring an encoder areenabled". In the event of encoder error, bit "NotErrorEnc" is always set to FALSE regardless of the configuration. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.0.3: ID: 549255 Support of motion system mapp Motion HWX file extended for usage with motion system mapp Motion. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23),2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.2: ID: 495970 Checking of application rules in SafeDESIGNER The rules for the application of SafeMOTION modules are checked as far as possible in SafeDESIGNER in Safety Release 1.10 and later. If the safety application is compiled and a rule violation detected, an erroris output in SafeDESIGNER. The check for the parameters actually transferred continues to takeplace on the SafeMOTION module. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 496005 / Support ID: 400195703 Dependencies between AR and Safety Release not correct The dependencies between the AR version and Safety Release 1.9 have been corrected for SafeMOTION. If subsequently SafeMachine options are used and therefore also library AsSafety, then the minimum AR version specified in the library must be taken into account. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.0: ID: 467470 8BVSV2SAFE1-1 support in Safety Release 1.10 To supportSafety Release 1.10, openSAFETY stack 1.5 has been integrated into the modulefirmware. There have been no functional changes. An OSDD file is generated, and the parameters were regrouped and renamed according to the groupings. The new firmware V321 is compatible with both Safety Release 1.9 and Safety Release 1.10. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.9.0.2: ID: 447805 / Support ID: 400163519 Error correction (not safety relevant): SafeMOTION module boots in FAILSAFEafter warm restart of the CPU After a warm restart of the CPU or an error in the PLK connection the safety FPGA was reconfigured. In somecases the reconfiguration lead to invalid recognition of an CRAM-CRC error and a FAILSAFE reaction. The firmware of the communication processor of the SafeMOTION module has beencorrected. The changes are not safety relevant. After updating the SafeMOTION module no FW exchange has to be acknowledged, becaus the safety relevant FW parts have not been exchanged. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(302) Version 1.9.0.1: ID: 446060 HW upgrade for 8BVSV2SAFE1-1 Reduction of memory requirements of ACOPOSmulti Safety modules at the SafeLOGIC by zeroising not used configurationparameters (TypicalInputSize and TypicalOutputSize). This change only takes effect if the axis is re-inserted in the project or the project is remade. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(301) Version 1.9.0.0: ID: 391060 SafeMOTION Release 1.9 for SafeMC EnDat2.2 Upgrade for SafeMOTION EnDat2.2 - supported Safety Releases: SR 1.3 to SR 1.9 - New functionts: *Safe Maschine Options (Additional Safety Parameters) * Remanente Safe Position (RSP) * Safety Function Safe Limited Acceleration (SLA) * Parametrization of encoder type * Support of external temperature sensors /support of B&R one-cable-motors * Incremental position is used in safetyfunctions to improve the availability * Improvement of the diagnosis ofsafety errors Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 391070 Supportof 8BVSV2SAFE1-1 for Safety Release 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 422125 Error response if plug-in module is selected Due to a wrong value (valuerange of ShutDownTime) within the HWX file error7021 was displayed when 8BVSV2SAFE1-1 was selected in Physical View or SystemDesigner Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_3.fw(301), 3\42798_2.fw(23) Version 1.4.0.4: ID: 441005 / Support ID: 400158456 HW upgrade for 8BVSV2SAFE1-1 Correction of HWX file - illegal character 'è' removed Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271),2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321), 4\42798_3.fw(325) Version 1.4.0.2: ID: 271840 / Support ID: 400075818 Red questionmark next to 8BVSV2SAFE1-1 in the HW-tree The HWC file of the SafeMC module was adapted in such a way that the red question mark in the HW-tree is not indicated any more. The adaption is not safety relevant, the FW and the module-paramters have not been changed! Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) Version 1.4.0.0: ID: 226485 Changes/ Features in Motion Safety Release 1.4 - New Safety Functions: * Safely Limited Position (SLP), * Safe Maximum Position(SMP) and * Safe Homing - Support of EnDat22 Functional Safety linear encoders - If SMP and/or SMS are used and "SetPos Alive testing" is activiated, thealive test must be done within 15min; otherethe SafeMC Modul will change to Functional Fail Safe State! - Warnings are only sent by µP1 - Logging entries got defined Levels Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) |
|||||
| 版本 | 语言 | 操作系统 | 日期 | 尺寸 | 类型 | 下载 |
| 1.10.1.5 | * | 11/30/2018 | 535 KB | EXE | AS4_HW_8BVSV2SAFE1-1.exe | |
| 描述 |
V4.0 HW Upgrade (8BVSV2SAFE1-1) Revision information 8BVSV2SAFE1-1 Version 1.10.1.5: ID: 616845 / Support ID: 400250882 Error 115958 und 115959 after ACOPOS startup When using an EnDat encoder, the following errors could be erroneously reported in rare cases during startup or encoder error acknowledgment: - 115958: SMC: Encoder - Initialization error,Info1=0x000000FF - 115959: SMC: Debug Information, Info1=0x23000000 - 115959: SMC: Debug Information, Info1=0x80400000 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 616890 / Support ID: 400229368, 400248609 logger entry 112174, 108078 Logger entry 112174, 108078 could happen sporadically with largeprojects. Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 616995 / Support ID: 400224079 Error 7014 or 7015 after ACOPOS startup If the encoder was used before the state "NotErrENC = TRUE" (see I/O Mapping of the SafeMOTION module), one of the following errors could have been reported: - 7014: Encoder: CRC error during parameter transfer - 7015: Encoder: Timeout error during parameter transfer In addition, at least version 5.05.0 of ACP10 must beused to solve this problem. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619620 / Support ID: 400251128 Network initialization accelerated Network initialization was accelerated for the following cases: - Encoder not connected - Encoder defective For this new function at least version V5.05.0 of ACP10 must be used. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 4\42798_3.fw(326) Version 1.10.1.4: ID: 601200 Display of the SafeModuleOK in Automation Studio The status "SafeModuleOK" is displayed in the IO mapping of the SafeMOTION module in Automation Studio. Channel description changed: Yes Configuration description changed: No Firmwarechanged: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.3: ID: 597565 / Support ID: 400254396, 400254333, 400254913 Update of the timestamp of the firmware file When updating from version 1.10.1.1 to version 1.10.1.2, the firmware file was not replaced in some cases. The reason is an incorrect timestamp in the firmware file. In upgrade 1.10.1.3, the timestamp has been updated. Thus the issueis resolved. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.2: ID: 588140 Not released FW version The HW upgrades 1.10.1.0 and 1.10.1.1 incorrectly contain an unreleased FW version V324. This FW version is not part of the module list and must be replaced with version V325! Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(325) Version 1.10.1.1: ID: 580155 Provide the internal cycle time for calculating the Safe Data Duration The hardware description has been adjusted so that the correct internal cycle time is used to calculate the"Safe Data Duration" using the Network Analyzer. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.1.0: ID: 513645 / Support ID: 400198909, 400193000 Some EnDat encoders have reported error 115958 erroneously. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562315 Firmware valid for Safety Release V1.4 andlater Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 562930 Disabling of encoder error response FFS if no safety function active "FUNCTIONAL FAIL SAFE" in response to an encoder error can be disabled by setting parameter "FFS - Caused by encoder error" to "Only if safety functions requiring an encoder areenabled". In the event of encoder error, bit "NotErrorEnc" is always set to FALSE regardless of the configuration. Channel description changed: No Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 4\42798_3.fw(324) Version 1.10.0.3: ID: 549255 Support of motion system mapp Motion HWX file extended for usage with motion system mapp Motion. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23),2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.2: ID: 495970 Checking of application rules in SafeDESIGNER The rules for the application of SafeMOTION modules are checked as far as possible in SafeDESIGNER in Safety Release 1.10 and later. If the safety application is compiled and a rule violation detected, an erroris output in SafeDESIGNER. The check for the parameters actually transferred continues to takeplace on the SafeMOTION module. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 496005 / Support ID: 400195703 Dependencies between AR and Safety Release not correct The dependencies between the AR version and Safety Release 1.9 have been corrected for SafeMOTION. If subsequently SafeMachine options are used and therefore also library AsSafety, then the minimum AR version specified in the library must be taken into account. Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.10.0.0: ID: 467470 8BVSV2SAFE1-1 support in Safety Release 1.10 To supportSafety Release 1.10, openSAFETY stack 1.5 has been integrated into the modulefirmware. There have been no functional changes. An OSDD file is generated, and the parameters were regrouped and renamed according to the groupings. The new firmware V321 is compatible with both Safety Release 1.9 and Safety Release 1.10. Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321) Version 1.9.0.2: ID: 447805 / Support ID: 400163519 Error correction (not safety relevant): SafeMOTION module boots in FAILSAFEafter warm restart of the CPU After a warm restart of the CPU or an error in the PLK connection the safety FPGA was reconfigured. In somecases the reconfiguration lead to invalid recognition of an CRAM-CRC error and a FAILSAFE reaction. The firmware of the communication processor of the SafeMOTION module has beencorrected. The changes are not safety relevant. After updating the SafeMOTION module no FW exchange has to be acknowledged, becaus the safety relevant FW parts have not been exchanged. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(302) Version 1.9.0.1: ID: 446060 HW upgrade for 8BVSV2SAFE1-1 Reduction of memory requirements of ACOPOSmulti Safety modules at the SafeLOGIC by zeroising not used configurationparameters (TypicalInputSize and TypicalOutputSize). This change only takes effect if the axis is re-inserted in the project or the project is remade. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(301) Version 1.9.0.0: ID: 391060 SafeMOTION Release 1.9 for SafeMC EnDat2.2 Upgrade for SafeMOTION EnDat2.2 - supported Safety Releases: SR 1.3 to SR 1.9 - New functionts: *Safe Maschine Options (Additional Safety Parameters) * Remanente Safe Position (RSP) * Safety Function Safe Limited Acceleration (SLA) * Parametrization of encoder type * Support of external temperature sensors /support of B&R one-cable-motors * Incremental position is used in safetyfunctions to improve the availability * Improvement of the diagnosis ofsafety errors Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes ID: 391070 Supportof 8BVSV2SAFE1-1 for Safety Release 1.9 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 422125 Error response if plug-in module is selected Due to a wrong value (valuerange of ShutDownTime) within the HWX file error7021 was displayed when 8BVSV2SAFE1-1 was selected in Physical View or SystemDesigner Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_3.fw(301), 3\42798_2.fw(23) Version 1.4.0.4: ID: 441005 / Support ID: 400158456 HW upgrade for 8BVSV2SAFE1-1 Correction of HWX file - illegal character 'è' removed Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271),2\42798_2.fw(23), 2\42798_3.fw(280), 3\42798_2.fw(23), 3\42798_3.fw(321), 4\42798_3.fw(325) Version 1.4.0.2: ID: 271840 / Support ID: 400075818 Red questionmark next to 8BVSV2SAFE1-1 in the HW-tree The HWC file of the SafeMC module was adapted in such a way that the red question mark in the HW-tree is not indicated any more. The adaption is not safety relevant, the FW and the module-paramters have not been changed! Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) Version 1.4.0.0: ID: 226485 Changes/ Features in Motion Safety Release 1.4 - New Safety Functions: * Safely Limited Position (SLP), * Safe Maximum Position(SMP) and * Safe Homing - Support of EnDat22 Functional Safety linear encoders - If SMP and/or SMS are used and "SetPos Alive testing" is activiated, thealive test must be done within 15min; otherethe SafeMC Modul will change to Functional Fail Safe State! - Warnings are only sent by µP1 - Logging entries got defined Levels Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42798_2.fw(23), 1\42798_3.fw(271), 2\42798_2.fw(23), 2\42798_3.fw(280) |
|||||
