New features in v2.98: Difference between revisions
framelog mf4 event block |
|||
| Line 7: | Line 7: | ||
== Add reported WMU to WCU's WMU configuration == | == Add reported WMU to WCU's WMU configuration == | ||
== Permission to control edit of WCUs. == | == Permission to control edit of WCUs and Vehicles. == | ||
Starting from version 2.98.0, administrators can assign | Starting from version 2.98.0, administrators can assign new permissions that determine whether a user can edit a WCU or a vehicle. In the portal, these permissions are called '''WCU View Permission''' (<code>wcu:view:write</code>) for WCUs and '''Vehicle Edit Permission''' (<code>vehicle:view:write</code>) for vehicles. Read more about it [[Roles and permissions|here]]. | ||
== Add or revoke permissions to existing tasks == | == Add or revoke permissions to existing tasks == | ||
Revision as of 06:57, 21 May 2026
Show existing PINs for resource groups
Enable fetching PINs from PIE for individual vehicles
Resource group WMUs
Add reported WMU to WCU's WMU configuration
Permission to control edit of WCUs and Vehicles.
Starting from version 2.98.0, administrators can assign new permissions that determine whether a user can edit a WCU or a vehicle. In the portal, these permissions are called WCU View Permission (wcu:view:write) for WCUs and Vehicle Edit Permission (vehicle:view:write) for vehicles. Read more about it here.
Add or revoke permissions to existing tasks
The options to add or revoke permissions to existing tasks have been improved from version 2.98. In summary, when removing a WCU from a permission either by removing it as resource from the permission itself, or by removing it from the resource group used in the permission or by removing the permission label from the resource, access to existing tasks can also be removed. More information and example can be found in Roles and permissions#Permission for specific tasks.
Signal Reader supports LIN frame logging in MDF4 format
Signal Reader now supports LIN frame logging in MDF4 format in addition to ASC format. The setting for whether to use MDF4 or ASC is the same as for CAN frame logging, in the Signal Reader module configuration.
New trigger expression for DM1 Diagnostic Trouble Codes in Signal Reader
A new type of trigger expression makes it possible to react DM1 DTC, by triggering on ECU id, SPN and FMI.
Signal Reader supports channel mapping as meta information for frame logs
When logging CAN and LIN frames in MDF4, meta-information is added to the output file describing the mapping of the CAN/LIN buses.
Signal Reader supports MDF4 Event Blocks for frame logs
Signal Reader can now generate MDF4 Event Blocks for frame logs in the same way as for signal logs. This makes it easier to correlate frame logs and signal logs (and other data) in post-processing operations.