WICE Wiki v2.95 - User contributions [en]

Creating a Task

2020-02-27T12:23:52Z

Julian: /* SWDL */

<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 assignment you want to create. Note that it is not possible to create a new task for a WCU which have the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU have 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 assignments available (Canrecorder, IDC, SoH, Signal Reader, SWDL, Video, MQTT, ETAS, SoftHub and blue piraT).

=== CAN-recorder ===
[[File:CanrecorderIllust.png|thumb|Canrecorder]]

Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment 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.

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

=== SoH ===
[[File:Illustration SoH.png|thumb|271x271px|SoH]]
A State of Health (SoH) assignment collects specific status information from vehicles. You select which information you want the assignment to collect by filling in one or more of the six boxes shown in Figure "SoH tab". In order for SoH data to be correctly interpreted, relevant description files (SDDB/GDS) for the vehicles executing the SoH assignment must have been defined. To add a SDDB/GDS file to 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
*Read OBD-II PIDs
*App Diagnotstic Db Part Num

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

=== Signal Reader ===
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader assignment]]
Signal Reader is a measurement module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data. To create a Signal Reader assignment 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 assignment 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 assignment 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]].

Signal Reader can act as a Signal Broker for other software components. Read more about this in [[WICE Signal Broker API]].
This task can also be scheduled in the same manner as described for the Canrecoder task.

==== 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 assignment. 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 queries in the sequence file are of functional type, i.e. posed to all ECUs, and in such cases you can select the option of using ''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 queries. 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 are also available. The following WICE-internal signals are supported:
{| class="wikitable"
!'''Signal name'''
!Description
|-
|Audio_Device_1
|The status of audio device 1 (1=recording, 0 = not recording). When present in a recorder, the audio module will record sound from the device.
|-
|Audio_Device_2
|The status of audio device 2 (1=recording, 0 = not recording). When present in a recorder, the audio module will record sound from the device.
|-
|Busload_CAN_<n>
|The bus load on CAN bus <n>
|-
|CSQ
|The built-in modem's CSQ value (Signal Quality)
|-
|Date Year
|The year of the current date.
|-
|Date Month
|The month (1-12) of the current date.
|-
|Date Day
|The day of the month (1-31) of the current date.
|-
|Date Weekday
|The day of the week (1-7, where 1 is Sunday).
|-
|Date Hour
|The hour of the day (0-23).
|-
|Date Minute
|The minute of the hour (0-59).
|-
|Date Second
|The second of the minute (0-59).
|-
|Dynamic_<n>
|Special signals with values assignable from external software components (typically used for Rapid Prototyping).
|-
|IO__AI_<n>
|Analog input number <n>
|-
|IO__DI_<n>
|Digital input number <n>
|-
|IO__DO_<n>
|Digital output number <n>
|-
|Log_All_Frames_CAN_<n>
|Log all CAN frames on CAN bus <n>
|-
|Log_All_Frames_FlexRay_<n>
|Log all CAN frames on Flexray bus <n>
|-
|Latitude
|The GPS latitude
|-
|Longitude
|The GPS longitude
|-
|Power_Mode
|The power mode of the WCU
|-
|Random
|A random number generator
|-
|Random_Start
|A random number generator updated once, at program start
|-
|Random_Setup_Switch
|A random number generator updated at each measurement set-up switch
|-
|Start_Signal
|The start signal of the WCU
|-
|Speed
|The GPS speed
|-
|Start_Switch
|The start switch of the WCU
|-
|Tester Present
|When present in a measurement set-up, Tester Present will be sent periodically.
|-
|Time Since Epoch
|The time elapsed since the epoch (Jan 1, 1970, 00:00)
|-
|Time Since Start
|The time elapsed since the start of the assignment
|-
|Time Since Setup Switch
|The time elapsed since the activation of the current measurement set-up
|-
|Trigger_Button
|The trigger button connected to the WCU
|-
|Usage_CPU
|The WCU CPU usage in percent
|-
|Usage_Memory
|The WCU memory usage in percent
|-
|Video_Camera_1
|The status of video camera 1 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.
|-
|Video_Camera_2
|The status of video camera 2 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.
|-
|WCU_Battery
|The WCU battery voltage in millivolts
|-
|WCU_Temp
|The WCU internal temperature in degrees Celsius
|-
|WCU_Voltage
|The WCU WCU voltage in millivolts
|}
 

=== SWDL ===
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. As of WCU version 2.57 it is also possible to include sequence files that are to be executed before or after the SWDL process.

The SWDL module can be configured to perform SWDL either over CAN or over Ethernet (DoIP).

=== 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 assignment description file you select must be a .exp 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 assignment file, and then proceed in the same way as the Signal Reader task.

The SoftHub assignment 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]].

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

=== 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 using either a trigger button or a recorder start event from Signal Reader. You can also let the video recording start as soon as the WCUs has started. 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]].

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

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

=== Audio ===
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in three ways:
* '''Trigger button''': to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.
* '''None''': start the recording as soon as possible.
* '''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.
* '''Audio level''': Start the trigger once the microphone registers volume above a certain threshold.
In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button and signal reader 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.

The duration of the recording can also be set, in seconds from the trigger event. If you do not enter a duration it will be set to a default value of 120 seconds.
[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]
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]. You have more information [[Wice audio|here]].This task can be scheduled in the same manner as described for the Canrecoder task.

New features in v2.57

2020-02-27T09:12:52Z

Julian: /* Audio level trigger for Audio assignments */

== Preview individual drive cycles in Plot Route ==
You are now able to preview individual drive cycles with ease in [[Plot Route|the "Plot route"-tool]]. All drive cycles for the currently searched out interval are listed, and can be selected to be previewed individually.

== No longer possible to add new tasks for WCUs which are shelved or have shelving in progress ==
As of this version it is no longer possible to add new tasks to a WCU with the system labels ''shelving_in_progress'' or ''shelving_done''. If such a WCU is selected it is marked red in the selected WCU's table. However, if the latter label is present it is possible to unshelve the WCU using the corresponding button in the bottom panel of the Vehicle-tab. Read more about shelving [[Shelve and Unshelve a WCU|here]].

== New module settings added for Signal Reader ==
For WCUs of version >=2.57 it is possible to set whether or not the MDF-files are to be written upon recorder stop, whether or not 22 service requests are to be aggregated and the default OBD-II period in ms. More information is found [[The Portal Administrator View#Configure the Signal Reader Module|here]].

== Add comment to acknowledged alarms ==

As of this version it is possible to add comments to acknowledged alarms. Read more about this feature [[Alarm#Acknowledge alarm|here]].

== SWDL pre and post sequence files ==
You are now able to add sequence files to run through IDC before and after your SWDL-assignment. This also requires that the targetted WCU has at least version 2.57. More information can be found [[Creating a Task#SWDL|here]].

== Audio level trigger for Audio assignments ==
Triggering on audio level is now available for Audio assignments targetting 2.57 (or later) WCUs. More information can be found [[Creating a Task#Audio|here]].

Creating a Task

2020-02-27T09:11:25Z

Julian: /* Audio */ Audio level

<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 assignment you want to create. Note that it is not possible to create a new task for a WCU which have the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU have 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 assignments available (Canrecorder, IDC, SoH, Signal Reader, SWDL, Video, MQTT, ETAS, SoftHub and blue piraT).

=== CAN-recorder ===
[[File:CanrecorderIllust.png|thumb|Canrecorder]]

Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment 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.

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

=== SoH ===
[[File:Illustration SoH.png|thumb|271x271px|SoH]]
A State of Health (SoH) assignment collects specific status information from vehicles. You select which information you want the assignment to collect by filling in one or more of the six boxes shown in Figure "SoH tab". In order for SoH data to be correctly interpreted, relevant description files (SDDB/GDS) for the vehicles executing the SoH assignment must have been defined. To add a SDDB/GDS file to 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
*Read OBD-II PIDs
*App Diagnotstic Db Part Num

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

=== Signal Reader ===
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader assignment]]
Signal Reader is a measurement module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data. To create a Signal Reader assignment 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 assignment 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 assignment 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]].

Signal Reader can act as a Signal Broker for other software components. Read more about this in [[WICE Signal Broker API]].
This task can also be scheduled in the same manner as described for the Canrecoder task.

==== 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 assignment. 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 queries in the sequence file are of functional type, i.e. posed to all ECUs, and in such cases you can select the option of using ''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 queries. 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 are also available. The following WICE-internal signals are supported:
{| class="wikitable"
!'''Signal name'''
!Description
|-
|Audio_Device_1
|The status of audio device 1 (1=recording, 0 = not recording). When present in a recorder, the audio module will record sound from the device.
|-
|Audio_Device_2
|The status of audio device 2 (1=recording, 0 = not recording). When present in a recorder, the audio module will record sound from the device.
|-
|Busload_CAN_<n>
|The bus load on CAN bus <n>
|-
|CSQ
|The built-in modem's CSQ value (Signal Quality)
|-
|Date Year
|The year of the current date.
|-
|Date Month
|The month (1-12) of the current date.
|-
|Date Day
|The day of the month (1-31) of the current date.
|-
|Date Weekday
|The day of the week (1-7, where 1 is Sunday).
|-
|Date Hour
|The hour of the day (0-23).
|-
|Date Minute
|The minute of the hour (0-59).
|-
|Date Second
|The second of the minute (0-59).
|-
|Dynamic_<n>
|Special signals with values assignable from external software components (typically used for Rapid Prototyping).
|-
|IO__AI_<n>
|Analog input number <n>
|-
|IO__DI_<n>
|Digital input number <n>
|-
|IO__DO_<n>
|Digital output number <n>
|-
|Log_All_Frames_CAN_<n>
|Log all CAN frames on CAN bus <n>
|-
|Log_All_Frames_FlexRay_<n>
|Log all CAN frames on Flexray bus <n>
|-
|Latitude
|The GPS latitude
|-
|Longitude
|The GPS longitude
|-
|Power_Mode
|The power mode of the WCU
|-
|Random
|A random number generator
|-
|Random_Start
|A random number generator updated once, at program start
|-
|Random_Setup_Switch
|A random number generator updated at each measurement set-up switch
|-
|Start_Signal
|The start signal of the WCU
|-
|Speed
|The GPS speed
|-
|Start_Switch
|The start switch of the WCU
|-
|Tester Present
|When present in a measurement set-up, Tester Present will be sent periodically.
|-
|Time Since Epoch
|The time elapsed since the epoch (Jan 1, 1970, 00:00)
|-
|Time Since Start
|The time elapsed since the start of the assignment
|-
|Time Since Setup Switch
|The time elapsed since the activation of the current measurement set-up
|-
|Trigger_Button
|The trigger button connected to the WCU
|-
|Usage_CPU
|The WCU CPU usage in percent
|-
|Usage_Memory
|The WCU memory usage in percent
|-
|Video_Camera_1
|The status of video camera 1 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.
|-
|Video_Camera_2
|The status of video camera 2 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.
|-
|WCU_Battery
|The WCU battery voltage in millivolts
|-
|WCU_Temp
|The WCU internal temperature in degrees Celsius
|-
|WCU_Voltage
|The WCU WCU voltage in millivolts
|}
 

=== SWDL ===
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 SWDL module can be configured to perform SWDL either over CAN or over Ethernet (DoIP).

=== 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 assignment description file you select must be a .exp 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 assignment file, and then proceed in the same way as the Signal Reader task.

The SoftHub assignment 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]].

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

=== 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 using either a trigger button or a recorder start event from Signal Reader. You can also let the video recording start as soon as the WCUs has started. 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]].

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

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

=== Audio ===
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in three ways:
* '''Trigger button''': to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.
* '''None''': start the recording as soon as possible.
* '''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.
* '''Audio level''': Start the trigger once the microphone registers volume above a certain threshold.
In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button and signal reader 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.

The duration of the recording can also be set, in seconds from the trigger event. If you do not enter a duration it will be set to a default value of 120 seconds.
[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]
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]. You have more information [[Wice audio|here]].This task can be scheduled in the same manner as described for the Canrecoder task.

New features in v2.57

2020-02-27T08:32:18Z

Julian:

== Preview individual drive cycles in Plot Route ==
You are now able to preview individual drive cycles with ease in [[Plot Route|the "Plot route"-tool]]. All drive cycles for the currently searched out interval are listed, and can be selected to be previewed individually.

== No longer possible to add new tasks for WCUs which are shelved or have shelving in progress ==
As of this version it is no longer possible to add new tasks to a WCU with the system labels ''shelving_in_progress'' or ''shelving_done''. If such a WCU is selected it is marked red in the selected WCU's table. However, if the latter label is present it is possible to unshelve the WCU using the corresponding button in the bottom panel of the Vehicle-tab. Read more about shelving [[Shelve and Unshelve a WCU|here]].

