WICE Wiki v2.98 - Recent changes [en]

New features in v2.98

Jonas — Thu, 21 May 2026 13:04:11 GMT

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.

New features in v2.98

Robin.karhu — Thu, 21 May 2026 10:52:00 GMT

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. ==

The Portal Administrator View

Robin.karhu — Thu, 21 May 2026 09:42:59 GMT

Manage PINs

← Older revision		Revision as of 09:42, 21 May 2026
Line 679:		Line 679:

	==== Manage PINs ====		==== Manage PINs ====
	For portals with [[Vehicle Communication Forwarder\|VCF]] enabled this button opens a ~~submenu~~ with three selections:		For portals with [[Vehicle Communication Forwarder\|VCF]] enabled this button opens a menu with three selections:

	* '''Check Existing PINs'''. Checks which ECUs and areas have PINs for each vehicle (grouped by WCU) in the resource group.		* '''Check Existing PINs'''. Checks which ECUs and areas have PINs for each vehicle (grouped by WCU) in the resource group.

New features in v2.98

Robin.karhu — Thu, 21 May 2026 09:42:30 GMT

Show existing PINs for resource groups

← Older revision		Revision as of 09:42, 21 May 2026
(One intermediate revision by the same user not shown)
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 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 ==

The Portal Administrator View

Robin.karhu — Thu, 21 May 2026 09:36:37 GMT

Manage PINs

← Older revision		Revision as of 09:36, 21 May 2026
(One intermediate revision by the same user not shown)
Line 678:		Line 678:
	You can require that assignments must have been reviewed and approved before they can be applied to a resource group by checking the box "Require Approved Assignments". If an assignment does not meet these criteria, the assignment will not be applied to the resource group. Read more about the assignment review process [[Review assignment process\|here]].		You can require that assignments must have been reviewed and approved before they can be applied to a resource group by checking the box "Require Approved Assignments". If an assignment does not meet these criteria, the assignment will not be applied to the resource group. Read more about the assignment review process [[Review assignment process\|here]].

	==== ~~Fetch~~ PINs ====		==== Manage PINs ====
	For portals with VCF enabled ~~there~~ will ~~be a button~~ '''Fetch PINs''' ~~that will connect~~ with PIE to fetch any available PINs for the resources in the group. These PINs ~~can~~ then ~~be applied to the VCF configurations of the group. Read more about VCF [[Vehicle Communication Forwarder\|here]] and about applying the fetched PINs [[I/O configurations#Apply uploaded PINs\|here]]~~.		For portals with [[Vehicle Communication Forwarder\|VCF]] enabled this button opens a submenu with three selections:

			* '''Check Existing PINs'''. Checks which ECUs and areas have PINs for each vehicle (grouped by WCU) in the resource group.
			* '''Check Missing PINs'''. Opens a window to select which ECUs and areas to perform the check on. The result for each vehicle/WCU in the group will only show which combinations of ECU and area are missing PINs.
			* '''Fetch PINs'''. Connect with PIE to fetch any available PINs for the resources in the group. These PINs are then automatically used when needed.

	====Manipulating Resources in a Resource Group====		====Manipulating Resources in a Resource Group====

New features in v2.98

Robin.karhu — Thu, 21 May 2026 09:15:49 GMT

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. ==

Signal Reader Trigger Expressions

Mathias — Thu, 21 May 2026 07:14:58 GMT

← Older revision		Revision as of 07:14, 21 May 2026
Line 91:		Line 91:
	\|-		\|-
	!DM1		!DM1
	\|Returns the FMI value of a specified ECU's J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN)		\|Returns the FMI value of a specified ECU's J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN), where ECU-id should be i hexadecimal, e.g. 0x10.
	\|}		\|}

New features in v2.98

Mathias — Thu, 21 May 2026 07:08:46 GMT

← 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 ==

Signal Reader Trigger Expressions

Mathias — Thu, 21 May 2026 07:06:54 GMT

← Older revision		Revision as of 07:06, 21 May 2026
(2 intermediate revisions by the same user not shown)
Line 89:		Line 89:
	!TIME_SINCE_UPDATE		!TIME_SINCE_UPDATE
	\|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE('Signal')		\|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE('Signal')
			\|-
			!DM1
			\|Returns the FMI value of a specified ECU's J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN)
	\|}		\|}

