WICE Wiki v2.95 - User contributions [en]

Vehicle Profiles

2022-10-06T04:30:48Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
[[File:Vehicle-description-files.png|thumb|The Vehicle Description files portlet]]

The "Vehicle Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* '''DBC''' - describing CAN interfaces
* '''FIBEX''' - describing Flexray interfaces
* '''A2L''' - describing ECU interfaces
* '''ECU''' '''Diagnostics''' (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

New features in v2.79

2022-10-06T04:29:23Z

Loe.Lindstrom:

== ECU Diagnostics tab moved: Non-admin users have access ==
The tab for uploading diagnostic files "ECU Diagnostic files" was previously found under the "Administration" tab. Now it has been moved to the tab "Vehicle Profiles" (which is under the "Administration tab). In the "Vehicle profile tab" it is located in the Descriptor files portlet among the other file upload tabs there (see [[Vehicle Profiles#Manage Description files|Manage Description Files]]).

This also changes so that anyone with the permission to read vehicle profiles can see these files and anyone with the permission to write to vehicle profiles can upload new files. See more about handling permissions under [[Roles and permissions]].

New features in v2.79

2022-10-05T09:27:15Z

Loe.Lindstrom: /* ECU Diagnostics tab moved: Non-admin users have access */

== ECU Diagnostics tab moved: Non-admin users have access ==
The tab for uploading diagnostic files "ECU Diagnostic files" was previously found under the "Administration" tab. Now it has been moved to the tab "Vehicle Profiles" (which is under "Administration tab). In the "Vehicle profile tab" it is located in the Descriptor files portlet among the other file upload tabs there (see [[Vehicle Profiles#Manage Description files|Manage Description Files]]).

This change also that anyone with the permission to read vehicle profiles can see these files and anyone with the permission to write to vehicle profiles can upload new files.

(Edit in progress)

The Portal Administrator View

2022-10-05T08:12:56Z

Loe.Lindstrom: /* The ECU Diagnostics Tab */

An administrator can do everything a user can do and more. In addition to what a normal user can do, an administrator can create and modify users and stop tasks for any task.
These new functions will be explained in the next three chapters.

We will start with the ''Search'' tab where two more buttons are visible. Next is the ''Vehicles'' tab.
Lastly is the ''Administration'' tab with five sub tabs consisting of: the ''Connect'' tab, the ''Archives'' tab the
''GDS/SDDB files'' tab, the ''Resource Groups'' tab and the ''Users'' tab.

==The Tasks Tab==
[[File:Illustration 32a.png|thumb|Stopping Running Task]]
[[File:Illustration 32b.png|thumb|Force Stop Task]]

In addition to the functionality for an ordinary user, an administrator the administrator can search and view any user's task. Also, it has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running Task" shows the "Stop assigment" button. This button is the same as for the ordinary user and is used to stop a running task. When a running task is stopped, it changes state to "Stop pending". This means that the portal is waiting for a stop message from the WCU before the state is changed to "Stopped" in the portal view. The administrator view's "Force Stop Task" button, which can be seen in Figure "Force Stop Task", forces a "Stop pending" task into "Stopped" state without waiting for the stop signal from the WCU.

For a portal of version 2.60 and forward, it is also possible for an administrator to remove all resultfiles for a selected task using the corresponding context menu option. When doing so, a confirmation dialog pops up to ensure that it is in fact the intended choice. Note that this option is disabled if multiple tasks are selected or if the selected task does not have any result files attached.

==The Vehicles Tab==
An administrator can do quite a lot of things in this view, an illustration of which is presented in Figure "The Administrator's Vehicles Tab". The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

At the bottom you have a set of buttons to aid in handling the WCUs. To add a new WCU to the portal, the “New” buttons opens up a dialog for that. The “Get Log Files” button fetches log files for the selected WCU from the portal.

[[File:42vehiclestab.png|thumb|left|800px|The Administrator's Vehicles Tab]]
<br clear="all">

===The New WCU Dialog===
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog presented in in Figure "The Add New WCU Dialog".

[[File:Illustration34.png|frame|left|The Add New WCU Dialog]]
<br clear="all">

You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===The Edit WCU Dialog===
[[File:Edit wcu.png|thumb|Edit WCU Dialog]]

To edit a WCU simply mark it in the table and press the button called "Edit WCU". This results in a dialog where the fields differ depending on editability. For one selected WCU these are the comment, name, whether it is active or not and the labels for the WCU. However, if the WCU has tasks which have status pending, running, warning or error (or corresponding partial statuses), the active option is disabled. This is also true if the WCU is connected to a vehicle or if it is included in a resource group. If the selected WCU is a resource group the dialog will appear as presented in Figure "Edit WCU Dialog". The difference here is the "Apply label to resource group's WCUs"checkbox. When this option is selected the labels selected in the "Manage labels"-selector are also added to the WCUs included in the resource group. It is, though, not possible to remove labels from the resource group's WCUs using this checkbox. To do so use instead the context menu options for label management.

It is also possible to edit multiple WCUs simultaneously. If several WCUs are selected the dialog presented in Figure "Edit Multiple WCUs" appear. This is only possible for the fields "Comment" and "Active" and these are enabled using the corresponding checkbox to the right. If one of the selected WCUs fulfill the conditions presented above for the disablement of the Active-option, it will not be possible to select the corresponding checkbox.

[[File:Edit wcu multiple.png|thumb|left|Edit Multiple WCUs]]

<br clear="all">

===Edit the WCU Configuration===
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in Figures "Edit Configuration: Modules", "Edit Configuration: Connection", "Edit Configuration: WCU", "Edit Configuration: Power Management", "Edit Configuration: Upload", "Edit Configuration: IO", and "Edit Configuration: Extra bundles". The WCU configuration window is divided into five tabs where each tab is described below.

<br>
<gallery widths="150" mode="nolines">
File:Wcu config1.png|Edit Configuration: Modules.
File:Wcu config2.png|Edit Configuration: Connection.
File:Wcu config3.png|Edit Configuration: WCU.
File:Wcu config4.png|Edit Configuration: Power Management.
File:Wcu config5.png|Edit Configuration: Upload.
File:Edit configuration IO.png|Edit Configuration: IO.
File:Wcu extra bundles.png|Edit Configuration: Extra bundles.
</gallery>

<br clear="all">

====Modules====
The set of checkboxes for the different modules that are present are at the top. Check or uncheck these to tell the WCU if they are present or not. Disabling modules will speed up the boot process of the WCU (but will make the corresponding functionality unavailable).

To edit "Car type", click on the field where the car type is displayed to open the "Edit car" dialog. This dialog is described in section [[The_Portal_Administrator_View#The_Edit_Car_Dialog]]

The last three checkboxes, "Run IDC at boot", "Run IDC at ignition off" and "Enable VIN reader" are pretty much self-explanatory.

====Connection====
This tab can be seen in Figure "Edit Configuration: Connection" and the tab content is described [[WCU as WiFi Access Point|here.]]

====WCU====
This tab can be seen in Figure "Edit Configuration: WCU".

:'''Unit ID'''
The automatically generated unique WCU identifier. The ID is immutable.

:'''Platform type'''
The WCU platform type.

:'''Platform subtype'''
The WCU platform subtype.

:'''WCU software version'''
This is the currently installed WCU software version.

:'''Preferred WCU software'''
This is the new preferred WCU software version to be installed. When updating to a new version, the configuration dialog will update itself immediately to reflect what is available in the new version, hence accordingly also when downgrading. This means that new settings regarding the WCU's modules will also be upgraded which makes it possible to edit the modules according to the new version. In addition, when creating new tasks, validation will be carried out to the new version and hence you will not have to wait for the WCU to be updated to the new version to use new features.

:'''Perform reset on update'''
Removes all data on the WCU when installing a new WCU software.

:'''MX4 firmware version'''
The currently installed MX4 firmware version.

:'''Preferred MX4 firmware'''
The new preferred MX4 firmware.

From version 2.40 of the WCU software, all WCUs report its platform type. The platform type determines, among other things, the number of available CAN buses in the IO tab. (see [[I/O configurations]]) Since a resource group is a collection of WCUs it has no platform type of its own to report. From version 2.41 of the portal the user has the option to set a fictive platform type for a resource group. This is also a prerequisite to also set the [[I/O configurations]] for a resource group. The platform type (and possibly subtype) is set in the WCU tab. If the resource group has members with other platform type(s) than the type that is about to be set, the user will get a warning.

If the platform type of the resource group differs from the platform type of its members the I/O tab will be disabled. This is also the case when the platform type of the resource group and one member is the same but another member has another platform type.

From version 2.42 it is possible to update the WCU root password. To update the password, write the new password in "Set root password" and save the configuration.

:'''WCU Local Scheduling Time Zone'''

For a WCU of version 2.53 or higher it is possible to configure a local time zone for the WCU using the option "Local scheduling time zone" presented in Figure "Edit Configuration: WCU". This field consist of a drop down menu displaying the selectable time zones, which are as follows:
* Universal
* Africa/Cairo
* America/Anchorage
* America/Caracas
* America/Chicago
* America/Denver
* America/Los_Angeles
* America/New_York
* America/Sao_Paulo
* Asia/Dhaka
* Asia/Dubai
* Asia/Hong_Kong
* Asia/Karachi
* Asia/Tokyo
* Australia/Adelaide
* Australia/Brisbane
* Australia/Darwin
* Australia/Sydney
* Europe/London
* Europe/Moscow
* Europe/Paris

The zone defined here will be enforced selecting "WCU local time" when scheduling a task, see description [[Creating a Task#CAN-recorder#Scheduling|here]].

:'''Blink Controller'''
For WCUs of version later than or equal to 2.54 it is possible to configure the blink controller for the WCU diods, which can be set to blink in different patterns to represent different WCU states. Selecting "Legacy" in the corresponding drop down menu will result in the WCU controlling the diods and the "DioIPD"-option means that the DioIPD will controll them.

:'''Enable NTP Server'''
It is possible to enable or disable the NTP server by the use of a checkbox named thereafter for WCUs of version 2.60 or later.

:'''WCU Certificate'''
[[File:Wcu certficate three files.png|thumb|Files for Certificate Update]]

If the WCU is version 2.52 or later you have an opportunity to update the WCU's certificate and related files. If the conditions mentioned are met you will see a checkbox saying "Update certificate related files", see Figure "Files for Certificate Update". When checking the checkbox, an additional three fields are revealed. They are:
* Certificate file, choose a certificate file to upload which is in PEM format.
* Private key file, choose a private key to upload in PEM format as well.
* Password file, choose a file with the password to the private key. The file should be plain text.

You must supply all three files.

In order to see what certificate is installed on the WCU at any time, there is text field called "Current fingerprint". If you have recently updated a WCUs certificate, you can by hovering over the field also see if the WCU is using the latest certificate. If this the case a message saying "Using latest certificate".

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Perodic Wake-up]]
This tab can be seen in Figure "Edit Configuration: Power Management" and the tab content is described below.

“Power mode” has two settings: "Sleep" and "Cut-off". In cut-off mode, the WCU is not woken up at regular intervals to report battery voltage, GPS position etc.

In the other mode, sleep, some more settings are visible which also can be seen in Figure "Edit Configuration: Power Management".
You can select the WCU to remain unpowered by selecting "External cut-off". In addition, you may enable the WCU's wake-up functionality. This function is simply made up of a cycle time called “Periodic wake-up time” and the corresponding “Periodic run-time”. The “Periodic run-time” determines how long time the WCU should be awake before going back to sleep. The “Periodic wake-up time” indicates the time for each new wake-up cycle.

From version 2.43 it is also possible to set power mode to "deep sleep" for WCUs running on platform MX4 T20/T30 and MX4 V61. The configuration is the same as for mode "sleep".

'''Example: '''
A periodic run-time of 600 seconds means that the WCU will be alive for 600 seconds (10 minutes). A periodic wake-up time of 3600 seconds means that the WCU will start a new run-time (600 seconds in this case) every new hour. (3600 seconds = 60 min). The sleep time in each cycle is, for the general case, the wake-up time minus the run-time and in this example 3600 minus 600 = 3000 seconds (50 min).
This example is illustrated in Figure "Perodic Wake-up".



====Upload====
<span id="upload tab wcu configuration"></span>
This tab can be seen in Figure "Edit Configuration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the vehicle will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up.
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the ignition of the vehicle is turned off.
|-
|'''Upload periodically'''
|Uploads data every 10 minutes.
|}

====IO====
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

====Extra bundles====
[[Extra bundles|For more information about Extra bundles, click here]].

From portal version 2.47 and if the WCU is running 2.47 (or is about to be upgraded to 2.47) there is a new tab "Extra bundles" in the WCU configuration window, see Figure "Edit Configuration: Extra bundles". In the tab, it is possible to select additional software to be installed on the WCU. The installation will start as soon as the WCU fetches the updated configuraton. This tab is only enabled if the current WCU is an MX4.

===The Edit Car Dialog===
[[File:Illustration37.png|thumb|200px|right|Edit One Car]]
[[File:Illustration38.png|thumb|200px|right|Edit Several Cars]]

To edit the information about a car, press the “Edit Car” button. The dialog in Figure "Edit One Car" opens up.The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.

In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. If the selected car is connected to a WCU in a resource group, strict or not, this option is disabled. To enable it it either has to be disconnected from the WCU or the WCU must be excluded from its resource group. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars. However, if the car is connected to a WCU this option will be disabled from editing. In order to deactivate such a car you need to first disconnect it from the WCU. It is possible to choose not to update history cars with the provided changes. This option should only used in specific cases and with a well grounded reason.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes, except for the VIN and plate number, for all the selected cars at once. This is achieved using the extended dialog presented in Figure "Edit Several Cars". The options which are to be edited for all cars must be selected using the corresponding checkbox. If not, the option is disabled, as for instance the "Comment"-option in the "Edit Several Car"-figure.

=== Add Vehicle Dialog ===
[[File:Add-car-dialog.png|alt=add car dialog|thumb|Add Car dialog]]
[[File:Save car response dialog.png|thumb|Response dialog when creating a new vehicle]]
Usually you do not have to create vehicles manually, they are created automatically by the WCU if they are not found. It is possible, however, to create a vehicle manually using the portal by pressing the button "Add Car" in the vehicles panel. By doing so you will be presented with the dialog found on the right. Here you can set a number of attributes. Important to remember is that the field VIN is mandatory and must be unique among all vehicles registered on the portal. From version 2.57 of the portal the checkbox "Generate unique VIN" is present to the right of the input field VIN. By checking that box a unique VIN will be generated once you save the vehicle. The name consists of a prefix, which is centrally preconfigured, and a monotonically increasing integer number. After pressing save you will be presented with the following dialog (in the right below).

Here you have the opportunity to inspect the generated VIN and your other settings. You can either select to dismiss the dialog or go to the result which mens that the newly created vehicle will be presented in the table in the vehicles panel.<br clear="all">

===Upload a Car Import File===
It is possible to import a file that describes a set of vehicles. It can consist of both new vehicles and vehicles already in the database but that might need to be updated with new information.
A car import file consists of a comma separated file where each line describes a vehicle. The first line of the file must look as follows:<br>
'''VIN,regNr,description,project,protoNumber,tsu,series'''

There are seven attributes currently. When uploading the file you have a choice of modifying existing cars on the portal. If you do not check this box and there are cars that already exists, the import will fail.

=== Show or export SIM card ID ===
The SIM card ID for a single WCU can be seen when right-clicking on a WCU in the Vehicles tab and selecting "Show info".

SIM card ID's for one or multiple WCUs can also be exported as a csv file. Select the WCUs you are interested in (in the Vehicles tab) and press the button "Export SIM card info" located in the bottom row below the Vehicles grid. The downloaded file will contain five columns: WCU ID, WCU Name, RegNr (Plate nr), VIN and SIM Card ID.

=== Upload WCU file ===
The WCU attributes 'WCU Name' and 'WCU Comment' can from version 2.43 of the portal be updated for multiple WCUs via a comma separated txt/xls/xlsx file. Click the "Upload WCU File" button to open up the import file to upload dialog.

The uploaded file has the following requirements:
* The file must have two mandatory columns with the names 'WCU ID' and 'WCU Name'.
* Furthermore, an optional column named 'Comments' can be added.
* The columns should be in said order.
* The amount of columns on each row must match the amount of columns in the header.
* The columns should be separated by using tab or by a comma.
If there is a 'Comment' column and a blank comment on a row then the old comment, if any, for the specific WCU will be kept.

To remove a comment from a WCU simply check the checkbox for erasing comments. Doing so will result in that empty comments in the uploaded file will erase current comments.

<br clear="all">
{{:Shelve and Unshelve a WCU}}
<br clear="all">

==Resource Groups==
As described above in [[Vehicles#Resource Groups]], you can define a set of resource groups in order to easily handle large groups of resources collectively. An example is if you have 100
WCUs in such a resource group and you would like to edit the configuration for all WCUs. Instead of having to open the configuration for each individual WCU, you simply open the configuration for the resource group, do your edits and when you press save, the configuration
will be saved to all WCUs in one go. Resource groups are created in the [[The Portal Administrator View#Resource group|Resource groups panel]], described further below.

[[File:AddWCUtoResourceGroup.png|thumb|Adding Resources to Resource Group|right]]
==== Add a resource to a resource group ====
To add resources to a resource group you start by selecting the resources you are interested in adding to a resource group.

When you are satisfied with your selection, press the button “Add WCU(s) to resource group”. Pressing this button will show the dialog to the left. The group box will list the available groups. If you know the name of the resource group you can type the name and as you type the box will show names that fit what you type.

The two check boxes requires a deeper discussion. Assume you have a resource group that has been used for some time. A new WCU is registered on the portal and you would like to add that WCU to your group. A common situation is that you would like that WCU to be configured the same way as the rest of the WCUs in the resource group. This is accomplished by checking “Update WCU configuration”. If this requires an update of the WCU software it will automatically be taken care of. Also, a WCU comes pre-configured with a set of modules. Usually you will probably want to update the module configurations as well. In order to do so, it is required that you also update the WCU-configuration.

[[File:ConfirmMovingResourceToResourceGroup.png|thumb|Dialog: WCU Moved to Another Resource Group|right]]
<br>
==== Moving a resource between resource groups ====
In this same dialog it is also possible to move WCUs between resource groups. Just as with adding a WCU to a resource group, select the WCU(s) you wish to move and press the "Add WCU(s) to resource group" button. If a WCU already belongs to a resource group, that resource group is listed in the grid alongside the WCU. Select the desired resource group you wish to move the WCU to, in the group box and press the "Save" button. An information dialog will pop up, informing you that a WCU will move from one resource group to another. Press "OK" to confirm the WCU moving to a new resource group or press "Cancel" to return to the previous dialog.

[[File:AddWCUToStrictResourceGroup.png|thumb|Adding/Moving WCU to Strict Resource Group.|right]]
<br>
==== Requirements for moving or adding a resource to a strict resource group ====
When adding or moving WCUs to a strict resource group, it is required that the WCU shares the same platform type (and platform subtype, should one exist) and that a car is connected to the WCU (see [[Strict resource group|strict resource groups]]). Furthermore, updating the WCU-configuration and the module configurations are mandatory and, as such, these options are set and not able to be changed.

<br>

==Modules for the WCU==
[[File:Screenshot from 2021-09-10 15-34-09.png|alt=Tool configurations.|thumb|687x687px|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Area5
# Audio
# Blue piraT
# Canrecorder
# DLT
# DoIP
# ETAS
# Ethernet capture
# GPS
# IDC
# M-log
# MCD-Hub (deprecated)
# MQTT
# Rapid Prototyping (RP)
# Signal Reader
# Smart Eye
# Soft-Hub
# State of Health (SoH)
# Software Download (SWDL)
# Uptime
# Video
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Figure "The Administrator's Vehicles Tab" in [[#The Vehicles Tab]].
In Figure "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

Each tool has its own entry in each of the stacks. In Figure "Handling Tool Configurations" there is only one MCD-Hub present and it is “0”. Each tool is recognized with a tool ID which is set by the WCU. This ID is usually not descriptive and therefore you have the possibility to set a name of your likings. Change the name by pressing the button “Edit name”. You can also add a description to the tool that shows up as a “tool tip” when hovering over the name of the selected tool. Analogously, change the description by pressing the button “Edit description”. To reload the set of available tools press the “Reload” button.

Below each tool configuration there messages are presented to indicate the module status. The different types of which are presented in Figure "Module Status Indicators".

<br>
<gallery widths="200" mode="nolines">
File:Modules no settings changed.png|Module Status Indicators
File:Modules settings not saved.png
File:Modules settings saved.png
File:Modules tool upgrade pending.png
</gallery>

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.
[[File:Screenshot from 2021-04-09 10-54-55.png|thumb|Module status with information on when it was changed and by whom]]
In addition to the module status indicator above, a date and user will show when the configuration was changed and by whom.

=== Configure the Arcos Module ===
[[File:Arcos-module.png|alt=Arcos-module|thumb|Arcos-module]]
As of version 2.71 of the portal, Arcos tasks can be created and these are the configurations variables that can be configured:
* Username
* Password
* Frontend number
* [[Debug level]]
When configuring the module on a resource group level the username and password will be set on all resources in the resource group. The frontend number however, will not be updated on all the resources but rather retain the individual settings made on each resource.

=== Configure the Area5 Module ===
As of version 2.61 of the portal, it is possible to create Area5 tasks. The Area5 tool only has one configuration, the [[debug level]], which determines the level of logging during the execution of the Area5 tasks.

=== Configure the Audio Module ===
The audio module can be configured both regarding '''recording''' and '''monitoring'''. The recording settings refer to what is recorded on the WCU to disc to be uploaded, whereas the monitoring settings refer to the parameters used for monitoring live audio.

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
* '''Recording volume''', can be set to a value between 0 and 100, where default is 95.
The available monitoring settings are:
* '''Channels''', 1 (mono) or 2 (stereo). Default is 1.
* '''Codec''', LPCM, GSM or G.711. Default is LPCM (Linear PCM 16 bits per sample, 16 kHz).
* '''Destination IP address'''. This is the address to where the audio is sent for live monitoring.
* '''Enable monitoring'''. In order to monitor audio live for an audio task, the module must be enabled for monitoring. If the task is enabled for monitoring but the module is not, no audio can be monitored live. Default is disabled.<br clear="all">

It is possible to have four audio sources simultaneously. To add a new source, simply press the button "Add audio source" and the corresponding settings will appear in a new tab. If there already is an audio source with device set to internal, the new device will have default device USB. However, if there is no previous device set to internal, this will be the default option.

=== Configure the Blue piraT Module ===
As of version 2.44 of the portal it is possible to create blue piraT tasks. The blue piraT tool only has one configuration, the [[debug level]], which determines the level of logging during the execution of the blue piraT tasks.

=== Configure the Canrecorder Module ===
The configurable settings for the Canrecorder module can be seen in Figure "Settings for the Canrecorder module".

[[File:Modules Canrecorder.png|thumb|left|250px|Settings for the Canrecorder module]]
<br clear="all">

In the aforementioned figure, it is clear that this panel can be used to edit the speed on both the high- and low-speed CAN-buses. It is also possible to set the date for which the update is valid, the canrecorder version and the debug level.

=== Configure the DLT Module ===
For WCUs with software version earlier than 2.72.0 the DLT module have two DLT-specific settings, one for the daemon address and one for the daemon port. Have a look [[DLT Module|here]].

For WCUs with software version 2.72.0 or later, the daemon addresses and ports (several daemons are supported from this version) are instead specified when creating a [[Creating a Task#Diagnostic Log and Trace (DLT)|Diagnostic Log and Trace (DLT) task]]. The only thing specified in the module is the debug level - the level of logging from the WCU regarding its handling of this task.

=== Configure the DoIP Module ===
In figure "Settings for the DoIP module" the configuration for the DoIP module is presented.

'''Proxy address:''' The proxy address for the DoIP module.

'''Proxy port:''' The proxy port.

'''ID:''' The ID of the DoIP module.

'''Active session:''' Checkbox to let the DoIP module start announcing an ongoing synchronous diagnostic session. This is typically done by setting a LED on the WCU connected to the vehicle, signaling that a synchronous diagnostic session is ongoing.

The Proxy address should usually be set to the localhost IP address 127.0.0.1 for technical reasons (it will be tunneled) and the proxy port number should usually be 6757. The ID is a textual string that identifies a particular user group that will gain access to the WCUs by configuring the client interface system with the same identifier. (This configuration is done at doipc install time.) All WCUs configured with the same ID will be reachable through the same client system interface. For more information see [[Remote Diagnostics over IP (DoIP)|Remote Diagnostics over IP (DoIP)]].

[[File:Modules DoIP.png|thumb|left|250px|Settings for the DoIP module]]
<br clear="all">

=== Configure the ETAS Module ===
In Figure "Settings for the ETAS module" the configuration panel for the ETAS module is presented.

[[File:Modules ETAS.png|thumb|left|250px|Settings for the ETAS module]]
<br clear="all">

This panel can be used to change the username and password as well as the debug level.

=== Configure the Ethernet capture module ===
[[File:Screenshot from 2021-04-01 09-34-02.png|thumb|Settings for the Ethernet capture module]]
The only available setting here is debug level.

=== Configure the File fetcher module ===
The only available setting here is [[debug level]].

===Configure the GPS Module===
[[File:Screenshot from 2021-04-01 09-36-42.png|thumb|Settings for the GPS module]]
There are four settings involved:
# Enable GPS. Sets whether the GPS should be enabled or not. If you disable the GPS all the other settings will also be disabled.
# GPS sampling interval. Sets the position sampling interval in seconds.
# GPS monitor enabled. If this setting is enabled the WCU will continuously send its GPS position to the portal enabling real-time monitoring of the whereabouts of the WCU.
# GPS monitor interval. Set how often the position will be updated. The interval is in seconds.

===Configure the IDC Module===
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.
[[File:Screenshot from 2021-10-19 10-17-38.png|none|thumb|Settings for the IDC module]]
From version 2.68.0 another option also exists where the file output format can be set.

===Configure the M-log Module===
[[File:Screenshot from 2022-04-21 16-11-28.png|alt=Settings for the M-log module|left|thumb|250x250px|Settings for the M-log module]]
From version 2.75.0 of the M-log module there are two more fields present. They are "Current firmware" which is the last known firmware for the M-log logger. "Desired firmware" consists of a drop-down list a out-of-band firmware files present on the portal. Select one the files and the WCU will try to apply the firmware upgrade to the M-log as soon as possible.<br clear="all">

===Configure the MCD-Hub Module===
The MCD-Hub module is deprecated and should not be used anymore. The configuration for the MCD-Hub has only two settings. The first is the MCD-Hubs IP address and the second is is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

===Configure the MQTT Module===
The available settings for the MQTT Module is presented in Figure "Settings for the MQTT module".

[[File:Modules MQTT.png|thumb|left|250px|Settings for the MQTT module]]
<br clear="all">

This panel can be used to define an alternative host for the MQTT broker. Default is, as displayed in the illustration, localhost. Here you can also change the debug level for the module.

===Configure the RP Module===
For this module it is only possible to configure modify the debug level, see Figure "Settings for the RP module".

[[File:Illustration44.png|thumb|left|250px|Settings for the RP module]]
<br clear="all">

More information on how to use the RP module is found in the [[WICE RP Manual]] and the [[WICE RP How-To]].

===Configure the Signal Reader Module===
[[File:Modules Signal-Reader.png|thumb|250px|Settings for the Signal Reader module]]
As of version 2.33 of the WCU software it is possible to monitor signals in real time. For this to happen you must enable the feature by checking the box “Enable monitor” illustrated in Figure "Settings for the Signal Reader module". The monitoring can either be set as asynchronous or synchronous. In the former case, there is a regular signal communication with the portal and in the latter case with a specified destination port. For the synchronous case it is also possible to specify which transport protocol to use: TCP or UDP. The monitoring rate for both cases is set using the "Interval" field, where the default is once per second.

Also here it is possible to define the debug level. Further, the module settings include selecting whether or not the MDF files are to be written upon recorder stop and the version of the generated MDF file. In the sampling section there are two main choices; whether or not to record samples on change and enabling/disabling of piecewise linear approximation (PLA). If samples are to be recorded on change, it is possible to also choose to include one sample before the change. With the choice of PLA comes the option of defining the error percentage for the signal range and the maximum segment length in number of samples.

Thereafter you can select whether to aggregate ReadDataByIdentifier (service 22) diagnostic requests and which channel that should be used as the default diagnostics channel. Default interface can be CAN or DoIP and will affect the assignment that has the interface "Default Channel" selected and also the DREC. It is also possible to enter appropriate values for the diagnostics timeout. The timeout values determine how long time to wait for diagnostic responses before assuming that there are none. Typically, the timeout for sequence file diagnostics is set to a higher value due to the fact that it doesn't negatively impact the update frequency of active (diagnostics) signals.

===Configure the SmartEye Module===
The configuration for this module is identical to that of the RP module, depicted in Figure "Settings for the RP module".

===Configure the Soft-Hub===
As for the RP and Smarteye module, its only editable parameter is the debug level using a panel as displayed in Figure "Settings for the RP module".

===Configure the State of Health Module===
The state of health module has the same settings as the IDC module above.

===Configure the Software Download Module===

The SWDL module has the same settings as the IDC module above apart from one difference highlighted in red in Figure "Settings for the Software Download Module".

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
<br clear="all">

For WCUs of version 2.53 and forward it is possible to allow updates to be performed without manual interaction by checking the high-lighted checkbox. If this option is chosen, the updates will instead be performed as soon as possible.

===Configure the Uptime Module===

This module is used to report how much and how long the WCU is running and its configuration is set using the panel displayed in Figure "Settings for the Uptime Module".

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
<br clear="all">

First of all you can enable/disable the functionality all together with the “Enabled” checkbox. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

=== Configure the Video Module ===
A description of how to configure the video module can be found here. An explanation of the module in more general terms is found in the [[WICE video]] section.

The video module can be configured both regarding the recording and the monitoring. The recording parameters refers to what is recorded on the WCU to disc to be uploaded, whereas the monitoring parameters refer to the live video that is streamed from the WCU.

The available '''recording''' settings are:
* '''Width''', which is the width in pixels of the recorded video.
* '''Height''', which is the height in pixels of the recorded video.
* '''Frame rate''', which is the number of video frames per second to be recorded.
* '''Codec''', which is the video codec used when recording video clips to disc. Avaliable codecs are JPEG and VP8. (Note that the video that is uploaded to the portal is typically transcoded to MPEG-4 format, and codec only refers to the recording phase in the WCU.)
* '''Clip size''', which is the size in seconds or bytes of clips recorded on the WCU. The clips are subsequently concatenated on the Portal, if needed.
* '''Clip unit''', which is the unit for the clip size setting (bytes or seconds).

The available '''monitoring''' settings are:
* '''Enable monitoring''', which enables or disables monitoring of video.
* '''Width''', which is the width in pixels of the monitored video.
* '''Height''', which is the height in pixels of the monitored video.
* '''Frame rate''', which is the number of video frames per second to be recorded.
* '''Codec''', which is the video codec used when streaming monitored video. Avaliable codecs are JPEG and VP8.
* '''Destination IP address''', which is the IP address to which monitored video is transmitted.

There is also a setting for rotating the video, to be used if the camera is installed upside-down or at a 45 degree angle.

=== Configure the Vinreader Module ===
[[File:Screenshot from 2022-04-22 08-59-33.png|alt=Settings for the Vinreader module|thumb|250x250px|Settings for the Vinreader module]]
The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11, BP, TEA2+, UDS, DoIP''' or '''FIXED'''. The preferred setting for this is OBD2, whereby a standardized OBD-II diagnostic service is used to read out the VIN. SPA29 and SPA11 refers to using CAN diagnostic requests using either 29 bit or 11 bit SPA addressing respectively. The CAN channel (on the WCU) is selected in 'Default CAN channel'.

When the setting FIXED is used, the VIN will not be read out from the vehicle using a diagnostic service, but rather a preset value entered in the item named 'Fixed VIN' is used.
[[File:Screenshot from 2022-04-22 09-09-21.png|alt=Vehicle ID method type|thumb|Vehicle ID method type]]
[[File:Screenshot from 2022-04-22 09-55-55.png|alt=No identifying label selected|thumb|No identifying label selected]]
[[File:Skärmavbild 2019-12-18 kl. 15.17.58.png|thumb|Audio module settings]]

'Save VIN' is a checkbox for save vin. As default the box is checked which means that it will save the VIN number if the WCU can successfully read it. If the 'Save VIN' is unchecked then the WCU will try to read the VIN number every time it boots.

There are currently two ways of identifying a vehicle, either by reading the VIN or the chassis number. The selection is shown in Illustration 'Vehicle ID method type' to the right. When using 'Chassis NO' as identification type you must select which valued label to use for this mechanism. If no such label has been selected, you will see the the text 'No label selected in backend' to the right of the selected type, see Illustration 'No identifying label selected' on the right. To select which label to use, head over to the [[Labels#Administer labels|label administration tab]] to make the selection.

==The Administration Tab==
This tab is a collection of the administrative tasks available in the portal. These are “Connect car to WCU”, “Archives”, “GDS/SDDB file”, “Resource Groups”, “Users”, "Labels", "WCU Status" and "Key Figures".

===The Connect Car to WCU Tab===

To archive which vehicle a specific WCU was in at the time a task was run can be done by connecting a vehicle to a WCU in this tab. This is usually done automatically but in some situations it is necessary to do this manually

The area is divided into two tables, one for searching WCUs, the left one, and one for searching vehicles, the right one. When you start typing the name of the WCU you are looking for in the upper left corner just above the table, matching WCUs appear in the left table. To find the vehicle you are looking for, you do the same in the right table but here you have the option of using either the VIN or plate number.

To connect a WCU with a vehicle you drag the WCU you would like to connect onto the vehicle in the right table. When you drop it onto a car a small icon will show signifying that the WCU and vehicle are connected.

From version 2.42 it is also possible to select a WCU and a Car and then click on the new "Connect" button located between the two grids.

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Figure "Connect Cars to WCU" for an example.

[[File:Illustration 45.png|thumb|frame|left|600px|Connect Cars to WCU]]
<br clear="all">
The connection is a sort of instantaneous carbon copy of the situation at the time that a task was created. If you later change the connection, already running/run tasks will not be affected.

===The Resource Groups Tab===
This tab is used to administer some parts of the creation and destruction of resource groups and more. The panel for administering the resource groups is depicted in the Figure "Resource Group Tab".

[[File:Illustration 57.png|thumb|left|800px|Resource Group Tab]]
<br clear="all">

At the top is a search field to search for resource groups. Next are two tables, side by side. The left table lists the resource groups found depending on your search criteria. When a resource group is selected, the resources that are part of the resource group are shown in the right table. Next, the functionality of the buttons will be covered.

====Add and Remove Resource Groups====
[[File:CreateNewResourceGroup.png|thumb|Add Resource Group Dialog]]

To add a resource group you simply press the “New resource group” button and the following window will show. Here you can type the name for the new resource group, set the resource group as strict (see [[Strict resource group|Strict Resource Groups]]) and, if you choose to set the resource group as strict, set what platform type and platform subtype it should have. When you feel satisfied with your selections press “Create” to create the resource group. If you change your mind, press the “Cancel” button. Resource groups are global and writable and that means that names must be unique. The reason for this is that a resource group name takes on the form as both the resources car and WCU and those must be unique and therefore the resource groups must also be unique. One can, however, imagine situations where this must not be enforced but at the moment this is the case.

To remove a resource group, press the “Remove resource group” button. Be aware that no warning is given if there are resources in the group when removing it.

====Manipulating Resources in a Resource Group====
In the right hand table in Figure "Manipulating Resources in Resource Group", you see a set of resources for a resource group.

[[File:Illustration 59.png|thumb|frame|left|800px|Manipulating Resources in Resource Group]]
<br clear="all">

Here are both WCUs and cars part of the group. In addition to the type there is a column named “Status”. That column only applies to WCUs. The use of this column is as follows. Assume you have a resource group consisting of 50 WCUs. Further, lets make a configuration change to that resource group. Depending on where the WCUs geographically are and how they are used the WCUs will be updated at different times. How do you you know when all WCUs are up to date in the resource group? You could check them individually in the “Vehicles” panel but that is not very elegant and time saving. Instead, just watch the “Status” column for the WCUs. When a WCU is up to date with respect to the group configuration the color in the column will be green. The value is updated each 30 seconds.

The different color values are:

===== Red =====
The WCU's configuration was edited after the resource group's configuration was saved. The WCU will never use the resource group's configuration.

===== Yellow =====
The WCU's configuration is the same as the resource group's but the WCU has not yet updated to this configuration.

===== Green =====
The WCU has updated to the resource group's configuration.

You can remove individual resources from a group by selecting the resource and then press the “Remove resource” button.

Yet another button remains and it is the button “Base Group on Resource”. When you add a WCU to a resource group in the “Vehicles” panel you have the option of not updating the WCU configuration to match the one of the resource group's, see Figure "Dialog: WCU Moved to Another Resource Group" in [[#Resource Groups]]. Using this function it is possible to base the whole group on a WCU's configuration rather than the group's configuration.

=== The Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|here]].

=== The Alarm Tab ===

This tab is further described [[Alarm|here]].

===The User Tab===
[[File:Illustration46.png|border|800x800px]]The basic layout of the areas is just the same here as before. At the top you have a search area, in the middle is a result are and at the bottom are a set of buttons. The tab with a set of example users is in the Figure "User Administration Tab".
The nine columns are:

* '''User ID'''. The unique ID that the user must enter when logging in.
* '''Name'''. The name of the user.
* '''Roles'''. Depending on which roles the user has to, he/she have different privileges. The roles are non-overlapping, i.e. being an “Admin” does not necessarily mean that you can do everything a “User” can do.
* '''Enabled'''. Tells whether the account is enabled or not.
* '''Email Address'''. By registering an email address a user can receive notifications via email from a WCU when certain event occurs.
* '''Last login date'''. The date when the user last logged in.
* '''Two factor auth'''. Whether the two-factor authentication is turned on for a particular user.
* '''Logged in'''. You can see if the user is currently logged in.
* '''Creation Date'''. The date of when the user was created. Only visible on users created after December 3 2020.

At the bottom there are eight buttons. They are:
# The “New” button brings up the “New User” dialog which adds a new user to the portal
# The “Edit” button brings up the “Edit User” dialog
# The “Change Password” button brings up a dialog to change a user's password.
# The “Create new secret” button. Pressing this generates a new cryptographic salt to be used when generating one-time passwords. If you do this for a user without enabling the possibility to see the secret on the next login, renders the user unable to login to the portal. No dialog is opened, simply a message saying that a new one has been generated is shown.
# The “Show secret” button. Shows a dialog with the cryptographic salt shown in clear text as well as the QR-code, more on this later.
# Edit roles and permissions
# The “Save headers” button. Saves the headers and their order to be used as default on later logins.
# Video. Start a video conversations with another user of the portal. You must have the software “Confero” installed for this to work.

====The New User Dialog====
By pressing the “New User” button the dialog appears as presented in Figure "New User Dialog". Mandatory fields are User ID and the two password fields. Remember that the User ID must be unique and you will be notified if it is not. Add the roles that you want the user to have by moving roles from the left list to the right. You can hover each role to view more information about them. Click the “Add” button to add the user or change you mind by clicking “Cancel”. If you click "Add" and the roles you have selected gives the user access to some wcus tasks, you will also be prompted about giving the user access to currently running tasks on these wcus as well. This can also be done when editing the roles of a user.

Once the new user has been created, that user is granted a default minimalistic view in both the Tasks- and Vehicles-panel. This mechanism exists to prevent new users from being overwhelmed by the large amount of columns available in these panels. Instead, they are only presented with the most important columns, with the option to see more columns if they want to. The default columns for new users are:
* Tasks panel
** Task ID
** Assignment name
** Assignment type
** WCU ID
** Status
** Task creator
** Creation date
** Resource group
* Vehicles panel
** WCU ID
** VIN
** WCU comment
** WCU software version
** WCU connection time
** Resource group
** Active alarms
[[File:NewUserDialog252.png|left|thumb|New User Dialog]]
[[File:PromptNewUserCurAss.png|left|thumb|Prompt to give user permission to currently running tasks on specified wcus]]
<br clear="all">

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Figure "Modify User Dialog". The User ID cannot be changed. A disabled account can not be used for logging onto the portal even if the correct user name and password are given. To modify the user roles, select or deselect a role by using the check boxes. To turn on two-factor authentication for a user, check the appropriate box. When you are satisfied with your modifications, press the “Save” button to make them permanent on the portal or press the “Cancel” button if you change your mind.

To enable two factor authentication, tick the check box “Enable two factor authentication”. This will force the user to add another special one time password in addition to the account password when logging into the portal. The one time password is generated by a program on either your computer or if you want to you can install it on your smart phone which is probably the best solution. The program that generates one time password is based on a cryptographic salt and the current time. The cryptographic salt is randomly generated by the portal and is individual for each user. A secret can at any time be regenerated for a user which will render the user unable to login if you do not tick the check box “Show the secret to the user on their next login”.

Just like when adding a new user, you can give or remove roles to the user by clicking "Edit user roles" and moving roles from the left list to the right and vice versa. If you edit the user roles to add some wcu task permission to the user, you will also here be prompted about giving the user access to currently running tasks on these wcus as well.
[[File:EditUser252.png|left|thumb|Modify User Dialog]]
<br clear="all">

====The Change Password Dialog====

To change a user's password, press the “Change Password” button and the dialog below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
<br clear="all">

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|QR-code Window]]

A QR-code is shown that can be transferred to a smart phone by simply starting the authenticator app, point it at the screen and let the phone read the QR-code. An example of such a QR-code can be seen in Figure "QR-code Window". If the application that is to be used as a password generator do not support QR codes, the secret is shown in clear text at the top.

==== Edit User Roles and Permissions ====

Here it is also possible to edit user roles and permissions, read further instructions [[Roles and permissions|here]].

=== The Labels Tab ===
This tab is used to administer labels. Here you can enable/disable labels, rename labels which are not system labels and it is possible to make private labels global. If the feature is enabled at your site, it is also possible to configure label announcements here.

More about these functions can be found in [[Labels#Administer labels|Administer Labels]].

===The WCU Status Tab===
From version 2.47 the WCU status tab has changed. See [[WCU Status]].

'''The Following applies to portal version 2.46 and older:'''

This view is supposed to be used for supervising a set of vehicles. The supervision is done in real time and the values for the set of vehicles are updated as soon as they arrive on the server from the different vehicles.

The set of status information collected comprises three parts:

'''General information:'''
* Alive, a heart beat signal
* Connectivity, what data rates are currently available to the vehicle.
** 4G
** 3G
** 2G
** none
* Cell Signal Quality (CSQ). Indicates the signal strength of the mobile modem. The values are between 0 – 31, the higher the value the better. The special value of 99 is designated an unknown or not even detectable signal.
* GPS, simply a binary indicator of fix or no fix for the GPS.

'''Data Storage Usage:'''<br>
This set of data informs how much collected data resides in the WCU for each type of data collector (module). Total data indicates how much of the total amount of data storage available is used. After that, each type of data collector is lined up.

'''Data Collection Status:'''<br>
When modules collect data they go through a set of states when triggers starts, stops and other events occur. Currently, only such events for the signal reader module is available. An optional message accompanying the current state is shown in parenthesis.

The screen is divided in two parts, on the left hand side is a table with search functionality for finding the vehicles of interest and on the right hand side is the monitored vehicles. To monitor a vehicles you search for it in the table and then drag and drop the vehicle on the right hand panel.

A view of the panel is depicted in the Figure "WCU Status Tab".

[[File:Illustration57.png|left|frame|WCU Status Tab]]
<br clear="all">

===The Key Figures Tab===

In this tab it is possible to view charts over recorded statistics for the portal. More about this option is found under [[Key Figures]].

File:VehicleProfiles.png

2022-10-05T08:06:15Z

Loe.Lindstrom: Loe.Lindstrom uploaded a new version of File:VehicleProfiles.png

VehicleProfiles

Vehicle Profiles

2022-10-05T08:03:08Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
[[File:Vehicle-description-files.png|thumb|The Vehicle Description files portlet]]

The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* '''DBC''' - describing CAN interfaces
* '''FIBEX''' - describing Flexray interfaces
* '''A2L''' - describing ECU interfaces
* '''ECU''' '''Diagnostics''' (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

File:Vehicle-description-files.png

2022-10-05T08:02:24Z

Loe.Lindstrom:

Description files portlet in vehicle profiles tab

Vehicle Profiles

2022-10-04T10:29:34Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* '''DBC''' - describing CAN interfaces
* '''FIBEX''' - describing Flexray interfaces
* '''A2L''' - describing ECU interfaces
* '''ECU''' '''Diagnostics''' (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

Vehicle Profiles

2022-10-04T10:29:20Z

Loe.Lindstrom:

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* '''DBC''' - describing CAN interfaces
* '''FIBEX''' - describing Flexray interfaces
* '''A2L''' - describing ECU interfaces
* '''ECU''' Diagnostics (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

Vehicle Profiles

2022-10-04T10:27:05Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* '''DBC''' - describing CAN interfaces
* '''FIBEX''' - describing Flexray interfaces
* '''A2L''' - describing ECU interfaces
* '''ECU''' Diagnostics (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

Vehicle Profiles

2022-10-04T10:22:44Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* DBC - describing CAN interfaces
* FIBEX - describing Flexray interfaces
* A2L - describing ECU interfaces
* ECU Diagnostics (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

Vehicle Profiles

2022-10-04T10:19:29Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* DBC - describing CAN interfaces
* FIBEX - describing Flexray interfaces
* A2L - describing ECU interfaces
* ECU Diagnostics (e.g. sddb-files) - provides which ECUs that are available for creating diagnostic templates (see above).

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

Vehicle Profiles

2022-10-04T10:00:05Z

Loe.Lindstrom: /* Manage Description files */

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel|none]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profiles-vehicle-profile-portlet.png|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[The Portal Administrator View#The ECU Diagnostics Tab|The ECU Diagnostics Tab]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

== Manage Description files ==
The "Description files" portlet let the user upload, change or remove description files. These files are used to describe the interfaces. Currently, the descriptiojn files taht are supported are DBC for CAN, FIBEX for Flexrasy and A2L for ECU.

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

New features in v2.79

2022-09-26T10:40:49Z

Loe.Lindstrom:

== ECU Diagnostics tab moved: Non-admin users have access ==
The tab that could previously be found here.

Can now be found here.

This means that anyone with the permission to read vehicle profiles can see these files and anyone with the permission to write to vehicle profiles can upload new files.

(Edit in progress)

New features in v2.78

2022-09-01T04:55:48Z

Loe.Lindstrom: /* Ethernet capture task can specify a pre-trigger duration */

== File fetcher task supports multiple file paths ==
The task [[Creating a Task#File fetcher|File fetcher]] now supports multiple file paths if the WCU is v.2.78 or later - hence multiple files can be fetched from the WCU and made available for download in the Portal.

== WCU History Panel shows info about Resource Group ==
WCU History Panel has been expanded with a new column "Resource group". This column shows the resource group history of the selected WCU. Reach the WCU history from the [[Vehicles#Right click context menu|Vehicles tab]].

== Tasks tab shows Resource Group at creation of task ==
Resource group in [[Tasks Tab|Tasks tab]] has now been updated to show what resource group the task had when it was created. Before it showed the Resource Group that the WCU was currently in.

== Vehicles tab can sort on WCU storage usage ==
It is possible to sort on the column "WCU storage usage" in the [[Vehicles#Right click context menu|Vehicles tab]]. The column shows how many percentage are used of the total storage capacity. The total storage capacity is also shown but the column is sorted by the percentage used.

== Updated information Panel with new information ==
Statistics has been added to resource group in information Panel. Read more about it [https://wiki.alkit.se/wice278/index.php/Information_Panel here]

== Ethernet capture task can specify a pre-trigger duration ==
When creating an [[Ethernet capture|Ethernet capture task]] there is now an option to add a pre-trigger duration, meaning that traffic from some time before the actual trigger is also captured.

The pre-trigger duration may be set to anything between 10 and 1000 seconds and is available on WCUs with version 2.67.0 or later.

New features in v2.78

2022-08-31T13:09:47Z

Loe.Lindstrom: /* Ethernet capture task can specify a pre-trigger duration */

== File fetcher task supports multiple file paths ==
The task [[Creating a Task#File fetcher|File fetcher]] now supports multiple file paths if the WCU is v.2.78 or later - hence multiple files can be fetched from the WCU and made available for download in the Portal.

== WCU History Panel shows info about Resource Group ==
WCU History Panel has been expanded with a new column "Resource group". This column shows the resource group history of the selected WCU. Reach the WCU history from the [[Vehicles#Right click context menu|Vehicles tab]].

== Tasks tab shows Resource Group at creation of task ==
Resource group in [[Tasks Tab|Tasks tab]] has now been updated to show what resource group the task had when it was created. Before it showed the Resource Group that the WCU was currently in.

== Vehicles tab can sort on WCU storage usage ==
It is possible to sort on the column "WCU storage usage" in the [[Vehicles#Right click context menu|Vehicles tab]]. The column shows how many percentage are used of the total storage capacity. The total storage capacity is also shown but the column is sorted by the percentage used.

== Updated information Panel with new information ==
Statistics has been added to resource group in information Panel. Read more about it [https://wiki.alkit.se/wice278/index.php/Information_Panel here]

== Ethernet capture task can specify a pre-trigger duration ==
When creating an Ethernet capture task there is now an option to add a pre-trigger duration, meaning that traffic from some time before the actual trigger is also captured.

The pre-trigger duration may be set to anything between 10 and 1000 seconds and is available on WCUs with version 2.67.0 or later.

Ethernet capture

2022-08-31T13:08:08Z

Loe.Lindstrom: /* Pre-trigger duration (Since 2.67) */

The ethernet capture task and module can capture ethernet traffic from interfaces on the WCU in a format known as [[wikipedia:Pcap|pcap]]. This is a standarized format of saving packet information and can be used in many tools to be analyzed. As there can be a lot of traffic on ethernet interfaces, there is an option to enter a filtering expression (Capture expression) to only capture certain packets of interest. Examples and descriptions of filter expressions can be found [https://biot.com/capstats/bpf.html here] and [https://www.comparitech.com/net-admin/pcap-guide/ here].
[[File:Screenshot from 2021-04-01 08-53-12.png|thumb|Creating an Ethernet capture task|350x350px]]

== Ethernet interface and capture expression ==
To create a task of this type you need to at least enter the interface which you would like to capture from using the "Ethernet interface" drop-down selector at the top. Only interfaces available for the current platform will show. In the section "Capture expression" you simply enter the expression for capturing packets. Depending on the installation at your site, there might be a button for validating the expression "Validate expression". Press this to validate the expression. If this is not available, you could use any local tool available to you to validate the capture expression. Examples of such tools are [https://www.tcpdump.org/manpages/tcpdump.1.html tcpdump] and [https://www.wireshark.org/ wireshark].

When done, simply press "Submit & Close" to get the task down to the WCU.

== Triggers ==

=== Start- and stop-triggers (Since 2.66) ===
It is possible to add trigger expressions that will start and/or stop the task. To do this, check the box "Enable Triggers". Use the buttons "Start trigger..." and "Stop trigger..." to add a start and stop trigger expression. Note that the signals that are used in the start and stop trigger expressions '''must''' be measured by the signal reader assignment on the WCU/s in question. It is possible to leave the Stop Trigger blank, but a Start Trigger must be supplied. It is also possible to set how long the capture should undergo after the Start trigger expression has been met by using the Max Duration field.

=== Pre-trigger duration (Since 2.67) ===
For WCUs with version 2.67 or later it is also possible to add a pre-trigger duration. By adding this the traffic before the start trigger will also be captured, for the amount of time specified.

== Analyzing Results ==
The results from the captured data on the WCU is delivered as pcap files. This is a standardized binary format for captured ethernet packets. One of the most widely used tools to analyze such data is [https://www.wireshark.org/ wireshark] which is available for most computer platforms.

Ethernet capture

2022-08-31T12:46:06Z

Loe.Lindstrom: /* Analyzing Results */

The ethernet capture task and module can capture ethernet traffic from interfaces on the WCU in a format known as [[wikipedia:Pcap|pcap]]. This is a standarized format of saving packet information and can be used in many tools to be analyzed. As there can be a lot of traffic on ethernet interfaces, there is an option to enter a filtering expression (Capture expression) to only capture certain packets of interest. Examples and descriptions of filter expressions can be found [https://biot.com/capstats/bpf.html here] and [https://www.comparitech.com/net-admin/pcap-guide/ here].
[[File:Screenshot from 2021-04-01 08-53-12.png|thumb|Creating an Ethernet capture task|350x350px]]

== Ethernet interface and capture expression ==
To create a task of this type you need to at least enter the interface which you would like to capture from using the "Ethernet interface" drop-down selector at the top. Only interfaces available for the current platform will show. In the section "Capture expression" you simply enter the expression for capturing packets. Depending on the installation at your site, there might be a button for validating the expression "Validate expression". Press this to validate the expression. If this is not available, you could use any local tool available to you to validate the capture expression. Examples of such tools are [https://www.tcpdump.org/manpages/tcpdump.1.html tcpdump] and [https://www.wireshark.org/ wireshark].

When done, simply press "Submit & Close" to get the task down to the WCU.

== Triggers ==

=== Start- and stop-triggers (Since 2.66) ===
It is possible to add trigger expressions that will start and/or stop the task. To do this, check the box "Enable Triggers". Use the buttons "Start trigger..." and "Stop trigger..." to add a start and stop trigger expression. Note that the signals that are used in the start and stop trigger expressions '''must''' be measured by the signal reader assignment on the WCU/s in question. It is possible to leave the Stop Trigger blank, but a Start Trigger must be supplied. It is also possible to set how long the capture should undergo after the Start trigger expression has been met by using the Max Duration field.

=== Pre-trigger duration (Since 2.67) ===
For WCUs with version 2.67 or later it is also possible to add a pre-trigger duration. By adding this, the traffic before the start trigger will be captured. How much before is given by the pre-trigger duration. I.e. if the pre-trigger is set to 20 seconds, the traffic happening from 20 seconds before the start trigger up until the start-trigger will also be captured and saved.

== Analyzing Results ==
The results from the captured data on the WCU is delivered as pcap files. This is a standardized binary format for captured ethernet packets. One of the most widely used tools to analyze such data is [https://www.wireshark.org/ wireshark] which is available for most computer platforms.

Ethernet capture

2022-08-31T12:42:30Z

Loe.Lindstrom:

The ethernet capture task and module can capture ethernet traffic from interfaces on the WCU in a format known as [[wikipedia:Pcap|pcap]]. This is a standarized format of saving packet information and can be used in many tools to be analyzed. As there can be a lot of traffic on ethernet interfaces, there is an option to enter a filtering expression (Capture expression) to only capture certain packets of interest. Examples and descriptions of filter expressions can be found [https://biot.com/capstats/bpf.html here] and [https://www.comparitech.com/net-admin/pcap-guide/ here].
[[File:Screenshot from 2021-04-01 08-53-12.png|thumb|Creating an Ethernet capture task|350x350px]]

== Ethernet interface and capture expression ==
To create a task of this type you need to at least enter the interface which you would like to capture from using the "Ethernet interface" drop-down selector at the top. Only interfaces available for the current platform will show. In the section "Capture expression" you simply enter the expression for capturing packets. Depending on the installation at your site, there might be a button for validating the expression "Validate expression". Press this to validate the expression. If this is not available, you could use any local tool available to you to validate the capture expression. Examples of such tools are [https://www.tcpdump.org/manpages/tcpdump.1.html tcpdump] and [https://www.wireshark.org/ wireshark].

When done, simply press "Submit & Close" to get the task down to the WCU.

== Triggers ==

=== Start- and stop-triggers (Since 2.66) ===
It is possible to add trigger expressions that will start and/or stop the task. To do this, check the box "Enable Triggers". Use the buttons "Start trigger..." and "Stop trigger..." to add a start and stop trigger expression. Note that the signals that are used in the start and stop trigger expressions '''must''' be measured by the signal reader assignment on the WCU/s in question. It is possible to leave the Stop Trigger blank, but a Start Trigger must be supplied. It is also possible to set how long the capture should undergo after the Start trigger expression has been met by using the Max Duration field.

=== Pre-trigger duration (Since 2.67) ===
For WCUs with version 2.67 or later it is also possible to add a pre-trigger duration. By adding this, the traffic before the start trigger will be captured. How much before is given by the pre-trigger duration. I.e. if the pre-trigger is set to 20 seconds, the traffic happening from 20 seconds before the start trigger up until the start-trigger will also be captured and saved.

== Analyzing Results ==
Th results from the captured data on the WCU is delivered as pcap files. This is a standardized binary format for captured ethernet packets. One of the most widely used tools to analyze such data is [https://www.wireshark.org/ wireshark] which is available for most computer platforms.

File:Screenshot from 2021-04-01 08-53-12.png

2022-08-31T12:40:29Z

Loe.Lindstrom: Loe.Lindstrom uploaded a new version of File:Screenshot from 2021-04-01 08-53-12.png

Creating an ethernet capture task

Ethernet capture

2022-08-31T12:34:58Z

Loe.Lindstrom: /* Triggers (Since 2.66) */

[[File:Screenshot from 2021-04-01 08-53-12.png|thumb|Creating an Ethernet capture task|782x782px]]
The ethernet capture task and module can capture ethernet traffic from interfaces on the WCU in a format known as [[wikipedia:Pcap|pcap]]. This is a standarized format of saving packet information and can be used in many tools to be analyzed. As there can be a lot of traffic on ethernet interfaces, there is an option to enter a filtering expression (Capture expression) to only capture certain packets of interest. Examples and descriptions of filter expressions can be found [https://biot.com/capstats/bpf.html here] and [https://www.comparitech.com/net-admin/pcap-guide/ here].

== Ethernet interface and capture expression ==
To create a task of this type you need to at least enter the interface which you would like to capture from using the "Ethernet interface" drop-down selector at the top. Only interfaces available for the current platform will show. In the section "Capture expression" you simply enter the expression for capturing packets. Depending on the installation at your site, there might be a button for validating the expression "Validate expression". Press this to validate the expression. If this is not available, you could use any local tool available to you to validate the capture expression. Examples of such tools are [https://www.tcpdump.org/manpages/tcpdump.1.html tcpdump] and [https://www.wireshark.org/ wireshark].

When done, simply press "Submit & Close" to get the task down to the WCU.

== Triggers ==

=== Start- and stop-triggers (Since 2.66) ===
It is possible to add trigger expressions that will start and/or stop the task. To do this, check the box "Enable Triggers". Use the buttons "Start trigger..." and "Stop trigger..." to add a start and stop trigger expression. Note that the signals that are used in the start and stop trigger expressions '''must''' be measured by the signal reader assignment on the WCU/s in question. It is possible to leave the Stop Trigger blank, but a Start Trigger must be supplied. It is also possible to set how long the capture should undergo after the Start trigger expression has been met by using the Max Duration field.

=== Pre-trigger duration (Since 2.67) ===
For WCUs with version 2.67 or later it is also possible to add a pre-trigger duration. By adding this, the traffic before the start trigger will be captured. How much before is given by the pre-trigger duration. I.e. if the pre-trigger is set to 20 seconds, the traffic happening from 20 seconds before the start trigger up until the start-trigger will also be captured and saved.

== Analyzing Results ==
Th results from the captured data on the WCU is delivered as pcap files. This is a standardized binary format for captured ethernet packets. One of the most widely used tools to analyze such data is [https://www.wireshark.org/ wireshark] which is available for most computer platforms.

New features in v2.78

2022-08-31T12:06:49Z

Loe.Lindstrom:

== File fetcher task supports multiple file paths ==
The task [[Creating a Task#File fetcher|File fetcher]] now supports multiple file paths if the WCU is v.2.78 or later - hence multiple files can be fetched from the WCU and made available for download in the Portal.

== WCU History Panel shows info about Resource Group ==
WCU History Panel has been expanded with a new column "Resource group". This column shows the resource group history of the selected WCU. Reach the WCU history from the [[Vehicles#Right click context menu|Vehicles tab]].

== Tasks tab shows Resource Group at creation of task ==
Resource group in [[Tasks Tab|Tasks tab]] has now been updated to show what resource group the task had when it was created. Before it showed the Resource Group that the WCU was currently in.

== Vehicles tab can sort on WCU storage usage ==
It is possible to sort on the column "WCU storage usage" in the [[Vehicles#Right click context menu|Vehicles tab]]. The column shows how many percentage are used of the total storage capacity. The total storage capacity is also shown but the column is sorted by the percentage used.

== Updated information Panel with new information ==
Statistics has been added to resource group in information Panel. Read more about it [https://wiki.alkit.se/wice278/index.php/Information_Panel here]

== Ethernet capture task can specify a pre-trigger duration ==
When creating an [[Ethernet capture|Ethernet capture task]] start and stop triggers have been possible to add, i.e. when to start/stop capturing the ethernet traffic. Now there is an option to add a pre-trigger duration, which will capture traffic that happened before the start-trigger. Currently traffic can be captured between 10 and 1000 seconds before the start trigger.

This is available on WCUs with version 2.67.0 or later.

New features in v2.78

2022-08-31T11:53:42Z

Loe.Lindstrom: /* Vehicles tab can sort on WCU storage usage */

New features in v2.78

2022-08-31T11:52:10Z

Loe.Lindstrom:

== File fetcher task supports multiple file paths ==
The task [[Creating a Task#File fetcher|File fetcher]] now supports multiple file paths if the WCU is v.2.78 or later - hence multiple files can be fetched from the WCU and made available for download in the Portal.

== WCU History Panel shows info about Resource Group ==
WCU History Panel has been expanded with a new column "Resource group". This column shows the resource group history of the selected WCU. Reach the WCU history from the [[Vehicles#Right click context menu|Vehicles tab]].

== Tasks tab shows Resource Group at creation of task ==
Resource group in [[Tasks Tab|Tasks tab]] has now been updated to show what resource group the task had when it was created. Before it showed the Resource Group that the WCU was currently in.

== Vehicles tab can sort on WCU storage usage ==
It is possible to sort on the column WCU storage usage in the [[Vehicles#Right click context menu|Vehicles tab]]. The column shows how many percentage are used of the total storage capacity. The total storage capacity is also shown but the column is sorted by the percentage used.

== Updated information Panel with new information ==
Statistics has been added to resource group in information Panel. Read more about it [https://wiki.alkit.se/wice278/index.php/Information_Panel here]

New features in v2.78

2022-08-31T11:41:06Z

Loe.Lindstrom: /* Tasks Panel shows Resource Group at creation of task */

File:WikiwcuHistory.png

2022-08-31T11:38:36Z

Loe.Lindstrom: Loe.Lindstrom uploaded a new version of File:WikiwcuHistory.png

Example of a Show WCU history

New features in v2.78

2022-08-31T11:04:51Z

Loe.Lindstrom: /* Tasks Panel shows Resource Group at creation of task */

New features in v2.78

2022-08-31T11:03:30Z

Loe.Lindstrom: /* Added resource group in WCU History Panel. */

New features in v2.78

2022-08-31T10:51:24Z

Loe.Lindstrom: /* File fetcher task supports multiple file paths */

New features in v2.78

2022-08-31T10:46:22Z

Loe.Lindstrom: /* Support multiple paths for assignment type filefetcher. */

== File fetcher task supports multiple file paths ==
The task [[Creating a Task#File fetcher|File fetcher]] now supports multiple file paths if the WCU is v.2.78 or later. Read more [https://wiki.alkit.se/wice278/index.php/Creating_a_Task#File_fetcher here]

== Added resource group in WCU History Panel. ==
WCU History Panel has been expanded with a new column "resource group". This column shows the resource group history of the selected WCU.

== Updated resource group in Task Panel. ==
Resource group in Task Panel has now been updated to show what resource group the task had when it was create.

== Updated information Panel with new information. ==
Statistics has been added to resource group in information Panel. Read more about it [https://wiki.alkit.se/wice278/index.php/Information_Panel here]

File:File fetcher proxy example.png

2022-08-31T09:23:05Z

Loe.Lindstrom: Loe.Lindstrom uploaded a new version of File:File fetcher proxy example.png

The proxy feature for the file fetcher task.

Creating a Task

2022-08-31T09:10:55Z

Loe.Lindstrom: /* File fetcher */

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

== 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:CanrecorderIllust.png|thumb|Canrecorder]]

Canrecorder is a measurement module that allows CAN frames to be captured and logged. This task has four options described in Figure "Canrecorder" and below:

1. In the grid, select which bus (or buses) to record from. By clicking the check box in the top left corner, you can select all buses at once.

2. Specify which CAN frames you want to record by entering their CAN IDs in the CAN frame ID column in the grid, on the same row as the bus you have selected, or by entering the IDs in the text box labeled “Set filters on selected CAN buses”. If you use the latter option, the filters will be set on all of the buses you have selected. To enter a filter on a specific bus use the method of entering the filter on the same row as the selected bus, on the grid. This can only be done if the CAN frame passthrough filter is turned on. Turning off the CAN frame passthrough filter option will disable the CAN frame ID column in the grid. Press the “Clear All” button to remove all the entered filters from all buses.

3. Turning on or off a CAN frame pass-through filter. If you choose to have the filter on you must specify which CAN bus or CAN buses you wish to record.

4. Select how long time to record before and after the trigger.

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

[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]
<br clear="all">

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) ==
DLT itself provides a log and trace interface, based on the standardised 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].
[[File:New-task-dlt-2-72.png|thumb|The DLT new task dialog.]]
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 on WCUs with software version 2.72.0 or later 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.
# 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].

==== Older WCUs ====
For WCUs with software version earlier than 2.72.0 only one daemon is supported and only filters can be configured when creating a DLT task. To specify the daemon address and port go to the [[DLT Module]] instead.

== 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.<br />
== 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 are 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.

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

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

=== 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:UpdateWikiSWDL.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 a .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.

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

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

New features in v2.78

2022-08-31T09:05:51Z

Loe.Lindstrom: /* Support multiple paths for assignment type filefetcher. */

== File Fetcher task now support multiple file paths ==
The task [[Creating a Task#File fetcher|File fetcher]] now supports multiple file paths if the WCU is of v.2.78 or later - hence it can fetch multiple files from a WCU and make them available for download in the Portal.

== Added resource group in WCU History Panel. ==
WCU History Panel has been expanded with a new column "resource group". This column shows the resource group history of the selected WCU.

== Updated resource group in Task Panel. ==
Resource group in Task Panel has now been updated to show what resource group the task had when it was create.

== Updated information Panel with new information. ==
Statistics has been added to resource group in information Panel. Read more about it [https://wiki.alkit.se/wice278/index.php/Information_Panel here]

I/O configurations

2022-06-23T05:44:24Z

Loe.Lindstrom: /* The Miscellaneous Section */

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).

===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

===Set 5V out on boot===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-23T05:42:28Z

Loe.Lindstrom: /* Set digital out 3 on boot */

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).

===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

===Set 5V out on boot===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-23T05:40:00Z

Loe.Lindstrom: /* Set digital out 3 on boot */

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on boot. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).

===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

===Set 5V out on boot===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-23T05:30:40Z

Loe.Lindstrom:

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on boot. The purpose of this is to trigger an external measurement equipment like the [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]].

===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

===Set 5V out on boot===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-22T12:10:49Z

Loe.Lindstrom:

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".
===Set 5V out on boot===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. The option is visible for WCUs with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-22T12:08:46Z

Loe.Lindstrom:

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin.
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".
===Set 5V out on boot===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. The option is visible for WCUs with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

New features in v2.77

2022-06-22T12:03:35Z

Loe.Lindstrom: /* Activate buzzer on detected digital input change */

== Set 5V out on boot ==
New option on the WCU to set one of the output pins to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later and resides under Vehicles tab -> "Edit Configuration" -> "IO"-tab -> "Miscellaneous". See [[I/O configurations#Set 5V out on boot|Set 5V out on boot]].

== Activate buzzer on detected digital input change ==
New option on the WCU to enable a buzzing sound when a trigger-button (or other digital input) is activated. The option is visible for WCUs with version 2.76.0 or later and resides under Vehicles tab -> "Edit Configuration" -> "IO"-tab -> "Miscellaneous". See [[I/O configurations#Activate buzzer on detected digital input change|Activate buzzer on detected digital input change]].

== Support to use display names for labels ==
[[File:Edit-car-dialog-attribute-highlighted.png|alt=Red rectangle around an attribute label that have a display name showing instead of the label name. Also the display description is shown because the mouse pointer hovers over the attribute.|thumb|The new ''Display name'' and ''Display description'' in action]]
Labels can now beside their names also have a ''Display name'' and a ''Display description''. The name will show when a label is added as an attribute on a resource (e.g. a WCU) and the description will show when hovering over such an attribute. See [[Labels#Labels in Vehicles|managing labels on resources]]. To read more in depth about how to create and manage labels see [[Labels#Administer labels|Administer labels]].

I/O configurations

2022-06-22T11:45:25Z

Loe.Lindstrom: /* Set 5V out on boot */

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin.

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".
===Set 5V out on boot===
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. The option is visible for WCUs with version 2.76.0 or later.

===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-22T11:42:33Z

Loe.Lindstrom: /* Activate buzzer on detected digital input change */

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin.

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".
===Set 5V out on boot===
Option on the WCU to enable a buzzing sound when a trigger-button (or other digital input) is activated. The option is visible for WCUs with version 2.76.0 or later.
===Activate buzzer on detected digital input change===
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2022-06-22T11:42:00Z

Loe.Lindstrom: /* The Miscellaneous Section */

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin.

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".
===Set 5V out on boot===
Option on the WCU to enable a buzzing sound when a trigger-button (or other digital input) is activated. The option is visible for WCUs with version 2.76.0 or later.
===Activate buzzer on detected digital input change===
Option on the WCU to set one of the output pins to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later.

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

File:WCU conf io misc.png

2022-06-22T11:37:33Z

Loe.Lindstrom: Loe.Lindstrom uploaded a new version of File:WCU conf io misc.png

WCU conf io misc

I/O configurations

2022-06-22T11:35:12Z

Loe.Lindstrom:

<div class="keywords"> io, io configurations, io config, io configs </div>
<includeonly>= I/O configurations =</includeonly>
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin.

==Edit CAN channels==
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.

===Channel===
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.

===Speed (kB)===
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.

===Name===
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.

===Comment===
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.

==Edit Ethernet Channels==
[[File:WCU conf io eth channels.png|thumb|Edit Ethernet Channels]]
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains five columns and the individual meaning is as follows.

===Channel===
This column is a checkbox were you can enabled and disable ethX. Currently this setting has no meaning on the WCU.

===DHCP type===
In this column the DHCP type of the WCU is configured. The choices are "Client", "Server" and "None". Choosing "Client" means that the WCU will act as a DHCP client. "Server" means that it will act as a DHCP server. Choosing "None" means that it will use a static IP address which is set in the next column.

===IP address===
Here you set the static IP address if you have selected "None" as the DHCP type. The IP address here will also act as a fallback if the DHCP failed.

===Name===
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.

===Comment===
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is available for WCUs with version 2.49 or later.
===Set digital out 3 on boot===
===Diagnostic tester priority===
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".
===Set 5V out on boot===
===Activate buzzer on detected digital input change===

==Preselect template==
[[File:Io config2.png|thumb|frame|Preselect Template]]
Admins can save configs as templates (see [[#Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.
To select and apply a template, click "Preselect template" and the small window shown in Figure "Preselect Template" will pop up. From the drop down menu, select the template you want to apply and click "OK". You can always change settings or add more info, the template could be anything you need or just act as a starting point.

==Manage templates (for admins)==
[[File:Io config3.png|thumb|frame|Manage Templates]]
If you are a admin you have a extra button, "Manage templates" to the left of the "Preselect template" button. If you click "Manage templates" a new window will open up which can be seen in Figure "Manage Templates".
Previously saved templates are listed in the "Templates" table. To remove a template, click the red "Remove record" icon to the right of the template name. A confirmation dialog will popup prevent deletion by mistake.

To save the current config as a template, click the "Save current config as a template" button. You will be asked to set a name for the new template and when you press OK, the new template will be saved and listed in the "Templates" table above.

==Show Vehicle Profile==
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

File:Edit configuration IO.png

2022-06-22T11:23:40Z

Loe.Lindstrom: Loe.Lindstrom uploaded a new version of File:Edit configuration IO.png

New features in v2.77

2022-06-15T11:54:23Z

Loe.Lindstrom: /* Support to use display names for labels */

== Set 5V out on boot ==
New option on the WCU to set one of the output pins to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later and resides under Vehicles tab -> "Edit Configuration" -> "IO"-tab -> "Miscellaneous".

== Activate buzzer on detected digital input change ==
New option on the WCU to enable a buzzing sound when a trigger-button (or other digital input) is activated. The option is visible for WCUs with version 2.76.0 or later and resides under Vehicles tab -> "Edit Configuration" -> "IO"-tab -> "Miscellaneous".

== Support to use display names for labels ==
[[File:Edit-car-dialog-attribute-highlighted.png|alt=Red rectangle around an attribute label that have a display name showing instead of the label name. Also the display description is shown because the mouse pointer hovers over the attribute.|thumb|The new ''Display name'' and ''Display description'' in action]]
Labels can now beside their names also have a ''Display name'' and a ''Display description''. The name will show when a label is added as an attribute on a resource (e.g. a WCU) and the description will show when hovering over such an attribute. See [[Labels#Labels in Vehicles|managing labels on resources]]. To read more in depth about how to create and manage labels see [[Labels#Administer labels|Administer labels]].

New features in v2.77

2022-06-15T11:53:07Z

Loe.Lindstrom: /* Support to use display names for labels */

== Set 5V out on boot ==
New option on the WCU to set one of the output pins to supply electricity at 5V to external equipment. It is possible on all MX4 models except V61. The option is visible for WCUs with version 2.76.0 or later and resides under Vehicles tab -> "Edit Configuration" -> "IO"-tab -> "Miscellaneous".

== Activate buzzer on detected digital input change ==
New option on the WCU to enable a buzzing sound when a trigger-button (or other digital input) is activated. The option is visible for WCUs with version 2.76.0 or later and resides under Vehicles tab -> "Edit Configuration" -> "IO"-tab -> "Miscellaneous".

== Support to use display names for labels ==
[[File:Edit-car-dialog-attribute-highlighted.png|alt=Red rectangle around an attribute label that have a display name showing instead of the label name. Also the display description is shown because the mouse pointer hovers over the attribute.|thumb|The new ''Display name'' and ''Display description'' in action]]
Labels can now beside their names also have a ''Display name'' and a ''Display description''. The name will show when a label is added as an attribute on a resource (e.g. a WCU) and the description will show when hovering over such an attribute. See [[Labels#Labels in Vehicles|managing labels on resources]]. To read more about how to create and manage labels see [[Labels#Administer labels|Administer labels]].

File:Edit-car-dialog-attribute-highlighted.png

2022-06-15T11:51:31Z

Loe.Lindstrom:

The edit car dialog with an attribute label highlighted.

Labels

2022-06-15T11:16:15Z

Loe.Lindstrom: /* Administer labels */

From version 2.45 the concept of labels has been introduced in the WICE portal.

== Add labels to resources ==
Labels can currently be added to WCUs, vehicles and resource groups. In the [[Vehicles|Vehicles tab]], search out your resource, right click and choose "Manage labels" as illustrated in Figure "Adding Label to Resource". In the sub menu you can choose to either add or remove labels, the latter of which is only possible if the selected resources are associated with such.

When choosing to add labels, a new window as can be seen in Figure "Adding Label Dialog" will show up. Using the checkboxes it is possible to either add labels to the selected WCU, the connected vehicle or both. In the "Add labels"-selector, you can choose to add an already existing label from the drop down menu. If the desired label does not exist, you will get the opportunity to create it by pressing the enter key. This will open up the window as can be seen in Figure "Creating Label Dialog". When clicking "Save" the new label will be temporarily added to the resource as can be seen in Figure "Label Temporarily Added". Here you have the option to add another label by repeating the previous step. When finished, save the label(s) added to the current resource by clicking "Save".
<gallery widths="250" mode="nolines">
File:Labels add wcu.png|Adding Label to Resource
File:Labels add wcu2.png|Adding Label Dialog
File:Labels add wcu3.png|Creating Label Dialog
File:Labels add wcu4.png|Label Temporarily Added
</gallery>

When adding a label you also have the option to set a value if "Enable values" are enabled for the label of interest. See screenshot "Creating Label Dialog" above.

If values are enabled, the new label or the selected label has a small filter icon as can be seen in the screenshot "Show value selector" below. If this icon is clicked, a new value can either be selected by typing in the selector or by using the drop down menu. For a new label, the drop down menu is always empty.

If a resource already has a label with a value associated, the value can be replaced by adding the label again with a different value. The value can also be removed by adding the label without a label associated. The value can also be changed directly if you edit the labels via the [[#Manage labels on multiple resources|Manage labels on multiple resources]] in Vehicles. <gallery>
File:Add value.png|Show value selector
File:Add value2.png|Select or type value
</gallery>

To remove a label from a resource, select the "Remove labels from resources" option in the submenu of "Manage labels on resources". Doing so, results in the dialog presented in Figure "Removing label from Resource Dialog", which shows a list of all labels associated with the selected resources. To remove a label simply click it, resulting in it being grayed out, see Figure "Label Removed from Resource". When pressing "Save" the deselected labels are removed from all selected resources.

<gallery widths="250" mode="nolines">
File:Labels remove.png|Removing label from Resource Dialog
File:Labels remove2.png|Label Removed from Resource
</gallery>

Labels can currently only be managed on resources via the [[Vehicles]] tab. See [[#Labels in Vehicles]] for more info about adding labels while modifying other resource attributes.

== Global and private labels ==
[[File:Labels add wcu5.png|thumb|150x150px|Private Label]]
By default all user created labels in the WICE portal are global meaning that they are visible for every logged in user. When creating a new label, as in Figure "Creating Label Dialog" in [[#Add labels to resources]], you have the option make the label private by ticking the "Private" checkbox as can be seen in Figure "Private Label". A private labels renders with rounded corners as opposite to global labels which renders with sharp corners. Compare the Figure "Private Label" with any of the figures in [[#Add labels to resources]].

Private labels are, as the name suggests, only visible for the one who created it. In [[#Administrate labels]], there is a feature to turn private labels global.

== System labels ==
Currently there are two types of system labels; WCU software version and MX4 firmware version. System labels are labels created by the system and can not be added to the resource by a user. These labels are typically added to a resource (WCU) when its software changes or when to describe which software (and firmware) a WCU had at a certain time. More about this in [[#Labels in Tasks]].

== Values for labels ==
From version 2.64 it is possible to add values to labels in the WICE Portal. Values for labels makes it possible to use labels as a way to dynamically add new attributes (e.g vehicle colour etc) to resources and use the values to filter resources in the [[Tasks Tab|Tasks]] or the [[Vehicles]] tab.

A value for an existing label can only be added if the the "Enable values" option is turned on for the label of interest. See [[#Administer labels]]
[[File:Add value.png|thumb|A label where "Enable values" is turned on]]
If one wants to add a value to a new label when adding the new label to a resource, the "Enable values" options needs to be turned on when the label is created as described in [[Labels#Add labels to resources|Add labels to resources]]

When a resource has a label with a value associated, the value can be used to further filter the resources in the [[Tasks Tab|Tasks]] or [[Vehicles]] tab. See [[#Search by label values|Search by label values]]

== Labels in [[Vehicles]] ==
[[File:Labels add wcu6.png|thumb|150x150px|Labels in Vehicles Tab]]
Figure "Labels in Vehicles Tab" illustrates how the Vehicles tab looks like when we have searched out a resource associated with a label. A resource associated with a label as a small label icon before the "WCU ID" if the resource is a WCU or a resource group or before the "Plate number" if the resource is a car. When hovering the label icon, all associated labels on that resource pops up. The labels can be global labels added by other users, private labels added by the currently logged in user or system labels added by the system.

=== Add labels ===
Labels are added directly to a resource as described in section [[#Add labels to resources]].

=== Manage labels on resource ===
[[File:Labels add wcu7.png|thumb|150x150px|Edit WCU Dialog]]
Labels on a resource can be managed (add or remove labels) as described in [[#Add labels to resources]]. Alternatively, if only one resource is selected, the "Edit WCU" or "[[The Portal Administrator View#The Edit Car Dialog|Edit Car]]" button can be used for a WCU or Car, respectively. The Figure "Edit WCU Dialog" shows the "Edit WCU" dialog. To remove the label "wicewiki", simply click the label and it will disappear. The new state of the WCU is not saved until we click the button "Save". In this view we also have the option to add other labels exactly in the same way as we described in [[#Add labels to resources]].

=== Manage labels on multiple resources ===
From portal version 2.47 it is possible to manage labels on multiple resources at once.

To manage labels on multiple resources, search out the resources(in the Vehicles tab), right click and choose one of the options under "Manage labels" to either add or remove labels, as described in [[#Add labels to resources]]. This will give you the window in Figure "Add Label to Multiple Resources".

This can be done if the selected rows are resource groups or WCUs/Cars, not both. If one or more resource groups are selected it is possible to add the label to the WCUs and/or Cars in the group(s) and/or the resource group it self using the dialog checkboxes.

=== Search by labels ===
Above the regular search criteria filter editors there is a "Search by labels" widget as can be seen in Figure "Search by Labels". This widget let the user to include one or many labels in the search criteria which is further specified using the drop down menu with the three options "Match any", "Match all" and "Match none", where the foremost is the default choice.

<br clear="all">
[[File:Labels search.png|thumb|800px|left|Search by Labels]]
<br clear="all">

''Match any'' - Will show hits including resources which have any of the selected labels attached.

''Match all'' - Will show hits including resources with all of the selected labels attached.

''Match none'' - Will show hits including resources where the resources with the selected labels are excluded

Also note that in Figure "Search by Labels" there is a checkbox option: "Show all private labels". This is only available for administrators and enables the user to also retrieve private labels created by other users.

=== Search by label values ===
If a selected label has "Enable values" feature turned on (See [[Labels#Values for labels|Values for labels)]] the search criteria can be further narrowed by providing a value search criteria. A value search criteria is either added by simply typing the criteria or by selecting an available value via the drop down menu. When typing the criteria, regular expressions matching multiple values can also be used. See screenshot "Filter by value using regular expression".
[[File:Label value expression.png|thumb|Filter by value using regular expressions]]

=== Add label with values as a column ===
To ease filtering and use values for labels as a way to add dynamic attributes to resources (as mentioned in [[Labels#Values for labels|Values for labels)]] a label (with values enabled) can be added as resource type column to the Vehicles grid by right clicking the label. If the label has values enabled the context menu in the screenshot "Add as column" is displayed. If the label is added as a column, the column is added to the grid as seen in screenshot "Vehicle column".

This column can then be treated as any column in terms of filtering and sorting. When adding a label as a column, the column will be used to filter and show values for the selected resource type. In other words, if you add the column "Colour" as a vehicle column, the column will show the values for all vehicles that have the label "Colour" associated and have values selected for that label. The column will not show the values if the only WCU connected to the vehicle has the label "Colour" associated. These values are shown only if the label is added as a WCU column. The selected resource type is displayed via an icon as can be seen in the screenshot "Vehicle column".<gallery>
File:Add as column.png|Add as column
File:Vehicle colour column.png|Vehicle column
</gallery>

== Labels in [[Tasks Tab|Tasks]] ==
In the tasks tab it is possible to search for labels in the same way as described in [[#Search by labels]]. The difference for this tab compared to the Vehicles tab is that the labels associated with a resource, are the labels that were associated with the resource when the assignment was created.

=== Resource Labels for a Task ===
The Figure "Label Associated with WCU" shows the labels associated with the WCU "johan1" for task 7663. The only label is a [[#System label]] that was automatically added to the WCU when the task was created. This means that there were no other global or private labels associated with this WCU when task 7663 was created.

Illustration "System Label Associated with WCU" shows the labels associated with "johan1" for task 7664. In addition to the system label, we have the "wicewiki" label. This means that the WCU "johan1" had the label "wicewiki" when task 7664 was created.

<gallery widths="250px" mode="nolines">
File:Labels add wcu9.png|Label Associated with WCU
File:Labels add wcu10.png|System Label Associated with WCU
</gallery>

=== Assignment labels ===
[[File:Labels add wcu11.png|thumb|200px|right|Labels Added to Assignment]]

Labels can not be added to a assignment by a user but the system can add system labels to a assignment if the assignment is either running, pending or stopped pending. These labels are not visible for a result row in the same way as resource labels but are instead accessible if one selects a row and presses the button "View assignment". An example can be seen in Figure "Labels Added to Assignment". If the WCU software and/or MX4 firmware is changed while a assignment is either running, pending or stopped pending, a system label describing the change will be added to the assignment.

<br clear="all">

== Labels in [[Search Tab|Search]] ==
[[File:Labels add wcu12.png|thumb|200px|Search Tab Label Widget]]
The [[Search Tab|search tab]] has a new labels widget as can be seen in Figure "Search Tab Label Widge". This widget works in the same way as for the [[#Labels in Tasks|Tasks tab]]. When searching for labels in the [[Search Tab|search tab]] we are searching for labels in the same way as for the tasks tab, e.g labels that were associated with WCUs and/or cars when the tasks were created. If we include system labels in the label search criteria, we are also including assignment labels among the the resource types we are searching in.
<br clear="all">

== Administer labels ==
In the [[The Portal Administrator View#The Administration Tab]] there is a "Labels" tab where users can administrate their private labels and administrators can administrate all labels in the system. Here it is possible to search for labels either by label name, creator or status both in terms of global/private and enabled/disabled. The status based search is based on a checkbox which has three modes: unselected, checked or unchecked. The checked and unchecked option initiates a search matching the selected choice. However, the default setting is unselected, which is represented by a gray checkbox, and it shows hits disregarding its status.

=== Enable/disable labels ===
[[File:Labels add wcu13.png|thumb|200px|Enable/Disable Label]]
Labels can be enabled or disabled by checking/unchecking the checkbox in the "Enabled" column as can be seen in Figure "Enable/Disable Label". The changes are instant when checking the checkbox.

Disabled labels can not be added to resources and are not visible in the "Search by labels" widgets. They are however visible when when hovering a resource in the Tasks tab.

=== Rename label ===
[[File:Labels add wcu14.png|thumb|200px|Edit Label Dialog]]
A label can be renamed by clicking the label in the labels grid. An "Edit label" window will popup as can be seen in illustration "Edit Label Dialog". To rename the label, simply edit the text box and click save.

=== Enable Display name and Display description ===
A ''Display name'' can be added to the label which will be shown instead of the label name e.g. when a label is added as an attribute on a resource. In addition to this a ''Display description'' might be added too which can hold for example a clarification of the label's purpose. The description will show when hovering the label as in when hovering over a label added as an attribute on a resource.

=== Administrator specific features ===
As an administrator there are some more features in the labels administration tab.

==== Show all private labels ====
When checking the "Show all private labels" checkbox, all private labels in the system will be visible when searching. In this way, an administrator can edit other users private labels.

==== Turn private label global ====
When clicking a label (as described in [[#Rename label]]) an administrator can choose to turn a private label global. This has to be done with some care since it is not possible to turn a global label private again.
[[File:Screenshot from 2022-04-22 10-34-09.png|alt=Editing a label|thumb|Editing a label]]

==== Enable values for label ====
Values for an existing label can be added by checking "Enable values" in the "Edit Label Dialog". Note that when values has been enabled, this can not be disabled again.

==== Associate vehicle using this label ====
This feature is not available for all customers. If the vehicle identification type is set to 'Chassis NO' for the [[The Portal Administrator View#Configure the Vinreader Module|VINreader module]], this label will be used for the mechanism to automatically connect a WCU with a vehicle if checked. Only one label can have this checked. If you check this, the previously checked label will be unchecked. Also, the label must have values enabled.

=== Configure label announcements ===
If the feature is enabled at your site, it is possible to configure label announcements in the "Edit Label Dialog" as well as the "Create Label Dialog". It is also possible to search for labels via the columns "To be announced", "Only announce with values", and "Resource type".

==== To be announced ====
This checkbox determines whether a label is to be included in announcements.

==== Only announce with values ====
When a label has "Enable values" checked, this checkbox determines whether a label must have a value for it to be included in announcements.

==== Resource type ====
Set which resource type the label is to be associated with. The options are:

''Any -'' The label will to be included in the announcement if it is associated with either the WCU, the vehicle or both.

''WCU -'' The label will be included in the announcement if the label is associated with the WCU that is related to the announcement.

''Vehicle -'' The label will be included in the announcement if the label is associated with the vehicle that is related to the announcement.