== New module settings added for Signal Reader ==
For WCUs of version >=2.57 it is possible to set whether or not the MDF-files are to be written upon recorder stop, whether or not 22 service requests are to be aggregated and the default OBD-II period in ms. More information is found [[The Portal Administrator View#Configure the Signal Reader Module|here]].

== Add comment to acknowledged alarms ==

As of this version it is possible to add comments to acknowledged alarms. Read more about this feature [[Alarm#Acknowledge alarm|here]].

== SWDL pre and post sequence files ==
You are now able to add sequence files to run through IDC before and after your SWDL-assignment. This also requires that the targetted WCU has at least version 2.57.

== Audio level trigger for Audio assignments ==
Triggering on audio level is now available for Audio assignments targetting 2.57 (or later) WCUs.

New features in v2.57

2020-02-04T13:56:29Z

Julian:

Plot Route

2020-02-04T12:34:26Z

Julian: Added generic information about plot route, and an image of a measurement

[[File:Plot-route-measure.png|thumb|Signal reader measurement visible in the map. Can be clicked to review the data available from that measurement.]]
Plot route is a tool that enables plotting the GPS-coordinates of a resource from a specific time interval. Additionally, signal reader measurements are marked out on the map where they occurred. The user can click on these markers to immediately access the [[Preview data|Preview data tool]] where the clicked measurement can be examined in detail.

==How to access this tool==
If you are interested in seeing where the car was driven while making measurements you can use the “Plot route” tool. This tool can be accessed either by selecting and then right-clicking a task in the tasks panel. You can also access the tool from the bottom menu in both the tasks and vehicles panel.

== How it works ==
An important detail to note is that plot route is a tool that operates using the data of a specific car. The tool will check which car you have selected. It will then aggregate the GPS-data of all the WCUs that has been installed in the car during the specified time period. This is the data that is plotted.

== Sidebar controls ==
[[File:Plot-route-20200204.png|frame|Plot route controls]]
On the right sight of the screen there is a set of controls available to the user to navigate through the route data available for the selected resource.

=== Car information ===
The "Car Information" panel displays the plate number, VIN and when the latest known GPS update occurred for the selected resource.

=== Set date interval ===
The "Set date interval"-form can be used to select an interval within which you wish you know where the resource has been. '''This interval has a maximum length of one month''', and is by default set to the last known GPS update date. If you wish to change the interval, simply enter the date interval of your choice and click "update map".

=== Controls ===
If you are having any trouble locating the data in the map you can utilize the "'''Fit all'''"-button. This button ensures that all position data is visible on the map by zooming out and panning to an appropriate location.

Also in the controls panel is the option to hide/show measurement markers.

=== Drive cycle list ===
The drive cycle list provides a way to preview individual drive cycles. By '''clicking on a row''' in the list all drive cycles on the map are hidden except for the one that is selected. Additionally it is possible to '''double click on a row''' which not only displays the selected drive cycle, but also pans the map view and zooms in so that the drive cycle can be seen clearly. If at any point you wish to see all drive cycles in the view again you can click the "'''Show all drive cycles'''"-button, which will return the map to its initial state.

== Visualization of drive cycles and signal reader measurements ==

=== Drive cycles ===
If the plot route tool detects that there was a significant time difference between two reported positions, then it will assume that they are part of different "drive cycles". This is visualized in the map by giving different drive cycles different colors. However, after a certain threshold too many drive cycles will result in the colors repeating, thus giving some data series the same color.

=== Signal reader measurements ===
Measurements are visualized on the map using markers. These markers are positioned where the measurement started. You can click the measurement markers to jump straight to the [[Preview data|preview tool]] where you can preview signal data from that specific measurement.

File:Plot-route-measure.png

2020-02-04T12:33:07Z

Julian:

Assignment measurement plotted in the plot route tool.

Plot Route

2020-02-04T12:28:34Z

Julian: Drive cycle information added

==How to access this tool==
If you are interested in seeing where the car was driven while making measurements you can use the “Plot route” tool. This tool can be accessed either by selecting and then right-clicking a task in the tasks panel. You can also access the tool from the bottom menu in both the tasks and vehicles panel.

== How it works ==
An important detail to note is that plot route is a tool that operates using the data of a specific car. The tool will check which car you have selected. It will then aggregate the GPS-data of all the WCUs that has been installed in the car during the specified time period. This is the data that is plotted.

== Sidebar controls ==
[[File:Plot-route-20200204.png|frame|Plot route controls]]
On the right sight of the screen there is a set of controls available to the user to navigate through the route data available for the selected resource.

=== Car information ===
The "Car Information" panel displays the plate number, VIN and when the latest known GPS update occurred for the selected resource.

=== Set date interval ===
The "Set date interval"-form can be used to select an interval within which you wish you know where the resource has been. '''This interval has a maximum length of one month''', and is by default set to the last known GPS update date. If you wish to change the interval, simply enter the date interval of your choice and click "update map".

=== Controls ===
If you are having any trouble locating the data in the map you can utilize the "'''Fit all'''"-button. This button ensures that all position data is visible on the map by zooming out and panning to an appropriate location.

Also in the controls panel is the option to hide/show measurement markers.

=== Drive cycle list ===
The drive cycle list provides a way to preview individual drive cycles. By '''clicking on a row''' in the list all drive cycles on the map are hidden except for the one that is selected. Additionally it is possible to '''double click on a row''' which not only displays the selected drive cycle, but also pans the map view and zooms in so that the drive cycle can be seen clearly. If at any point you wish to see all drive cycles in the view again you can click the "'''Show all drive cycles'''"-button, which will return the map to its initial state.

== Visualization of drive cycles and signal reader measurements ==

=== Drive cycles ===
If the plot route tool detects that there was a significant time difference between two reported positions, then it will assume that they are part of different "drive cycles". This is visualized in the map by giving different drive cycles different colors. However, after a certain threshold too many drive cycles will result in the colors repeating, thus giving some data series the same color.

=== Signal reader measurements ===
Measurements are visualized on the map using markers. These markers are positioned where the measurement started. You can click the measurement markers to jump straight to the [[Preview data|preview tool]] where you can preview signal data from that specific measurement.

File:Plot-route-20200204.png

2020-02-04T12:08:00Z

Julian:

Plot route with populated drive cyle list

Alarm

2020-02-03T12:29:25Z

Julian: Edited poor choice of words

<includeonly>=== The Alarm Tab===</includeonly>
Alarms assists in keeping track of the health and status of individual WCUs. Alarms are created for individual WCUs if certain conditions are met. Typically these conditions are indicators that suggest that a resource has encountered a problem, or has entered a state that could potentially be problematic or harmful. When an alarm is registered it shows up in the WICE portal under the Administration/Alarms tab. Using the Alarm panel a user can get an overview of any WCUs that requires attention in the form of a list. By default, the alarms from the last 24 hours are kept in the list. The list is updated automatically with new alarms once every 10 minutes. Alarms already on the list are not removed, hence, over time there will be alarms from over 24 hours ago. A figure of the alarm panel is on the right. An alarm consists of five components: a '''resource identifier''', a '''time''', a '''message''', a '''severity''' and a '''category'''.
[[File:The alarm panel.png|thumb|A set of alarms in the alarm tab.]]A '''resource identifier''' can basically take any form, it is a string that identifies the source of the alarm. In the case to the right there are three distinct WCU resources with id ''wcu::04-1B-94-00-20-8C'', ''wcu::00-09-D8-02-B7-4A'' and ''wcu::04-1B-94-00-20-76''.

'''Time''' is simply at what time the alarm was triggered.

A '''message''' is a textual description of what happened. In this case it was because certificates are about to expire. The message looks as follows: 'Certificate expires on 20181019-184056 +02:00'.

'''Severity''' is a way to communicate the urgency of the alarm. Severity is currently divided into two types, ''Error'' and ''Warning''. Error implies that something unexpected has happened which requires attention. Warning implies that a resource has entered a state that could potentially (but not necessarily) be harmful.

'''Category''' is a way to categorize an alarm. This is particularly useful for searching.

The '''remark''' column tells what has happened with the alarm. If it is empty, the alarm has simply been raised. If there are letter present the are either an <big>A</big>, which means acknowledged, or a <big>G</big> which means that the alarm situation has been resolved either as a consequence of the acknowledgement or automatically. An example of where it has automatically been resolved is the case where the SD card in the WCU has reached, let us say, an 85% usage degree and later when data is uploaded the usage degree drops below 80%. By hovering over the remark column you will be presented with the date and user of when an alarm was acknowledged and with a date if it was automatically closed.

At the top is a set of controls to filter alarms based on other criteria than the text in the columns. First out we have the checkbox "'''Use fetch interval'''". Checking this box enables the two items "'''Time unit'''" and "'''Time interval'''". This makes it possible to fetch alarms from more than 24 hours back. Its default setting is conveniently 24 hours. The '''time unit''' says how the number should be interpreted, e.g. changing the '''time unit''' to Days while leaving the '''time interval''' at 24 will mean to fetch alarms from 24 days back. Available '''time units''' are '''hours''', '''days''' and '''months'''. Also, you choose to include closed alarm by checking the box "'''Include closed alarms'''" and/or including acknowledged alarms by checking "'''Include acknowledged alarms'''". It is only when either or both of these check boxes are checked that the remark column is populated.

== Functions ==
There are a few functions in this panel. You can '''update''' an alarm list, '''reload''' the alarm list, '''acknowledge''' an alarm and '''search''' among the alarms in the table.

=== Update alarm list ===
A said earlier, the list is automatically updated every 10 minutes. But if you feel like not waiting, simply press the 'Update alarms' button. This will fetch new alarms from the server.

=== Reload alarm list ===
By pressing 'Reload alarms' button you will clear the current set of alarms and fetch a new set from the last 24 hours. Usually this is not needed but it is here for your convenience. The button needs to be pressed if you use and change the fetch interval.

=== Acknowledge alarm ===
When alarm is 'taken care of' you can acknowledge this by pressing the button 'Acknowledge alarm'. This will make the alarm be marked as 'acknowledged'.

=== Search alarm ===
[[File:Alarm list filtered on resource.png|thumb|Alarm list filtered on resource '20']]
Over time, many alarms will accumulate and the list will be rather long. In order to find alarms of a specific category or for a specific resource, you can enter text in some of the filter column entries to filter the list. If you enter text in more than one of the filter entries an and-operation is used to filter the list. As an example see the figure to the right where a filter for WCUs having '20' in their id has been filtered for. As you can see, there are two WCUs that match this filter expression. No regular expression can be used here, it is a simple text search.

=== Alarm fetch interval ===
At the top is a set of controls to filter alarms based on other criteria than the text in the columns. First out we have the checkbox "'''Use fetch interval'''". Checking this box enables the two items "'''Time unit'''" and "'''Time interval'''". This makes it possible to fetch alarms from more than 24 hours back. Its default setting is conveniently 24 hours. The '''time unit''' says how the number should be interpreted, e.g. changing the '''time unit''' to Days while leaving the '''time interval''' at 24 will mean to fetch alarms from 24 days back. Available '''time units''' are '''hours''', '''days''' and '''months'''. Also, you choose to include closed alarm by checking the box "'''Include closed alarms'''" and/or including acknowledged alarms by checking "'''Include acknowledged alarms'''". It is only when either or both of these check boxes are checked that the remark column is populated.

== Available alarms ==
Presented below is the set of alarms currently available.

=== Certificate expires ===
This alarm is identified with '''wcu::info::cert::expire''<nowiki/>'. Currently, alarms start to appear from 30 days of certificate expiry date. The alarm is triggered at most once per 24 hours.

=== Certificate not present ===
This alarm is identified with '''wcu::info::cert::not_present''<nowiki/>'. It means there is no certificate at all on the WCU. The alarm is automatically closed when the WCU reports that there is a certificate installed on the WCU. It is triggered at most once per 24 hours.

=== Certificate password missing ===
The alarm is identified with '''wcu::info::cert::password::missing''<nowiki/>'. There is a certificate on the WCU and the private key is encrypted but there is no password supplied to decrypt it with. As soon as correct a password is supplied this alarm will be automatically closed.

=== Certificate unlock failed ===
The alarm is identified with '''wcu::info::cert::unlock::failed''<nowiki/>'. The most common problem to this alarm is that the wrong password has been supplied to decrypt the private key. As soon as correct a password is supplied this alarm will be automatically closed.

=== Sdcard usage ===
The alarm is identified with '''wcu::info::sdcard::use_percent''<nowiki/>'. An alarm is raised, currently, when the usage percentage of the SD card on the WCU is 80% or more. Alarms for this are triggered at most once every 24 hours. If the usage percentage is 95% or more, an alarm can be triggered up to once every 10 minutes. Once the usage percentage drops below 80% alarms are automatically closed.

=== Switch in INT position ===
The alarm is identified with '''wcu::info::start_switch::int''<nowiki/>'. An alarm is raised when the WCU reports that the switch is in the int position. It is automatically closed when the WCU reports that the switch is in position ext.

Alarm

2020-02-03T12:22:47Z

Julian: Clarified confusing introduction to Alarms a bit.

<includeonly>=== The Alarm Tab===</includeonly>
Alarms assists in keeping track of the health and status of individual WCUs. Alarms are created for individual WCUs if certain conditions are met. Typically these conditions are indicators that suggest that a resource has encountered a problem, or has entered a state that could potentially be problematic or harmful. When an alarm is registered it shows up in the WICE portal under the Administration/Alarms tab. Using the Alarm panel a user can get an overview of any WCUs that requires attention in the form of a list. By default, the alarms from the last 24 hours are kept in the list. The list is updated automatically with new alarms once every 10 minutes. Alarms already on the list are not removed, hence, over time there will be alarms from over 24 hours ago. A figure of the alarm panel is on the right. An alarm consists of five components: a '''resource identifier''', a '''time''', a '''message''', a '''severity''' and a '''category'''.
[[File:The alarm panel.png|thumb|A set of alarms in the alarm tab.]]A '''resource identifier''' can basically take any form, it is a string that identifies the source of the alarm. In the case to the right there are three distinct WCU resources with id ''wcu::04-1B-94-00-20-8C'', ''wcu::00-09-D8-02-B7-4A'' and ''wcu::04-1B-94-00-20-76''.

'''Time''' is simply at what time the alarm was triggered.

A '''message''' is a textual description of what happened. In this case it was because certificates are about to expire. The message looks as follows: 'Certificate expires on 20181019-184056 +02:00'.

'''Severity''' is a way to communicate the urgency of the alarm. Severity is currently divided into two categories, ''Error'' and ''Warning''. Error implies that something unexpected has happened which requires attention. Warning implies that a resource has entered a state that could potentially (but not necessarily) be harmful.

'''Category''' is a way to categorize an alarm. This is particularly useful for searching.

The '''remark''' column tells what has happened with the alarm. If it is empty, the alarm has simply been raised. If there are letter present the are either an <big>A</big>, which means acknowledged, or a <big>G</big> which means that the alarm situation has been resolved either as a consequence of the acknowledgement or automatically. An example of where it has automatically been resolved is the case where the SD card in the WCU has reached, let us say, an 85% usage degree and later when data is uploaded the usage degree drops below 80%. By hovering over the remark column you will be presented with the date and user of when an alarm was acknowledged and with a date if it was automatically closed.

At the top is a set of controls to filter alarms based on other criteria than the text in the columns. First out we have the checkbox "'''Use fetch interval'''". Checking this box enables the two items "'''Time unit'''" and "'''Time interval'''". This makes it possible to fetch alarms from more than 24 hours back. Its default setting is conveniently 24 hours. The '''time unit''' says how the number should be interpreted, e.g. changing the '''time unit''' to Days while leaving the '''time interval''' at 24 will mean to fetch alarms from 24 days back. Available '''time units''' are '''hours''', '''days''' and '''months'''. Also, you choose to include closed alarm by checking the box "'''Include closed alarms'''" and/or including acknowledged alarms by checking "'''Include acknowledged alarms'''". It is only when either or both of these check boxes are checked that the remark column is populated.

== Functions ==
There are a few functions in this panel. You can '''update''' an alarm list, '''reload''' the alarm list, '''acknowledge''' an alarm and '''search''' among the alarms in the table.

=== Update alarm list ===
A said earlier, the list is automatically updated every 10 minutes. But if you feel like not waiting, simply press the 'Update alarms' button. This will fetch new alarms from the server.

=== Reload alarm list ===
By pressing 'Reload alarms' button you will clear the current set of alarms and fetch a new set from the last 24 hours. Usually this is not needed but it is here for your convenience. The button needs to be pressed if you use and change the fetch interval.

=== Acknowledge alarm ===
When alarm is 'taken care of' you can acknowledge this by pressing the button 'Acknowledge alarm'. This will make the alarm be marked as 'acknowledged'.

=== Search alarm ===
[[File:Alarm list filtered on resource.png|thumb|Alarm list filtered on resource '20']]
Over time, many alarms will accumulate and the list will be rather long. In order to find alarms of a specific category or for a specific resource, you can enter text in some of the filter column entries to filter the list. If you enter text in more than one of the filter entries an and-operation is used to filter the list. As an example see the figure to the right where a filter for WCUs having '20' in their id has been filtered for. As you can see, there are two WCUs that match this filter expression. No regular expression can be used here, it is a simple text search.

=== Alarm fetch interval ===
At the top is a set of controls to filter alarms based on other criteria than the text in the columns. First out we have the checkbox "'''Use fetch interval'''". Checking this box enables the two items "'''Time unit'''" and "'''Time interval'''". This makes it possible to fetch alarms from more than 24 hours back. Its default setting is conveniently 24 hours. The '''time unit''' says how the number should be interpreted, e.g. changing the '''time unit''' to Days while leaving the '''time interval''' at 24 will mean to fetch alarms from 24 days back. Available '''time units''' are '''hours''', '''days''' and '''months'''. Also, you choose to include closed alarm by checking the box "'''Include closed alarms'''" and/or including acknowledged alarms by checking "'''Include acknowledged alarms'''". It is only when either or both of these check boxes are checked that the remark column is populated.

== Available alarms ==
Presented below is the set of alarms currently available.

=== Certificate expires ===
This alarm is identified with '''wcu::info::cert::expire''<nowiki/>'. Currently, alarms start to appear from 30 days of certificate expiry date. The alarm is triggered at most once per 24 hours.

=== Certificate not present ===
This alarm is identified with '''wcu::info::cert::not_present''<nowiki/>'. It means there is no certificate at all on the WCU. The alarm is automatically closed when the WCU reports that there is a certificate installed on the WCU. It is triggered at most once per 24 hours.

=== Certificate password missing ===
The alarm is identified with '''wcu::info::cert::password::missing''<nowiki/>'. There is a certificate on the WCU and the private key is encrypted but there is no password supplied to decrypt it with. As soon as correct a password is supplied this alarm will be automatically closed.

=== Certificate unlock failed ===
The alarm is identified with '''wcu::info::cert::unlock::failed''<nowiki/>'. The most common problem to this alarm is that the wrong password has been supplied to decrypt the private key. As soon as correct a password is supplied this alarm will be automatically closed.

=== Sdcard usage ===
The alarm is identified with '''wcu::info::sdcard::use_percent''<nowiki/>'. An alarm is raised, currently, when the usage percentage of the SD card on the WCU is 80% or more. Alarms for this are triggered at most once every 24 hours. If the usage percentage is 95% or more, an alarm can be triggered up to once every 10 minutes. Once the usage percentage drops below 80% alarms are automatically closed.

=== Switch in INT position ===
The alarm is identified with '''wcu::info::start_switch::int''<nowiki/>'. An alarm is raised when the WCU reports that the switch is in the int position. It is automatically closed when the WCU reports that the switch is in position ext.

Alarm

2020-02-03T12:08:34Z

Julian: Added a definition of warnings and errors

<includeonly>=== The Alarm Tab===</includeonly>
There is a lot going on in the system with WCUs uploading data and many there are thousands of WCUs doing all sorts of things. Keeping track if all this is a tough job and this is where the alarms are at your disposal. This view is meant to collect all relevant information regarding the status of individual WCUs. Of course, it can keep status of more than WCUs but at this very moment that is what is there.
[[File:The alarm panel.png|thumb|A set of alarms in the alarm tab.]]
As default, the alarms from the last 24 hours are kept in the list. The list is updated automatically with new alarms once every 10 minutes. Alarms already on the list are not removed, hence, over time there will be alarms from over 24 hours ago. A figure of the alarm panel is on the right. An alarm consists of five parts, a '''resource identifier''', a '''time''', a '''message''', a '''severity''' and a '''category'''.

A '''resource identifier''' can basically take any form, it is a string that identifies the source of the alarm. In the case to the right there are three distinct WCU resources with id ''wcu::04-1B-94-00-20-8C'', ''wcu::00-09-D8-02-B7-4A'' and ''wcu::04-1B-94-00-20-76''.

'''Time''' is simply at what time the alarm was triggered.

A '''message''' is a textual description of what happened. In this case it was because certificates are about to expire. The message looks as follows: 'Certificate expires on 20181019-184056 +02:00'.

'''Severity''' is a way to communicate the urgency of the alarm. Severity is currently divided into two categories, ''Error'' and ''Warning''. Error implies that something unexpected has happened which requires attention. Warning implies that a resource has entered a state that could potentially (but not necessarily) be harmful.

'''Category''' is a way to categorize an alarm. This is particularly useful for searching.

The '''remark''' column tells what has happened with the alarm. If it is empty, the alarm has simply been raised. If there are letter present the are either an <big>A</big>, which means acknowledged, or a <big>G</big> which means that the alarm situation has been resolved either as a consequence of the acknowledgement or automatically. An example of where it has automatically been resolved is the case where the SD card in the WCU has reached, let us say, an 85% usage degree and later when data is uploaded the usage degree drops below 80%. By hovering over the remark column you will be presented with the date and user of when an alarm was acknowledged and with a date if it was automatically closed.

At the top is a set of controls to filter alarms based on other criteria than the text in the columns. First out we have the checkbox "'''Use fetch interval'''". Checking this box enables the two items "'''Time unit'''" and "'''Time interval'''". This makes it possible to fetch alarms from more than 24 hours back. Its default setting is conveniently 24 hours. The '''time unit''' says how the number should be interpreted, e.g. changing the '''time unit''' to Days while leaving the '''time interval''' at 24 will mean to fetch alarms from 24 days back. Available '''time units''' are '''hours''', '''days''' and '''months'''. Also, you choose to include closed alarm by checking the box "'''Include closed alarms'''" and/or including acknowledged alarms by checking "'''Include acknowledged alarms'''". It is only when either or both of these check boxes are checked that the remark column is populated.

== Functions ==
There are a few functions in this panel. You can '''update''' an alarm list, '''reload''' the alarm list, '''acknowledge''' an alarm and '''search''' among the alarms in the table.

=== Update alarm list ===
A said earlier, the list is automatically updated every 10 minutes. But if you feel like not waiting, simply press the 'Update alarms' button. This will fetch new alarms from the server.

=== Reload alarm list ===
By pressing 'Reload alarms' button you will clear the current set of alarms and fetch a new set from the last 24 hours. Usually this is not needed but it is here for your convenience. The button needs to be pressed if you use and change the fetch interval.

=== Acknowledge alarm ===
When alarm is 'taken care of' you can acknowledge this by pressing the button 'Acknowledge alarm'. This will make the alarm be marked as 'acknowledged'.

=== Search alarm ===
[[File:Alarm list filtered on resource.png|thumb|Alarm list filtered on resource '20']]
Over time, many alarms will accumulate and the list will be rather long. In order to find alarms of a specific category or for a specific resource, you can enter text in some of the filter column entries to filter the list. If you enter text in more than one of the filter entries an and-operation is used to filter the list. As an example see the figure to the right where a filter for WCUs having '20' in their id has been filtered for. As you can see, there are two WCUs that match this filter expression. No regular expression can be used here, it is a simple text search.

=== Alarm fetch interval ===
At the top is a set of controls to filter alarms based on other criteria than the text in the columns. First out we have the checkbox "'''Use fetch interval'''". Checking this box enables the two items "'''Time unit'''" and "'''Time interval'''". This makes it possible to fetch alarms from more than 24 hours back. Its default setting is conveniently 24 hours. The '''time unit''' says how the number should be interpreted, e.g. changing the '''time unit''' to Days while leaving the '''time interval''' at 24 will mean to fetch alarms from 24 days back. Available '''time units''' are '''hours''', '''days''' and '''months'''. Also, you choose to include closed alarm by checking the box "'''Include closed alarms'''" and/or including acknowledged alarms by checking "'''Include acknowledged alarms'''". It is only when either or both of these check boxes are checked that the remark column is populated.

== Available alarms ==
Presented below is the set of alarms currently available.

=== Certificate expires ===
This alarm is identified with '''wcu::info::cert::expire''<nowiki/>'. Currently, alarms start to appear from 30 days of certificate expiry date. The alarm is triggered at most once per 24 hours.

=== Certificate not present ===
This alarm is identified with '''wcu::info::cert::not_present''<nowiki/>'. It means there is no certificate at all on the WCU. The alarm is automatically closed when the WCU reports that there is a certificate installed on the WCU. It is triggered at most once per 24 hours.

=== Certificate password missing ===
The alarm is identified with '''wcu::info::cert::password::missing''<nowiki/>'. There is a certificate on the WCU and the private key is encrypted but there is no password supplied to decrypt it with. As soon as correct a password is supplied this alarm will be automatically closed.

=== Certificate unlock failed ===
The alarm is identified with '''wcu::info::cert::unlock::failed''<nowiki/>'. The most common problem to this alarm is that the wrong password has been supplied to decrypt the private key. As soon as correct a password is supplied this alarm will be automatically closed.

=== Sdcard usage ===
The alarm is identified with '''wcu::info::sdcard::use_percent''<nowiki/>'. An alarm is raised, currently, when the usage percentage of the SD card on the WCU is 80% or more. Alarms for this are triggered at most once every 24 hours. If the usage percentage is 95% or more, an alarm can be triggered up to once every 10 minutes. Once the usage percentage drops below 80% alarms are automatically closed.

=== Switch in INT position ===
The alarm is identified with '''wcu::info::start_switch::int''<nowiki/>'. An alarm is raised when the WCU reports that the switch is in the int position. It is automatically closed when the WCU reports that the switch is in position ext.

The Portal Administrator View

2020-01-30T13:16:13Z

Julian: /* The Edit User Dialog */ Default new user view columns

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 assignments 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 Assignment]]
[[File:Illustration 32b.png|thumb|Force Stop Assignment]]

In addition to the functionality for an ordinary user, an administrator has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running Assignment" shows the "Stop assigment" button. This button is the same as for the ordinary user and is used to stop a running assignment. When a running assignment 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 Assignment" button, which can be seen in Figure "Force Stop Assignment", forces a "Stop pending" assignment into "Stopped" state without waiting for the stop signal from the WCU.

Also, the administrator can search and view any user's task.

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

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

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

 

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

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

 

====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 "WCU" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Unit ID:
| The automatically generated unique WCU identifier. The ID cannot be changed from the portal.
|-
| style="font-weight: bold;" | Platform type:
| The WCU platform type.
|-
| style="font-weight: bold;" | Platform subtype:
| The WCU platform subtype.
|-
| style="font-weight: bold;" | WCU software version:
| This is the currently installed WCU software version.
|-
| style="font-weight: bold;" | Preferred WCU software:
| This is the new preferred WCU software version to be installed.
|-
| style="font-weight: bold;" | Perform reset on update:
| Removes all data on the WCU when installing a new WCU software.
|-
| style="font-weight: bold;" | MX4 firmware version:
| The currently installed MX4 firmware version.
|-
| style="font-weight: bold;" | 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]].

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

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.

 

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

 
{{:Shelve and Unshelve a WCU}}
 

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

 