New features in v2.98

Henrik.Moller — Thu, 21 May 2026 06:57:51 GMT

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 ==

Roles and permissions

Henrik.Moller — Thu, 21 May 2026 06:55:11 GMT

← Older revision		Revision as of 06:55, 21 May 2026
(One intermediate revision by the same user not shown)
Line 55:		Line 55:
	==== Resource Group Create permission ====		==== Resource Group Create permission ====
	This permission enables a user to create resource groups by pressing Add New in the Resource groups panel of the Administration tab. It will also enable access to the Resource groups panel. Any permissions that may be needed to initially manage or edit the created resource group will be added to a role specific to the creator upon creating the group.		This permission enables a user to create resource groups by pressing Add New in the Resource groups panel of the Administration tab. It will also enable access to the Resource groups panel. Any permissions that may be needed to initially manage or edit the created resource group will be added to a role specific to the creator upon creating the group.

			==== WCU View permission ====
			This permission controls whether a user can view or modify a WCU through read or write access.

			* Users with '''read''' permission can view all or selected WCUs in the ''Vehicles'' tab.
			* Users with '''write''' permission can edit WCU settings and values.
			* Users without this permission can still open the ''Edit WCU'' view and see the settings, but they cannot modify any values.

			==== Vehicle Edit permission ====
			This permission allows the user to edit a vehicle.

			Similar to the ''WCU View Write'' permission, users without this permission can still open the ''Edit Vehicle'' view from the ''Vehicles'' tab and view the vehicle details, but they cannot modify any values.

	=== Selecting resources using uploaded file ===		=== Selecting resources using uploaded file ===

New features in v2.98

Mathias — Thu, 21 May 2026 06:49:31 GMT

framelog mf4 event block

← Older revision		Revision as of 06:49, 21 May 2026
(One intermediate revision by the same user not shown)
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.

			== 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.

New features in v2.98

Henrik.Moller — Thu, 21 May 2026 06:43:03 GMT

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 ==

New features in v2.98

Mathias — Thu, 21 May 2026 06:40:23 GMT

LIN MDF4

← Older revision		Revision as of 06:40, 21 May 2026
Line 12:		Line 12:
	== Add or revoke permissions to existing tasks ==		== 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]].		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 features in v2.98

Alkitjohan — Wed, 20 May 2026 14:17:37 GMT

← Older revision		Revision as of 14:17, 20 May 2026
Line 9:		Line 9:
	== 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. 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]].

Roles and permissions

Alkitjohan — Wed, 20 May 2026 14:06:13 GMT

Permission for specific tasks

