WICE Wiki v2.98 - User contributions [en]

New features in v2.98

2026-05-20T14:17:37Z

Alkitjohan:

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

2026-05-20T14:06:13Z

Alkitjohan: /* Permission for specific tasks */

<includeonly>====Roles and permissions====</includeonly>
In order to restrict access to resources and functions in the portal, there is a framework using roles and permissions. Permissions are given on a set of resources. These permissions are grouped into roles, and roles are then attached to one or several users to be granted specific permissions.

The “Edit roles and permission” dialog can be seen in Figure "Edit Roles and Permissions Dialog". It consists of three tables. The top left table holds a list of the roles, the top right holds the user(s) for the selected role and the bottom one hold the selected role's permissions. Their size is adjustable and you can minimize them by clicking on the line between them.
[[File:Roles and permissions panel-20210217-144811.png|left|thumb|400x400px|Edit Roles and Permissions Dialog]]
 
You add a new role by pressing the button “Add role” and delete a role along with its permissions by pressing the red button next to it. When making a role you add a description and unique name. To edit an already existing role, double click the entry you wish to edit.

When you select a role in the top left table, the lower table shows that specific role's permissions and the upper right table shows which users have that role. The permissions table consists of two columns, a string that is the actual permission and the set of resources that apply to that permission.

=== Creating and editing roles and permissions ===

[[File:Add permission.png|thumb|Creating New Permission]]

To create a new permission press the “Add permission” button. It opens the following interaction depicted in Figure "Creating New Permission".

[[File:Editing permissions.png|thumb|400x400px|Editing Task Permissions]]

# 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'''. 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.
## '''Vehicle Profile''' See [[#Vehicle Profile permission]]
## '''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"
## '''WCU Configuration.''' This permission controls whether you are allowed to work with a WCU's configuration.
## '''WCU Module'''. The permission controls the access to individual module configurations on a WCU. An example of a module is Signal reader.
## '''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.
## '''WCU Plot route'''. To see a historic GPS track of a WCU a user must have this permission.
## '''WCU Position'''. Allows a user to see a WCU's current position.
## '''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.
# 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.
# Set what type of tasks the permission applies to. It is automatically set to have all selected but you can unselect all and selecting other tasks. This option is only available on the '''WCU task''', '''assignment''' '''creator,''' '''monitor''' and '''module''' permissions. It corresponds to the set of available modules for a WCU.
When you are done press "Save changes" or "Reset changes" if you want to revert the changes. You can always edit the permission by selecting it in the table. The dialog described above will show and you can make your changes, except that you can not change what type of task it is.

==== Assignment Creator permission ====
This permission concerns the [[Signal Reader Assignment Editor|signal reader assignment editor]]. If you give the user a read permission they can look at already created assignments. If you give a user the write permission they will also be able to create and delete assignments.

==== Vehicle Profile permission ====
With this permission you can delegate to individual users the possibility to view vehicle profiles if given the read permission. This makes the tab visible in the GUI but all buttons concerning editing/adding/removing are disabled. If a user has the write permission as well, the user will be able to edit/add and remove vehicle profiles.