==Modules for the WCU==
[[File:Illustration40.png|400px|thumb|Handling 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:
# Audio
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# 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
# Audio

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 "Handling Tool Configurations" there are a set of tools present. 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 for both MCD-Hub and Canrecorder, press the “Reload” button.

=== 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:
* '''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.
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 assignment, the module must be enabled for monitoring. If the assignment is enabled for monitoring but the module is not, no audio can be monitored live. Default is disabled. 

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

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

In the forementioned figue, 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 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:''' Check to let the DoIP module start signaling a synchronous diagnostic session.

[[File:Modules DoIP.png|thumb|left|250px|Settings for the DoIP module]]
 

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

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

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

===Configure the M-log Module===
[[File:Modules Mlog.png|thumb|left|250px|Settings for the M-log module]]
 

===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 the preferred firmware version. The other two configuration settings shown in Figure "Handling Tool Configurations" is “MCD-Hub firmware version” which shows the current version used by the hub 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]]
 

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

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:Signal Reader Module.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.

Further, the module settings include defining the debug level, the version of the generated MDF-file and determining 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 model has the same settings as the IDC module above.

===Configure the Software Download Module===

The state of health model 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]]
 

For WCUs of version 2.53 and forward it is possible to allow updates to be performed without manual interaction by checking the marked out 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]]
 

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:Modules Vinreader.png|thumb|250px|Settings for the Vinreader module]]The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11''' 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:Skärmavbild 2019-12-18 kl. 15.17.58.png|thumb|Audio module settings]]

==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 an assignment 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]]
 
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 GDS/SDDB File Tab===
In order for the portal to be able to translate error codes into a human readable format, a GDS or SDDB file must be selected for a vehicle. The set of GDS/SDDB files to choose from is administered in this tab, see Figure "GDS/SDDB File View".

[[File:Illustration53.png|left|frame|GDS/SDDB File View]]
 

To upload a new GDS/SDDB file, press upload new file and you will be presented with dialog where you select the file, sets an optional name (if no name is entered, the file name is used) and an optional comment. To upload a new file for an existing entry, press the edit file button and you will be presented with a dialog where you can upload a new file. To edit the comment or the name that should show up when select which GDS/SDDB file to use for a vehicle, simply double click the cell and edit directly in the table.

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

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

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 Custom Car Types Tab ===

This tab is further described [[Custom Car Types|here]].

=== The Alarm Tab ===

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

===The User Tab===
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 eight columns are:

[[File:Illustration46.png|frame|none|left|User Administration Tab]]

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

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 assiginments, you will also be prompted about giving the user access to currently running assignments 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 assignments on specified wcus]]
 

====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 assignment permission to the user, you will also here be prompted about giving the user access to currently running assignments on these wcus as well.
[[File:EditUser252.png|left|thumb|Modify User Dialog]]
 

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

To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward 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]]
 

====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. More about these functions is found under [[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 WICE portal < 2.47:'''

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

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

