New features in v2.98
Show existing PINs for resource groups
The button Fetch PINs in the Resource Groups tab has been changed to Manage PINs. Pressing Manage PINs opens a menu to where the previous Fetch PINs function has been moved. Additionally the ability to check which ECUs and areas have missing PINs and which have existing PINs are also accessible from the menu. Selecting check missing PINs from this menu will allow the user to select which ECUs and areas the check should be performed on. Checking existing PINs has been available for individual vehicles since 2.97.0, but from this menu it is now also possible to check existing PINs across the whole resource group.
Enable fetching PINs from PIE for individual vehicles
Since 2.97.0 it has been possible to view which ECUs and areas have PINs for a given vehicle through Edit Vehicle, from that view it will now also be possible to fetch PINs from PIE for that vehicle.
Resource group WMUs
It is now possible to configure WMUs for a resource group from the I/O tab in the group's WCU configuration, same as how it works for individual WCUs.
Add reported WMU to WCU's WMU configuration
The Reported WMUs view in the I/O tab of the WCU configuration now has a button to more conveniently add the reported WMU to the 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. For more information, see Signal Reader Trigger Expressions.
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.