==== Vehicle Create permission ====
This permission enables a user to do [[The Portal Administrator View#Add Vehicle Dialog|Add Vehicle]]. This will also let a user view any disconnected vehicles in the vehicles tab.

==== Resource Group Manage permission ====
This permission enables a user to [[The Portal Administrator View#Resource Groups|manage resource groups]]. Managing resource groups entails adding and removing WCUs from groups, editing groups, and removing groups. It will also enable access to the Resource groups panel.

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

=== Selecting resources using uploaded file ===
As described above, you can select resources in the select resources widget. In addition to this, you can upload a file containing the vehicles or WCUs that you would like to apply to a permission or a set of permissions. By pressing the button called 'Import vehicle file' you will be presented with a dialog where you can upload a file containing multiple vehicles or WCUs. You can either upload an excel file or a CSV type of text file. What is important is that there is a header column saying what type of identifiers can be found in the file. Identifiers currently supported are: vin, plate or wcu. An example content of file (CSV):

<kbd>
wcu 
04-1B-35-98 
90-80-AA 
</kbd>
[[File:Import vehcile file-20210217-151236.png|thumb|Import a vehicle file for permission resource selection]]
Just by changing the heading to plate or vin you should reference such identifiers in the file. The dialog also presents the option to ignore resources not found and apply the changes for those found. The default is however to do nothing if any of the resources are not found. The checkbox 'Ignore unconnected vehicles' is only applicable if you have plate or vin identifiers.

If you have selected a permission in the permission table, the resources in the file will be applied to only the selected permission. If you have selected a role in the top leftmost table, the resources in the file will be applied to all permissions of the role.

=== Changing a users roles and permissions ===
You can change a user's roles under in the edit user dialog if you press the button "Edit user roles". The edit user dialog then gets extended as two boxes appear, a left one with available roles and a right one with current roles. In the left one you can search the role(s) you want and drag them to the right box or press the button pointing right. With the two buttons at the bottom corner(the paper and clipboard ones) you can copy the names of the roles and also insert the names of roles to add them.

You can also change a users permission to view tasks in the tasks tab: By right-clicking the task(s) you want to change permissions for and hovering over "Permission" you will get the options "Show who can see task" and "Add who can see task". "Show who can see task" will open a window with a left and a right box where the left contains users without permission to view the task and the right contains users who have permission. By moving users from the left to right and vice versa you can give or remove someones permission. You can also press the clipboard the the right bottom to copy the users who have permissions or add users by writing their name within parentheses. Users in the right box can be unselectable and that is if they have a role giving them the permission to view that task the only way to remove that is to remove that role from them. "Add who can see task" works the same way as "Show who can see task" except that the right box does not show users with permission so you can not remove permissions, this is so that with add you can add permissions for many tasks at the same time as the show can not show users from many tasks.

[[File:Copy user assignment permissions.png|thumb|300x300px|Copy User Task Permissions Dialog]]

You can also edit a users role by searching for user(s) and right clicking on them to get a window with different options. There are five different options where the three first can be used on multiple users at the same time while the bottom two can not.
* "Add user task permissions to this user" will open the dialog shown in Figure "Copy User Task Permissions Dialog". With this button you take a user's task permissions and add them to the selected user(s). You do this by searching and selecting a user and then pressing "OK".
* "Replace user task permissions with user" will open a similar dialog to the one in Figure "Copy User task Permissions Dialog". This button is much like the one before except that instead of adding permissions to the current user this replaces the permissions that the selected user(s) have. Here you also search the user whose permissions you want to replace the select them and press "OK".
* "Copy user roles to this user" will open a similar dialog to Figure "Copy User Task Permissions Dialog". Instead of replacing permissions, this dialog replaces selected user(s) roles with the roles of a user who you chose. Search the user whose roles you want to copy for replacement and press "OK".

[[File:Give permission on car.png|thumb|Give Permission on Vehicle Dialog]]

* "Give this user permission to all tasks on vehicle" gives task permission on one or many vehicles. The dialog will look like the dialog in Figure "Give Permission on Vehicle Dialog". In the left box you select vehicles and move them to the right to give permission on them, you can also as you see below the left box select a file with vehicles to easily select a set of vehicles. Then you select which types of tasks it should give permission to (leaving this empty will not give any permissions). You can also check the checkbox "Reset user permission" to replace the roles of the selected user instead of adding new to the current ones.
* "Give this user permission to all tasks on WCU" is identical to the previous button except that it applies to WCUs instead of vehicles.

==== User specific roles ====
A role may also be set to be specific to just one user. Doing this will remove the role from any other users that currently have it as well as prevent adding the role to any other users but the specified user.

=== Permission for specific tasks ===
The above text discuss permissions as they are found from the User panel. There are also a set of "implicit" permissions created when a new task is created, based on the task type permission discussed above. Let us elaborate a bit on this to make it clear what it means. The use case is as follows; a user has a read task permission on a WCU ("wcu:assignment:soh:read:awcu"). (Observe that a task permission might contain the word "assignment" even if it is referring to a task. Look at the menu names instead to confirm that you are working with a task.) Let us say that a new state-of-health task is created on the WCU ("''awcu''") while the user has the above permission. Regardless of who created the task, the user will now be able to list this task in the Tasks panel and download any data produced. Later, as time goes by, the WCU is no longer used in the particular project and an administrator removes the permission "wcu:assignment:soh:read:awcu" from the user. When new tasks are created on this WCU our user above will not be able to see the new tasks created in the Tasks panel. However, the user will be able to see the previous task, i.e. when the user had the correct permission. Thus, this solution enables users to retain the permission to see historical tasks, let us call this a '''historical task permission'''. This type of permission cannot be seen in the permission panel. To see who has access to which '''historical task''' you must turn to the Task panel.

[[File:Task-panel-permission.png|thumb|Permission Choices in the Tasks Panel]]

As an administrator you have the possibility to both see and modify who has access to individual tasks. There are two options presented if you right-click an task in the Tasks panel. To the right you see the two choices available. The top choice is only available if you have selected a single row in the table. The bottom one is always available, also if electing multiple rows.

==== Top selection "Show who can see task" ====
By selecting the top selection you will be presented with a dialog where on the left hand side you have all available users that do not have the permission to see the task. On the right hand side you have the users that have the permission to do so. On the right hand side you might see that some users are grayed. Those users have the ''task permission,'' not to be confused with the WCU task permission'','' described above. Also, the users visible are enabled, disabled users will not be displayed.

[[File:Users-with-read-permission-tasks-panel.png|thumb|Users with Permission on a Specific Task]]

To give a user the permission to see the task, simply move the user from the left side to the right side. This is accomplished by selecting one or more users and then click the right-arrow. Conversely, to remove a user from the permission select the users from the right side and click the left-arrow. At the top of the left side you can search for users by typing and as you go the users will be filtered to match what you type.

In the picture "Users with Permission on a Specific Task" to the right you see the user 'serverTriggerUser' which is an enabled user which do not yet have the permission to see the task.

==== Bottom selection "Add who can see 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).<gallery>
</gallery>

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

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''' ====
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''' ====
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''' ====
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''' ====
[[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: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''' ====
[[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}}

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

2026-05-20T13:59:17Z

Alkitjohan:

Remove label used in WCU Task permission from WCU

2026-05-20T08:41:17Z

Alkitjohan: /* Creating and editing roles and permissions */

Roles and permissions

2026-05-20T08:31:49Z

Alkitjohan:

<includeonly>====Roles and permissions====</includeonly>
In order to restrict access to resources and functions in the portal, there is a framework using roles and permissions. Permissions are given on a set of resources. These permissions are grouped into roles, and roles are then attached to one or several users to be granted specific permissions.

The “Edit roles and permission” dialog can be seen in Figure "Edit Roles and Permissions Dialog". It consists of three tables. The top left table holds a list of the roles, the top right holds the user(s) for the selected role and the bottom one hold the selected role's permissions. Their size is adjustable and you can minimize them by clicking on the line between them.
[[File:Roles and permissions panel-20210217-144811.png|left|thumb|400x400px|Edit Roles and Permissions Dialog]]
 
You add a new role by pressing the button “Add role” and delete a role along with its permissions by pressing the red button next to it. When making a role you add a description and unique name. To edit an already existing role, double click the entry you wish to edit.

When you select a role in the top left table, the lower table shows that specific role's permissions and the upper right table shows which users have that role. The permissions table consists of two columns, a string that is the actual permission and the set of resources that apply to that permission.

=== Creating and editing roles and permissions ===

[[File:Add permission.png|thumb|Creating New Permission]]

To create a new permission press the “Add permission” button. It opens the following interaction depicted in Figure "Creating New Permission".

[[File:Editing permissions.png|thumb|400x400px|Editing Task Permissions]]

# 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]"
## '''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.
## '''Vehicle Profile'''
## '''WCU Task'''
## '''WCU Configuration.''' This permission controls whether you are allowed to work with a WCU's configuration.
## '''WCU Module'''. The permission controls the access to individual module configurations on a WCU. An example of a module is Signal reader.
## '''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.
## '''WCU Plot route'''. To see a historic GPS track of a WCU a user must have this permission.
## '''WCU Position'''. Allows a user to see a WCU's current position.
## '''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'''
##'''Resource Group Manage'''
##'''Resource Group Create'''
##'''View Inactive WCU'''
##'''View Inactive Vehicle'''
##'''Vehicle Edit'''
# 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.
# Set what type of tasks the permission applies to. It is automatically set to have all selected but you can unselect all and selecting other tasks. This option is only available on the '''WCU task''', '''assignment''' '''creator,''' '''monitor''' and '''module''' permissions. It corresponds to the set of available modules for a WCU.
When you are done press "Save changes" or "Reset changes" if you want to revert the changes. You can always edit the permission by selecting it in the table. The dialog described above will show and you can make your changes, except that you can not change what type of task it is.

==== Assignment Creator permission ====
This permission concerns the [[Signal Reader Assignment Editor|signal reader assignment editor]]. If you give the user a read permission they can look at already created assignments. If you give a user the write permission they will also be able to create and delete assignments.

==== Vehicle Profile permission ====
With this permission you can delegate to individual users the possibility to view vehicle profiles if given the read permission. This makes the tab visible in the GUI but all buttons concerning editing/adding/removing are disabled. If a user has the write permission as well, the user will be able to edit/add and remove vehicle profiles.

==== Vehicle Create permission ====
This permission enables a user to do [[The Portal Administrator View#Add Vehicle Dialog|Add Vehicle]]. This will also let a user view any disconnected vehicles in the vehicles tab.

==== Resource Group Manage permission ====
This permission enables a user to [[The Portal Administrator View#Resource Groups|manage resource groups]]. Managing resource groups entails adding and removing WCUs from groups, editing groups, and removing groups. It will also enable access to the Resource groups panel.

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

=== Selecting resources using uploaded file ===
As described above, you can select resources in the select resources widget. In addition to this, you can upload a file containing the vehicles or WCUs that you would like to apply to a permission or a set of permissions. By pressing the button called 'Import vehicle file' you will be presented with a dialog where you can upload a file containing multiple vehicles or WCUs. You can either upload an excel file or a CSV type of text file. What is important is that there is a header column saying what type of identifiers can be found in the file. Identifiers currently supported are: vin, plate or wcu. An example content of file (CSV):

<kbd>
wcu 
04-1B-35-98 
90-80-AA 
</kbd>
[[File:Import vehcile file-20210217-151236.png|thumb|Import a vehicle file for permission resource selection]]
Just by changing the heading to plate or vin you should reference such identifiers in the file. The dialog also presents the option to ignore resources not found and apply the changes for those found. The default is however to do nothing if any of the resources are not found. The checkbox 'Ignore unconnected vehicles' is only applicable if you have plate or vin identifiers.

If you have selected a permission in the permission table, the resources in the file will be applied to only the selected permission. If you have selected a role in the top leftmost table, the resources in the file will be applied to all permissions of the role.

=== Changing a users roles and permissions ===
You can change a user's roles under in the edit user dialog if you press the button "Edit user roles". The edit user dialog then gets extended as two boxes appear, a left one with available roles and a right one with current roles. In the left one you can search the role(s) you want and drag them to the right box or press the button pointing right. With the two buttons at the bottom corner(the paper and clipboard ones) you can copy the names of the roles and also insert the names of roles to add them.

You can also change a users permission to view tasks in the tasks tab: By right-clicking the task(s) you want to change permissions for and hovering over "Permission" you will get the options "Show who can see task" and "Add who can see task". "Show who can see task" will open a window with a left and a right box where the left contains users without permission to view the task and the right contains users who have permission. By moving users from the left to right and vice versa you can give or remove someones permission. You can also press the clipboard the the right bottom to copy the users who have permissions or add users by writing their name within parentheses. Users in the right box can be unselectable and that is if they have a role giving them the permission to view that task the only way to remove that is to remove that role from them. "Add who can see task" works the same way as "Show who can see task" except that the right box does not show users with permission so you can not remove permissions, this is so that with add you can add permissions for many tasks at the same time as the show can not show users from many tasks.

[[File:Copy user assignment permissions.png|thumb|300x300px|Copy User Task Permissions Dialog]]

You can also edit a users role by searching for user(s) and right clicking on them to get a window with different options. There are five different options where the three first can be used on multiple users at the same time while the bottom two can not.
* "Add user task permissions to this user" will open the dialog shown in Figure "Copy User Task Permissions Dialog". With this button you take a user's task permissions and add them to the selected user(s). You do this by searching and selecting a user and then pressing "OK".
* "Replace user task permissions with user" will open a similar dialog to the one in Figure "Copy User task Permissions Dialog". This button is much like the one before except that instead of adding permissions to the current user this replaces the permissions that the selected user(s) have. Here you also search the user whose permissions you want to replace the select them and press "OK".
* "Copy user roles to this user" will open a similar dialog to Figure "Copy User Task Permissions Dialog". Instead of replacing permissions, this dialog replaces selected user(s) roles with the roles of a user who you chose. Search the user whose roles you want to copy for replacement and press "OK".

[[File:Give permission on car.png|thumb|Give Permission on Vehicle Dialog]]

* "Give this user permission to all tasks on vehicle" gives task permission on one or many vehicles. The dialog will look like the dialog in Figure "Give Permission on Vehicle Dialog". In the left box you select vehicles and move them to the right to give permission on them, you can also as you see below the left box select a file with vehicles to easily select a set of vehicles. Then you select which types of tasks it should give permission to (leaving this empty will not give any permissions). You can also check the checkbox "Reset user permission" to replace the roles of the selected user instead of adding new to the current ones.
* "Give this user permission to all tasks on WCU" is identical to the previous button except that it applies to WCUs instead of vehicles.

==== User specific roles ====
A role may also be set to be specific to just one user. Doing this will remove the role from any other users that currently have it as well as prevent adding the role to any other users but the specified user.

=== Permission for specific tasks ===
The above text discuss permissions as they are found from the User panel. There are also a set of "implicit" permissions created when a new task is created, based on the task type permission discussed above. Let us elaborate a bit on this to make it clear what it means. The use case is as follows; a user has a read task permission on a WCU ("wcu:assignment:soh:read:awcu"). (Observe that a task permission might contain the word "assignment" even if it is referring to a task. Look at the menu names instead to confirm that you are working with a task.) Let us say that a new state-of-health task is created on the WCU ("''awcu''") while the user has the above permission. Regardless of who created the task, the user will now be able to list this task in the Tasks panel and download any data produced. Later, as time goes by, the WCU is no longer used in the particular project and an administrator removes the permission "wcu:assignment:soh:read:awcu" from the user. When new tasks are created on this WCU our user above will not be able to see the new tasks created in the Tasks panel. However, the user will be able to see the previous task, i.e. when the user had the correct permission. Thus, this solution enables users to retain the permission to see historical tasks, let us call this a '''historical task permission'''. This type of permission cannot be seen in the permission panel. To see who has access to which '''historical task''' you must turn to the Task panel.

[[File:Task-panel-permission.png|thumb|Permission Choices in the Tasks Panel]]

As an administrator you have the possibility to both see and modify who has access to individual tasks. There are two options presented if you right-click an task in the Tasks panel. To the right you see the two choices available. The top choice is only available if you have selected a single row in the table. The bottom one is always available, also if electing multiple rows.

==== Top selection "Show who can see task" ====
By selecting the top selection you will be presented with a dialog where on the left hand side you have all available users that do not have the permission to see the task. On the right hand side you have the users that have the permission to do so. On the right hand side you might see that some users are grayed. Those users have the ''task permission,'' not to be confused with the WCU task permission'','' described above. Also, the users visible are enabled, disabled users will not be displayed.

[[File:Users-with-read-permission-tasks-panel.png|thumb|Users with Permission on a Specific Task]]

To give a user the permission to see the task, simply move the user from the left side to the right side. This is accomplished by selecting one or more users and then click the right-arrow. Conversely, to remove a user from the permission select the users from the right side and click the left-arrow. At the top of the left side you can search for users by typing and as you go the users will be filtered to match what you type.

In the picture "Users with Permission on a Specific Task" to the right you see the user 'serverTriggerUser' which is an enabled user which do not yet have the permission to see the task.

==== Bottom selection "Add who can see 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).

{{DEFAULTSORT:Rolas and Permissions}}

Main Page

2026-05-06T11:05:57Z

Alkitjohan:

'''Welcome to the WICE Wiki!''' Here you can find information about the WICE System and how-to guides of all the features in the WICE Portal.

The WICE system is a powerful and flexible data collection and fleet management system developed by Alkit Communications AB. The WICE Portal is the user interface of the WICE system.

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

New features in v2.98

2026-05-06T09:32:07Z

Alkitjohan: Created blank page

Creating a Task

2025-11-03T14:15:26Z

Alkitjohan: /* Diagnostic Log and Trace (DLT) */

<includeonly>== Creating a Task==</includeonly>
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of task you want to create. Note that it is not possible to create a new task for a WCU which has the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU has the latter label, it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of tasks available. Remember that not all of the task types will be available as this depends on customer configuration and some types might not be enabled in the portal.

To learn about how to add resources to the task, check [[New task|here]].

== Arcos ==
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]
The WICE system can interact with external loggers as well. From version 2.71 the portal can interact with the Arcos-logger from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.ccmc''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.

Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the Arcos - no upload will be required.

Since version 2.79.0 Arcos tasks can now have software version validation in the same manner as described for the M-Log task (see [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).

== Area5 ==
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]
Area5 tasks are used to read out data from the memory of ECUs.

'''Assignment:''' To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]].

'''Validate ECU SW version on WCU:''' By checking this box, the WCU will validate that the ECU SW version of the task and the actual ECU are the same before starting the task. If they are different, it will not start the task.

'''Trigger Expression:''' The task can be started by an expression. This option lets the user specify start trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). For an explanation of trigger conditions look [[Server Trigger|here]].

'''Sync Signal:''' It is possible to specify a signal with given values that will be sent when the Area5 task starts and stops. This can be used to synchronize the Area5 read-out with external measurements systems like the M-Log.

== Audio ==
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:
* '''Trigger button''': to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.
* '''Signal reader''': initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader '''recorder''' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the audio recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected.
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of triggers look [[Server Trigger|here]].
* '''Audio level''': Start the trigger once the microphone registers volume above a certain threshold.
* '''None''': start the recording as soon as possible.

In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero].

There is more information about audio in WICE [[Wice audio|here]].

Audio tasks can be scheduled in the same manner as described for the Canrecoder task.

== Blue piraT ==
The blue PiraT is a measurement system from Telemotive AG that can be configured with measurement set-ups, and data accessed through the WICE Portal. Note that to use the blue PiraT module, the WCUs to be used need to be preconfigured with a special software package (i.e. an "extra bundle"). Contact Alkit Communications in order to set this up.

== CAN-recorder ==
[[File:Canrecorder.png|thumb|Canrecorder]]
Canrecorder is a measurement module that allows CAN frames to be captured and logged.

1. In the grid, select which bus (or buses) to record from. By clicking below active column or select a row and click on “Toggle” button.

2. To apply filters on specific CAN buses, select a row and click on “Edit filter”. There it is possible to select one specific frame or several by separating them by “,”. It is also possible to select a range between frames by using “-”. The value can either be decimal or hexadecimal. A example of a filter: “1, 0x12-0xFF”

3. Below the grid settings for how long the recording should be and how many shots. If not using shot count, infinite result files will be created as long as the units are on.

===Scheduling===

For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached. By selecting the "On ignition" checkbox, the task will be performed once on ignition. If delay is above 0 then the task will be performed once the configured amount of seconds have passed after ignition.

[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with 'On ignition' enabled]]
 

To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the [[The Portal Administrator View#The Vehicles Tab|Vehicles panel]]. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.

== Diagnostic Log and Trace (DLT) ==
The DLT functionality comes in two flavors. One is based on communicating with a DLT daemon on the ECU and the other is based on the UDS service 38. You switch between the using the button "DLT UDS mode".
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]
From version 2.96 it also possible to create a task with DLT daemon and DLT UDS mode enabled at the same time by checking the "Enable multi task" checkbox as can be seen in the screenshot the right.

=== DLT Daemon Mode ===
DLT itself provides a log and trace interface, based on the standardized protocol specified in the AUTOSAR standard 4.0 DLT. A DLT task in the WICE Portal makes it possible to collect such logs in a vehicle where this functionality is available and transfer the data to the WICE portal where logs can be downloaded for further analysis. For a more in-depth description, you can go [https://github.com/GENIVI/dlt-daemon here].

Basically the WCU is connecting to one or more DLT Daemons and unique filters can be applied to each daemon, filtering out specific log messages.

So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:

# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check "Use vehicle announcement" (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.
# Daemon port - which port on the address the daemon is at.
# Filter configurations - filter expressions to be applied on the log messages. If left empty no filter is applied. For an explanation on how to write filter expressions, see [https://github.com/GENIVI/dlt-daemon#learn-more here].

=== DLT UDS Mode ===
When in this mode the user is presented with a list of directories to handle. Each row in the table is for a specific WCU and directory, as indicated in the illustration for the UDS mode to the right. To add a row, or directory to fetch, press the button "Add transfer". An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number, an optional pin code (more on this later) and the directory to fetch. You can add as many entries as you wish.
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]
There is a check box with the text "Use vehicle specific PINs". By checking the box, the system will try to get a vehicle specific PIN code for each ECU and WCU. The type of PIN for this service is area 19. How to supply the system with such PIN codes is described [[Vehicles#Upload Vehicle pins|here]].

There is also a button "Check PINs" available to resource groups that will—if the above check box is checked—look for any missing PINs in the portal for the configured ECUs.

== ETAS ==
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.

When creating an ETAS task, the task description file you select must be a .exp file.

== Ethernet capture ==
This kind of task is used to capture packet data from one of the ethernet interfaces on the WCU. The basics for this kind of task is that you choose the interface you would like to capture from and a capture expression to filter which packets you are interested in. The results from this task type is pcap files. To read more about this task type, go [[Ethernet capture|here]].

== File fetcher ==
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.

The following needs to be specified when creating such a task:

* '''File path''' - One or several paths to a files or file-containing directories on the unit's file system. This specifies which files that will be fetched.
* '''Username''' - To log in to the unit.
* '''Password''' - To log in to the unit.
* '''IP address''' - To find the unit.
* '''Port''' - To find the unit. Default is 22, but can be changed.

Furthermore, the task also allows the use of a proxy.

To use a proxy, the '''Use Proxy''' checkbox has to be checked, and the following must be specified:

* '''Proxy Username''' - To log in to the proxy unit.
* '''Proxy Password''' - To log in to the proxy unit.
* '''Proxy IP Address''' - To find the proxy unit.
* '''Proxy Port''' - To find the proxy unit. Default is 22, but can be changed. 
== IDC ==
The Internal Diagnostic Client (IDC) is a measurement module that allows a sequence of diagnostic requests to be sent and responses recorded. The sequence of diagnostic requests can be created as an assignment in the Assignment tab, alternatively can be uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.

== IPEmotion RT ==
The WICE system can interact with external loggers as well. From version 2.72 the portal can interact with the logger IPEmotion RT from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.irf''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.

Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.

Since version 2.79.0 IPEmotion RT tasks can now have software version validation in the same manner as described for the M-Log task (see [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).

== LPD ==
This type of task is ultimately handled by a separate App in an iPhone or iPad. The WICE system simply makes this task available to the App through a REST interface running on the WCU. The task consists of a specially crafted excel file. When the file is uploaded to the WICE portal it is validated to make sure that it can be read by the App.
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]
From version 2.83.0 of the WICE portal the task measurement file can be updated via the View Task function in the Tasks tab and a dialog as shown to the right will appear. By pressing the "Edit" button in the lower right corner, you will be presented with the possibility to upload a new measurement task file. This is shown with a red triangle in the illustration on the right.

== M-Log ==
The WICE system can interact with external loggers as well. One such logger is called M-Log from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.[[File:MlogForWiki.png|thumb|M-Log task]]
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the MLOG - no upload will be required.

==== Software version validation (Available from version 2.74.0) ====
The measurement assignment for an MLOG is created using an external tool to WICE. An assignment is created with a certain version of the ECU software in mind for each ECU in the assignment. In order for the assignment to work it might be important that the ECU software version in the vehicle matches the software version of the ECU it was created for. In WICE, you can ask the system to read the current software version for each ECU which is stored and can be viewed, e.g. via the [[ECU List|ECU list]]. As WICE cannot know which software versions the assignment was created for, the user can supply this to WICE. By doing that, WICE can validate the entered software versions against what has been read out for each vehicle and thus aid the user in making sure that an assignment will work once it will run.

To make the validation possible the user enters a ECU by its address, not the name. To help find out the address for an ECU you can go to the [[ECU List|ECU list]] to find the address of a specific ECU. Have a look at the illustration, Entering ECU software version, to see where in the dialog this is entered. On the top you enter the ECU address on the left and what software version is expected on the right. When satisfied, press the "Add" button. The data you just entered will be added to the table and evaluated against what the WICE system has read out from the vehicle. In the example to the right something is incorrect which is indicated by the yellow color. To see the exact reason, simply use the cursor to see the specific message.

A negative validation in not enforced in the sense that you cannot run the assignment but rather an indication that it might not work as expected. You can always go ahead and press "Submit".

== MQTT ==
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.

== Rapid prototyping ==
A Rapid prototyping (RP) task makes it possible to download RP binaries to multiple WCUs and keep track of the result files the RP task might produce. For more information about RP, see [[WICE RP How-To]] and [[WICE RP Manual]].
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]
The rapid prototyping tab can be seen in Figure "Rapid prototyping task".

An RP task must consist of at least an 'RP binary' or a 'Web application zip file'.

== SoftHub ==
The SoftHub is a measurement system that can be run either as a stand alone unit or as a software module on the WCU, with functionality similar to the Signal Reader module. A SoftHub task is created much in the same way as a Signal Reader task.

When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task.

The SoftHub task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''server triggers''' to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].

== Signal Reader ==
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]
Signal Reader is a data capture module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data, and ECU-internal signals read by CCP or XCP. To create a Signal Reader task you proceed as follows:

1. You either select an assignment file of .haf format, or choose an assignment created in the assignment creator (see [[Signal Reader Assignment Wizard]]). Your current choice will be displayed in the "Chosen file" field.

2. When you have selected an assignment and one or more WCUs, the CAN buses defined in the assignment and on the WCU will be mapped. If they can be automatically mapped a green check symbol will be displayed, otherwise a red cross will be displayed. Clicking the mapping button will open the mapper. In the pop-up window you will have to map the different buses to each other manually and then save. Once this is done correctly, the red cross will become a green check mark, indicating that the mappings are ready to be automatically applied upon submit. Read more about this in [[I/O configurations]] and [[Mappings]].

3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting "Monitor signals". When selected, two boxes will appear under the task description. In the left one you search for signals and drag them over to the right one where the signals to be monitored are listed. You can later see the monitored signals by pressing the '''Monitor Signals''' button either in the Tasks tab or in the Vehicles tab. It is also possible to copy the signals text in the bottom right corner of the right box. Next to the copy text button you can also paste signals as text where the pasted signal names will be matched against the list of unselected signals

4. You can choose if you want the signals to have their data source names as a prefix (e.g. CAN1.EngineSpeed instead of EngineSpeed).

5. The Signal Reader task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''Server Triggers''' to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].

A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.

=== The Signal Broker ===
Signal Reader can act as a Signal Broker for other software components. For instance, the audio and video modules relies on the Signal Broker API of Signal Reader for evaluating start and stop trigger expressions. Moreover, the Signal Broker gives programmatical access to signals for Rapid Prototyping tasks. Read more about this in [[WICE Signal Broker API]].

=== Files containing references to sequence files ===
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]]
If the measurement file contains references to sequence files, you are also required to select these in order to run the task. The portal scans the .haf file for such entries and presents this to you, see illustration 4.2. Click the button for each sequence file reference to upload each sequence file needed. Some requests in the sequence file may be for reading DTCs, and in such cases you can select the option of also reading associated ''Snapshots'' or ''Extended data''. An example of this can found in Figure "Sequence Files References in .haf File".
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]]

Here, the .haf file contained two references to sequence files. As no sequence files have yet been uploaded, the selection for reading snapshot or extended data is grayed out. In Figure "Sequence File with Functional Query" we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read ''Extended data''. It is also possible to select both ''Snapshots'' and ''Extended data''.
 

=== WICE internal signals ===
In addition to CAN and FlexRay signals, a number of internal signals (i.e. internal to the WCU) are also available. The following WICE-internal signals are supported: [[WICE Internal Signals|WICE Internal Signals]]

== SoH ==
[[File:Screenshot from 2021-04-01 09-43-34.png|thumb|799x799px|SoH]]
A State of Health (SoH) task collects specific status information from vehicles. You select which information you want the task to collect by filling in one or more of the checkboxes shown in Figure "SoH". The number of checkboxes shown can vary depending on the WICE installation. In order for SoH data to be correctly interpreted, relevant description files (e.g. SDDB) for the vehicles executing the SoH task may have to been available. To add such a description file for a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:
*Mileage
*Voltage
*Read ECU software numbers
*Read ECU DTC:s (optionally including 'Snapshot' and 'Extended data')
*Read OBD-II PIDs
*App Diagnotstic Db Part Num
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)
*Clear DTCs.
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)
**If this option (Clear DTC) is chosen it is optionally possible to set a PIN code for unlocking a gateway module - e.g. Vehicle Gateway Module (VGM). (Available from WCU version 2.66)
*Engine hours, reading engine hours using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.64). The result for this can be read in the generated j1939-file from the task. It is a text type of file. In addition, a system value label called 'engine_hours' (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle.

This task can also be scheduled in the same manner as described for the Canrecoder task.

Some selections above might not be available to you as this is a configuration setting depending on customer.

== SWDL ==
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table.

SWDL tasks can optionally include a '''pre-update sequence file and/or a post-update sequence file'''. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.

SWDL tasks can optionally include one '''signature file''' (containing checksums). The file is assumed to be an xml file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)