Vehicles

2019-12-20T13:56:36Z

Julian: Context menu explanation. Needs more info in the future

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.

[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]

The number of possible columns to show is quite large. You can elect which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:

{| class="wikitable sortable"
|-
|'''Active alarms'''
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.
|-
| style="font-weight: bold;" | Connected
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.
|-
| style="font-weight: bold;" | Distance
| Shows the distance the car has been driven the last week. (SoH assignment specific)
|-
| style="font-weight: bold;" | Last DRO
| Says when the DRO log file was last transferred to the portal.
|-
| style="font-weight: bold;" | Last log
| Shows when the last log file was transferred to the portal.
|-
| style="font-weight: bold;" | Mileage
| The column shows the mileage of the car.
|-
| style="font-weight: bold;" | Plate number
| The plate number of the car where the WCU is mounted.
|-
|'''Platform type'''
|Search WCU by platform type.
|-
| style="font-weight: bold;" | Project Id
| Shows the project identification number.
|-
| style="font-weight: bold;" | Proto number
| Shows the proto number.
|-
|'''Resource group'''
|The resource group (if any) the WCU is part of.
|-
| style="font-weight: bold;" | Series
| Shows the series attribute.
|-
| style="font-weight: bold;" | TSU
| Shows the TSU identifier.
|-
| style="font-weight: bold;" | Upload
| This column says how much data has been transferred from the WCU to the portal the last week.
|-
| style="font-weight: bold;" | Upload date
| Contains which date the last upload was done
|-
| style="font-weight: bold;" | Upload size
| Says what the size, in kilobytes, of the last data upload was.
|-
| style="font-weight: bold;" | Up-time
| Shows how many hours the WCU been running the last week.
|-
| style="font-weight: bold;" | VIN
| Shows the Vehicle Identification Number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | Voltage 
| The column shows the latest known battery voltage as reported by the CEM.
|-
| style="font-weight: bold;" | WCU ID
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.
|-
| style="font-weight: bold;" | WCU Description
| A textual comment attached to the WCU.
|-
| style="font-weight: bold;" | WCU voltage
| Shows the voltage as measured by the WCU.
|-
| style="font-weight: bold;" | WCU Version
| Shows which version the current WCU software has.
|-
| style="font-weight: bold;" | WCU storage usage
| Shows the amount of storage available to store data on the WCU.
|-
|'''WCU name'''
|Shows the name of the WCU
|}

Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].

There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating assignments you can select a resource group instead of the individual WCU:s to start a new assignment. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.

When selecting a row in the table the selected row changes to a blue shade. You can modify
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.

== Right click context menu ==
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu which contains row specific actions which are described here.

=== Go to Tasks Panel ===
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.

=== Go to Search Panel ===
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.

=== Go to Timeline ===
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.

=== Go to alarms ===
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.

==Show the Vehicle Position==
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in.

If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]].

==View Diagnostic Trouble Codes==
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]

If an SoH assignment has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle.
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".

==View ECU software==
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]
It is possible to see the ECU software number for each ECU in a vehicle.
Press the button “ECU SW” after you have selected one vehicle. The following view will be
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with
when it was read. You can download the list as a tab-separated text file if you press “Download”.

==Get WCU Up-time==
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.

Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.

From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].

==Export SoH Data==
[[File:Soh data export.png|frame|SoH Data Export Panel]]
You can export data from SoH assignments to your local computer by using the function
“Export SoH data”. Select the cars you are interested in as you can export for more than
one car in one export.
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage and storage usage.
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.

==Resource Groups==
WCUs and cars can collectively be referred to as "resources". As such they can be grouped
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only
one type of resource is in a resource group.

You identify a resource group by a gray arrow like icon to the left in the table row. If you
click the icon the entry opens up and makes room for showing which resources are part
of the resource group.

From version 2.42 the showing of the resource group's resources has been improved. More info can be found in [[Resource group's resources]].

When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a
resource group or not. If you select a resource group, the new assignment will be downloaded to all the WCUs that are part of the resource group.
As a regular user you can not create and remove resource groups, only an administrator
of the portal can do this.

From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.

This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.

Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".

==Modules==
If you have the right permission you will be able to view a WCU:s modules, and
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:

* [[The Portal Administrator View#Configure the audio module|Audio]]
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]
* [[The Portal Administrator View#Configure the GPS Module|GPS]]
* [[The Portal Administrator View#Configure the IDC Module|IDC]]
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]
* [[The Portal Administrator View#Configure the M-log Module|M-log]]
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]
* [[The Portal Administrator View#Configure the Video Module|Video]]

Vehicles

2019-12-20T13:13:43Z

Julian: Removed non-existing column

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.

[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]

The number of possible columns to show is quite large. You can elect which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:

{| class="wikitable sortable"
|-
|'''Active alarms'''
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.
|-
| style="font-weight: bold;" | Connected
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.
|-
| style="font-weight: bold;" | Distance
| Shows the distance the car has been driven the last week. (SoH assignment specific)
|-
| style="font-weight: bold;" | Last DRO
| Says when the DRO log file was last transferred to the portal.
|-
| style="font-weight: bold;" | Last log
| Shows when the last log file was transferred to the portal.
|-
| style="font-weight: bold;" | Mileage
| The column shows the mileage of the car.
|-
| style="font-weight: bold;" | Plate number
| The plate number of the car where the WCU is mounted.
|-
|'''Platform type'''
|Search WCU by platform type.
|-
| style="font-weight: bold;" | Project Id
| Shows the project identification number.
|-
| style="font-weight: bold;" | Proto number
| Shows the proto number.
|-
|'''Resource group'''
|The resource group (if any) the WCU is part of.
|-
| style="font-weight: bold;" | Series
| Shows the series attribute.
|-
| style="font-weight: bold;" | TSU
| Shows the TSU identifier.
|-
| style="font-weight: bold;" | Upload
| This column says how much data has been transferred from the WCU to the portal the last week.
|-
| style="font-weight: bold;" | Upload date
| Contains which date the last upload was done
|-
| style="font-weight: bold;" | Upload size
| Says what the size, in kilobytes, of the last data upload was.
|-
| style="font-weight: bold;" | Up-time
| Shows how many hours the WCU been running the last week.
|-
| style="font-weight: bold;" | VIN
| Shows the Vehicle Identification Number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | Voltage 
| The column shows the latest known battery voltage as reported by the CEM.
|-
| style="font-weight: bold;" | WCU ID
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.
|-
| style="font-weight: bold;" | WCU Description
| A textual comment attached to the WCU.
|-
| style="font-weight: bold;" | WCU voltage
| Shows the voltage as measured by the WCU.
|-
| style="font-weight: bold;" | WCU Version
| Shows which version the current WCU software has.
|-
| style="font-weight: bold;" | WCU storage usage
| Shows the amount of storage available to store data on the WCU.
|-
|'''WCU name'''
|Shows the name of the WCU
|}

Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].

There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating assignments you can select a resource group instead of the individual WCU:s to start a new assignment. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.

When selecting a row in the table the selected row changes to a blue shade. You can modify
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.

==Show the Vehicle Position==
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in.

If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]].

==View Diagnostic Trouble Codes==
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]

If an SoH assignment has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle.
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".

==View ECU software==
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]
It is possible to see the ECU software number for each ECU in a vehicle.
Press the button “ECU SW” after you have selected one vehicle. The following view will be
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with
when it was read. You can download the list as a tab-separated text file if you press “Download”.

==Get WCU Up-time==
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.

Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.

From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].

==Export SoH Data==
[[File:Soh data export.png|frame|SoH Data Export Panel]]
You can export data from SoH assignments to your local computer by using the function
“Export SoH data”. Select the cars you are interested in as you can export for more than
one car in one export.
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage and storage usage.
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.

==Resource Groups==
WCUs and cars can collectively be referred to as "resources". As such they can be grouped
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only
one type of resource is in a resource group.

You identify a resource group by a gray arrow like icon to the left in the table row. If you
click the icon the entry opens up and makes room for showing which resources are part
of the resource group.

From version 2.42 the showing of the resource group's resources has been improved. More info can be found in [[Resource group's resources]].

When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a
resource group or not. If you select a resource group, the new assignment will be downloaded to all the WCUs that are part of the resource group.
As a regular user you can not create and remove resource groups, only an administrator
of the portal can do this.

From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.

This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.

Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".

==Modules==
If you have the right permission you will be able to view a WCU:s modules, and
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:

* [[The Portal Administrator View#Configure the audio module|Audio]]
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]
* [[The Portal Administrator View#Configure the GPS Module|GPS]]
* [[The Portal Administrator View#Configure the IDC Module|IDC]]
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]
* [[The Portal Administrator View#Configure the M-log Module|M-log]]
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]
* [[The Portal Administrator View#Configure the Video Module|Video]]

Vehicles

2019-12-20T13:06:08Z

Julian: Ordered the columns alphabetically

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.

[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]

The number of possible columns to show is quite large. You can elect which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:

{| class="wikitable sortable"
|-
|'''Active alarms'''
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.
|-
| style="font-weight: bold;" | Connected
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.
|-
| style="font-weight: bold;" | Distance
| Shows the distance the car has been driven the last week.
|-
| style="font-weight: bold;" | GDS/SDDB
| The name of the GDS/SDDB file used when parsing SoH assignment data.
|-
| style="font-weight: bold;" | Last DRO
| Says when the DRO log file was last transferred to the portal.
|-
| style="font-weight: bold;" | Last log
| Shows when the last log file was transferred to the portal.
|-
| style="font-weight: bold;" | Mileage
| The column shows the mileage of the car.
|-
| style="font-weight: bold;" | Plate number
| The plate number of the car where the WCU is mounted.
|-
|'''Platform type'''
|Search WCU by platform type.
|-
| style="font-weight: bold;" | Project Id
| Shows the project identification number.
|-
| style="font-weight: bold;" | Proto number
| Shows the proto number.
|-
|'''Resource group'''
|The resource group (if any) the WCU is part of.
|-
| style="font-weight: bold;" | Series
| Shows the series attribute.
|-
| style="font-weight: bold;" | TSU
| Shows the TSU identifier.
|-
| style="font-weight: bold;" | Upload
| This column says how much data has been transferred from the WCU to the portal the last week.
|-
| style="font-weight: bold;" | Upload date
| Contains which date the last upload was done
|-
| style="font-weight: bold;" | Upload size
| Says what the size, in kilobytes, of the last data upload was.
|-
| style="font-weight: bold;" | Up-time
| Shows how many hours the WCU been running the last week.
|-
| style="font-weight: bold;" | VIN
| Shows the Vehicle Identification Number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | Voltage 
| The column shows the latest known battery voltage as reported by the CEM.
|-
| style="font-weight: bold;" | WCU ID
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.
|-
| style="font-weight: bold;" | WCU Description
| A textual comment attached to the WCU.
|-
| style="font-weight: bold;" | WCU voltage
| Shows the voltage as measured by the WCU.
|-
| style="font-weight: bold;" | WCU Version
| Shows which version the current WCU software has.
|-
| style="font-weight: bold;" | WCU storage usage
| Shows the amount of storage available to store data on the WCU.
|-
|'''WCU name'''
|Shows the name of the WCU
|}

Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].

There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating assignments you can select a resource group instead of the individual WCU:s to start a new assignment. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.

When selecting a row in the table the selected row changes to a blue shade. You can modify
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.

==Show the Vehicle Position==
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in.

If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]].

==View Diagnostic Trouble Codes==
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]

If an SoH assignment has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle.
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".

==View ECU software==
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]
It is possible to see the ECU software number for each ECU in a vehicle.
Press the button “ECU SW” after you have selected one vehicle. The following view will be
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with
when it was read. You can download the list as a tab-separated text file if you press “Download”.

==Get WCU Up-time==
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.

Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.

From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].

==Export SoH Data==
[[File:Soh data export.png|frame|SoH Data Export Panel]]
You can export data from SoH assignments to your local computer by using the function
“Export SoH data”. Select the cars you are interested in as you can export for more than
one car in one export.
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage and storage usage.
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.

==Resource Groups==
WCUs and cars can collectively be referred to as "resources". As such they can be grouped
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only
one type of resource is in a resource group.

You identify a resource group by a gray arrow like icon to the left in the table row. If you
click the icon the entry opens up and makes room for showing which resources are part
of the resource group.

From version 2.42 the showing of the resource group's resources has been improved. More info can be found in [[Resource group's resources]].

When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a
resource group or not. If you select a resource group, the new assignment will be downloaded to all the WCUs that are part of the resource group.
As a regular user you can not create and remove resource groups, only an administrator
of the portal can do this.

From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.

This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.

Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".

==Modules==
If you have the right permission you will be able to view a WCU:s modules, and
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:

