New features in v2.98 - Revision history

Jonas: /* Signal Reader supports MDF4 Event Blocks for frame logs */

2026-05-21T13:04:11Z

Signal Reader supports MDF4 Event Blocks for frame logs

← Older revision		Revision as of 13:04, 21 May 2026
Line 28:		Line 28:
	== Signal Reader supports MDF4 Event Blocks for frame logs ==		== 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.		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.

			== Support to merge DBC files ==
			There is support to merge uploaded DBC files.

Robin.karhu: /* Resource group WMUs */

2026-05-21T10:52:00Z

Resource group WMUs

← Older revision		Revision as of 10:52, 21 May 2026
Line 6:		Line 6:

	== Resource group WMUs ==		== 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.		It is now possible to configure [[WMU\|WMUs]] for a resource group from the [[I/O configurations\|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 ==		== 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.		The Reported WMUs view in the [[I/O configurations\|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. ==		== Permission to control edit of WCUs and Vehicles. ==

Robin.karhu: /* Show existing PINs for resource groups */

2026-05-21T09:42:30Z

Show existing PINs for resource groups

← Older revision		Revision as of 09:42, 21 May 2026
Line 1:		Line 1:
	== Show existing PINs for resource groups ==		== Show existing PINs for resource groups ==
	The button '''Fetch PINs''' in the [[The Portal Administrator View#The Resource Groups Tab\|Resource Groups tab]] has been changed to '''Manage PINs'''. Pressing Manage PINs opens a ~~submenu~~ 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 ~~submenu~~. 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.		The button '''Fetch PINs''' in the [[The Portal Administrator View#The Resource Groups Tab\|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 ==		== Enable fetching PINs from PIE for individual vehicles ==

Robin.karhu: /* Show existing PINs for resource groups */

2026-05-21T09:41:58Z

Show existing PINs for resource groups

← Older revision		Revision as of 09:41, 21 May 2026
Line 1:		Line 1:
	== Show existing PINs for resource groups ==		== Show existing PINs for resource groups ==
	~~In the Resource Groups tab there is now a~~ button '''~~Manage~~ PINs''' ~~which used~~ to be '''~~Fetch~~ PINs'''. Pressing Manage PINs opens a submenu 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 submenu. 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.		The button '''Fetch PINs''' in the [[The Portal Administrator View#The Resource Groups Tab\|Resource Groups tab]] has been changed to '''Manage PINs'''. Pressing Manage PINs opens a submenu 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 submenu. 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 ==		== Enable fetching PINs from PIE for individual vehicles ==

Robin.karhu: PINs and WMUs

2026-05-21T09:15:49Z

PINs and WMUs

← Older revision		Revision as of 09:15, 21 May 2026
Line 1:		Line 1:
	== Show existing PINs for resource groups ==		== Show existing PINs for resource groups ==
			In the Resource Groups tab there is now a button '''Manage PINs''' which used to be '''Fetch PINs'''. Pressing Manage PINs opens a submenu 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 submenu. 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 ==		== 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 ==		== 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 ==		== 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. ==		== Permission to control edit of WCUs and Vehicles. ==

Mathias at 07:08, 21 May 2026

2026-05-21T07:08:46Z

← Older revision		Revision as of 07:08, 21 May 2026
Line 17:		Line 17:

	== New trigger expression for DM1 Diagnostic Trouble Codes in Signal Reader ==		== 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.		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 ==		== Signal Reader supports channel mapping as meta information for frame logs ==

Henrik.Moller: /* Permission to control edit of WCUs. */

2026-05-21T06:57:51Z

Permission to control edit of WCUs.

← Older revision		Revision as of 06:57, 21 May 2026
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 a new ~~permission~~ that ~~determines~~ whether a user can edit a WCU. In the portal ~~the permission is~~ called "WCU View Permission" (wcu:view:write). Read more about it [[Roles and permissions\|here]].		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 ==

Mathias: framelog mf4 event block

2026-05-21T06:49:31Z

framelog mf4 event block

← Older revision		Revision as of 06:49, 21 May 2026
Line 18:		Line 18:
	== New trigger expression for DM1 Diagnostic Trouble Codes in Signal Reader ==		== 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.		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.

Mathias: DM1 Triggers

2026-05-21T06:43:38Z

DM1 Triggers

← Older revision		Revision as of 06:43, 21 May 2026
Line 15:		Line 15:
	== Signal Reader supports LIN frame logging in MDF4 format ==		== 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.		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.

Henrik.Moller: /* Permission to control edit of WCUs. */

2026-05-21T06:43:03Z

Permission to control edit of WCUs.

← Older revision		Revision as of 06:43, 21 May 2026
Line 8:		Line 8:

	== Permission to control edit of WCUs. ==		== Permission to control edit of WCUs. ==
	Starting from version 2.98.0, administrators can assign a new permission that determines whether a user can edit a WCU. Read more about it here.		Starting from version 2.98.0, administrators can assign a new permission that determines whether a user can edit a WCU. In the portal the permission is called "WCU View Permission" (wcu:view:write). Read more about it [[Roles and permissions\|here]].

	== Add or revoke permissions to existing tasks ==		== Add or revoke permissions to existing tasks ==