SWDL tasks can optionally include a '''VGM unlock''' access control mechanism, with a PIN code for the VGM node. This is specifically for vehicles requiring this kind of access control for ECU re-programming.

By checking the box '''Run SoH after completion''' it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.

If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "'''Use Vehicle Pin mappings'''". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].

SWDL tasks can optionally contain a '''Trigger Expression''' which must be fulfilled within a specified time limit ("Wait time") for ECU re-programming to be allowed. The trigger expression follows the same syntax as Signal Reader trigger expressions (or [[Server Trigger|Server Triggers]], audio/video triggers), and should be built up from signals being measured in a Signal Reader assignment. The user must make sure that there is a Signal Reader assignment on the WCUs of the SWDL task, with the signals of the trigger expression being measured.

It is also possible to choose to '''ignore checksums''' and/or '''disable pre-programming''' using the corresponding checkboxes.

The SWDL module can be [[The Portal Administrator View#Configure the Software Download Module|configured]] to perform SWDL either over CAN or over Ethernet (DoIP).

== Video ==
A video task makes it possible to record and monitor live video from one or two cameras attached to a WCU. You can trigger recording of video in four ways:
* '''Trigger button''': To initiate the recording you need to attach a button to the WCU in order to start in the video recording.
* '''Signal reader''': Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader ''recorder'' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the video recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected.
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of how to enter triggers, have a look [[Server Trigger|here]].
* '''None''': start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)

In addition to this, you can set the '''pre-trig''' time (not valid in the cases of the 'None' trigger option above). As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the video has already been recorded for the number of seconds specified.

A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.

If monitoring of video from a WCU is enabled, a live video stream will be transmitted which can be viewed using a RTP-based video tool, for instance [http://confero.alkit.se Alkit Confero]. This task can also be scheduled in the same manner as described for the Canrecoder task.

Read more about the video support in WICE [[WICE_video|here]].

== Applicable for all types ==
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]].