* [[The Portal Administrator View#Configure the audio module|Audio]]
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]
* [[The Portal Administrator View#Configure the GPS Module|GPS]]
* [[The Portal Administrator View#Configure the IDC Module|IDC]]
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]
* [[The Portal Administrator View#Configure the M-log Module|M-log]]
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]
* [[The Portal Administrator View#Configure the Video Module|Video]]

Vehicles

2019-12-20T12:51:15Z

Julian: Cleared up a couple of old points, and added Active alarms

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.

[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]

The number of possible columns to show is quite large (24). The columns shown below are in
default order. You will have to account for any changes you have made yourself. The columns
are:

{| class="wikitable sortable"
| style="font-weight: bold;" | WCU ID
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.
|-
| style="font-weight: bold;" | WCU Description
| A textual comment attached to the WCU.
|-
| style="font-weight: bold;" | Last DRO
| Says when the DRO log file was last transferred to the portal.
|-
| style="font-weight: bold;" | Last log
| Shows when the last log file was transferred to the portal.
|-
| style="font-weight: bold;" | Upload size
| Says what the size, in kilobytes, of the last data upload was.
|-
| style="font-weight: bold;" | Upload date
| Contains which date the last upload was done
|-
| style="font-weight: bold;" | Upload
| This column says how much data has been transferred from the WCU to the portal the last week.
|-
| style="font-weight: bold;" | Plate number
| The plate number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | VIN
| Shows the Vehicle Identification Number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | Voltage 
| The column shows the latest known battery voltage as reported by the CEM.
|-
| style="font-weight: bold;" | Mileage
| The column shows the mileage of the car.
|-
| style="font-weight: bold;" | Up-time
| Shows how many hours the WCU been running the last week.
|-
| style="font-weight: bold;" | Distance
| Shows the distance the car has been driven the last week.
|-
| style="font-weight: bold;" | Project Id
| Shows the project identification number.
|-
| style="font-weight: bold;" | Proto number
| Shows the proto number.
|-
| style="font-weight: bold;" | TSU
| Shows the TSU identifier.
|-
| style="font-weight: bold;" | WCU Version
| Shows which version the current WCU software has.
|-
| style="font-weight: bold;" | Connected
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.
|-
| style="font-weight: bold;" | GDS/SDDB
| The name of the GDS/SDDB file used when parsing SoH assignment data.
|-
| style="font-weight: bold;" | WCU voltage
| Shows the voltage as measured by the WCU.
|-
| style="font-weight: bold;" | WCU storage usage
| Shows the amount of storage available to store data on the WCU.
|-
| style="font-weight: bold;" | Series
| Shows the series attribute.
|-
|'''WCU name'''
|Shows the name of the WCU
|-
|'''Resource group'''
|The resource group (if any) the WCU is part of.
|-
|'''Platform type'''
|Search WCU by platform type.
|-
|'''Active alarms'''
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.
|}

Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].

There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating assignments you can select a resource group instead of the individual WCU:s to start a new assignment. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.

When selecting a row in the table the selected row changes to a blue shade. You can modify
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.

==Show the Vehicle Position==
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in.

If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]].

==View Diagnostic Trouble Codes==
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]

If an SoH assignment has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle.
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".

==View ECU software==
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]
It is possible to see the ECU software number for each ECU in a vehicle.
Press the button “ECU SW” after you have selected one vehicle. The following view will be
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with
when it was read. You can download the list as a tab-separated text file if you press “Download”.

==Get WCU Up-time==
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.

Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.

From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].

==Export SoH Data==
[[File:Soh data export.png|frame|SoH Data Export Panel]]
You can export data from SoH assignments to your local computer by using the function
“Export SoH data”. Select the cars you are interested in as you can export for more than
one car in one export.
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage and storage usage.
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.

==Resource Groups==
WCUs and cars can collectively be referred to as "resources". As such they can be grouped
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only
one type of resource is in a resource group.

You identify a resource group by a gray arrow like icon to the left in the table row. If you
click the icon the entry opens up and makes room for showing which resources are part
of the resource group.

From version 2.42 the showing of the resource group's resources has been improved. More info can be found in [[Resource group's resources]].

When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a
resource group or not. If you select a resource group, the new assignment will be downloaded to all the WCUs that are part of the resource group.
As a regular user you can not create and remove resource groups, only an administrator
of the portal can do this.

From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.

This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.

Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".

==Modules==
If you have the right permission you will be able to view a WCU:s modules, and
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:

* [[The Portal Administrator View#Configure the audio module|Audio]]
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]
* [[The Portal Administrator View#Configure the GPS Module|GPS]]
* [[The Portal Administrator View#Configure the IDC Module|IDC]]
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]
* [[The Portal Administrator View#Configure the M-log Module|M-log]]
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]
* [[The Portal Administrator View#Configure the Video Module|Video]]

New features in v2.56

2019-12-20T09:06:42Z

Julian:

New features in v2.56.

== Drive cycles and measurements in "Plot route"-tool ==
Individual drive cycles are now drawn using different colors in the plot route tool, which is available through the Vehicles-tab. On top of that, Plot route will now also draw markers on the map to indicate triggered measurements. Clicking on such a marker takes you to the Preview-tool, allowing you easy access to your data. You can read more about the changes to the "Plot route"-tool by [[Plot Route|clicking this link]].

== Periodic upload ==
It is now possible to have a WCU upload its data periodically. You can enable this by going to the WCU configuration of any 2.56 WCU, and go to the upload tab. Inside, you will see a checkbox with the label "Upload periodically". Checking this will result in the WCU uploading its data every 10 minutes.

== Alarm column in the Vehicles panel ==
You are now able to get an easy to grasp alarm summary in the vehicles panel. To enable this, right click on the table header and go to "Columns". From there, select "Active alarms". This will enable a column that counts the alarms for each resource in the list.

== Go to alarms from the Vehicles panel ==
You can select one or more rows in the vehicles panel, right click and then select "Go to alarms" to instantly get the alarms relevant for the selected resources.

== Default columns for new users ==
When a new user is created only some columns will be visible by default in the Vehicles and Task panels. More information is available in [[The Portal Administrator View#The New User Dialog|the section about the new user dialogue]].

== Audio ==
The possibility to record sound using a WCU is introduced. Have a look [[Wice audio|here]].

Plot Route

2019-12-20T09:03:40Z

Julian: Drive cycles and measurement markers

==How to access this tool==
If you are interested in seeing where the car was driven while making measurements you can use the “Plot route” tool. This tool can be accessed either by selecting and then right-clicking a task in the tasks panel. You can also access the tool from the bottom menu in both the tasks and vehicles panel.

== How it works ==
An important detail to note is that plot route is a tool that operates using the data of a specific car. The tool will check which car you have selected. It will then aggregate the GPS-data of all the WCUs that has been installed in the car during the specified time period. This is the data that is plotted.

== Usage ==
[[File:Plot-route-toolbar.png|frame]]

=== Car information ===
On the top right of the screen the "Car Information" panel displays the plate number, VIN and when the cars latest known GPS update occured.

=== Set date interval ===
In the side-menu to the right there is a "Set date interval" form. You can use this form to select an interval within which you wish you know where the car has been. '''This interval has a maximum length of one month''', and is by default set to the last known GPS update date. If you wish to change the interval, simply enter the date interval of your choice and click "update map".

=== Viewing the data ===
If you are having any trouble locating the data in the map you can utilize the "'''Fit all'''"-button. This button ensures that all position data is visible on the map by zooming out and panning to an appropriate location.

Also in the controls panel is the option to hide/show measurement markers.

== Visualization of drive cycles and signal reader measurements ==

=== Drive cycles ===
If the plot route tool detects that there was a significant time difference between two reported positions, then it will assume that they are part of different "drive cycles". This is visualized in the map by giving different drive cycles different colors. However, if there are too many drive cycles available then two drive cycles may receive the same color.

=== Signal reader measurements ===
Measurements are visualized on the map using markers. These markers are positioned where the measurement started. You can click the measurement markers to jump straight to the [[Preview data|preview tool]] where you can preview signal data from that specific measurement.

File:Plot-route-toolbar.png

2019-12-20T08:54:07Z

Julian:

Plot route toolbar

The Portal Administrator View

2019-12-20T08:42:54Z

Julian: /* The Edit User Dialog */

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 assignments 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 Assignment]]
[[File:Illustration 32b.png|thumb|Force Stop Assignment]]

In addition to the functionality for an ordinary user, an administrator has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running Assignment" shows the "Stop assigment" button. This button is the same as for the ordinary user and is used to stop a running assignment. When a running assignment 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 Assignment" button, which can be seen in Figure "Force Stop Assignment", forces a "Stop pending" assignment into "Stopped" state without waiting for the stop signal from the WCU.

Also, the administrator can search and view any user's task.

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

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

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 (oe corresponding partial statuses), the active option is disabled. This is also true if the WCU is connected to a car 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]]

 

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

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

 

====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 "WCU" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Unit ID:
| The automatically generated unique WCU identifier. The ID cannot be changed from the portal.
|-
| style="font-weight: bold;" | Platform type:
| The WCU platform type.
|-
| style="font-weight: bold;" | Platform subtype:
| The WCU platform subtype.
|-
| style="font-weight: bold;" | WCU software version:
| This is the currently installed WCU software version.
|-
| style="font-weight: bold;" | Preferred WCU software:
| This is the new preferred WCU software version to be installed.
|-
| style="font-weight: bold;" | Perform reset on update:
| Removes all data on the WCU when installing a new WCU software.
|-
| style="font-weight: bold;" | MX4 firmware version:
| The currently installed MX4 firmware version.
|-
| style="font-weight: bold;" | 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]].

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

 

===Upload a Car Import File===
It is possible to import a file that describes a set of cars. It can consist of both new cars and cars 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 car. The first line of the file must look as follows: 
'''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.

 
{{:Shelve and Unshelve a WCU}}
 

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

 

==Modules for the WCU==
[[File:Illustration40.png|400px|thumb|Handling 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:
# Audio
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# 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 "Handling Tool Configurations" there are a set of tools present. 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 for both MCD-Hub and Canrecorder, press the “Reload” button.

=== 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:
* '''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.
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 assignment, the module must be enabled for monitoring. If the assignment is enabled for monitoring but the module is not, no audio can be monitored live. Default is disabled. 

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

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

In the forementioned figue, 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 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:''' Check to let the DoIP module start signaling a synchronous diagnostic session.

[[File:Modules DoIP.png|thumb|left|250px|Settings for the DoIP module]]
 

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

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

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

===Configure the M-log Module===
[[File:Modules Mlog.png|thumb|left|250px|Settings for the M-log module]]
 

===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 the preferred firmware version. The other two configuration settings shown in Figure "Handling Tool Configurations" is “MCD-Hub firmware version” which shows the current version used by the hub 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]]
 

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

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:Signal Reader Module.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.

Further, the module settings include defining the debug level, the version of the generated MDF-file and determining 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 model has the same settings as the IDC module above.

===Configure the Software Download Module===

The state of health model 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]]
 

For WCUs of version 2.53 and forward it is possible to allow updates to be performed without manual interaction by checking the marked out 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]]
 

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:Modules Vinreader.png|thumb|250px|Settings for the Vinreader module]]The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11''' 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:Skärmavbild 2019-12-18 kl. 15.17.58.png|thumb|Audio module settings]]

==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 car a specific WCU was in at the time an assignment was run can be done by connecting a car 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 cars, 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 car 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 car you drag the WCU you would like to connect onto the car in the right table. When you drop it onto a car a small icon will show signifying that the WCU and car 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]]
 
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 GDS/SDDB File Tab===
In order for the portal to be able to translate error codes into a human readable format, a GDS or SDDB file must be selected for a vehicle. The set of GDS/SDDB files to choose from is administered in this tab, see Figure "GDS/SDDB File View".

[[File:Illustration53.png|left|frame|GDS/SDDB File View]]
 

To upload a new GDS/SDDB file, press upload new file and you will be presented with dialog where you select the file, sets an optional name (if no name is entered, the file name is used) and an optional comment. To upload a new file for an existing entry, press the edit file button and you will be presented with a dialog where you can upload a new file. To edit the comment or the name that should show up when select which GDS/SDDB file to use for a vehicle, simply double click the cell and edit directly in the table.

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

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

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 Custom Car Types Tab ===

This tab is further described [[Custom Car Types|here]].

=== The Alarm Tab ===

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

===The User Tab===
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 eight columns are:

[[File:Illustration46.png|frame|none|left|User Administration Tab]]

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

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 assiginments, you will also be prompted about giving the user access to currently running assignments 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.
[[File:NewUserDialog252.png|left|thumb|New User Dialog]]
[[File:PromptNewUserCurAss.png|left|thumb|Prompt to give user permission to currently running assignments on specified wcus]]
 

====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 assignment permission to the user, you will also here be prompted about giving the user access to currently running assignments on these wcus as well.
[[File:EditUser252.png|left|thumb|Modify User Dialog]]
 

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

To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward 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]]
 

====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. More about these functions is found under [[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 WICE portal < 2.47:'''

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

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

New features in v2.56

2019-12-20T08:41:52Z

Julian: /* Default columns for new users */

New features in v2.56.

== Drive cycles and measurements in "Plot route"-tool ==
Individual drive cycles are now drawn using different colors in the plot route tool, which is available through the Vehicles-tab. On top of that, Plot route will now also draw markers on the map to indicate triggered measurements. Clicking on such a marker takes you to the Preview-tool, allowing you easy access to your data.

== Periodic upload ==
It is now possible to have a WCU upload its data periodically. You can enable this by going to the WCU configuration of any 2.56 WCU, and go to the upload tab. Inside, you will see a checkbox with the label "Upload periodically". Checking this will result in the WCU uploading its data every 10 minutes.

== Alarm column in the Vehicles panel ==
You are now able to get an easy to grasp alarm summary in the vehicles panel. To enable this, right click on the table header and go to "Columns". From there, select "Active alarms". This will enable a column that counts the alarms for each resource in the list.

== Go to alarms from the Vehicles panel ==
You can select one or more rows in the vehicles panel, right click and then select "Go to alarms" to instantly get the alarms relevant for the selected resources.

== Default columns for new users ==
When a new user is created only some columns will be visible by default in the Vehicles and Task panels. More information is available in [[The Portal Administrator View#The New User Dialog|the section about the new user dialogue]].

== Audio ==
The possibility to record sound using a WCU is introduced. Have a look [[Wice audio|here]].

The Portal Administrator View

2019-12-20T08:37:52Z

Julian: /* The Edit User Dialog */ Default columns for new users

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 assignments 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 Assignment]]
[[File:Illustration 32b.png|thumb|Force Stop Assignment]]

In addition to the functionality for an ordinary user, an administrator has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running Assignment" shows the "Stop assigment" button. This button is the same as for the ordinary user and is used to stop a running assignment. When a running assignment 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 Assignment" button, which can be seen in Figure "Force Stop Assignment", forces a "Stop pending" assignment into "Stopped" state without waiting for the stop signal from the WCU.

Also, the administrator can search and view any user's task.

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

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

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 (oe corresponding partial statuses), the active option is disabled. This is also true if the WCU is connected to a car 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]]

 

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

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

 

====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 "WCU" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Unit ID:
| The automatically generated unique WCU identifier. The ID cannot be changed from the portal.
|-
| style="font-weight: bold;" | Platform type:
| The WCU platform type.
|-
| style="font-weight: bold;" | Platform subtype:
| The WCU platform subtype.
|-
| style="font-weight: bold;" | WCU software version:
| This is the currently installed WCU software version.
|-
| style="font-weight: bold;" | Preferred WCU software:
| This is the new preferred WCU software version to be installed.
|-
| style="font-weight: bold;" | Perform reset on update:
| Removes all data on the WCU when installing a new WCU software.
|-
| style="font-weight: bold;" | MX4 firmware version:
| The currently installed MX4 firmware version.
|-
| style="font-weight: bold;" | 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]].

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

 

===Upload a Car Import File===
It is possible to import a file that describes a set of cars. It can consist of both new cars and cars 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 car. The first line of the file must look as follows: 
'''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.

 
{{:Shelve and Unshelve a WCU}}
 

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

 

==Modules for the WCU==
[[File:Illustration40.png|400px|thumb|Handling 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:
# Audio
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# 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 "Handling Tool Configurations" there are a set of tools present. 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 for both MCD-Hub and Canrecorder, press the “Reload” button.

=== 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:
* '''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.
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 assignment, the module must be enabled for monitoring. If the assignment is enabled for monitoring but the module is not, no audio can be monitored live. Default is disabled. 

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

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

In the forementioned figue, 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 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:''' Check to let the DoIP module start signaling a synchronous diagnostic session.

[[File:Modules DoIP.png|thumb|left|250px|Settings for the DoIP module]]
 

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

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

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

===Configure the M-log Module===
[[File:Modules Mlog.png|thumb|left|250px|Settings for the M-log module]]
 

===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 the preferred firmware version. The other two configuration settings shown in Figure "Handling Tool Configurations" is “MCD-Hub firmware version” which shows the current version used by the hub 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]]
 

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

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:Signal Reader Module.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.

Further, the module settings include defining the debug level, the version of the generated MDF-file and determining 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 model has the same settings as the IDC module above.

===Configure the Software Download Module===

The state of health model 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]]
 

