WICE Wiki v2.95 - User contributions [en]

The Portal Administrator View

2020-12-18T13:39:27Z

Erika: /* The Administration Tab */

An administrator can do everything a user can do and more. In addition to what a normal user can do, an administrator can create and modify users and stop 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 the administrator can search and view any user's task. Also, it has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running 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.

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

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

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

[[File:42vehiclestab.png|thumb|left|800px|The Administrator's Vehicles Tab]]
 

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

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

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

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

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

You must supply all three files.

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

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

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

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

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

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



====Upload====

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

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

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

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

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

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
* '''Recording volume''', can be set to a value between 0 and 100, where default is 95.
The available monitoring settings are:
* '''Channels''', 1 (mono) or 2 (stereo). Default is 1.
* '''Codec''', LPCM, GSM or G.711. Default is LPCM (Linear PCM 16 bits per sample, 16 kHz).
* '''Destination IP address'''. This is the address to where the audio is sent for live monitoring.
* '''Enable monitoring'''. In order to monitor audio live for an audio 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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

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

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

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 ECU Diagnostics 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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

Shelve and Unshelve a WCU

2020-12-18T13:38:53Z

Erika:

<includeonly>=== Shelve and Unshelve a WCU ===</includeonly>
When a WCU is shelved it is disconnected from its car, if connected, and removed from its resource group, if any. In addition all active measure assignments are set to stopped pending and the system label ''shelving_in_progress'' is attached. This label will remain until all tasks for the WCU have status ''Stopped'' and all gathered measure data is uploaded to the portal after of which the label is replaced by the system label ''shelving_done''. In this final stage it is also possible to unshelve the WCU using the corresponding button and thus removing the ''shelving_done''-label. Note that when a WCU either has shelving in progress or is shelved it is no longer possible to add new measure assignments.

It is possible to "Unshelve" one or multiple WCUs using the "Unshelve"-button in the Vehicles-tab. If the choices does not apply to the set of selected resources the button is disabled. It is possible to unshelve a WCU from any of the existing shelving states; shelving in progress, shelved, shelving refurbish in progress or refurbished. Note that the user must have the role '''wcu:shelving:write''' to be able to perform this operation.

New features in v2.60

2020-10-30T15:04:14Z

Erika:

== Options added to WCU Configuration ==

New features have been added to both the WCU-tab and the IO-tab in the WCU Configuration-dialog. It is now possible to enable and disable the NTP server using a checkbox in the WCU tab and
in the IO-tab the diagnostic tester priority can be set to a value between 1-12. Read more about the new features [[The Portal Administrator View#Edit the WCU Configuration|here]].

== New section in the Signal Reader Module Settings ==

For WCUs of version >= 2.60 there is a new "Sampling"-section when defining the Signal Reader module settings. The checkbox "Record samples of change", previously found under "Measure Data Format", is moved here with the additional option to "Recorde one sample before change" if selected. In addition, it is possible to choose "Piecewise linear approximation". When doing so the error percentage of the signal range and the maximum number of samples for the segment. Read more about the Signal Reader module settings [[The Portal Administrator View#Configure the Signal Reader Module|here]].

== Resource group filter in the Alarms tab ==

It is from this version forward possible to search for alarms for WCUs based on their resource group. To do so, enter the resource identifier *rg::* followed by the *full* name of the resource group in question. It is also possible to select a resource group in the Vehicles tab and use the context menu option "Go to Alarms". Read more about the Alarms panel [[Alarm|here]].

== Removing all result files for a task ==
From this version forward it is possible for administrators to remove all result files for a task selected in the Tasks tab. Read more about the administrator specifics in the Tasks tab [[The_Portal_Administrator_View#The_Tasks_Tab|here]].

The Portal Administrator View

2020-10-30T15:01:09Z

Erika: /* The Tasks Tab */

An administrator can do everything a user can do and more. In addition to what a normal user can do, an administrator can create and modify users and stop 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 the administrator can search and view any user's task. Also, it has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running 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.

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

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

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

[[File:42vehiclestab.png|thumb|left|800px|The Administrator's Vehicles Tab]]
 

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

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

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

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

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

You must supply all three files.

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

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

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

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

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

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



====Upload====

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

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

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

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

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

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

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

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

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

The Portal Administrator View

2020-10-30T13:08:08Z

Erika: /* The Tasks Tab */

An administrator can do everything a user can do and more. In addition to what a normal user can do, an administrator can create and modify users and stop 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 the administrator can search and view any user's task. Also, it has one more button present. An administrator can send a ''Force Stop'' command to any WCU.

Figure "Stopping Running 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.

For a portal of version 2.60 and forward, it is also possible for an administrator to remove all resultfiles for a selected task using the corresponding context menu option. When doing so, a confirmation dialog pops up to ensure that that is in fact the intended choice.

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

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

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

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

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

You must supply all three files.

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

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

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

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

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

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



====Upload====

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

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

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

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

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

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

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

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

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

WCU Uptime

2020-10-30T12:35:51Z

Erika: /* Get uptime for a period of time */

[[File:Wcu uptime1.png|thumb|WCU Uptime Window]]
<includeonly>== WCU Uptime ==</includeonly>
The uptime of a WCU can now be tracked in minute resolution. To show the uptime for a WCU, you can either right click on the WCU in the Vehicles tab and select "WCU status" or select the WCU and then click on the "WCU status" button located in the bottom line of the Vehicles tab. The window in Figure "WCU Uptime Window" will then be visible.

When the "WCU Status" window opens it will by default show the uptime for the last seven days. If the WCU did not record any uptime during this period, the "WCU status" will look an additional seven days backwards in time until it finds an uptime sequence.

To view uptime sequences prior to the last uptime sequence, the user can step to the left on the time axis using the "left" arrow button and "fast rewind" button located in the bottom left corner of the window. Clicking the "left" button will result in stepping one uptime sequence backwards. Clicking the "fast rewind" button results in stepping 10 sequences backwards. By default when stepping backwards the number of visible uptime sequences will always be the same. In other words, if you have only one sequence visible as in Figure "WCU Uptime Window" and then clicks the "left" button this results in only showing the uptime sequence prior to current one. This can be changed by unchecking the "Preserve duration" checkbox located above the uptime chart. When having this checkbox unchecked, the result of a backward step on the time axis will result in the new uptime sequences being appended to the currently visible sequences.

Example: If only one uptime sequence is visible and we click the "left" button while having "Preserve duration" unchecked, this results in two uptime sequences after the result has been fetched from the server.

The "right" button and the "fast forward" button work the opposite way unless we are on the last uptime sequence as in Figure "WCU Uptime Window".
[[File:Wcu uptime2.png|thumb|WCU Uptime Interval Search]]

=== Get uptime for a period of time ===
Instead of stepping backwards on the time axis it is possible to display all uptime sequences for a period of time. In the Figure "WCU Uptime Interval Search" we have searched for uptime between 2018-11-01 and 2018-11-28. This search will be inclusive, i.e. if the from or to date is in the middle of an uptime sequence it will include the entire uptime sequence. This is for instance the case in the forementioned figure, where the entered from date is in the middle of the marked uptime sequence and the search is therefore extended to include its alive date; 2018-10-31.

=== Zoom in and zoom out ===
To zoom in the chart you can simply mark the area of interest by drag-and-drop, as illustrated in Figure "WCU Uptime Zoom". This can be done several times and to completely reset the zoom, press the "Reset zoom"-button in the upper right corner in the graph, see Figure "WCU Uptime Reset Zoom". It is also possible to use the stepping arrows based on the zoomed interval. However, after doing so a new search is performed and it is no longer possible to reset the zoom.

 
<gallery widths="400" heights="200" mode="nolines">
File:WCU uptime zoom.png|thumb|WCU Uptime Zoom
File:WCU uptime reset zoom.png|thumb|WCU Uptime Reset Zoom
</gallery>

 

=== Real-time monitoring ===
The WCU status window can also be used to monitor if the WCU is currently up and running. To enable this, check "Enable realtime data" located above the main chart. When enabled, any uptime for the last 24h will be fetched and displayed. Additionally, the server will be asked for new uptime data every minute and any new data will be added to the current result. Since the WCU uploads its uptime data every 5 minutes, it can take up to 5 minutes before any results are visible in the WCU status window.

=== Additional features ===
* The display unit can be changed from minutes (default) to hours or days. If changing to hours, 160 minutes will be displayed as 02:40 (hh:mm).
* When real-time monitoring, the WCU status window can be sent to a new browser window using the little arrow located to left of the minimize-maximize buttons in the upper right corner of the window.

File:Wcu uptime2.png

2020-10-30T12:13:30Z

Erika: Erika uploaded a new version of File:Wcu uptime2.png

WCU Uptime

2020-10-30T08:37:04Z

Erika: /* Zoom in and zoom out */

[[File:Wcu uptime1.png|thumb|WCU Uptime Window]]
<includeonly>== WCU Uptime ==</includeonly>
The uptime of a WCU can now be tracked in minute resolution. To show the uptime for a WCU, you can either right click on the WCU in the Vehicles tab and select "WCU status" or select the WCU and then click on the "WCU status" button located in the bottom line of the Vehicles tab. The window in Figure "WCU Uptime Window" will then be visible.

When the "WCU Status" window opens it will by default show the uptime for the last seven days. If the WCU did not record any uptime during this period, the "WCU status" will look an additional seven days backwards in time until it finds an uptime sequence.

To view uptime sequences prior to the last uptime sequence, the user can step to the left on the time axis using the "left" arrow button and "fast rewind" button located in the bottom left corner of the window. Clicking the "left" button will result in stepping one uptime sequence backwards. Clicking the "fast rewind" button results in stepping 10 sequences backwards. By default when stepping backwards the number of visible uptime sequences will always be the same. In other words, if you have only one sequence visible as in Figure "WCU Uptime Window" and then clicks the "left" button this results in only showing the uptime sequence prior to current one. This can be changed by unchecking the "Preserve duration" checkbox located above the uptime chart. When having this checkbox unchecked, the result of a backward step on the time axis will result in the new uptime sequences being appended to the currently visible sequences.

Example: If only one uptime sequence is visible and we click the "left" button while having "Preserve duration" unchecked, this results in two uptime sequences after the result has been fetched from the server.

The "right" button and the "fast forward" button work the opposite way unless we are on the last uptime sequence as in Figure "WCU Uptime Window".
[[File:Wcu uptime2.png|thumb|WCU Uptime Interval Search]]

=== Get uptime for a period of time ===
Instead of stepping backwards on the time axis it is possible to display all uptime sequences for a period of time. In the Figure "WCU Uptime Interval Search" we have searched for uptime between 2018-07-01 and 2018-11-30. What is important to note is that we only show charts in their entirety. This means that when we search for a start date (e.g. 2018-07-01) the server tries to find the nearest date to this date when the WCU went alive. The found date could be exactly the provided start date but can also be as in Figure "WCU Uptime Interval Search" 2018-06-30 which is the neerest date for recorded uptime. In the case of a long uptime sequence that starts before the provided start date but stretches over and ends after the start date, this sequence may not always be visible due to the "find nearest date" mentioned above. If one is interested to see if the WCU was up at a particular date one strategy is to have this date between the start date and end date to ensure it will be included. Another strategy is to get the uptime for a period as in "WCU Uptime Interval Search" and then step backwards or forwards to even include the nearest uptime sequences that did not match the search query.
=== Zoom in and zoom out ===
To zoom in the chart you can simply mark the area of interest by drag-and-drop, as illustrated in Figure "WCU Uptime Zoom". This can be done several times and to completely reset the zoom, press the "Reset zoom"-button in the upper right corner in the graph, see Figure "WCU Uptime Reset Zoom". It is also possible to use the stepping arrows based on the zoomed interval. However, after doing so a new search is performed and it is no longer possible to reset the zoom.

 
<gallery widths="400" heights="200" mode="nolines">
File:WCU uptime zoom.png|thumb|WCU Uptime Zoom
File:WCU uptime reset zoom.png|thumb|WCU Uptime Reset Zoom
</gallery>

 

=== Real-time monitoring ===
The WCU status window can also be used to monitor if the WCU is currently up and running. To enable this, check "Enable realtime data" located above the main chart. When enabled, any uptime for the last 24h will be fetched and displayed. Additionally, the server will be asked for new uptime data every minute and any new data will be added to the current result. Since the WCU uploads its uptime data every 5 minutes, it can take up to 5 minutes before any results are visible in the WCU status window.

=== Additional features ===
* The display unit can be changed from minutes (default) to hours or days. If changing to hours, 160 minutes will be displayed as 02:40 (hh:mm).
* When real-time monitoring, the WCU status window can be sent to a new browser window using the little arrow located to left of the minimize-maximize buttons in the upper right corner of the window.

WCU Uptime

2020-10-30T08:32:20Z

Erika: /* Zoom in and zoom out */

[[File:Wcu uptime1.png|thumb|WCU Uptime Window]]
<includeonly>== WCU Uptime ==</includeonly>
The uptime of a WCU can now be tracked in minute resolution. To show the uptime for a WCU, you can either right click on the WCU in the Vehicles tab and select "WCU status" or select the WCU and then click on the "WCU status" button located in the bottom line of the Vehicles tab. The window in Figure "WCU Uptime Window" will then be visible.

When the "WCU Status" window opens it will by default show the uptime for the last seven days. If the WCU did not record any uptime during this period, the "WCU status" will look an additional seven days backwards in time until it finds an uptime sequence.

To view uptime sequences prior to the last uptime sequence, the user can step to the left on the time axis using the "left" arrow button and "fast rewind" button located in the bottom left corner of the window. Clicking the "left" button will result in stepping one uptime sequence backwards. Clicking the "fast rewind" button results in stepping 10 sequences backwards. By default when stepping backwards the number of visible uptime sequences will always be the same. In other words, if you have only one sequence visible as in Figure "WCU Uptime Window" and then clicks the "left" button this results in only showing the uptime sequence prior to current one. This can be changed by unchecking the "Preserve duration" checkbox located above the uptime chart. When having this checkbox unchecked, the result of a backward step on the time axis will result in the new uptime sequences being appended to the currently visible sequences.

Example: If only one uptime sequence is visible and we click the "left" button while having "Preserve duration" unchecked, this results in two uptime sequences after the result has been fetched from the server.

The "right" button and the "fast forward" button work the opposite way unless we are on the last uptime sequence as in Figure "WCU Uptime Window".
[[File:Wcu uptime2.png|thumb|WCU Uptime Interval Search]]

=== Get uptime for a period of time ===
Instead of stepping backwards on the time axis it is possible to display all uptime sequences for a period of time. In the Figure "WCU Uptime Interval Search" we have searched for uptime between 2018-07-01 and 2018-11-30. What is important to note is that we only show charts in their entirety. This means that when we search for a start date (e.g. 2018-07-01) the server tries to find the nearest date to this date when the WCU went alive. The found date could be exactly the provided start date but can also be as in Figure "WCU Uptime Interval Search" 2018-06-30 which is the neerest date for recorded uptime. In the case of a long uptime sequence that starts before the provided start date but stretches over and ends after the start date, this sequence may not always be visible due to the "find nearest date" mentioned above. If one is interested to see if the WCU was up at a particular date one strategy is to have this date between the start date and end date to ensure it will be included. Another strategy is to get the uptime for a period as in "WCU Uptime Interval Search" and then step backwards or forwards to even include the nearest uptime sequences that did not match the search query.
=== Zoom in and zoom out ===
To zoom in the chart you can simply mark the area of interest by drag-and-drop, as illustrated in Figure "WCU Uptime Zoom". This can be done several times and to trace back your step you simply press the "Zoom out"-button. If you want to completely reset your zoom, press "Reset zoom".

 
<gallery widths="400" heights="200" mode="nolines">
File:WCU uptime zoom.png|thumb|WCU Uptime Zoom
File:WCU uptime reset zoom.png|thumb|WCU Uptime Reset Zoom
</gallery>

 

=== Real-time monitoring ===
The WCU status window can also be used to monitor if the WCU is currently up and running. To enable this, check "Enable realtime data" located above the main chart. When enabled, any uptime for the last 24h will be fetched and displayed. Additionally, the server will be asked for new uptime data every minute and any new data will be added to the current result. Since the WCU uploads its uptime data every 5 minutes, it can take up to 5 minutes before any results are visible in the WCU status window.

=== Additional features ===
* The display unit can be changed from minutes (default) to hours or days. If changing to hours, 160 minutes will be displayed as 02:40 (hh:mm).
* When real-time monitoring, the WCU status window can be sent to a new browser window using the little arrow located to left of the minimize-maximize buttons in the upper right corner of the window.

WCU Uptime

2020-10-30T08:22:03Z

Erika:

[[File:Wcu uptime1.png|thumb|WCU Uptime Window]]
<includeonly>== WCU Uptime ==</includeonly>
The uptime of a WCU can now be tracked in minute resolution. To show the uptime for a WCU, you can either right click on the WCU in the Vehicles tab and select "WCU status" or select the WCU and then click on the "WCU status" button located in the bottom line of the Vehicles tab. The window in Figure "WCU Uptime Window" will then be visible.

When the "WCU Status" window opens it will by default show the uptime for the last seven days. If the WCU did not record any uptime during this period, the "WCU status" will look an additional seven days backwards in time until it finds an uptime sequence.

To view uptime sequences prior to the last uptime sequence, the user can step to the left on the time axis using the "left" arrow button and "fast rewind" button located in the bottom left corner of the window. Clicking the "left" button will result in stepping one uptime sequence backwards. Clicking the "fast rewind" button results in stepping 10 sequences backwards. By default when stepping backwards the number of visible uptime sequences will always be the same. In other words, if you have only one sequence visible as in Figure "WCU Uptime Window" and then clicks the "left" button this results in only showing the uptime sequence prior to current one. This can be changed by unchecking the "Preserve duration" checkbox located above the uptime chart. When having this checkbox unchecked, the result of a backward step on the time axis will result in the new uptime sequences being appended to the currently visible sequences.

Example: If only one uptime sequence is visible and we click the "left" button while having "Preserve duration" unchecked, this results in two uptime sequences after the result has been fetched from the server.

The "right" button and the "fast forward" button work the opposite way unless we are on the last uptime sequence as in Figure "WCU Uptime Window".
[[File:Wcu uptime2.png|thumb|WCU Uptime Interval Search]]

=== Get uptime for a period of time ===
Instead of stepping backwards on the time axis it is possible to display all uptime sequences for a period of time. In the Figure "WCU Uptime Interval Search" we have searched for uptime between 2018-07-01 and 2018-11-30. What is important to note is that we only show charts in their entirety. This means that when we search for a start date (e.g. 2018-07-01) the server tries to find the nearest date to this date when the WCU went alive. The found date could be exactly the provided start date but can also be as in Figure "WCU Uptime Interval Search" 2018-06-30 which is the neerest date for recorded uptime. In the case of a long uptime sequence that starts before the provided start date but stretches over and ends after the start date, this sequence may not always be visible due to the "find nearest date" mentioned above. If one is interested to see if the WCU was up at a particular date one strategy is to have this date between the start date and end date to ensure it will be included. Another strategy is to get the uptime for a period as in "WCU Uptime Interval Search" and then step backwards or forwards to even include the nearest uptime sequences that did not match the search query.
=== Zoom in and zoom out ===
[[File:WCU uptime zoom.png|thumb|WCU Uptime Zoom]]
[[File:WCU uptime reset zoom.png|thumb|WCU Uptime Reset Zoom]]
To zoom in the chart you can simply mark the area of interest by drag-and-drop, as illustrated in Figure "WCU Uptime Zoom". This can be done several times and to trace back your step you simply press the "Zoom out"-button. If you want to completely reset your zoom, press "Reset zoom".

=== Real-time monitoring ===
The WCU status window can also be used to monitor if the WCU is currently up and running. To enable this, check "Enable realtime data" located above the main chart. When enabled, any uptime for the last 24h will be fetched and displayed. Additionally, the server will be asked for new uptime data every minute and any new data will be added to the current result. Since the WCU uploads its uptime data every 5 minutes, it can take up to 5 minutes before any results are visible in the WCU status window.

=== Additional features ===
* The display unit can be changed from minutes (default) to hours or days. If changing to hours, 160 minutes will be displayed as 02:40 (hh:mm).
* When real-time monitoring, the WCU status window can be sent to a new browser window using the little arrow located to left of the minimize-maximize buttons in the upper right corner of the window.

File:WCU uptime reset zoom.png

2020-10-30T08:21:19Z

Erika:

WCU uptime reset zoom

File:WCU uptime zoom.png

2020-10-30T08:17:16Z

Erika:

WCU uptime zoom

File:Wcu uptime2.png

2020-10-30T08:13:54Z

Erika: Erika uploaded a new version of File:Wcu uptime2.png

File:Wcu uptime1.png

2020-10-30T08:12:34Z

Erika: Erika uploaded a new version of File:Wcu uptime1.png

New features in v2.60

2020-10-29T14:31:08Z

Erika:

New features in v2.60

2020-10-29T14:30:56Z

Erika:

Alarm

2020-10-29T14:25:22Z

Erika:

<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. To further inspect the resource for which the alarm occurred it is possible to base a search in the vehicle- or task tab using a right click option. 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. 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''. The currently existing identifiers in the alarm-tab are ''wcu::'' and ''rg::'', the last of which can be used to search out all alarms for the WCUs currently included in the named resource group.

'''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. Here it is possible to restrict the search to a specified time interval by checking the boxes "'''From'''" and "''''To'''". It is also possible to only select one of the two thus searching for all alarms from a certain date or after a date. However, if the "'''To'''"-option is selected this means that the automatic update of alarms is temporarily switched off, which is notified with a warning icon. In addition, you can 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 ===
[[File:Alarm acknowledge.png|thumb|200px|Comment dialog]]
When alarm is 'taken care of' you can acknowledge this by pressing the button 'Acknowledge alarm'. When doing so a dialog pops up providing to opportunity of adding a comment, presented in Figure 'Comment dialog'. If there is no need to comment, simply leave the field empty and save. The alarm is thereafter marked as 'acknowledged' with the remark A and if a comment is added it is also 'commented' with the remark C. To view the existing comments for an acknowledged alarm, or to add new comments, mark it in the table and press the button 'Show comment'. This will result in a panel appearing to the right of the table as can be seen in Figure 'Comment history panel'.

[[File:Alarm comment panel.png|thumb|left|600px|Comment history panel]]
 

The existing comments for the alarm is presented in a list in reversed chronological order along with date and user. To add a new comment press the 'Add new'-button at the bottom of the panel. The panel can be hidden again by either pressing the 'Hide'-button at the bottom of the panel or the 'Hide comment' button at the bottom of the alarm table.

=== Search alarm ===
The alarms are presented in pages with 50 hits in each which are stepped through by the use of the arrow buttons at the bottom of the panel. To narrow down the search result, specify dates using the "'''From'''" and "'''To'''" options above the table and/o by entering search expressions for the resource, message, severity and category columns. When entering a value in one of these columns, it is interpreted as a regular expression and a search is performed. However, to search for alarms for WCUs included in a specified resource group, using the resource identifier ''rg::,'' the full name of the resource group needs to be entered. When the automatic update is run, or if the "'''Update alarms'''"-button is pressed, the new alarms which fit into the currently selected page, with search expression and ordering taken into consideration, is incorporated into the page content. If there exist new alarms which do not fit into the currently selected page an information icon appears on the "'''Update alarms'''"-button. It will disappear either when you choose to press the button, switch page or when the next automatic update is run and there are no new alarms outside the page.

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

=== Block alarms ===
Sometimes it might not be relevant to show all existing alarms in the portal. For instance, when an alarm is being handled but is not yet ready to be acknowledged. In such cases it is possible to block a set of alarms which fulfill certain requirements using the red alarm block icon in the right bottom corner of the table, see Figure "Block alarm for WCU". To block alarms for one specific WCU, select it in the grid before pressing this button. The appearing window lists all existing alarm blocks. To create a new blockage, press "Block alarms" and enter the conditions in the appearing dialog, an example of which is presented in Figure "New alarm block".

[[File:Block alarm.png|thumb|400px|Block alarm for WCU]]
[[File:New alarm block.png|thumb|left|150px|New alarm block]]
 

Alarms can be blocked for a specific WCU, selected in the grid, or for all WCUs. If the logged in user is an administrator, the blockage can be put in place for all users or for the current user. If this is not the case, the user options are hidden and alarms can then only be blocked for that user. Additionally, it is possible to select one or several severeties and/or categories to block. If no severity and/or category is selected the alarms of all severities/categories will be blocked. End with naming the alarm block and save it. It will now appear in the list as presented in Fiugre "Block alarm list" and from here it is possible to edit or delete it. Edit the block by either double-clicking the list tile or by pressing the pen icon. To delete it simply press the green alarm button.

[[File:Block alarms list.png|thumb|left|150px|Block alarm list]]
 

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

New features in v2.60

2020-10-29T10:42:46Z

Erika:

New features in v2.60

2020-10-29T10:42:21Z

Erika:

New features in v2.60

2020-10-29T10:41:31Z

Erika:

The Portal Administrator View

2020-10-29T10:34:40Z

Erika:

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

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

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

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

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

You must supply all three files.

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

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

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

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

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

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



====Upload====

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

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

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

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

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

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

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

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

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

File:Modules Signal-Reader.png

2020-10-29T10:32:13Z

Erika: Erika uploaded a new version of File:Modules Signal-Reader.png

The Portal Administrator View

2020-10-29T10:30:37Z

Erika:

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

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

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

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

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

You must supply all three files.

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

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

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

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

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

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



====Upload====

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

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

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

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

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

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

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

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

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

File:Modules Signal-Reader.png

2020-10-29T09:39:16Z

Erika: Erika uploaded a new version of File:Modules Signal-Reader.png

I/O configurations

2020-10-28T16:01:52Z

Erika:

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

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

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

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

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

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

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

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

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

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

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

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

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is added for WCUs of version 2.49 or later and it includes the option of whether or not to set digital out 3 on boot. For WCUs of version later than or equal to 2.60 it is also possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

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

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

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

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

File:WCU conf io car interf.png

2020-10-28T16:01:32Z

Erika:

WCU conf io car interf

I/O configurations

2020-10-28T16:00:41Z

Erika:

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

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

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

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

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

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

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

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

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

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

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

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

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is added for WCUs of version 2.49 or later and it includes the option of whether or not to set digital out 3 on boot. For WCUs of version later than or equal to 2.60 it is also possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

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

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

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

==Show Vehicle Profile==
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.

I/O configurations

2020-10-28T15:49:02Z

Erika: /* The Miscellaneous Section */

I/O configurations

2020-10-28T15:48:50Z

Erika: /* The Miscellaneous Section */

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

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

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

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

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

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

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

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

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

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

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

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

==The Miscellaneous Section==
[[File:WCU conf io misc.png|thumb|Miscellaneous]]
This section is added for WCUs of version 2.49 or later and it includes the option of whether or not to set digital out 3 on boot. For WCUs of version later than or equal to 2.60 it is also possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".

 

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

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

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

I/O configurations

2020-10-28T15:48:12Z

Erika:

File:WCU conf io misc.png

2020-10-28T15:46:24Z

Erika:

WCU conf io misc

I/O configurations

2020-10-28T15:44:36Z

Erika: /* The Miscellaneous Section */

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

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

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

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

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

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

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

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

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

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

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

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

==The Miscellaneous Section==
This section is added for WCUs of version 2.49 or later and it includes the option of whether or not to set digital out 3 on boot. For WCUs of version later than or equal to 2.60 it is also possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected.

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

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

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

I/O configurations

2020-10-28T15:35:34Z

Erika:

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

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

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

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

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

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

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

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

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

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

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

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

==The Miscellaneous Section==
This section includes the option of whether or not to set digital out 3 on boot.

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

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

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

I/O configurations

2020-10-28T15:24:15Z

Erika:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

File:WCU conf io eth channels.png

2020-10-28T15:23:24Z

Erika:

WCU conf io eth channels

File:WCU conf io can channels.png

2020-10-28T15:22:39Z

Erika:

WCU conf io can channels

File:Io config3.png

2020-10-28T15:15:10Z

Erika: Erika uploaded a new version of File:Io config3.png

File:Io config2.png

2020-10-28T15:14:32Z

Erika: Erika uploaded a new version of File:Io config2.png

New features in v2.60

2020-10-28T14:09:05Z

Erika:

New features in v2.60

2020-10-28T14:08:20Z

Erika:

New features in v2.60

2020-10-28T14:06:07Z

Erika:

== Options added to WCU Configuration ==

In this version of the portal, new features have been added to both the WCU-tab and the IO-tab in the WCU Configuration-dialog. It is now possible to enable and disable the NTP server using a checkbox in the WCU tab.

The Portal Administrator View

2020-10-28T13:44:43Z

Erika: /* WCU */

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

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

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

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

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

You must supply all three files.

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

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

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

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

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

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



====Upload====

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

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

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

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

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

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

Also here it is possible to define the debug level. Further, the module settings include selecting to record samples on change, whether or not the MDF-files are to be written upon recorder stop and the version of the generated MDF-file. Thereafter you can select whether to aggregate ReadDataByIdentifier (service 22) diagnostic requests and which channel that should be used as the default CAN diagnostics channel. It is also possible to enter appropriate values for the diagnostics timeout. The timeout values determine how long time to wait for diagnostic responses before assuming that there are none. Typically, the timeout for sequence file diagnostics is set to a higher value due to the fact that it doesn't negatively impact the update frequency of active (diagnostics) signals.

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

The Portal Administrator View

2020-10-28T13:42:03Z

Erika: /* WCU */

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

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

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

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

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

===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|180px|thumb|Selecting Tool Configurations]]
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# 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 "Selecting Tool Configurations" there are a set of tools present where each type is grouped on the left side using a stack panel. Show the Signal Reader settings by selecting the Signal Reader stack and select the Canrecorder stack to see the canrecorder settings and so forth.

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

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

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

When a module is selected, or reloaded, it will say "No settings saved". In this mode the save-button is disabled and it will not be enabled until one of the settings is edited. Then the message "Settings not saved" appears until the save button is pressed. When the configuration is successfully saved, the status is updated to "Settings saved" and the Save-button is once again disabled. In addition, if there is a pending upgrade of the tool, this also will be indicated below the configuration panel.

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

The available recording settings are:
* '''Device''', can be set to internal or USB, where default is internal
* '''Channels''', can be set to either 1 (mono) or 2 (stereo), default is 2
* '''Sample rate''', can be set to 48000, 44100, 16000 or 8000. Default is 48000. The unit is Hz.
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. 

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

=== Configure the Blue piraT Module ===
As of version 2.44 of the 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 is “MCD-Hub firmware version” which shows the current version used by the hub. The other two configuration settings are the preferred firmware version and the second is “Last configuration update date” which states when the MCD-Hubs current configuration was brought into action.
When you are done with your configuration you save it by pressing the “Save” button. If you for any reason need to reload the configuration, press the “Reload” button.

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

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

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

Also here it is possible to define the debug level. Further, the module settings include selecting to record samples on change, whether or not the MDF-files are to be written upon recorder stop and the version of the generated MDF-file. Thereafter you can select whether to aggregate ReadDataByIdentifier (service 22) diagnostic requests and which channel that should be used as the default CAN diagnostics channel. It is also possible to enter appropriate values for the diagnostics timeout. The timeout values determine how long time to wait for diagnostic responses before assuming that there are none. Typically, the timeout for sequence file diagnostics is set to a higher value due to the fact that it doesn't negatively impact the update frequency of active (diagnostics) signals.

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

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

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

===Configure the Software Download Module===

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

[[File:Modules SWDL.png|thumb|left|250px|Settings for the Software Download Module]]
 

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

===Configure the Uptime Module===

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

[[File:Illustration43.png|thumb|left|250px|Settings for the Uptime Module]]
 

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 Vehicle Profiles Tab ===

This tab is further described [[Vehicle Pofiles|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 below will appear. It is pretty straightforward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

[[File:Illustration49.png|thumb|frame|left|Change Password Dialog]]
 

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

2020-06-26T12:32:53Z

Erika: /* Alarm tab updates */

== New features for SWDL tasks ==
* For WCU:s with version >= 2.59 it is possible to choose to ignore checksums by checking a corresponding checkbox. A similar option can also be used too disable pre-programming.
* The software part type for each VBF-file is now presented next to the ECU- and file name
* In the ECU PIN code table, a column is added displaying the number of files uploaded per ECU

Read more about creating a SWDL task [[The Portal User View#SWDL|here]].

== Alarm tab updates ==
The search feature in the Alarm tab is updated to a pagewise presentation where the search is specified by a "From"- and/or "To"-date, resource, message, severity and/or category expressions. The search is immediate when an expression is altered and it can also be triggered by the use of the "Reload alarms"-button. Read more about the new features [[Alarm|here]]. Also, the icons for blocking and unblocking alarms have bee updated.

New features in v2.59

2020-06-26T12:32:28Z

Erika:

== New features for SWDL tasks ==
* For WCU:s with version >= 2.59 it is possible to choose to ignore checksums by checking a corresponding checkbox. A similar option can also be used too disable pre-programming.
* The software part type for each VBF-file is now presented next to the ECU- and file name
* In the ECU PIN code table, a column is added displaying the number of files uploaded per ECU

Read more about creating a SWDL task [[The Portal User View#SWDL|here]].

== Alarm tab updates ==
The search feature in the Alarm tab is updated to a pagewise presentation where the search is specified by a "From"- and/or "To"-date, resource, message, severity and/or category expressions. The search is immediate when an expression is altered and it can also be triggered by the use of the "Reload alarms"-button. Read more about the new features here. Also, the icons for blocking and unblocking alarms have bee updated.

Alarm

2020-06-26T12:25:55Z

Erika: /* Search alarm */

<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. To further inspect the resource for which the alarm occurred it is possible to base a search in the vehicle- or task tab using a right click option. 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. 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. Here it is possible to restrict the search to a specified time interval by checking the boxes "'''From'''" and "''''To'''". It is also possible to only select one of the two thus searching for all alarms from a certain date or after a date. However, if the "'''To'''"-option is selected this means that the automatic update of alarms is temporarily switched off, which is notified with a warning icon. In addition, you can 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 ===
[[File:Alarm acknowledge.png|thumb|200px|Comment dialog]]
When alarm is 'taken care of' you can acknowledge this by pressing the button 'Acknowledge alarm'. When doing so a dialog pops up providing to opportunity of adding a comment, presented in Figure 'Comment dialog'. If there is no need to comment, simply leave the field empty and save. The alarm is thereafter marked as 'acknowledged' with the remark A and if a comment is added it is also 'commented' with the remark C. To view the existing comments for an acknowledged alarm, or to add new comments, mark it in the table and press the button 'Show comment'. This will result in a panel appearing to the right of the table as can be seen in Figure 'Comment history panel'.

[[File:Alarm comment panel.png|thumb|left|600px|Comment history panel]]
 

The existing comments for the alarm is presented in a list in reversed chronological order along with date and user. To add a new comment press the 'Add new'-button at the bottom of the panel. The panel can be hidden again by either pressing the 'Hide'-button at the bottom of the panel or the 'Hide comment' button at the bottom of the alarm table.

=== Search alarm ===
The alarms are presented in pages with 50 hits in each which are stepped through by the use of the arrow buttons at the bottom of the panel. To narrow down the search result, specify dates using the "'''From'''" and "'''To'''" options above the table and/o by entering search expressions for the resource, message, severity and category columns. It is also possible to order the search by the columns :resource, triggered on, message, severity and category. When the automatic update is run, or if the "'''Update alarms'''"-button is pressed, the new alarms which fit into the currently selected page, with search expression and ordering taken into consideration, is incorporated into the page content. If there exist new alarms which do not fit into the currently selected page an information icon appears on the "'''Update alarms'''"-button. It will disappear either when you choose to press the button, switch page or when the next automatic update is run and there are no new alarms outside the page.

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

=== Block alarms ===
Sometimes it might not be relevant to show all existing alarms in the portal. For instance, when an alarm is being handled but is not yet ready to be acknowledged. In such cases it is possible to block a set of alarms which fulfill certain requirements using the red alarm block icon in the right bottom corner of the table, see Figure "Block alarm for WCU". To block alarms for one specific WCU, select it in the grid before pressing this button. The appearing window lists all existing alarm blocks. To create a new blockage, press "Block alarms" and enter the conditions in the appearing dialog, an example of which is presented in Figure "New alarm block".

[[File:Block alarm.png|thumb|400px|Block alarm for WCU]]
[[File:New alarm block.png|thumb|left|150px|New alarm block]]
 

Alarms can be blocked for a specific WCU, selected in the grid, or for all WCUs. If the logged in user is an administrator, the blockage can be put in place for all users or for the current user. If this is not the case, the user options are hidden and alarms can then only be blocked for that user. Additionally, it is possible to select one or several severeties and/or categories to block. If no severity and/or category is selected the alarms of all severities/categories will be blocked. End with naming the alarm block and save it. It will now appear in the list as presented in Fiugre "Block alarm list" and from here it is possible to edit or delete it. Edit the block by either double-clicking the list tile or by pressing the pen icon. To delete it simply press the green alarm button.

[[File:Block alarms list.png|thumb|left|150px|Block alarm list]]
 

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

Creating a Task

2020-06-26T11:58:35Z

Erika: /* 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).

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

=== 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 (optionally including 'Snapshot' and 'Extended data')
*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 data capture module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data, and ECU-internal signals read by CCP or XCP. To create a Signal Reader 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. For instance, the audio and video modules relies on the Signal Broker API of Signal Reader for evaluating start and stop trigger expressions. Moreover, the Signal Broker gives programmatical access to signals for Rapid Prototyping tasks. Read more about this in [[WICE Signal Broker API]].

A Signal reader task can 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 requests in the sequence file may be for reading DTCs, and in such cases you can select the option of also reading associated ''Snapshots'' or ''Extended data''. An example of this can found in Figure "Sequence Files References in .haf File".
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]]

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

==== WICE internal signals ====
In addition to CAN and FlexRay signals, a number of internal signals are also available. The following WICE-internal signals are supported:
{| class="wikitable"
!'''Signal name'''
!Description
|-
|Accelerometer_X
|The value of the X direction of the WCU's built-in accelerometer.
|-
|Accelerometer_Y
|The value of the Y direction of the WCU's built-in accelerometer.
|-
|Accelerometer_Z
|The value of the Z direction of the WCU's built-in accelerometer.
|-
|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, a Tester Present diagnostic request (with suppress Positive Response bit set) 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 ===
[[File:SWDL new task.png|thumb|791x791px|New SWDL task]]
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table.

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

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

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

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

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

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

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

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

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

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

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

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

In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.

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

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

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

Alarm

2020-06-26T11:48:27Z

Erika:

<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. To further inspect the resource for which the alarm occurred it is possible to base a search in the vehicle- or task tab using a right click option. 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. 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. Here it is possible to restrict the search to a specified time interval by checking the boxes "'''From'''" and "''''To'''". It is also possible to only select one of the two thus searching for all alarms from a certain date or after a date. However, if the "'''To'''"-option is selected this means that the automatic update of alarms is temporarily switched off, which is notified with a warning icon. In addition, you can 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 ===
[[File:Alarm acknowledge.png|thumb|200px|Comment dialog]]
When alarm is 'taken care of' you can acknowledge this by pressing the button 'Acknowledge alarm'. When doing so a dialog pops up providing to opportunity of adding a comment, presented in Figure 'Comment dialog'. If there is no need to comment, simply leave the field empty and save. The alarm is thereafter marked as 'acknowledged' with the remark A and if a comment is added it is also 'commented' with the remark C. To view the existing comments for an acknowledged alarm, or to add new comments, mark it in the table and press the button 'Show comment'. This will result in a panel appearing to the right of the table as can be seen in Figure 'Comment history panel'.

[[File:Alarm comment panel.png|thumb|left|600px|Comment history panel]]
 

The existing comments for the alarm is presented in a list in reversed chronological order along with date and user. To add a new comment press the 'Add new'-button at the bottom of the panel. The panel can be hidden again by either pressing the 'Hide'-button at the bottom of the panel or the 'Hide comment' button at the bottom of the alarm table.

=== Search alarm ===
The alarms are presented in pages with 50 hits in each. To step through the pages use the arrow buttons at the bottom of the panel.

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

=== Block alarms ===
Sometimes it might not be relevant to show all existing alarms in the portal. For instance, when an alarm is being handled but is not yet ready to be acknowledged. In such cases it is possible to block a set of alarms which fulfill certain requirements using the red alarm block icon in the right bottom corner of the table, see Figure "Block alarm for WCU". To block alarms for one specific WCU, select it in the grid before pressing this button. The appearing window lists all existing alarm blocks. To create a new blockage, press "Block alarms" and enter the conditions in the appearing dialog, an example of which is presented in Figure "New alarm block".

[[File:Block alarm.png|thumb|400px|Block alarm for WCU]]
[[File:New alarm block.png|thumb|left|150px|New alarm block]]
 

Alarms can be blocked for a specific WCU, selected in the grid, or for all WCUs. If the logged in user is an administrator, the blockage can be put in place for all users or for the current user. If this is not the case, the user options are hidden and alarms can then only be blocked for that user. Additionally, it is possible to select one or several severeties and/or categories to block. If no severity and/or category is selected the alarms of all severities/categories will be blocked. End with naming the alarm block and save it. It will now appear in the list as presented in Fiugre "Block alarm list" and from here it is possible to edit or delete it. Edit the block by either double-clicking the list tile or by pressing the pen icon. To delete it simply press the green alarm button.

[[File:Block alarms list.png|thumb|left|150px|Block alarm list]]
 

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

File:Block alarms list.png

2020-06-26T11:10:12Z

Erika: Erika uploaded a new version of File:Block alarms list.png

File:New alarm block.png

2020-06-26T11:07:48Z

Erika: Erika uploaded a new version of File:New alarm block.png