=== Site specific features ===

==== Announce result file availability ====
[[File:Resultfilepanel.png|thumb|Announced On column]]
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there's a new 'Announced On' column that keeps track of when the result file was announced.

==== Retention time ====
[[File:Retention time.png|thumb|435x435px|Retention time]]
This function works by setting a retention time in days which simply says that data coming in from the task, i.e. result files and positions will be kept the set number of days from when the data was collected. If, e.g. setting the retention time for an task to 30 days, will keep data until it is 30 days old where it will be automatically removed. See image.

It is possible to set a default retention time for resource groups. To do this, add a global value label named '''RETENTION_TIME''' to the resource group and give it an appropriate value. This value will then be used as a template value when creating a new task for this resource group. If multiple resource groups have this label and they have different values, the one with the lowest/shortest retention time value will be chosen as the template value.

File:DLT multi task and vehicle announcement.png

2025-11-03T14:12:02Z

Alkitjohan:

Screenshot showing DLT multi task and vehicle announcement available from version 2.96.0

New features in v2.96

2025-10-23T12:20:46Z

Alkitjohan:

Main Page

2025-08-25T08:56:39Z

Alkitjohan:

'''Welcome to the WICE Wiki!''' Here you can find information about the WICE System and how-to guides of all the features in the WICE Portal.

