Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.

{| class="wikitable"
!=
|Tests for equality. Syntax: expression = expression
|-
!!=
|Tests for inequality. Syntax: expression != expression
|-
!<
|Tests for left side of expression being less than right side. Syntax: expression < expression
|-
!>
|Tests for left side of expression being greater than right side. Syntax: expression > expression
|-
!<=
|Tests for left side of expression being less or equal to right side. Syntax: expression <= expression
|-
!>=
|Tests for left side of expression being greater or equal to right side. Syntax: expression >= expression
|-
!AND
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression
|-
!OR
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression
|-
!CHANGE
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)
|-
!CHANGE_UP
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)
|-
!CHANGE_DOWN
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)
|-
!CHANGE_FROM_TO
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)
|-
!CHANGE_BY
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)
|-
!CHANGE_UP_BY
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)
|-
!CHANGE_DOWN_BY
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)
|-
!CHANGE_FROM_TO
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)
|-
!TIMER
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)
|-
!EXPR_TIMER
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)
|-
!TIME_COUNTER
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)
|-
!SAMPLE_COUNTER
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)
|-
!EVERY
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)
|-
!MOVAV
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)
|-
!ABS
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)
|-
!MIN
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)
|-
!MAX
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)
|-
!MEAN
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)
|-
!LOSS_OF_SIGNAL
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)
|}

New features in v2.75

2022-04-19T06:19:15Z

Mathias:

== New way of handling diagnostic references for vehicle profiles ==
[[File:Edit-diag-ref-edit-mode.png|thumb|The dialog for editing diagnostic references - a new way to choose ECUs for a vehicle profile.]]
Before, one and only one diagnostic reference file (sddb-file) could be connected to a vehicle profile. This release introduces a new and more complex way of choosing which ECUs and software versions that are associated to a vehicle profile. It is possible to select single files like before, combine multiple files or manually add/remove single ECUs.

This functionality is reached through [[Vehicle Profiles|the Vehicle Profiles tab]] and how to manage it is described in the section [[Vehicle Profiles#Edit diagnostic reference - Manage active signals connected to the vehicle profile|Edit diagnostic reference]].

== New trigger expression for Loss of Signal ==
Signal Reader supports a new trigger expression intended for situations where a signals disappears after being present on a communication bus. The syntax is LOSS_OF_SIGNAL(SignalName, Seconds), which will become true when the named signal is gone for at least the specified number of seconds.

== Signal Reader support for J1939 DM1 messages ==
Signal Reader now supports reading and logging of J1939 DM1 messages.

== Support for alternative means of automatic connection of a vehicle to a WCU ==
Historically, WCUs have had the functionality of automatically telling the portal which vehicle it is in. This has been done by reading the vehicle's VIN number and reporting this to portal which then has made a connection between the two entities.

== The periodicity of Active Signals can be set in the Signal Reader Assignment Editor ==
The periodicity active signals can be set in the 'Modules' tab in the Signal Reader assignment editor. Click the 'Modules Settings' button to browse the Active Signals by ECU and view/edit the periodicity.

== Support for M-Log firmware updates ==
The firmware of an M-Log unit can be updated by selecting the desired firmware version in the M-Log module settings.

New features in v2.75

2022-04-19T06:17:04Z

Mathias:

Signal Reader Trigger Expressions

2022-04-14T06:48:16Z

Mathias:

Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.

{| class="wikitable"
!=
|Tests for equality. Syntax: expression = expression
|-
!!=
|Tests for inequality. Syntax: expression != expression
|-
!<
|Tests for left side of expression being less than right side. Syntax: expression < expression
|-
!>
|Tests for left side of expression being greater than right side. Syntax: expression > expression
|-
!<=
|Tests for left side of expression being less or equal to right side. Syntax: expression <= expression
|-
!>=
|Tests for left side of expression being greater or equal to right side. Syntax: expression >= expression
|-
!AND
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression
|-
!OR
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression
|-
!CHANGE
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)
|-
!CHANGE_UP
|True when the specified signal increases its value with the specified amount. Syntax: CHANGE_UP(Signal, amount)
|-
!CHANGE_DOWN
|True when the specified signal increases its value with the specified amount. Syntax: CHANGE_DOWN(Signal, amount)
|-
!CHANGE_FROM_TO
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)
|-
!TIMER
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal,time)
|-
!EXPR_TIMER
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression,time)
|-
!TIME_COUNTER
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)
|-
!SAMPLE_COUNTER
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)
|-
!EVERY
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)
|-
!MOVAV
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)
|-
!ABS
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)
|-
!MIN
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)
|-
!MAX
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)
|-
!MEAN
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)
|-
!LOSS_OF_SIGNAL
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)
|}

2022-03-18T07:03:09Z

Mathias:

2022-01-21T07:11:26Z

Mathias: /* SoH */

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

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]. Currently this task type supports filtering of logs on the WCU by entering filter expressions into the text area "Filters", one on each line. For an explanation on how to write such filters, see [https://github.com/GENIVI/dlt-daemon#learn-more here]. For a description of the settings of the module DLT, see [[DLT Module|here]].

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

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

Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the MLOG - no upload will be required (Available from WCU version 2.66).
[[File:Mlog-20210216-160132.png|thumb|M-Log task]]

== 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 similat to the Singnal Reader module. A SoftHub task is created much in the same way as a Signal Reader task.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== SWDL ==
[[File: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.

Labels

2022-01-18T08:23:00Z

Mathias: /* Add labels to resources */

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.

 
[[File:Labels search.png|thumb|800px|left|Search by Labels]]
 

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

 

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

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

=== 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:Enabled values.png|thumb|Enable values for existing labels]]

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

Labels

2022-01-18T08:22:22Z

Mathias: /* Add labels to resources */

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

 
[[File:Labels search.png|thumb|800px|left|Search by Labels]]
 

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

 

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

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

=== 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:Enabled values.png|thumb|Enable values for existing labels]]

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