Please choose country and language

V4.0 HW Upgrade (8BVSV2SAFE1-1)

DWL@DWL10000623190

Version Language
Operating System
Date
Size
Type Download
1.10.3.0 * 12/05/2019 893 KB EXE AS4_HW_8BVSV2SAFE1-1.exe
Description 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)
Back to list

Please choose country and language

B&R Logo

Please choose country

B&R Logo