The WICE system is a powerful and flexible data collection and fleet management system developed by Alkit Communications AB. The WICE Portal is the user interface of the WICE system.

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.95|New features in v2.95.]] (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]].

New features in v2.95

2025-08-25T08:56:17Z

Alkitjohan: Created blank page

2025-08-11T14:05:37Z

Alkitjohan:

Main Page

2025-08-11T14:05:28Z

Alkitjohan:

'''Welcome to the WICE Portal Wiki!''' Here you can find information and how-to guides of all the features in the portal.

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.94|New features in v2.94.]] (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]].

Downloading Files

2025-06-13T07:42:09Z

Alkitjohan:

From version 2.94 of the portal, the background preparation described below is no longer needed. The download will start instantly when clicking the Download or "Get all files" buttons.

When using functions such as "Get file(s)" to download files, the files will first be prepared and compiled into a zip file before the actual download. This is because the preparation can take a considerable time and is therefore best done in the background. When pressing download or get to download file(s) you will get a message telling you that your files are being prepared and you will be notified when it is ready, as shown in the Figure "Message: File Preparation".

[[File:Illustration20.png|Message: File Preparation|link=https://wiki.alkit.se/index.php/File:Illustration20.png|none|thumb|800x800px]]

When the preparation is done and your files are ready for download, the message presented in Figure "Message: File Preparation Done" will be shown in conjunction with the download icon in the tool strip.

[[File:Illustration21.png|Message: File Preparation Done|link=https://wiki.alkit.se/index.php/File:Illustration21.png|none|thumb|350x350px]]

To see which file(s) are ready for download you press the blue folder icon with a download sign located at the top of the screen. With the dialog that opened you can see and manage your downloads. Here there are two bars where you can see the preparation progress and download progress going from gray to green. To easily tell the different downloads apart, you can see their assigned description (is given) to easily remember which contains what. To download a file or a set of files you press the downwards pointing arrow icon where you will get an option to set a filename before pressing download. You can also remove or cancel downloads by pressing the red icon with a cross.

New features in v2.94

2025-06-13T07:40:21Z

Alkitjohan:

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable tester address for signal reader, IDC, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Tab ==
A new column has been introduced to the Vehicles tab that will show the current state of the WCU.

== Support for SOVD IP Address in the WCU configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'SOVD IP Address' field located under the Connection tab in the WCU configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit from. More importantly, only the configuration settings changed will be applied to the WCUs, all other configuration settings will be untouched.

== Support for new platform Kvaser Edge ==
There is support for a new platform called Kvaser Edge.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in the Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==
You can now view the frame name for both CAN and LIN signals directly within the "Add Signal" dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.

== Improved assignment editor permission ==
We've upgraded the assignment permission settings to give more control.

Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].

== Improved handling of copy assignment ==
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.

The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

== Support to search for empty values in label columns ==
You can now search for the absence of values in your label columns in various places.

== Cyber security settings ==
For the WCU a bunch of cyber security settings are available.

* Disable USB ethernet interfaces
* Lock signal reader pub/sub communication to localhost
* Disable the SSH daemon
* Root password checks to prevent too weak passwords

== Instant downloads of multiple files ==
From version 2.94 the previous background zipping of files described in [[Downloading Files]] is no longer needed. Instead the downloading starts immediately when clicking the "Get all files" button in [[Tasks Tab]] or the the "Download" button in the [[Search Tab]].

MediaWiki:Sidebar

2025-05-27T12:48:44Z

Alkitjohan:

Main Page

2025-05-27T12:48:33Z

Alkitjohan:

New features in v2.94

2025-05-27T12:48:03Z

Alkitjohan: Created blank page

New features in v2.93

2025-03-06T09:42:56Z

Alkitjohan: /* Platform types in WMUs */

== Support for using labels to control permissions ==
It is now possible to select resources by labels as an alternative to select resources manually when selecting resources for a permission in [[Roles and permissions]].
[[File:Labels in permissions1.png|thumb]]
[[File:Permission label2.png|thumb|Select resources by labels]]
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.

== Support for impersonating another user ==
[[File:Impersonate user.png|thumb|Impersonate user]]
An admin user can impersonate another user by selecting a user in the [[The Portal Administrator View#The_User_Tab]] and click the new button "Impersonate" as can be seen in the screenshot "Impersonate user".
[[File:Impersonating user.png|thumb|Impersonating user]]
When the button has been clicked, the portal will be reloaded and once logged in again you are now impersonating the selected user. See screenshot "Impersonating user".

To stop impersonating, one can either click the new "Stop impersonating user" icon next to the red text "Impersonating user" or click the logout icon in the upper right corner of the portal.

== Platform types in WMUs ==
[[File:Selected platform for new WMU.png|thumb|Select platform for new WMU]]
When adding a new WMU via the portal GUI it is now mandatory to select the platform for the new WMU as can be seen in the screenshot "Select platform for new WMU".

If the WMU is running WMU version 3.0.0 or above it will also report its platform back to the portal. In the case the reported platform does not match the selected platform a warning will be shown and the selected platform must be changed to the reported before the WCU configuration can be saved.
[[File:Reported WMU platform does not match selected2.png|thumb|Reported WMU platform does not match selected]]
See screenshot "Reported WMU platform does not match selected.

== Support for moving a vehicle to a resource group when applying a vehicle template ==
It is now possible to move a vehicle into a resource group with the help of vehicle templates. For more detailed information on how to use this feature, you can read more [https://wiki.alkit.se/wice293/index.php/Vehicle_templates here].

== Support to update all vehicles to use a specific SDDB/CSV file ==
[[File:ApplyFileToAllVehicles.png|thumb|Apply File To all Vehicles]]
A new button, "Apply File to All Vehicles," has been added in ECU Diagnostics, allowing users to apply an SDDB/CSV file to all vehicles simultaneously.