← Older revision		Revision as of 14:06, 20 May 2026
Line 140:		Line 140:

	==== '''Remove permission to historical tasks when permission controlled label is removed from WCU''' ====		==== '''Remove permission to historical tasks when permission controlled label is removed from WCU''' ====
	~~TODO~~		[[File:Remove label used in WCU Task permission from WCU.png\|thumb\|Remove label used in WCU Task permission from WCU]]
			Similar to when removing a WCU from a resource group used in a WCU Task permission described in [[#Remove permission to historical tasks when WCU is removed from resource group]] it is possible to remove access to any existing tasks on the WCU the label is removed from. In screenshot "Remove label used in WCU Task permission from WCU" the label TP2 is removed from the WCU and all Task status types are selected. This means that all users with the role '''task_permission_label''' will have the access revoked on all historical tasks matching the task types defined in the permission for this WCU. So, if the permission defines access to SoH tasks for resources with the label TP2, then the access to all SoH tasks on WCU will be revoked.

	{{DEFAULTSORT:Rolas and Permissions}}		{{DEFAULTSORT:Rolas and Permissions}}

File:Remove label used in WCU Task permission from WCU.png

Alkitjohan — Wed, 20 May 2026 13:59:16 GMT

Alkitjohan uploaded File:Remove label used in WCU Task permission from WCU.png

New page

Remove label used in WCU Task permission from WCU

Roles and permissions

Alkitjohan — Wed, 20 May 2026 13:49:23 GMT

Add permission to historical tasks when WCU is associated with permission controlled label

← Older revision		Revision as of 13:49, 20 May 2026
Line 136:		Line 136:
	[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]		[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]
	[[File:Remove WCU from resource group used in WCU Task permission2.png\|thumb\|Remove WCU from resource group used in WCU Task permission]]		[[File:Remove WCU from resource group used in WCU Task permission2.png\|thumb\|Remove WCU from resource group used in WCU Task permission]]
	~~TODO~~		[[File:Add label used in WAP to WCU.png\|thumb\|Associate label used in WCU Task permission with a WCU]]
			As mentioned in [[#Creating and editing roles and permissions]], labels can be used in permissions to define the resources that are part of the permission. So when association WCU with a label that is used in a permission the WCU is added to the permissions resources. When associating a label used in a WCU Task permission (WTP) with a WCU it is from version 2.98 possible to give users of the related roles access to any existing tasks on the WCU similar to when adding a WCU to resource group described in [[#Add permission to historical tasks when WCU is added to resource group]]. An example of this can be seen in screenshot "Associate label used in WCU Task permission with a WCU".

	==== '''Remove permission to historical tasks when permission controlled label is removed from WCU''' ====		==== '''Remove permission to historical tasks when permission controlled label is removed from WCU''' ====

File:Add label used in WAP to WCU.png

Alkitjohan — Wed, 20 May 2026 13:47:51 GMT

Alkitjohan uploaded File:Add label used in WAP to WCU.png

New page

Add label used in WAP to WCU

Roles and permissions

Alkitjohan — Wed, 20 May 2026 13:25:53 GMT

Bottom selection "Add who can see task"

← Older revision		Revision as of 13:25, 20 May 2026
Line 110:		Line 110:

	You can also give a user permission to all running tasks on WCUs whose task types that user has access to. See [[The Portal Administrator View#The New User Dialog\|The new user dialog]] (the portal administrator view).<gallery>		You can also give a user permission to all running tasks on WCUs whose task types that user has access to. See [[The Portal Administrator View#The New User Dialog\|The new user dialog]] (the portal administrator view).<gallery>
	~~File:Add permission to existing tasks on permission update.png~~
	~~File:Remove permission for existing tasks.png\|TODO~~
	~~File:Add WCU to group used in WCU Task permission.png~~
	~~File:Remove WCU from resource group used in WCU Task permission.png~~
	</gallery>		</gallery>

Line 135:		Line 131:

	==== '''Remove permission to historical tasks when WCU is removed from resource group''' ====		==== '''Remove permission to historical tasks when WCU is removed from resource group''' ====
	~~TODO~~		Similar to when adding a WCU to a resource group used in a WCU Task permission (WTP) mentioned above, access to tasks on WCUs can be revoked when the WCUs are removed from the resource group. In the screenshot "Remove WCU from resource group used in WCU Task permission" a WCU is removed from the group 'johan1_grupp' and all Tasks status types are selected which means that all access to any tasks on the WCU will be revoked for the users having the mentioned roles.

	==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====		==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====
	[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]		[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]
	[[File:Remove WCU from resource group used in WCU Task ~~permission~~.png\|thumb\|Remove WCU from resource group used in WCU Task permission]]		[[File:Remove WCU from resource group used in WCU Task permission2.png\|thumb\|Remove WCU from resource group used in WCU Task permission]]
	TODO		TODO

File:Remove WCU from resource group used in WCU Task permission2.png

Alkitjohan — Wed, 20 May 2026 13:23:03 GMT

Alkitjohan uploaded File:Remove WCU from resource group used in WCU Task permission2.png

New page

Remove WCU from resource group used in WCU Task permission

Roles and permissions

Alkitjohan — Wed, 20 May 2026 13:14:32 GMT

Permission for specific tasks

← Older revision		Revision as of 13:14, 20 May 2026
Line 109:		Line 109:
	The bottom selection from above 'Add who can see task' will not list who already has access to the task, but rather just list all users available regardless whether they already have permission or not to the task.		The bottom selection from above 'Add who can see task' will not list who already has access to the task, but rather just list all users available regardless whether they already have permission or not to the task.

	You can also give a user permission to all running tasks on WCUs whose task types that user has access to. See [[The Portal Administrator View#The New User Dialog\|The new user dialog]] (the portal administrator view).		You can also give a user permission to all running tasks on WCUs whose task types that user has access to. See [[The Portal Administrator View#The New User Dialog\|The new user dialog]] (the portal administrator view).<gallery>
			File:Add permission to existing tasks on permission update.png
			File:Remove permission for existing tasks.png\|TODO
			File:Add WCU to group used in WCU Task permission.png
			File:Remove WCU from resource group used in WCU Task permission.png
			</gallery>

	==== Add permission to historical tasks on permission update ====		==== Add permission to historical tasks on permission update ====
Line 134:		Line 139:
	==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====		==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====
	[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]		[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]
			[[File:Remove WCU from resource group used in WCU Task permission.png\|thumb\|Remove WCU from resource group used in WCU Task permission]]
	TODO		TODO

File:Remove WCU from resource group used in WCU Task permission.png

Alkitjohan — Wed, 20 May 2026 13:12:18 GMT

Alkitjohan uploaded File:Remove WCU from resource group used in WCU Task permission.png

New page

Remove WCU from resource group used in WCU Task permission

Roles and permissions

Alkitjohan — Wed, 20 May 2026 13:10:21 GMT

Add permission to historical tasks when WCU is added to resource group

← Older revision		Revision as of 13:10, 20 May 2026
Line 125:		Line 125:

	==== '''Add permission to historical tasks when WCU is added to resource group''' ====		==== '''Add permission to historical tasks when WCU is added to resource group''' ====
	~~TODO~~		If a resource group is used in a WCU Task permission (WTP) (like the group 'johan1_grupp' in the screenshots mentioned before) any resource part of the group is also included in the permission. When adding a new WCU to a group that is part of a WTP users will from version 2.98 have the option to give access to any existing tasks on the WCU when the WCU is added to the group. The logic is the same as when a WCU is added to a permission described in [[#Add permission to historical tasks on permission update]]. An example of this can be seen screenshot "Add WCU to group used in WCU Task permission" where all users having the mentioned role will be given access to any 'Pending' or 'Running' tasks matching the individual WCU Task permission defined in the role.

			So in this case, if the role 'assignment_task' defines a WTP with read access to SoH tasks and the WCU johan4 has a task of type SoH with the status Pending or Running, all users with the role 'assignment_task' will be given access to these SoH tasks.

	==== '''Remove permission to historical tasks when WCU is removed from resource group''' ====		==== '''Remove permission to historical tasks when WCU is removed from resource group''' ====
Line 131:		Line 133:

	==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====		==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====
			[[File:Add WCU to group used in WCU Task permission.png\|thumb\|Add WCU to group used in WCU Task permission]]
	TODO		TODO

File:Add WCU to group used in WCU Task permission.png

Alkitjohan — Wed, 20 May 2026 12:56:55 GMT

Alkitjohan uploaded File:Add WCU to group used in WCU Task permission.png

New page

Add WCU to group used in WCU Task permission

New features in v2.98

Henrik.Moller — Wed, 20 May 2026 12:18:39 GMT

Permission to control edit of WCUs.

← Older revision		Revision as of 12:18, 20 May 2026
(2 intermediate revisions by the same user not shown)
Line 6:		Line 6:

	== Add reported WMU to WCU's WMU configuration ==		== Add reported WMU to WCU's WMU configuration ==

			== 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.

New features in v2.98

Robin.karhu — Wed, 20 May 2026 10:56:41 GMT

headings

← Older revision	Revision as of 10:56, 20 May 2026
Line 1:	Line 1:
		== 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 ==

Roles and permissions

Alkitjohan — Wed, 20 May 2026 09:20:16 GMT

Permission for specific tasks

← Older revision		Revision as of 09:20, 20 May 2026
(2 intermediate revisions by the same user not shown)
Line 114:		Line 114:
	[[File:Add permission to existing tasks on permission update.png\|thumb\|Add permission to existing tasks on permission update]]		[[File:Add permission to existing tasks on permission update.png\|thumb\|Add permission to existing tasks on permission update]]
	From version 2.98 of the WICE portal it is possible to give users access to existing tasks when updating the WCU Task permission. See screenshot "Add permission to existing tasks on permission update". In "Apply updated permission" it is possible to select the desired task statuses (for example only running tasks, stopped tasks etc) to apply the permission update to. For some environments all, or a subset of, statuses are preselected as default values. When saving this permission with "Selected resources" checked, any existing task having the the desired statuses on the WCUs in the list of 'Selected resources' will be accessible for the users with the current permission. This is the same as searching for the WCUs of interest in the Tasks tab and manually adding permissions to these tasks via "Show who can see task" discussed in [[#Top selection "Show who can see task"]].		From version 2.98 of the WICE portal it is possible to give users access to existing tasks when updating the WCU Task permission. See screenshot "Add permission to existing tasks on permission update". In "Apply updated permission" it is possible to select the desired task statuses (for example only running tasks, stopped tasks etc) to apply the permission update to. For some environments all, or a subset of, statuses are preselected as default values. When saving this permission with "Selected resources" checked, any existing task having the the desired statuses on the WCUs in the list of 'Selected resources' will be accessible for the users with the current permission. This is the same as searching for the WCUs of interest in the Tasks tab and manually adding permissions to these tasks via "Show who can see task" discussed in [[#Top selection "Show who can see task"]].

			Note that applying updated permission to tasks always applies to all resources in 'Selected resources' so it is not possible to a subset of the resources.

	==== '''Remove permission to historical tasks on permission update''' ====		==== '''Remove permission to historical tasks on permission update''' ====
	As discussed in [[Roles and permissions#Permission for specific tasks\|Permission for specific tasks]] a user has access to a historical task on a WCU even if that WCU is removed from the WCU Task permission. To remove the permission for historical tasks one have to lists the tasks in the Tasks tab, use "Show who can see task" and remove the users manually.		As discussed in [[Roles and permissions#Permission for specific tasks\|Permission for specific tasks]] a user has access to a historical task on a WCU even if that WCU is removed from the WCU Task permission. To remove the permission for historical tasks one have to lists the tasks in the Tasks tab, use "Show who can see task" and remove the users manually.
			[[File:Remove permission for existing tasks.png\|thumb\|Remove permission for existing tasks when updating a WCU Task permission]]
			Similar to "Add permission to historical tasks on permission update" discussed above, this can from version 2.98 be done when updating a WCU Task permission. In the screenshot "Remove permission for existing tasks when updating a WCU Task permission" the WCU "johan4"is removed from the permission. In "Apply updated permission" 'Remove resources" is selected along with all existing Task statuses. This will remove access to any existing tasks on 'johan4' for the users having the role the current permission is part of.

			Like for "Add permission to historical tasks on permission update" the list of desired Tasks statuses might be preselected as default values.

			==== '''Add permission to historical tasks when WCU is added to resource group''' ====
			TODO

			==== '''Remove permission to historical tasks when WCU is removed from resource group''' ====
			TODO

			==== '''Add permission to historical tasks when WCU is associated with permission controlled label''' ====
			TODO

	~~Similar to "Add~~ permission to historical tasks on permission ~~update" discussed above, this can~~ from ~~version 2.98 be done when updating a~~ WCU ~~Task permission.~~		==== '''Remove permission to historical tasks when permission controlled label is removed from WCU''' ====
			TODO

	{{DEFAULTSORT:Rolas and Permissions}}		{{DEFAULTSORT:Rolas and Permissions}}

File:Remove permission for existing tasks.png

Alkitjohan — Wed, 20 May 2026 09:09:30 GMT

Alkitjohan uploaded File:Remove permission for existing tasks.png

New page

Remove permission for existing tasks when updating a WCU Task permission

Roles and permissions

Alkitjohan — Wed, 20 May 2026 09:08:45 GMT

Remove permission to historical tasks on permission update

← Older revision		Revision as of 09:08, 20 May 2026
(One intermediate revision by the same user not shown)
Line 110:		Line 110:

	You can also give a user permission to all running tasks on WCUs whose task types that user has access to. See [[The Portal Administrator View#The New User Dialog\|The new user dialog]] (the portal administrator view).		You can also give a user permission to all running tasks on WCUs whose task types that user has access to. See [[The Portal Administrator View#The New User Dialog\|The new user dialog]] (the portal administrator view).

			==== Add permission to historical tasks on permission update ====
			[[File:Add permission to existing tasks on permission update.png\|thumb\|Add permission to existing tasks on permission update]]
			From version 2.98 of the WICE portal it is possible to give users access to existing tasks when updating the WCU Task permission. See screenshot "Add permission to existing tasks on permission update". In "Apply updated permission" it is possible to select the desired task statuses (for example only running tasks, stopped tasks etc) to apply the permission update to. For some environments all, or a subset of, statuses are preselected as default values. When saving this permission with "Selected resources" checked, any existing task having the the desired statuses on the WCUs in the list of 'Selected resources' will be accessible for the users with the current permission. This is the same as searching for the WCUs of interest in the Tasks tab and manually adding permissions to these tasks via "Show who can see task" discussed in [[#Top selection "Show who can see task"]].

			==== '''Remove permission to historical tasks on permission update''' ====
			As discussed in [[Roles and permissions#Permission for specific tasks\|Permission for specific tasks]] a user has access to a historical task on a WCU even if that WCU is removed from the WCU Task permission. To remove the permission for historical tasks one have to lists the tasks in the Tasks tab, use "Show who can see task" and remove the users manually.

			Similar to "Add permission to historical tasks on permission update" discussed above, this can from version 2.98 be done when updating a WCU Task permission.

	{{DEFAULTSORT:Rolas and Permissions}}		{{DEFAULTSORT:Rolas and Permissions}}

File:Add permission to existing tasks on permission update.png

Alkitjohan — Wed, 20 May 2026 08:48:25 GMT

Alkitjohan uploaded File:Add permission to existing tasks on permission update.png

New page

Add permission to existing tasks on permission update

Roles and permissions

Alkitjohan — Wed, 20 May 2026 08:41:17 GMT

Creating and editing roles and permissions

← Older revision		Revision as of 08:41, 20 May 2026
(One intermediate revision by the same user not shown)
Line 18:		Line 18:

	# Select what kind of permission you want. There are a number of different permissions, ten for WCUs and one to give permission to all tasks (the task permission can not be modified). The permissions are:		# Select what kind of permission you want. There are a number of different permissions, ten for WCUs and one to give permission to all tasks (the task permission can not be modified). The permissions are:
	## '''Task'''. ~~Controls if a user~~ is ~~permitted~~ to ~~create/see tasks of a specific type on a WCU. More what this means is discussed below~~ in ~~"[https://wiki~~.~~alkit~~.~~se/wice270/index.php?title=Roles_and_permissions#Permission_for_specific_tasks Permission to specific tasks]"~~		## '''Task'''. A special permission which is used to give users access to every existing task in the system. Typically only used for admins.
	## '''Assignment Creator'''. This permission handles access to creating/editing/viewing assignments in the tab Assignment (see [[Signal Reader Assignment Wizard\|signal reader]] and [[Area5 Assignment Wizard\|Area5]]). Having a read-permission means that you can see a list of assignments but you cannot go ahead and edit or create them. A write-permission on the other hand makes you eligible to edit and create assignments. Currently, the permission is only relevant for signal reader and Area5.		## '''Assignment Creator'''. This permission handles access to creating/editing/viewing assignments in the tab Assignment (see [[Signal Reader Assignment Wizard\|signal reader]] and [[Area5 Assignment Wizard\|Area5]]). Having a read-permission means that you can see a list of assignments but you cannot go ahead and edit or create them. A write-permission on the other hand makes you eligible to edit and create assignments. Currently, the permission is only relevant for signal reader and Area5.
	## '''Configuration.''' This permission controls whether you are allowed to work with a WCU's configuration.		## '''Vehicle Profile''' See [[#Vehicle Profile permission]]
	## '''Module'''. The permission controls the access to individual module configurations on a WCU. An example of a module is Signal reader.		## '''WCU Task''' Controls if a user is permitted to create/see tasks of a specific type on a WCU. More what this means is discussed below in "Permission to specific tasks"
	## '''Monitor'''. A task can have a monitor function to report data in real time. In order to see the real time data the user must have this permission.		## '''WCU Configuration.''' This permission controls whether you are allowed to work with a WCU's configuration.
	## '''Plot route'''. To see a historic GPS track of a WCU a user must have this permission.		## '''WCU Module'''. The permission controls the access to individual module configurations on a WCU. An example of a module is Signal reader.
	## '''Position'''. Allows a user to see a WCU's current position.		## '''WCU Monitor'''. A task can have a monitor function to report data in real time. In order to see the real time data the user must have this permission.
	## '''Shelving'''. Allows a user to handle any shelving, unshelving and refurbishing of a WCU.		## '''WCU Plot route'''. To see a historic GPS track of a WCU a user must have this permission.
	## '''View'''. This permission applies to the Vehicles tab. It has to do with whether you are allowed to list a WCU in the table. Selecting this subtype makes the subtype type part unnecessary and therefore, it is removed if you choose this resource type.		## '''WCU Position'''. Allows a user to see a WCU's current position.
	##'''Connect'''. Allows a user to connect a WCU to a vehicle.		## '''WCU Shelving'''. Allows a user to handle any shelving, unshelving and refurbishing of a WCU.
			## '''WCU View'''. This permission applies to the Vehicles tab. It has to do with whether you are allowed to list a WCU in the table. Selecting this subtype makes the subtype type part unnecessary and therefore, it is removed if you choose this resource type.
			##'''WCU Connect'''. Allows a user to connect a WCU to a vehicle.
			##'''Vehicle Create''' See [[Roles and permissions#Vehicle Create permission\|#Vehicle Create permissions]]
			##'''Resource Group Manage''' See [[#Resource Group Manage permission]]
			##'''Resource Group Create''' See [[#Resource Group Create permission]]
			##'''View Inactive WCU''' Allows a user to view inactive WCUs.
			##'''View Inactive Vehicle''' Allows a user to view inactive vehicles.
			##'''Vehicle Edit''' Allows a user to edit vehicles.
	# Choosing if the permission should be a read and/or write permission. One of these have to be selected or you will not be able to save changes.		# Choosing if the permission should be a read and/or write permission. One of these have to be selected or you will not be able to save changes.
	# Selecting which resources that apply to the permission. The selection is made using the two tables you see in Figure "Editing Task Permissions". To select a resource, which can be a resource group, you enter the name of the resource in the left table filter area. As you type, the table is automatically filled with resources matching the criteria. If a resource is part of a resource group the icon to the left is shown. If you hold the mouse over the resource name you will see which resource group it is part of. If you instead see the icon shown to the left, the resource is a resource group. Holding the mouse over the entry will show you which resources are part of the resource group. To select a resource, drag it over to the right table or select the resource and then press the right-arrow. To deselect a resource, drag it to the left table or press the left-arrow. There is a “Select all” option. It selects all current and future resources to which this permission should be applied. [[File:Labels in permissions1.png\|thumb\|Select resources by labels]][[File:Permission label2.png\|thumb\|Resource selected by label]]From version 2.93 of the WICE portal it is also possible to let labels select the resources that will be part of the permission. When a label is selected as in the screenshot to the right, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels. After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.		# Selecting which resources that apply to the permission. The selection is made using the two tables you see in Figure "Editing Task Permissions". To select a resource, which can be a resource group, you enter the name of the resource in the left table filter area. As you type, the table is automatically filled with resources matching the criteria. If a resource is part of a resource group the icon to the left is shown. If you hold the mouse over the resource name you will see which resource group it is part of. If you instead see the icon shown to the left, the resource is a resource group. Holding the mouse over the entry will show you which resources are part of the resource group. To select a resource, drag it over to the right table or select the resource and then press the right-arrow. To deselect a resource, drag it to the left table or press the left-arrow. There is a “Select all” option. It selects all current and future resources to which this permission should be applied. [[File:Labels in permissions1.png\|thumb\|Select resources by labels]][[File:Permission label2.png\|thumb\|Resource selected by label]]From version 2.93 of the WICE portal it is also possible to let labels select the resources that will be part of the permission. When a label is selected as in the screenshot to the right, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels. After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.

Main Page

Alkitjohan — Wed, 06 May 2026 11:05:57 GMT

← Older revision		Revision as of 11:05, 6 May 2026
Line 5:		Line 5:
	Feel free to suggest improvements and add pages if you feel that some information is missing.		Feel free to suggest improvements and add pages if you feel that some information is missing.

	To see the addtions/changes of the previous version of the WICE portal, see [[New features in v2.97\|New features in v2.97.]] (Also available from the sidebar to the left.)		To see the addtions/changes of the previous version of the WICE portal, see [[New features in v2.98\|New features in v2.98.]] (Also available from the sidebar to the left.)

	For full release history see [https://wice-sysdoc.alkit.se/index.php/Release_notes WICE Release history].		For full release history see [https://wice-sysdoc.alkit.se/index.php/Release_notes WICE Release history].

New features in v2.98

Alkitjohan — Wed, 06 May 2026 09:32:07 GMT

Created blank page

New page

MediaWiki:Sidebar

Alkitjohan — Wed, 06 May 2026 09:31:51 GMT

← Older revision		Revision as of 09:31, 6 May 2026
Line 13:		Line 13:
	**M2M REST API\| 6. M2M REST API		**M2M REST API\| 6. M2M REST API
	<!--** New_features_in_v2.40\|New in v2.40-->		<!--** New_features_in_v2.40\|New in v2.40-->
	** New features in v2.97\|New in v2.97		** New features in v2.98\|New in v2.98
	* SEARCH		* SEARCH
	* TOOLBOX		* TOOLBOX
	* LANGUAGES		* LANGUAGES

Vehicle Communication Forwarder

Jonas — Mon, 27 Apr 2026 14:01:39 GMT

← Older revision		Revision as of 14:01, 27 April 2026
Line 7:		Line 7:
	To read more about adding a VCF, see the [[I/O configurations#Add CAN channels\|Add CAN channels]] section in I/O configurations.		To read more about adding a VCF, see the [[I/O configurations#Add CAN channels\|Add CAN channels]] section in I/O configurations.

	A PIN for SGA area ~~0x17~~ has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu\|individual]] or for [[Vehicles#Upload Vehicle pins\|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab\|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.		A PIN for SGA area 0x5 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu\|individual]] or for [[Vehicles#Upload Vehicle pins\|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab\|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.
	[[File:VCF MRCOM forwarding.png\|thumb\|768x768px\|VCF MRCOM forwarding with CAN and LIN channel configurations]]		[[File:VCF MRCOM forwarding.png\|thumb\|768x768px\|VCF MRCOM forwarding with CAN and LIN channel configurations]]
	[[File:VCF raw MRCOM.png\|thumb\|769x769px\|VCF raw MRCOM with CAN and LIN channel configurations]]		[[File:VCF raw MRCOM.png\|thumb\|769x769px\|VCF raw MRCOM with CAN and LIN channel configurations]]

← Older revision		Revision as of 14:01, 27 April 2026
Line 7:		Line 7:
	To read more about adding a VCF, see the [[I/O configurations#Add CAN channels\|Add CAN channels]] section in I/O configurations.		To read more about adding a VCF, see the [[I/O configurations#Add CAN channels\|Add CAN channels]] section in I/O configurations.

	A PIN for SGA area ~~0x17~~ has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu\|individual]] or for [[Vehicles#Upload Vehicle pins\|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab\|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.		A PIN for SGA area 0x5 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu\|individual]] or for [[Vehicles#Upload Vehicle pins\|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab\|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.
	[[File:VCF MRCOM forwarding.png\|thumb\|768x768px\|VCF MRCOM forwarding with CAN and LIN channel configurations]]		[[File:VCF MRCOM forwarding.png\|thumb\|768x768px\|VCF MRCOM forwarding with CAN and LIN channel configurations]]
	[[File:VCF raw MRCOM.png\|thumb\|769x769px\|VCF raw MRCOM with CAN and LIN channel configurations]]		[[File:VCF raw MRCOM.png\|thumb\|769x769px\|VCF raw MRCOM with CAN and LIN channel configurations]]