| Key | Issue Type | Summary | Resolution | Release Note |
|---|---|---|---|---|
| CANOPEN-128 | Improvement | Update visibility of internal methods. |
Fixed | |
| CANOPEN-127 | Improvement | Reduce Sonarqube errors. |
Fixed | |
| CANOPEN-125 | Bug | Editor shows wrong settings when modification will be done on a locked object. |
Fixed | |
| CANOPEN-120 | Improvement | CANopen Safety Slave: The data types of the objects in the SRDO must match to those in the Safety I/O Mapping |
Fixed | |
| CANOPEN-113 | Improvement | 3S CANopenStackUnsafe: Activate and Complete LibDoc |
Fixed | |
| CANOPEN-107 | Improvement | CANbus: Possibility to deactivate auto reset. |
Duplicate | [[GENERAL]] Duplicated by CANOPEN-46, |
| CANOPEN-53 | Improvement | PDO Mapping Editor: Columns are not adjusted when opening the editor. |
Fixed | |
| CANOPEN-52 | Bug | CANopenSlave: Mapping on existing variable in ObjectDictionary isn't possible with array elements |
Fixed | |
| CANOPEN-50 | Bug | CANopen Stack: Unclear error messages generated in the Log by CANbus component |
Won't Fix | [[GENERAL]] This is as designed! To reduce memory footprint logger messages of CAN stacks only contain binary data which will be translated in the CODESYS logger GUI by LoggerTextTranslator. The strings used by the translator are part of CANbus/CANopenManager/J1939Manager devdesc. If unclear messages are shown on customer side there are two possible error reasons: 1. The manager and CANbus devdesc of the customer misses the logger strings. ==> Update devdesc accordingly to default CODESYS devdesc content. 2. Customer implements a custom logger which doesn't use the LoggerTextTranslator. ==> Change implementation accordingly ==> No error on CODESYS side! ==> Won't fix |
| CANOPEN-48 | Improvement | CANOpenStack: Too much mailbox full log messages, if no slave connected with CANopen |
Fixed | |
| CANOPEN-46 | Improvement | CANbus: Possibility to deactivate auto recovery for CAN stacks |
Fixed | [[COMPATIBILITY_INFORMATION]] Error passive will not be treated as bus error anymore because sending/receiving works in a normal way in this state and it will be recovered automatically. Only bus off state will be treated as bus error. Device now shows a red exclamation mark if Error Passive is pending. |
| CANOPEN-45 | Improvement | CANbus: Ignore Error Passive |
Duplicate | [[GENERAL]] Fixed with CANOPEN-46. Error passive will not be treated as bus error anymore because sending/receiving works in a normal way in this state and it will be recovered automatically. Only bus off state will be treated as bus error. Device now shows a red exclamation mark if Error Passive is pending. |
| CANOPEN-44 | Improvement | Improve performance for CANopen device |
Fixed | |
| CANOPEN-42 | Bug | CANopen: Some CANopen objects are not available for PDO Mapping |
Fixed | [[GENERAL]] For SELXM32A_0126E the behavior is as designed. The eds file has a granularity of 16bit. So, only mapping entries >= 16 bit are allowed. For ASD-A2 servo drive_2 the behavior was wrong and fixed. Granularity 5 means all objects >= 5 bits can be mapped. In previous versions, the CANopen configurator only showed objects which are a multiple of 5. |
| CANOPEN-39 | Bug | CANopen: DCF Import does not set Communication Cycle Period |
Won't Fix | [[GENERAL]] Communication cycle period is a setting in the CANopenManager device. A slave DCF should not change settings in the Manager device node because there could be different DCF files with conflicting communication cycle period. ==> Won't Fix |
| CANOPEN-38 | Bug | CANopen, Device: In tab "General" the Vendor-, Product- and Revision number should displayed as UDINT |
Fixed | |
| CANOPEN-37 | Bug | CAN Configurator: CAN_Sync Cycle period not respected in call of associated External task |
Cannot Reproduce | [[GENERAL]] Error in CANminidriver implementation of customer. |
| CANOPEN-34 | Bug | CANbus library references CANbus Use Case Library. |
Fixed | |
| CANOPEN-29 | Bug | CANopenSafety: SRDO Views are not shown if mapping object is not part of EDS. |
Fixed | |
| CANOPEN-27 | Bug | CANopen SIL2: SRDO editor is not shown if some CRC objects are missing. |
Fixed | |
| CANOPEN-26 | Bug | CANopen Manager: Inconsistent project if SVN or user management blocks write access to application object. |
Fixed | |
| CANOPEN-25 | Improvement | Fieldbus Low/High Profile / CANopen: Licence Check |
Fixed | |
| CANOPEN-22 | Improvement | Use new CanEds GAC |
Fixed | |
| CANOPEN-21 | Bug | Mapped objects of an EDS file are not shown in the PDOs tab |
Duplicate | [[GENERAL]] For SELXM32A_0126E the behavior is as designed. The eds file has a granularity of 16bit. So, only mapping entries >= 16 bit are allowed. For ASD-A2 servo drive_2 the behavior was wrong and fixed. Granularity 5 means all objects >= 5 bits can be mapped. In previous versions, the CANopen configurator only showed objects which are a multiple of 5. |
| CANOPEN-15 | Bug | DeviceEditorCANbus: Config Version conversion may lead to inconsistent config data if any error occurs on recursive update. |
Fixed | |
| CANOPEN-12 | Improvement | Fieldbus Low/High Profile / CANopen: Count and Display used IO-Data Bytes |
Fixed | |
| CANOPEN-10 | Bug | Potential exception when creating I/O channels |
Fixed | |
| CANOPEN-9 | Improvement | CANopenDevice: Remove IoDrvUtilities Placeholder |
Fixed | |
| CANOPEN-7 | Improvement | CANopenStack: Support event time and inhibit time on RPDO's |
Fixed | |
| CANOPEN-6 | Bug | CANopenStack: No communication if more than 256 TPDOs. |
Fixed | |
| CANOPEN-5 | Bug | CANopen: Hidden I/O mappings if module will be moved. |
Fixed | |
| CANOPEN-4 | Bug | CANopen: Remove Sonarqube bugs and blocking code smells |
Fixed |