DWL@DWL10000302975
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
---|---|---|---|---|---|---|
2.15.0.0 | * | 13/10/2022 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.15.0.0: ID: 758850 Optimization of asynchronous register access Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(433), 1\42917_3.fw(433) Version 2.14.0.0: ID: 737340 NUMBER:JACK improved ISN (TCP start sequence) generation in IP stack Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 737345 POWERLINK Security Vulnerability (CVE-2020-13987 & CVE-2020-17438) POWERLINK Security Vulnerability (CVE-2020-13987) The POWERLINK IP stack was affected by a security vulnerability impacting thechecksum calculation of TCP/UDP packets. POWERLINK Security Vulnerability (CVE-2020-17438) The POWERLINK IP stack was affected by a security vulnerability impacting fragmented packet reassembly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 739455 Module documentation revised Data sheet V3.08 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(432), 1\42917_3.fw(432) Version 2.11.1.0: ID: 697885 Support for automatic DNA configuration from AS 4.9.1 Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.11.0.0: ID: 664420 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 665800 ModuleOk of IO module FALSE after warm restart even though the moduleis working as expected Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 665880 Accessing non-cyclic registers with AsIOAcc while ModuleOk = FALSE preventsmodule from starting/communicating Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 666165 Module documentation revised Data sheet V3.06 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.9.3.0: ID: 639730 / Support ID: 400268096 Alignment of AS output according to the FieldBusDesigner Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.9.0.0: ID: 629050 Ring redundancy: Cannot address the CN that closes the ring Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629125 DNA: BC as head-end station switching hub off again Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629200 Shortened preamble of Ethernet frame leading to incorrectly detected CRC errors Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629245 Optimization of hub behavior Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behind the bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate of X2XLink module at POWERLINK Stations does not work since H4.34 Since H4.34 the firmware update of X2XLink modules connected to X67BC8321-1did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs onBC and SL: X20BC0083 X20cBC0083 < HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed: No Configuration description changed:No Firmware changed: No ID: 621720 / Support ID: 400264883 Display of further diagnostic data points in the I / O mapping of the X2X interface from the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware:1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configurationdescription changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiRsupport Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel descriptionchanged: No Configuration description changed: No Firmware changed:Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration descriptionchanged: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X busof the BC - new objects: 20A3h and 2000h/9 - support for Simulationdevice added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152),1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensionsand Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed:No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to notexisting objects in OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.14.0.0 | * | 25/10/2021 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.14.0.0: ID: 737340 NUMBER:JACK improved ISN (TCP start sequence) generation in IP stack Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 737345 POWERLINK Security Vulnerability (CVE-2020-13987 & CVE-2020-17438) POWERLINK Security Vulnerability (CVE-2020-13987) The POWERLINK IP stack was affected by a security vulnerability impacting thechecksum calculation of TCP/UDP packets. POWERLINK Security Vulnerability (CVE-2020-17438) The POWERLINK IP stack was affected by a security vulnerability impacting fragmented packet reassembly. Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 739455 Module documentation revised Data sheet V3.08 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(432), 1\42917_3.fw(432) Version 2.11.1.0: ID: 697885 Support for automatic DNA configuration from AS 4.9.1 Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.11.0.0: ID: 664420 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 665800 ModuleOk ofIO module FALSE after warm restart even though the module is working as expected Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 665880 Accessing non-cyclicregisters with AsIOAcc while ModuleOk = FALSE prevents module from starting/communicating Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 666165 Module documentation revised Data sheet V3.06 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.9.3.0: ID:639730 / Support ID: 400268096 Alignment of AS output according to the FieldBusDesigner Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(427),1\42917_3.fw(427) Version 2.9.0.0: ID: 629050 Ring redundancy: Cannot address the CN that closes the ring Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629125 DNA: BC as head-end station switching hub off again Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629200 Shortened preamble of Ethernet frame leading to incorrectly detected CRC errors Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629245 Optimization of hub behavior Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behindthe bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate of X2XLink module at POWERLINK Stations does not work since H4.34 Since H4.34 the firmware update of X2XLink modules connected to X67BC8321-1did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs on BC and SL: X20BC0083 X20cBC0083 < HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 621720 / Support ID: 400264883 Display of further diagnostic data points in the I / O mapping of the X2X interface from the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPUPowerCycle wenn SLXhinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FWupgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on theCPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes -Firmware-Version is transferred via IdentResponse in the first 4 bytes of thefield VendorSpecificExt1 - Support of PollResponse-Chaining Channeldescription changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb theBC (only possible with 3rd party MN) - Access to not existing objects inOD could cause firmware crash - When running X2X cycle times <200 us theX2X Bus was not working correctly(A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.11.1.0 | * | 24/08/2020 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.11.1.0: ID: 697885 Support for automatic DNA configurationfrom AS 4.9.1 Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.11.0.0: ID: 664420 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 665800 ModuleOk of IO module FALSE after warm restart even though the module is working as expected Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 665880 Accessing non-cyclic registers with AsIOAcc while ModuleOk = FALSE preventsmodule from starting/communicating Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 666165 Module documentation revised Data sheet V3.06 Channel descriptionchanged: No Configuration description changed: No Firmware changed:No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.9.3.0: ID: 639730 / Support ID: 400268096 Alignment of AS output according to the FieldBusDesigner Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.9.0.0: ID: 629050 Ring redundancy: Cannot address the CN that closes the ring Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629125 DNA: BC as head-end station switching hub off again Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629200 Shortened preamble of Ethernet frame leading to incorrectly detected CRC errors Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629245 Optimization of hub behavior Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmwarechanged: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behind the bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate of X2XLink module at POWERLINK Stations does not work since H4.34 Since H4.34 the firmware update of X2XLink modules connected to X67BC8321-1did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs on BC and SL: X20BC0083 X20cBC0083 < HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 621720 / Support ID: 400264883 Display of further diagnostic data points in the I / O mapping of the X2X interfacefrom the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDP ASnd SDO transfert after long timetakes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed:No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware:1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware:1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed:No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operationin Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) -Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objects in OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.11.0.0 | * | 20/02/2020 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.11.0.0: ID: 664420 Adaptations for Automation Studio 4.8 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 665800 ModuleOk of IO module FALSE after warm restart even though the module is working as expected Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 665880 Accessing non-cyclic registers withAsIOAcc while ModuleOk = FALSE prevents module from starting/communicating Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 666165 Module documentation revised Data sheet V3.06 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(430), 1\42917_3.fw(430) Version 2.9.3.0: ID: 639730 / Support ID: 400268096 Alignment of AS output according to the FieldBusDesigner Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.9.0.0: ID: 629050 Ring redundancy: Cannot address the CN that closes the ring Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629125 DNA: BC as head-end station switching hub off again Channel description changed: No Configuration description changed: No Firmwarechanged: Yes ID: 629200 Shortened preamble of Ethernet frame leading to incorrectly detected CRC errors Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629245 Optimization of hub behavior Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behind the bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate ofX2XLink module at POWERLINK Stations does not work since H4.34 Since H4.34 the firmware update of X2XLink modules connected to X67BC8321-1did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs on BC and SL: X20BC0083 X20cBC0083< HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed:No Configuration description changed: No Firmware changed: No ID: 621720 / Support ID: 400264883 Display of further diagnostic datapoints in the I / O mapping of the X2X interface from the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 FirstPOWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channeldescription changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modulesin connection with PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2XFW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINKbus controllers no longer achieving Operationalmode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411),1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achievingOperationalmode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID:400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BCimproved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happenedthat IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objects in OD could causefirmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.9.3.0 | * | 12/04/2019 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.9.3.0: ID: 639730 / Support ID: 400268096 Alignment of AS output according to the FieldBusDesigner Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.9.0.0: ID: 629050 Ring redundancy: Cannot address the CN that closes the ring Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629125 DNA: BC as head-end stationswitching hub off again Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629200 Shortened preamble of Ethernet frame leading to incorrectly detected CRC errors Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629245 Optimization of hub behavior Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behind the bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configurationdescription changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate of X2XLink module at POWERLINK Stations does not work since H4.34 Since H4.34 the firmware update of X2XLink modules connected to X67BC8321-1did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs on BC and SL: X20BC0083 X20cBC0083 < HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 621720 / Support ID: 400264883 Display of further diagnostic data points in the I / O mapping of the X2X interface from the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with onlyinput datapoints, are not initialized.by SL Channel description changed:No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration descriptionchanged: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontrollerwas interrupted. Restarting the boscontroller restored communication. Loss ofasynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Updateof IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed:No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/Oconstellations, the X2X modules don't start Channel description changed:No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse inthe first 4 bytes of the field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objects in OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.9.0.0 | * | 13/03/2019 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.9.0.0: ID: 629050 Ring redundancy: Cannot address the CN that closes the ring Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629125 DNA:BC as head-end station switching hub off again Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629200 Shortened preamble of Ethernet frame leading to incorrectly detected CRC errors Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 629245 Optimization of hub behavior Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(427), 1\42917_3.fw(427) Version 2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behind the bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate of X2XLink moduleat POWERLINK Stations does not work since H4.34 Since H4.34 the firmwareupdate of X2XLink modules connected to X67BC8321-1 did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs on BC and SL: X20BC0083 X20cBC0083 < HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed: No Configuration description changed: No Firmware changed: No ID: 621720 / Support ID: 400264883 Display of further diagnostic data points in the I / O mapping of the X2X interface from the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2XFW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllersno longer achieving Operationalmode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restoredcommunication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules withbig FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication(unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASndframes with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objects in OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.8.0.0 | * | 12/12/2018 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.8.0.0: ID: 619240 / Support ID: 400257683 DNA: PLK hub forwarding for the next node not enabled in rare cases Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619270 / Support ID: 400262159 Outputs of I/O modules behind the bus coupler not working in some cases if poll-response chaining active Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 619650 / Support ID: 400268920 Firmwareupdate of X2XLink module at POWERLINK Stations does not work since H4.34 Since H4.34 the firmware update of X2XLink modules connected to X67BC8321-1did not work, if they are connected to POWERLINK-Buscontrollers that have no explicit enable for streaming. Problem occurs on BC and SL: X20BC0083 X20cBC0083 < HW-Upgrade 2.2.0.0 X20BC1083 X20cBC1083 < HW-Upgrade 2.5.0.0 X20BC8083 X20cBC8083 < HW-Upgrade 2.5.0.0 X20BC8084 X20cBC8084 < HW-Upgrade 2.5.0.0 X20SL8101 X20cSL8101 X67BC81RT.L12 < HW-Upgrade 2.5.0.0 X67BC8321-1 X67BC8331 X67BC8513.L12 Channel description changed: No Configuration description changed: No Firmwarechanged: No ID: 621720 / Support ID: 400264883 Display of further diagnostic data points in the I / O mapping of the X2X interface from the X67 bus controller Channel description changed: Yes Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(426), 1\42917_3.fw(426) Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with only input datapoints, arenot initialized.by SL Channel description changed: No Configurationdescription changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220/ Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modulesbehind POWERLINK bus controllers no longer achieving Operationalmode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanentboot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID:400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configurationdescription changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configurationdescription changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID:277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior onX2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC -new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeIDassignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objectsin OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.5.6.0 | * | 23/07/2018 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.5.6.0: ID: 603859 APROL: missing attribute for channel-parameter with "Sig_*" inserted. Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 /Support ID: 400202320 BC sporadically not going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063, 400190752 First POWERLINK UDPASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connectionwith PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 / Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed:No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINK V1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link-selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmulti with SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID: 299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavior on X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with high X2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions and Bugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) - Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objects in OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |
|||||
Version | Langue | Système d'exploitation | Date | Taille | Type | Téléchargement |
2.5.5.0 | * | 08/09/2017 | 2 Mo | EXE | AS4_HW_X67BC8331.exe | |
Description |
V4.0 HW Upgrade (X67BC8331) Revision information X67BC8331 Version 2.5.5.0: ID: 551155 Startup time optimizations Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(421), 1\42917_3.fw(421) Version 2.5.4.0: ID: 540355 / Support ID: 400202320 BC sporadicallynot going into Operational due to X2X-bus problems at startup Channel description changed: No Configuration description changed: No Firmwarechanged: Yes Firmware: 1\42917_1.fw(419), 1\42917_3.fw(419) Version 2.5.2.0: ID: 493920 / Support ID: 400103115, 400101850, 400154063,400190752 First POWERLINK UDP ASnd SDO transfert after long time takes up to 5s. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(415), 1\42917_3.fw(415) Version 2.5.0.0: ID: 468210 / Support ID: 400178654 Safety modules in connection with PLK BCs, with only input datapoints, are not initialized.by SL Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468215 optimization of X2X FW updates Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468220 / Support ID: 400177243 X2X FW update of several X2X modules is not working Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 468580 CiR support Channel description changed: No Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(413), 1\42917_3.fw(413) Version 2.2.0.0: ID: 460145 / Support ID: 400168329 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 460265 /Support ID: 400150525 Error 114834 "Fehler interner SLX-Kommandokanal" bei CPU PowerCycle wenn SLX hinter BC Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(411), 1\42917_3.fw(411) Version 2.1.0.0: ID: 439140 / Support ID: 400150496 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 439245 / Support ID: 400128436 I/O modules behind POWERLINK bus controllers no longer achieving Operational mode after multiple power-on cycles Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(400), 1\42917_3.fw(400), 1\42917_5.fw(400) Version 2.0.0.0: ID: 390310 / Support ID: 400129274 Uncommon X2X settings cause permanent boot of bus controller Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(210), 1\42917_3.fw(210) Version 1.3.4.0: ID: 310880 / Support ID: 400097674 POWERLINK V1: Bug-fix for Up/Downgrade POWERLINKV1 FW upgrade problem could be accored after PowerOn beginning with HW- Upgrade Version 1.3.1.0 Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 311045 / Support ID: 400051206 Expansion: Link- selector flag New datapoints:<br/>- RedundancyFirstLinkState<br/>- RedundancySecondLinkState Channel description changed: Yes Configuration description changed: Yes Firmware changed: No Firmware: 1\42917_1.fw(168), 1\42917_3.fw(168) Version 1.3.3.0: ID: 305185 / Support ID: 400094368 ACOPOSmultiwith SafeMC, asynchronous communication lost When there was a high load on the CPU, asynchronous communication to the buscontroller was interrupted. Restarting the boscontroller restored communication. Loss of asynchronous communication caused the safety-IO to stop. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(167), 1\42917_3.fw(167) Version 1.3.2.0: ID:299005 / Support ID: 400090781 Problem with FW-Update of IO modules on Powerlink buscontrollers The firmware update of IO modules does not work in certain configurations. Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(165), 1\42917_3.fw(165) Version 1.3.1.0: ID: 289035 Certain X2X configurations don't work In very rare I/O constellations, the X2X modules don't start Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(163), 1\42917_3.fw(163) Version 1.3.0.0: ID: 277195 Support of 'Multiple Asynchronous Send' Channel description changed: No Configuration description changed: No Firmware changed: Yes ID: 277765 New X2X datapoints - NettimeOffsetX2X and NettimeX2X Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(160), 1\42917_3.fw(160) Version 1.2.0.0: ID: 246690 DNA support; Update behavioron X2X bus of the BC improved - DNA support (Dynamic Node Allocation) - faster updating of modules with big FW files on the X2X bus of the BC - new objects: 20A3h and 2000h/9 - support for Simulation device added Channel description changed: Yes Configuration description changed: Yes Firmware changed: Yes Firmware: 1\42917_1.fw(152), 1\42917_3.fw(152) Version 1.0.8.0: ID: 218520 Extensions and Bugfixes - Firmware-Version is transferred via IdentResponse in the first 4 bytes ofthe field VendorSpecificExt1 - Support of PollResponse-Chaining Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(145) Version 1.0.7.0: ID: 214450 Extensions and Bugfixes - In systems with highX2X load it happened that IO modules were not restarted when the CPU did a warmstart (A&P 211805) - Activation of MultipleRead/Write feature for faster startup after configuration change - Writing to Objekt 20F0h/SubIndex 22 caused SDO errors when accessed faster than allowed - Number of configuration entries per IO module changed from 100 to 155 Channel descriptionchanged: No Configuration description changed: No Firmware changed:Yes Firmware: 1\42917_1.fw(144) Version 1.0.6.0: ID: 210945 Extensions and Bugfixes - Error correction for operation in Powerlink V1 networks (A&P 210765) Channel description changed: No Configuration description changed: No Firmware changed: Yes Firmware: 1\42917_1.fw(143) Version 1.0.5.0: ID: 209765 Extensions andBugfixes - New ASICS will be set to 3mA output current (A&P 182905) - Optimization of SDO communication (unnecessary acknowledges removed) -Support of commands ReadMultipleParameter / WriteMultipleParameter - NodeID assignment by digital inputs supported (NodeId 241 and 242) - Minor corrections certification - ASnd frames with unknown ServiceID could disturb the BC (only possible with 3rd party MN) - Access to not existing objects in OD could cause firmware crash - When running X2X cycle times <200 us the X2X Bus was not working correctly (A&P 190630) - When in state PREOP_2 no SoC is received for 10sec the BC will fall back in PREOP_1 Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(142) Version 1.0.0.0: ID: 190480 Support X67BC8331 Support X67BC8331, first version Channel description changed: No Configuration description changed: No Firmware changed: No Firmware: 1\42917_1.fw(141) |