Changelog v7.2.0
Release v7.2.0 provides a series of bug fixes and additional driver support.
It now requires Java JRE 17 (included in the Windows Version).
A detailed list of new features and bugfixes can be found below.
- 1 General
- 2 CANopen
- 2.1 New and Noteworthy
- 2.2 Bugfixes
- 3 EtherCAT
- 3.1 New and Noteworthy
- 3.2 Bugfixes
General
New and Noteworthy
Type | Key | Summary | Description |
---|---|---|---|
Story | Update to JDK 17 | Compile and run with JDK 17. | |
Story | Update to Eclipse 2022-12 | Update to Eclipse framework 2022-12. |
CANopen
New and Noteworthy
Type | Key | Summary | Description |
---|---|---|---|
Story | Update CiA profiles 301, 302 and 306 | Fix several issues in the CiA profiles 301, 302 and 306. | |
Story | Add driver support for XMC4xxx FreeRTOS | Add driver support for the Infineon XMC4xxx CPU family. | |
Story | Add initial support for CANopen library v4.7.x | Add initial support for CANopen library v4.7.x | |
Story | Add driver support for NXP LPC4000 family using FreeRTOS | Add driver support for the NXP LPC4000 family using FreeRTOS. | |
Story | Add driver support for Renesas RX66T | Add driver support for Renesas RX66T bare metal. | |
Story | Add driver support for Renesas RA6M5 | Add CANopen driver support for Renesas RA6M5. | |
Story | Driver support for STM32F4xx uCOSII | Add driver support for STM32F4xx using uCOSII. | |
Story | Use 64 bit data types for Linux by default | The default value for 64 bit data types for Linux (Configurations > Configuration > CPU Settings: Linux > Use 64 bit data types) should be “enabled”. |
Bugfixes
Type | Key | Summary | Description |
---|---|---|---|
Bug | Wrong heartbeat consumer values calculated | The default values for the heartbeat consumer entries are not correctly calculated. | |
Bug | RECORD with octet-string not shown | The UI does not display subentries for records with octet string types. | |
Bug | After converting CANopen project, describing files no longer generated | After converting an ICC project from CANopen library version v4.6 to v.7, the describing files (*.eds, *xdd, *.txt etc.) are no longer generated. | |
Bug | Export profile button accidentally disabled | Export button for profile buttons is disabled as soon as the index is changed. | |
Bug | PDO Dummy Mapping entries show erroneous warnings | The ICC shows warning when data types are mapped to receive PDOs. As those entries are just placeholders, the warning is not correct and needs to be removed. | |
Bug | Wrong values for object 0x1016 cannot be fixed | Wrong values larger than 0x007FFFFF cannot be corrected using the UI as the text field is disabled even if Non-standard extensions are enabled. | |
Bug | Driver for XMC4xxx bare metal only allows selection of XMC4200 | The driver for the Infineon XMC4xxx CPU family supports the XMC4200, XMC4300, XMC4500 and XMC4800. But only the XMC4200 can be selected. | |
Bug | Project error when disabling TPDO/RTR | The ICC reports an error when RTR is disabled for object 0x1800 COB-ID. | |
Bug | Wrong caption for PDO SYNC start value | The caption for PDO SYNC start values is incorrect and needs to be rearranged. | |
Bug | Redundant doublication of CONFIG_CAN_OBJECTS | Avoid doubling of objects when 0x1F60 exists and Redundancy is active. | |
Bug | Number of segment per blocks for SDO allows invalid values | Fix upper and lower bounds for number of segment per blocks for SDO block transfer. | |
Bug | Rework of settings for SDO block transfer | Rework and cleanup of settings for SDO block transfer. | |
Bug | Erroneous warning when object 1001h is mapped into a PDO | In case object 1001h is mapped into a PDO, a warning is shown that this object is not allowed to be mapped. But according to standard, it is allowed to be mapped to TPDO. | |
Bug | Missing setting for CO_CONFIG_REDCY_INACTIVE_PDO_DATA_IND | The setting Project Setting > Services > Application Layer > Enable indication for PDO data received on inactive CAN line for compiler define | |
Bug | Variable generation for multi-line line-dependent objects incorrect | When generating line-indepedent objects, the values for all related objects should be stored in a common C variable. |
EtherCAT
New and Noteworthy
Type | Key | Summary | Description |
---|---|---|---|
Story | Support for EtherCAT data type REAL64 | Add experimental support for |
Bugfixes
Type | Key | Summary | Description |
---|---|---|---|
Bug | Wrong default names for Sync Manager PDO assignment objects | The default names for Sync Manager PDO assignment objects 0x1C10 and above contain a wrong number which is too low by one. | |
Bug | Allow selection of PDOs from modules as default mapping in base OD | When using MDP, it should be possible to select objects from modules as default mapping in the basic object dictionary of the device. | |
Bug | SafetyPdoType attribute missing for TxPdo tags in ESI files | When safety relevant data is mapped in the Tx PDOs, the according | |
Bug | User specific part in ecat_conf.h is overwritten | In the file ecat_Conf.h there is an area that is enclosed by the macros | |
Bug | Import of OD from ESI File leads to invalid objects 0x1C12:00 and 0x1C13:00. | If the object dictionary was imported from an ESI file, Objects | |
Bug | Wrong upper limits when converting EDT projects | In case a project from the legacy EtherCAT Design Tool (ECT) is imported, data objects may contain incorrect upper limits. | |
Bug | Invalid length definition for strings in ESI file | When a data type of As an example, a
Instead, it should result in:
| |
Bug | Incomplete object value tables generated | The ICC generates the object dictionary as tables in the file For each table type the ICC creates an empty table that is missing a data type and the postfix in its name. These tables are: |