For WCUs of version 2.53 and forward it is possible to allow updates to be performed without manual interaction by checking the marked out 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]]
 

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:Modules Vinreader.png|thumb|250px|Settings for the Vinreader module]]The method of reading a vehicle's VIN (Vehicle Identification Number) can be set to '''SPA29''', '''OBD2''', '''SPA11''' 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:Skärmavbild 2019-12-18 kl. 15.17.58.png|thumb|Audio module settings]]

==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 car a specific WCU was in at the time an assignment was run can be done by connecting a car 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 cars, 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 car 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 car you drag the WCU you would like to connect onto the car in the right table. When you drop it onto a car a small icon will show signifying that the WCU and car 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]]
 
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 GDS/SDDB File Tab===
In order for the portal to be able to translate error codes into a human readable format, a GDS or SDDB file must be selected for a vehicle. The set of GDS/SDDB files to choose from is administered in this tab, see Figure "GDS/SDDB File View".

[[File:Illustration53.png|left|frame|GDS/SDDB File View]]
 

To upload a new GDS/SDDB file, press upload new file and you will be presented with dialog where you select the file, sets an optional name (if no name is entered, the file name is used) and an optional comment. To upload a new file for an existing entry, press the edit file button and you will be presented with a dialog where you can upload a new file. To edit the comment or the name that should show up when select which GDS/SDDB file to use for a vehicle, simply double click the cell and edit directly in the table.

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

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

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 Custom Car Types Tab ===

This tab is further described [[Custom Car Types|here]].

=== The Alarm Tab ===

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

===The User Tab===
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 eight columns are:

[[File:Illustration46.png|frame|none|left|User Administration Tab]]

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

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 assiginments, you will also be prompted about giving the user access to currently running assignments 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 will be 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.
[[File:NewUserDialog252.png|left|thumb|New User Dialog]]
[[File:PromptNewUserCurAss.png|left|thumb|Prompt to give user permission to currently running assignments on specified wcus]]
 

====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 assignment permission to the user, you will also here be prompted about giving the user access to currently running assignments on these wcus as well.
[[File:EditUser252.png|left|thumb|Modify User Dialog]]
 

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

To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward 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]]
 

====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. More about these functions is found under [[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 WICE portal < 2.47:'''

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

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

New features in v2.56

2019-12-17T15:05:30Z

Julian: Go to alarms

New features in v2.56.

== Drive cycles and measurements in "Plot route"-tool ==
Individual drive cycles are now drawn using different colors in the plot route tool, which is available through the Vehicles-tab. On top of that, Plot route will now also draw markers on the map to indicate triggered measurements. Clicking on such a marker takes you to the Preview-tool, allowing you easy access to your data.

== Periodic upload ==
It is now possible to have a WCU upload its data periodically. You can enable this by going to the WCU configuration of any 2.56 WCU, and go to the upload tab. Inside, you will see a checkbox with the label "Upload periodically". Checking this will result in the WCU uploading its data every 10 minutes.

== Alarm column in the Vehicles panel ==
You are now able to get an easy to grasp alarm summary in the vehicles panel. To enable this, right click on the table header and go to "Columns". From there, select "Active alarms". This will enable a column that counts the alarms for each resource in the list.

== Go to alarms from the Vehicles panel ==
You can select one or more rows in the vehicles panel, right click and then select "Go to alarms" to instantly get the alarms relevant for the selected resources.

== Default columns for new users ==
When a new user is created only some columns will be visible by default in the Vehicles and Task panels.

New features in v2.56

2019-12-17T15:03:19Z

Julian: Default table view

New features in v2.56

2019-12-17T15:00:16Z

Julian: Plot route drive cylces

The Portal Administrator View

2019-12-17T14:56:17Z

Julian: WCU configuration -> Upload periodically

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 assignments 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 Assignment]]
[[File:Illustration 32b.png|thumb|Force Stop Assignment]]

In addition to the functionality for an ordinary user, an administrator has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running Assignment" shows the "Stop assigment" button. This button is the same as for the ordinary user and is used to stop a running assignment. When a running assignment 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 Assignment" button, which can be seen in Figure "Force Stop Assignment", forces a "Stop pending" assignment into "Stopped" state without waiting for the stop signal from the WCU.

Also, the administrator can search and view any user's task.

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

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

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 (oe corresponding partial statuses), the active option is disabled. This is also true if the WCU is connected to a car 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]]

 

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

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

 

====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 "WCU" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Unit ID:
| The automatically generated unique WCU identifier. The ID cannot be changed from the portal.
|-
| style="font-weight: bold;" | Platform type:
| The WCU platform type.
|-
| style="font-weight: bold;" | Platform subtype:
| The WCU platform subtype.
|-
| style="font-weight: bold;" | WCU software version:
| This is the currently installed WCU software version.
|-
| style="font-weight: bold;" | Preferred WCU software:
| This is the new preferred WCU software version to be installed.
|-
| style="font-weight: bold;" | Perform reset on update:
| Removes all data on the WCU when installing a new WCU software.
|-
| style="font-weight: bold;" | MX4 firmware version:
| The currently installed MX4 firmware version.
|-
| style="font-weight: bold;" | 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]].

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

 

===Upload a Car Import File===
It is possible to import a file that describes a set of cars. It can consist of both new cars and cars 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 car. The first line of the file must look as follows: 
'''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.

 
{{:Shelve and Unshelve a WCU}}
 

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

 

==Modules for the WCU==
[[File:Illustration40.png|400px|thumb|Handling 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:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# 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 "Handling Tool Configurations" there are a set of tools present. 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 for both MCD-Hub and Canrecorder, press the “Reload” button.

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

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

In the forementioned figue, 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 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:''' Check to let the DoIP module start signaling a synchronous diagnostic session.

[[File:Modules DoIP.png|thumb|left|250px|Settings for the DoIP module]]
 

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

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

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

===Configure the M-log Module===
[[File:Modules Mlog.png|thumb|left|250px|Settings for the M-log module]]
 

===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 the preferred firmware version. The other two configuration settings shown in Figure "Handling Tool Configurations" is “MCD-Hub firmware version” which shows the current version used by the hub 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]]
 

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

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:Signal Reader Module.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 and UDP. Thereafter the monitoring rate for both cases is set using the "Interval"-field, where the default is once per second.

Further, the module settings include defining the debug level, the version of the generated MDF-file and determining appropriate values for the diagnostics timeout. The timeout values determine how long time the receiver is to wait for the diagnostic values before assuming that there are none. Typically, the timeout for sequence file diagnostics is set to a higher value due to the fact that this answer might require more time.

===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 model has the same settings as the IDC module above.

===Configure the Software Download Module===

The state of health model 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]]
 

For WCUs of version 2.53 and forward it is possible to allow updates to be performed without manual interaction by checking the marked out 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]]
 

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 here [[WICE video]].

=== Configure the Vinreader Module ===
[[File:Modules Vinreader.png|thumb|left|250px|Settings for the Vinreader module]]
 

 

==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 car a specific WCU was in at the time an assignment was run can be done by connecting a car 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 cars, 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 car 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 car you drag the WCU you would like to connect onto the car in the right table. When you drop it onto a car a small icon will show signifying that the WCU and car 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]]
 
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 GDS/SDDB File Tab===
In order for the portal to be able to translate error codes into a human readable format, a GDS or SDDB file must be selected for a vehicle. The set of GDS/SDDB files to choose from is administered in this tab, see Figure "GDS/SDDB File View".

[[File:Illustration53.png|left|frame|GDS/SDDB File View]]
 

To upload a new GDS/SDDB file, press upload new file and you will be presented with dialog where you select the file, sets an optional name (if no name is entered, the file name is used) and an optional comment. To upload a new file for an existing entry, press the edit file button and you will be presented with a dialog where you can upload a new file. To edit the comment or the name that should show up when select which GDS/SDDB file to use for a vehicle, simply double click the cell and edit directly in the table.

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

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

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 Custom Car Types Tab ===

This tab is further described [[Custom Car Types|here]].

=== The Alarm Tab ===

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

===The User Tab===
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 eight columns are:

[[File:Illustration46.png|frame|none|left|User Administration Tab]]

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

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 assiginments, you will also be prompted about giving the user access to currently running assignments on these wcus as well. This can also be done when editing the roles of a user.
[[File:NewUserDialog252.png|left|thumb|New User Dialog]]
[[File:PromptNewUserCurAss.png|left|thumb|Prompt to give user permission to currently running assignments on specified wcus]]
 

====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 assignment permission to the user, you will also here be prompted about giving the user access to currently running assignments on these wcus as well.
[[File:EditUser252.png|left|thumb|Modify User Dialog]]
 

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

To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward 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]]
 

