| Key | Issue Type | Summary | Resolution | Note |
|---|---|---|---|---|
| TRACE-277 | Bug | Device Trace: Variables can be deleted in the Device Trace online mode, using the Delete keyboard key |
Fixed | [[GENERAL]] Delete, Cut, Paste and <Del>, <Strg+X>, <Strg+V> are no longer supported for Device Traces |
| TRACE-276 | Bug | Deleting the last diagram is not possible |
Fixed | |
| TRACE-273 | Bug | Strange behaviour when unchecking diagrams and variables |
Fixed | |
| TRACE-272 | Bug | Checkstate of variable is changed when moving to individual diagrams |
Fixed | |
| TRACE-261 | Bug | SignalPane: Adjusted column widths get lost after reopening the trace editor |
Fixed | |
| TRACE-257 | Bug | Unexpected changes when editing variable name in diagram tree |
Fixed | [[GENERAL]] When a signal in a trace diagram is renamed, then a new variable is inserted in the list of trace variables, if the variable does not already exist in the list of variables, and this new variable will be referred in the diagram. Other references to the same variable are not affected by the change. |
| TRACE-244 | Bug | Scale in microsecs changes to millisecs after reset warm/cold |
Fixed | |
| TRACE-243 | Bug | Exception when deselecting all trace variables |
Fixed | |
| TRACE-242 | Bug | Scripting: a legacy trace might be created |
Fixed | [[GENERAL]] The scripting interface for trace.create expects a parent object. Depending on whether this is a device or an application, a device trace or an application trace is created. |
| TRACE-241 | Bug | Trace, Trace Configuration, Add New Variable, Intellisense: No Intellisense for Softmotion Axis variables is supportet |
Fixed | [[GENERAL]] This implements a partial fix in the trace. The full issue can only be fixed with the next codesys service pack release. |
| TRACE-238 | Improvement | DeviceTrace for Safety device |
Fixed | [[GENERAL]] A devicetrace can now be placed below every device that has the targetsetting "trace/tracemgr" set to 1. |
| TRACE-237 | Bug | F1 within an open trace object/tab does only lead to on generic Helppage |
Fixed | |
| TRACE-235 | Bug | SignalPane: Repeated insertion using Strg+C/Strg-V does not work reliable |
Fixed | |
| TRACE-233 | Bug | SignalPane: Drag&Drop of variable into SignalPane does not work with recent CODESYS versions |
Fixed | |
| TRACE-176 | Bug | Trace Configuration: key combination <strg+a> in "Variable" field not supported |
Fixed | |
| TRACE-144 | Bug | Trace: Strange behaviour with copy&paste |
Cannot Reproduce | |
| TRACE-143 | Bug | Trace: Paste Operation on Variables uses diagram name for target |
Fixed | |
| TRACE-142 | Bug | Trace: Drag&Drop should behave the same as Cut&Paste |
Cannot Reproduce | [[GENERAL]] In 4.4.0.0 Cut&Paste of variables in the trace editor behaves like Drag&Drop: in both cases an empty diagram is the result, if the last variable in the diagram is removed from the diagram. |
| TRACE-107 | Bug | TraceMgr: Samples of a trace might get lost |
Won't Fix | [[GENERAL]] Trace Samples of one variable with the same time stamp might get lost. The Trace is supposed to be a function of time. Each value is collected with the point in time at which the value is recorded. The problematic trace reported is a sequence of samples with 3 values with equal time stamps. When a new batch of values is collected from the runtime, the trace object searches for values with a newer time stamp than the already collected values. Therefore, if later collected values have a timestamp less or equal to previously collected time stamps, these values might get lost. |
| TRACE-82 | Epic | Trace editor: Allow non-ASCII identifiers for the trace name and traced variables |
Fixed | [[KNOWN_LIMITATIONS]] Unicode identifiers in recording tasks require a compiler version >= 3.5.18.0 with the enabled option "UTF8 Encoding for strings" |
| TRACE-75 | Improvement | Trace, Diagrams: Support Drag&Drop between diagrams |
Cannot Reproduce | |
| TRACE-68 | Bug | Trace: No tooltip if trace is stopped by trigger |
Won't Fix | [[GENERAL]] We do not display a tool tip in other situations as well. The trigger information is shown in the status bar. The values at the trigger event can be displayed with a cursor. |
| TRACE-66 | Bug | Trace, Intellisense: Shadowed POUs suggested for Trace Add Variable |
Cannot Reproduce | [[GENERAL]] This behaviour can not be fixed in the trace, but must be fixed with a standard service pack release. The current version SP21 already fixes this issue. |
| TRACE-63 | Bug | Trace: Fixed length time axis not working with us |
Fixed | |
| TRACE-62 | Bug | Trace editor, diff viewer: changes are not correctly applied if variables are deleted |
Cannot Reproduce | |
| TRACE-60 | Bug | Trace: csv file with recorded data of typ bit cannot be loaded |
Fixed | |
| TRACE-59 | Bug | Trace-Editor won't show the last variable in the list |
Cannot Reproduce | [[GENERAL]] The trace file uses data version 1.0.0.0. One variable is defined twice in the <TraceConfiguration> segment but only once in the <TraceRecord> segment, meaning the data for the last configuration entry is missing; therefore, the import behaves as expected. In version 4.4.0.0, exporting a variable used in multiple diagrams works correctly. Unfortunately there is no information on how the data was generated, but the use of an older version strongly suggests this is the result of a legacy export bug. |