====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. More about these functions is found under [[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 WICE portal < 2.47:'''

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

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

New features in v2.56

2019-12-17T14:53:55Z

Julian:

New features in v2.56.

== Periodic upload ==
It is now possible to have a WCU upload its data periodically. You can enable this by going to the WCU configuration of any 2.56 WCU, and go to the upload tab. Inside, you will see a checkbox with the label "Upload periodically". Checking this will result in the WCU uploading its data every 10 minutes.

== Alarm column in the vehicles panel ==
You are now able to get an easy to grasp alarm summary in the vehicles panel. To enable this, right click on the table header and go to "Columns". From there, select "Active alarms". This will enable a column that counts the alarms for each resource in the list.

New features in v2.54

2019-10-18T13:24:31Z

Julian:

=== Improved vehicles tab performance ===
The vehicles tab has been significantly optimized. The search button has been removed as searches will now be performed automatically once any of the search fields are changed.

=== Resource group member history ===
You can now display the membership history of individual WCUs within a resource group by right clicking on a resource group in the vehicles panel and selecting "Member history".

=== Re-design of Dialogs for Managing Labels on Resources ===
The dialogs used to add and remove labels on resources, found when selecting the corresponding right-click option for resources in the [[Vehicles|Vehicles tab]], is re-designed in purpose and appearance. Read more about the new design [[Labels|here]].

=== Scheduling Added for CAN-recorder, IDC, Signal Reader and Video Tasks ===
From this version forward it is possible to schedule tasks of type CAN-recorder, IDC, Signal Reader and Video. This is done in the same manner as scheduling of SoH tasks, read more [[Creating a Task#CAN-recorder#Scheduling|here]].
=== Signal Reader Assignment Wizard extensions ===
Several new features have been implemented to the Haf file creator/Signal reader assignment wizard. They include:
* Now possible to sort by last edited date while browsing saved assignments
* If a CAN bus has frame format Extended, this is now also written in the resulting .haf file
* OBD_II signals have been added
* New Wice Internal signals added
** WICE_Generic_Internal.Video_Camera_1
** WICE_Generic_Internal.Video_Camera_2
* Added possibility to change the type of recorder to DREC (Diagnostic Recorder) that allows the uploading of sequence files
* Now possible to monitor Wice Internal and OBD_II signals
* General bug fixes

=== SWDL .vbf progress bars ===
When uploading .vbf-files you will now be able to monitor the upload-progress using a progress bar.

=== Video in preview ===
You are now able to view video in the signal preview tool. This allows you to correlate video signals with regular signals. The preview tool will automatically tell you if your signal data has any video data correlated to it. [[Preview data|Click here if you would like to know more.]]

New features in v2.54

2019-10-18T13:08:55Z

Julian:

=== Improved vehicles tab performance ===
The vehicles tab has been significantly optimized. The search button has been removed as searches will now be performed automatically once any of the search fields are changed.

=== Resource group member history ===
You can now display the membership history of individual WCUs within a resource group by right clicking on a resource group in the vehicles panel and selecting "Member history".

=== Re-design of Dialogs for Managing Labels on Resources ===
The dialogs used to add and remove labels on resources, found when selecting the corresponding right-click option for resources in the [[Vehicles|Vehicles tab]], is re-designed in purpose and appearance. Read more about the new design [[Labels|here]].

=== Scheduling Added for CAN-recorder, IDC, Signal Reader and Video Tasks ===
From this version forward it is possible to schedule tasks of type CAN-recorder, IDC, Signal Reader and Video. This is done in the same manner as scheduling of SoH tasks, read more [[Creating a Task#CAN-recorder#Scheduling|here]].
=== Signal Reader Assignment Wizard extensions ===
Several new features have been implemented to the Haf file creator/Signal reader assignment wizard. They include:
* Now possible to sort by last edited date while browsing saved assignments
* If a CAN bus has frame format Extended, this is now also written in the resulting .haf file
* OBD_II signals have been added
* New Wice Internal signals added
** WICE_Generic_Internal.Video_Camera_1
** WICE_Generic_Internal.Video_Camera_2
* Added possibility to change the type of recorder to DREC (Diagnostic Recorder) that allows the uploading of sequence files
* Now possible to monitor Wice Internal and OBD_II signals
* General bug fixes

=== SWDL .vbf progress bars ===
When uploading .vbf-files you will now be able to monitor the upload-progress using a progress bar

=== Video in preview ===
You are now able to view video in the signal preview tool. This allows you to correlate video signals with regular signals. The preview tool will automatically tell you if your signal data has any video data correlated to it. [[Preview data|Click here if you would like to know more.]]

New features in v2.54

2019-10-18T12:00:04Z

Julian:

=== Resource group member history ===
You can now display the membership history of individual WCUs within a resource group by right clicking on a resource group in the vehicles panel and selecting "Member history".

=== Improved vehicles tab ===
The vehicles tab has been significantly optimized. The search button has been removed as searches will now be performed automatically once any of the search fields are changed.

=== Video in preview ===
You are now able to view video in the signal preview tool. This allows you to correlate video signals with regular signals. The preview tool will automatically tell you if your signal data has any video data correlated to it. [[Preview data|Click here if you would like to know more.]]

=== Signal Reader Assignment Wizard extensions ===
Several new features have been implemented to the Haf file creator/Signal reader assignment wizard. They include:
* Now possible to sort by last edited date while browsing saved assignments
* If a CAN bus has frame format Extended, this is now also written in the resulting .haf file
* OBD_II signals have been added
* New Wice Internal signals added
** WICE_Generic_Internal.Video_Camera_1
** WICE_Generic_Internal.Video_Camera_2
* Added possibility to change the type of recorder to DREC (Diagnostic Recorder) that allows the uploading of sequence files
* Now possible to monitor Wice Internal and OBD_II signals
* General bug fixes

=== Re-design of Dialogs for Managing Labels on Resources ===
The dialogs used to add and remove labels on resources, found when selecting the corresponding right-click option for resources in the [[Vehicles|Vehicles tab]], is re-designed in purpose and appearance. Read more about the new design [[Labels|here]].

=== Scheduling Added for CAN-recorder, IDC, Signal Reader and Video Tasks ===
From this version forward it is possible to schedule tasks of type CAN-recorder, IDC, Signal Reader and Video. This is done in the same manner as scheduling of SoH tasks, read more [[Creating a Task#CAN-recorder#Scheduling|here]].

New features in v2.54

2019-10-18T11:12:47Z

Julian:

=== Improved vehicles tab ===
The vehicles tab has been significantly optimized.

=== Video in preview ===
You are now able to view video in the signal preview tool. This allows you to correlate video signals with regular signals. The preview tool will automatically tell you if your signal data has any video data correlated to it. [[Preview data|Click here if you would like to know more.]]

=== Signal Reader Assignment Wizard extensions ===
Several new features have been implemented to the Haf file creator/Signal reader assignment wizard. They include:
* Now possible to sort by last edited date while browsing saved assignments
* If a CAN bus has frame format Extended, this is now also written in the resulting .haf file
* OBD_II signals have been added
* New Wice Internal signals added
** WICE_Generic_Internal.Video_Camera_1
** WICE_Generic_Internal.Video_Camera_2
* Added possibility to change the type of recorder to DREC (Diagnostic Recorder) that allows the uploading of sequence files
* Now possible to monitor Wice Internal and OBD_II signals
* General bug fixes

=== Re-design of Dialogs for Managing Labels on Resources ===
The dialogs used to add and remove labels on resources, found when selecting the corresponding right-click option for resources in the [[Vehicles|Vehicles tab]], is re-designed in purpose and appearance. Read more about the new design [[Labels|here]].

=== Scheduling Added for CAN-recorder, IDC, Signal Reader and Video Tasks ===
From this version forward it is possible to schedule tasks of type CAN-recorder, IDC, Signal Reader and Video. This is done in the same manner as scheduling of SoH tasks, read more [[Creating a Task#CAN-recorder#Scheduling|here]].

Quick Start

2019-10-18T09:24:11Z

Julian:

This chapter takes you on a tour to quickly get acquainted with the WICE Portal to see how it works.

As the WICE Portal is a web based tool there is no need to install any software on your computer. All you need is a web browser, such as Internet Explorer, which has Javascript enabled. Using the WICE Portal you can for example see which measurement assignments are running, check each assignment's respective status, get result files from measurement tasks, and much more.

In this quick start you will first be introduced to the basic model, and how it is supposed to work. Once the basics have been covered a simple scenario will be presented. This scenario will show how a task you have created is sent to a car and then started. How to access the data generated by a task will also be covered.

__TOC__

==Basic Conceptual Model==
[[File:Illustration1.png|alt=|thumb|Figure 1: This image shows how you the user, the WICE portal and the cars in the field are connected. As you see here you as the user access the WCUs and their cars through the portal.]][[File:Illustration2.png|thumb|Figure 2: This figure shows how a task, assignment and WCU correlates. As you see the task is connected with an unspecified amount of WCUs where the task will execute. The task is also connected to one of the nine assignment as its that assignment that the task will be running.|277x277px]]The basic functionality of the WICE portal is to manage so called ''tasks''. A task is an assignment to perform a specific action, typically collect measurement data from one or more cars. Tasks are created in the WICE portal and connected to a number of Wireless Communication Units (WCUs), which are in-vehicle units connected to the vehicles' internal communication buses. After a task has been created, the assignment is downloaded by each of the defined cars when ignition is turned on. Each WCU then runs the task's assignment, typically producing output in the shape of measurement data files, which are uploaded to the WICE portal. The user can then see the task's result on each WCU as the task's assignment will get different results depending on which WCU it ran on. To recap and illustrate how this works you can look at figure 1 and 2 explaining how this correlates.
[[File:A Simple Scenario.png|thumb|Figure 3: This is how a task can look when it is ready to be created.]]

==A Simple Scenario==
Now that we have gone through the concept of the WICE portal we will give a more concrete example. Let's say you want to create a task with a State of Health (SoH) assignment where you collect the mileage and battery voltage of a car. To do this you need to [[The Portal User View#Login|log in]] to the WICE portal with your WICE login (username and password).

Now that you are logged in you create a new task by clicking the "New Task" button at the bottom of the screen. When pressing the button a dialog will be shown with one tab for each type of assignment. To make the task a SoH task you click the SoH tab where the options for creating one will be shown. There you will at the top see six different checkboxes with different data items that SoH can collect. Check the boxes for voltage and mileage and scroll down to click "Add resources". A window will appear where we can search and add WCUs. You can search for a WCU by different criterea and when you have found the WCU(s) you wanted and have dragged them to the bottom box with the selected WCUs you press "Done". Now it should look like it does in figure 3 and you can now press "OK" to start the task. We don't need to fill the other boxes as we don't need a description, notification about status via email or schedule. That was a quick instruction on how to create a new task but you can read more detailed about how to create every sort of task at [[The Portal User View#Creating a Task|Creating a Task]].

When the task is done it will have generated results. You can find them by searching for the WCU(s) you used in the Tasks tab (on the home screen). When you have found the WCU and your assignment you can select it and press the "Get Result Files" in the bottom left corner. This will open a panel where you can search among the result files. When you have selected a file you gain access to multiple options. You can download the files (get files), plot the GPS data of the vehicle (plot route), preview the data files, or study the log files. There is more information about the Tasks tab and viewing results in [[The Portal User View#Tasks Tab|Tasks Tab]].

Quick Start

2019-10-18T09:24:01Z

Julian: Grammar and fixed some incorrect instructions

The Portal Administrator View

2019-10-18T07:41:33Z

Julian: Added link to extra bundles

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 assignments 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 Assignment]]
[[File:Illustration 32b.png|thumb|Force Stop Assignment]]

In addition to the functionality for an ordinary user, an administrator has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running Assignment" shows the "Stop assigment" button. This button is the same as for the ordinary user and is used to stop a running assignment. When a running assignment 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 Assignment" button, which can be seen in Figure "Force Stop Assignment", forces a "Stop pending" assignment into "Stopped" state without waiting for the stop signal from the WCU.

Also, the administrator can search and view any user's task.

==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|none|left|frame|The Administrator's Vehicles Tab]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|The Add 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". 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.

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

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

 

====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 "WCU" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Unit ID:
| The automatically generated unique WCU identifier. The ID cannot be changed from the portal.
|-
| style="font-weight: bold;" | Platform type:
| The WCU platform type.
|-
| style="font-weight: bold;" | Platform subtype:
| The WCU platform subtype.
|-
| style="font-weight: bold;" | WCU software version:
| This is the currently installed WCU software version.
|-
| style="font-weight: bold;" | Preferred WCU software:
| This is the new preferred WCU software version to be installed.
|-
| style="font-weight: bold;" | Perform reset on update:
| Removes all data on the WCU when installing a new WCU software.
|-
| style="font-weight: bold;" | MX4 firmware version:
| The currently installed MX4 firmware version.
|-
| style="font-weight: bold;" | 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]].

===== 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====
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 MCD-Hub and 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 car 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 car is turned off
|}

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

To edit the information about a car, press the “Edit Car” button. The dialog in Figure "Edit A 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. 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.

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 of all the selected cars at once. To do this, the dialog is extended as can be seen in Figure "Edit Several Cars".

<gallery widths="200px" heights="200px" mode="nolines">
File:Illustration37.png|Edit A Car
File:Illustration38.png|Edit Several Cars
</gallery>

===Upload a Car Import File===
It is possible to import a file that describes a set of cars. It can consist of both new cars and cars 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 car. The first line of the file must look as follows: 
'''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.

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

 

==Modules for the WCU==
[[File:Illustration40.png|400px|thumb|Handling 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:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader
# Video

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 "Handling Tool Configurations" there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

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 for both MCD-Hub and Canrecorder, press the “Reload” button.

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

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

===Configure the MCD-Hub Module===
The configuration for the MCD-Hub has only two settings. The first is the MCD-Hubs IP address and the second is the preferred firmware version. The other two configuration settings shown in Figure "Handling Tool Configurations" is “MCD-Hub firmware version” which shows the current version used by the hub 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 RP Module===
[[File:Illustration44.png|thumb|250px|Settings for the RP module]]

For this module it is only possible to configure modify the debug level, see Figure "Settings for the RP module". 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:Signal Reader Module.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 and UDP. Thereafter the monitoring rate for both cases is set using the "Interval"-field, where the default is once per second.

Further, the module settings include defining the debug level, the version of the generated MDF-file and determining appropriate values for the diagnostics timeout. The timeout values determine how long time the receiver is to wait for the diagnostic values before assuming that there are none. Typically, the timeout for sequence file diagnostics is set to a higher value due to the fact that this answer might require more time.

===Configure the Software Download Module===
[[File:Modules SWDL.png|thumb|250px|Settings for the Software Download Module]]
The state of health model has the same settings as the IDC module above apart from one difference highlighted in red in Figure "Settings for the Software Download Module". For WCUs of version 2.53 and forward it is possible to allow updates to be performed without manual interaction by checking the marked out checkbox. If this option is chosen, the updates will instead be performed as soon as possible.

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

===Configure the Uptime Module===
[[File:Illustration43.png|thumb|250px|Settings for the Uptime Module]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. 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 here [[WICE video]].

 

==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 car a specific WCU was in at the time an assignment was run can be done by connecting a car 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 cars, 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 car 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 car you drag the WCU you would like to connect onto the car in the right table. When you drop it onto a car a small icon will show signifying that the WCU and car 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]]
 
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 GDS/SDDB File Tab===
In order for the portal to be able to translate error codes into a human readable format, a GDS or SDDB file must be selected for a vehicle. The set of GDS/SDDB files to choose from is administered in this tab, see Figure "GDS/SDDB File View".

[[File:Illustration53.png|left|frame|GDS/SDDB File View]]
 

To upload a new GDS/SDDB file, press upload new file and you will be presented with dialog where you select the file, sets an optional name (if no name is entered, the file name is used) and an optional comment. To upload a new file for an existing entry, press the edit file button and you will be presented with a dialog where you can upload a new file. To edit the comment or the name that should show up when select which GDS/SDDB file to use for a vehicle, simply double click the cell and edit directly in the table.

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

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

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 Custom Car Types Tab ===

This tab is further described [[Custom Car Types|here]].

=== The Alarm Tab ===

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

===The User Tab===
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 eight columns are:

[[File:Illustration46.png|frame|none|left|User Administration Tab]]

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

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 assiginments, you will also be prompted about giving the user access to currently running assignments on these wcus as well. This can also be done when editing the roles of a user.
[[File:NewUserDialog252.png|left|thumb|New User Dialog]]
[[File:PromptNewUserCurAss.png|left|thumb|Prompt to give user permission to currently running assignments on specified wcus]]
 

====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 assignment permission to the user, you will also here be prompted about giving the user access to currently running assignments on these wcus as well.
[[File:EditUser252.png|left|thumb|Modify User Dialog]]
 

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

To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward 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]]
 

====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. More about these functions is found under [[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 WICE portal < 2.47:'''

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

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

Extra bundles

2019-10-18T07:38:02Z

Julian: New page about extra bundles

An "extra bundle" is an optional software that can be run directly on the WCU. By default, all WCUs contain the Mechanics GUI (mek-gui), which is a software that allows for basic diagnostics, and also shelving the WCU. If a user wants to install additional extra bundles then they may do so trough the "Edit configuration"-panel that can be accessed through the Vehicles-tab.

== Available extra bundles ==
Here is a condensed list of available extra bundles.
{| class="wikitable"
!Extra bundle name
!Short name
!Functionality
|-
|Blue Pirat client
|pirat
|
|-
|Mechanics GUI
|mek-gui
|Provides a GUI on port 4200 for basic WCU diagnostic, video camera calibration and shelving
|-
|NodeJS
|nodejs
|Platform upon which Javascrtipt-based web server applications can be run. Used by the "Mechanics GUI" and "WCU Status".
|-
|Softhub software
|softhub
|
|-
|WCU Status
|wcu-status-gui
|Provides a GUI on port 3000 for monitoring WCU health, assignments and Signal reader. Can be used to trigger SWDL.
|}

Preview data

2019-10-09T12:02:15Z

Julian: Fixed dated information about signal preview

[[File:Video-in-preview.png|thumb|400x400px|Figure 1:
The preview data window with integrated video support.
]]
This is a tool used to graph signal values from MDF-files, preview Video and visualize GPS-data.

== How to use ==
# Select a "Source" (file or measurement) from the source list on the left hand side of the screen
# A list of signals will show up in the signal list on the right hand side of the screen. Select one or more.
# Each selected signal will show up as a thumbnail at the bottom of the screen
# In order to inspect a signal more closely, double click or "drag and drop" the signal into the Master signal preview.
# If there is any GPS data available, then that data will be visualized in the map.
# If there is any video data available, then one or more blue fields labelled "video" will be visible in the plot window. To access the video, click on the blue field.

== Integrated video preview ==
To see what videos are available a signal needs to be selected and inserted into the master signal preview.

The preview tool will automatically detect if there is any video correlated to the currently selected file. If such video exists, then a blue field will show up in the plot that is labelled "Video". Such a field is visible in Figure 1. If you want to preview that video, simply click on the blue field. The video view will open, and the video will start playing. You can also click on the plot line inside of the video field to jump to an exact timestamp in the video. This means that if you wish to see what happened in the video when a certain signal peak occurred then you can click on that peak and the video will instantly jump to the correct timestamp.

== Integrated GPS data visualization ==
[[File:Map-in-preview.png|thumb|Figure 2:
The preview data window with integrated GPS data visualization
]]
By default the map will be set to display a plot, along side of a map. Once a signal is selected and pushed up into the mater signal preview any available GPS data will be visualized in the map. If you click on the plot line a marker will be placed in the map which indicates where the car was at that point in time.

== Y-axis scaling ==
By default the vertical axis is scaled based on a signals predetermined minimum and maximum values which are embedded into the MDF file. This has two advantages. Primarily it makes the same signal from two different measurements easier to compare, but it should also help display the signal using a scale that is relevant for that particular signal. There are however a set of circumstances in which this principle is abandoned in favor of auto fit:
* If the signal has no default min/max values
* If the signals min value is greater than its max value
* If the actual signal is outside of the predetermined min/max bounds.
* If the predetermined max is a lot higher than the actual max of the signal. This is to prevent the previewed signal from being displayed as nothing but a flat line at the bottom of the graph.
If any of these conditions are true, then the vertical min/max will be automatically fitted to the curve based on the curves extreme values.

== Plot toolbar ==

=== Preview modes ===
[[File:Preview-views.png|frameless]]

"Master signal preview" has four different preview modes which you can select from the bottom left corner of the "Master signal preview" window:
# View only one plot
# View two plots side by side
# View a plot, and video side by side
# View a plot and GPS data visualization side by side (this is the default view)

=== Window size ===
If you want to have a bigger "Master signal preview" you can press the fullscreen button on the bottom right of the Master signal preview window, or you can manually hide other areas you do not wish to see by pressing the "H" on them. To show the areas again you can press the "S".

=== Switching between plots ===
There are always two plots even though there might only be one shown. This means you can always use the button "Switch" to make the plots switch places. When there are two plots shown they switch positions but when there is only one plot shown the shown plot (the left one) will switch with the hidden plot (the right one). This can be useful when comparing signals.

=== Zooming ===
To zoom in on graphs you drag between two points(not necessarily data points) on the graf and it will zoom in between those two points.To zoom out you press "Reset zoom" for L or R depending on which plot you want to zoom out. Notice that "Zoom out (R)" is only clickable when you show two plots and that is because even if there always are two plots you can only zoom out and clear shown plots.

=== Statistics ===
You can see statistics for the plots and their signal(s) at the bottom under the tab "Statistics". To the left you have a button for if you want to show the left or right plot. What being showed is the plots signal and x/y min/max, mean value, standard devation, total amount of data samples and shown amount of data samples for each signal. Note that the plot can only show 500 samples for each signal and therefore need to hide samples for bigger signals. The plot will always try to have an as even as possible space between the samples and if it is showing a signal with 502 signals it will show 251 as it will give the smoothest and most accurate view even if its not showing as many samples as it could.

== Other features ==

=== Export options ===
At the bottom you can also download a plot as a text file. Under the tab "Data export" you select which plot you want to download, select between which time values it should download data points, set a download description (optional) and then press "To text file" to make the file ready for download. The text file you download is supported in Excel.

=== Saving signals ===
You can save the currently selected signals by pressing the signal symbol with a plus on it located on the bottom right of the "Signal List". This allows you to reload these signals in any source as long as that source contains signals with exactly matching names.

=== Quick selection mode ===
This selection mode allows you preview the same set of signals from an array of files with ease. Here is how it works:
# This requires you to have selected two or more files before you entered the signal preview interface.
# Beneath the source list to the left you will find a checkbox that says "Quick selection mode". Click it.
# Select a file by clicking on a file in the source list.
# Select any number of signals in the signal list.
# If you want to add any of the signals into the master preview, then do so by dragging and dropping (or double clicking) the thumbnails as usual.
# You can now swap between files by selecting any file you like from the source list. When you swap file the signals you selected previously will now be selected again in the new file.
'''Notice: This will only work if both files have signals with the exact same name. Any deviation in signal naming will cause the program to be unable to find the signal, thus skipping it and moving on to the next signal'''

File:Preview-views.png

2019-10-09T11:43:45Z

Julian:

...

File:Map-in-preview.png

2019-10-09T11:39:42Z

Julian:

Preview tool with map

File:Video-in-preview.png

2019-10-09T11:33:46Z

Julian:

preview tool

New features in v2.54

2019-10-01T07:37:37Z

Julian: Video in preview

=== Video in preview ===
You are now able to view video in the signal preview tool. This allows you to correlate video signals with regular signals. The preview tool will automatically tell you if your signal data has any video data correlated to it. [[Preview data|Click here if you would like to know more.]]

Vehicles

2019-09-25T11:17:27Z

Julian: /* Show the Vehicle Position */

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.

[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]

The number of possible columns to show is quite large (24). The columns shown below are in
default order. You will have to account for any changes you have made yourself. The columns
are:

{| class="wikitable"
| style="font-weight: bold;" | WCU ID
| The ID of the WCU. An example is MM-320:1
|-
| style="font-weight: bold;" | WCU Description
| A textual comment attached to the WCU.
|-
| style="font-weight: bold;" | Last DRO
| Says when the DRO log file was last transferred to the portal.
|-
| style="font-weight: bold;" | Last log
| Shows when the last log file was transferred to the portal.
|-
| style="font-weight: bold;" | Upload size
| Says what the size, in kilobytes, of the last data upload was.
|-
| style="font-weight: bold;" | Upload date
| Contains which date the last upload was done
|-
| style="font-weight: bold;" | Upload
| This column says how much data has been transferred from the WCU to the portal the last week.
|-
| style="font-weight: bold;" | Plate number
| The plate number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | VIN
| Shows the Vehicle Identification Number of the car where the WCU is mounted.
|-
| style="font-weight: bold;" | Voltage 
| The column shows the latest known battery voltage as reported by the CEM.
|-
| style="font-weight: bold;" | Mileage
| The column shows the mileage of the car.
|-
| style="font-weight: bold;" | Up-time
| Shows how many hours the WCU been running the last week.
|-
| style="font-weight: bold;" | Distance
| Shows the distance the car has been driven the last week.
|-
| style="font-weight: bold;" | Project Id
| Shows the project identification number.
|-
| style="font-weight: bold;" | Proto number
| Shows the proto number.
|-
| style="font-weight: bold;" | TSU
| Shows the TSU identifier.
|-
| style="font-weight: bold;" | WCU Version
| Shows which version the current WCU software has.
|-
| style="font-weight: bold;" | Connected
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.
|-
| style="font-weight: bold;" | GDS/SDDB
| The name of the GDS/SDDB file used when parsing SoH assignment data.
|-
| style="font-weight: bold;" | WCU voltage
| Shows the voltage as measured by the WCU.
|-
| style="font-weight: bold;" | WCU storage usage
| Shows the amount of storage available to store data on the WCU.
|-
| style="font-weight: bold;" | Series
| Shows the series attribute.
|-
|'''WCU name'''
|Shows the name of the WCU
|-
|'''Resource group'''
|The resource group (if any) the WCU is part of.
|-
|'''Platform type'''
|Only from v2.44: Search WCU by platform type.
|}

Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, click the “Save headers” button after you have selected your columns.

There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating assignments you can select a resource group instead of the individual WCU:s to start a new assignment. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.

When selecting a row in the table the selected row changes to a blue shade. You can modify
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.

==Show the Vehicle Position==
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in.

If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]].

==View Diagnostic Trouble Codes==
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]

If an SoH assignment has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle.
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".

==View ECU software==
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]
It is possible to see the ECU software number for each ECU in a vehicle.
Press the button “ECU SW” after you have selected one vehicle. The following view will be
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with
when it was read. You can download the list as a tab-separated text file if you press “Download”.

==Get WCU Up-time==
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.

Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.

From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].

==Export SoH Data==
[[File:Soh data export.png|frame|SoH Data Export Panel]]
You can export data from SoH assignments to your local computer by using the function
“Export SoH data”. Select the cars you are interested in as you can export for more than
one car in one export.
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage and storage usage.
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.

==Resource Groups==
WCUs and cars can collectively be referred to as "resources". As such they can be grouped
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only
one type of resource is in a resource group.

You identify a resource group by a gray arrow like icon to the left in the table row. If you
click the icon the entry opens up and makes room for showing which resources are part
of the resource group.

From version 2.42 the showing of the resource group's resources has been improved. More info can be found in [[Resource group's resources]].

When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a
resource group or not. If you select a resource group, the new assignment will be downloaded to all the WCUs that are part of the resource group.
As a regular user you can not create and remove resource groups, only an administrator
of the portal can do this.

From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.

This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.

Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".

==Modules==
If you have the right permission you will be able to view a WCU:s modules, and
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:

* Blue piraT
* Canrecorder
* DoIP
* ETAS
* GPS
* IDC
* MCD-Hub
* Rapid Prototyping (RP)
* Signal Reader
* SoftHub
* Software Download (SWDL)
* State of Health (SoH)
* Uptime
* Vinreader

New features in v2.53

2019-09-25T11:14:54Z

Julian: /* Improved all maps */

=== Rotating video ===
A new setting for the video module has been introduced to rotate the video, see [[Video module]].

=== Scheduling of SoH ===
A new scheduling feature is added for creating SoH tasks for WCUs of version >= 2.53. More information can be found [[Creating a Task#SoH|here]].

=== WCU Local Scheduling Time Zone ===
When scheduling a SoH task, one option is to use the local time zone of the WCU. For this to be enforced in practice, a time zone for the WCU needs to be defined by the use of Edit Configuration in the Vehicles tab, read more [[The Portal Administrator View#WCU Local Scheduling Time Zone|here]].

=== New setting for SWDL Module ===
For WCUs of version >= 2.53 it is possible to allow unattended upgrades by changing the corresponding module settings. Read more about this feature [[The Portal Administrator View#Configure the Software Download Module|here]].

=== Improved all maps ===
All tools that utilizes maps has been reconditioned. This includes the following tools:
* [[Preview data|MDF preview]]
* [[Plot Route|Plot route]]
* [[Show position|Show postion]]
* [[Monitor signals|Signal monitor]]
The functionality is mostly the same, but in some places the GUI has been polished to improve the user experience.

Show position

2019-09-25T11:14:01Z

Julian:

[[File:Sp.png|thumb|Show position displaying multiple resources simultaneously]]
The "Show position" tool allows you to follow a car/wcu in real-time.

==How to access this tool==
It can be accessed under the "Vehicles"-tab, at the bottom of the page. First, at least one vehicle row needs to be selected. Once a row has been selected the "Show position"-button becomes enabled, and you can click it to show the position of all currently selected resources.
==How it works==
It takes the last known position of each selected resource and plots it onto a map. The tool stores a short position history for each selected resource, which is visualized in the form of a colored trail following the current position of each selected resource.
==Usage==
To zoom in on the map you can either use the mouse scrolling-wheel while hovering over the map, or the +/- signs at the top left corner of the map.

To the right-hand side of the screen is a list of each selected resource.

=== Pan to a resource ===
You can pan to a resource by clicking on it in the list to the right

=== Follow a resource ===
if you double-click a resource in the list the view will keep that resource in view.

=== Resource information ===
At the bottom of the list you can choose if the list should display "WCU ID", Plate number or VIN. If you select a resource from the list the specifics of that resource will be listed underneath the list in the "Selected WCU"-form.

Plot Route

2019-09-25T11:01:09Z

Julian: Fixed headers

Show position

2019-09-25T10:59:51Z

Julian: Created page with "Multiple driving cars visible in "Show position""

[[File:Sp.png|thumb|Multiple driving cars visible in "Show position"]]

File:Sp.png

2019-09-25T10:59:02Z

Julian:

Show position in use

New features in v2.53

2019-09-25T09:19:57Z

Julian: Added link to plot route

=== Rotating video ===
A new setting for the video module has been introduced to rotate the video, see [[Video module]].

=== Scheduling of SoH ===
A new scheduling feature is added for creating SoH tasks for WCUs of version >= 2.53. More information can be found [[Creating a Task#SoH|here]].

=== WCU Local Scheduling Time Zone ===
When scheduling a SoH task, one option is to use the local time zone of the WCU. For this to be enforced in practice, a time zone for the WCU needs to be defined by the use of Edit Configuration in the Vehicles tab, read more [[The Portal Administrator View#WCU Local Scheduling Time Zone|here]].

=== New setting for SWDL Module ===
For WCUs of version >= 2.53 it is possible to allow unattended upgrades by changing the corresponding module settings. Read more about this feature [[The Portal Administrator View#Configure the Software Download Module|here]].

=== Improved all maps ===
All tools that utilizes maps has been reconditioned. This includes the following tools:
* MDF preview
* [[Plot Route|Plot route]]
* Show postion
* Signal monitor
The functionality is mostly the same, but in some places the GUI has been polished to improve the user experience.

Plot Route

2019-09-25T09:19:21Z

Julian: Updated with information about the new plot route tool (2.53)

==Plot Route==
[[File:Plot Route.png|thumb|Plotting where a car has been during the course of a week.]]

=== How to access this tool ===
If you are interested in seeing where the car was driven while making measurements you can use the “Plot route” tool. This tool can be accessed either by selecting and then right-clicking a task in the tasks panel. You can also access the tool from the bottom menu in both the tasks and vehicles panel.

=== How it works ===
An important detail to note is that plot route is a tool that operates using the data of a specific car. The tool will check which car you have selected. It will then aggregate the GPS-data of all the WCUs that has been installed in the car during the specified time period. This is the data that is plotted.

=== Usage ===

==== Car information ====
On the top right of the screen the "Car Information" panel displays the plate number, VIN and when the cars latest known GPS update occured.

==== Set date interval ====
In the side-menu to the right there is a "Set date interval" form. You can use this form to select an interval within which you wish you know where the car has been. '''This interval has a maximum length of one month''', and is by default set to the last known GPS update date. If you wish to change the interval, simply enter the date interval of your choice and click "update map".

==== Viewing the data ====
If you are having any trouble locating the data in the map you can utilize the "'''Fit all'''"-button. This button ensures that all position data is visible on the map by zooming out and panning to an appropriate location.

You can also use the date marker count-slider to increase the amount of detailed data points. These detailed data points contains specific time information which may help you determine when the car was in a specific position. You can also disable these date markers by clicking the "'''Disable date markers'''"-button directly below the slider.

File:Plot Route.png

2019-09-25T09:03:15Z

Julian:

Plotting where a car has been during a specific week.